Sleep issue with ota - Acer Iconia A500

I'm posting this in case someone sees something similar. I just updated ota from 4.010.11 to. 13 a couple days ago. I noticed suddenly when I checked battery usage that the system was awake all the time. It never slept. I ended up backing up my apps/data and wiping and reinstalling 4.010.11 fresh by itself. Seems something wigged out between all of the back to back ota's.
After reinstall and ota update to 4.010.13 my system now sleeps again.

dottat said:
I'm posting this in case someone sees something similar. I just updated ota from 4.010.11 to. 13 a couple days ago. I noticed suddenly when I checked battery usage that the system was awake all the time. It never slept. I ended up backing up my apps/data and wiping and reinstalling 4.010.11 fresh by itself. Seems something wigged out between all of the back to back ota's.
After reinstall and ota update to 4.010.13 my system now sleeps again.
Click to expand...
Click to collapse
Maybe it was something screwed up in /data. By any chance did you apply any mods/patches to the broken install?

Nope. No patches. Was true ota progression.

dottat said:
Nope. No patches. Was true ota progression.
Click to expand...
Click to collapse
Hmmm. . . Well sometimes odd things happen, as long as its working now

Related

Update this AM in US, but...

Took an OTA update this AM in the US, but nothing seemed to change. Switched back to stock recovery, took update, downloaded, installed (no errors), rebooted, message said somethings about a Pre-Install APK, then nothing. Tablet info says I am now up to date, but nothing else seems to have changed.
I'm still on custom kernel (thor's), still on 3.1. I forget the GEN info, but I don't think that changed either.
Was this a pre-update update?
I got the update too.
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Ditto. Used stock recovery and unroot to get it to install. It's Gen 2.
Sent from my ADR6300 using XDA App
Same here, updated with no errors. Didn't lose root and it still says 3.1
With the update to 3.1 they sent out a smaller update a few days earlier. This one may be the same thing.
It's just a small update, about less than 20MB download. But I have no idea what's been changed.
GShyneDM said:
I got the update too.Same thing happaned to me
Seemed to freeze up on me after installing (Gave it about 15 minutes on a black screen after installing, before I gave up). I had to power it off and back on. After booting, I got a message that the "Update Was Successful"
Kernal Number is: 2.6.36.3
Build is 4.010.13_COM_GEN2
But still Android 3.1
Click to expand...
Click to collapse
Same thing happened to me...
System Update
System Update 4.010.13
(14.49MB).
A new system update is available for your device. A network connection is required to download and update your device. You may incur additional charges from your service provider. Thank you for not replacing me with the HP TouchPad.
Click to expand...
Click to collapse
i'm gonna hold off on installing this until i know more of what its all about...
I uploaded the zip in development, I don't think I'm gonna install either...
I also installed the 14MB update today. The tablet was rooted, but otherwise stock. After the update the tablet remains rooted. I have experienced no other issues.
Cheers,
A
I had the same experience as above. So far no issues.
This actually made me worried about the possibility of us to get an update to 3.2 on 8/25. Otherwise, they should just pass this incremental.

Frequent SOD after 4.3 update

I started with a stock 4.2.2 and the only modification to the phone was unlocked bootloader and root (no custom recovery or anything like that).
The phone has had a couple of SOD instances but they were very rare. After doing a sideload OTA update I've had it SOD twice in the last 2 days. I haven't re-rooted this phone (waiting for SuperSU to be less...hacky) or installed anything to mess with power management. I read that there may be a netflix SOD issue but it's not applicable as I don't have the app.
Anyone else get SOD with 4.3 or am I the only one?
smapdi said:
I started with a stock 4.2.2 and the only modification to the phone was unlocked bootloader and root (no custom recovery or anything like that).
The phone has had a couple of SOD instances but they were very rare. After doing a sideload OTA update I've had it SOD twice in the last 2 days. I haven't re-rooted this phone (waiting for SuperSU to be less...hacky) or installed anything to mess with power management. I read that there may be a netflix SOD issue but it's not applicable as I don't have the app.
Anyone else get SOD with 4.3 or am I the only one?
Click to expand...
Click to collapse
You are not alone. My wife's phone is experiencing the same issues. I have chosen not to install the update for this very reason. Hopefully it will get fixed and there will be a new update in the near future. Sorry I don't yet have a solution.
pfederighi said:
You are not alone. My wife's phone is experiencing the same issues. I have chosen not to install the update for this very reason. Hopefully it will get fixed and there will be a new update in the near future. Sorry I don't yet have a solution.
Click to expand...
Click to collapse
Yeah, me too. I have had instances where it has just completely shut off and i've had to hard reboot. My other half also has a similar issue on the N4 and these were when I was on stock. I'm now running PA 3.90 and I haven't had any (as of yet)
Kitch16 said:
Yeah, me too. I have had instances where it has just completely shut off and i've had to hard reboot. My other half also has a similar issue on the N4 and these were when I was on stock. I'm now running PA 3.90 and I haven't had any (as of yet)
Click to expand...
Click to collapse
For what it's worth, doing a "factory reset" cured my wife's phone of the issue. Be sure to do a backup of important data like contacts and picture first.

