Here is the definitive solution for those suffering from low SOT and battery drain after updating to Android 10
a) 30 min video playback on mxplayer (720p movie)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
b)20 min web browsing on chrome (news articles and embedded media playback)
c)20 min web browsing on Opera mini(scrolling through forum)
So the real culprit for low SOT is poorly optimised/developed app (in my case opera mini)
--Conclusion--
1)Android 10.3.0 kernel does have reduced 'target load' (hope it might get restored to stock 90% in 10.3.1){as evidenced by checking kernel perameters and behaviour along with terminal emulator for ram usage_under root}
2)Some apps are getting released unoptimized for Android 10,they are exploiting poorly designed or rather I would say performance tuned kernels and are draining battery.
3)Battery optimization of OnePlus software won't work for such an app coz whenever it runs,either in foreground or background it will drain battery
--Solution--
1)Install an app which shows cpu states {the one I used is Ex kernel manager,it's a paid app and i use it to tweak kernel whenever i decide to root my phone,but there are free apps on playstore that offer battery stats functionality for free,download one and make sure the stats shown are that of Gold(big cluster) 825Mhz - 2803Mhz and not Silver(little cluster)}
2)Run the apps you regularly use one after another for atleast 20 min and check cpu stats before and after.
3)You will find app making cpu to run at 2.8Ghz,stop using it and find an alternative,if you can't avoid using it then hope either the app's or oneplus's next update fixes it.
Agreed, as we discussed in another thread. Since then i've seen multiple people talk about the stock kernel shooting up to high frequencies way too fast.
Wouldn't reducing the target load via EX Kernel Manager be possible ? I don't remember if the stock kernel exposes these settings in the app.
Related
chamonix said:
I wrote BetterBatteryStats because I was missing the great battery history that Spare Parts allowed to call on Froyo:
- Process stats with User and System CPU time
- *removed till issue #1 is fixed* Network Usage with bytes sent and received
- Wakelock stats (the most important one when it comes to battery drain)
- Other Usage stats: Awake, Screen On, Phone On, Wifi On, Wifi Running ratios
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This app is still under development and may contain bugs. If you find one you can keep it but I'd be happy if you could also report it to me.
BetterBatteryStats is calling the "batteryinfo" service of Android to retrieve data already lying there without generating overhead.
BetterBatteryStats is focussing and has been tested on Froyo, Gingerbread and Honeycomb (3.1, thanks to daveid) and the APK is set to run only on those versions only.
What are wakelocks and why should you care about them?
When it comes to Android the most discussed and commented topic that I know is battery drain / battery life. I'm a quite heavy user because I spend a lot of time on the train every day reading my mails, surfing and listening to music but still my phone is off for a long time during the day and while I accept the battery being drained while I use the phone I care about it draining slowly while "doing nothing".
And here's the point: my SGS2 drains about 2-10 mAh where it was up at 20-100 mAh before I started cleaning stuff up (readings were taken with "Battery Monitor Widget" after leaving the phone alone 1/2 hour).
Try it yourself
Thanks
to nobnut and brandall for their support, testing and constructive feedback in the early stages of the development
Click to expand...
Click to collapse
Check it out seem to work well, been playing with it for few mintues.
http://forum.xda-developers.com/showthread.php?t=1179809
Battery draining out very fast... Any solutions even after calibarating batterry drain pattern is similar.. Any solutions ?
On xxkpq and non oc v7 kernel..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"screen on" causes drain
There is no a magic solution for that, you just could calibrate the battery as usual, try to set the brightness to the lower level instead of automatic, use only 3G connections when you gonna browse or download something, if you just gonna check the email or whatsapp, etc. you just could use 2G Edge connections to improve the battery life, does not use live wallpapers and root your phone, use an app like no-frills to set a custom processor speed, etc.
but... more than 24 hours with battery it's like a miracle.
I would also try to figure out what causes your phone not to go into deep sleep. Many times your screen is off butbthe phone is awake. BetterBatteryStats might help you with that.
Sent from my GT-I9003 using XDA App
there must be some apps running in the background and prevent deep sleep of the phone and this causes the phone to stay at 300+ mhz looking at the "awake" time of your battery history.
i can just give you the advice to close an app if you dont use it anymore, always close it via the BACK button not via HOME because multitasking might be very cool but the app wont close automaticaly.
Use a task manager ( im actually using the standard task manager) and close the apps which are currently running. You can also check whether your phone goes into "sleep mode" or not with the app CPU Spy. its free on market and shows you the history of your processor speed.
Disable wifi 3g and stuff if you dont use it and close all apps and wait a bit. Then check via CPU Spy if phone was in "deep sleep".
Also how many RAM usage do you have by average?
I get 16-18 hrs of standard battery life.. Is it good? Also my average RAM usage is 330-380...
Sent from my GT-I9003 using XDA App
Yesterday I charged the phone 100% after rurning off the charger kept it untouched for 30 minutes lost 1% battery cause of wakelock.
I had not rebooted the phone for a few days so some apps I used where still running like a dictionary I use which prevents the phone from sleeping.
I used the phone for 70 minutes to watch videos on MX Player for 68 minutes and using tapatalk for 2 minutes then restarted the phone before I went to bed. I had 86% battery left & It was 1.10 am then.
Today I again started using the phone at 12.05 pm or so & I was amazed that my battery was at 83%
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Conclusion: The wakelock is not the fault of Google' Android OS but it's a but that left unresolved by Samsung which does not kill apps completely after using them.
I had removed the dictionary from current tasks, killed running apps using both task manager's RAM Cleanup & Clean Master's memory boost yet the app didn't get killed completely & it's Battery permission which states that the dictionary will prevent the phone from sleeping triggered the stay awake(wakelock) of the Android OS. When I restarted the phone the dictionary got killed completely and thus the phone ate very very less battery.
This was just one app, we have multiple apps inatalled on our phone which prevent it from sleeping.
I really would like to report this to Samsung before they put KitKat out for Exynos Note 3, posting here since at least there are many people here who can help me do so. So that we can have a better user experience with our phone in the future.
Closing Statement: in short poor Task Management & Apps not geeting killed completely trigger Wakelocks.
Solution: Restart the phone before you keep it unused for long durations so you wint suffer from Wakelocks.
Sent from my SM-N900 using Tapatalk
Hello all,
I'm hoping someone can help me figure out what exactly is causing these issues as I've tried all sorts and I can't figure it out.
I'm getting battery drain via android OS (kworker process according to BBS) and I don't know what's causing it. I've attached some screen shots to highlight the problem;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see my phone isn't even awake according to the battery summary screen.
Does anyone know what could be causing this? Or how I can figure out what (app?) is using the kworker process?
I've restored my phone to stock, clean flashed mahdi and installed an earlier version of AK kernel (v068) that I know for certain I didn't have these issues on. However, I'm still getting the issue on a setup I know for certain I wasn't having any issues on a couple of weeks ago.
I've also tried restoring a nandroid from a few weeks ago that I know for certain didn't have any issues (I keep a backlog of 5 previous nandroids each time I update my kernel etc to try and ensure I always have 1 stable version) but I'm still getting the issue on that too.
Thanks for any advice/suggestions.
Anyone? It's driving me crazy! Haha
I'm still getting decent battery life despite this process error, it's just before this I was averaging 0.2% per hour while idle, I'm now averaging 0.6%
Should I be looking for an app as a culprit or is it the kernel/rom or something else completely? I'm guessing it's not the kernel/rom as I've ran this setup before without issues, but what I have managed to find on the kworker process online is that it's kernel related. :s
Just for information for anyone who finds this thread after having similar issues, I've solved it, I still have some kworker CPU time but that's to be expected - its MUCH lower than it was in the screenshots above.
One of or all of the following reduced my kworker process CPU times to a reasonable amount.
Set Wifi Ip address to static rather than dhcp on home network
Changed CPU governor from smartmax to intellimm (ak kernel)
Disabled all services in "Google play services" containing "location.reporting"
Powered by Bacon
While Pixel phones are generally known for creating little interfearance with app perfoamance, in terms of things like managing battery life, I noticed a rather vague option where the OS will improve your phones's battery life by doing things probabbly like sleeping and or ricksting background usage for unused apps and the like.
From what I understand the 7 isn;t the first phone to have this feature as I saw people talking about it ont he 6 series too, though what I was manily wondering is for people who have this turned on or have used it int he past, if they have noticed any issues with some of their apps, such as missed notifactions?
I turned mine off more as a just in case, as comming from Samsung previpously who is nortiorus for being very heavy handed when it comes to their battery savng measures, I'm just wondering how much impact this option has (if any at all), so if it might need to start being listed as a potential problem to check in places such as don't kill my app, or if Google somehow manages to make it a lot less intrusive?
I haven't been able to find any technical infomation on what excatly the feature does to trey and determine just how invavse it might be.
Keep adaptive battery & battery optimization on - Pixel Phone Help
To have apps use your phone's battery only when you need them to, keep adaptive battery and battery optimi
support.google.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've never turned it off since it got introduced. No issues at all. It's supposed to learn how you use your phone, so I'd imagine you shouldn't have missed notifications. And if that's the reason my 7 Pro gets it's 8-10+ hours of SoT, I'd keep on using it.
Never turned off and I think that MUST stay on, because the battery life is really good.
Without it would certainly not be so good.
I am using the way adaptive charging tuned off and adaptive battery tuned on