Develop Bugs

New to SetCPU!

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.

[Q] SetCpu VS Voltage Control Lite

Im currently running SRF 1.2, twilight kernel. Im interested in trying voltage control but dont completely understand the app as i do setcpu with its profiles and all. I am more into saving battery life while sleep than overclocking. My phone is fast enough. For undervolting, what do you guys suggest? Thanks in advance

There's nothing you can do with voltage control you can't with set cpu. I think vc pro does allow you to over volt but if your hitting your desired freq's without freezing you should have no need.
Cd's or tapes?

MrEpic said:
Im currently running SRF 1.2, twilight kernel. Im interested in trying voltage control but dont completely understand the app as i do setcpu with its profiles and all. I am more into saving battery life while sleep than overclocking. My phone is fast enough. For undervolting, what do you guys suggest? Thanks in advance
Click to expand...
Click to collapse
You say you want to save more battery while sleep...then you need to check CPUspy and Spare Parts to make sure your phone is going into deep sleep. No change in voltage (which VC allows you to do) will save or use more battery there. What you want to look for is partial wakes...programs that disturb your phones sleep by syncing or running while sleeping. Change the syncs to manual or uninstall apps using too much battery in standby.
As for any undervolting or overvolting, every phone is different..some can tolerate no changes in voltage where others will take anything you give it. Small changes should be tested thoroughly before applying upon boot so if your phone freezes during a test it will revert to a working voltage upon reboot.

My Nexus not waking up?

basically just recently i have noticed my Nexus not waking up.
will simply go sleep perfectly fine but sometimes will not wake and sort of reboots in away.
tried all sort of ROMS, kernels, radios with no effect. even switched back to ICS but still get the same results.
Galaxy nexus
Android 4.1.1
XXLF1
Rom: Latest CM10 Nightly
Kenel: Stock (even tried Francos)
Logcats:
http://pastebin.com/tpeuQYqx
Any ideas guys?

Did you try wiping everything on the phone and starting fresh. Go in the Android Revolution thread and run the superwipe script and wipe again then reinstall everything see if that helps.
I didn't look at the logcats, too tedious.

See here. http://forum.xda-developers.com/showthread.php?p=29839968
good day.

clarkey1269 said:
basically just recently i have noticed my Nexus not waking up.
will simply go sleep perfectly fine but sometimes will not wake and sort of reboots in away.
tried all sort of ROMS, kernels, radios with no effect. even switched back to ICS but still get the same results.
Galaxy nexus
Android 4.1.1
XXLF1
Rom: Latest CM10 Nightly
Kenel: Stock (even tried Francos)
Logcats:
http://pastebin.com/tpeuQYqx
Any ideas guys?
Click to expand...
Click to collapse
Does this happen on stock. This logcat is using franco's kernel, are you UV'ing? OC'ing? Smartreflex? I don't know if actually Francisco is using official stock voltages today, or is already uv'ing a little from source.
And I just finished going through your log, there's nothing useful there; you should be getting it while it happens, or better yet would be /proc/last_kmsg immediately after the reboot; Grab it like this, for example:
Code:
adb shell cat /proc/last_kmsg > last_kmsg_on_my_pc
Also, what you're experiencing is called Sleep of Death.

chopper the dog said:
See here. http://forum.xda-developers.com/showthread.php?p=29839968
good day.
Click to expand...
Click to collapse
also happens on ICS not just JB
full wipe is taken out with every flash or nightly update without fail.
even did a fresh start with locking and relocking the bootloader with no effect i still get the annoying wake

Are you using any app to control your min CPU voltage? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU voltage is too low...

cayte2 said:
Are you using any app to control your min CPU frequency? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU frequency is too low...
Click to expand...
Click to collapse
Why? It's more likely that it's the voltages that are causing it, they're probably too low for his chip. What you're saying is that "it doesnt have enough power", so you're kind of contradicting yourself. And CPU ramps you know? So, if it meets a intensive task (if you call waking up the screen and bringing up UI an intensive task), it will ramp UP to the next step, until it reaches the defined workload percentage for max cpu speed defined in the governor.

bk201doesntexist said:
Why? It's more likely that it's the voltages that are causing it, they're probably too low for his chip. What you're saying is that "it doesnt have enough power", so you're kind of contradicting yourself. And CPU ramps you know? So, if it meets a intensive task (if you call waking up the screen and bringing up UI an intensive task), it will ramp UP to the next step, until it reaches the defined workload percentage for max cpu speed defined in the governor.
Click to expand...
Click to collapse
Sorry I meant to say voltage

