I do not know what is causing this, but no matter what current JellyBean rom I flash, I cannot adjust my MIN and MAX cpu power. As soon as I toch it it defaults to 100/100 and I can't adjust it anymore. Anyone know what is going on?
nafeasonto said:
I do not know what is causing this, but no matter what current JellyBean rom I flash, I cannot adjust my MIN and MAX cpu power. As soon as I toch it it defaults to 100/100 and I can't adjust it anymore. Anyone know what is going on?
Click to expand...
Click to collapse
Just outta curiosity, are you by any chance using devil kernel with the JB roms that you are trying?
If this is the case, I've noticed that the devil control app tends to override any changes made with say nstools...
I'm not sure if this is the case, since I myself have done very little testing on JB roms...but food for thought.
Also, how are you changing your values exactly? Nstools? Voltage control? Baked in settings? Some other app?
Yeah it its the Devil kernel. Can you point that out in the HEllyBean thread, because doesn't seem anyone believes me.
I can adjust max in performance settings but it won't let me change minimum.
Edit: just figured this out, if you have cpu when screen off set in dkc app, it will not let you set CPU min in performance to anything other than that minimum setting.
sent from the depths of helly bean
samsgun357 said:
I can adjust max in performance settings but it won't let me change minimum.
Edit: just figured this out, if you have cpu when screen off set in dkc app, it will not let you set CPU min in performance to anything other than that minimum setting.
sent from the depths of helly bean
Click to expand...
Click to collapse
That's what I thought!
Thanks for confirming dude
Related
i have it set up as follows:200MHz Minimum Slider, 1200MHz Maximum Slider, Conservative mode and just followed the instructions as per https://sites.google.com/site/projec...allation-guide, but every time i boot up my phone and i start setcpu my readings are 1000max 100min but my sliders are set as 200MHz Minimum , 1200MHz Maximum. i know there is an option to set on boot but according to the link it states not to:
"Do not configure profiles, do not configure for set on boot. Set manually. There is a known problem with SetCPU that incorrectly configures your system at boot if selected. "
so if i want the settings to stick i have to click on the slider and it sets them to 200MHz Minimum , 1200MHz Maximum.
any suggestions as doing this manually is a pain....
adinis78 said:
i have it set up as follows:200MHz Minimum Slider, 1200MHz Maximum Slider, Conservative mode and just followed the instructions as per https://sites.google.com/site/projec...allation-guide, but every time i boot up my phone and i start setcpu my readings are 1000max 100min but my sliders are set as 200MHz Minimum , 1200MHz Maximum. i know there is an option to set on boot but according to the link it states not to:
"Do not configure profiles, do not configure for set on boot. Set manually. There is a known problem with SetCPU that incorrectly configures your system at boot if selected. "
so if i want the settings to stick i have to click on the slider and it sets them to 200MHz Minimum , 1200MHz Maximum.
any suggestions as doing this manually is a pain....
Click to expand...
Click to collapse
Until the bugs are fixed in the program, get used to manually setting it every time you re-boot your phone. Thems the breaks I'm afraid. Gotta set it manually, there is no work around until it gets fixed inside the program.
Dragoth12 said:
Until the bugs are fixed in the program, get used to manually setting it every time you re-boot your phone. Thems the breaks I'm afraid. Gotta set it manually, there is no work around until it gets fixed inside the program.
Click to expand...
Click to collapse
thank you, hoping there was another way
adinis78 said:
thank you, hoping there was another way
Click to expand...
Click to collapse
I actually just barely ran across this in another thread, I can't vouch for how it works as I am just relaying info, check out this post:
http://forum.xda-developers.com/showpost.php?p=8725283&postcount=10294
If it works, you will not even have to use SetCPU. Good luck.
Dragoth12 said:
I actually just barely ran across this in another thread, I can't vouch for how it works as I am just relaying info, check out this post:
http://forum.xda-developers.com/showpost.php?p=8725283&postcount=10294
If it works, you will not even have to use SetCPU. Good luck.
Click to expand...
Click to collapse
hmm sounds like an idea but how do i access /system/etc/init.d and i don't mind using SetCPU as i have a profile saved so that if my phone starts to overheat it will revert to the setting i have set up, i might just stick with it until SetCPU is fixed.
Dragoth12 said:
I actually just barely ran across this in another thread, I can't vouch for how it works as I am just relaying info, check out this post:
http://forum.xda-developers.com/showpost.php?p=8725283&postcount=10294
If it works, you will not even have to use SetCPU. Good luck.
Click to expand...
Click to collapse
That idea is now brain fart? uhhhhhh. hahaha.
I'm also using 1.9.1 currently, and I use profiles, and use the "autodetect" option in setcpu. Haven't had any problems since.
Even though the sliders say 100min/1000max, it shows 200min/1200max.
PaiPiePia said:
That idea is now brain fart? uhhhhhh. hahaha.
Click to expand...
Click to collapse
haha, that's funny....guess it doesn't work.
Sorry this is somewhat off topic from the thread...but what's the benefits/pros of using SetCPU? And are there any negatives/cons to using it?
The option exists in Glitch's kernel recovery. What does it mean? Should I have enabled it?
Thank you!
The phone will work fine without it, though you can set it to whatever you want. I set it to conservative. All it does is make it so that it changes the cpu governor when you turn the screen off.
Sent from my MIUI SCH-i500
sageDieu said:
The phone will work fine without it, though you can set it to whatever you want. I set it to conservative. All it does is make it so that it changes the cpu governor when you turn the screen off.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
+1... plus you save a lot a battery that way.
Hi guys i have a tiny problem i need clarifying please.
Before anyone says anything i already asked this question and no one seemed to be able to answer it to me. So here it goes.
My question is can we combine the two. What i mean is use Voltage Control to set cpu Voltages and use No Frills to adjust Cpu clock speeds. Voltage Control on my latest rom that i am on Hyperdroid latest version does not save my overclocking and reverts back to stock frequencies 1200Mhz-200Mhz even after i save it on boot. I leave it to reboot for a few minutes till the phone settles and go to check it and governor and i/o schedulers are saved and my voltages also but the only thing that reverts back is the cpu clock frequencies. When using No -Frills though it saves my overclocking.
So my question can i use one app to overclock and the other to undervolt and use them both at the same time?
I know stupid question and i am pretty sure that i know the answer already but if i can get a few opinions regarding the matter i would appreciate it..Also why on the latest firmware it reverts back to stock frequencies even when we save it on Voltage Control is it a bug or something and does anyone if it will get fixed as i really like that app since it does everything i need it to.
Thanks again
you can use both, but I don't see why, VC has also CPU sliders so you can set both parameters from one app
maranello69 said:
you can use both, but I don't see why, VC has also CPU sliders so you can set both parameters from one app
Click to expand...
Click to collapse
Yes i know that. But see the whole point of asking this question is that Voltage Control reverts my frequencies back to stock..So say i try to set my cpu clock frequencies to 1600max-200min and then save it and set on boot once i reboot my phone it reverts it back to stock frequencies...Hence why i am currently using only No frills at the moment till this issue is fixed...And hence why i was wondering if i can undervolt with one app and overclock with the other
I recently updated my stock SCH-i605 to JellyBean's ROM build 21, with saber kernel. Now, once or twice a day, it will freeze after it's been in low power / locked for 10 minutes or more. When I try to unlock it, the screen turns on, and it is frozen as the last image that was displayed (e.g. I set it down and let it go to sleep, or lock it, from the web browser, and it then shows the page) It's completely frozen, and won't do anything. The only thing I've noticed is that it will do a quick single vibrate after holding down the lock or home button for a second. The only way to fix it is to take out the battery, since no other button combos work, like the force reset/shutdown.
Has anyone seen anything like this? Any ideas on what could be causing it or how to fix it?
Raise the minimum cpu speed up from 100. Some phones can't handle that low. Use the standard 200mhz minimum and you should be fine
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Raise the minimum cpu speed up from 100. Some phones can't handle that low. Use the standard 200mhz minimum and you should be fine
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I did set the minimum speed to 100MHz it one point, but switched it back to 200 shortly after. I just double checked, and its still set to the default 200. What else could cause this?
Also, I've noticed that it only happens when I leave it at an app, it's never frozen at the home screen. I've mostly had it freeze at settings and in the browser.
Slovedon said:
I did set the minimum speed to 100MHz it one point, but switched it back to 200 shortly after. I just double checked, and its still set to the default 200. What else could cause this?
Also, I've noticed that it only happens when I leave it at an app, it's never frozen at the home screen. I've mostly had it freeze at settings and in the browser.
Click to expand...
Click to collapse
Have you undervolted or underclocked anything? Messed with the gpu speed? Used the touch wake features?
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Have you undervolted or underclocked anything? Messed with the gpu speed? Used the touch wake features?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I'd overclocked and enabled touchwake, but the issue was actually forgetting to disable the ripple effect in with the AOSP lock screen enabled.
Slovedon said:
I'd overclocked and enabled touchwake, but the issue was actually forgetting to disable the ripple effect in with the AOSP lock screen enabled.
Click to expand...
Click to collapse
Glad you figured it out buddy. Cheers. Glad to see it wasn't even saber. Good to know. btw we've all made that lockscreen ripple sleep of death on aosp lock screen error. You're not alone haha
Sent from my SCH-I605 using Tapatalk 2
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.
Here is what I did and what I see:
1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.
2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.
3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.
4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.
5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.
6) Powersaving is set to normal, not smart, or ultra.
Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
Netrunner157 said:
So I installed the Lollipop stock rom via the dload folder in the official manner by rebooting and holding vol up + power. Rom installed just fine and everything works but the CPU frequencies are driving me up the wall. This rom/kernel seems to ignore SetCpu's or No Frill Cpu's settings.
Here is what I did and what I see:
1) Yes I've commented out the build.prop entry where it says min=787 and rebooted several times.
2) On boot up I see via Setp CPU min frequency is 787. Draging the min value to any value below 787 doesn't work.
3) Sometimes after turning on the device I'll go into SetCpu and see min set to 300. However several times in the day I'll check out of paranoia and it's back to 787.
4) I've used both Set Cpu and No frils cpu app and set "Set on boot" and that does nothing. I'll often catch the min value floating @ 787Mhz. This is also confirmed by checking time in state and even when turning off the screen, I'll see the 787 usage jump but not the 300 or 384 speeds.
5) Sometimes I see really whacky ****. Like I had Set Cpu open, and the Max was changing from 1593, to 1497, to 1400, to 1100 and then back to 1497.
6) Powersaving is set to normal, not smart, or ultra.
Has anyone gotten the kernel to follow the min/max settings for CPU freq? Anyone have a solution?
Click to expand...
Click to collapse
Mpdecision.. Qualcomm closed source. Hate it.
> Have you checked to see if CPU hotplugging is turned on? If it is then it will make changing the min almost impossible.
How do I do this?
> Mpdecision.. Qualcomm closed source. Hate it.
Is this a tool that fixes this?
So many people have upgraded to Lollipop and yet how is it that I'm the only one bringing up this 787 issue?
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
This is from the program kernel adiutor program you can find here( http://forum.xda-developers.com/android/apps-games/app-kernel-adiutor-t2986129) If you turn hotplugging off you might have better luck setting the min. It will be listed as CPU hotplug in the menu.
Davinci50 said:
https://www.google.com/search?q=Mpd...ome..69i57&sourceid=chrome&es_sm=122&ie=UTF-8
Click to expand...
Click to collapse
Oh man I did not know how to use google. You opened my eyes. /s
> kernel adiutor
kernel auditor did not help, even after two reboots. i still see min stuck at 787. Is this issue perhaps solved in the lollipop pacman rom?
CM drops to 300.. Turn off mpdecision.
OK so I definitely turned off mp decision both via the app and by renaming /system/bin/mpdecision --> /system/bin/mpdecision-lolololol
Rebooted and checked setcpu and my min is still stuck at 787. Granted I check in a few times a day and sometimes I catch the min at 300 yet sometimes I catch it at 787. What else am I missing?
Moody66 said:
CM drops to 300.. Turn off mpdecision.
Click to expand...
Click to collapse
Is it a stable rom? How many reboots do you get, wifi issues, force closes etc? I'm not a fan of rom's not based off of stock rom, because of instability. I left those behind with the Note 1, Motorola Atrix.
Its in snapshot phase. Of course its stable.
Moody66 said:
Its in snapshot phase. Of course its stable.
Click to expand...
Click to collapse
Yes it might be a stable version of CM but is it stable on the Mate 2. I know the difference between stable and nightly.
Its fine. Read the cm forum thread.
@Moody66
No probably like most of the rest he wants to be spoon fed, I was able to determine what you meant in your first post about mp desicsion and determine the appropriate course of action that I wanted to take and also referenced your thread about battery life.
Make a backup, load the rom ,and test drive it like we all do.
God I love Google NO /s
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
Moody66 said:
Its in snapshot phase. Of course its stable.
Click to expand...
Click to collapse
Moody66 said:
I found a governor that replaces mpdecision. Going to add it to a build. Last two attempts I had issues. Nothing related to governor though. Soon. Pilled a nub mistake with boot.IMG. lol three year old distracting me. So all good. Should help tremendously with cpu. A couple of builds floating around with another governor that does help quite a bit.
Click to expand...
Click to collapse
So the general consensus is that Lolipop stock rom cannot have the 787min freq fixed and the solution is to switch rom's altogether? Like I said I disabled mpdecision and even renamed the binary and commented out the entry in build.prop. What else is left?
Isn't that easy. It will always default of there isn't something to takes its place.
Moody66 said:
Isn't that easy. It will always default of there isn't something to takes its place.
Click to expand...
Click to collapse
Isn't that easy. It will always default of there isn't something to takes its place.
Click to expand...
Click to collapse
what is easy? You mean to tell me stock lollipop will default to 787 until what takes it's place? No one knows?
It's stock ROM. If you want to make changes flash a ROM. Huawei isn't going to give you that customization.
Noone has made a custom kernel for it. Obviously since it has emui.
Is 787 hardcoded somewhere in this rom that it's usually defaulted to?