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

Report your 2.1 OTA error /bugs/complaints here.

trj44 said:
I got my update this morning, so far everything seems ok, except the lock button doesnt lock the phone anymore. It unlocks fine. Anyone seen this one yet?
Click to expand...


Finally fixed the problem on mine.
Download "spare parts" app. Select End Button Behavior. Select Go To Sleep.
Hope this works for you.
 
Got my notification to do the OTA update last night:

1. Most important/annoying issue: I had been using Spare Parts so that I could hit my "End" button to either take me Home, then lock my screen when anywhere on the phone, or to just lock the screen when already Home. That functionality is completely lost. How do I reconfigure this, and how am I supposed to lock the phone besides letting it auto-lock? This seems liek a huge oversight. Someone in my thread on this helped by telling me I can use Spare Parts to lock the screen, which is helpful for some of you with this issue. However, previously I could also tell it to take me home, then press again for lock, and I can't anymore.

2. I had been using the No Call Log app so that when a call ended, it shot me right back to my home screen. The app still works, but now it takes waaaay long to go back to home, making it completely useless. Any ideas/alternatives?

3. When I have the Doggcatcher podcast app playing, now I get both a notification bar icon for the Doggcatcher player which is fine and I use, as well as something called "Doggcatcher keep-alive" with the subtitle "playing audio" which is a little soundwave icon...what is this, and how do i get rid of it? I dont need two notification icons for this, and it wasn't like this on 1.5.

4. The Music app is significantly slower, both to load, and when responding to presses and volume changes. Really, really annoying. Any ideas here?

5. Finally, when I hit the back button in Google Voice, it takes me Home, but then really quickly back to my inbox...I have to use the Home button to actually go and stay Home...is this a 2.1 bug?

Frankly, I'm considering this update to have some seriously unacceptable problems, especially based on the trouble others are having. I don't even want the Incredible, but I'm wondering at what point I decide I have to argue my way to a super early upgrade.
 
Battery life SUCKS. I don't know what would be causing it but it takes forever to charge and lost 40% battery over night with good service where i normally lose 5-10% over night
 
Posted this in its own thread but thought I should copy it here:

Just manually upgraded to the 2.1 OTA from stock 1.5. Did a factory reset prior to upgrade. Everything seems to be working fine except that I get this error message when trying to install any app:

Installation error: Insufficient storage available

When I check the phone storage settings I see this:

SD Card: 7.39GB total space - 7.27GB available space
Internal phone storage: 136MB

Also, I'm noticing that the "Format SD Card" option is greyed out. Any ideas what could be going on here?

Edit: A factory reset solved the problem.
 
1. blue-tooth phone book transfer not working

2. email message indicator always shows "1" message waiting

3. with all the features were missing, feels like we got version 2.1 Lite, i wanted full 2.1, guess ill be looking close at that evo!
 
2.1v3 works like a charm very fast. Having no problems. I see my signal shows 50% don't know my exact signal until I make a call. You tube works better. Got handcent and was able to use the speech to text option. Got Swype from another contributor. I haven't received the official OTA but I have no complaints about it cause it does so much more than 1.5 even on its bad day.
 
jordn613 said:
2. I had been using the No Call Log app so that when a call ended, it shot me right back to my home screen. The app still works, but now it takes waaaay long to go back to home, making it completely useless. Any ideas/alternatives?

5. Finally, when I hit the back button in Google Voice, it takes me Home, but then really quickly back to my inbox...I have to use the Home button to actually go and stay Home...is this a 2.1 bug?
Click to expand...

Regarding "Not Call Log," when you open the app, it allows you to choose a speed (from "N1" to "G1", which is fast to slow), so have you tried it on the "N1" setting?

