2.1 OTA Beginning 5/11/2010

[orcsbane13]

What about voice to text? That is still on the PDF and it is NOT in the 2.1 v3 leak.

I wonder about that too...it's the one thing I'm REALLY excited about!

leak v3 does support voice to text it's just not mapped onto the default keyboard. I use betterkeyboard and it works like a charm.



Sent from my Eris using Tapatalk

 

[AdrianC14]

Anyone get the update yet? I am hearing it's no different from leak v3 .....

There are a lot of differences like for example, in the OTA, there is multitouch in Google Maps.

 

[kbergou21]

I live in Jackson, Michigan..when will i recieve my update?

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

 

[BigBeefy]

really? Same question, same answer going to be given. Hundreds of posts and its all the same crap. READ first before posting. How is that for something new? You people are something else. Its like a bunch of first graders asking if we are there yet. Give it a break.
How about this. WHEN YOU GET IT, POST YOU GOT IT. Dont ask if you got it anymore.

 

[AdrianC14]

when wil i get my update??!?! i live in Jackson, Michigan.

I can tell you that you will receive the update in the next two weeks.

 

[goose42195]

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

My magic eight ball says I'm next!

 

[deathratlehead]

If I remember correctly, you can go back to v2 of the leak from v3, correct? I'm wondering if we should flash back to that during the rollout. I would probably increase our chances of getting it. I'm pretty sure someone said you could do it because the bootloader is the same....although I admit to having no technical knowledge to support it.

 

[ndsustudent]

If I remember correctly, you can go back to v2 of the leak from v3, correct? I'm wondering if we should flash back to that during the rollout. I would probably increase our chances of getting it. I'm pretty sure someone said you could do it because the bootloader is the same....although I admit to having no technical knowledge to support it.

I don't believe that is possible. There was someone posting this in another thread. Basically the bootloader will not let you flash to an older ROM. Either way, Verizon said that everyone (hopefully implying us with v3) will get the update. Also I thought I read in another post that someone with v3 got it but I am not sure.

 

[tilejoesham]

If I remember correctly, you can go back to v2 of the leak from v3, correct? I'm wondering if we should flash back to that during the rollout. I would probably increase our chances of getting it. I'm pretty sure someone said you could do it because the bootloader is the same....although I admit to having no technical knowledge to support it.

dont think there is a way to go back at this point

 

[wamsille]

You cannot go back to v2 from v3. Another user tried it and posted the error message that they received. You are "stuck" with v3 for now. You should see the official file on VZW's site or on pcdphones.com by 5/16 more than likely. If not, well.....


Honestly, it's a software update for your phone. I have most of the functionality (sans multi-touch in Google Maps) on my v3 leak. Go to XDA and get the HTC_IME mod for the keyboard and you will have the voice to text feature. Another user here posted the 3D gallery app that works perfectly with v3 on the Eris.

 

[Mattius14]

You gotta admit, 26 pages of forum comments looks a little daunting to someone just finding our thread. We are now hitting the influx of people coming in asking the old questions because they don't want to go through what we've gone through for the last two days straight.

Which is selfish.

To answer the much asked question of why exactly we're even bothering going through these motions, the most reliable information we have is that the update may come to all of us within the next two days or two weeks. That's all well and good, but since we've been waiting for three months, having it now as opposed to in two weeks sounds like a much better prospect. Imagine starving in the desert for two days only to have some asshole hold a sandwich in front of you but tell you that you might not get it for another 2 hours. If someone is there with you and could get you that sandwich earlier, you'd appreciate someone making that effort. If you can wait for that sandwich, then wait.

Some of us would like to have our sandwich now if we can.

[Update - You can also insert a cheesy stale donut/eclair reference in there somehow, but I used up my analogy rights already]

 

[szymchack]

It says that everyone should have it by May 16th.

 

[FredNitz]

You gotta admit, 26 pages of forum comments looks a little daunting to someone just finding our thread. We are now hitting the influx of people coming in asking the old questions because they don't want to go through what we've gone through for the last two days straight.

Which is selfish.

To answer the much asked question of why exactly we're even bothering going through these motions, the most reliable information we have is that the update may come to all of us within the next two days or two weeks. That's all well and good, but since we've been waiting for three months, having it now as opposed to in two weeks sounds like a much better prospect. Imagine starving in the desert for two days only to have some asshole hold a sandwich in front of you but tell you that you might not get it for another 2 hours. If someone is there with you and could get you that sandwich earlier, you'd appreciate someone making that effort. If you can wait for that sandwich, then wait.

Some of us would like to have our sandwich now if we can.

[Update - You can also insert a cheesy stale donut/eclair reference in there somehow, but I used up my analogy rights already]

But there is the old adage: "You can't have your sandwich and eat it too."

 

[Mama Bee]

Dumb question but...

When the update comes through does it signal or alert you (like a text message or email) or does it just quietly appear and you don't notice it's there until turn the screen on? I was just wondering...

 

[mrshdavis]

It says that everyone should have it by May 16th.

Who Said that?

 

[tilejoesham]

Dumb question but...

When the update comes through does it signal or alert you (like a text message or email) or does it just quietly appear and you don't notice it's there until turn the screen on? I was just wondering...

this is on verizons pdf but it will just be in a notification and please folks like previously stated the redundancy is getting absolutely ridiculous

 

[Mattius14]

Dumb question but...

When the update comes through does it signal or alert you (like a text message or email) or does it just quietly appear and you don't notice it's there until turn the screen on? I was just wondering...

It should appear as an update icon in the top notification bar. When you pull the drawer down to see it, you should see "System Update Available" if it doesn't pop up in your face first.

 

[dawynkoop]

I'll take Eclair for 200 Alex.

 

[tilejoesham]

I'll take Eclair for 200 Alex.

+1

 

[tilejoesham]

does everyone know how to log this when it comes ? there was a post earlier that explained this very well and easily instead of some mumbo jumbo ill go find it and quote it i dont want it to get lost in all the posts

 

[tilejoesham]

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.

here goes folks best explanation on how to "SHARE" our update if it happens to pop up on your phone

 

[szymchack]

Who Said that?

verizon

 

[wamsille]

Who Said that?

Verizon's Twitter.

 

[tilejoesham]

Verizon's Twitter.

that wasnt the official twitter support from verizon is was verizon tech support or something like that the official verizon is @vzwsupport so take it as you will but @vzwsupport said 13 days so count on that and if you get it sooner consider it a bonus

 

[jlrosell]

does everyone know how to log this when it comes ? there was a post earlier that explained this very well and easily instead of some mumbo jumbo ill go find it and quote it i dont want it to get lost in all the posts

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.