I froze all of the DRM services as shown in the picture below, yet it is still hogging battery resources as shown below.
Does anyone know how this is possible and how to fix this?
I'm using SleeperRom 1.0.11 and Shadow Kernel 1.03+.
Thanks.
That doesn't help. Percentages don't mean anything. ALL your applications have to run through android system. Take off android from your phone and you can't run anything. To see what is using your battery check Betterbatterystats. What files have the most time on them? Check processes and partial wakes if your battery drains while your phone is in standby. Also get CPUSpy and make sure your phone goes into deep sleep when in standby and not on charge.
Just because it lists DRM in the android system does not mean it is using more than a second or two of quick checking services. This is why some apps screw up if it is removed instead of just frozen. It has to check if the files are still on your phone.
Thanks, i'll try that app. I assumed that since it was at the top, it was using the most. Since updating to SleeperRom 1.0.11 and Shadow Kernel 1.03+, my battery does not seem to be as good even though I have not changed the way I use my phone. This is why I was investigating.
after checking betterbatterystats, I don't even see the DRM service anywhere within the app, so I guess that is good.
I guess my phone just doesn't agree with the update to sleeper 1.0.11 and shadow 1.03+
akuentzler said:
Thanks, i'll try that app. I assumed that since it was at the top, it was using the most. Since updating to SleeperRom 1.0.11 and Shadow Kernel 1.03+, my battery does not seem to be as good even though I have not changed the way I use my phone. This is why I was investigating.
Click to expand...
Click to collapse
I have not tried that combo but is there a default overclocking setting? I tried SleeperROM before and it defaulted to 1100 Mhz overclock. If you came from a ROM with no OC set then that would explain it.
kennyglass123 said:
I have not tried that combo but is there a default overclocking setting? I tried SleeperROM before and it defaulted to 1100 Mhz overclock. If you came from a ROM with no OC set then that would explain it.
Click to expand...
Click to collapse
I usually don't touch the overclock settings and I always to do clean wipe when installing my roms, so whatever is default should stay.
voltage control is set to conservative, min 100, max 1000 Mhz.
akuentzler said:
I usually don't touch the overclock settings and I always to do clean wipe when installing my roms, so whatever is default should stay.
voltage control is set to conservative, min 100, max 1000 Mhz.
Click to expand...
Click to collapse
If you set that as apply on boot after the wipes if you mean data wipe, and install then it should be 1000 max. Easiest way is just check CPUspy. Have you changed brightness on your display? Did the ROM add any apps like Gtalk with video that you didn't have before that may need to be frozen? Definitely get Betterbatterystats and check what's running.
kennyglass123 said:
If you set that as apply on boot after the wipes if you mean data wipe, and install then it should be 1000 max. Easiest way is just check CPUspy. Have you changed brightness on your display? Did the ROM add any apps like Gtalk with video that you didn't have before that may need to be frozen? Definitely get Betterbatterystats and check what's running.
Click to expand...
Click to collapse
I think the major difference is the shadow kernel and the use of voodoo color. I was previously on samurai 2.0.6 or 2.0.8 i think.
I have always had auto brightness on. Betterbatterystats did not reveal anything out of the ordinary.
I guess i'll just try a new rom/kernel combo and see if I can get better results. Thanks for your help Kenny. Betterbatterystats is a nice tool i had not known about.
No problem. I did find that voodoo color and the voodoo control app use a little extra battery plus having to increase brightness a little with voodoo color used up a little more battery.
Sent from my SPH-D700 using XDA App
Related
So I'm running baked snack here and really beginning to enjoy it and this whole root thing. I've installed setcpu but every time I back out of the interface it goes down to 691 no matter how high I set it or on any profile. Does this not work with baked snack? Am I overlooking something or did I set it up wrong(I used auto detect when I started)?
Did you flash a different kernal?
Sent from my PC36100 using XDA App
Nope I flashed kernel 3 I think or what ever came included in the baked snack.
should I DL that kernel by itself and then flash over the Baked snack with it? and whats the difference between flash over and flash ontop of?
Damn the stupidity of it all... lol. I set my profile to 691 if my battery was under 40% which it was... but now when I plug my phone in the cpu goes up to 1ghz which I have it set to but my battery keeps going down. Now this is a problem here if I'm not able to charge my phone while the setcpu is running it will get really annoying really fast. Considering the app manager that I have refuses to close it so I have to manually go to settings > applications > manage applications then go to setcup and force close it to charge my phone it seems. Do you guys think its a problem with my cpu being set to high while charging should I drop it down a whole bunch for the charge process too? That doesn't seem like a very needed thing to do I would assume it would be able to charge just fine without that. Looks like I got a lot to learn about this whole rooted phone thing.
Check your profiles in setcpu and make sure you don't have one that's at that speed with the highest priority. If that all checks out fine I would flash kernal 2 (my favorite) don't wipe just flash. And as for your question over or on top they mean the same thing and that's flashing the kernal without wiping.
Sent from my PC36100 using XDA App
Also do you have overclock widget running as well? If so they might be fighting eachother
Sent from my PC36100 using XDA App
not even quite sure where the overclock widget is. I looked to see if setcpu had a widget and it wasn't in the widget menu. Where as most of my other installed apps have a widget assossiated with them. I'll look into kernel #2 right now, I still have some more flashing to do.
crimeslunk said:
not even quite sure where the overclock widget is. I looked to see if setcpu had a widget and it wasn't in the widget menu. Where as most of my other installed apps have a widget assossiated with them. I'll look into kernel #2 right now, I still have some more flashing to do.
Click to expand...
Click to collapse
Overclock widget is just another widget you can download that runs seperatly from SetCPU. You should have a SetCPU widget though. I would try reinstalling SetCPU also
I need educated on a few things, I'm concerned with the performance of my phone so I have it rooted and I have installed system panel to monitor things, autokill memory optimizer for ram of course as well as watchdog to alert me if any apps are outta control. Am I crazy for having these or is it a good idea? Also is there anything better I should use rather then what I already have? I just want my phone to run smooth and my battery to last bc I use my phone all day long
Sent from my ADR6300 using XDA App
trembly01 said:
I need educated on a few things, I'm concerned with the performance of my phone so I have it rooted and I have installed system panel to monitor things, autokill memory optimizer for ram of course as well as watchdog to alert me if any apps are outta control. Am I crazy for having these or is it a good idea? Also is there anything better I should use rather then what I already have? I just want my phone to run smooth and my battery to last bc I use my phone all day long
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
A lot of that is unneeded. I have System Panel, but only use it if I'm having problems with an app. Rarely is there a use for watchdog. On stable ROMs, I've never seen an app get out of control, and rarely on betas. So it justs sits in the background eating battery itself. Also try, using a stock speed, undervolted battery with SetCPU. If I'm trying to make mine last, I have a screen off profile of powersave 384/245, and regular of 700-800ish (I forget)/245 conservative.
PonsAsinorem said:
A lot of that is unneeded. I have System Panel, but only use it if I'm having problems with an app. Rarely is there a use for watchdog. On stable ROMs, I've never seen an app get out of control, and rarely on betas. So it justs sits in the background eating battery itself. Also try, using a stock speed, undervolted battery with SetCPU. If I'm trying to make mine last, I have a screen off profile of powersave 384/245, and regular of 700-800ish (I forget)/245 conservative.
Click to expand...
Click to collapse
ok thanks, i installed setcpu and have two profiles set, one for when screen is off with settings similar to yours and another set to when my battery is >30%. could you please tell me what the governor options of on demand, userspace, or performance mean ?? also should i set priority's to anything other then the default 50 % ? thanks for the help
I finally got srf 1.2 to work really good. I have a few questions about voltage control.
1. Is it safe to overclock and undervolt?
2. What advantages will I see from undervolting, longer battery life?
3. Does overclocking really make that much difference, and is it safe?
4. Is there a how to, or a guide that can show me how to do it?
Thanks
Yes its safe just don't use the set on boot feature. As for battery improvement some people notice a difference and others don't I personally do undervolt. As for the guide just mess around with it for a while everyone Has different Preferences so results will always be different. I don't undervolt below 75 cause when I do I get lock ups. If you lock up just pull the battery and you'll be fine. I also recommend to use journaling ON cause if you lock up and pull the battery with journaling off you might get data corruption.
Hope this helps.
Sent from my SPH-D700 using XDA App
Yeah that helped but I really just don't know how to use it.
Led4lyf said:
I finally got srf 1.2 to work really good. I have a few questions about voltage control.
1. Is it safe to overclock and undervolt?
2. What advantages will I see from undervolting, longer battery life?
3. Does overclocking really make that much difference, and is it safe?
4. Is there a how to, or a guide that can show me how to do it?
Thanks
Click to expand...
Click to collapse
What kernel are you on?
I'm on Twilight and can overclock to 1.3ghz with full stability. I don't undervolt. Combination of my phone doesn't like it and I'm not looking to save that little battery to get wakelocks (phone doesn't come out of sleep mode because the processor speed is too slow or doesn't have enough juice to make that push.)
If you're using a kernel that can go to 1.4 or 1.5 test it for a while before you save your settings. Also consider buying the paid version. It allows over volting which may allow you to supply enough power if 1.4 or 1.5 causes freezes.
The app is pretty basic. The top bar on the first screen is how low you allow the processor to go in speed. The bottom is how fast. Lower than 100 mhz causes wakelock for me. Or used to. Haven't tried since. My settings are 200-1300 mhz. Second page is voltages. They start at default. If you have extreme, moving them to the right will overvolt and give those speeds extra power. Moving the slider to the left undervolts. Some people can only undervolt at the lowest speeds of say 100-400 mhz. It's a lot of trial and error. Have fun though!
So on the main page my settings are 200-1300, then I press apply settings. How can I tell If it is working, it does not seem that much faster? Do I have to set this every time I turn my phone on? Do I want to save thos for boot up?
Led4lyf said:
So on the main page my settings are 200-1300, then I press apply settings. How can I tell If it is working, it does not seem that much faster? Do I have to set this every time I turn my phone on? Do I want to save thos for boot up?
Click to expand...
Click to collapse
It wont make it much faster
Sent from my SPH-D700 using XDA App
Led4lyf said:
So on the main page my settings are 200-1300, then I press apply settings. How can I tell If it is working, it does not seem that much faster? Do I have to set this every time I turn my phone on? Do I want to save thos for boot up?
Click to expand...
Click to collapse
When you turn your phone off then on, does it show those same settings? The speed boost will be slight. It's not like we're resurrecting Jesus here.
can anyone suggest a good overclock tool with voltage parameters? setcpu doesn't seem to have one for the play... and antutu seems bugged when setting voltages... (keeps changing the value for 1300mhz to 1300mv)
seagheart89 said:
can anyone suggest a good overclock tool with voltage parameters? setcpu doesn't seem to have one for the play... and antutu seems bugged when setting voltages... (keeps changing the value for 1300mhz to 1300mv)
Click to expand...
Click to collapse
I'm using Antutu CPU Master Pro and I don't find it buggy. This is better to use imo than setcpu which consumes more battery. Longpress the frequency you are in and using then set to -25mv. Tick on "set on boot" then click "apply". Reboot your phone and check again your settings if it was changed or not. Also, try to reinstall your overclocking app and clear some cache on your phone.
anbu187 said:
I'm using Antutu CPU Master Pro and I don't find it buggy. This is better to use imo than setcpu which consumes more battery. Longpress the frequency you are in and using then set to -25mv. Tick on "set on boot" then click "apply". Reboot your phone and check again your settings if it was changed or not. Also, try to reinstall your overclocking app and clear some cache on your phone.
Click to expand...
Click to collapse
i do agree that antutu is very good... but the problems started when i updated to 2.5... i was using 2.3 before
is -25 the lowest it can go??? isnt -50 safe?
EDIT: also in 2.5 it keeps saying that it has been granted superuser permissions... in 2.3 it only does that whenever i change any setting...
I use OC/UV Beater2v1.7, and it's awesome! Unlike setcpu, it won't run in the background, but rather sets up scripts in init.d (don't set as permanent unless you're 100% sure of your OC/UV settings, otherwise bootloops can occur)
seagheart89 said:
i do agree that antutu is very good... but the problems started when i updated to 2.5... i was using 2.3 before
is -25 the lowest it can go??? isnt -50 safe?
EDIT: also in 2.5 it keeps saying that it has been granted superuser permissions... in 2.3 it only does that whenever i change any setting...
Click to expand...
Click to collapse
I use 2.3.1 version. I tried -50 on setcpu and it crashed my phone. Haven't tried -50 yet on Antutu. I rolled back my speed from 1.5ghz to around 900+mhz as the speed is still fast (btw im using T.E.A.M. rom).
jacklebott said:
I use OC/UV Beater2v1.7, and it's awesome! Unlike setcpu, it won't run in the background, but rather sets up scripts in init.d (don't set as permanent unless you're 100% sure of your OC/UV settings, otherwise bootloops can occur)
Click to expand...
Click to collapse
so i only have to run this once? seems good... will try it later...
anbu187 said:
I use 2.3.1 version. I tried -50 on setcpu and it crashed my phone. Haven't tried -50 yet on Antutu. I rolled back my speed from 1.5ghz to around 900+mhz as the speed is still fast (btw im using T.E.A.M. rom).
Click to expand...
Click to collapse
i set my cpu to -50 and it runs fine... did some stress tests and it is stable... running at 1.4ghz (just right for psx games)
jacklebott said:
I use OC/UV Beater2v1.7, and it's awesome! Unlike setcpu, it won't run in the background, but rather sets up scripts in init.d (don't set as permanent unless you're 100% sure of your OC/UV settings, otherwise bootloops can occur)
Click to expand...
Click to collapse
What are bootloops btw? ty
anbu187 said:
What are bootloops btw? ty
Click to expand...
Click to collapse
Bootloop means your phone endlessly reboots without ever getting past the bootlogo
jacklebott said:
Bootloop means your phone endlessly reboots without ever getting past the bootlogo
Click to expand...
Click to collapse
ah ok thanks, that never happened to me so far. Anyway, any idea why my battery is drained that much even when im not using it. No wifi, no other background apps enabled, or is it with the kernel? ty
I have a S4 mini running custom carbon kk unofficial 4.4.3 as it comes with the settings to set CPU's and governors but the phone keeps changing the min to around 1400 but the max stays at 1700.i don't notice until my battery is draining really fast or gets hot. anyone kno a fix to this?
matizkool said:
I have a S4 mini running custom carbon kk unofficial 4.4.3 as it comes with the settings to set CPU's and governors but the phone keeps changing the min to around 1400 but the max stays at 1700.i don't notice until my battery is draining really fast or gets hot. anyone kno a fix to this?
Click to expand...
Click to collapse
Which governor is it using to set a min of 1400? Ever likely it gets hot and eats power! I use f4k's kernel, and the 'Performance Control' app to look at and alter stuff - you don't say what you use or have tried.
There is a Carbon 4.4.4 available with f4ktion 1.5 kernel - might be an idea to flash that and the problem might go away!
xbin said:
Which governor is it using to set a min of 1400? Ever likely it gets hot and eats power! I use f4k's kernel, and the 'Performance Control' app to look at and alter stuff - you don't say what you use or have tried.
There is a Carbon 4.4.4 available with f4ktion 1.5 kernel - might be an idea to flash that and the problem might go away!
Click to expand...
Click to collapse
It's on every governor this happens but I use Wheatley. I would manually set it to around the 300s but in a couple of hours it would auto set at 1400 on its on. This causes my battery to drain my kernel version is 3.4.91 f4ktion 1.4.5 eur lte
matizkool said:
It's on every governor this happens but I use Wheatley. I would manually set it to around the 300s but in a couple of hours it would auto set at 1400 on its on. This causes my battery to drain
Click to expand...
Click to collapse
Strangely enough I've settled with Wheatley too! but it spends most of its time at 162 when not in deep sleep (a bit like me!). This really needs posting in the Carbon thread so I would post a few more things here to help or comment on stuff to get to 10 posts and then ask in there. I can't think what could be causing that behaviour, if it was me it would be bye bye 4.4.3 and hello 4.4.4
xbin said:
Strangely enough I've settled with Wheatley too! but it spends most of its time at 162 when not in deep sleep (a bit like me!). This really needs posting in the Carbon thread so I would post a few more things here to help or comment on stuff to get to 10 posts and then ask in there. I can't think what could be causing that behaviour, if it was me it would be bye bye 4.4.3 and hello 4.4.4
Click to expand...
Click to collapse
Yeah i flashed to 4.4.4 thanks though
Never mind above still happens even though I flashed 4.4.4
matizkool said:
Never mind above still happens even though I flashed 4.4.4
Click to expand...
Click to collapse
Does the actual minimum change rather than it simply running continually at 1400+ and if so which governor does it change to if any!
I read somewhere in the Carbon thread someone was having similar problems so they flashed the kernel twice, one directly after the other; seems something wasn't getting written correctly the first time but was the second, and the problem went away. Worth a go...
xbin said:
Does the actual minimum change rather than it simply running continually at 1400+ and if so which governor does it change to if any!
I read somewhere in the Carbon thread someone was having similar problems so they flashed the kernel twice, one directly after the other; seems something wasn't getting written correctly the first time but was the second, and the problem went away. Worth a go...
Click to expand...
Click to collapse
I found this : Q: CPU/GPU frequency doesn't stick?
A: If your frequency settings don’t stick, it's because on certain Qualcomm or JB and higher devices, there are certain system services (thermald/mpdecision/project butter) or kernel feature that rewrite frequency settings based on current thermal status and/or touch input. Certain custom kernels for your device should include work around for these issues.
Is this a fix?
matizkool said:
I found this : Q: CPU/GPU frequency doesn't stick?
A: If your frequency settings don’t stick, it's because on certain Qualcomm or JB and higher devices, there are certain system services (thermald/mpdecision/project butter) or kernel feature that rewrite frequency settings based on current thermal status and/or touch input. Certain custom kernels for your device should include work around for these issues.
Is this a fix?
Click to expand...
Click to collapse
It could help. Trickster is good. However, this suggests that there is something else causing or forcing the frequency setting to be changed. The question is what? and I've no idea:crying:
Haha I found the problem it was either this battery saver app or I changed to scheduler to anything besides row
matizkool said:
Haha I found the problem it was either this battery saver app or I changed to scheduler to anything besides row
Click to expand...
Click to collapse
Thats good. It was probably the battery saver because they usually do the opposite!