• 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

jlrosell said:
Very few people here have gotten the OTA at all. I dont think you can really make any conclusions whether or not v3 users will get it yet.
Click to expand...
Very true, I'm just hoping for some sliver of hope since I bought my eris with v3 already on it so I didn't have a choice. I'd love the more polished version.
 
Also, I don't think people should draw conclusions about the difference in file size between the update and the 2.1v3 leak. There's a whole bunch of reasons as to why there's a difference - checksumming files, different compression method, code changes... I'm more intrigued by the 2.1v3 leak and the OTA updates having the same version numbers on Firmware and Kernel. I guess Verizon have 2 options - only deliver the payload to people whose versions are below a certain level, or just blanket the whole Eris population with it regardless of version. Hopefully it's the latter but I fear the former (my personal opinion). Doesn't really matter though, as I'm sure some kind soul will make the update available for a manual install...

BTW I just got my Eris 2 weeks ago. Loving it... 3 days after I got it, found out about 2.1v1 leak. An hour after installing that, I found out about 2.1v3... :-|

Sitting, waiting patiently for 2.1 OTA Official.

A question for the people who have it installed - is Voice Dialling on Bluetooth supported now?
 
Geesh I wasn't anxious until I read this thread...now I feel like I just drank 12 cups of coffee and its Christmas morning!!!

Come on already!!!

*mashes home button again*
 
it is defo for real, guy posted shots from a digi cam with all the update screens he was getting that couldn't be photoshopped.
 
I just got a notification of 3 updates but going to My Downloads failed. It seems the Market is down, at least for me. I was hoping for a System Update. Oh well, maybe tomorrow.

Sent from my Eris using Tapatalk
 
Gobd said:
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.[/

any chance you have insructions for thosr of us using a mac. thanks for posting this btw
Click to expand...
 
So I can't download the update unless I have 78 MB free on my phone's drive? Gah, I have 71 after clearing all of my cache.
 
philr5150 said:
A question for the people who have it installed - is Voice Dialling on Bluetooth supported now?
Click to expand...

Unfortunately, no Android phone supports voice dialing via Bluetooth, and Google has no stated intention of ever adding it:

Issue 1181 - android - [VoiceDial] Voice confirmation for Voice Dialer - Project Hosting on Google Code

This has been listed as a "medium" priority "enhancement" for a couple years, despite being a basic feature on virtually every other phone, dumb or smart for the last 5+ years (except the iPhone until a year ago, but that's a different story).

I love my phone and the Android concept in general, but in a year when I'm due to renew I will most likely go back to AT&T and get an iPhone or similar if there are no phones that address this then. I make very few car calls, but it's horribly inconvenient to have no way to keep the phone in my pocket, press a button on the headset and say "call Home", as my crappy old Nokia did. It's worse that even once you do get connected manually, you can't force the screen lock to come on so you can put the phone in a pocket right away.
 
You must log in or register to reply here.
Back
Top Bottom