My phone is usually on idle and not used due to my job. But Im noticing extreme battery consumption even when Im not using it. Never had this issue with other phones. Last night I checked the batter before sleep and it was at 67% at 1 AM, today its 62% at 7 AM so there must be an issue because it should only drain 1 or 2 percents during idle.
In battery settings the top app using the battery is phone idle.
Im on xiaomi.eu 12.5.6 rom but I had the same issue with stop 12.5.3 so I dont think it's because of rom.
I had great battery life with my last phone which was poco x3 nfc with the same settings and apps so it's not because of any third party apps either.
Anyone else experiencing the same problem?
With AOSP ROMs, I even had worst experience when I installed one of the custom kernels because they somehow didn't put the phone into deep doze correctly. But yeah, the idle consumption is quite high - even on stock Kernel.
Currently I use HavocOS and its stock Kernel - and SuperFreeze (from F-Droid store) to freeze most apps right after screen lock. Idle consumption has dropped to 0.1-0.2%/h as a result. I made a thread some days ago regarding this topic... see here.
Thanks. Im gonna try your guide but it's not the most noob friendly guide I've seen
Just Kidding, thanks for your time.
Oh, my thread wasn't meant to be a guide... I did put it in "Question" like you did, but a mod seems to have moved the thread to "General"
My "solution" is only temporary - at least I hope there are still developers out there who value a low idle drain more than fast charging and benchmark numbers...
esszett said:
... and SuperFreeze (from F-Droid store) to freeze ...
Click to expand...
Click to collapse
Sorry for the OT, could it be that the app. is called SuperFreezZ?
Have you noticed any good battery life gains with this app.?
Yeah, sorry, SuperFreezZ: https://f-droid.org/en/packages/superfreeze.tool.android/
For several months I had the problem that from a certain moment, the consumption at idle suddenly increased enormously (from 0.1-0.2 % to 2-3% per hour). Even if I manually forced all apps to stop, In Android's battery info "Android OS" and "Android System" showed up with double-digit percentages. I could only get the phone back to its previous behavior with a restart.
To date, however, it is not clear to me what triggered this. I suspected GCam for a while, then Osmand+, but I couldn't ever confirm that because the problem didn't start whenever I used those programs, just sometimes.
I never found a real solution for this, but SuperFreezZ did.
The best thing I've used for years now is Greenify, its hasn't received an update in more than a year but still works perfectly
Do we need root to use these apps? I remember using greenify before onmy older devices with root but havent used it for a while. Gonna see how much it drops tonight and then try to tweek some things and recheck it tomorrow night.
Weird thing is, I was getting an awesome battery life out of poco x3 nfc, could it be because of the cpu idle? Because that's the only thing that seems different between the 2 devices. (X3 even had an lcd which is supposedly less battery friendly)
Kianush said:
Do we need root to use these apps?
Click to expand...
Click to collapse
Yes.
Kianush said:
I was getting an awesome battery life out of poco x3 nfc
Click to expand...
Click to collapse
Unfortunately, hardly anyone notices this because most users do exactly what the F3 was designed for: Playing games.
I came from a 2.5 years old F1 and it lasts easily longer than the F3 although it has a smaller battery and a LCD screen... The F3 behaves anything but fully developed. These latest high-end SOCs (870, 888) are really powerful, but unfortunately not equally power-efficient. That's the reason why I throttled the CPU and undervolted the GPU. This dropped the active drain from ~8 %/h to <5 %/h on my device and my usecases.
esszett said:
Yes.
Unfortunately, hardly anyone notices this because most users do exactly what the F3 was designed for: Playing games.
I came from a 2.5 years old F1 and it lasts easily longer than the F3 although it has a smaller battery and a LCD screen... The F3 behaves anything but fully developed. These latest high-end SOCs (870, 888) are really powerful, but unfortunately not equally power-efficient. That's the reason why I throttled the CPU and undervolted the GPU. This dropped the active drain from ~8 %/h to <5 %/h on my device and my usecases.
Click to expand...
Click to collapse
Yeah. I used to underclock the cpu on my old phones but I dont know about undervolting. wouldnt it cause issues? I just used 3c toolbox app to set a lower max clock and a lower min clock for cpu cores. I read somewhere that rooting xiaomi.eu rom breaks some functions so I havent rooted it yet. do you have any info on that?
Kianush said:
Yeah. I used to underclock the cpu on my old phones but I dont know about undervolting. wouldnt it cause issues?
Click to expand...
Click to collapse
As long you don't push too hard with undervolting, it works quite well. See attached image (it's not mine, but I have oriented to it).
Kianush said:
I just used 3c toolbox app to set a lower max clock and a lower min clock for cpu cores.
Click to expand...
Click to collapse
I've never heard of it... This seems to be a powerful tool! Nice!
Kianush said:
I read somewhere that rooting xiaomi.eu rom breaks some functions so I havent rooted it yet. do you have any info on that?
Click to expand...
Click to collapse
Konabess doesn't need root, afaik. Extract the boot.img of your ROM and copy it into a folder of your device. Then use Konabess to modify the settings and repack it into a modified boot.img. This file you can flash with TWRP. No guarantee that it works for xiaomi.eu, but it works for AOSP (at least it worked for me).
Kianush said:
My phone is usually on idle and not used due to my job. But Im noticing extreme battery consumption even when Im not using it. Never had this issue with other phones. Last night I checked the batter before sleep and it was at 67% at 1 AM, today its 62% at 7 AM so there must be an issue because it should only drain 1 or 2 percents during idle.
In battery settings the top app using the battery is phone idle.
Im on xiaomi.eu 12.5.6 rom but I had the same issue with stop 12.5.3 so I dont think it's because of rom.
I had great battery life with my last phone which was poco x3 nfc with the same settings and apps so it's not because of any third party apps either.
Anyone else experiencing the same problem?
Click to expand...
Click to collapse
I'm ont he same rom as you and let me explain my experience.
My battery has been insanely good. Even with heavy usage over a period of 4 hours, which included 1.5hrs of SoT and pandora playing though bluetooth all 4 of those hours with dolby and viper enabled. Was at 100 and dropped down to 94%. So It may be an app or setting that you have installed causing problems and draining battery. The only battery saver addition I have installed is Universal GMS doze. Idle time for me It takes me about 5 hours to drop down 1%.
Zaiaku said:
I'm ont he same rom as you and let me explain my experience.
My battery has been insanely good. Even with heavy usage over a period of 4 hours, which included 1.5hrs of SoT and pandora playing though bluetooth all 4 of those hours with dolby and viper enabled. Was at 100 and dropped down to 94%. So It may be an app or setting that you have installed causing problems and draining battery. The only battery saver addition I have installed is Universal GMS doze. Idle time for me It takes me about 5 hours to drop down 1%.
Click to expand...
Click to collapse
Well if there is an app that is causing this, it should be shown in the battery settings. But the only thing that is eating up my battery is phone idle. So it might be a service or something. Im out of options right now unless I find a way to root this rom without facing new problems.... Worst thing with miui is that you cant do things like rooting as easy as other roms.
Btw, would you please tell me the settings and xiaomi.eu version you are on? Im on 12.5.6 stable and using 120hz + vivid color scheme and most of my apps are on blcok background activity except my messaging app. And Im losing battery on phone idle not the screen on time!
Ss below.(dropped from 92 to 82 woh only 30mins screen on time doing nothing but checking xda!) And 7hrs of those 9hrs I was asleep and the phone was on airplane mode + gps off!
You could try BBS or similar apps. Maybe it's an app which prevents the phone to go to deep doze (wakelocks).
BTW: MIUI sucks
Kianush said:
Well if there is an app that is causing this, it should be shown in the battery settings. But the only thing that is eating up my battery is phone idle. So it might be a service or something. Im out of options right now unless I find a way to root this rom without facing new problems.... Worst thing with miui is that you cant do things like rooting as easy as other roms.
Btw, would you please tell me the settings and xiaomi.eu version you are on? Im on 12.5.6 stable and using 120hz + vivid color scheme and most of my apps are on blcok background activity except my messaging app. And Im losing battery on phone idle not the screen on time!
Ss below.(dropped from 92 to 82 woh only 30mins screen on time doing nothing but checking xda!) And 7hrs of those 9hrs I was asleep and the phone was on airplane mode + gps off!
Click to expand...
Click to collapse
I switch my screen refresh rate down to 60hz but since your phone is idle it really shouldn't come into play unless you have always on display or turn screen on for notifications.
Rooting this phone is amazingly easy. Takes like 5mins if that. My Mi 9 lite took longer to root then this phone.
As far as an app draining battery, It more then likely not it since you saying phone idle, which in the past people have said if you phone has problems with signal this can drain a battery. For me this has been a major issue. With AT&T service I would loose double the amount of battery over night (I play pandora through out the night when sleeping). Also if you have apps that are heavy internet usage (unsure where you at but things like facebook and messenger drain tons and yet don't register battery drain on most analytics. And since you using a xiaomi.eu rom I know alot of those bg services are disabled or removed.
Zaiaku said:
I switch my screen refresh rate down to 60hz but since your phone is idle it really shouldn't come into play unless you have always on display or turn screen on for notifications.
Rooting this phone is amazingly easy. Takes like 5mins if that. My Mi 9 lite took longer to root then this phone.
As far as an app draining battery, It more then likely not it since you saying phone idle, which in the past people have said if you phone has problems with signal this can drain a battery. For me this has been a major issue. With AT&T service I would loose double the amount of battery over night (I play pandora through out the night when sleeping). Also if you have apps that are heavy internet usage (unsure where you at but things like facebook and messenger drain tons and yet don't register battery drain on most analytics. And since you using a xiaomi.eu rom I know alot of those bg services are disabled or removed.
Click to expand...
Click to collapse
Yeah thanks for the info. I used to root my devices easily by flashing magisk but it seems they have changed the method, though I found the method on a post on xiaomi.eu website and rooted my device.
Tried to lower cpu frequencies a little and use superfreez app. It seems better now but not as good as what you say...
Gonna play with settings a little bit more and wait for another xiaomi.eu stable update to see if it's a bug on this version.
Kianush said:
Yeah thanks for the info. I used to root my devices easily by flashing magisk but it seems they have changed the method, though I found the method on a post on xiaomi.eu website and rooted my device.
Tried to lower cpu frequencies a little and use superfreez app. It seems better now but not as good as what you say...
Gonna play with settings a little bit more and wait for another xiaomi.eu stable update to see if it's a bug on this version.
Click to expand...
Click to collapse
Someone made a auto script for it, but you will have to reflash rom and factory reset data. You really shouldn't have to change cpu feqs. Also uploading a screenshot of my last 2 hours. I know its only 21min of SoT but also 2 hours off charger but playing pandora as well as some other app usage but still at 100%
esszett said:
As long you don't push too hard with undervolting, it works quite well. See attached image (it's not mine, but I have oriented to it).
I've never heard of it... This seems to be a powerful tool! Nice!
Konabess doesn't need root, afaik. Extract the boot.img of your ROM and copy it into a folder of your device. Then use Konabess to modify the settings and repack it into a modified boot.img. This file you can flash with TWRP. No guarantee that it works for xiaomi.eu, but it works for AOSP (at least it worked for me).
Click to expand...
Click to collapse
Konabess without root won't start, any idea?
thanks
tojdvd said:
Konabess without root won't start, any idea?
Click to expand...
Click to collapse
Ah, ok... I thought you could load a separate boot.img - my fault, sorry!
Then you've to have root for Konabess...
Just to show what's possible with HavocOS 4.9 and 12.5.6 EEA firmware, see atached screenshot... It's with the stock kernel of HavocOS, but with the modifications I did mention here.
Running for almost 2 days
~8 hrs SOT (2 hrs of which with 120 Hz and 2 hrs of which with 100 % brightness, otherwise 60 Hz and brightness between 25 and 50 %) and still 50 % battery left.
Related
I have a SM-T800 on CM12.1 that averages a current drain of around 60 mA during deep sleep. I also have a OnePlus One that averages around 9 mA during deep sleep.
I'm using Battery Monitor Widget Pro with the "Android mA" setting to get my readings on the SM-T800.
Obviously, there's quite a difference there. The SM-T800 draws almost 7x as much current while it's doing nothing - no screen on time.
It makes me think that there must be something I can do to reduce the current drain, especially with a rooted device. But, I haven't been able to figure out what.
Has anyone been successful getting their battery drain lower? If "yes", what have you done?
Thanks,.
¿GJ?
Did you forget the thread you made 2 weeks ago.
http://forum.xda-developers.com/galaxy-tab-s/help/sm-t800-barry-drain-t3157867
John.
Yeah, @Tinderbox (UK), but since the title was messed up I didn't think folks were looking/responding/searching to the older thread.
I think this is still something we can all benefit from, if someone has figured out a way to get our power consumption down. And if someone does respond back to this thread, other folks will be able to find it when they search now.
I use Euphoria OS and debloat it, that gives me a few weeks of standby if it's just sitting on a shelf. Ensure you delete Trebuchet (replace with Nova/Apex/etc) as it sucks a huge amount of CPU power when idle.
If you can run without GApps you'll maximize the savings.
As i said last time my T800 only used 1-2% in 16hours what ma does that work out too, the battery is 7900mah
7900mah/100 =79/16*2=9.8mah
Every time you install an app, it can make an huge difference, if it stops your tablet from sleeping.
You need to check your wakelocks to see which apps are keeping your tablet from going into deep sleep, auto check for emails, sync, alarms will cause your tablet to come out of deep sleep.
John
Thanks, @Tinderbox (UK).
As a test, I decided to wipe out my current installation, and just load the latest Nvertigo SM-T800 ROM and the very minimal nano Open GApps. I had to load a few minor things beyond that to get functional (KeePass Droid, Opera, MyBackup Pro, Wakelock Detector). I disabled all Google account sync items.
I disabled Trebuchet wake-ups, and set autostart off (Thanks, @fraser.dk)
I'm still seeing about 1% drop every 4-5 hours.
Nothing stood out from Wakelock detector. After 24 hours of the tablet sitting idle, the wakelocks were all less than 30 each.
Are you running a specific ROM or Kernel?
I am on the Stock UK v4.4.2 kitkat rom, I have never flashed though i am rooted.
If you are rooted, try the app in the link below, it link to XDA and you can download a version of cpu spy reloaded, it works great at spotting wakelocks it`s the only wakelock detector i use now.
I am running an Sony App that is supposed to stop all wakelocks, it`s in standby mode, you can whitelist apps if you like, I am not certain if it`s doing anything at the moment, you need root and exposed installed.
http://www.xda-developers.com/optimize-battery-life-with-this-useful-app/
A 1% drop over 5-6 hours is not bad.
John.
So i have an result on the Sony Battery App, I put my Tab S into sleep mode at approx 12:30AM it was at 69% , I woke it up at 6:50pm, it was still on 69% after 17hrs.
Click the link below, to see an screenshot of GSam Battery Monitor.
John.
http://i.imgur.com/mJlQQYM.png
for me i have downgraded back to stock kitkat 4.4.2, debloated, rooted and xposed installed, and use powernap, i can use the tablet all day and still have between 45% - 60% battery left depends on if i am playing games or not... i have tried so many apps and custom roms in lolipop and none of them have good battery life....
PowerNap which is the Sony app i use, only reduce battery drain in sleep mode, by stopping all wakelocks, it does not reduce the power that games or other high drain app require, so how does you battery last longer, how much power were you loosing overnight when you tablet should have been sleeping it must have been immense.
John.
Tinderbox (UK) said:
PowerNap which is the Sony app i use, only reduce battery drain in sleep mode, by stopping all wakelocks, it does not reduce the power that games or other high drain app require, so how does you battery last longer, how much power were you loosing overnight when you tablet should have been sleeping it must have been immense.
John.
Click to expand...
Click to collapse
on kitkat i had no major battery drain, i just like having powernap on my device... on LP like i say even just using the tab battery would drain like 1% every min... just doing typical web use... i have tried everything to get good battery life on LP but nothing works for me at least.. but with KK i have no issues...
A lot of people say they have had no problems with lollipop, but there is an significant number that have reported problems after upgrading, I decided to stick with kitkat and await android m.
1% a minute just browsing that`s bad.
John.
Monster212 said:
on kitkat i had no major battery drain, i just like having powernap on my device... on LP like i say even just using the tab battery would drain like 1% every min... just doing typical web use... i have tried everything to get good battery life on LP but nothing works for me at least.. but with KK i have no issues...
Click to expand...
Click to collapse
I think I'll try going back to KitKat, and see how things go.
I have been frustrated on how fast the battery drains when doing minimal tasks, like reading an ebook (about 1% drain a minute).
Downloading KitKat from Sammobile now.
¿GotJazz? said:
I think I'll try going back to KitKat, and see how things go.
I have been frustrated on how fast the battery drains when doing minimal tasks, like reading an ebook (about 1% drain a minute).
Downloading KitKat from Sammobile now.
Click to expand...
Click to collapse
that how it was for me... 1% a minute.. i like kitkat and very happy with it does what i need and awesome battery life..
Bummer.
I installed the Canadian stock KK ROM (T800XXU1ANJ6_T800XAC1ANI1_HOME.tar.md5) onto my US SM-T800, and it's boot-looping.
I thought I should be able to load the Canadian version without any problem.
Is there a way to turn the tablet off when it is bootlooping? I don't want the battery to drain while I'm downloading another ROM.
Try this to stop boot loop.
Step 13 of post 3.
http://forum.xda-developers.com/galaxy-tab-s/help/sm-t800-best-to-downgrade-5-0-2-to-t3069929
John
¿GotJazz? said:
Bummer.
I installed the Canadian stock KK ROM (T800XXU1ANJ6_T800XAC1ANI1_HOME.tar.md5) onto my US SM-T800, and it's boot-looping.
I thought I should be able to load the Canadian version without any problem.
Is there a way to turn the tablet off when it is bootlooping? I don't want the battery to drain while I'm downloading another ROM.
Click to expand...
Click to collapse
Thanks, @Tinderbox (UK)!
Out of the bootloop now, and setting up KK.
What do you do to prevent OTA updates? I have TWRP installed via the All-in-One Auto Root.
If you are rooted you will not get ota updates, if you are not freeze the updater an tab s owner did that with an app called "package disabler" it works without root but the free version keeps being removed from google play store, the full version is £2 (£1.50) just reduce.
John.
@Tinderbox (UK) WHAT KITKAT ROM YOU ARE USING ????
stock UK kitkat rom v4.4.2, Lollipop has been out for my T800 10.5" for an couple of months, but it is full of bugs, and quite a few people have went back to kitkat.
Kitkat has been solid for me, I ran it for 164 days continually, I never rebooted or shutdown in that whole time, no problem at all.
John.
rookie12 said:
@Tinderbox (UK) WHAT KITKAT ROM YOU ARE USING ????
Click to expand...
Click to collapse
Been poking around here and reading all the posts that people had mentioning battery life on stock/cm11. Is battery life really that good? I find myself trying everything possible (including hardly using the device, turning brightness all the way down, turning off bluetooth & Dynamic perspective) and I find that my phone is dropping like a brick. I can have the phone lose %s in front of me just having the screen open for a few minutes doing nothing else.
I even have two apps to optimize/kill all other apps and I'm finding that this phone is dying faster than a t-mobile pre paid LG L90 I was using prior. I just don't see how people with stock and all the features on are getting more than 5 hours battery life tops. This phone dies while you use it on the charger, which is a first from any phone I've ever used.
How do your experiences stack up? Do I just have a bad unit? Really considering going to cm11 now (really wanted to like Fire OS).
You must have something wrong with the phone. I have had Samsung S3's and S4's and the Fire is far and away the best I have experienced for battery life. I am getting close on two days on a full charge although I do not use it a great deal for voice calls.
dmarchant said:
You must have something wrong with the phone. I have had Samsung S3's and S4's and the Fire is far and away the best I have experienced for battery life. I am getting close on two days on a full charge although I do not use it a great deal for voice calls.
Click to expand...
Click to collapse
Are you keeping Dynamic perspective off with a low brightness instead of auto? Don't see how two days is possible unless you absolutely never used the device. I can lose like 10% an hour just on the browser reading text sites.
Fire has the best battery life of any android phone I've owned. I'm on fire os with a different launcher and I have dynamic perspective on (not for home screen obviously). I'm also using auto brightness. I'm rooted with gapps installed. I get great standby time and even in use its good. You should get gsam battery monitor and see what's going on, although I think you might have a broke unit.
Here is a picture from Gsam (I don't have my phone rooted). I think this is pretty bad for only 3:28hrs of screen on time and that was with the screen at the lowest brightness, not on auto. For app usage I have 7% coming from a game I was playing, but the rest of the drain is coming from system and kernel. Would really like to see another users stats with similar screen on time, as I'm pretty sure I could completely kill this phone's battery in 4-5 hours just using silk browser on Reddit.
h ttp://i.imgur.com/JSXxRGN.png
Sent from my SD4930UR using XDA Free mobile app
Ztcc said:
Here is a picture from Gsam (I don't have my phone rooted). I think this is pretty bad for only 3:28hrs of screen on time and that was with the screen at the lowest brightness, not on auto. For app usage I have 7% coming from a game I was playing, but the rest of the drain is coming from system and kernel. Would really like to see another users stats with similar screen on time, as I'm pretty sure I could completely kill this phone's battery in 4-5 hours just using silk browser on Reddit.
h ttp://i.imgur.com/JSXxRGN.png
Sent from my SD4930UR using XDA Free mobile app
Click to expand...
Click to collapse
Can you check the kernel wake lock section of the same app?
ratbags said:
Can you check the kernel wake lock section of the same app?
Click to expand...
Click to collapse
On the off chance that you or anyone else can help me understand what's going on I ran a ~10% drain test and made a picture including information from WakeLock Detector and GSam. This drain seems very bad considering the screen was only on for a total of 16 minutes and I lost 8% power.
imgur.com/YbgFfmA
Ztcc said:
On the off chance that you or anyone else can help me understand what's going on I ran a ~10% drain test and made a picture including information from WakeLock Detector and GSam. This drain seems very bad considering the screen was only on for a total of 16 minutes and I lost 8% power.
imgur.com/YbgFfmA
Click to expand...
Click to collapse
Your phone isn't going into deep sleep. It's hard to determine exactly what's going on there but if you download kernel adiutor (yes, that's the spelling) you'll see its locked at 300mhz most of the time. I know it sounds crazy but have you rebooted? That can often sort out a misbehaving app. Are you rooted? If so deploy greenify.
ratbags said:
Your phone isn't going into deep sleep. It's hard to determine exactly what's going on there but if you download kernel adiutor (yes, that's the spelling) you'll see its locked at 300mhz most of the time. I know it sounds crazy but have you rebooted? That can often sort out a misbehaving app. Are you rooted? If so deploy greenify.
Click to expand...
Click to collapse
I am rooted. That screenshot was with using greenify :[
I will get that kernel app.
ratbags said:
Your phone isn't going into deep sleep. It's hard to determine exactly what's going on there but if you download kernel adiutor (yes, that's the spelling) you'll see its locked at 300mhz most of the time. I know it sounds crazy but have you rebooted? That can often sort out a misbehaving app. Are you rooted? If so deploy greenify.
Click to expand...
Click to collapse
Do you have any recommended settings for that app? I disabled something that I think is allowing me to enter deep sleep more, but I have to finish testing. Thanks for the help ratbags!
Oh I see what's the wrong.
Battery usage give me a wrong information.
My fire phone lasting about 5hrs turning on screen.
Very very good !!
Thank you.:good::good:
Five hours is good??
Ztcc said:
Five hours is good??
Click to expand...
Click to collapse
5 hours of "screen on time" is solid, the combined time incl. standby, etc. is of course much longer. He didn't know how to interpret the statistics from the device, it was a misunderstanding.
Ztcc said:
Do you have any recommended settings for that app? I disabled something that I think is allowing me to enter deep sleep more, but I have to finish testing. Thanks for the help ratbags!
Click to expand...
Click to collapse
That kernel app won't help battery life but it will show you how long you spend in deep sleep.
As for greenify, you should greenify all the Google apps. I actually greenify everything except sms app, browser, phone and alarm apps.
Also, this could possibly be some kind of location based frippery. Turn location services off or onto battery saving mode if only temporarily. And turn off auto sync if it's on.
I recently purchased a P2. Every thing's good. Battery life is also better than most of the phones. But, one thing that I noticed is that Cpu usage is high in idle state too. I did a factory reset. But, the problem persists. I usually get around 8hrs SOT. I think that's lower than most P2's.
Is there a way to solve this? My bootloader is not yet unlocked. Have to wait 12 more days.
Thanks.
Wait 12 more days, unlock the bootloader and flash the DrainFix.zip that can be found in Lineage and RR threads.
911-Future_Maker said:
Wait 12 more days, unlock the bootloader and flash the DrainFix.zip that can be found in Lineage and RR threads.
Click to expand...
Click to collapse
Thanks..
Are you still on Marshmallow ? There was a bug that caused the cpu to stay at 1689mhz on some phones .
And Drainfix wont make any difference . It changes the governor from performance to interactive , but your already on the interactive governor .
The Mero said:
Are you still on Marshmallow ? There was a bug that caused the cpu to stay at 1689mhz on some phones .
And Drainfix wont make any difference . It changes the governor from performance to interactive , but your already on the interactive governor .
Click to expand...
Click to collapse
I am now on nougat. But same problem. Already performed factory reset a couple of times. Cpu doesn't stay on 1689mhz. Now it fluctuates. But, still heavy usage from CPU.
Battery drains by 7-8% overnight.
I already installed Nougat, but the phone is sleeping as dead. Charged it to 95% last night, put it on airplain mode and today in the morning after 9h to battery is still 95%.
The android battery stats show that CPU is awake all time, but BetterBatteryStats shows that everything is fine.
Sent from my Lenovo P2a42 using Tapatalk
bibekdwa said:
I am now on nougat. But same problem. Already performed factory reset a couple of times. Cpu doesn't stay on 1689mhz. Now it fluctuates. But, still heavy usage from CPU.
Battery drains by 7-8% overnight.
Click to expand...
Click to collapse
Mine is dropping in Flight mode too . Its probably the system tuning itself up while its idle , it should settle down in a few days
I have the same problem
Have you found any solution? I purchased it on 21 April 2017 and currently running it on Naugat.
The Mero said:
Are you still on Marshmallow ? There was a bug that caused the cpu to stay at 1689mhz on some phones .
And Drainfix wont make any difference . It changes the governor from performance to interactive , but your already on the interactive governor .
Click to expand...
Click to collapse
Here is how it was for me.
I took phone out of the box with MM preinstalled and right after i turned up the screen and connected to my wifi network it asked me to update OS to Nougat 7.0 so i did. The bug that caused CPU stays at 1.69Ghz occures for 100% on Nougat, and you say on MM too ?
Anyways, for me, hard reset solved the problem, at least this one.
But battery drain still takes place. In normal mode 3-4%, in ultra power saving - 5-6% over night (5-7h). This is pretty a lot i would say.
ps: Phone goes into deep sleep mode according to BetterBatStats.
On p2 i get average SOT of around 13hrs
Antaroo said:
Here is how it was for me.
I took phone out of the box with MM preinstalled and right after i turned up the screen and connected to my wifi network it asked me to update OS to Nougat 7.0 so i did. The bug that caused CPU stays at 1.69Ghz occures for 100% on Nougat, and you say on MM too ?
Anyways, for me, hard reset solved the problem, at least this one.
But battery drain still takes place. In normal mode 3-4%, in ultra power saving - 5-6% over night (5-7h). This is pretty a lot i would say.
ps: Phone goes into deep sleep mode according to BetterBatStats.
Click to expand...
Click to collapse
I had same problem under stock Nougat before i installed the magisk and the crossbreeder mod. Now I have 0-2% battery drain at night.
Vis77 said:
I had same problem under stock Nougat before i installed the magisk and the crossbreeder mod. Now I have 0-2% battery drain at night.
Click to expand...
Click to collapse
What are those mods ? Are they xposed modules ? What do they do ?
Antaroo said:
What are those mods ? Are they xposed modules ? What do they do ?
Click to expand...
Click to collapse
Magisk module:
https://forum.xda-developers.com/apps/magisk/tweak-crossbreeder-lite-t3594401
Thanks ill try it once im rooter in 9 days.
So far im very dissapointed with my bateery life. I get 8.5h over 3 days use. It's not really a good result as for such a battery and screen technology.
I counted exactly - 23% of battery went for standby. It's a lot, isnt it ?
Any ideas if its Nougat fault, or bad piece of phone ?
I think u need to drain your battery completely till the phone shuts down then recharge completely while the phone is off then power on and try
Vis77 said:
I had same problem under stock Nougat before i installed the magisk and the crossbreeder mod. Now I have 0-2% battery drain at night.
Click to expand...
Click to collapse
How did you install magisk? Did you root using magisk or using phh superuser? Right now I am rooted with phh.. I would like to change to magisk. Please guide or send link to a guide..
Thanks
spunxhoe said:
How did you install magisk? Did you root using magisk or using phh superuser? Right now I am rooted with phh.. I would like to change to magisk. Please guide or send link to a guide..
Thanks
Click to expand...
Click to collapse
Systemless root under Nougat with magisk:
1. Format data partition to ext4.
2. Type in the recovery terminal :
echo "SYSTEMLESS=true" >> /data/.supersu
3. Flash the magisk12.zip
4. Reboot
5. Install Magisk manager
If you have another su like phh, will not work, you need reinstall the original boot image.
Should be around 0.2%/hr...
Antaroo said:
Thanks ill try it once im rooter in 9 days.
So far im very dissapointed with my bateery life. I get 8.5h over 3 days use. It's not really a good result as for such a battery and screen technology.
I counted exactly - 23% of battery went for standby. It's a lot, isnt it ?
Any ideas if its Nougat fault, or bad piece of phone ?
Click to expand...
Click to collapse
The only way to know the standby drain is normal or not, try install GSam Battery Monitor app...
As shown above, native stock ROM S233 should drain around 0.2% per hour, which in turn to be 0.2% x 8 hours sleep = 1.6% or 1.6% of 5,100mAh is 81.6mAh energy consumption...
Conclusion:
P2a42 can survive in airplane mode for 20 days on a single charge.
azeemzuhair said:
The only way to know the standby drain is normal or not, try install GSam Battery Monitor app...
View attachment 4189280
As shown above, native stock ROM S233 should drain around 0.2% per hour, which in turn to be 0.2% x 8 hours sleep = 1.6% or 1.6% of 5,100mAh is 81.6mAh energy consumption...
Conclusion:
P2a42 can survive in airplane mode for 20 days on a single charge.
Click to expand...
Click to collapse
So, i just checked my Gsam, and here is what is says:
0.7%/h drain in standby which is more or less what im losing of battery juice over night. It's stick Nougat form OTA update.
Right now im at 44% and i switched into ultra power saving mode. It says that i have left around 51h. I dont think this is normal. Isnt it really very little time ?
It's just a little over 2 full days @ 44%
Damn...
Should i return this piece to store with complain i got faulty one ?
Can you please switch to ultra power saving mode just for a second and tell me what did it calculate aproximately as time left on battery ?
Ever since I updated to 8.1.0 with December security patch, I've noticed my battery draining faster than normal. I was getting 4-5 hours of SOT with around 45-50% battery left. This was after being off the charger for 12-16 hours. Now I'm getting about half the SOT at similar numbers. Anyone have any ideas?
Sent from my Nexus 6 using Tapatalk
andrewjt19 said:
Ever since I updated to 8.1.0 with December security patch, I've noticed my battery draining faster than normal. I was getting 4-5 hours of SOT with around 45-50% battery left. This was after being off the charger for 12-16 hours. Now I'm getting about half the SOT at similar numbers. Anyone have any ideas?
Click to expand...
Click to collapse
Excuse my stating the obvious, but you need to find what process or app is using the battery. You should be able to get a rough idea just using the new features under Settings>>Battery. It will identify which apps are using the most juice. Run the phone in Safe Mode to see if your battery life goes back to normal. It could also be a service like Google Play Service which sometimes wigs out and starts chewing battery. Are you rooted? If you need more detailed information there are battery drain apps available to help isolate the problem (BBS and GSam). These apps require root to give the best results.
v12xke said:
Excuse my stating the obvious, but you need to find what process or app is using the battery. You should be able to get a rough idea just using the new features under Settings>>Battery. It will identify which apps are using the most juice. Run the phone in Safe Mode to see if your battery life goes back to normal. It could also be a service like Google Play Service which sometimes wigs out and starts chewing battery. Are you rooted? If you need more detailed information there are battery drain apps available to help isolate the problem (BBS and GSam). These apps require root to give the best results.
Click to expand...
Click to collapse
Not rooted and currently locked. I've downloaded GSAM and have adb permissions and it simply says things like Chrome, RCS Phone and Play services. If you see from the photos below you can see what I'm talking about. Chrome currently isn't that bad, but yesterday and the past couple days it's been like 9% or more of the battery.
https://photos.app.goo.gl/hFvQKO7q3pZTHFNb2
Sorry the screenshots were too large for uploading.
Sent from my Nexus 6 using Tapatalk
andrewjt19 said:
Not rooted and currently locked. I've downloaded GSAM and have adb permissions and it simply says things like Chrome, RCS Phone and Play services. If you see from the photos below you can see what I'm talking about. Chrome currently isn't that bad, but yesterday and the past couple days it's been like 9% or more of the battery.
Click to expand...
Click to collapse
Two things: I've never seen phone or kernel use that much battery. On one page phone usage is 33 seconds, yet it used 9% ? I think RCS is running the background all the time. See if you can toggle it to not run in the background under Settings>>Apps>. High kernel I'm guessing is a kernel wakelock or multiple. You've probably loaded app(s) that are creating the problem, but you need to find out which one is causing the wakelocks. There is a wakelock detector "lite" app that doesn't need root but I don't know how well it works. I know the root version works well. Lastly, on the first screenshot with the battery, scroll to the bottom of the page and see which apps are listed there. I'd be willing to bet if you ran the phone in Safe Mode, your battery drain would disappear, meaning your user apps are causing it.
v12xke said:
Two things: I've never seen phone or kernel use that much battery. On one page phone usage is 33 seconds, yet it used 9% ? I think RCS is running the background all the time. See if you can toggle it to not run in the background under Settings>>Apps>. High kernel I'm guessing is a kernel wakelock or multiple. You've probably loaded app(s) that are creating the problem, but you need to find out which one is causing the wakelocks. There is a wakelock detector "lite" app that doesn't need root but I don't know how well it works. I know the root version works well. Lastly, on the first screenshot with the battery, scroll to the bottom of the page and see which apps are listed there. I'd be willing to bet if you ran the phone in Safe Mode, your battery drain would disappear, meaning your user apps are causing it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/4v8seKwMJnceaVUG3
Well in safe mode my drain is gone so I'm not sure which app is doing it, but to directly answer your question about the RCS it is an overall app meaning it is related to several Google play services. I'll upload a photo of it. I have to reboot into normal mode.
Edit: I'm wrong about that it was the play services.. I'll have to start uninstalling the apps to determine which one is draining the battery I guess.
andrewjt19 said:
https://photos.app.goo.gl/4v8seKwMJnceaVUG3
Well in safe mode my drain is gone so I'm not sure which app is doing it, but to directly answer your question about the RCS it is an overall app meaning it is related to several Google play services. I'll upload a photo of it. I have to reboot into normal mode.
Edit: I'm wrong about that it was the play services.. I'll have to start uninstalling the apps to determine which one is draining the battery I guess.
Click to expand...
Click to collapse
RCS can be a real battery hog, but I don't know why. I don't have RCS on AT&T. Do you use Messages as your primary SMS? Open Settings>>Advanced and see if you can toggle off "Enhanced Features". Open properties and check if it is using battery optimization. If it is not, set Messages to battery optimization. You can always turn these back on later if the battery drain remains.
My battery life has been restored to pretty much the same as it was with 8.0. I also noticed poor battery life after installing the 8.1 update, even though they changed the way battery life is estimated with this update (supposedly). Something just felt off, but now everything feels great! I am fairly certain what changed is installing the Greenify Magisk module and/or the Google play services doze module (this enables battery optimization on the Google play services app). Not sure which one really made the difference because I installed them at the same time. However, there is definitely a major difference!!
js042507 said:
My battery life has been restored to pretty much the same as it was with 8.0. I also noticed poor battery life after installing the 8.1 update, even though they changed the way battery life is estimated with this update (supposedly). Something just felt off, but now everything feels great! I am fairly certain what changed is installing the Greenify Magisk module and/or the Google play services doze module (this enables battery optimization on the Google play services app). Not sure which one really made the difference because I installed them at the same time. However, there is definitely a major difference!!
Click to expand...
Click to collapse
Here's proof!!
js042507 said:
Here's proof!!
Click to expand...
Click to collapse
In my experience that's really good.
Before 8.1 I noticed about 11% per hour during screen on use and about 0.33% per hour while on stand by in my pocket or a little bit better if it's just sitting on my night stand not moving while I'm sleeping (I think doze is more extreme in that situation) which seems to match what you are getting. Based on that screen shot I think that's like 8 hours screen on time over like 35 hours for a full charge. I've done a little bit better but not much. That's excellent battery life.
Since 8.1 it has dropped. Best now is maybe 7 to MAYBE 7.5 hours over maybe 26-28 hours. In my experience battery life always drops after an update but this case is far from the worst. I remember when my Nexus 5 updated from KitKat to Lollipop. The battery drop was awful and to make matters worse the battery life of the Nexus 5 was pretty bad to begin with.
js042507 said:
Here's proof!!
Click to expand...
Click to collapse
Which font is that?
MarwanTamer said:
Which font is that?
Click to expand...
Click to collapse
Default. I didn't change the system font.
js042507 said:
Here's proof!!
Click to expand...
Click to collapse
What are your settings for Greenify
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
What are your settings for Greenify
Click to expand...
Click to collapse
Here...
So in my last reply I thought I was wrong about RCS Phone app being a conglomerate of several apps in the phone. For some reason I couldn't find the information I needed at that time. I wiped my phone and started over after posting this thread. I was trying to isolate the misbehaving app. I thought it might have been greenify actually, but no the drain has returned to a lesser extent though. Here's some photos of this RCS app from GSAM.
https://photos.app.goo.gl/rvw077mBfNULbsRE3
I'm not sure what is causing the drain at this point. I've installed Better Battery Stats to locate the wakelocks so I can ignore them through ADB.
Sent from my Nexus 6 using Tapatalk
andrewjt19 said:
So in my last reply I thought I was wrong about RCS Phone app being a conglomerate of several apps in the phone. For some reason I couldn't find the information I needed at that time. I wiped my phone and started over after posting this thread. I was trying to isolate the misbehaving app. I thought it might have been greenify actually, but no the drain has returned to a lesser extent though. Here's some photos of this RCS app from GSAM.
Click to expand...
Click to collapse
Have you tried disabling RCS ? (Post #6). BBS is good for idle drain, active drain not so much. It's best run overnight without touching the phone for 8 hours or so. Pick the phone up in the morning and create/save a log file as quickly as possible. Post the log to the BBS thread if you need help deciphering.
v12xke said:
Have you tried disabling RCS ? (Post #6). BBS is good for idle drain, active drain not so much. It's best run overnight without touching the phone for 8 hours or so. Pick the phone up in the morning and create/save a log file as quickly as possible. Post the log to the BBS thread if you need help deciphering.
Click to expand...
Click to collapse
I cannot disable it since it is comprised of multiple apps. You can see it in the pics on my last post.
Sent from my Nexus 6 using Tapatalk
I know that many of you are satisfied to get through the day with one battery charge because you use the device permanently. At night, the smartphone is connected to the charger and that's it. If you belong to exactly this group of users, you can save yourself the further reading
Well, I am a bit different in this aspect. I sit in front of the PC for most of the day and use the smartphone comparatively rarely. I want to be reachable by phone, but I don't need to chat via Messenger all day. When I have time, I turn on WiFi or mobile data and retrieve messages manually. Generally, I only turn on all needed connections when I'm actively using them - the only exception is cellular for calls and text messages, that only gets turned off at night with flight mode. I also don't watch Netflix & Co via smartphone, in general I rather rarely watch videos on the smartphone. I also do not need to play games with the smartphone and if I do, then Sudoku or similar is enough for me For all these applications I have a PC, large monitors and an even larger TV as screen. Sounds oldscool, and yeah, that's me
I also have relatively few apps installed - only the ones I actually use. When possible, I use the mobile versions of websites rather than installing an app for them. This has the advantage that I only need one app for many things, and I need to keep it up-to-date: a browser.
In short: I am not interested in benchmark numbers of CPU/GPU. I need a reasonably good camera and a not too lame CPU for post-processing. In my free time, I am usually in the outback for several days/weeks without a power source (well, I have a small powerbank, of course), so a long runtime is mandatory. I want an enduring and reasonably smooth running phone that I don't have to charge every day or even every two or three days.
When I (not entirely voluntarily) switched from the F1 to the F3, I expected a lot because of the OLED screen and the larger battery. However, I had to realize that I have problems to even come close to the runtimes of my optimized F1.
I started logging the battery charges of the F1 purely out of interest.
A few relevant averages from 119 logged charges (in 787 days) are as follows:
Run time: 109 hours (so about 4.5 days).
SOT: 8 hours
Phone calls: 2.5 hours
I continued the log with the F3. The averages from 30 logged charges (in 111 days):
Run time: 62 hours (so just over 2.5 days).
SOT: 6.5 hours
Phone calls: 1.5 hours
Of course, AOD, pocket mode, DT2W, light sensor and all that stuff is disabled and I only use dark themes and 60 Hz. Just like on the F1, I don't use any Google services on the F3. Practically nothing changed in my usage behavior. However, the results are mighty disappointing...
I experimented a lot, other kernels, other ROMs, but it was practically the same/similarly bad everywhere. Now I'm running HavocOS with its own Kernel for the time being, because the idle consumption seemed to be lower than with other ROMs/Kernels. However, I made a few tweaks (all apps are available in the F-Droid Store):
1. Smartpack Kernel Manager: I lowered the boost clocks of the prime core and of the 3 main cores by a few 100 MHz.
2. Konabess: I undervolted the GPU and flashed the modified Kernel.
3. SuperFreeze: Most apps are frozen when the screen is locked. There are a few exceptions (Tidal, OsmAnd+, AntennaPod, etc.) that are allowed to run in the background until I force them to stop.
4. Autostart: I disabled the start triggers of almost all apps to keep closed apps closed.
Of course, my F3 does not break any benchmark records with this, but that is not my point. Everything still runs smoothly. With these things in place, I'm finally getting these averages from 3 charges:
Run time: 83 hours (so about 3,5 days)
SOT: 9 hours
Phone calls: 2 hours
That's still far from my original hope, but at least it's a significant increase. I very much hope that I have not yet reached the maximum.
TLDR
I would be interested to know if there are any people here at XDA who are similarly "passive". And if so, how satisfied they are with the F3 and/or what settings/tweaks they have made to achieve long runtimes and good SOT at the same time. I would be pleased about a few experiences and comparison values
I know this is probably the opposite of what you want to read, and I'm just a simple active user of my phone, but I'd say, don't get too frustrated with battery life / SOT. I'd say it just is what it is.
If you adjust your phone to as much battery saving as possible, it's probably not fun, because you have so many cool awesome features on the Poco F3, like 120 Hz and MEMC for YouTube etc...
I'd say if you want to keep Bluetooth on to receive notifications and calls on your smartwatch then just go ahead.
Instead of going for maximum battery saving, you could go for a balance of enabling some of the cool features and ditching the ones you don't want as much, like AOD or a 2. sim-card..
I don't know if this reply is any helpful, probably not, but what gives シ
{
"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"
}
dreamytom said:
I don't know if this reply is any helpful, probably not, but what gives
Click to expand...
Click to collapse
Haha, thanks for your answer
Indeed, I have set up the phone according to my needs and wishes and I am disappointed that contrary to the logical assumption (that a larger battery and an OLED display promise longer runtimes), the runtime has decreased significantly compared to the F1.
I'm not limiting myself, if that's how you understood my post. I have to limit the phone and turn off all the unnecessary stuff, because a smartphone is more a useful tool than a toy for me. I don't need permanent location tracking. Most of the time I know where I am and where I want to go. If not: It takes 2-3 seconds for the GPS to find me after switching on... I don't need 120 Hz, because I don't see any difference in my usecases... Beyond that, I don't need a smartwatch either. I'm glad I don't have to wear a watch anymore since there are mobile phones.... And after all, I don't need to be permanently available via chat. Whoever has something important to say can call me. Otherwise this one can wait for an answer... When my smartphone is locked, so the screen is off, it should be quiet, unless it is important or I explicitly want to get notified. If it's constantly blinking, vibrating or jingling, I would never get to work
I know, it sounds not very trendy: Many of the "innovative" features bring solutions to problems that I didn't/don't have.
Good idea. When I used mi 9 lite or poco x3 nfc I was able to use my phone from 3 to 5 days without chargeing. Now I have poco f3 and I have to change something. Ok, I use only LOS from years on all my devices ... maybe time to change ...
My way to manage battery was and is now is a script in Automagic. When I lock the screen I turn off interfaces like wifi, mobile data, locatin/gps, bluetooth, nfc, (cellular in tablets without card) and turn on when screen is unlocked. Never use airplane mode for cut LTE signal and smses. When the phone is locked more than 60 minutes I turn on battery saver mode.
Of course , each device has predefined which interface can be turned off ... Autostart I control in SDMaid. If I cut init signals app will not be able to start and use energy in background in exception I will call it. (The games are the best example to want do something in background what is absolutely not needed for me) I never freeze any apps neither overeclock cpu nor undervoltage gpu.
This what I see on my new F3 is no power after 40 hours of work. I found wakelock in LOS but blocking it in Optimus does not change many - I see deep sleep but 1%/h night lost is not very big difference when I had no deep sleep in LOS kernel. Baallam is empty of this problem but 1%-0.9% is the same result.
I have to say goodbye to LOS , I afraid.
Today I have active drain 8%/h, idle drain 0.86%/h (LOS 18.1 and baalam).
To be honest, I am OK with the battery backup of the F3. With all the modifications I could now at least manage to equalise the running time of the F1 (with LOS 16, Android Pie). But considering that the battery of the F3 is 500 mAh bigger than that of the F1, this is somehow quite bad.
Now, however, I have recently received a battery dump of my old F1, with Havoc 4 (Android 11, without major optimisations). The analysis shows a significantly lower runtime and at the same time a significantly lower sum of call time and SOT as it was with Android 9. This suggests that Android itself is a major contributor to the fact that consumption has increased significantly in recent years (with the same hardware).
@Tomek0000
I had the problem that the consumption in idle mode suddenly increased massively. After each restart everything was fine, but at a certain point the consumption was like hell. Although I could never find the cause, I found a solution: I was able to prevent this by freezing most of the apps as soon as I turn off the screen (with SuperFreeze). Now the idle drain keeps low over the whole runtime.
The last run with the F3 (Havoc 4.14, NOKernel 2.3 battery, CPU underclocked, GPU undervolted):
Run time: 158 hours (about 6.5 days).
SOT: 9 hours
Phone calls: 1 hour
I have played with havoc yesterday and have results from the night. I moved my card to old x3 nfc and night lost of energy is 0.25% without freezing, down voltage or airplane mode. The havoc in F3 eats 1% of battery during each night hour and it was without using gsm card suppoort! I thought, havoc is better in this subject and additionaly has adaptive charging and wakelock blocker. No it is not better. Adaptive charging does not work and wakelock blocker blocks but not wakelocks. I did not find wakelocks on its list. I do not know what is on this list ... it is all but not wakelocks.
Ok I invested time in havoc and I will play with it some time, but card will be in x3, and ... LOS is better in the first sight.
I know, you will suggest additional apps (freezing ...) , but I will use it when I will decide which custom rom will be the best for it.
I think, I made a big mistake when I decided to buy new smartfon with snap 8xx. It should be 778 or 780. This is excelent lesson for the future.
Havoc has the same wakelock problem like LOS and it has to be result of MIUI 12.5.6.0 using as a base. Ironic ... build in wakelock blocker does not see it at all. When I will finish with Havoc I will have to use older MIUI as a base.
Let me know how you's go with this. I seem to have this same wake lock regardless of which ROM I use, losing 7-8% battery OVERNIGHT is far from normal.
I'm currently on HelluvaOS "HOS" 12 on base V12.5.6.0.RKHMIXM, as far as I recall the issue was present on older bases back from when I bought my F3 on launch.
The way to fix the wakelock is to block it. Havoc has not working wakelock block. You have to use optimus or ballam kernel. The both have working blocker. Optimus will block it but ( a supprise) ballam does not have this wakelock problem. This is my experience from time of use LOS 18.1. I tested N0Kernel 2.3 too, but it doubling energy use and does not have blocker.
Did you write, the c440000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smb5 problem exists from earlier versions of MIUI ? Is not only in 12.5.6.0 ?
Vulnerability said:
Let me know how you's go with this. I seem to have this same wake lock regardless of which ROM I use, losing 7-8% battery OVERNIGHT is far from normal.
I'm currently on HelluvaOS "HOS" 12 on base V12.5.6.0.RKHMIXM, as far as I recall the issue was present on older bases back from when I bought my F3 on launch.
Click to expand...
Click to collapse
Does this wakelock exists in earlier miui versions? Which version number has the oldest you tried?
Tomek0000 said:
I think, I made a big mistake when I decided to buy new smartfon with snap 8xx. It should be 778 or 780. This is excelent lesson for the future.
Click to expand...
Click to collapse
I totally understand!
The thing with these new Snappys is that although they might be more efficient than their predecessors, this advantage is thrown overboard by constant clocking at the limit. Unfortunately, a modern Snappy from a smaller series is not necessarily more efficient. They all seem to be maxed out...
Tomek0000 said:
I do not know what is on this list ... it is all but not wakelocks.
Click to expand...
Click to collapse
You cannot block every system/kernel wakelock because your system would break then.
Regarding a full cycle, my phone has
1.5 to 11 app wakelocks per hour
1500 to 4000 kernel wakelocks per hour
- depending on what I've done during the cycle.
The number of kernel wakelocks sounds a lot at first, but they do not necessarily mean to effect the idle drain of your phone. The cycle I mentioned above, shows 2,276 app wakelocks and 266,641 (!) kernel wakelocks in sum (runtime 158h). Both, the app wakelocks and the kernel wakelocks did wake the phone for about 2 hours each.
The exact wakelock you mentioned (c440000.qcom,spmi:qcom,[email protected]:qcom,qpnp-smb5) didn't show up on my device at all. I've installed the latest EEA firmware (12.5.8).
Did you make a clean flash with formatting all data?
I have read more and this wakelock could be connected to ACC app. If you do not control your charging process maybe you do not see this problem. I do not use ACC in havoc , but initiated adaptive charge and adaptive battery. I have to decide if I use 12.5.8 or like LOS requires 12.5.3.
Yep, I don't use adaptive charging. I charge my F3 every 4 days (in average) with 12 W. The battery is full in less than 1.5 hours. That's ok... And I always charge up to 100 %. Within the >11 months I own the F3 I charged it about 100x (84 of which are protocolled; 34 of which with a full bugreport incl, battery dump).
I don't see the benefit of smart/adaptive charging. All my previous phones lasted 5 years or more with always full charging - it never was the battery which gives up. I still use my ZUK Z1 as mp3 player (always power on, about 1h per day active usage as mp3 player) and I have to charge it once in 2-3 weeks...
So, adaptive charging doesn't work in Havoc? Then turn it off and you're rid of the wakelock!
I always use battery charge limit but it did not worked with LOS on F3. Maybe when I change kernel it will start working. I use it for keep battery in good condition for additional 25% of live time. I be voice informed by script about 30% or lower and I connect charge for all night and charge will stop when level will be 85%. And it was enough for 3-5 days of using my previous smartfons.
I reinstalled 12.5.8 and April LOS and did not install ACC. No wakelock, very good power consumption during screen off.
In my experience, exposing the battery to heat/cold and/or charging/discharging excessively quickly is much more damaging to the battery than charging it gently up to 100 % and then unplug. But, of course, if you charge your phone overnight and it's plugged for hours, it might be useful to stay below 100 %.
However, in our case (charging only once every few days), it will probably be the lack of updates/features that drives us to switch the phone...
Tomek0000 said:
I reinstalled 12.5.8 and April LOS and did not install ACC. No wakelock, very good power consumption during screen off.
Click to expand...
Click to collapse
Great. Would you mind writing here how long your phone last on one cycle?
One cycle ? I am not sure how to check it. 95% deep sleep and FKM report 0.35%/h nightly lost using LOS kernel. Previous result was ~1.8% with ACC installed.
Tomek0000 said:
Does this wakelock exists in earlier miui versions? Which version number has the oldest you tried
Click to expand...
Click to collapse
I've had the phone since day 1 and have had this idle drain issue since. The oldest I've tried is whatever shipped with the first batch of phones
Interesting. I found this wakelock in LOS if I installed Acc and in Havoc when activated adaptive charge. If I do not use it , the problem does not exist. The use of Battery Charge Limit does not activate the wakelock too.
This is very interesting like kernels work. If the wakelock was a problem, the best result was with balaam kerenl. When no problem , the balaam seems to be the worst.
esszett said:
2. Konabess: I undervolted the GPU and flashed the modified Kernel.
Click to expand...
Click to collapse
Could you share your definition file ?
I used this app and idle lost jumped 250%.
Do you use version 0.16 or older?
Tomek0000 said:
Could you share your definition file ?
I used this app and idle lost jumped 250%.
Do you use version 0.16 or older?
Click to expand...
Click to collapse
I use 0.14b... I only changed the voltages of the existing frequencies, saved and then flashed the modified kernel.
305 MHz --> MIN_SVS
400 MHz --> MIN_SVS
441 MHz --> MIN_SVS
490 MHz --> LOW_SVS_L1
525 MHz --> SVS_L0
587 MHz --> SVS_L0
670 MHz --> SVS_L2
Anyway, that doesn't affect the idle consumption at all, of course. It should only affect the SOT.
esszett said:
1. Smartpack Kernel Manager: I lowered the boost clocks of the prime core and of the 3 main cores by a few 100 MHz.
Click to expand...
Click to collapse
BTW: In the meantime I used FKM for that. But i stopped underclocking, because several tests with my phone showed me that underclocking is more or less useless. Although a significantly lower frequency was reliably applied, this did not reduce the consumption or at best minimally - but without any influence on the runtime... I now have uninstalled both Smartpack Kernel Manager and FKM.
I still only understand the consumption of the F3 to a very limited extent. While I now have the consumption in idle under control, the consumption remains very high during light and medium loads. For example, when I make calls with the F3 with LTE, the consumption is 1.5-2x as high as with the F1 with LTE. I just don't know how to lower the consumption
Thank you. I used config file from thread about optimum setting for overclock and downvoltage. It has to be not optimum solution.
Could you write your consumption during light and medium load for F1 and F3 ? (For compare possibility)
Have you ever thought about using runinbackgroundper1.5.apk ? I found it this week .
[APP][Root][7.0+]RunInBackgroundSetter v1.4 :: [25.07.2017]
Few hours ago explainAndroid posted article on xda main page onto how to use android's hidden RUN_IN_BACKGROUND permission to restrict app's background behavior. I made an app for that. Here's link to original article...
forum.xda-developers.com