cayte2 said:
Are you using any app to control your min CPU frequency? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU frequency is too low...
Click to expand...
Click to collapse
cayte2 said:
Sorry I meant to say voltage
Click to expand...
Click to collapse
It seems you didn't understand where you're contradicting yourself.
min cpu frequency is not equal to min cpu frequency voltage. If you set min cpu freq to 700mhz step, but lower the voltage to a value where that same cpu step it's not stable, it will still have issues.
Another thing I recalled: OP, are you limiting your MAX cpu freq, WHEN screen is off? Like with cpu profilers and such apps?

bk201doesntexist said:
It seems you didn't understand where you're contradicting yourself.
min cpu frequency is not equal to min cpu frequency voltage. If you set min cpu freq to 700mhz step, but lower the voltage to a value where that same cpu step it's not stable, it will still have issues.
Another thing I recalled: OP, are you limiting your MAX cpu freq, WHEN screen is off? Like with cpu profilers and such apps?
Click to expand...
Click to collapse
when using Francos kernel i have being using his app.
haven't messed with any frequency's and is set to what ever the kernel is standard. with no effect.
no fancy profiles set in his app either.
really starting to bug me now

clarkey1269 said:
when using Francos kernel i have being using his app.
haven't messed with any frequency's and is set to what ever the kernel is standard. with no effect.
no fancy profiles set in his app either.
really starting to bug me now
Click to expand...
Click to collapse
Does it happen when using google's factory image?

Do you have Eugene cpu sleeper installed? I was having that happen to mine and I just uninstalled, wiped caches, fixed permissions and I haven't had a problem since.
Sent from my Galaxy Nexus using xda premium

bk201doesntexist said:
Does it happen when using google's factory image?
Click to expand...
Click to collapse
fresh instal of googles stock image and il report back

Is my Note 4 defective?

I need somebody's help. The coolest my Note 4 CPU/GPU seems to get is about 53 degrees C and that's when I turn it on after it's been asleep on my desk. It is not a rogue app or anything like that because I have done both Factory resets and I have install custom roms, so everything has been factory reset multiple times. The water damage sticker indicates no water damage whatsoever. I know phones can get hot when gaming, my Note 4 gets to anywhere between 70 to 85 degrees Celsius and I am just wondering if that's normal I reduced my screen resolution to 720P and disabled two cores of the quad core processor and it does not seem to help one bit. Is this temperature normal or do I need to get rid of the phone?
PS when doing normal browsing it seems to hover around 60 to 67 degrees C
And the battery does not seem to go over 37 degrees Celsius

bucs9115 said:
I need somebody's help. The coolest my Note 4 CPU/GPU seems to get is about 53 degrees C and that's when I turn it on after it's been asleep on my desk. It is not a rogue app or anything like that because I have done both Factory resets and I have install custom roms, so everything has been factory reset multiple times. The water damage sticker indicates no water damage whatsoever. I know phones can get hot when gaming, my Note 4 gets to anywhere between 70 to 85 degrees Celsius and I am just wondering if that's normal I reduced my screen resolution to 720P and disabled two cores of the quad core processor and it does not seem to help one bit. Is this temperature normal or do I need to get rid of the phone?
PS when doing normal browsing it seems to hover around 60 to 67 degrees C
And the battery does not seem to go over 37 degrees Celsius
Click to expand...
Click to collapse
Okay, so I got rid of my Note 4 so this is off of memory (full-disclosure). My Note 4 always ran pretty hot when it had to do anything. When flashing ROMs I'd be lucky if the CPU was below 70 C and any time I'd be playing a GPU intensive game it would get too hot to touch. I never had a lot of issues with the battery temp being too high though despite this.
As far as solutions go:
1) Screen res might help.....but I would try my other suggestions first
2) I wouldn't recommend disabling cores, it just makes the other two have to work harder to accomplish the same tasks and may be worse overall.
3) Kernel adiutor will allow you to do two things: adjust thermal throttling and adjust max GPU/CPU frequencies. I always reduced the max GPU frequency on this phone to lower the temps and adjusted thermal throttling to 55 C. The only CPU adjustments I did were to make sure the CPU wasn't overclocked.
4) I know you said it wasn't a rouge app, but get a task viewer (this is a good one) just to make sure (I had Nova taking 25% CPU usage in the background because I restored it from TiBu).
I saw your post in the NSeven thread and decided to respond, but please in the future try not to post errors in other threads unless you have the issue in that ROM. It sounds like you might have the same issue in that ROM as well, but you didn't say so in your post.

