Hello all
I have a bit of a small problem. I like to run my phone using the Performance Governor but after a while it goes to 1Ghz on all 4 cores despite me running it at 1.8Ghz. Setting it back seems to correct the issue but in time it goes down again.
I believe it is getting a bit warm and thus it hits a limit and the system auto slows to 1Ghz.
Can anyone confirm this behaviour? It never happened to me before but I have had a few kernel updates and updates to the Omega ROM that could be the cause but I am not sure. Is there a setting where I can tell my phone what temps to throttle at?
Also, I assume all this is down to the Kernel and not the ROMs?
Would like some imput regards where to start my search to return my phone to its previous state as a pocket heater.
Many Thanks
Syl
. I like to run my phone using the Performance Governor
Click to expand...
Click to collapse
Don't use it. Pegasusq is the only one really working for multi-core CPU's with hotplugging and so on.
but after a while it goes to 1Ghz on all 4 cores despite me running it at 1.8Ghz.
Click to expand...
Click to collapse
1.8Ghz is not healthy for the CPU in the long run and will cause overheating which is exactly what you are currently seeing.
Especially since you keep the phone on 100% CPU power all the time (performance governor) which should drain battery like hell as a side effect.
Also, I assume all this is down to the Kernel and not the ROMs?
Click to expand...
Click to collapse
This is down to your settings. Neither rom nor kernel.
- Don't overclock (much)
-Use a good kernel such as Siyah
-Undervolt if the phone remains stable
-Use pegasusq Governor
-Enjoy
d4fseeker said:
Don't use it. Pegasusq is the only one really working for multi-core CPU's with hotplugging and so on.
1.8Ghz is not healthy for the CPU in the long run and will cause overheating which is exactly what you are currently seeing.
Especially since you keep the phone on 100% CPU power all the time (performance governor) which should drain battery like hell as a side effect.
This is down to your settings. Neither rom nor kernel.
- Don't overclock (much)
-Use a good kernel such as Siyah
-Undervolt if the phone remains stable
-Use pegasusq Governor
-Enjoy
Click to expand...
Click to collapse
Hi buddy and thanks for your response.
I am not sure about what you said regarding it working correctly, it gets the best results for any benchmark compared to others so I would be interested in more detail about the specifics of how its not working correctly as I have never been told that. It would be appreciated.
I dont mind the battery drain although I do heed your warning about about longevity of the CPU.
I have been using Siyah Kernel for some time now and I find undervolting a little unstable, for now I am forced to use pegasusq.
Can you or anyone else answer the original question as I still wish to pursue this to a resolve other than not using it.
Many thanks for your time and efforts non the less!
Syl
SyLvEsTeR20007 said:
Hi buddy and thanks for your response.
I am not sure about what you said regarding it working correctly, it gets the best results for any benchmark compared to others so I would be interested in more detail about the specifics of how its not working correctly as I have never been told that. It would be appreciated.
I dont mind the battery drain although I do heed your warning about about longevity of the CPU.
I have been using Siyah Kernel for some time now and I find undervolting a little unstable, for now I am forced to use pegasusq.
Can you or anyone else answer the original question as I still wish to pursue this to a resolve other than not using it.
Many thanks for your time and efforts non the less!
Syl
Click to expand...
Click to collapse
it´s samsung´s based roms related: when the battery temp hits 41C the cpu will throttle. Nothing related with de cpu temp (can be at 80C before throttles).
try CM10.1 and you´ll see what im talking about.
We need a solution for this throttling with samsung based roms
Hello. I have been running CyanogenMod 10.1-10.2 since I got my device back in July, everything has been working great. Bugfixes have been lovely and all that good stuff; however one thing continues to annoy me. I cannot underclock my device properly. Let's say I go into the normal CyanogenMod Performance settings. Then I put my CPU to something like 1024MHz, then I see how the results went over with PerfMon from Chainfire, it will underclock only on Core 0, the rest of the cores still run up to the standard limit, 1890MHz. The only way I can somewhat successfully underclock is by setting my CPU to 594MHz or lower, at which point it will disable all cores except Core 0.
This has been annoying me for a while, I am running the standard CyanogenMod kernel, and recently I tried the Elite Kernel. The only thing the Elite Kernel did was remove the ability to disable the other 3 cores when below 594MHz. (And add the ability to go up to 2.2GHz, but who wants to overclock the Galaxy S4 yet?)
It may be worth mentioning if I try to tweak individual core settings with Tasker, on Core 0 it will let me set a CPU frequency, then if I go in and try to set something on Core 1, it won't have any of the default values for anything, and I enter them manually, then it will give me some errors about not finding the governor I said and stuff like that.
Anyone who knows any way to fix this (Custom kernels, different ROMs (Only for curiosity, I would stick to CyanogenMod anyway), etc) would be greatly appreciated.
Anyone who questions my motives for underclocking, question away. I don't like how my battery life is next to junk when I'm not even touching my phone all day, and the GS4 hardly needs the CPU it has, so I plan to use Tasker to set up a bunch of power saving mechanisms.
I suppose I do have one other question. Will underclocking even benefit me if I can't modify the voltage settings? Are they modified automatically when you're running at lower frequencies? (You would hope so, considering it's kinda a mobile device with a power source that isn't infinite). But if it won't help me without lowering my voltage (and if it isn't modified automatically) is there any good way to do that with a Tasker based setup, so it can be switched instantly whenever I do something? For example, launching a music player. All 4 cores shoot up to 1890MHz (I know they eventually settle down to lower frequencies, but for example's sake), I would rather have it so when I launched the app, Tasker would come in and set my CPU to ~800MHz with only a single core. Everything might slightly lag, but it would work and I would potentially get better battery life while listening to music.
Also, I never tested this on TouchWiz, as I didn't stay on it for more than 30 minutes after I got my device.
I am running the latest CyanogenMod nightly in case it matters (20131002, and it'll be 20131003 tomorrow unless it breaks something)
Thanks in advance to anyone who can possibly help with this. I'm sorry if the post is unorganized, but I hope it's understandable.
[bump]
Forgive me for my ignorance since I'm on ME7 and unable to flash CM10.x yet, but couldn't you just try different governors instead? On my old phone I was using lulzactive and it gave me great battery life, and you could tweak all the values any way you want for more performance or battery life.
I also remember when I experimented with undervolting and much to my dismay it turns out it made my battery life WORSE because of all the error correcting it was doing.
I get at least a days worth of moderate/heavy use on mine and with how fast it charges I don't really care about battery life but I'm curious how much actual gain you'll get for your efforts
Hello,
I'm planning going on a trip soon, and I would like to use my i9300 as my main navigation device (both on roads and out in the field). Because of that I'm looking for a rom (or rom-kernal combination) that we'll have good battery life, functioning GPS and good internet reception. So far I've tried several roms from the website (all CM based), but suffered from severe battery drain.
Can you please reccomand on a simple, battery saving rom for my purposes?
Thank you very much!!
mk010 said:
Hello,
I'm planning going on a trip soon, and I would like to use my i9300 as my main navigation device (both on roads and out in the field). Because of that I'm looking for a rom (or rom-kernal combination) that we'll have good battery life, functioning GPS and good internet reception. So far I've tried several roms from the website (all CM based), but suffered from severe battery drain.
Can you please reccomand on a simple, battery saving rom for my purposes?
Thank you very much!!
Click to expand...
Click to collapse
We can't discuss ROMs here, but with any kernel that comes with an configuration app you can change the voltage, CPU governors and I/O schedulers, enable or disable zram (obviously depending on the kernel)
On xda there's a topic that shows the differences between CPU governors. Also you can try changing it yourself. They will determinate how much battery your device will eat while active. Obs: zram can give you better memory management, compensating the lack of physical RAM but will DRAIN your battery (like seriously, without zram I have +5h on my battery - low/normal usage)
@mk010: I recommend NCS-ROM: all sensors work optimally, no surprises in unknown environment. For long battery live try (in BoefflaConfigApp) governor zzmoove /profile battery plus.
Hello folks!
This thread is intended for sharing, please be kind. Any suggestions would be appreciated
A few days ago I was tired of having my Mi3 running on stock global dev MIUI 8, it was inefficient system with really bad memory management. On my experience, the MIUI tend to run out of memory. In some case, after a few hours of usage the system cannot reclaim the occupied RAM, thus making the system lags a lot and generate excessive heat!
Yes, MIUI is a feature-rich ROM, and the Mi ecosystem is a pretty mature ecosystem. However, those all greatness needs a lot of power to run on our 3 year old device. After a few research I decided to switch to CM13 ROM.
With efficiency in mind, I do my research and tinkering with my device to get the best setup possible without losing performance. The results are AMAZING! I can use my phone for a whole day without recharge in the mid day. All of this with huge improvement on performance, Real Racing 3 highest graphic setting without any noticeable lag! CPU and battery temperature are now significantly lower (43-47C idle / light tasks, 55-57C heavy gaming). Now that I've found the best setup, I want to share it with you folks! Here we go:
Mi3W 64GB
CM13 ROM snapshot build
CM kernel (automatically flashed while flashing CM13 zip through TWRP)
Screen resolution changed to 720x1280 use this guide
Modded interactive CPU governor (see screenshot below)
Undervolt (see screenshot below, this one really helps reduce CPU working temperature)
Noop I/O scheduler
Reduce aggresiveness of LMK (see screenshot below)
Thats all folks, hope this guide will get our Mi3 having another year of flagship-grade experience! Cheers! :highfive:
How did u undervolt
kingnikpic said:
How did u undervolt
Click to expand...
Click to collapse
It depends on the kernel used. Cm kernel that he used supports undervolt. Careful when undervolting though as too much of it can cause cpu instability and reboots.
kingnikpic said:
How did u undervolt
Click to expand...
Click to collapse
Yes, it depends on the kernel used. Some kernel support undervolting while others don't. You need to flash kernel that support undervolt.
solazz said:
It depends on the kernel used. Cm kernel that he used supports undervolt. Careful when undervolting though as too much of it can cause cpu instability and reboots.
Click to expand...
Click to collapse
While testing CPU voltage value, don't tick "apply on boot" option until you find the most stable voltage without causing system reboot or crashes. Every CPU has different limit on how far you can undervolt, but you can use the values on my screenshot as guidance (Snapdragon 801 / MSM8974-AB only)
Wow!! Thanks a lot bro. I'll fiddle now with my phone.
miui8polska，i cant root it .can you give me a supersu.zip?
Sent from my MI 4LTE using XDA Labs
Random reboot after setting undervolt just likes yours
z1d4n21 said:
Random reboot after setting undervolt just likes yours
Click to expand...
Click to collapse
Undervolting (and clock adjustment, in general) pretty much is a case-per-case basis, so different handsets (even if it's the same type of device) may have different setup. Try lowering it first incrementally and test it, until you have it stable enough.
rxl.noir said:
Undervolting (and clock adjustment, in general) pretty much is a case-per-case basis, so different handsets (even if it's the same type of device) may have different setup. Try lowering it first incrementally and test it, until you have it stable enough.
Click to expand...
Click to collapse
Ok thanks i will test it later
UPDATED FOR MARCH SECURITY PATCH! 08/03/2017
Hey folks!
Today I decided to share my actual setup for everyone to try and report back.
Mind that is still WIP, absolutely far from perfect and it's based on my personal preference, since it's built around the way I use the phone. But it can be easily adopted for many people here since it's pretty flexible.
The main goal of this setup is to provide consistency, both in battery and performance. Also, I mind security a bit, this is why I update the phone often; Because of that I want to flash the least possibile .zip files in recovery after updating to the latest security image (I'm lazy and I like things done nice once, and I never do them twice when it's not needed)
With this setup you should go between 10%/h to 15%/h SOT, consistently. I've seen some of my friends dropping to 9%/h, but no guarantees
Also, added bonus: It DOESN'T trips SafetyNet, so you can use Pay and your beloved Pokemon go!
Also note that english isn't my native language, but I try my best to write as readable that I can. Sorry about that.
This require an unlocked bootloader, but not necessary a rooted phone.
The Setup:
1) First things first: Clean your phone from junk around (I suggest a pretty hard wipe) and since this require to be on the stock system (which IMO works best) flash latest N build.
2) Convert your data and cache to F2FS. It's pretty good, and even if in your opinion it doesn't boost performance THAT much, take in mind that it requires no trimming (which EXT4 does need). Mind not converting /system, this is UNSUPPORTED on stock system. It needs a custom rom.
3) Flash "Flash Kernel" from here. You can literally use any kernel you prefer, but I found this rich enough to use it. Mind it does support F2FS, if you converted to it in step 2.
4) Flash Magisk. This way you have root out-of-the-box and safetynet isn't tripped (for you Pay users!) Also, it plays nice with the mods in the next steps. Don't forget to activate "magisk hide" in the app!
5) Flash this magisk mod (increases media volume steps to 30, in call volume steps to 15)
6) Reboot your phone and set it up.
7) Install Magisk App, WakeBlock, and your kernel manager for the kernel you chose. In this setup, I use EX Kernel Manager.
8) Now, from your favourite root file manager go to /cache and create this directory structure: magisk_mount/system/framework/oat/arm64/ then place in the last folder (arm64) this file. It's from this mod, called WakeBlock. (It basically acts like amplify, but doesn't need xposed NOR root)
9) Reboot the phone.
The setup it's done, you can now tweak it as you prefer or just follow the below steps.
The Kernel tweaking:
1) Open up EX Kernel App and go to CPU, set both governors to Interactive and tick stick on reboot
2) Go to governor options and choose your governor. I use AmanuensisOne v1.0, which gives me around 6-7h sot. Load it, stick it on reboot and back to CPU.
3) Go to CPU Boost options, and disable everything (set everything to 0/disabled) and tick stick on reboot. Then back to CPU.
4) Enable core_control and disable msm_thermal, stick them on reboot.
5) Go to Memory and Disable UKSM stick on reboot.
6) Go to Miscellaneous set I/O Scheduler to FIOPS, stick on reboot, Readahead to 1024 with stick on reboot, disable fsync, also set it to reboot.
Done!
Blocking those nasty wakelocks and save the battery! (aka R.I.P. NlpCollectorWakelock):
It's reccomanded to use the phone for a while before doing this. Wakeblock collects informations on wakelocks only when they fire the first time, so a bit of use it's needed.
1) Open wakeblock app and check if it says "service bound". If it doesn't you may have missed something on the "The setup" part, check point #8.
2) Go to wakelocks and block this wakelocks (the time is expressed in ms in the app - Don't enter spaces, of course.) if you don't have a wakelock, skip it:
- NlpWakeLock -- 600 000ms
- GCoreFlp -- 600 000ms
- RILJ -- 800 000ms
- UrlDispSvcFastWL -- 600 000ms
- CMWakeLock -- 600 000ms
- *net_scheduler* -- 3 600 000ms
- Wakeful StateMachine: GeofencerStateMachine -- 600 000ms
- LocationManagerService -- 600 000ms
- SyncLoopWakeLock -- 600 000ms
- NetworkStats -- 800 000ms
- Icing -- 3 600 000 ms
- ULR_BarometerReading_WakeLock -- 600 000ms
- NfcService:mRoutingWakeLock -- 3 600 000ms
- NlpCollectorWakeLock -- 600 000ms
Take in mind that this wakelocks are blocked without impacting ANY functionality of the phone. You may want to increase the time if don't use geolocation at your own risk
More tweaks (improve smoothness and perceived UI speed):
This is a highly WIP part, setting anything different might break your system or get your phone into bootloop (happend twice to me). I highly suggest to have a backup if you want to fiddle more with these settings. You are advised. If you find something useful, please share.
1) Download HEBF and L Speed. These two apps have many tweaks to improve UX and saves a little bit more juice.
2) Open up L Speed and set it this way:
- Main tweaks: Activate Kernel sleepers optimization, Improve scrolling, Liquid smooth UI
- Battery: Activate Battery improvement
- LNET Optimizer: Activate all the tweaks and set NET Buffers to small (or big, but it wastes more battery)
- Seeder: Set to Enlarger mode
- Settings: apply on boot delay set to 60 sec.
3) Open up HEBF and set it this way:
- Set user type to "Chuck Norris" and proceed.
- Battery: Activate Google play services drain fix (Master) and usage report
4) Go into Settings > Developer options and scale all animations to 0.5x
Done, if you done all of this correctly you should see a dramatic improvement on battery life and performance.
I still reccomend to use Naptime, or better, Greenify to save some extra juice.
Have a good day, and enjoy your phone!
Please comment with your battery stats or suggestions if you wish to improve this topic.
Today's battery performance pic
Well, pretty good for me!
CappyT said:
Today's battery performance pic
Well, pretty good for me!
Click to expand...
Click to collapse
What's your average SOT?
Inviato dal mio Pixel XL utilizzando Tapatalk
giovanto98 said:
What's your average SOT?
Inviato dal mio Pixel XL utilizzando Tapatalk
Click to expand...
Click to collapse
Normally i go for 6-7h pretty consistently, i touched 8h, but it was a day were i kept my screen on pretty much all the time with really quick screen offs.
The average sot may vary, but with my friends we've tested around 6h
As you can see from the screen i've installed accubattery few hours ago, but is already almost accurate in battery reading.
I can provide more accurate averages in a week or two
CappyT said:
Normally i go for 6-7h pretty consistently, i touched 8h, but it was a day were i kept my screen on pretty much all the time with really quick screen offs.
The average sot may vary, but with my friends we've tested around 6h
As you can see from the screen i've installed accubattery few hours ago, but is already almost accurate in battery reading.
I can provide more accurate averages in a week or two
Click to expand...
Click to collapse
Why don't you use a custom rom? Any reason in particular?
DEVILOPS 007 said:
Why don't you use a custom rom? Any reason in particular?
Click to expand...
Click to collapse
Using a custom rom has for sure some advantages, but:
- It may (and possibly will) be unstable or certain features bugged out
- Doesn't provide much more than stock rom already does (and if it does, are just secondary things like looks and customization that you can live without)
- No wakeblock for it, which saves a TON of battery (i might compile it, but hell, takes a lot of time)
- You can switch Android versions easily (and mostly without wiping /data)
- Much more support (even the official one)
- The feel and look of a clean android version
- I often don't like crap integrated with other roms based on stock
- Odexed it's faster and saves a little little juice (i don't do app modding, so...)
That's pretty much why.
Take in mind that this is my thought, and doesn't universally qualify as truth.
CappyT said:
Using a custom rom has for sure some advantages, but:
- It may (and possibly will) be unstable or certain features bugged out
- Doesn't provide much more than stock rom already does (and if it does, are just secondary things like looks and customization that you can live without)
- No wakeblock for it, which saves a TON of battery (i might compile it, but hell, takes a lot of time)
- You can switch Android versions easily (and mostly without wiping /data)
- Much more support (even the official one)
- The feel and look of a clean android version
- I often don't like crap integrated with other roms based on stock
- Odexed it's faster and saves a little little juice (i don't do app modding, so...)
That's pretty much why.
Take in mind that this is my thought, and doesn't universally qualify as truth.
Click to expand...
Click to collapse
Okay thanks, I appreciate your opinion. I mainly prefer custom roms not for customisability and features but roms (mainly Chad's uber) is faster and snappier than any rom out there and is on Clang 4.0 unlike any other roms I think. Also custom roms typically have less bloat and all and has more support for themes and stuff. Can you use substratum and what wakelocks do you block? If you do ever look at getting wakeblock on custom roms could you please look into Chad's uber. I contacted him but he hasn't responded. I'd be happy to help and do it myself but I don't know how to unfortunately.
---------- Post added at 07:03 PM ---------- Previous post was at 06:58 PM ----------
CappyT said:
Using a custom rom has for sure some advantages, but:
- It may (and possibly will) be unstable or certain features bugged out
- Doesn't provide much more than stock rom already does (and if it does, are just secondary things like looks and customization that you can live without)
- No wakeblock for it, which saves a TON of battery (i might compile it, but hell, takes a lot of time)
- You can switch Android versions easily (and mostly without wiping /data)
- Much more support (even the official one)
- The feel and look of a clean android version
- I often don't like crap integrated with other roms based on stock
- Odexed it's faster and saves a little little juice (i don't do app modding, so...)
That's pretty much why.
Take in mind that this is my thought, and doesn't universally qualify as truth.
Click to expand...
Click to collapse
I was also wondering, are there any great custom roms that currently work with wakeblock? So odexed custom roms
CappyT said:
Normally i go for 6-7h pretty consistently, i touched 8h, but it was a day were i kept my screen on pretty much all the time with really quick screen offs.
The average sot may vary, but with my friends we've tested around 6h
As you can see from the screen i've installed accubattery few hours ago, but is already almost accurate in battery reading.
I can provide more accurate averages in a week or two
Click to expand...
Click to collapse
What % of battery health accubattery shows you?
Inviato dal mio Pixel XL utilizzando Tapatalk
DEVILOPS 007 said:
Okay thanks, I appreciate your opinion. I mainly prefer custom roms not for customisability and features but roms (mainly Chad's uber) is faster and snappier than any rom out there and is on Clang 4.0 unlike any other roms I think. Also custom roms typically have less bloat and all and has more support for themes and stuff. Can you use substratum and what wakelocks do you block? If you do ever look at getting wakeblock on custom roms could you please look into Chad's uber. I contacted him but he hasn't responded. I'd be happy to help and do it myself but I don't know how to unfortunately.
Click to expand...
Click to collapse
Yeah, I understand custom rom may be compiled with different toolchains to be faster, but the speed gain is between negligible and placebo, to me. The stock with these settings is buttery smooth and fast. Also, to have a faster look, go to developer settings and set all the animations to 0.5x. I know it doesn't affect performance, but the percieved smoothness is increased.
I tried many custom roms. It's mostly a fight than a good experience for me, so I gave up on it (I used to have cyanogemod on all my phones, for years and I was a big fan of it)
For WakeBlock, I don't plan to compile it for other roms, I'm just currently working on a LineageOS version, but that's it. It's up to your rom dev to integrate it.
BTW Yes, I can use substratum themes, but only in legacy mode. Keep in mind that this will OFC trigger SafetyNet. (like all substratum themes)
giovanto98 said:
What % of battery health accubattery shows you?
Inviato dal mio Pixel XL utilizzando Tapatalk
Click to expand...
Click to collapse
96%, right now.
Solid guide, similar to what i'm already doing but i use Uber as my ROM. Flash kernel is great, although for some reason i universally have a problem on my 6P where my android system usage is as high if not higher than my screen usage? Has anyone else had this issue regardless of their ROM etc? Tried multiples of combos, including stock/dark rom/Stock+ w/ different kernels. Any help would be appreciated!! Good guide none the less!
mrgenie1 said:
Solid guide, similar to what i'm already doing but i use Uber as my ROM. Flash kernel is great, although for some reason i universally have a problem on my 6P where my android system usage is as high if not higher than my screen usage? Has anyone else had this issue regardless of their ROM etc? Tried multiples of combos, including stock/dark rom/Stock+ w/ different kernels. Any help would be appreciated!! Good guide none the less!
Click to expand...
Click to collapse
Lot of users had this problem, check out the tread "nougat battery life" here on xda.
Inviato dal mio Pixel XL utilizzando Tapatalk
mrgenie1 said:
Solid guide, similar to what i'm already doing but i use Uber as my ROM. Flash kernel is great, although for some reason i universally have a problem on my 6P where my android system usage is as high if not higher than my screen usage? Has anyone else had this issue regardless of their ROM etc? Tried multiples of combos, including stock/dark rom/Stock+ w/ different kernels. Any help would be appreciated!! Good guide none the less!
Click to expand...
Click to collapse
I had a similar problem and I found out that it was my WiFi signal too low.
I used "Battery Historian" to see that.
iI's a gui that helps you find what is draining your battery giving you a graph and very detailed stats.
You can also see the wakelocks that wake your device and how much you doze in screen off.
It's located in bathist.ef.lc and it needs a bugreport from your device(to get it you need to run "bugreport > /sdcard/bugreport.txt or you can use the dedicated function into "Developer options")
SimoIanni said:
I had a similar problem and I found out that it was my WiFi signal too low.
I used "Battery Historian" to see that.
iI's a gui that helps you find what is draining your battery giving you a graph and very detailed stats.
You can also see the wakelocks that wake your device and how much you doze in screen off.
It's located in bathist.ef.lc and it needs a bugreport from your device(to get it you need to run "bugreport > /sdcard/bugreport.txt or you can use the dedicated function into "Developer options")
Click to expand...
Click to collapse
okay thanks, ill look into it! my WiFi router is right outside my room, but i still get 3 bars so maybe that's the issue.. the wifi chip's dying or something similar.
mrgenie1 said:
Solid guide, similar to what i'm already doing but i use Uber as my ROM. Flash kernel is great, although for some reason i universally have a problem on my 6P where my android system usage is as high if not higher than my screen usage? Has anyone else had this issue regardless of their ROM etc? Tried multiples of combos, including stock/dark rom/Stock+ w/ different kernels. Any help would be appreciated!! Good guide none the less!
Click to expand...
Click to collapse
It could be even ART JIT, since in 7.x apps aren't optimized at installation time, but at runtime. It may take a week to have everything ok.
Anyway thanks, the only difference I made here is the fact that I'm using wakeblock, a mod that I co-developed in the absence of xposed (and amplify)
Saves a ton of battery, so if you are wakelocking, check it out
Do you use adaptive brightness, set it manually, or what do you do?
HTC_Phone said:
Do you use adaptive brightness, set it manually, or what do you do?
Click to expand...
Click to collapse
Adaptive/automatic, the bar is set just a little before the middle
Some updates on the average battery life
CappyT said:
Some updates on the average battery life
Click to expand...
Click to collapse
Would you recommend using ForceDoze in place of Greenify/L Speed/NapTime?
I know ForceDoze works better with 6.0 since with stock Doze, it only works when the device is at a still position for at least 30 mins and ForceDoze has the ability to alleviate that, letting the device set into Doze mode regardless how much the device moves around, but with 7.0/7.1+, its like an improved Doze v2. So...
explorer-10 said:
Would you recommend using ForceDoze in place of Greenify/L Speed/NapTime?
Click to expand...
Click to collapse
I personally use greenify and l speed for some additional tweaks.
Take in mind that you can use whatever you feel it's right, depending on your needs (greenify for example is selective, while the others aren't)
Anyway all of these will provide only a little bit of reduction of screen off drain, so the difference (for me, at least) it's pretty negligible.
The real deal in screen off performance is limiting the wakelocks, this way you can doze a lot more.