Hi,
I have tried different rom + kernel:
cleanrom
ultra fast rom: http://forum.xda-developers.com/showthread.php?t=1901784
untermensch kernel: http://forum.xda-developers.com/showthread.php?t=1892326
and still can't oc the cpu to something higher than 1.3ghz
I used the No-frills CPU as well as the antutu cpu master (free version)
for the No-frills cpu, whenever I set the CPU speed to something high (ie. 1.6ghz max and 102mhz min), checked apply on root then apply, it worked fine for a while, but later on when I open no-frills cpu, th e current max and min will reset back to 1.3ghz and 102mhz.
Governor and I/O scheduler is fine though.
Sounds to me like u need to check start on boot..i havent oveclocked mine yet but option should be there where u select governors and such...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Of course i have checked that it just didnt work
Give Voltage Control a try. It gives you the options to apply on boot or init.d. I use the init.d setting because the phone boots quicker. I had that problem with CPU Master in the past while running it on my phone.
Sent from my LG-LG855 using Xparent Green Tapatalk 2
Will do, however i dont think it's the reboot problem. The problem was, when i set the cpu speed to 1.5 or 1.6 its works fine for an hour or so ( i closed the cpu app, reopen it and the curent seed got set) but then an hour or so, it got resetted back to 1.3 without rebooting the device
redjersey said:
Will do, however i dont think it's the reboot problem. The problem was, when i set the cpu speed to 1.5 or 1.6 its works fine for an hour or so ( i closed the cpu app, reopen it and the curent seed got set) but then an hour or so, it got resetted back to 1.3 without rebooting the device
Click to expand...
Click to collapse
Hi !
Overclock automatically deactivates when the device enters in standby !
surdu_petru said:
Hi !
Overclock automatically deactivates when the device enters in standby !
Click to expand...
Click to collapse
Ahh, that's what I thought was going on, this is happening to me as well.
treo4life said:
Ahh, that's what I thought was going on, this is happening to me as well.
Click to expand...
Click to collapse
Hi!
No, this happens to everyone
However, it seems a pretty good thing - why we need OC - if the device sleep ? :laugh:
- it is also good for battery - !
So i will have to reoverclock it everytime ??
Mine doesn't do this at all. I use CleanROM 3.1, unters kernel and setcpu. No issues.
I guess I know why it's because setcpu has the profile settings allows u to set the CPU speed when screen is on / when screen is unlocked
Othe CPU apps I have tried have no such feature which means oc works when u set it, but when u turn off the screen then turn it on , it will reset back to 1.3ghz
Using setcpu, what I did was set a "screen off" profile to max out at 1700ghz when the screen is off or in sleep mode and it worked for me!!! That way will not default back to stock 1300ghz everytime I hit screen off or sleep mode.
Related
Since we've had root I have been running tiamat and using setcpu to overclock to 1500 and its been working great.
After the 3.2 upgrade to 2.6.36.4Tiamat_Xoom-V2.0.0 for 3.2, SetCPU has a habit of going to 216MHz even thought its set for 1500. If I open setcpu it says 216 but if I simply click on the Max bar it jumps back to 1500.
I have had setcpu on Performance and Interactive - Both do the same. It may keep 1500 for a few hours or only an hour - then the system gets slow due to the 216MHz clock....
Any ideas?
Never heard of such an issue on the Xoom until now...
Common sense I know, but... make sure you don't have any profiles set up to cause this. That is the only thing I can think of. Ex: It's set to clock to the lowest speed while AC charging, etc.
If all else fails... wiping data is your best friend to fix strange problems while flashing custom Roms. Back up all of your apps with their data via Titanium Backup, then wipe data, wipe cache, wipe dalvik cache, then restore all apps with data, but do not restore any system data or system apps. That's the best thing you can do, if you do not do this... you may experience problems like so. I've had strange issues before and doing this fixed it all up no problem.
PensFan66 said:
Since we've had root I have been running tiamat and using setcpu to overclock to 1500 and its been working great.
After the 3.2 upgrade to 2.6.36.4Tiamat_Xoom-V2.0.0 for 3.2, SetCPU has a habit of going to 216MHz even thought its set for 1500. If I open setcpu it says 216 but if I simply click on the Max bar it jumps back to 1500.
I have had setcpu on Performance and Interactive - Both do the same. It may keep 1500 for a few hours or only an hour - then the system gets slow due to the 216MHz clock....
Any ideas?
Click to expand...
Click to collapse
You can set the lowest speed higher. Use interactive and don't set on boot unless you are really sure that it's stable.
Speaking about SetCPU, on phones, there is the menu button which you can click but it doesn't seem to appear on the Xoom which basically allows you to autodetect speeds, are you guys able to access that other than only on the first launch of setcpu after installed?
Almighty1 said:
Speaking about SetCPU, on phones, there is the menu button which you can click but it doesn't seem to appear on the Xoom which basically allows you to autodetect speeds, are you guys able to access that other than only on the first launch of setcpu after installed?
Click to expand...
Click to collapse
I think it only works the first time on the Xoom.
okantomi said:
I think it only works the first time on the Xoom.
Click to expand...
Click to collapse
setcpu never worked right for me. use no-frills cpu.
Hi all,
I've got a problem with System Tuner. On every ICS ROM I try the CPU clock and voltage settings won't stick. After I reboot the phone they go back to their defaults. Hence, I've got 3 questions:
1. Does everyone have these problems? Did I not check a setting or something?
2. What alternatives to System Tuner don't turn the second CPU core permanetly on?
And 3. Is there an init.d script which lets you set the clock speeds/voltage settings? Because I would rather not use an app at all to do that.
Set your CPU clock and voltages, then press Boot settings on the cpu tab( small button ), press Re-apply CPU Settings -> On boot completed.
ccs16rocks said:
Set your CPU clock and voltages, then press Boot settings on the cpu tab( small button ), press Re-apply CPU Settings -> On boot completed.
Click to expand...
Click to collapse
Yes I did that, but the minimum frequency doesn't stick.
Nobody?
I'm using No-frills atm, but does that turn CPU1 permanently on?
-editedpost-
V1k70r said:
Yes I did that, but the minimum frequency doesn't stick.
Click to expand...
Click to collapse
My setup is similar to yours except I'm on ARHD 6.5.3.
I can confirm it is changing back to 192Mhz min. Could be kernel related as I'm on bricked 3.0 v5 too. Maybe we should ask showp-1984 or it cold be related to System Tuner.
Did you have tried another software like setCPU?
yasobaso said:
My setup is similar to yours except I'm on ARHD 6.5.3.
I can confirm it is changing back to 192Mhz min. Could be kernel related as I'm on bricked 3.0 v5 too. Maybe we should ask showp-1984 or it cold be related to System Tuner.
Did you have tried another software like setCPU?
Click to expand...
Click to collapse
Hi there I'm on same Rom but with serbas ken and I use system tuner pro and mine sticks even after reboot, on a off chance do you have oc demon disabled in boot settings
Sent from my ARHD ICS powered senny
boroboy69r said:
Hi there I'm on same Rom but with serbas ken and I use system tuner pro and mine sticks even after reboot, on a off chance do you have oc demon disabled in boot settings
Sent from my ARHD ICS powered senny
Click to expand...
Click to collapse
Could you be more detailed Do you mean " Re-Apply CPU settings" if so yes I had it enabled. I will reflash stock o any other kernel and check if it's going to solve this.
I also have this problem with system tuner pro, now i'm using setcpu and the settings stick.
using vipers 1.1.0, tried anthrax/bricked/faux123 all didn't stick.
You know you.could ask the dev of super tuner. He's always very responsive anytime I've had issues. Also having different versions backed up in Ti helps as well cause a new update fixes one thing from a slew of phones but might just break yours. Having a backup versions means you can go back restore and test.
Casperi.
Sent from my SGH-T989 using xda premium
In relation to your second question, what kernel are you using? Faux's kernel has the second core on by default. System tuner doesn't have the ability to turn it off. If you want it offline until it's needed, try seb's or bricked kernels instead.
System Tuner 3.0
Just to let you know System Tuner 3.0 was released some time ago and provides improved CPU handling, new GPU, Gamma, MP, thermal controls on many custom kernels and a lot of other new or improved features (entropy, fstrim to name a few).
This is now a spawn of Android Tuner, and benefits from a larger user-base, improved stability and performance.
It now has the ability to turn on/off CPU cores, with a dedicated screen-off option. Only if custom kernel allows it though.
V18.1 Available
Share to all of You my little program
Features:
- CPU governor switch on the fly
- Fix for MTK6577 bug when 2nd core keep sleeping after screen unlock
Available governors:
- hybrid (default) - 2nd core starts then 1st is 100% loaded, max freq=1001Mhz
- ondemand - both cores work together, more time on freqs between 250-1001Mhz
- powersave - both cores work on 250Mhz
- super powersave - only one core, works on 250Mhz
- perfomance - both cores always run on 1001Mhz
- userspace fixed - fixed freq for both cores, no scaling
- userspace scaling- upper scaling freq thresholds is calculating on CPU load - in this mode, app runs 01processor.sh script from bumbon4ik
- visualization - upper line - cpu frequency, 1001mhz = full screen width, 250mhz = 25% etc. below - both cores, 100% load = current frequency line width. for ex. - fixed 500mhz and 100% both cores load will show three lines on half a screen
:good:
IMPORTANT.
On some phones & ROMs v18.1 may freeze the phone.
To delete app install this update from recovery - v18.1_recovery_uninstall.zip.
Its code:
Code:
mount("ext4", "EMMC", "data", "/data");
delete("/data/app/MTK6577_governor_switcher_v18.1.apk");
unmount("/data");
So it delete only apk in data partition, to remove apps data You have remove folder data/data/MTK6577_governor_switcher_v18.1 and the same MTK6577_governor_switcher_v18.1.odex from dalvik-cache manually.
michfood said:
Share to all of You my little program
Features:
- CPU governor switch on the fly
- Fix for MTK6577 bug when 2nd core keep sleeping after screen unlock in ondemand mode
Available governors:
- hybrid (default) - 2nd core starts then 1st is 100% loaded, max freq=1001Mhz
- ondemand - both cores work together, more time on freqs between 250-1001Mhz
- powersave - both cores work on 250Mhz
- perfomance - both cores always run on 1001Mhz
- userspace - don`t know
Click to expand...
Click to collapse
Thanks michfood :good:
I will give this a try on my zopo zp300+ because the power drain on the phone is very bad so I hope this can sort out those cpu's :fingers-crossed:
Do we have to reboot to switch between the different mode's ie: switching from hybrid to on demand will this require a reboot?
Also I assume I must disable/un-install any other cpu controllers such as set-cpu
no need to reboot.
you can see current governor and cpu freq in such programs as CpuSpy, SystemPanel, CoolTool and others.
about other CPU controlling soft - yes, it`s better to use only one thing.
so AFAIK setcpu do not work properly because of that ondemand bag - after screenunlock only one core works.
it can be shown for ex. in SystemPanel or MicroCpuMonitor
michfood said:
no need to reboot.
you can see current governor and cpu freq in such programs as CpuSpy, SystemPanel, CoolTool and others.
about other CPU controlling soft - yes, it`s better to use only one thing.
so AFAIK setcpu do not work properly because of that ondemand bag - after screenunlock only one core works.
it can be shown for ex. in SystemPanel or MicroCpuMonitor
Click to expand...
Click to collapse
Thanks for the advice michfood :highfive:
You are correct about setcpu I made changes with setcpu but did not see any big improvements only slight improvements :crying:
I am installing your APK now and I will report back after a couple of days use :good:
Keep up the great work michfood it's really appreciated buddy
Thanks for this app! I will give it a try and see what it can do
michfood said:
Share to all of You my little program
Features:
- CPU governor switch on the fly
- Fix for MTK6577 bug when 2nd core keep sleeping after screen unlock in ondemand mode
Available governors:
- hybrid (default) - 2nd core starts then 1st is 100% loaded, max freq=1001Mhz
- ondemand - both cores work together, more time on freqs between 250-1001Mhz
- powersave - both cores work on 250Mhz
- perfomance - both cores always run on 1001Mhz
- userspace - don`t know
ATTENTION!! - found an interesting bug:
- after performance governor CPU keeps running on 1001Mhz, solved in v2 - there is ALWAYS NEEDED to switch hybrid and after that - to other governor.
please - reload
Click to expand...
Click to collapse
I installed this on my Micromax A89, after keypad unlock, governor is changing back to hybrid automatically.
hafeezluqman said:
I installed this on my Micromax A89, after keypad unlock, governor is changing back to hybrid automatically.
Click to expand...
Click to collapse
ufffff... yes - You are right.... another problem... but it seems it do not get back to hybrid (as for my phone) - it only keeps 1001 running
AW: MTK6577 CPU Governor Switcher
hafeezluqman said:
I installed this on my Micromax A89, after keypad unlock, governor is changing back to hybrid automatically.
Click to expand...
Click to collapse
Same issue here!
michfood said:
ufffff... yes - You are right.... another problem... but it seems it do not get back to hybrid (as for my phone) - it only keeps 1001 running
Click to expand...
Click to collapse
Ya it's changing back to hybrid after screen locks. If possible please correct this problem.
michfood said:
ufffff... yes - You are right.... another problem... but it seems it do not get back to hybrid (as for my phone) - it only keeps 1001 running
Click to expand...
Click to collapse
I also tried CPU Sleeper Dual Core from play market. But heating problem still exist. Is it the problem of kernel ?
without checked "2nd core activation" it stays on "ondemand"....
try it!
kra_ppo said:
without checked "2nd core activation" it stays on "ondemand"....
try it!
Click to expand...
Click to collapse
We want 2nd core activation. Unticking it, is waste.
michfood said:
ufffff... yes - You are right.... another problem... but it seems it do not get back to hybrid (as for my phone) - it only keeps 1001 running
Click to expand...
Click to collapse
Hi michfood,
No Problems on the zopo zp350+ mtk6577 michfood it work's great at the moment. :victory:
I did have a little problem at first I think caused by installing cpu spy after I installed your app.
Try to Install cpu spy first then install your app it worked for me. My setting's now hold no problem. :good:
Hope this helps:fingers-crossed:
Regards bigrammy
V3 issued - tried to fix bugs.
Please reload.
Seems works fine, please test it.
PS - with Fix_on option, after screen unlock 2nd core ALWAYS awakes from sleeping, in ALL governors. It is really needed only for "ondemand", but I think it`s not bad for others. And may be we should asleep 2core in "powersave" mode to achieve min battery drain?
michfood said:
V3 issued - tried to fix bugs.
Please reload.
Seems works fine, please test it.
PS - with Fix_on option, after screen unlock 2nd core ALWAYS awakes from sleeping, in ALL governors. It is really needed only for "ondemand", but I think it`s not bad for others. And may be we should asleep 2core in "powersave" mode to achieve min battery drain?
Click to expand...
Click to collapse
Bug fixed : Governor is not reverting back to hybrid after screen unlock or reboot. I will reply after 2-3 hours about overheating.
I am using it on Ondemand governor. After 1 hour of temple run 2 gameplay with mp3 playing in background, Heat is 20% less on my device. Battery came down from 50% to 24%. It means 26% drained in 1hour gameplay.
is it good?
Sent from my JY-G3 using xda app-developers app
It is good. Without this app, the 2nd core will sleep after screen unlock. So this app is a must have. Is there any app, which shows the load of 2 core seperately, like task manager of windows 7.
yes it's Micro Cpu Monitor.
it doesn't show frequency, but only load
Sent from my JY-G3 using xda app-developers app
guys - have a good news, SetCPU 3.0.9 seems to work properly with our ondemand mode and 2nd core! :good:
so I guess there is no need to go on with my app - SetCPU is quit enough
Hello everyone.
I have rooted my tab 2 (model: P5110 running official android 4.1.2)
I recently installed the setCPU and tried to create some profiles
for example: working in 1008 mhz in performance mode while charging
However, after I screen off, it would be powered off automatically and I have to long press the power button to power on again.:crying:
I guess that it is not about the profile I set but the setCPU crashed in Tab2.
Is there any method to solve the problem or cannot not use the setCPU?
Thanks a lot !
I am guessing you are using stock kernel as well?
You will need to install a custom kernel that will allow you to overclock to use SetCPU.
With stock kernel, you don't have an option of changing CPU clock speed. I don't know if that is why you are having problems.
Yes, I am using the stock kernel.
I am not going to overclock my tab2 to 1.2Ghz or even higher
but I just want to increase the minimum clock speed since tab 2 is very lag.
For example running at full speed while you are charging the tab
install android tweaker from play store for better perfomance
It's known problem. I called it, sleep too deep. Do not play around with the CPU governor if you are using stock kernel.
Yes, you will need a custom kernel before you can mess around with CPU settings.
i have the 1689mhz bug!!! at random time the MIN freq of the cpu is stuck at 1689mhz andthe max still at 2ghz. ( you can activate on developer options the "show cpu info" toggle)
i cannot change the min value from kernel adiutor, i click on 652mhz but nothing changes, only a REBOOT actually fix the min freq used.
i thought it was a problem of my custom rom resurrection 5.8.3 or the fact i am using kernel adiutor, in fact this app does randomly give CPU LOAD BUG on several devices i mod! sometimes kernel adiutor load my cpu cores at 100% also on light load, but just forceclosing the app the cores return to lower freq.
but the 1689mhz bug is a KERNEL BUG, i read about this bug also on people with stock rom, and the p2a42 phone.... and i have p2c72 hardware phone!!! so this kernel BUG is found in EVERY VERSION of this phone.
please developers, we need a modded kernel that fixes this bug, and why not.......... new i/o schedulers and governors.... and maybe a little undervolt for every cpu freq
realista87 said:
i have the 1689mhz bug!!! at random time the MIN freq of the cpu is stuck at 1689mhz andthe max still at 2ghz. ( you can activate on developer options the "show cpu info" toggle)
i cannot change the min value from kernel adiutor, i click on 652mhz but nothing changes, only a REBOOT actually fix the min freq used.
i thought it was a problem of my custom rom resurrection 5.8.3 or the fact i am using kernel adiutor, in fact this app does randomly give CPU LOAD BUG on several devices i mod! sometimes kernel adiutor load my cpu cores at 100% also on light load, but just forceclosing the app the cores return to lower freq.
but the 1689mhz bug is a KERNEL BUG, i read about this bug also on people with stock rom, and the p2a42 phone.... and i have p2c72 hardware phone!!! so this kernel BUG is found in EVERY VERSION of this phone.
please developers, we need a modded kernel that fixes this bug, and why not.......... new i/o schedulers and governors.... and maybe a little undervolt for every cpu freq
Click to expand...
Click to collapse
Haha! Have very less hopes,bcoz some feel that custom kernels are not at all needed! They think that a device wid 2ghz processor doesn't need custom kernel
And btw the post topic is 100% right,bt the place where it's posted is wrong! This should be under discussion section
realista87 said:
i have the 1689mhz bug!!! at random time the MIN freq of the cpu is stuck at 1689mhz andthe max still at 2ghz. ( you can activate on developer options the "show cpu info" toggle)
i cannot change the min value from kernel adiutor, i click on 652mhz but nothing changes, only a REBOOT actually fix the min freq used.
Click to expand...
Click to collapse
Yes, thats true. The bug is i think VDD related. Sometimes the VDD switches automatically on, the min CPU freq goes up to 1689 MHz, and can not be lowered until you don't switch off the VDD. You can switch off in Kernel Adiutor/Thermal section, or use the following command :
echo '0' > /sys/module/msm_thermal/vdd_restriction/enabled
I use the KSLABS Schedule! app to run the command every 5 minutes.
I hope this will help you, until we get one bugfree kernel.
u are right
now the bug is MORE AGGRESSIVE THAN EVER............ i rebooted, i attachedthe phone to a charger, arrived 100%, then rest for 1h30min on idle(deep sleep) but when i started using the phone... i checked the frequencies and BOOM....... another time the bug of 1689mhz!!! the battery was 100%......
maybe there is an app that causes this... but which one?
realista87 said:
maybe there is an app that causes this... but which one?
Click to expand...
Click to collapse
Which ROM do you use?
I have stock 244, but the method worked for me in 233 too. In the past, I used the Magisk Crossbreeder Lite module to eliminate this problem, but the latest (1.6+) versions made the phone very slow, especially booting.
Vis77 said:
Yes, thats true. The bug is i think VDD related. Sometimes the VDD switches automatically on, the min CPU freq goes up to 1689 MHz, and can not be lowered until you don't switch off the VDD. You can switch off in Kernel Adiutor/Thermal section, or use the following command :
echo '0' > /sys/module/msm_thermal/vdd_restriction/enabled
I use the KSLABS Schedule! app to run the command every 5 minutes.
I hope this will help you, until we get one bugfree kernel.
Click to expand...
Click to collapse
can you help me with the console command... but with macrodroid? i don't use that app
edit_ i setted your app, ibut i prefer every 1h to toggle VDD off
realista87 said:
u are right
now the bug is MORE AGGRESSIVE THAN EVER............ i rebooted, i attachedthe phone to a charger, arrived 100%, then rest for 1h30min on idle(deep sleep) but when i started using the phone... i checked the frequencies and BOOM....... another time the bug of 1689mhz!!! the battery was 100%......
maybe there is an app that causes this... but which one?
Click to expand...
Click to collapse
Maybe the Kernel adiutor itself cause the high load, as background task make 28-30% cpu load, see the attachment.
But, the 1689 MHz bug still exist. :-\
Vis77 said:
Maybe the Kernel adiutor itself cause the high load, as background task make 28-30% cpu load, see the attachment.
But, the 1689 MHz bug still exist. :-\
Click to expand...
Click to collapse
what app do you use to see the % of cpu for each thread?
i don't think that the cause is kernel adiutor... i repeat, a lot of people with 100% stock rom have this bug.....
hey vis could you help me with the string of the scheduler app? i don't understand how to set every 1 hour my previous screenshot i think is wrong because it does not work every 1 h
sorry but the "cron expression" is too much difficult to me to understand.....
EDIT i found how to do every 1h!! 0 0 0/1 1/1 * ? *
thanks to this site!!! http://www.cronmaker.com/
realista87 said:
what app do you use to see the % of cpu for each thread?
i don't think that the cause is kernel adiutor... i repeat, a lot of people with 100% stock rom have this bug.....
[/B]
Click to expand...
Click to collapse
The app name is 3C Toolbox Pro.
Yes the bug is still here, Kernel Adiutor is only different problem.
After reading all your discussion.. I understood that one of you knew solution to stop the bug ,and the other guy learnt how to do it ..
But I don't get a single thing ,what and how you solved that bug
Note : I don't even know that 1698 bug is present , all I know is cpu idle is consuming more power ..
Is this the same thing you guys were discussing?
If yes ..how can a I solve it ? Any walkthrough?for dumb minds like me ...?
nandakis4 said:
After reading all your discussion.. I understood that one of you knew solution to stop the bug ,and the other guy learnt how to do it ..
But I don't get a single thing ,what and how you solved that bug
Note : I don't even know that 1698 bug is present , all I know is cpu idle is consuming more power ..
Is this the same thing you guys were discussing?
If yes ..how can a I solve it ? Any walkthrough?for dumb minds like me ...
Click to expand...
Click to collapse
I've made the following observations:
On a fresh install(stock or custom rom(i have not tried Firelord versions)), rooted phone(with Magisk or SuperSU), if you install the Kernel Adiutor, and go to Thermal section the VDD restriction by default is OFF. You can change freely the CPU minimum frequency.
After some hours/days(total random) something switch ON the VDD restriction, the CPU minimun frequency going up to 1698 MHz, and unable to set back the default 652 MHz. If you switch off the screen the cores going to deep sleep, but if you switch on the screen the min. freq. is still 1698 MHZ.
If you manually switch OFF the VDD restriction, the CPU working normal, until switched ON automatically again.
If your phone is not rooted, the only thing what you can notice that the battery is dropping faster than usual, or the phone a bit warmer.
The problem still occurs even if you do not have a program that you can turn on/off the VDD.
The above solution does not repair the problem, it only remedies the symptoms...
I sometimes notice that even though I don't use it, "Google Play Services" consume an unusual amount of battery and will continue to do so unless I reboot the phone. I have never investigated the cause. Might this be related to the 1698MHz bug ?
medwatt said:
I sometimes notice that even though I don't use it, "Google Play Services" consume an unusual amount of battery and will continue to do so unless I reboot the phone. I have never investigated the cause. Might this be related to the 1698MHz bug ?
Click to expand...
Click to collapse
I do not think so, but check the status of VDD when you have rooted phone. Sometimes I have too huge battery usage caused by the Google Play Services, but i would suspect first of the Location services. If I use some sport tracker, or navigation app then growing for me the Google Play Services consumption.
Vis77 said:
I do not think so, but check the status of VDD when you have rooted phone. Sometimes I have too huge battery usage caused by the Google Play Services, but i would suspect first of the Location services. If I use some sport tracker, or navigation app then growing for me the Google Play Services consumption.
Click to expand...
Click to collapse
My phone is rooted. I will start monitoring VDD. FYI, I don't use any google app (Gmail, Play Store, Maps, etc ...). Location services is also turned off. Sometimes, out of nowhere, I'd see Google Play Services at the top of the battery consumption details. Yesterday, it had a very high CPU consumption time of around 1h (prevented the phone from going to sleep; had 3000+ wakelocks). I had to reboot the phone to get it to stop eating my battery. Usually, Google Play Services use the CPU for a total of 10min on a full charge.
medwatt said:
My phone is rooted. I will start monitoring VDD. FYI, I don't use any google app (Gmail, Play Store, Maps, etc ...). Location services is also turned off. Sometimes, out of nowhere, I'd see Google Play Services at the top of the battery consumption details. Yesterday, it had a very high CPU consumption time of around 1h (prevented the phone from going to sleep; had 3000+ wakelocks). I had to reboot the phone to get it to stop eating my battery. Usually, Google Play Services use the CPU for a total of 10min on a full charge.
Click to expand...
Click to collapse
If you don't use it, you can remove what is mentioned on the MicroG Prerequisites page[0].
Some apps nag about it but the only noticable problem I have is messenger lite notifications don't go automaticaly away after replying. Even my banking app keeps working.
[0]https://github.com/microg/android_packages_apps_GmsCore/wiki/Prerequisites