Very disappointed in OP3t battery life. Not sure what to do.

[¿GotJazz?]

Well, the results for my v4.0.3 battery drain tests are pretty depressing, so far. The lowest Deep Sleep current draw I have seen is so far is -27 mA for a very short burst, but the majority of the readings were well over -100 mA to -200 mA. This was with basically nothing installed on my OP3t except a few extra battery monitoring apps.

After those results, I tried loading FrancoKernel r12 to see if things improved for battery drain.

... And, they didn't. I even had FrancoKernel set to the "Power-saving" profile.

Yeh i thought nougat aggressive doses the moment the screen is off and doze on the go was disabled. But theres no otherway to explain how i go from 7 percent drain to 2 percent drain overnight with greenify.---------- Post added at 09:53 AM ---------- Previous post was at 09:52 AM ----------

0.2% percent per hour

Hi, @EuEra - Please let us know your settings!! A lot of us would benefit!

 

[domsch1988]

I really can't relate to your problems. On stock 4.0.3 with stock kernel and root I get great battery. Wi-Fi and BT on, data is on. Usage is mostly XDA, browsing, WhatsApp. Some BT music in the car. Compared to my trusty old note 4 this is unbelievably great.
I personally don't care so much for standby drain. I care how much I can use my phone through the day. In the end, I recharge it in the morning anyways...

 

[domsch1988]

Screenshots weren't showing up...

 

[Pavononer23]

Screenshots weren't showing up...

Were you running Wi-Fi all the time or does Wi-Fi appears to you 100% of the time for some reason? I'm asking this, because I get that even when not using Wi-Fi

 

[domsch1988]

Were you running Wi-Fi all the time or does Wi-Fi appears to you 100% of the time for some reason? I'm asking this, because I get that even when not using Wi-Fi

I just never bother to switch it off. But no, i was not connected 100% of the time. More like 30%. I'm not sure what BBS is trying to tell us with these different values. Maybe it's reading something wrong

Just to update: I didn't charge the phone yesterday. Lost 2% over night (9 hours). I put it on the charger with 15% left and 8:50 SoT. These are incredible values compared to any other phone i had to date.

 

[terragady]

For me the battery life is extremely inconsistent, sometimes I can get 8-9 and sometimes 4h is max with less usage than higher SOTs. Not sure what is going on, sometimes google play services, sometimes messegner, sometimes something else. I do not care as 4h SOT i enough for me for one day

 

[¿GotJazz?]

Just to update: I didn't charge the phone yesterday. Lost 2% over night (9 hours). I put it on the charger with 15% left and 8:50 SoT. These are incredible values compared to any other phone i had to date.

@domsch1988 - 2% loss for 9 hours would be really nice. I still lose about 1% per hour overnight (which is why I am still frustrated - I know it should be better). Would you mind running Battery Monitor Widget and let me know what your lowest / average battery drain (in mA) is when the phone is sleeping overnight? I'm seeing about -35 mA per reading. You should configure BMW Current Flow method with "Reverse Android uA".

 

[domsch1988]

@domsch1988 - 2% loss for 9 hours would be really nice. I still lose about 1% per hour overnight (which is why I am still frustrated - I know it should be better). Would you mind running Battery Monitor Widget and let me know what your lowest / average battery drain (in mA) is when the phone is sleeping overnight? I'm seeing about -35 mA per reading. You should configure BMW Current Flow method with "Reverse Android uA".

Sure, i just installed it. I'm Monitring every 5 minutes. Battery is configured with 3400mAh. I'll let it sit some time and report back later. Additionally i'll report back tomorrow after the night.
Just to be sure: i switched back to franco R12 today. I had stock yesterday because of BT Problems. Turned out it wasn't kernel related. Will be interesting to see if it makes any difference. On top i added Magisk plus Dolby Atmos and Stereo mod today. I change from SuperSU to PHH Superuser. All this shouldn't change battery usage in idle mode, but who knows. :silly:

Edit: Where exactly do i find the amount drawn? The table only shows time and Voltage...

 

[¿GotJazz?]

Re-run the Configuration Wizard by pressing the four squares in the upper right corner of the History screen.

On the last configuration screen, enable "History" and "Show mA in history"

 

[domsch1988]

Re-run the Configuration Wizard by pressing the four squares in the upper right corner of the History screen.

On the last configuration screen, enable "History" and "Show mA in history"

Just found it. Long pressing an entry in the History works too.:good:

Edit: Also, have you thought about maybe Battery Monitor Widget being part of the problem? For it to work it'll have to at least produce a wakelock every 10 Minutes... Since we're talking under 1% change over an hour, this might very well increase that too. Adding to that, this app uses the devices own sensor for measuring the draw. This could also lead to differing results on different devices. I think, apart from measuring directly between the battery and the phone with a proper Ampere meter (not possible really), these values can only be estimated. And measuring a difference of 50mA is not an easy task.

 

[EuEra]

I think the key is definitely greenify for standby drain. I installed the xda app this morning. Read 2 posts I was quoted in, didn't reply and closed the app. That's it all day and somehow xda has drained the most out of my battery for the day. I notice WhatsApp is always up there but I can't greenify that or I won't get messages obviously. My guess is it's apps that are sending and receiving a lot of packet sin the background which the xda app has done. I'm going to reset my battery stats, greenify xda app and do the same as I did this morning and check back in a bit if it's at the top of my battery drain again. If not greenify is confirmed to be needed even with androids built in force doze and with Naptime installed.

 

[domsch1988]