I think the Google Voice double-back-out bug is a bug in Google Voice, not necessarily in 2.1 (even if it didn't happen that way in 1.5), so hopefully Google will fix it.
 
Caddyman said:
seems like the OTA has lots more bugs then v3...
Click to expand...


I was thinking the same thing. I don't have the voice problem on my device. The only problem that I see, occasionally, is that the picture is slow to display when I receive a call. Oh, and even though my slot cycle is at 1, every once in awhile a caller will say it rang a lot before I answered.

I use beautiful widgets, so i don't have the HTC clock/weather issue.
 
Caddyman said:
seems like the OTA has lots more bugs then v3...
Click to expand...

The sad thing is, people are actually going to believe that the OTA is "better" than v3, because they already know about the bugs that were reported in the leaks, so they don't have to do the troubleshooting from scratch. For instance, we won't have fifty pages of:

"What's your time without a signal?"
"How do you find that?"
"Mine is 50%!! Holy crap!"
"What's yours?"
"It's 27%."
"Are you indoors?"
"Did you do *228?"
"What part of the country are you in?"
"Does it depend on your PRL"?
"My phone doesn't have a signal half the time!!! Am I missing calls?!?!"
"I think I fixed mine... I put it in airplane mode, then plugged it in, then walked around the block, then did jumping jacks, then unplugged it, then put it in airplane mode again, then blew on it, then out of airplane mode, and the number is shrinking!"

...Because now we already know to expect it, how to fix it, and that it's not a big deal.
 
thenestor said:
Regarding "Not Call Log," when you open the app, it allows you to choose a speed (from "N1" to "G1", which is fast to slow), so have you tried it on the "N1" setting?

I think the Google Voice double-back-out bug is a bug in Google Voice, not necessarily in 2.1 (even if it didn't happen that way in 1.5), so hopefully Google will fix it.
Click to expand...

Yep, tried it on multiple settings, always takes at least 5 seconds, where it used to be instant. And such a blatant bug in a native Google app used for a basic phone function is pretty sad.

My battery seemed to drain faster today than usual, also.
 
I feel like I was at a daily battery life that was really acceptable ,and pretty good. If this keeps up, I'm not sure how I should be handling things. What's Verizon going to do for me, give me new phones over and over claiming it's just a "bad" one? What options do we have, seeing as Verizon is unlikely to respond with a prompt fix for this on a phone at "end of life" or whatever.
 
I've read from OTD's thread that the 50% bug doesn't seem to effect her phones battery, but from my experience it's a must for me to do the airplane trick.. considering going to have a talk with Verizon, I recently just received this replacement for problems with the leak v3 audio bug, and honestly would rather just have a new phone with 1.5.. I don't believe this phone was meant for 2.1. just my opinion of coarse.
 
gpa111 said:
Went to a verizon store, and they have no knowledge of any issues with the update...

Why don't their engineers read any forums? lol
Click to expand...

Because if they did then they would learn that the world is not perfect. As a former engineer, the worst thing in your world is hearing that everything you just did is not perfect. As an engineer, my first response was always "they are doing it wrong" and I still have that response to many things I deal with today.

LOL.
 
I was using nav today, and got a call on the phone. I hit ignore the call so I could continue navigating, but this gave me a blank screen. All but the notification bar. (same thing that happened while I browsed the market this morning).
Saw the missed call, and the nav symbol both in my notification bar, so I pulled it down, and selected nav. Back to the black screen.
Pulled it down pressed on my missed call to clear that message. Once in my call log, I pressed the back button, and it took me all the way out to the homescreen. Nav stopped.
Had to set it all back up again. All this while driving. I didnt crash though, and found my way home.

One thing I must say to all those complaining about the battery though. Mine was horrible yesterday after upgrading, but I must say I do notice it improving. Just like when the phone was new and it improved over time. Be patient. In a day or so, after a few charges, itl be back to where you want it.
 
HTCthebestdroid said:
I've read from OTD's thread that the 50% bug doesn't seem to effect her phones battery, but from my experience it's a must for me to do the airplane trick..
Click to expand...

It's a must for me too. If I forget to do this my battery won't last throughout the day.

I'm curious to see if anyone experiences the awake time problem that I have. When I put the phone into airplane mode, the awake time continues to climb.
 
SirEagle said:
The 50% bug is time without signal not awake time.
Click to expand...
Right.
Although about the awake time. My phone up time is 31:26:45
And my awake time is 30:23:24
Weird how close they are. I dont believe that is right.
But like I said, I have noticed improvements in my battery life already since upgrading yesterday and having it rapidly drain.
I honestly dont think airplane mode is necessary for anyone at all. The battery thing will settle.
 
You must log in or register to reply here.
Back
Top Bottom