• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

2.1 OTA Beginning 5/11/2010

Hello
I just clicked on my QuickSettings icon and at the top it reads that I have "Phone free: 44% (70Mb)"
it also reads that I have "SD card free: 92% (6990Mb).
If we need 77Mb of phone space, where is it going to go? All my apps are already on my SD card. How do we make room for the new update?
 
I just got the Google maps notification that people were discussing in this thread yesterday, but when I try to update it, it keeps saying 'download unsuccessful'. Anyone have an idea why? I have 2.1 v.1 BTW, dont know if that has something to do with it.

I had the exact same problem - I connected to my office WiFi and the update downloaded and installed without a hitch - don't know why, but that worked for me -
 
Hello
I just clicked on my QuickSettings icon and at the top it reads that I have "Phone free: 44% (70Mb)"
it also reads that I have "SD card free: 92% (6990Mb).
If we need 77Mb of phone space, where is it going to go? All my apps are already on my SD card. How do we make room for the new update?

The update replaces files that already take space in memory.
 
Hello
I just clicked on my QuickSettings icon and at the top it reads that I have "Phone free: 44% (70Mb)"
it also reads that I have "SD card free: 92% (6990Mb).
If we need 77Mb of phone space, where is it going to go? All my apps are already on my SD card. How do we make room for the new update?


Apps on your sd card? Are you rooted? If not how did ya do this?
 
Hello
I just clicked on my QuickSettings icon and at the top it reads that I have "Phone free: 44% (70Mb)"
it also reads that I have "SD card free: 92% (6990Mb).
If we need 77Mb of phone space, where is it going to go? All my apps are already on my SD card. How do we make room for the new update?

Menu > Settings > Applications > Manage Applications

Go through each app and clear the cache for those you can. You'll prolly get the 7 or 8 mb you need.
 
God damn, ok here's how to log the URL of the OTA update since everyone and their mother supposedly knows how to do this but is unwilling to provide instructions. This is for Windows. First, install HTC Sync this includes the USB driver you need. On your phone go to menu > settings > application settings > development and check USB debugging. Next unzip the Android SDK anywhere and copy the tools folder to your C: drive. Now go to start > run and type in cmd. Then type in cd C:\tools. Then type in adb logcat > logcat_accept.txt and you're good. I assume you do this right before you start downloading the update.
 
God damn, ok here's how to log the URL of the OTA update since everyone and their mother supposedly knows how to do this but is unwilling to provide instructions. This is for Windows. First, install HTC Sync this includes the USB driver you need. On your phone go to menu > settings > application settings > development and check USB debugging. Next unzip the Android SDK anywhere and copy the tools folder to your C: drive. Now go to start > run and type in cmd. Then type in cd C:\tools. Then type in adb logcat > logcat_accept.txt and you're good. I assume you do this right before you start downloading the update.

Thank you for the "Angry" assistance. ;)
 
For all those who have received the OTA...why haven't you done what is explained in the following link (obviously if you didn't know, then not your fault)?

Leakers about the OTA - xda-developers

Please, if you can, do this. If you do, there is no more waiting for the OTA and everyone can just install it directly to their phone. Also, it gives the devs something to work with to look at possibly rooting the official 2.1.

You seem very anxious to have people do this, yet I and several others have said that those instructions may as well be in Latin. I have no idea what that means. If they want someone to do what they are asking, then someone needs to explain the process in plain English.
 
So far, everyone I've read said that apps were retained and files on the SD card weren't affected. Of course, there's always some risk.
 
Back
Top Bottom