Phone always awake after latest update (November 2016 E3 Power)!

Aman301582

Senior Member
Oct 17, 2012
266
62
0
Lucknow
This update was 22.x mb in size, updated security patch to october,2016. I updated 2 days ago and since then the battery is draining constantly because phone is always awake in battery stats (10% drain last night). Anyone else having the same problem? Any fix?
 

vimaljohnmr

Member
Apr 7, 2016
10
2
0
This update was 22.x mb in size, updated security patch to october,2016. I updated 2 days ago and since then the battery is draining constantly because phone is always awake in battery stats (10% drain last night). Anyone else having the same problem? Any fix?
I also updated.. but my phone is working fine.. check ur settings in display if something has changed
 
  • Like
Reactions: Aman301582

ach82002

New member
Sep 13, 2016
1
0
0
Battery drain after update

My moto e3 power too is having similar excessive battery drain after the 22mb update due to phone being always awake. :(
Please reply if anyone has a fix.
 

bubba1601

Senior Member
Aug 23, 2016
1,885
1,191
113
48
Don't go for small updates they were buggy and with lots of other issues stay on stock for better experience.
i'm still on 23.0XT1706_S131_160905_ROW and device perform very good (Getting 2.5 day battery backup).
Thank you for that clarification, this was driving me crazy because my E3 had many problems after this update.
Google now launcher force closing, all Google apps force closing, and rebooting every few minutes.
All my system information did not make sense and was wrong.

Motorola have now repaired my device it had to be wiped and the firmware reflashed, it now has System version S131 and was System version S124 before the update.
I have received notification yesterday about another 22.3 mb update, this will increase my system version from S131 to S135 as in my screenshot.
I have not installed this update.
I have read in Motorolas own forum and the E3 Facebook page many people complaining about problems with this update.

Thank you again for making us users aware this update is problematic and possibly faulty :)
 
Last edited: