I've been noticing something with my cpu that seems strange to me. I run an app called system panel to monitor my phone for various things and I've noticed for the past few days that my second core is constantly sleeping, even under a full load it stays at 100% idle and system panel says that cpu 1 is asleep. I downloaded kernel tuner and it says that cpu 0 is active but cpu 1 is offline. Was running stock rooted with no tweaks or other things added so i tried using odin to go back to stock but I still get the same info. The first screenshot is from kernel tuner with root and the sceond is from system panel with no root. Could my phone be defective?
Sent from my SGH-T989 using xda premium
Try system tuner in the play store. It has an option in settings to force the second core online, all the time. Set it to always on, and set it to boot that way. At least you can test it to see if it can be forced online. It is normal for the second core to be sleeping most of the time. In your first screenshot I see a toggle for cpu1 on/off at the bottom. You accidently toggle that?
Also, what's up with your CPU temp being 32°F? Are you in the arctic tundra?
You could also try flashing a new kernel. I believe there are a few for touchwiz based ROMs. IMO you should go aosp based ROMs. Slimbean4.1.2 with asdk kernel is the best performing rom/kernel combination I've ever flashed
there is no spoon.....
I tried flashing other kernels when my phone was rooted but it kept giving me the same thing. I tried the toggle in kernel tuner to see if I could turn the second core on after noticing the issue but it did nothing. System tuner was able to force the second core on for a bit but about 30mins after boot, the core went offline and has not come back on since.
Update: found out why core went offline. Apparently, if I touch any frequency settings such as core speed or governor for either core, the processor doesn't like it and shuts down the second core. Not sure if that's normal or not. Once phone is charged enough, gonna try flashing a different kernel to see if the same thing happens when I try to change the speed and governor.
Sent from my SGH-T989 using xda premium
Here is a long story, but please read it all as I really think it will help explain how the two cores work together.
I had/have the same thing. Exactly as you described it. Here is what I found (What I think anyway). I ODIN'd to stock, rooted, and installed Trickster MOD. That app showed only one core working. From reading up on Trickster MOD changing any CPU settings will apply to both cores. I changed the speed, and check the info panel. It showed both cores at the same speed that I changed it to, but the second core was still not moving. I reset Trickster MOD to default, uninstalled it, and installed Kernel Tuner. Same thing. Only one core was working. I started to think it was the stock kernel, so I flashed Tiberius, Jedi, and am now on Faux123. All kernels are doing it. It's not a kernel issue, but a kernel/Stock ROM function. Here is why I say that. I installed CPU Stats, and enabled it to display the CPU cores in the status bar. 99.9% of the time only one core was working (When I mention "99.9% of the time" I mean only one core would be working for about five minutes at a time. Which would lead a person to think somethings wrong since they normally wouldn't stare for ten minutes at the phone's kernel stats trying to catch the second core come on, and think only one was working.). I did catch the second core come on very briefly, so I knew it was working even for a split second. When I did see the second one on I tried to quickly open whatever kernel tuner I had to see what the cores were set to, and what they were doing, but by the time I opened the app only one core was working. I did some thinking, and I opened Lookout and ran a full scan, opened a couple more apps that use a lot of CPU. Then I opened, and kept on top my kernel tuner. To my surprise again 99.9% of the time only one core was working. Even if the CPU load was at 100%. The second core never came on, BUT it was because the first core wasn't at 100%. The CPU load would get to 90% when the first core would hit 100% under heavy load, but no second core was working at all. I finally watched it long enough to see a pattern (Like 15 minutes). The second core will only come on when the first core is at 100% AND the CPU load is at 100%. Then the second core kicks in. Once both cores were working at the same time the CPU load quickly dropped back under 100%, and once it did the second core shut right off to leave the first core do the work. So long story short your phone is not broken. That's the way it's meant to work. In my finding anyway. I'm running the stock ROM from ODIN with Faux123 JB release 1 kernel. That's all my mods are, and running quadrant I get an average score of 3730, so I'm thinking both cores have to be working to get a score like that. Here is the Play link to the CPU Stats app: https://play.google.com/store/apps/details?id=jp.takke.cpustats
And here is what it looks like in the status bar (The last icon on the left showing both cores at max in one screen shot, and the second screen shot showing only one core working. Just to show it does show both cores working separately.):
Thanks for the explination. I watched everything like you did and same results as you. I'm grateful for everyone's input. It puts my mind at ease knowing that everything is like it should be.
Sent from my SGH-T989 using xda premium
That's a good score. What frequency and governor you running?
there is no spoon.....
ctrlaltdeln said:
That's a good score. What frequency and governor you running?
there is no spoon.....
Click to expand...
Click to collapse
It's easier to show in pics that type all the stats. Here you go:
Not sure if me forcing my second core to be on constantly did something or what but I just ran quadrant twice and I got a score of 5661 the first time and 5981 the second.
Sent from my SGH-T989 using xda premium
damn dude. Now that's a score. Obviously your battery life will suffer with that kind of performance. If still using system tuner u definitely want to turn that second core back to default. You dont need all that muscle. I run at 1.18ghz/ lag free governor monday - Friday and 1.67ghz on the weekend. Battery life is more important to me. And everything is still buttery smooth. Glad all is well, your phone is back baby.
there is no spoon.....
Related
Is anyone using SetCPU with gingerbread?
I'm using GingerVillain 1.5 but I can't seem to find the right profiles with SetCPU.
Oc'd @ 1,2 Ghz without profiles.
Because when I use the screen off profile, my screen sometimes won't turn on.
Screen off - min 245 max 1200
Can someone help me finding the right profiles?
Share your user experience.
In my experience and many others too, the profiles are not needed. The only profile you should ever need is a temperature profile and that's only if you really have it cranked up.
Having a screen off profile is always bad since switching to another profile doesn't happen instantly - there are polling intervals involved and until the next cycle runs your phone will still be using the screen off profile. That makes the phone slow which causes SetCPU to take longer in switching profiles, bogs down the cpu and it becomes a vicious cycle for a few seconds (sometimes a couple minutes). All the while it's draing your battery because the cpu has to work harder. Even regular profiles eat the battery due to the constant querying of the systems status and processing power used for that - which is the main reason you'll hear people whining about their battery life (some aren't effected as much).
Profiles are just not a good idea except for a temp profile for those that oc to the higher GHz (probably 1.4+).
You could try using cpu tuner instead. Gives you way more options.
CM 7
You have a lot of options with cpu tuner.
What triggers and/or profiles do you use?
My screen on/off has been working fine with CM7 nightlies before and after the RC1. I've been using SetCPU with a normal profile of 1017max/245min and a screen off profile of 365max/245min.
I think your issue is with overclocking. Idk about Gingervillain but as far as CM7 goes lots of people are having issues with the on/off animations and wakelock issues when overclocked over 1ghz. Try using your profiles and clocking at or under 1ghz and see how things change.
Not sure why anyone would really need a higher clock than 1ghz but what do I know. I dont see any slowdowns at 1017mhz and I feel that anything faster than that would lead to heat or battery issues?
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
thanks bro, i OC'd to 1017 and there are no issues
ibemad1 said:
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
martonikaj said:
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
Click to expand...
Click to collapse
Every kernel that I know of out there drops down the clock cycle when the screen times out. The reason not having the screen off profile saves the battery is because SetCPU isn't constantly sending requests about the phones state and then checking that against your profiles to see if it meets the parameters set in them.
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
KCRic said:
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
Click to expand...
Click to collapse
This is very true. It is definitely hard to make a blanket statement because no two people have the exact same setup. All I was saying is what I've been doin with the screen off animation and I've been having pretty solid battery numbers.
I'm looking to optimize my battery life without sacrificing performance when I need it. I know it sounds easier said than done, but I figure that if anyone might know how, they'd be here. My goal here is to have the performance when I need it, and to keep the battery preserved when I don't.
I'm rooted and running ViperROM 4.0.4 Trinity v2.0. I have the "Genocide 1.2GhzOC EB13 Kernel v0.3a" kernel also flashed to my phone. SetCPU is installed and I've set up my profiles, but I think I may be doing something wrong with them.
I am using autodetect settings as is recommended for adjusting clockspeed. Everything is set to on boot. All profiles are set to conservative as I'm not sure which ones actually apply. Below are screens for everything I have currently set up.
|
|
Am I doing anything wrong here? And if not, is there anything I need to do to improve battery life without sacrificing performance?
I would bump your charging max to 1200Mhz and keep the min at 1000Mhz, although I keep max and min while charging through AC power at 1200Mhz.
Your screen off profile is fine. If you get hiccups or missed calls for any reason, bump the max up to 400Mhz.
If you can run it smoothly, set your minimums for your battery profiles to 100Mhz. It what I'm at now and it runs fine. You may want to keep your minimum for your "screen off" profile at 200Mhz if you get hiccups or missed calls like I mentioned before.
As for your battery <50% profile, I'd set the min at 200Mhz if you're wanting to save battery. Don't want the phone running at a higher clock when it doesn't need it. That's the point of running the min lower.
I personally uncheck the "set on boot" to allow SetCPU to always come back to the appropriate profile rather than going back to the default setting.
Also, set a Battery < 101% profile which will be your new default. I have mine at max 1000Mhz and min 100Mhz and it works well.
Also, conservative simply means the battery will remain at the lowest possible clock until it needs more juice. Assuming it starts at 200Mhz, it'll bump up to 400Mhz, 800Mhz, etc. depending on what the demand is. It will jump frequencies from 200Mhz to 1000Mhz if necessary.
On Demand means the CPU will either be at your minimum set clock frequency or your maximum.
On Demand is usually the most compatible/stable, but the conservative setting is best for battery/performance if your kernel allows it.
Hope this helps =). Let us know if you have more questions.
EDIT: The "set on boot" button simply sets the min and max that's shown on the main screen in SetCPU. If this button is unchecked but the "enable" button on the profiles menu is checked, your profiles will still adjust accordingly.
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
badbeats said:
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
Click to expand...
Click to collapse
This might be a dumb question, but is your phone fully rooted?
I think so I used Clockwork mod 3.0.6 and I am running Bonsai 3, with 2.2.1
ZeppelinJ0 said:
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
Click to expand...
Click to collapse
Yeah I hear you, I get the same crummy battery life with SyndicateROM, I was dying for the 30 hours ! Starting to think it's the battery itself.
musclehead84 said:
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
Click to expand...
Click to collapse
Do you keep your 1200/100 on conservative? And what's the battery life you're getting on average? Dummy question but you know...
I'm going to try out this setting today actually with BakedSnack.
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Blankrubber said:
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Click to expand...
Click to collapse
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
ZeppelinJ0 said:
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
Click to expand...
Click to collapse
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
+1 I think this was a bug with the original release of Twilight Zone that was fixed in 1.0.1.
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I'm trying this out right away, thanks!
This whiny message brought to you by the letter E for Epic 4g
I'm on sfr 1.2 with genocide 1.1 final kernel, what are optimal settings for voltage control for speed, everytime I put it at 1.4 it instantly freezes and I have to pull battery, then when I put it at 1.3 it will be fine foor a little while but if I multitask like using music player the phone freezes and I must pull battery again, what should the speed mhz and voltage be?
Sent from my SPH-D700 using XDA App
xxDRKAxx said:
I'm on sfr 1.2 with genocide 1.1 final kernel, what are optimal settings for voltage control for speed, everytime I put it at 1.4 it instantly freezes and I have to pull battery, then when I put it at 1.3 it will be fine foor a little while but if I multitask like using music player the phone freezes and I must pull battery again, what should the speed mhz and voltage be?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
First of all, this topic has been touched on before, but I will give you a quick rundown as long as you promise to read the "You are new to XDA post" in the general forums.
Every phone is different, which is why Voltage Control is so awesome. You can "feel" out each phone's "max" and "low" and set it accordingly. If you are just using the first page of VC, set the max to 1400, min to 200 and leave the dropdown menus where they are (mine is on cfq and conservative, but I can switch between the others with no problem). If you keep the min at 100, you almost always have problems.
Also, try doing a completely clean flash. Boot into CWM, wipe everything three times (sometimes I do over-kill and go 4 or 5 if I am feeling froggy or have nothing better to do) and then install ROM, then Kernel.
If this does not help you, then you can only run at 1300. Unless anyone else has any ideas. *shrug* I am still n00b.
Or 1200. Every phone is different. I personally can't go above 1200 without near-daily issues like abnormal freezing, lag, and overheat. But like I said, it's all phone-to-phone. Play with the settings when you're bored and have a recent nandroid backup. Same goes for undervolting, though I don't bother with such. There's much more to potential consequences of undervolting than what you'll read in many of these threads.
Sent from my SPH-D700 using XDA Premium App
Also, music and video tend to push the phone the most. A good way to test if 1300 will work for you is to run YouTube, play music, etc. Always set "apply for now" as well until you know your settings are rock solid. If you select "set on boot" and lockup or freeze you will most likely have to wipe everything and start again. It takes some people days to get Voltage Control just right especially when it comes to undervolting. Test every combination of the apps you use the most.
Sent from my SPH-D700 using XDA Premium App
Hi All,
After being a long time iPhone user i recently purchased htc one x, as a result my android skills are almost non-existent; so please bear with me.
I managed to flash clockworkmod recovery and rooted with SuperSU with no issues.
Purchased setCPU after reading the reviews and enabled. However the phone would reboot randomly a few times a day. Ususally when the screen was off.
After disabling setCPU there was no rebooting issue.
Has anyone got this app to work on the OneX, and if so which settings did you use?
Also has it been confirmed to work with all 4 cores?
FYI I had the following profiles setup.
Screen Off
Freq:640Mhz-51Mhz
Gov: conservative
Temp > 44.5
Freq:880Mhz-51Mhz
Gov: conservative
Battery < 30%
Freq:1000Mhz-51Mhz
Gov: powersave
Charging Any
Freq:1500Mhz-51Mhz
Gov: ondemand
Please note these profiles are based on no evidence, just on what I estimated to be about right...
Cheers
I did not start using SetCPU on my phone yet because it's not rooted, but first I would check if SetCPU doesn't require some kernel support? and if that's implemented in the custom ROM you're using? (if it's needed, I'm not sure).
Or maybe SetCPU needs an update to properly support our phones?
That Temp > 44.5 Profile, wouldn't that interfere with gaming? I have never used Temp profiles before (is it really needed?), only the other ones, like battery and screen-off and charging.
my one x has unlocked bootloader, recovery and root. I was running into some serious intermittent lagging issues, the phone in any app would just stall for 5+ seconds. after hours restoring after failure , it came down to the problem that using ANY cpu controll app, messed my phone up... BADLY! it seems at the moment (im assuming) apps like setcpu and cpu master are not quad core ready...
thanks for the responses guys.
I guess ill just wait until one of the devs can confirm this as working...
The reason is simple. We don't have rooted kernels yet. Until then stay away from messing with CPU speeds or under volting. Etc.
Sent from my HTC One X using xda premium
skywalker1970 said:
The reason is simple. We don't have rooted kernels yet. Until then stay away from messing with CPU speeds or under volting. Etc.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
+1
DO NOT mess with your CPU speeds yet. Undervoltage is causing reboots!
the software is not up to the hardware capability, i dont think the cpu control apps can handle quad core yet. and there is a lot of apps (esp. games) that lag a lot, and amazingly the cores are too lazy to work... im hoping for a better kernel that will address this issues.
If you want to at least see what's going on with the cores, I can confirm that Tablet CPU Usage Monitor works on HTC One X
It shows 2 icons in notification bar, each icon showing usage of 2 cores. Not sure how accurate it is, but so far had no problems with it and it seems to be reporting correctly. Developer is working on single icon with all 4cores in it, to save space.
I had the same problem, but if you delete your profiles you won't get reboots.
I'm just running default profile Max: 1500, Min: 760 Ondemand gov. and it has been a straight line for 6 hours when I was sleeping and no reboots.
jakejay said:
Hi All,
After being a long time iPhone user i recently purchased htc one x, as a result my android skills are almost non-existent; so please bear with me.
I managed to flash clockworkmod recovery and rooted with SuperSU with no issues.
Purchased setCPU after reading the reviews and enabled. However the phone would reboot randomly a few times a day. Ususally when the screen was off.
After disabling setCPU there was no rebooting issue.
Has anyone got this app to work on the OneX, and if so which settings did you use?
Also has it been confirmed to work with all 4 cores?
FYI I had the following profiles setup.
Screen Off
Freq:640Mhz-51Mhz
Gov: conservative
Temp > 44.5
Freq:880Mhz-51Mhz
Gov: conservative
Battery < 30%
Freq:1000Mhz-51Mhz
Gov: powersave
Charging Any
Freq:1500Mhz-51Mhz
Gov: ondemand
Please note these profiles are based on no evidence, just on what I estimated to be about right...
Cheers
Click to expand...
Click to collapse
I was having that problem too... In my opinion, I don't think that the phone can handle the Conservative governor setting. I set my governor to Interactive (On Demand works too)
Right now, I have my profile set to 1000mhz max and 475mhz min, with screen off profiles set to 475mhz max and min. I have not had any problems with the phone rebooting at all since setting those freqs. (And I don't want to quite go any lower yet). And I have it Set on Boot.
im now using rooted HTC One X(HOX) and installed RD-MIUI ROM quite sometimes. my kernel is still in stock. Im using setcpu and NO random reboot happen like what you have said. Yet, i am still confuse whether setcpu is good for my phone. based on my review, in the leading rom developer thread they not mention setcpu for their choice. they play alot with kernels to govern their hox cpu-s. could anyone do some comment.
I just wanted to confirm my understanding of eugene's sleeper script since I never fully got a handle on it. As I understand it, prior to this our phones second core never truly went offline (even though system tuner read it as offline). Now, our second core always goes offline when the screen is off (even though system tuner reads it as running at 192mhz). Is this right? Also, does it go offline at low load time periods when the screen is off?
yoft1 said:
I just wanted to confirm my understanding of eugene's sleeper script since I never fully got a handle on it. As I understand it, prior to this our phones second core never truly went offline (even though system tuner read it as offline). Now, our second core always goes offline when the screen is off (even though system tuner reads it as running at 192mhz). Is this right? Also, does it go offline at low load time periods when the screen is off?
Click to expand...
Click to collapse
On stock rooted ICS (though de-bloted) second core goes into deep sleep no problem when task scheduler/governor commands so and regardless if screen is On or Off.
What Eugene's script is doing: constantly looping every 2/4 sec (or whatever) and checking if screen is On or Off and then force CPU1 to go offline regardless what Linux Governor think is appropriate for current CPU load.
It might very much happened that next moment (in between loop cycles) governor would turn CPU1 back online if load on CPU0 is above threshold.
If script loop would be too short then script itself would burn battery juice... so, I think best thing to improve battery life is just keep phone clean from unwanted background processes.
Also, it might happened in reverse, when screen is on and there is no load - governor would turn CPU1 off, but script will continue to force CPU1 online.
Vlad_z said:
On stock rooted ICS (though de-bloted) second core goes into deep sleep no problem when task scheduler/governor commands so and regardless if screen is On or Off.
What Eugene's script is doing: constantly looping every 2/4 sec (or whatever) and checking if screen is On or Off and then force CPU1 to go offline regardless what Linux Governor think is appropriate for current CPU load.
It might very much happened that next moment (in between loop cycles) governor would turn CPU1 back online if load on CPU0 is above threshold.
If script loop would be too short then script itself would burn battery juice... so, I think best thing to improve battery life is just keep phone clean from unwanted background processes.
Also, it might happened in reverse, when screen is on and there is no load - governor would turn CPU1 off, but script will continue to force CPU1 online.
Click to expand...
Click to collapse
So if I understand you right, the script does nothing radically different, all it does is override the original cpu handling to force cpu1 offline when screen is off? It doesn't put cpu1 offline a different way than before?
yoft1 said:
So if I understand you right, the script does nothing radically different, all it does is override the original cpu handling to force cpu1 offline when screen is off? It doesn't put cpu1 offline a different way than before?
Click to expand...
Click to collapse
What do you mean by "different way"? (Script writes 1/0 into Linux CPU driver)
Vlad_z said:
What do you mean by "different way"? (Script writes 1/0 into Linux CPU driver)
Click to expand...
Click to collapse
I'm not sure, I just remember Eugene saying that cpu1 wasn't truly going offline before his script?
I don't pretend to understand any of it, but I will tell you that when the screen is off, it eats much less battery then before using it.
Vibrantnew-b said:
I don't pretend to understand any of it, but I will tell you that when the screen is off, it eats much less battery then before using it.
Click to expand...
Click to collapse
that's very possible. If you have some background processes, using this script, you basically trying to make from dual core CPU single.
or this is just placebo effect... how did you test it? My phone goes to deep sleep no problem, overnight 4% for 8 hours.