Database Users

Cure for battery drain in CM7

Hey guys just like we all i suffered from the insane battery drain in CM7 with my lovely Vibrant. But yesterday night i found a cure that gives me now great battery life - almost like a 2.2 rom.
What i did?
I googled around and found this post:
1. Open up the dialpad, and type:
*#*#4636#*#*
(the numbers are for 'info'; don't press call, it should automatically go to a 'Testing' menu)
2. Go into 'Phone information'
3. Press Menu, and select 'Select radio band' (this will result in a force close, but that's what we want.. just keep going.)
4. Go back into 'Phone information' and scroll down to the bottom'. It will probably still say 'CDMA auto (PRL)', but the problem is this is probably a visual glitch. Or it might say 'Unknown'. Either way, switch it to something else, then switch it back to 'CDMA auto (PRL)'. Then you can turn off the radio and turn it back on with the button right underneath that.
5. At this point, the fix has been applied, but it would be a good idea to clear the battery stats to get a fresh start. So boot into recovery and do that, then reboot. The fix *should* stick after this reboot, but I think it didn't when I first did it. But assuming it does, then you're golden. It will be like this for all other reboots. If it does not, then just do it again. You can tell if it worked if when you go into battery usage, and go into cell standby, the TWS% is much lower. I charged mine completely overnight after applying this fix and have been off the charger now for over a half hour and TWS% is still at 0% (even though cell standby is at 46% (but that's not a problem at all..), and my battery is still at 100%
My Vibrant gives me now GSM/CDMA auto (PRL) as network type.
So let me know whether it works for you too or not.
For me its asesome, since i can enjoy CM7 all day long ;-)

Seems to be working fine for me, would I have to do this for every nightly.
Sent from my SGH-T959

great find +1 the battery life of cm7 drove me away to a JVQ rom but imma try this find and use it!

I don't know if the cure will work for me, too. I found out that my device doesn't enter deep sleep, so even when I'm thinking it's sleeping, it is not.
The process Android System keeps it awaken. At least it did in #54 and other recent builds. It completly depletes my battery like me drinking lemonade.
Does it sleep for you?

I like this. I can actually stream music while charging without slowly losing charge.

I'm going to try this and see what happens

Hope this gets run through Atinm.

kleineschatz said:
Hey guys just like we all i suffered from the insane battery drain in CM7 with my lovely Vibrant. But yesterday night i found a cure that gives me now great battery life - almost like a 2.2 rom.
What i did?
I googled around and found this post:
1. Open up the dialpad, and type:
*#*#4636#*#*
(the numbers are for 'info'; don't press call, it should automatically go to a 'Testing' menu)
2. Go into 'Phone information'
3. Press Menu, and select 'Select radio band' (this will result in a force close, but that's what we want.. just keep going.)
4. Go back into 'Phone information' and scroll down to the bottom'. It will probably still say 'CDMA auto (PRL)', but the problem is this is probably a visual glitch. Or it might say 'Unknown'. Either way, switch it to something else, then switch it back to 'CDMA auto (PRL)'. Then you can turn off the radio and turn it back on with the button right underneath that.
5. At this point, the fix has been applied, but it would be a good idea to clear the battery stats to get a fresh start. So boot into recovery and do that, then reboot. The fix *should* stick after this reboot, but I think it didn't when I first did it. But assuming it does, then you're golden. It will be like this for all other reboots. If it does not, then just do it again. You can tell if it worked if when you go into battery usage, and go into cell standby, the TWS% is much lower. I charged mine completely overnight after applying this fix and have been off the charger now for over a half hour and TWS% is still at 0% (even though cell standby is at 46% (but that's not a problem at all..), and my battery is still at 100%
My Vibrant gives me now GSM/CDMA auto (PRL) as network type.
So let me know whether it works for you too or not.
For me its asesome, since i can enjoy CM7 all day long ;-)
Click to expand...
Click to collapse
I hope this works, but when i first went to phone info and did radio band, it asked for country, i choose usa, it didnt FC thou, then when my setting was already GSM/CDMA (prl) . I will report back tommorow how it goes. thanks

I'm guessing the same would apply to MIUI?

It definitely seems to be doing something. My signal hasn't dropped below the full four bars yet, which is weird considering it's normally around 1 or 2. The phone also seems to go to sleep faster, but that could be placebo.
Sent from my SGH-T959 using XDA App

duboi97 said:
I'm guessing the same would apply to MIUI?
Click to expand...
Click to collapse
yes i tried this it didnt seem to work for me i dont think i got it to stick on im gona try it again

didnt get Force closed at the select radio band. Now what should I do?

on Miui I had to select Turn Radio Off first, then it forced closed and now it seems to stick when I change radio bands. Just turn on/off radio a few times and it should help.

ferhanmm said:
on Miui I had to select Turn Radio Off first, then it forced closed and now it seems to stick when I change radio bands. Just turn on/off radio a few times and it should help.
Click to expand...
Click to collapse
Thanks! Finally I got it to force closed and I did everything else. But I went into cell standby I saw my TWS% is 71 when my cell standby is only 21%. Is that a problem?

SuperJMN said:
I don't know if the cure will work for me, too. I found out that my device doesn't enter deep sleep, so even when I'm thinking it's sleeping, it is not.
The process Android System keeps it awaken. At least it did in #54 and other recent builds. It completly depletes my battery like me drinking lemonade.
Does it sleep for you?
Click to expand...
Click to collapse
I had this same problem. Apparently alot of others did too, but no one seems to have a solution that I have seen.
Sent from my SGH-T959 using XDA App

Effect of USB Charging on CPU Idle Utilization CM7
First, this test was performed on nightly #55 with KB5 baseband. I have performed this on KA7 as well and found the results to be similar.
I am very sensitive to my battery utilization. In turn, I am also a very frequent charger. Even if I'm at 80%, I feel I must plug my phone in as soon as possible. Because of this, there is hardly a time where my phone is on during a session in which it had never been on usb. This changed, however, this last weekend. I was playing around with KA7 vs KB5, and was away from my computer and charger. Later, when I reviewed my cpu utilization during idle time, I was shocked to see that the phone was just sipping the battery. Less than 1% utilization in System panel.
My initial reaction was "KA7 is amazing." However, the next morning, battery usage appeared to be the same as normal. On a hunch, I wondered if it was possible that it was the charging that is causing issue. As we all know, when the phone is plugged in, cpu utilization is fairly high (~30%), and some even report the battery getting hot (in some cases, even to reboot the phone). But -- is it possible that even after you unplug, there is some lingering "stuff" happening that will not go away, regardless of how long you idle?
What I did was simply charge my phone fully, unplug, reboot. I consistently find that my phone will go in and out of very low cpu utilzation state when I do this. If I go into airplane mode, I will even see full sleep state with no green bars in System panel (not that I would do this, as I like to USE my phone).
I am very curious if some of you may be able to try this experiment and report back. If this is confirmed, I wonder if there may be a way to determine what is getting stuck and robbing our cpu cycles after the phone is unplugged from charging.
Attached are four screenshots:
syspanel_pre_reboot_8hr.jpg: showcasing the long overnight charge, followed by very low activity, yet with >3% cpu utilization while idle. (by wall charge, though this has shown to be the case via computer usb charging as well)
syspanel_pre_reboot_2hr.jpg: a closer look at the idle time after the charge.
syspanel_post_reboot_8hr.jpg: A big picture view of the charging, the reboot, and the subsequent idle time. The first thing I did once the phone booted was download and install several app updates from market. I wanted to stress the phone before letting it fall back to idle.
syspanel_post_reboot_2hr.jpg: here you can see the lower idle cpu utilization on the phone. Initially there is activity as I updated apps from the market, and then it fell to hover around ~1%.
This behavior can be replicated and repeated on my phone every time. I was hoping someone with logcat experience may be able to help me define a filter so that we can see exactly what processes plugging the phone into usb starts, compared to which it terminates when unplugged. If we were to find this, I would suspect it could be added to the code itself.

THAT is what I'm experiencing TOO.

I have tried that fix. When entering the "select radio band" it doesn't force close. I just see "EURO Band" , "USA Band" etc...
also on the bottom it says "GSM only".
Is the fox already applied for me?
I'm using TRIGGER (CM7 based).

ginzberg said:
First, this test was performed on nightly #55 with KB5 baseband. I have performed this on KA7 as well and found the results to be similar.
I am very sensitive to my battery utilization. In turn, I am also a very frequent charger. Even if I'm at 80%, I feel I must plug my phone in as soon as possible. Because of this, there is hardly a time where my phone is on during a session in which it had never been on usb. This changed, however, this last weekend. I was playing around with KA7 vs KB5, and was away from my computer and charger. Later, when I reviewed my cpu utilization during idle time, I was shocked to see that the phone was just sipping the battery. Less than 1% utilization in System panel.
My initial reaction was "KA7 is amazing." However, the next morning, battery usage appeared to be the same as normal. On a hunch, I wondered if it was possible that it was the charging that is causing issue. As we all know, when the phone is plugged in, cpu utilization is fairly high (~30%), and some even report the battery getting hot (in some cases, even to reboot the phone). But -- is it possible that even after you unplug, there is some lingering "stuff" happening that will not go away, regardless of how long you idle?
What I did was simply charge my phone fully, unplug, reboot. I consistently find that my phone will go in and out of very low cpu utilzation state when I do this. If I go into airplane mode, I will even see full sleep state with no green bars in System panel (not that I would do this, as I like to USE my phone).
I am very curious if some of you may be able to try this experiment and report back. If this is confirmed, I wonder if there may be a way to determine what is getting stuck and robbing our cpu cycles after the phone is unplugged from charging.
Attached are four screenshots:
syspanel_pre_reboot_8hr.jpg: showcasing the long overnight charge, followed by very low activity, yet with >3% cpu utilization while idle. (by wall charge, though this has shown to be the case via computer usb charging as well)
syspanel_pre_reboot_2hr.jpg: a closer look at the idle time after the charge.
syspanel_post_reboot_8hr.jpg: A big picture view of the charging, the reboot, and the subsequent idle time. The first thing I did once the phone booted was download and install several app updates from market. I wanted to stress the phone before letting it fall back to idle.
syspanel_post_reboot_2hr.jpg: here you can see the lower idle cpu utilization on the phone. Initially there is activity as I updated apps from the market, and then it fell to hover around ~1%.
This behavior can be replicated and repeated on my phone every time. I was hoping someone with logcat experience may be able to help me define a filter so that we can see exactly what processes plugging the phone into usb starts, compared to which it terminates when unplugged. If we were to find this, I would suspect it could be added to the code itself.
Click to expand...
Click to collapse
i usually reboot after i charge when i wake up then i send a few texts and work the phone a bit my battery life isnt too bad
romitkin said:
I have tried that fix. When entering the "select radio band" it doesn't force close. I just see "EURO Band" , "USA Band" etc...
also on the bottom it says "GSM only".
Is the fox already applied for me?
I'm using TRIGGER (CM7 based).
Click to expand...
Click to collapse
no i have the same problem for some reason i cant get this fix to work either

Gave it a try, will see what happens. Battery life is now the only bummer on CM, if this solves it, I'll be a happy guy.

sleep of death

i'm on the newest ota in the US. rooted.
just about every night if i leave it in standby long enough I will have to long hold the power key in the morning to reboot it. and it loses something like 30 pct of its power as well sometimes.
the issue has been seen on the transformer as well. do we have a fix on here? or is the best solution to just turn the darn thing off whenever it's not in use

lbhocky19 said:
i'm on the newest ota in the US. rooted.
just about every night if i leave it in standby long enough I will have to long hold the power key in the morning to reboot it. and it loses something like 30 pct of its power as well sometimes.
the issue has been seen on the transformer as well. do we have a fix on here? or is the best solution to just turn the darn thing off whenever it's not in use
Click to expand...
Click to collapse
I had this issue happen once on the acer rom and once on the primee transformer rom. Hopefully they all patch it soon like toshiba did.

I have seen that a couple times on my Virtuous Xoom ROMed A500. It seems like it happens when the battery gets fairly low on standby, but not so low that it wouldn't be able to run.
It should not lose 30% of its power on standby overnight. I have mine overclocked, sync enabled, wifi, tons of apps listed in task manager, and I think I go down just a couple % overnight.
Once I noticed my unit discharged quickly and I believe it was because I had used ADB over the USB. It was no longer connected but something continued to chew up power after that.

willyampz said:
I have seen that a couple times on my Virtuous Xoom ROMed A500. It seems like it happens when the battery gets fairly low on standby, but not so low that it wouldn't be able to run.
It should not lose 30% of its power on standby overnight. I have mine overclocked, sync enabled, wifi, tons of apps listed in task manager, and I think I go down just a couple % overnight.
Once I noticed my unit discharged quickly and I believe it was because I had used ADB over the USB. It was no longer connected but something continued to chew up power after that.
Click to expand...
Click to collapse
Willy, same here. I've left mine on standby for three days & maybe lost one or two %. That's with wifi on, don't get it.

Ridiculous ICS Battery Life

On Friday 1 June 2012, which is Friday last week at the time of writing, I gladly updated my phone through Kies after receiving word of the UK update being available from these very forums. Over the past week, I have noticed that my battery life is considerably worse since my upgrade to the new Android version and, when hearing of people hear who manage up to 36 hours of battery life through this phone, I really want to find out what they are doing exactly. At present, I have set the brightness at 1% (the minimum) and only up it to 40% when out in bright light conditions. At home, I also use the Screen Filter app which dims the screen further (I have this set to 50% of my already 1% brightness setting) and claims to improve battery on AMOLED devices. I also have Juice Defend Ultimate running on "Aggressive" mode along with the built-in power saving mode running as well. Yet, looking on CPU Spy, my phone still does not enter deep sleep which is needed to see a real improvement in battery life as far as I am aware. I have tried restarting the phone and also plugging it back into charge before unplugging it with the screen turned on as many have recommended. Any ideas what else I can do?

Uninstall juicedefender. Its not uncommon that it drains a lot more juice than it saves.

There is must be any Application that is hogging your battery.
Install better battery state... Find that application and uninstall that.
I am getting better battery life in ICS as compared to GB...

chintamanijaipuri said:
There is must be any Application that is hogging your battery.
Install better battery state... Find that application and uninstall that.
I am getting better battery life in ICS as compared to GB...
Click to expand...
Click to collapse
I have that app installed, but frankly have no idea how to use it very well. From what I can tell, it is Kik Messenger which is creating a partial wake lock (but I need that to send pictures to my friends), Juice Defender which is supposedly saving battery life and biggest partial wake lock is RILJ or something. But, that is caused from a weak signal and I get that regardless of network at my house. Besides moving, I cannot alter that. As for Juice Defender, I've heard nothing but positive reviews from it. My main aim is to get deep sleep working, but how?

Install Better Battery Stat and check what app is actually causing the problem :
http://forum.xda-developers.com/showthread.php?t=1179809
P_

pakalrtb said:
Install Better Battery Stat and check what app is actually causing the problem :
http://forum.xda-developers.com/showthread.php?t=1179809
P_
Click to expand...
Click to collapse
Read my previous post.

Brad387 said:
On Friday 1 June 2012, which is Friday last week at the time of writing, I gladly updated my phone through Kies after receiving word of the UK update being available from these very forums. Over the past week, I have noticed that my battery life is considerably worse since my upgrade to the new Android version and, when hearing of people hear who manage up to 36 hours of battery life through this phone, I really want to find out what they are doing exactly. At present, I have set the brightness at 1% (the minimum) and only up it to 40% when out in bright light conditions. At home, I also use the Screen Filter app which dims the screen further (I have this set to 50% of my already 1% brightness setting) and claims to improve battery on AMOLED devices. I also have Juice Defend Ultimate running on "Aggressive" mode along with the built-in power saving mode running as well. Yet, looking on CPU Spy, my phone still does not enter deep sleep which is needed to see a real improvement in battery life as far as I am aware. I have tried restarting the phone and also plugging it back into charge before unplugging it with the screen turned on as many have recommended. Any ideas what else I can do?
Click to expand...
Click to collapse
first ,samsung ICS is poorly made ,second you have a high chance of bricking if you wipe your phone with their official kernels so don't do it.
third ,like others said ,juice defender (and any app of this sort) doesn't work anymore (android 2.2 and up) so just uninstall it.
fourth ,not entering deep sleep is mostly due to a rouge app ,and since wiping is not an option for you you need to hunt it down manually ,use better battery status (learn how to use it!!!) and uninstall any apps you don't need.
fifth ,get some knowledge then get rid of crappy touchwiz ROM and install CM9 ,you'll see a huge improvement in terms of performance and battery life.

MR.change said:
first ,samsung ICS is poorly made ,second you have a high chance of bricking if you wipe your phone with their official kernels so don't do it.
third ,like others said ,juice defender (and any app of this sort) doesn't work anymore (android 2.2 and up) so just uninstall it.
fourth ,not entering deep sleep is mostly due to a rouge app ,and since wiping is not an option for you you need to hunt it down manually ,use better battery status (learn how to use it!!!) and uninstall any apps you don't need.
fifth ,get some knowledge then get rid of crappy touchwiz ROM and install CM9 ,you'll see a huge improvement in terms of performance and battery life.
Click to expand...
Click to collapse
Okay, well this is my first proper Android device (minus an old second-hand HTC Desire which had awful storage and I used for around one month). Secondly, I do know that other ROMs offer better performance and battery life but flashing them onto my phone is something I'm not very comfortable with and surely it would also void my warranty. I've only had the phone for four weeks and don't want it wrecked already.

Brad387 said:
Okay, well this is my first proper Android device (minus an old second-hand HTC Desire which had awful storage and I used for around one month). Secondly, I do know that other ROMs offer better performance and battery life but flashing them onto my phone is something I'm not very comfortable with and surely it would also void my warranty. I've only had the phone for four weeks and don't want it wrecked already.
Click to expand...
Click to collapse
I'm fairly new to android as well ,had an S2 (which was so good that I only rooted it ,no custom ROMs) for 5 months before the note and that's it.
but I rooted my note the first day I got it ,and installed a custom ROM less than a week later (was a total noob at the time but I read and learnt quickly) .
then CM9 arrived and I flashed that immediately and haven't regretted it so far.
but I had no warranty to begin with so.....
note that if there is something that can wreck your shinny new note ,then it's amsung official ICS update (read the announcement sticky on ICS and bricking) .

but how experts can explain the fact i face:
With every official and custom ROM i install, even CM9, my note keeps eating battery when in use plugged to the charger... it's unbelievable... I can't understand how it happens.
by the way: i always full wipe before installing any custom/official rom.

MR.change said:
I'm fairly new to android as well ,had an S2 (which was so good that I only rooted it ,no custom ROMs) for 5 months before the note and that's it.
but I rooted my note the first day I got it ,and installed a custom ROM less than a week later (was a total noob at the time but I read and learnt quickly) .
then CM9 arrived and I flashed that immediately and haven't regretted it so far.
but I had no warranty to begin with so.....
note that if there is something that can wreck your shinny new note ,then it's amsung official ICS update (read the announcement sticky on ICS and bricking) .
Click to expand...
Click to collapse
Well, is there nothing that I can do to trigger deep sleep or improve battery life on the stock ROM first of all? Secondly, how difficult is rooting and would that void any warranty?

Raphael Alo said:
but how experts can explain the fact i face:
With every official and custom ROM i install, even CM9, my note keeps eating battery when in use plugged to the charger... it's unbelievable... I can't understand how it happens.
by the way: i always full wipe before installing any custom/official rom.
Click to expand...
Click to collapse
it can't happen ,I'd say you either have a faulty battery\charger or there is someting wrong with the phone itself
the note charges while in use and connected to a charger.
Brad387 said:
Well, is there nothing that I can do to trigger deep sleep or improve battery life on the stock ROM first of all? Secondly, how difficult is rooting and would that void any warranty?
Click to expand...
Click to collapse
yes you can ,uninstall the violating apps ,learn to use better battery status ,you'll find that there is an app or two responsible for the wake locks ,thus preventing the phone from entering deep sleep.
or simply install every app and game that seems suspisious or poorly made ,and just keep the essential ones.
as for rooting ,it couldn't be simpler if done carefully and to the letter :
1.flash back to GB using PC ODIN
2.root it
3.backup your EFS folder (important , very important) search for it on the forums.
4. install custom ROMs (stay away from unsafe kernels please ,read the sticky thread about ICS kernels)
3. enjoy
use this guide
http://forum.xda-developers.com/showthread.php?t=1329360
yes there is an easy way to root while on stock ICS as per to this guide ,but I prefer you stay away from official ICS for the sole reason that it's dangerous.
remeber the key is to read and read and read ,in a month you could become a pro
on the other hand if you go the lazy way ,you could just end up with a bricked phone
also once you root ,your warranty is void ,though if you're careful you can return it to stock condition and they won't tell the difference
be careful

MR.change said:
fifth ,get some knowledge then get rid of crappy touchwiz ROM and install CM9 ,you'll see a huge improvement in terms of performance and battery life.
Click to expand...
Click to collapse
That's just wrong. CM9 battery drain with screen on is far, far worse than Stock ROM.

IndDoc said:
That's just wrong. CM9 battery drain with screen on is far, far worse than Stock ROM.
Click to expand...
Click to collapse
no my friend ,I'm afraid you're wrong ,with the 4\6 nightly my phone was running with low usage for 48+ hrs .
the battery life is phenomenal for me .

@Brad387
I have had mine for about 2 weeks. When I turned it on and did the initial setup it had a new software update which was ICS. Since then I have been having issues with deep sleep as well. I turned stuff on and off and it has been totally random what was preventing it from going to deep sleep.
I have done this trick that has been on this forum.
Put you phone to airplane mode.
Power it off completely
Remove battery for 20 seconds or more
put battery back in and power this thing back on
then turn off airplane mode.
This seems to have helped me get into deep sleep. BUT there have been instances of rogue crap going on. Like I was using Google maps with GPS on. When I got home and was done with my traffic mapping I turned off the GPS switch and turned off my phone. I checked an hour later and the battery had died 10% since I got home which was more than when I was driving. I checked Better Battery Stats and it showed that GPS was running that whole time. So I turned on GPS again in the toggle waited a couple seconds then turned it off again and bang it went into deep sleep. It sucks that I have to check crap on it all the time and have become a bit paranoid because the GPS glitch had my phone running pretty hot. Since then everything has been running well and deep sleeping.
There are other things I did do too and the below stuff is up to you if you wish to proceed. I rooted my phone which was very easy...at least for me. http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3 this is what I used with no problem.
From there you can freeze a bunch of stuff you may not use like Social Hub, Accuweather etc etc.You will need Titanium for that though and root access.
I logged out of Latitude too which was on by default for some reason.
If I remember anything else I did I will hit you back here.
Bottom line was finally yesterday I was able to get thru the entire day without needing to plug in so there is light at the end of the tunnel...I hope.
Not sure if this has been mentioned but CPU Spy lets you see if you are getting into deep sleep mode and how much time you are in it along with the other CPU mhz that its running.
Hopefully this can help out a bit because I have been in the same boat and it has been driving me mad. Sorry for all the random thoughts too...I just typed them as I remembered things.

jbeef86 said:
@Brad387
I have had mine for about 2 weeks. When I turned it on and did the initial setup it had a new software update which was ICS. Since then I have been having issues with deep sleep as well. I turned stuff on and off and it has been totally random what was preventing it from going to deep sleep.
I have done this trick that has been on this forum.
Put you phone to airplane mode.
Power it off completely
Remove battery for 20 seconds or more
put battery back in and power this thing back on
then turn off airplane mode.
This seems to have helped me get into deep sleep. BUT there have been instances of rogue crap going on. Like I was using Google maps with GPS on. When I got home and was done with my traffic mapping I turned off the GPS switch and turned off my phone. I checked an hour later and the battery had died 10% since I got home which was more than when I was driving. I checked Better Battery Stats and it showed that GPS was running that whole time. So I turned on GPS again in the toggle waited a couple seconds then turned it off again and bang it went into deep sleep. It sucks that I have to check crap on it all the time and have become a bit paranoid because the GPS glitch had my phone running pretty hot. Since then everything has been running well and deep sleeping.
There are other things I did do too and the below stuff is up to you if you wish to proceed. I rooted my phone which was very easy...at least for me. http://forum.xda-developers.com/showpost.php?p=20963730&postcount=3 this is what I used with no problem.
From there you can freeze a bunch of stuff you may not use like Social Hub, Accuweather etc etc.You will need Titanium for that though and root access.
I logged out of Latitude too which was on by default for some reason.
If I remember anything else I did I will hit you back here.
Bottom line was finally yesterday I was able to get thru the entire day without needing to plug in so there is light at the end of the tunnel...I hope.
Not sure if this has been mentioned but CPU Spy lets you see if you are getting into deep sleep mode and how much time you are in it along with the other CPU mhz that its running.
Hopefully this can help out a bit because I have been in the same boat and it has been driving me mad. Sorry for all the random thoughts too...I just typed them as I remembered things.
Click to expand...
Click to collapse
My phone does not seem to enter Deep Sleep, but runs constantly at 200 MHz instead. At present, after turning on the built-in power saving mode (not noticing any performance differs so can't even tell what it does), running Juice Defender Ultimate on aggressive and screen filter I burn around 2% per hour if I just leave my phone locked. Is that healthy?

Brad387 said:
But, that is caused from a weak signal and I get that regardless of network at my house. Besides moving, I cannot alter that.
Click to expand...
Click to collapse
Actually, there is something you can do about that!
Both Vodafone and Three can supply you with a Femtocell which can greatly improved your signal at home, and uses your home broadband as backhaul.
I know, because I have them!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2

Battery life of my Note was horrible after upgrade to ICS, and actually already quite bad the last month on GB2.3.6 (all unrooted).
It could get quite warm and often when opening my case the screen was already on.
So I did wipe my phone, reinstalled all apps and battery life has improved immensely.
I see several warnings here about chance to brick your phone when wiping on stock ROM, but not solving the battery drain is of course no option and we don't have a guarantee from Samsung for nothing...
Sent from my GT-N7000 using XDA

foxmeister said:
Actually, there is something you can do about that!
Both Vodafone and Three can supply you with a Femtocell which can greatly improved your signal at home, and uses your home broadband as backhaul.
I know, because I have them!
Regards,
Dave
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Well, thanks for offering that advice but how expensive are these things? Also, I'm the only person on 3 in my house so kind of a waste really...

Brad387 said:
My phone does not seem to enter Deep Sleep, but runs constantly at 200 MHz instead. At present, after turning on the built-in power saving mode (not noticing any performance differs so can't even tell what it does), running Juice Defender Ultimate on aggressive and screen filter I burn around 2% per hour if I just leave my phone locked. Is that healthy?
Click to expand...
Click to collapse
your phone should not be running at 200MHz when you hit the sleep/power button. So if its in your pocket and the screen is off then 200MHz is not healthy. Something is running in the background. Have you tried the airplane mode battery trick yet? What I did when that was happening to me was...turn on the airplane mode, power off the phone, pull out batt for 20 secs, put batt in and power on phone, turn off airplane mode, then go to CPU Stats and clear it, then put phone back to sleep and let it sit for a half hour or less if you cant handle that wait like I couldnt. Go back to CPU Stats and and click refresh and see if it helped and if your phone went into deep sleep.

N7 Turns Off/Won't Turn Back On/Battery Status Issues - The Fixes **UPDATE**...

**Update** See new note added 2/16/13 at bottom!
Trying to provide a single informational resource on three, typically related issues:
1. My N7 turns off randomly
2. My N7 dies early at ___% battery (you fill in the value)
3. My N7 turned itself off, and won't turn back on
There’s a ton of threads all over the net regarding these issues, some providing unintentionally misleading info, some progress towards actually defining the issue and posing possible solutions. Reports of these issues started back when the N7 was first released and continue to this day. These issues have been reported to Google, but who knows whether or not the Google God will attend to them anytime soon.
What follows is what I’ve learned about these issues, how they affected most users, and how they were resolved for most users. This is not intended to capture every possible exception.
Issue #1:
For some users, their N7 just turns off randomly, regardless of battery level. For them, a loose battery connector is typically the cause. Popping off the back cover, re-seating the connector and possibly putting a tiny piece of tape to keep it secured over time is the fix.
Issue #2:
Many users notice that their N7’s turn off by itself, typically when the battery is at the lower-end of the % scale – anywhere from 40% down to 20% or so. Most users think that their N7 is running out of power "early" – but it seems that the 40% - 20% indication is erroneous - the battery is really at 0%, and is turning off as it should. This appears to be the caused by a software glitch that Google has to address. Doing a Factory Reset and a battery pull appears to remedy this issue for just about everyone. Please note that a corollary to this issue is the observation that once charged, the N7 remains at 100% far longer than it should.
Issue #3:
Taken out of context, having an N7 that won’t start seems like a terrible thing. But in most cases, it’s caused by Issues #1 and #2.
- If Issue #1 caused it: reconnect the loose cable, recharge your battery if needed, and you are good-to-go.
- If #2 caused it, your N7 battery is dead. Plug your N7 into the original power supply, patiently wait a few minutes then patiently hold down the power button up to 30 seconds (actually look at your watch – it’s gotta be “up to 30 seconds”!), for just about everyone reporting, it’ll start up just fine.
- If both of these methods don't work, try powering-down via the bootloader: plug your N7 into the charger, press Volume-Down and Power at the same time, in the bootloader choose "Power-Off Device", unplug your N7 and plug it back in. Do you see the battery meter? If so, you're done.
- While the original power supply should be the best to use in these troubleshooting procedures, if you are not getting a resolution of this issue, some N7 owners have had success with power supplied by USB via PC. Give it a try.
Since these problems are widespread, there are a number of “fixes” offered other than those above, that are somewhat anecdotal – they only “work” in one/couple instances and therefore there’s no real evidence that they are relevant. This group includes:
- Using battery calibration apps to fix the problem
- Dumping battery stats
- Uninstalling a specific " troublesome" app
Some users send their N7’s back to Google, and their new N7’s are deemed "fine". A number of knowledgeable users have speculated that most of these N7’s sent back really only suffered from the fixable issues listed above. To support this notion, some have reported that the replacements have the same “defects” as their first units, and they continue to send them back.
My experience:
My N7 worked perfectly for the first two weeks of ownership. Then it started turning off at 30% and 23%. I also noted that once I charged-up, my N7 would stay at 100% forever, leading me to believe that the battery readings were hosed-up. After these problems started, it would not go below the 30%-20% thresholds. The first time I tried to power it up - it wouldn't - and I thought is had totally borked. I tried eventually figured out that I needed to add power, wait, then hold down the power button. Worked every time.
For me, I wanted to know if I had a loose battery connector - a common problem, even though my N7 was not shutting down randomly, it was always at low battery levels. I figured that I'd just do the two things that research showed would work for sure, and would cover two different issues. I popped the back off, found that the connector as well-seated, but I pulled it off anyway to do the "battery pull". I reconnected and added a bit of electrical tape to keep it secured. I then did a Factory Reset using the option under "Settings/Backup and Reset". My N7 has been absolutely PERFECT since - just as most users report.
There is still the apparent issue of Google fixing the issue that causes the battery indication to be inaccurate.
I hope that this post serves to help others that experience these issues.
_______________________________________________
Update 2/16/13
I noticed in the past 2 days that my N7 started staying on 100% for prolonged periods of time. I figured that it once again lost it's ability to provide accurate battery status. Therefore, I projected that when it gets down to 30% or so, it'll turn off. It did.
I did the fixes I outlined in the OP and this time they didn't work. After pulling the battery and doing a factory reset, it still indicated 30% battery left - and I KNOW it's really at/near 0%.
I've been monitoring this issue since I made this thread and I've noticed that a growing number of N7 users were fixing this issue by simply turning off their N7's for a period of time. So I gave that a go.
I plugged my N7 in for about 20 minutes to give it the juice it would need to restart after the period of time being turned off. Then, I unplugged it and turned it off. Waited an hour, and when I restarted it, the battery had been recalibrated to 0%. Awesome!
So where does this leave us? Here are my thoughts:
- Since there are a number of different causes that result in the symptoms listed in the OP, those fixes are still relevant for those specific causes.
- We should add this latest fix to the collection, as it worked perfectly for me today.
- It's possible that our N7's should be periodically turned off - possibly overnight as it charges. I know that I plan to occasionally do this. If you don't have a disconnected/loose battery cable, or some issue with software that is remedied by a Factory Reset, maybe your N7 just needs to be turned off to recalibrate every now and then. Update: As of 5/3013, my N7 has been flawless. It's entirely possible that this is because I shut-down my N7 every week or two to recalibrate.
As always, I hope this keeps N7 users from freaking out, or sending their N7's back - unless it's really necessary.
And as I said in the OP, Google really needs to address this, as there's plenty of evidence that many N7 owners experience these issues. I'll update my report to Google.

Stock 4.1 upgraded to 4.2.1
No Root/unlock
Software or Hardware? Who know's..
I received my N7 on dec 20th 2012, still haven;t gotten to use it more than a day or 2... had battery issues off the hope, shut of at 21% ish... tried turning it on... just got screen flickering. Tried chargin it for hours, still nothing... after submitting an RMA after a couple days of charging with device on or off or with screen flickering ,,,nothing worked. Hung up with support... tried with USB connected to PC... got the device to boot.
I also in between random variations of cables and what not I did the D/C on battery ... didn't do much for me.
Charged device to 100% used down to 60% charged to 75%
Used again for 5 minutes
Device turned off.
Wouldn't boot
Another day of messing around... got it to turn on
Booted, battery was at 0% said it was shutting down
Tried a few more times (without charging) Just shut down cause battery was at 0%
Tried again, Booted said battery was at 85%
Light Use
Plugged in to charge, got home from work next day, device won't turn on
Been 3 days
New device form RMA gets in today.
If it comes with 4.1 I am going to run it for a few days because when i received my first device, it seemed to be working fine for the first 2 hours... got my device setup then decided to do the update to 4.2.1
Immediately my device shut down and gave me a screen flickering issue... did hard reset (held power for like 10 sec) device turned on... then experienced all the crap above.
So if i update after a couple days... and then run into issues... it would tell myself that there could be an issue with the update... but who knows as all the reading I have been doing, every scenario is different.
Google told me to submit a second RMA if it continues.... I'd rather not have the device if I just have to keep returning it.

Blesseld said:
Stock 4.1 upgraded to 4.2.1
No Root/unlock
Software or Hardware? Who know's..
I received my N7 on dec 20th 2012, still haven;t gotten to use it more than a day or 2... had battery issues off the hope, shut of at 21% ish... tried turning it on... just got screen flickering. Tried chargin it for hours, still nothing... after submitting an RMA after a couple days of charging with device on or off or with screen flickering ,,,nothing worked. Hung up with support... tried with USB connected to PC... got the device to boot.
I also in between random variations of cables and what not I did the D/C on battery ... didn't do much for me.
Charged device to 100% used down to 60% charged to 75%
Used again for 5 minutes
Device turned off.
Wouldn't boot
Another day of messing around... got it to turn on
Booted, battery was at 0% said it was shutting down
Tried a few more times (without charging) Just shut down cause battery was at 0%
Tried again, Booted said battery was at 85%
Light Use
Plugged in to charge, got home from work next day, device won't turn on
Been 3 days
New device form RMA gets in today.
If it comes with 4.1 I am going to run it for a few days because when i received my first device, it seemed to be working fine for the first 2 hours... got my device setup then decided to do the update to 4.2.1
Immediately my device shut down and gave me a screen flickering issue... did hard reset (held power for like 10 sec) device turned on... then experienced all the crap above.
So if i update after a couple days... and then run into issues... it would tell myself that there could be an issue with the update... but who knows as all the reading I have been doing, every scenario is different.
Google told me to submit a second RMA if it continues.... I'd rather not have the device if I just have to keep returning it.
Click to expand...
Click to collapse
Sorry to hear of this.
Not sure that I read that you did the Factory Reset, as suggested in the OP.
Give that a try.
Pulling the battery and/or doing a full Factory Reset is the fix for the vast majority of N7 users.
You may be an exception to that. Hope not.

Ya I have done the factory reset and battery pull, after the reset it just reset to 4.2.1 it came with 4.1.
Then it shut down on me again, I have my new unit it now. Running solid so far, good battery charge... not taking forever. hasn't shut down yet.
I'm going to run it on 4.1 for a day or 2 then update. Hopefully I don't run into issue after the update... it was probably coincidence but i ran into problems after updating on my first N7 to 4.2.1

Well, then unlike many other N7 owners, since you did both the battery pull and Factory Reset, you can rest assured that you didn't waste your time sending your N7 back - it needed replacement.
Good luck with it!

Just reporting back with a status. The fixes I described above seem to be working perfectly for days now. Check my OP and give those recommendations a shot if you're having any issues. Hope this helps to simplify a potentially confusing landscape and to resolve these issues for other N7 owners.

Two of the ”fixes” that folks anecdotally reported... using a battery calibration app and clearing battery stats are 100% guaranteed not to work. Those who actually ascribe any effect to them are merely using faulty reasoning. Quite simply, the calibration apps are just another method of wiping battery stats. Nothing at all in batterystats.bin has any bearing on battery life or reported charge indication.
This isn't directed at anyone in particular. Rather, I'm just expounding on something from the OP.
Definitely a very useful thread, given what seems to be a not too uncommon issue. As an aside, I've also experienced the problem after flashing a new kernel. Reflashing the previous kernel corrected the issue.
Sent from my Nexus 7 using Tapatalk HD

najaboy said:
Two of the ”fixes” that folks anecdotally reported... using a battery calibration app and clearing battery stats are 100% guaranteed not to work. Those who actually ascribe any effect to them are merely using faulty reasoning. Quite simply, the calibration apps are just another method of wiping battery stats. Nothing at all in batterystats.bin has any bearing on battery life or reported charge indication.
This isn't directed at anyone in particular. Rather, I'm just expounding on something from the OP.
Definitely a very useful thread, given what seems to be a not too uncommon issue. As an aside, I've also experienced the problem after flashing a new kernel. Reflashing the previous kernel corrected the issue.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
najaboy:
Excellent background on those two "fixes", and I agree 100%.
In creating this thread, I didn't want to really slam-dunk any of the "fixes" that other people have offered in other threads. But the research shows that you are exactly right: calibration apps and wiping battery stats will do absolutely nothing - guaranteed.
It's amazing how many misleading threads I had to wade-through to get to the fixes I recommend. No wonder so many people have returned their N7's to get one that "doesn't have the issues".

Crisis averted
billykxda said:
Trying to provide a single informational resource on three, typically related issues:
1. My N7 turns off randomly
2. My N7 dies early at ___% battery (you fill in the value)
3. My N7 turned itself off, and won't turn back on
There’s a ton of threads all over the net regarding these issues, some providing unintentionally misleading info, some progress towards actually defining the issue and posing possible solutions. Reports of these issues started back when the N7 was first released and continue to this day. These issues have been reported to Google, but who knows whether or not the Google God will attend to them anytime soon.
What follows is what I’ve learned about these issues, how they affected most users, and how they were resolved for most users. This is not intended to capture every possible exception.
Issue #1:
For some users, their N7 just turns off randomly, regardless of battery level. For them, a loose battery connector is typically the cause. Popping off the back cover, re-seating the connector and possibly putting a tiny piece of tape to keep it secured over time is the fix.
Issue #2:
Many users notice that their N7’s turn off by itself, typically when the battery is at the lower-end of the % scale – anywhere from 40% down to 20% or so. Most users think that their N7 is running out of power "early" – but it seems that the 40% - 20% indication is erroneous - the battery is really at 0%, and is turning off as it should. This appears to be the caused by a software glitch that Google has to address. Doing a Factory Reset and a battery pull appears to remedy this issue for just about everyone. Please note that a corollary to this issue is the observation that once charged, the N7 remains at 100% far longer than it should.
Issue #3:
Taken out of context, having an N7 that won’t start seems like a terrible thing. But in most cases, it’s caused by Issues #1 and #2.
- If Issue #1 caused it: reconnect the loose cable, recharge your battery if needed, and you are good-to-go.
- If #2 caused it, your N7 battery is dead. Plug your N7 into the original power supply, patiently wait a few minutes then patiently hold down the power button up to 30 seconds (actually look at your watch – it’s gotta be “up to 30 seconds”!), for just about everyone reporting, it’ll start up just fine.
Since these problems are widespread, there are a number of “fixes” offered other than those above, that are somewhat anecdotal – they only “work” in one/couple instances and therefore there’s no real evidence that they are relevant. This group includes:
- Using battery calibration apps to fix the problem
- Dumping battery stats
- Uninstalling a specific " troublesome" app
Some users send their N7’s back to Google, and their new N7’s are deemed "fine". A number of knowledgeable users have speculated that most of these N7’s sent back really only suffered from the fixable issues listed above. To support this notion, some have reported that the replacements have the same “defects” as their first units, and they continue to send them back.
My experience:
My N7 worked perfectly for the first two weeks of ownership. Then it started turning off at 30% and 23%. I also noted that once I charged-up, my N7 would stay at 100% forever, leading me to believe that the battery readings were hosed-up. After these problems started, it would not go below the 30%-20% thresholds. The first time I tried to power it up - it wouldn't - and I thought is had totally borked. I tried eventually figured out that I needed to add power, wait, then hold down the power button. Worked every time.
For me, I wanted to know if I had a loose battery connector - a common problem, even though my N7 was not shutting down randomly, it was always at low battery levels. I figured that I'd just do the two things that research showed would work for sure, and would cover two different issues. I popped the back off, found that the connector as well-seated, but I pulled it off anyway to do the "battery pull". I reconnected and added a bit of electrical tape to keep it secured. I then did a Factory Reset using the option under "Settings/Backup and Reset". My N7 has been absolutely PERFECT since - just as most users report.
There is still the apparent issue of Google fixing the issue that causes the battery indication to be inaccurate.
I hope that this post serves to help others that experience these issues.
Click to expand...
Click to collapse
Brand new Nexus 7 purchased today, came with 4.1 and I applied 4.2.1. Difficulties getting it powered on in the first place and lots of reboots and apparent crashes. Factory reset once and found some of those other threads you mentioned, disabled location services and that seemed to help a bit but still getting reboots. More digging and I found your post. Took your advice and pulled off the back of the Nexus 7, pulled the battery up and the connector basically fell out, it obviously wasn't seeded properly. Popped it back in properly and it's working much better now, although I'm going to give it 24 hours to make sure my issues are resolved. I just created an account in here to thank you. Think I'll stick around and see what else I can learn.

got my nexus 7 at September 2012,
got no problem with the abttery at the first charge,
but few weeks later, the battery started to die at 20% , then died at 30%, i didnt notice until i saw the battery history, it just jumped from 30% to 0%,
keep in mind that i'm not using the asus standard charger (dont know if this affect us)
tried charging it with the original charger, look like the problem is fixed, the battery died at 5%.
not sure if this is a coincidence or not
sorry for the bad English

Hazmatilda said:
Brand new Nexus 7 purchased today, came with 4.1 and I applied 4.2.1. Difficulties getting it powered on in the first place and lots of reboots and apparent crashes. Factory reset once and found some of those other threads you mentioned, disabled location services and that seemed to help a bit but still getting reboots. More digging and I found your post. Took your advice and pulled off the back of the Nexus 7, pulled the battery up and the connector basically fell out, it obviously wasn't seeded properly. Popped it back in properly and it's working much better now, although I'm going to give it 24 hours to make sure my issues are resolved. I just created an account in here to thank you. Think I'll stick around and see what else I can learn.
Click to expand...
Click to collapse
Congrats!
Go enjoy your new N7!

webslasher said:
got my nexus 7 at September 2012,
got no problem with the abttery at the first charge,
but few weeks later, the battery started to die at 20% , then died at 30%, i didnt notice until i saw the battery history, it just jumped from 30% to 0%,
keep in mind that i'm not using the asus standard charger (dont know if this affect us)
tried charging it with the original charger, look like the problem is fixed, the battery died at 5%.
not sure if this is a coincidence or not
sorry for the bad English
Click to expand...
Click to collapse
Have you tried the recommendations in the op?

billykxda said:
Have you tried the recommendations in the op?
Click to expand...
Click to collapse
I guess you solved your issue?

Re: N7 Turns Off/Won't Turn Back On - A Summary...
I did have issue #2. I already had fully charged over night. Battery indicator showed 100% for a while, so I figured the problem wasn't solved. What I did was shut down my N7, then hook it up to the charger, boot my N7, unhooked it from charger, played 1 level in Amazing Alex and checked battery indicator again: 99%. I hope this means I solved the problem for now
Verstuurd van mijn Nexus 7 met Tapatalk

Fotogravin said:
I did have issue #2. I already had fully charged over night. Battery indicator showed 100% for a while, so I figured the problem wasn't solved. What I did was shut down my N7, then hook it up to the charger, boot my N7, unhooked it from charger, played 1 level in Amazing Alex and checked battery indicator again: 99%. I hope this means I solved the problem for now
Verstuurd van mijn Nexus 7 met Tapatalk
Click to expand...
Click to collapse
Interesting. There have been reports of people addressing this problem by just turning off their N7 for a while, booting back up and all is well. Others like you added the plug/unplug charger to the mix and that seemed to work for them.
This issue has been reported to Google as well - there is a thread on Googles defect site that also lists all sorts of "fixes" that people have attributed to this issue.
Still, the only highly-repeatable fixes I've seen in various threads/forums are in the OP. But, who knows? If you can get your N7 past these issues, it's a good thing!

Re: N7 Turns Off/Won't Turn Back On - A Summary...
Hi, you can add me to the list. My N7 often turn off itself when battery level is under 50%. I have tried everything (factory reset, flash stock image...) but problem still persists.
So i have a N7 with half battery capacity most of the time. I hope next update will fix it otherwise i'll send it to Asus.
Edit: mine just switch off at nearly 25%, i'll try to downgrade to 4.1.2 and see if it helps...
Sent from my Nexus 7 using xda premium

roswell782 said:
Hi, you can add me to the list. My N7 often turn off itself when battery level is under 50%. I have tried everything (factory reset, flash stock image...) but problem still persists.
So i have a N7 with half battery capacity most of the time. I hope next update will fix it otherwise i'll send it to Asus.
Edit: mine just switch off at nearly 25%, i'll try to downgrade to 4.1.2 and see if it helps...
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi!
Did you try all of the suggestions in the OP?
-bk

Re: N7 Turns Off/Won't Turn Back On - A Summary...
Hi, i didn't open the battery cover because i don't want to lose my warranty, i prefer to let Asus do it for me.
My history with Asus is finished, bought 3 products from them, 3 have problems...
Btw: of course downgrade to 4.1.2 did nothing
Thanks for your answer and have a good weekend.
Cheers, Ros.
Edit: RMA asked, hope Asus will fix it.
Sent from my GT-I9300 using xda premium

My N7 is driving me crazy. Bought it last year around October, and it seemed fine at first. Battery would die at around 4-5% which is acceptable. Then it started getting worse over time. At this time it was completely stock - locked and not rooted. It got to the point where it would shut itself off when it reached 40%, so I decided to factory reset, pull battery, unlock, root and install Paranoid Android, hoping this would solve (or help) the issue.
Did all my unlocking and rooting last night, installed PA, set everything up, then started reading on my N7. Device turned off at 65% now. To say that I'm disappointed is an understatement. I'm all out of ideas on what I can do to fix this thing. I charged it overnight and disconnected it from the charger 3 hours ago, and it's still at 100%, even though I've used it quite a bit. Infuriating.

ynrozturk said:
My N7 is driving me crazy. Bought it last year around October, and it seemed fine at first. Battery would die at around 4-5% which is acceptable. Then it started getting worse over time. At this time it was completely stock - locked and not rooted. It got to the point where it would shut itself off when it reached 40%, so I decided to factory reset, pull battery, unlock, root and install Paranoid Android, hoping this would solve (or help) the issue.
Did all my unlocking and rooting last night, installed PA, set everything up, then started reading on my N7. Device turned off at 65% now. To say that I'm disappointed is an understatement. I'm all out of ideas on what I can do to fix this thing. I charged it overnight and disconnected it from the charger 3 hours ago, and it's still at 100%, even though I've used it quite a bit. Infuriating.
Click to expand...
Click to collapse
Sorry to hear this. This is what I'd recommend...
Take the N7 back to bone stock to reduce the number of variables. Follow my suggestions in the OP (I know you've already done them - but I'd still "do the drill" again). If this doesn't work, you can try some of the outlier suggestions that others have made that are less substantiated - why not at that point? If it's still a no-go, I'd return it. For your money, you deserve a perfect N7.

Android P Developer Preview 3

It's out now with both factory images and OTAs
https://developer.android.com/preview/download
https://developer.android.com/preview/download-ota
FlashKernel v2.43 + Magisk 16.4 working fine

Magisk is still working for me, still passing SafetyNet.

Not possible to sideload the OTA file via TWRP, correct?

w0rdie said:
Not possible to sideload the OTA file via TWRP, correct?
Click to expand...
Click to collapse
Not sure. I installed it by unpacking the factory image and removing the -w from the flash-all script

I always forget about that.

got it yesterday through ota, till now it runs fine. No performance difference so far (no unlock timeout luckily, although the problem was with Oreo June update, you'll never know if it travels to P).
Think I found 2 differences so far. The first is pretty cool, on the AOD you see now the weather under the time, next to the date, the weather icon is in color, looks really nice! The battery indicator on the AOD looks the same, bit too small in my opinion, little doubt if the font size is +1... but i don't think so.
The second thing that i found is that when you search in the settings, the result isn't flashing anymore but just a solid color that indicates the option you where searchinig for.
Adaptive Battery is enabled automatic after update, i turned it off before, because it just used more battery in standby when i turned it on. In the first couple of hours, it looks like it now works when enabled. After a couple of days it should be clear if it makes the standby drain a little less.
Couple of dutch apps work now, those crashed before when launching them. NOS, Ziggo GO are working fine now. The ABN Wallet app (sort of google pay replacement) doesn't crash on launch, but i need a reader to enable this wallet, and that reader is at home, i'm at work now
I did not factory reset the phone because it is a small update.

I'm noticing terrible battery drain. For instance unplugged phone when fully charged at around 3:30am by 8:30am battery was at 56%. Before the update only 5-6% would be discharged during that time. Battery stats show no app usage and claims everything is fine so I have no idea of the cause.

nullness said:
I'm noticing terrible battery drain. For instance unplugged phone when fully charged at around 3:30am by 8:30am battery was at 56%. Before the update only 5-6% would be discharged during that time. Battery stats show no app usage and claims everything is fine so I have no idea of the cause.
Click to expand...
Click to collapse
https://developer.android.com/preview/release-notes
Well what you're describing is mentioned in the release notes under Known Issues.

EvilDobe said:
https://developer.android.com/preview/release-notes
Well what you're describing is mentioned in the release notes under Known Issues.
Click to expand...
Click to collapse
True, but it's good to let people know the extent of the problem, known or not. Personally I would not have updated if I knew the issue was this extreme. Point taken about it being a known issue though. :good:

nullness said:
True, but it's good to let people know the extent of the problem, known or not. Personally I would not have updated if I knew the issue was this extreme. Point taken about it being a known issue though. :good:
Click to expand...
Click to collapse
Until now (half day use) I don't have much battery difference between dp2 and dp3. Try to turn adjustable battery management off. In dp2 my phone had less drain with the feature off. This half a day I have turned it on and testing if the drain better or worse. But the drain you're describing isn't normal. Have you tried to factory reset? With Google backup it isn't much of a hassle in my opinion.

nullness said:
True, but it's good to let people know the extent of the problem, known or not. Personally I would not have updated if I knew the issue was this extreme. Point taken about it being a known issue though. :good:
Click to expand...
Click to collapse
I get what you're saying. Just didn't know if you knew about the known issue so I wanted to make you (and others) aware that there are known bug & where to find that documentation. We're all so excited to try the latest/greatest that we never look at what might be wrong.
Also my anecdotal battery usage has been decent since I flashed. Obviously today is my first full day of usage but so far it hasn't been too bad. I unplugged ~6:45am, made a 15min phone call, and it's been sitting on my desk getting minimal usage & I'm at 95% and it's currently 10am.

psychomaniac82 said:
Until now (half day use) I don't have much battery difference between dp2 and dp3. Try to turn adjustable battery management off. In dp2 my phone had less drain with the feature off. This half a day I have turned it on and testing if the drain better or worse. But the drain you're describing isn't normal. Have you tried to factory reset? With Google backup it isn't much of a hassle in my opinion.
Click to expand...
Click to collapse
It's pretty weird. I installed it yesterday afternoon and noticed very little difference, it was just like suddenly overnight despite no app updates or notifications the battery just drained. I turned off the adjustable battery management a couple hours ago and I'm already seeing a difference. I'm going to hold off on the factory reset until I give it another day to see if that does the trick. Thanks for your help!

Hey guys, I keep on getting the "an error has occurred" message when attempting to do the OTA. I know I can probably just side load the factory image later on tonight but is anyone else having this issue? I have a custom kernel installed so maybe that is causing the problem? Although, that said; the custom kernel didn't bother it going from Oreo to DP2.

Just finished installing pp3, along with root and flash kernel 2.43 (latest).
Pin stop being accepted after a couple of reboots, and didn't work not TWRP as well.
Once rebooted again started working
Keyboard didn't work at first just typing this post.
Hope it has something to do with everything just settling down.

Today I too experienced a noticeably faster battery drain. As alluded to above (from release notes) it might be attributed to the new screen settings. I'll see how it does but I've turned off adaptive display and set my static brightness setting to 40%...in the past I used to use 30% and it was plenty bright but not under the new system. Has anyone come up with a recommended brightness on the new slider that is both clean/legible and battery friendly?

mikeynavy1 said:
Today I too experienced a noticeably faster battery drain. As alluded to above (from release notes) it might be attributed to the new screen settings. I'll see how it does but I've turned off adaptive display and set my static brightness setting to 40%...in the past I used to use 30% and it was plenty bright but not under the new system. Has anyone come up with a recommended brightness on the new slider that is both clean/legible and battery friendly?
Click to expand...
Click to collapse
Try turning off Adaptive Battery in the battery settings, it got turned on by default in dp3. After I did that yesterday my battery drain stopped.

So, when I try to install magisk and patch my boot img via magisk manager, my installation keeps failing. It says it's unable to extract the magisk zip file. Anyone else having this problem?

nullness said:
Try turning off Adaptive Battery in the battery settings, it got turned on by default in dp3. After I did that yesterday my battery drain stopped.
Click to expand...
Click to collapse
I just turned it off and will see if there is any difference. I suspect that it may take a little while for the adaptive battery feature to "learn" so that might be the issue. If so, I'm hoping that Google or a thorough reviewer will put out some guidance on how it works and how long a user would need to be patient before seeing any advantage to using it.

A day later and adaptive battery is still on and do not experience the drain you guys experience. With adaptive on the phone has a better battery life than with dp2 and oreo. I travel for work witch has a severe impact on the battery. Normally I have a screen on time of 1 to 1,5 hour after work when the phone reaches 50%. Today it was about 2 hours and 20 to 30 minutes (not checked out at 50%). But I think it's better then before. Hope it will stay this way. Hoping a little more the 'ROM' will settle more and adaptive battery getting better. Will try to report this weekend or next week.

The only annoying thing on this update I found, when you press menu to see your opened apps, it sometimes put it at the side with the "clear all" already displayed.
An occurence which occur randomly: I open whatsapp, I go out to home screen, I press menu to show the opened apps.
Whatsapp is not in the middle, instead it is on the right side, with "clear all" button on the left side, other times it works normally on the middle.
The problem that occurs afterwards is that if I try to clear the application by swiping up, it is stuck in the menu mode, so I have to scroll up to get my list of applications, then scroll down to revert to home screen.
As I mention again, it seems to be random occurence, and I don't know if it's a bug or it's a problem with sensitivity.