Verizon's Twitter.
I believe the twitter that said this was an "unofficial" one, but that detail is also just hearsay. At any rate within 4 days is definitely a much more optimistic timeline than 2 weeks. Here's hoping.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Verizon's Twitter.
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.
I believe the twitter that said this was an "unofficial" one, but that detail is also just hearsay. At any rate within 4 days is definitely a much more optimistic timeline than 2 weeks. Here's hoping.
just wondering ...... your not taking credit for this are you ? seems you wrote the exact thing i QUOTED from someone else just without the quote but ty for your help
Just to let everyone know, my wife has 1.5 on her Eris..(she didn't trust the leaks)...and she could end up being the hero (no pun intended) for everyone here. I have her on constant watch for the update, and she will not update until I have a chance to copy the text log. I still haven't read all the instructions how to do it, but I believe as long as I keep telling the phone to do the update later, I should still be able to set everything up.
So yeah, if nobody has a link for us by the time her phone gets the update, I can guarantee that you'll get it from me.
Just to let everyone know, my wife has 1.5 on her Eris..(she didn't trust the leaks)...and she could end up being the hero (no pun intended) for everyone here. I have her on constant watch for the update, and she will not update until I have a chance to copy the text log. I still haven't read all the instructions how to do it, but I believe as long as I keep telling the phone to do the update later, I should still be able to set everything up.
So yeah, if nobody has a link for us by the time her phone gets the update, I can guarantee that you'll get it from me.
im no moderator but can we keep the "i dont have it yet" post to a minimum so that the info needed for when we see that "i got it" post doesnt get lost
but for real....i +1 thatUncalled for and inappropriate.
What, the whining about someone not posting the log or a link? You're right, it is inappropriate and uncalled for. You would think someone was passing out checks for a million dollars.
The same questions being posted over and over and over because people can't be bothered to read the previous posts gets old. It also dilutes the usefulness of the forum to get real information.
So, if anyone was offended by my post I apologize. But please think about what you're doing here. The update is being pushed. It will eventually get to you, or someone will post the file, or Verizon will put it on the support page. Might not happen today or tomorrow, but it will happen.
i am also set up and waiting......so hopefully it wont be much longer for the people that are enduring this long ass thread......lol
I believe I'm all set up for it. I installed SDK to the C: drive, used the command prompt to enter the directory for SDK, and then entered the command to log the update and hit enter....all it did after that was leave a blinking cursor underneath. I'm assuming if I repeat the process when the update comes, the cursor will give way to a bunch of text.
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:...
Oh, for f**k's sake! Must we have these stupid instructions and reminders posted so many f**king times!
Cut it out!!
wow... for the 12457543054352343454657654343208767954250 time, it comes out only to a certain number of customers a day and the release is random (or possibly regional), either way you would have better luck getting a definitive answer from a magic 8ball considering none of us have control over the OTA release
