So I have this problem I think many of you have had before.. I put SetCPU at 768mhz out of curiosity and voila it doesnt work. Is there any trick that I could pull to modify the value back to 710 (or default) without doing a full wipe ?
Help much appreciated.
Ps. I need my cell in about 1.5 hours.. :S
problem solved:
I installed a different kernel with default clocks ftw
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 am starting to believe that the ICS kernel scales properly although some people may claim it only scales from min to max.
I noticed on the stock GB kernel, the exact same thing happens when trying to use CPU controlling apps such as setcpu. However, for BOTH GB and ICS without using CPU controlling app, I can see the in between frequencies being used. When I try adjusting the slider THEN it starts the freaking out in terms of min/max. (Rom toolbox)
I even notice the battery life worsen tremendously when trying to use setcpu, antutu, etc on STOCK frequencies. Perhaps it has to do with people trying to use CPU apps on a kernel with the perflock enabled?
With the absence of a CPU controlling app on ICS , my battery can last the SAME (not worse, for sure) as it on GB.
Perhaps this can help those who complain about bad battery life on ICS
Sent from my ADR6425LVW using XDA
You don't need to wonder anymore! Its a function built into HTC kernels called "perflock" and its function is to continually reset the values for the min and max frequencies in order to prevent other applications such as setCPU from taking control over the CPU frequencies.
I've been using SEbastianFM's ICS OC kernel with setCPU. You are correct, that it does scale properly even though the min/max frequencies hop around. If you take notice of the current frequency, its usually appropriate for the current load level.
Furthermore, if use setCPU profiles to control the CPU speed, I've noticed it prevents the kernel from periodically reverting back to its default speed and governor settings. setCPU occasionally crashes (FC's) about once a day on me, but since I have the widget on my homescreen I notice it starts right back up again within a second or two and starts controlling the CPU speed again.
I have a Tablet: AMPE A86 with following details:
Android Version: 4.1.1
Kernel version: 3.0.8+
My tab has a bad issue of frequent freezing and reboots. After searching for several months I found that, it has issue in it's kernel (or something like that) and CPU. I have used SetCPU and setting the governor "Performance" solves the freezing issue and works smoothly (No more freeze and reboots). Other governor setting cannot stop the frequent freeze issue. but problem is that setting the governor "Performance" it become too hot and drains the battery too fast. I have used "Profile" menu to control the heat like below:
Screen Off
CPU 1608-252, Governor powersave
Priority 100,Exclusive
Charging Any
CPU 1608-252, Governor performance
Priority 95, Exclusive
Battery <=35%
CPU 1608-252, Governor powersave
Priority 90,Exclusive
But it does not reduce the heating issue still in Screen off. Another thing is that, in my tablet it does not identify the Temperature of the CPU (always shows 0.0 C).
Can someone help to to resolve my issue as I am suffering with this tab for last 1 year. I also have tried the Oma's CM10.1 and AOSP 4.2.2 with no luck. Can anyone provide me any better kernel or any solution for my problem?
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?