Well first of all I would like to say thank you! I have been hoping for a while that someone would have some knowledge on the subject and I very much appreciate yours. Secondly, I apologize and I will try to refrain from posting the wrong thing in the wrong area in the future. Thirdly I have kernel auditor when I changed their frequencies on my CPU cores they just change right back. If I set a minimum it will stay but then if I try to set a maximum it resets them both to the default setting. I will turn my other course back on though thank you for that information do you have any idea why I may be having this frequency issue?

bucs9115 said:
Well first of all I would like to say thank you! I have been hoping for a while that someone would have some knowledge on the subject and I very much appreciate yours. Secondly, I apologize and I will try to refrain from posting the wrong thing in the wrong area in the future. Thirdly I have kernel auditor when I changed their frequencies on my CPU cores they just change right back. If I set a minimum it will stay but then if I try to set a maximum it resets them both to the default setting. I will turn my other course back on though thank you for that information do you have any idea why I may be having this frequency issue?
Click to expand...
Click to collapse
You're welcome, and no worries for the post . As for your third point it would be really helpful if you tell me what you're running.
Could you list: kernel, ROM, root method, Android version, and any kernel mods (govtuner, skynet, etc)?
Also, does the same thing happen when you set a GPU max frequency? Have you tried having the settings run on boot and then reboot the phone?

Yes I have tried that a couple of times I am currently running the nseven ROM with the CPU frequencies set at a minimum of 300 megahertz and a maximum of 1190 megahertz, or at least that's what I'm attempting to do LOL I have not tried changing the GPU Max frequency. The N7 ROM I believe is Android version 6.0.1. here is what I have tried
Wiping cache in recovery
Starting in safe mode
Factory resetting
Turning off certain settings such as WiFi calling, data Etc.
Using apps such as greenify to limit background processes.
Changing screen resolution to 720P
I actually installed this ROM hoping that it would make a difference because I have the same exact issue on the stock ROM before I ever unlock my bootloader or rooted my phone at all. And according to the sticker on the back of the phone it is not nor has it ever been water damaged. The picture I have attached shows my phone's activity just while writing this reply to you. In the bottom left-hand corner you can see the statistics. Sorry for the Inception lol

bucs9115 said:
Yes I have tried that a couple of times I am currently running the nseven ROM with the CPU frequencies set at a minimum of 300 megahertz and a maximum of 1190 megahertz, or at least that's what I'm attempting to do LOL I have not tried changing the GPU Max frequency. The N7 ROM I believe is Android version 6.0.1. here is what I have tried
Wiping cache in recovery
Starting in safe mode
Factory resetting
Turning off certain settings such as WiFi calling, data Etc.
Using apps such as greenify to limit background processes.
Changing screen resolution to 720P
I actually installed this ROM hoping that it would make a difference because I have the same exact issue on the stock ROM before I ever unlock my bootloader or rooted my phone at all. And according to the sticker on the back of the phone it is not nor has it ever been water damaged. The picture I have attached shows my phone's activity just while writing this reply to you. In the bottom left-hand corner you can see the statistics. Sorry for the Inception lol
Click to expand...
Click to collapse
Since you're replying to both threads I'll keep my responses to your other Q&A thread to make life easier .

Big cluster freq. staying at 2361

As the title says, I have this problem where the big cluster frequency stays at 2361MHz and doesn't drop down to its idle frequency. It occasionally goes down to about 2000MHz, but rises back to its max frequency within a second.
I tried clean flashing OOS 5.0.3 (zip from OP website), I'm not rooted, no custom kernel (all stock basically). It seems to happen after a few hours and not as soon as the device is turned on.
I'm wondering if it's a kernel problem/bug or something else (play services for example). I'd really like to know if anyone else experienced it and if anyone got it fixed.

are you using a custom kernel or root?
if so download elementalx or any kernel editing tool and change the cluster back to 300mhz
i find i have to do this for the cluster to scale back down

You can try New Kernel by @jgcaap.
It's probably the best kernel for this phone with amazing performance/smoothness/battery.
In the latest build the idle freqs are back to normal after OnePlus mess/faulty optimisation in OB2.
https://forum.xda-developers.com/oneplus-5t/development/newkernel-t3710363
If your CPU doesn't idle it can also be an app running in background and hogging cpu time.