Anyone else get a system update 10 Aug 2015?

Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
dmkozak said:
Received notification of a system update today, 10 August 2015. I'm a little leery of installing this. I'm at 5.1.1 and after installing 5.1.1, I have the dreaded unannounced deaths where the phone will turn itself at random. Sometimes it will reboot if you hold the power button down for about 15 seconds. Sometimes the charger needs to be plugged in before it will reboot. Sometimes it cycles through all apps before completing the reboot. Sometimes not. If the new update will fix this, I'm all for it. But, I don't want to get fooled again with these updates. So, anyone else get an update? What does it do? Any problems after the update? Thanks.
Click to expand...
Click to collapse
It's the first update of Google's announced security patch program. Expect frequent OS updates now to address security issues. This one patches the well publicized Stagefright MMS exploit.
That was my guess. I rarely text, or other, message, so I'm not too worried about Stagefright. My gut tells me to wait until others have installed. I have enough memory leak auto turn-off issues, that I'm afraid of making my phone worse than it is.
If Google would be so kind as to include a memory leak resolution in these updates, I'd jump all over it.
Well I had been postponing updating to Lollipop for months... (was still on 4.4.4 cuz I didn't quite like the new UI) and decided to update Sunday morning.
Big mistake.
The OTA 5.1.1 5.0.1 update made my phone become unstable, lag, and crash at random. Constantly get "X ins't responding", where X can be anything from Launcher to System UI to Chrome!
I currently can't even use my N4, and I'm trying to find a way to revert the upgrade, My 4.4.4 was rooted, and now it's not and I can't even enter Recovery mode.
Not sure if it's 100% related to your troubles, but I've been having similar random reboots lately and just general instability.
Edit: my bad, I just realized it was 5.0.1 I upgraded to.
update aug 10, 2015
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
robpoth said:
I saw the update and thought it would be a good idea but I now have a tablet stuck in reboot loop. Have tried everything (clearing data, factory reset, etc) and still not able to get past looping. Might want to wait before you update.
Click to expand...
Click to collapse
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Stevica Smederevac said:
You have to lock your bootloader for Ota to work.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
ariesgodofwar said:
I don't think your bootloader has to be locked, but since 5.+ you do have to be unrooted with no changes to your /system partition. I know I have sideloaded the OTA after flashing stock images. Just did not want the poster to lock their bootloader and brick themselves thinking they will be able to boot the OTA if they have modified /system at all.
Click to expand...
Click to collapse
Yeah,you're right. Everything stock +locked bootloader for ota to work. I assumed he knew thhat part about everything stock.
Sent from my Nexus 4 using XDA Free mobile app
I have unlocked bootloader and still I updated successfully thru OTA. No problems at all.
Sent from my Nexus 4 using Tapatalk

WiFi won't turn on after Nandroid

So this started on Saturday. Motorola has been nagging me all week to update to Nougat and I have declined due to lack of XPosed compatibility. On Saturday, I turned my phone on only to see the update in progress. Don't know how they did that unless I unconsciously touched confirm with my butt at some point.
I have a Nandroid backup so I thought the solution would be simple -- restore the backup and get on with my life. After restoring the backup, the WiFi no longer works. On the searching for networks screen it appears to be on. But on the "more setting" screen, it is off and will not turn on.
I had this problem once before and reflashing the modem fixed it. I've flashed it three times now and it is still not fixed. What else might be the problem? Thanks!
pjcamp said:
So this started on Saturday. Motorola has been nagging me all week to update to Nougat and I have declined due to lack of XPosed compatibility. On Saturday, I turned my phone on only to see the update in progress. Don't know how they did that unless I unconsciously touched confirm with my butt at some point.
I have a Nandroid backup so I thought the solution would be simple -- restore the backup and get on with my life. After restoring the backup, the WiFi no longer works. On the searching for networks screen it appears to be on. But on the "more setting" screen, it is off and will not turn on.
I had this problem once before and reflashing the modem fixed it. I've flashed it three times now and it is still not fixed. What else might be the problem? Thanks!
Click to expand...
Click to collapse
First off, unless you signed a non-disclosure as part of MFN, you didn't get Nougat update (probably), it was just a security update... odd that it would even take since you have root and Xposed (and maybe TWRP) it would be impossible to apply to the update. Aside from that, IF you did get an update applied, then restored a Nandroid that means your boot image (kernel) and radio versions are out of sync... You need to either flash the modem package that matches your kernel or restore the nandroid you did before the restore.
acejavelin said:
First off, unless you signed a non-disclosure as part of MFN, you didn't get Nougat update (probably), it was just a security update... odd that it would even take since you have root and Xposed (and maybe TWRP) it would be impossible to apply to the update. Aside from that, IF you did get an update applied, then restored a Nandroid that means your boot image (kernel) and radio versions are out of sync... You need to either flash the modem package that matches your kernel or restore the nandroid you did before the restore.
Click to expand...
Click to collapse
So you're right.
The immediate reason for doing the Nandroid restore is because the update got my phone stuck in a boot loop. After the restore, it started pestering me to update again so I took the opportunity to look into it a little more closely and it is a security update, not Android N.
But that then raises another question, or two actually. I was under the impression that the Nandroid backup stored the entire contents of memory. Are there some bits, like the wifi modem, that aren't included? Also, if I unroot long enough to take the update, will that restore the wifi modem? I assume an update would check the integrity of system files.
Thanks for the quick reply. I don't come to xda often but it is always informative.
pjcamp said:
So you're right.
The immediate reason for doing the Nandroid restore is because the update got my phone stuck in a boot loop. After the restore, it started pestering me to update again so I took the opportunity to look into it a little more closely and it is a security update, not Android N.
But that then raises another question, or two actually. I was under the impression that the Nandroid backup stored the entire contents of memory. Are there some bits, like the wifi modem, that aren't included? Also, if I unroot long enough to take the update, will that restore the wifi modem? I assume an update would check the integrity of system files.
Thanks for the quick reply. I don't come to xda often but it is always informative.
Click to expand...
Click to collapse
A Nandroid doesn't include lots of stuff... It is 5 or so of 25-30 partitions, typical system, boot, data, cache, and sometimes recovery and a couple others, it doesn't include radios, persistent data (like IMEI or serial numbers), internal storage, bootloader, and lots of other stuff.
You cannot just "unroot" and take an OTA, for modern Moto devices your boot image and system partitions must be pure and untouched (the script can even tell if system was ever mounted r/w even if nothing has been changed) and you must have stock recovery. You must return to stock to take an OTA, there are several threads discussing ways to do it here.

VS9951BA Update has been updating for an hour.....

I made the mistake of accepting the April 2018 update (VS9951BA) for my non-rooted Verizon VS995 and the update has been installing for over an hour now. Think I should let it continue or power off/remove battery?
Ideas?
In case anyone else runs into the same issue, I waited two hours just in case and finally pulled the battery. So far, the phone seems ok and the update seems to have installed successfully.
JCDinPGH said:
I made the mistake of accepting the April 2018 update (VS9951BA) for my non-rooted Verizon VS995 and the update has been installing for over an hour now. Think I should let it continue or power off/remove battery?
Ideas?
Click to expand...
Click to collapse
This had happened to me with the last update!
I removed the battery, waited for 5 minutes and put it back in. Everything worked fine.

Categories

Resources