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.
Related
I know there are quite a few threads on setCPU BUT this is my first time using and i was wondering for my rom, kernel, and phone usage what you guys think is best to save battery but still be snappy when the screen is on.
My phone setup:
2.2 Android
2.15.00.09.01 Baseband
King CFS 10 kernel
Evervolv v0.2.1 rom
pri 1.77_003
PRL 60670
I have the phone on wifi about 90% of the time because some of my reading says it saves battery. I use my phone for browsing facebook and a few forums, send a few hundred texts a day, talk on the phone maybe 10 times a week ( im a college student), regularly on email. NOW with that said how would YOU set up the set cpu for battery life but no lag while operating.
You need to update your PRL ...
twigums said:
I know there are quite a few threads on setCPU BUT this is my first time using and i was wondering for my rom, kernel, and phone usage what you guys think is best to save battery but still be snappy when the screen is on.
My phone setup:
2.2 Android
2.15.00.09.01 Baseband
King CFS 10 kernel
Evervolv v0.2.1 rom
pri 1.77_003
PRL 60670
I have the phone on wifi about 90% of the time because some of my reading says it saves battery. I use my phone for browsing facebook and a few forums, send a few hundred texts a day, talk on the phone maybe 10 times a week ( im a college student), regularly on email. NOW with that said how would YOU set up the set cpu for battery life but no lag while operating.
Click to expand...
Click to collapse
I always leave my main profile at 245 mhz min and 998 mhz max (ondemand mode). Then, of course, you'll want a screen off profile, and as far as that goes, I've heard that 128 and 245 draw the same voltage, so I have mine set to 128 min, 245 max (powersave mode). Other than that I just have some low battery profiles and a temp one. I don't really get any lag with this setup, but I've heard some people do. If that's the case, and I'm only talking about lag when first turning on, just up the 245 to 384 or something and I'd make it ondemand.
do i need to check set on boot under the scaling option
twigums said:
do i need to check set on boot under the scaling option
Click to expand...
Click to collapse
No. I would leave it unchecked. This has been known to cause some issues.
grouse130 said:
No. I would leave it unchecked. This has been known to cause some issues.
Click to expand...
Click to collapse
what kind of issues are you talking about? i've only heard and practice leaving it off when experimenting with overclocking (since it can put you in a boot loop). once you find a stable overclock speed, you can check it to start on boot so that you don't have to open setcpu every time you reboot if you decide to run it at that speed.
on-demand is a little less laggy (barely noticeable to me) but may consume more juice than conservative.
most kernels will step down to 245 when the screen is off so creating a profile to do that is redundant. you can verify this with the app android system info under the system tab > cpu.
having said that, i don't use setcpu unless i'm benchmarking and want to overclock.
kings #6 bfs kernel is awesome for battery life (default is conservative governor). it's what i use. give it a go when you've gotten a good feel on how kings #10 cfs is working out for you.
Here's what I would hit up..
set it to conservative. Conservative starts your phone at your minimum clock speed and works its way up, as opposed to on demand which starts at the highest and works its way down.
then for advanced i have sampling rate at 50000
Up threshold at 95% <- that's saying that when the workload hits 98%, crank up the processing speed
Down threshold at 70% <- when the load hits 70% turn it down
That stuff right there is agressive as hell, and when I say agressive, i mean...you probably won't ever hit your max frequency unless you are seriously doing some heavy lifting. The settings there are what I use to save up battery, you can get through a day easy with everything on (GPS, Wifi, sync, 3g, the works) and with your current usage, since its similar to mine (except that i also run beejive, skype and twitter at refresh rate of 5min).
grouse130 said:
No. I would leave it unchecked. This has been known to cause some issues.
Click to expand...
Click to collapse
Yeah I think you've probably just seen that on some custom kernel pages. They only say not to do that because if you're testing battery life with say...HAVS, it could interfere w/o you realizing it. Set on boot just means you don't have to turn setCPU on everytime you reboot your phone.
just go set a profile on minimal mhz and on powersave mode if kerenal allows if not just use ondemand
My problem with the "Set on Boot" option is if you accidentally fat finger the slider past your stable clock with it checked, you're looking at boot loops and possibly having to restore from a backup to sort it out. SetCPU really needs the "Set on Boot" option grayed out and a "Lock Settings" option that must be checked before "Set on Boot" becomes accessible (unchecking "Lock Settings" would also uncheck "Set on Boot").
Another option would be a user defined field for max stable clock in the advanced settings that would limit the slider on the main tab. Either one should eliminate accidental boot loops.
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
Having some major headaches with my Note 2 right now. I'd previously had System Tuner set to cap screen-off frequency at 800MHz, with the pegasusq governor still selected. That was causing heavy drain (1-2% per hour) while idle, so I tried yesterday evening to scale it down to 200MHz with the powersave governor for screen off. It worked in the sense that my battery stayed flat at 67% overnight, but the phone took forever to come out of sleep so I could turn off my alarm clock, and then it started some type of fresh torment where it would freeze at the lockscreen and need a battery pull to reboot.
I switched the frequency to 500MHz this morning, but it's still locking up. Struggling to boot, too. I'd really rather not go back to 800MHz and pegasusq, but will if I need to. How do you guys have your screen-off behavior set in System Tuner, and has it caused you any problems? I'm on stock rooted, by the way, debloated by myself a while back.
T.J. Bender said:
Having some major headaches with my Note 2 right now. I'd previously had System Tuner set to cap screen-off frequency at 800MHz, with the pegasusq governor still selected. That was causing heavy drain (1-2% per hour) while idle, so I tried yesterday evening to scale it down to 200MHz with the powersave governor for screen off. It worked in the sense that my battery stayed flat at 67% overnight, but the phone took forever to come out of sleep so I could turn off my alarm clock, and then it started some type of fresh torment where it would freeze at the lockscreen and need a battery pull to reboot.
I switched the frequency to 500MHz this morning, but it's still locking up. Struggling to boot, too. I'd really rather not go back to 800MHz and pegasusq, but will if I need to. How do you guys have your screen-off behavior set in System Tuner, and has it caused you any problems? I'm on stock rooted, by the way, debloated by myself a while back.
Click to expand...
Click to collapse
I don't use system tuner, but in setcpu my screen off profile is set for 200-500 with pegasusq/cfq. I use almost no battery when my screen is off, and the wake up time is no slower than stock.
P1 Wookie said:
I don't use system tuner, but in setcpu my screen off profile is set for 200-500 with pegasusq/cfq. I use almost no battery when my screen is off, and the wake up time is no slower than stock.
Click to expand...
Click to collapse
Thanks for that. I had to restore (luckily I'd done a Nandroid yesterday!) because the system wouldn't boot past the Samsung splash. I've been anti-Juice Defender for a while here, but it seems like a decent chunk of the problem with my battery has been wlan_rx_wake, most likely caused by network traffic. That's what I get for letting my wife share my phone's wifi router instead of leaving her on the house.
Much as I hate to do so, I've put JD Ultimate back on my phone in hopes that its control over wifi and data will prevent those wifi and data wakelocks from happening. Hoping that 500 max with pegasusq (I'd put it back at 600 after restoring) will alleviate things.
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.....
Hello,
My phone began to get hot since 1 week and the battery drains very quickly. I investigated and found out that it's the ksm deamon that is causing that (30% + cpu usage all time). The ksm deamon scans all the memory at an interval to do things with it... It is a normal linux process but :
The problem is that the interval is set to 20ms ! And that the run value is at 1. The files are here : /sys/kernel/mm/ksm/run
I changed run from 1 to 0 with the terminal emulator, it fixes the problem, but then it goes back to 1 after some minutes. Same for the interval, I set it manually to 10000000000000000000 and then it goes back to 20.
It's like there's a virus changing the value or something like that.
Help me please, I can't use my phone anymore, it lags, gets hot and the battery drains very quickly :crying:
Thanks.
I'm having the same damn problem on my oneplus. It get's so hot it causes the touchpad to stop working and the phone becomes unresponsive and I have to force shutdown. Did you find a solution to this problem? I might try a custom ROM on here, I didn't have this problem with my last oneplus so not sure if it was a recent kernel update to CM11 that did this or what.
skini26 said:
Hello,
My phone began to get hot since 1 week and the battery drains very quickly. I investigated and found out that it's the ksm deamon that is causing that (30% + cpu usage all time). The ksm deamon scans all the memory at an interval to do things with it... It is a normal linux process but :
The problem is that the interval is set to 20ms ! And that the run value is at 1. The files are here : /sys/kernel/mm/ksm/run
I changed run from 1 to 0 with the terminal emulator, it fixes the problem, but then it goes back to 1 after some minutes. Same for the interval, I set it manually to 10000000000000000000 and then it goes back to 20.
It's like there's a virus changing the value or something like that.
Help me please, I can't use my phone anymore, it lags, gets hot and the battery drains very quickly :crying:
Thanks.
Click to expand...
Click to collapse
into_311 said:
I'm having the same damn problem on my oneplus. It get's so hot it causes the touchpad to stop working and the phone becomes unresponsive and I have to force shutdown. Did you find a solution to this problem? I might try a custom ROM on here, I didn't have this problem with my last oneplus so not sure if it was a recent kernel update to CM11 that did this or what.
Click to expand...
Click to collapse
I kept disabling it manually with the terminal and was monitoring my phone with a process manager. Then it stopped by itself I don't know how....
But it may come back one day I really don't know why, I didn't even uninstalled an application. This is very weird and it's a core functionnality of linux, why is it designed like that ?
skini26 said:
I kept disabling it manually with the terminal and was monitoring my phone with a process manager. Then it stopped by itself I don't know how....
But it may come back one day I really don't know why, I didn't even uninstalled an application. This is very weird and it's a core functionnality of linux, why is it designed like that ?
Click to expand...
Click to collapse
I've noticed KSMD only pegs out like crazy on my phone when it's active. While the phone is asleep it does nothing.
I can tell it's not at all related to running the TOP process either to monitor things because if you do a ps -ef --sort +time, you can see KSMD process constantly climbing a few seconds of a time of CPU use the longer your phone uptime\Screen-on-time goes on. It's not growing at a massive rate, but like 1 second of CPU time for every 30 seconds of screen on time.
I did a little digging and apparently this is an issue on many Linux distributions and is generally seen as a bug from the user community(unsure how the dev community feels about it, but it's pretty old.. you'd think they would address it by now). It's possible that the Gamma kernel is based on a Linux kernel distro that has that bug in it.