-
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
- Thread starter deathratlehead
- Start date
-
- Tags
- htc droid eris
TDianna
Android Enthusiast
lol
And for the record, I myself am a habitual "last page" clicker on threads. On most forums I like to see where conversations are at before I jump in. If the conversation seems heated, highly discussed, I go backwards and see how it got there. At times this can be very telling as to how far off the rails a conversation has gone.
Most of the responses now bear little to no fruit. Commit to logging the file and wait for the the OTA. Or, if you already got the OTA tell us if you had 1.5, a leak or you were rooted. If you were on a leak, tell us what version if you can think back that far. If you will neither commit to logging the URL of the OTA or share your OTA experience, the only other suggestion I have is to keep mum on the whole situation or pass along updates you find to further the discussion.
Most of the responses now bear little to no fruit. Commit to logging the file and wait for the the OTA. Or, if you already got the OTA tell us if you had 1.5, a leak or you were rooted. If you were on a leak, tell us what version if you can think back that far. If you will neither commit to logging the URL of the OTA or share your OTA experience, the only other suggestion I have is to keep mum on the whole situation or pass along updates you find to further the discussion.
deathratlehead
Android Enthusiast
I just called PCDPhones to see if I could get information. The rep was really nice and researched it for me. He said that they would have the update available on the website in about a week and a half to two weeks.
TDianna
Android Enthusiast
I agree, most people are getting their update and either saying how fast their phones are or complaining that some features are not working. Can someone instruct me to save the update when I receive it so I can share it? (By the way my phone is not rooted)
These are the easiest instructions I have seen.
"Making a Log for Noobs
Alrighty, I'm going to do a really quick explanation and try to let people who aren't so tech savvy know how this works:
You need to find that thread above and download the SDK stuff, it will be in a zip file that you'll need to extract. For this to work as easily as possible, you'll want to rename that extracted file that holds all the contents to something shorter, for example "android-sdk". After you do that, open up My Computer, click on your C: drive, and drop it right in there, in the open.
Next you'll want to activate the debug mode on your phone. Do that by going to Settings -> Applications -> Development on your phone, and make sure that USB Debugging option is CHECKED. After it is, plug it into your computer via USB, and let it install itself. Your computer may ask you to restart, if it does, do it. It's necessary to make this work.
Once you're all set, you should be able to make a log. What you do is click Start Menu -> Run to open up a command prompt. This is where you'll be giving the SDK software you downloaded the command to create the log. In order to get your command prompt into the right folder, you have to change the directory it's looking at. If you dropped the "android-sdk" folder into your C: drive, you'll need to type "cd C:\android-sdk\tools" into your command prompt. If you did it correctly, you'll see the text in your command prompt change to show that file path, and the blinking cursor should be right after it.
NOW you're in the right place, and you can give the command to start creating a log. Type "adb logcat > logcat_accept.txt" BEFORE you accept the update to your phone, and hit enter. Type it with spaces included, exactly as you see it above. After you hit enter, accept the update and let your phone do its thing. Once your phone reboots after installing the update, your command prompt should change, and be ready to accept more commands. If it doesn't, you simply press "ctrl+C" on your keyboard to stop running the last command you entered. Once that is done, your log has been created.
To find this log, simply open up your C: drive in explorer, find your "android-SDK" folder, open the "tools" folder, and find the text file labeled "logcat_accept.txt". This is your log. Inside this file, should be the http address of where the download came from. This is what everyone is looking for."
TDianna
Android Enthusiast
Noobs...lol..Thanks for the information...
TDianna
Android Enthusiast
That's what a tech from Verizon told me last night on the phone.
mc48
Android Enthusiast
I can attest to that, I've read some of his tweets
. eh....still an okay guy. Being an interesting twitterer does not make you a good (or especially intelligent) person though. I lol'd when they had the recent twitter force follow bug. All the celebrities were forced to follow us boring everyday ppl for a change. And then when Twitter dropped everyone's follower count down to zero, you should have seen the celebrity uproar 
btw, here in SC and on 1.5...no update yet.
socarwolverine
Well-Known Member
Hey, I'm in SC too, no update yet but I'm on 2.1v3.I can attest to that, I've read some of his tweets
btw, here in SC and on 1.5...no update yet.
Papadroid
Android Expert
It is definitely looking that way. I still question whether we have seen any differneces yet. But there's not enough people that have it yet to truly make a clear conclusion, obviously.
Frisco
=Luceat Lux Vestra=
I, too am eager to start seeing postings and blog input from those who've spent some time with the OTA.
The list of changes from 1.5 is there in the pdf, of course (and it seems to have been modified at least once since it was published online).
I suspect that the v3 leak was yet to undergo only a bit of finishing up and cleaning up prior to being declared the OTA.
hitman_dreams
Newbie
I'm on v3 and that's exactly what my software info says. There are big differences though. I don't have the speech to text key on my keyboards and some other things too. At least, i've read that the 2.1 OTA will have that and others.
I saw the instructions on logging but I am having some problems. I am on 1.5.
I saved the android-sdk on my C drive.
I opened the command prompt. Changed Directories ran the command and got waiting on device. I hit control c to end command.
Then I mounted my phone and tried again. The second time I got a message saying The process cannot access the file because it is being used by another process.
Any ideas?
I saved the android-sdk on my C drive.
I opened the command prompt. Changed Directories ran the command and got waiting on device. I hit control c to end command.
Then I mounted my phone and tried again. The second time I got a message saying The process cannot access the file because it is being used by another process.
Any ideas?
zutmin
Well-Known Member
I don't believe you are supposd to mount your phone. That may be your problem. Enable USB debugging and don't mount.
philr5150
Newbie
Control-C doesn't kill the adb program. Press CTRL+ALT+DEL, select Task Manager, go to Processes, highlight adb, then press End Process. Then it should work.
As for fixing waiting on device, install HTC Sycn and make sure your phone's USB mode is set to HTC Sync, not disk drive.
TDianna
Android Enthusiast
Why did they remove the speech to text key?
midnight assassin
Well-Known Member
Really? 3 days?
Someone in another thread said Contol C would kill it. But I will take your word for it. I do have HTC Sync installed.
I will try the rest of the steps now. I am glad someone is willing to help. Honestly its not skin off my back if I don't share the update.
philr5150
Newbie
It kills the logging and terminates the program but it either doesn't dump itself from memory or Windows holds onto it as a rogue process. Whichever it is, you can kill it from Task Manager then start adb again.
Make sure your phone's USB mode is on HTC Sync though. If you need to change it you can do it from the notification area on the phone.