I think the key is definitely greenify for standby drain. I installed the xda app this morning. Read 2 posts I was quoted in, didn't reply and closed the app. That's it all day and somehow xda has drained the most out of my battery for the day. I notice WhatsApp is always up there but I can't greenify that or I won't get messages obviously. My guess is it's apps that are sending and receiving a lot of packet sin the background which the xda app has done. I'm going to reset my battery stats, greenify xda app and do the same as I did this morning and check back in a bit if it's at the top of my battery drain again. If not greenify is confirmed to be needed even with androids built in force doze and with Naptime installed.

For me personally greenify never was a solution. It always created more problem than it solved. I stopped receiving notifications or random wakelocks. Same with amplify, powernap or any other battery saving solution. I extensively fiddled with size settings and what not. In the end, choosing the apps I install and their settings wisely has always worked best.

 

[EuEra]

For me personally greenify never was a solution. It always created more problem than it solved. I stopped receiving notifications or random wakelocks. Same with amplify, powernap or any other battery saving solution. I extensively fiddled with size settings and what not. In the end, choosing the apps I install and their settings wisely has always worked best.

Mate obviously you won't receive your notifications you aren't supposed to greenify apps like whatsapp unless you have xposed. You want to greenify every app you don't receive notifications on because it's clear to me android doesn't manage doze very well.

 

[domsch1988]

Mate obviously you won't receive your notifications you aren't supposed to greenify apps like whatsapp unless you have xposed. You want to greenify every app you don't receive notifications on because it's clear to me android doesn't manage doze very well.

I know. Of course I excluded those apps :silly:

So, this night I lost 4 percent in 8 hours. That's fine by me. BMW monitored anything between -22 and -59. I'll retest without BMW tonight.

 

[domsch1988]

Small update. After deleting battery monitor widget my nightly consumption dropped from 0.5 per hour to 0.3 per hour. So BMW was using one third of my battery over night...

 

[¿GotJazz?]

Just found it. Long pressing an entry in the History works too.:good:

Edit: Also, have you thought about maybe Battery Monitor Widget being part of the problem? For it to work it'll have to at least produce a wakelock every 10 Minutes... Since we're talking under 1% change over an hour, this might very well increase that too. Adding to that, this app uses the devices own sensor for measuring the draw. This could also lead to differing results on different devices. I think, apart from measuring directly between the battery and the phone with a proper Ampere meter (not possible really), these values can only be estimated. And measuring a difference of 50mA is not an easy task.

Sure, I've heard of the Heisenberg Uncertainty Principle. I did consider that.

However, I have not had that particular issue on any other Android device I've owned, at least not to the level I have been seeing on the OP3T. My OP3T is losing 1% / hr in standby on OOS 4.0.3 and other ROMs, with no apps installed except BMW and Wakelock Detector. I'm not even really logged in on much stuff when testing that way. On my OnePlus One, I consistently get around -7 mA per reading, and my actual battery life reflects that. I see longer stand-by battery life on my old OPO than I do with my OP3T with the exact same software installed. My old OPO still loses about 1% overnight. My new Kindle Fire HD8 is also running BMW, and I see single-digit battery current drains, and I see about .3% battery drain per day on standby. BMW was falling pretty low on the wakelock list on those devices.

It makes me wonder if there are some system setting(s) you made during your setup that you don't even think much about, but have a big impact on the stand-by battery. For example, I tried turning off the fingerprint sensor to see if it had an effect (since the phone can be woken at any time by the sensor). It didn't seem to impact the current draw by much, but maybe you've made a change like that which did. Location settings, WiFi settings, etc ...

Small update. After deleting battery monitor widget my nightly consumption dropped from 0.5 per hour to 0.3 per hour. So BMW was using one third of my battery over night...

Thanks for the update @domsch1988 (and, for helping out with this!). While BMW had some impact, it still doesn't explain why I'm @ 1% / hr on a barely-modified installation. But I'll also contact the developer - they may need to tweak BMW for the OP3T to reduce the impact.

 

[rapboy91]

Thanks for the update @domsch1988 (and, for helping out with this!). While BMW had some impact, it still doesn't explain why I'm @ 1% / hr on a barely-modified installation. But I'll also contact the developer - they may need to tweak BMW for the OP3T to reduce the impact.

I have same problem like you but after clean flash freedom rom I solved my problem.

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk

 

[¿GotJazz?]

I have same problem like you but after clean flash freedom rom I solved my problem.

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk

@rapboy91 - What are you seeing for your idle battery drain? Also, do you know if the "Menu Open / Close" button opens menus properly in FreedomOS? It doesn't in OOS 4.0.3.

 

[rapboy91]

@rapboy91 - What are you seeing for your idle battery drain? Also, do you know if the "Menu Open / Close" button opens menus properly in FreedomOS? It doesn't in OOS 4.0.3.

this is my actually situation with freedom and kernel franco,what is button menu[emoji28]

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk

 

[¿GotJazz?]

... what is button menu[emoji28]

Basically, under the Settings >> Buttons section.

To see the OOS 4.0.x menu failure issue, I can set Settings >> Buttons >> Back Button >> Long press action to: Open/Close Menu. Then, if I go to my Nova Launcher default home screen and do a long-press on the Back Button, nothing happens. The failure to bring up the menu options when long-pressing the Back Button occurs in other apps, too.

I don't see this problem with TugaPower for the OnePlus 3T. Assigning "Open/Close Menu" to the Recents Short-press action, and then pressing the Recents button will bring up the menu for any app.
@domsch1988 - I did a factory wipe, without installing BMW / Greenify / ForceDoze or any other battery-improving/monitoring apps. I'm still seeing 1% / hour screen-off battery drain.