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

Help If you do the update, prepare for frustration!!

R

redfishsc

Well-Known Member
My phone woke me up at 11pm tonight (i go to be WAY earlier than that!) with a system update. I think it upgraded me to 4.1.2, which is what it has now.



I was running Nova Launcher Prime (I use it on all my devices, smooths out the pathetic custom interfaces/launchers on them so that they all work the same). The update choked mightily on Nova.

The Nova Prime icon disappeared, and the phone would lock up at EVERY command. Couldn't access Nova settings, or anything.


I managed to turn Nova off (not sure how, but it asked me which launcher, so I chose the native "home" launcher and tapped "always"). This returned me to the native launcher theme, which is nearly untouched on my phone (I never changed it, always used Nova). Even with Nova off, the phone would freeze up when opening the app drawer or tapping "home".

After rebooting repeatedly, I turned on the 4G service, and almost immediately got a message saying that i have been upgraded (an insult at this point lol!).

Once I got that message, the phone smoothed out, but Nova Prime was 100% gone from the phone....except that Google Play thought I still had it. I had to open Play, search for Nova Prime, uninstall it, and reinstall it.

It seems to be working for now. For now.

Not rooted, btw.
 
What did this update do, exactly? In other words, what is different about "tonight's" phone versus the system I had prior to the update???
 
After reading this thread, I checked for an update on my commando and I see there is one available. It's 23MB in size.
It tells you to go to http://vzw.com/commando4gltesupport for more information but the info on that web page shows the Jelly Bean update, not this current one.
Guess I'll wait and see if they update that page before I actually install it.
​
 
Yeah mine still pretty much sucks, freezes on random screens requiring me to hit the power button/sleep mode repeated times. Often freezes on the unlock screen.

Turrible update!
 
redfishsc said:
Yeah mine still pretty much sucks, freezes on random screens requiring me to hit the power button/sleep mode repeated times. Often freezes on the unlock screen.

Turrible update!
Click to expand...



I doubt its the update, its likely your phone.

I know of three other people and myself ( total of 4 ) that the update is running fine. I still have no idea what it was but my phone is running quite well.
 
I updated last night, and I can report that my phone runs very slowly, but only during boot-up and for about 5 minutes after.

Upon further investigation, it seems that there is a period of time during and after start-up where the phone uses only one processor core, and the other remains in sleep. There is also a large amount of CPU usage dedicated to "system" rather than "user". I used the app System Panel to gather this information.

After a while, the second processor core will start to take some of the work and my phone seems as good as ever - maybe a little faster, it's hard to tell. Otherwise, I don't see much difference. What's the point of disabling one processor core? Is it some poorly-conceived multi-threading patch? :confused:
 
JKH62 said:
I doubt its the update, its likely your phone.

I know of three other people and myself ( total of 4 ) that the update is running fine. I still have no idea what it was but my phone is running quite well.
Click to expand...

No way, the phone worked just fine prior to the update, and immediately after is when it went ape.

Seems to have smoothed out, only improvement is that the Gshock watch seems to have a more stable connection...... Maybe
 
Just got my phone, so it came upgraded... (or got upgraded as soon as I turned it on) but it does freeze on the unlock screen between the "tap twice" and "tap again" screens. I'm finding that I'm popping the battery to fix this... unless there's a magic key sequence to reboot?
 
For anyone who is having issues with the update, it may be your phone. I recently got a warranty replacement... the phone I had before this one had all of the typical issues (lock-ups, can't get past unlock screen, etc.) I upgraded to M050, and it got worse - the CPU was constantly running at 50% in the SYS category, my battery life (with the extended battery) was about 4 hours. Then one day the phone just wouldn't turn on, not even after I removed and replaced the battery. So I got a warranty replacement.

The warranty replacement came with M040... it ran fine, exactly zero problems, for a few days. So I went ahead and upgraded to M050. The phone still runs great - my battery life is back up to about 24-36 hours, it's not slow, it doesn't lock up, etc. The only remaining problem is that every morning when I re-sync the phone and G-Shock watch, I get the "Unfortunately, BluetoothLE has stopped" error. I have to reboot the phone to restart BluetoothLE.
 
I found you can just turn off bluetooth then restart it and Bluetooth LE will operate just fine. No need to reboot phone.

CommandoJ said:
For anyone who is having issues with the update, it may be your phone. I recently got a warranty replacement... the phone I had before this one had all of the typical issues (lock-ups, can't get past unlock screen, etc.) I upgraded to M050, and it got worse - the CPU was constantly running at 50% in the SYS category, my battery life (with the extended battery) was about 4 hours. Then one day the phone just wouldn't turn on, not even after I removed and replaced the battery. So I got a warranty replacement.

The warranty replacement came with M040... it ran fine, exactly zero problems, for a few days. So I went ahead and upgraded to M050. The phone still runs great - my battery life is back up to about 24-36 hours, it's not slow, it doesn't lock up, etc. The only remaining problem is that every morning when I re-sync the phone and G-Shock watch, I get the "Unfortunately, BluetoothLE has stopped" error. I have to reboot the phone to restart BluetoothLE.
Click to expand...
 
CommandoJ said:
For anyone who is having issues with the update, it may be your phone. I recently got a warranty replacement... the phone I had before this one had all of the typical issues (lock-ups, can't get past unlock screen, etc.) I upgraded to M050, and it got worse - the CPU was constantly running at 50% in the SYS category, my battery life (with the extended battery) was about 4 hours. Then one day the phone just wouldn't turn on, not even after I removed and replaced the battery. So I got a warranty replacement.

The warranty replacement came with M040... it ran fine, exactly zero problems, for a few days. So I went ahead and upgraded to M050. The phone still runs great - my battery life is back up to about 24-36 hours, it's not slow, it doesn't lock up, etc. The only remaining problem is that every morning when I re-sync the phone and G-Shock watch, I get the "Unfortunately, BluetoothLE has stopped" error. I have to reboot the phone to restart BluetoothLE.
Click to expand...

Might be having the same battery issue. I wonder how Verizon will handle the replacement since I bought it used on Ebay. It only started to drain fast after the update, so maybe they will claim responsibility and give me a warranty replacement???
 
If you are not the original purchaser, or even if it's not on the same line you purchased it for then Verizon will not warranty it. Yes, you can save money buying used phones on eBay or Craigslist but the down side is that you are on your own when it comes to warranty issues.
 
You must log in or register to reply here.
Back
Top Bottom