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?
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?
Could anyone please tell me the settings and profiles that will give my x10 mini the best battery save? thanks
actually there is already a preset for that ..the "powersave" one..
Easy, just put both bars in 122880MHz..
Your phone are going to be rrrrreeeaaaallllyyy slow, but you save lots of milliamps
Use ondemand only. And set min to 122 and max to 600.
I use a profile when screen is off that set min to 128 and max to 320, ondemand too.
Step 1: Once the app has downloaded from the market open it.
Step 2: Hit auto recommend speeds on the first boot up of the app.
Step 3: Click the profile tab at the top.
Step 4: Hit Add Profile.
Step 5: The profile button selects what happens for the CPU to under clock or over clock. The max is the max the CPU will reach; the min is the minimum the CPU will reach.
Step 6: Profile: Screen off. Max: set to minimum. Min: set to minimum. Scaling: set to Conservative. Priority: set to 100. Press okay, and hit Enable.
Thanks to Ultralinks
Has anyone had problems with random freezes and reboots with SetCPU installed? I've had a couple random reboots, so for now I've uninstalled SetCPU to see if the problem goes away. I also have Advanced Task Killer installed but it wasn't set to kill tasks automatically.
raiderkilo said:
Step 1: Once the app has downloaded from the market open it.
Step 2: Hit auto recommend speeds on the first boot up of the app.
Step 3: Click the profile tab at the top.
Step 4: Hit Add Profile.
Step 5: The profile button selects what happens for the CPU to under clock or over clock. The max is the max the CPU will reach; the min is the minimum the CPU will reach.
Step 6: Profile: Screen off. Max: set to minimum. Min: set to minimum. Scaling: set to Conservative. Priority: set to 100. Press okay, and hit Enable.
Thanks to Ultralinks
Click to expand...
Click to collapse
Setting SetCPU like that is not very smart. For example, You have Your screen off, someone is calling You, what happens? You get the call ringer after few seconds (sometimes even 10-15!). Reminds of old Symbian versions? But just this. Next example - You have Your screen off, and You receive sms. What happens if You are using Handcent, and have to go to the app manually after phone wakes up? It takes ages... But if You have more than 1000 massages in Your inbox, and a new one come, and You get it after screen wakes up it can even lead to a reboot.
Lets add some random weird situations if You are listening to Your player while the screen is off... using some third party apps, etc...
Setting the minimum CPU for the screen off is not a good idea. Don't do that, or the phone will fail You in most unwanted cases.
so what are you guys using?
I am 122-600 on normal ondemand
and screen off on 122-256 ondemand
Anyone with better profiles?
just dont overclock!!!
why not? I see you are running 729/600.
WHY is your min 600?
Use smartass governor - auto profile, just upgrade to gingerbread.. best profile yet..
Set normal use 122Mhz-729Mhz 100% Priority
Set for charging: 122Mhz-245Mhz (or similar) - 100% Priority
Set for screen off 122-245 (or similar) - 100% Priority
^ this saved me battery when I used my phone for so much else besides calling and texting.
for good batter backup....set the minimum as 122Mhz and the max as 480 Mhz....anything above 748 and below 480 will get u into "restart & restore"...however, there is a overclock module allowing you to overclock to 825 Mhz (but dats juss fr "testin"...u'll lose battery like a freak and will get awfully hot readings)
achyut said:
for good batter backup....set the minimum as 122Mhz and the max as 480 Mhz....anything above 748 and below 480 will get u into "restart & restore"...however, there is a overclock module allowing you to overclock to 825 Mhz (but dats juss fr "testin"...u'll lose battery like a freak and will get awfully hot readings)
Click to expand...
Click to collapse
Only a handful devices supports being clocked to 825Mhz but it's very dangerous.
I doubt you can raise the clock speed to 825Mhz without the phone freezing up.
ruifung said:
I doubt you can raise the clock speed to 825Mhz without the phone freezing up.
Click to expand...
Click to collapse
Some have succeeded, but I doubt their phones lasted very long after that.
Just wondering, is the phones processor under the right side of the keyboard? cause after a few minutes @ 710Mhz, that area is hot. Since I switched to the smartass governor, it rarely is hot anymore (due to the fact it mostly spends time @ 245/320Mhz
Um... question?
Shouldn't the phone go into deep sleep when the screen is off with no cpu activity?
Also install cpu spy and see what the cpu is doing for how long.
https://market.android.com/details?id=com.bvalosek.cpuspy
1. The cpu does not make the most heat... it's the 3G radio.
2. Cpu should deep sleep automatically.
My OC prifile for mini pro:
Standard profile- 122 - 825mhz
If Battery < 15% then 122 - 600 "this gets rid of crashes due to low power OC"
Also.. i asked some of the developers that made the modules for overclocking and undervolting.
It's undervolting there is no upward voltage bump so it can't really nuke a cpu.
But you can nuke the power circuits if you use heavy internet on 3G and charge at the same time.
How can I put over 600 Mhz?
My SetCPU makes 600 Mhz the max. I want to put just on 700, but I can't. What is the problem?
@Felimenta97:
You don't have any overclock-enabler module installed/insmodded or if using any CM-based ROM, the corresponding setting is disabled.
I'm using smartass with 122-320 for screen off and ondemand with 320-729 for normal, no problems so far
The max MHz I could get was 729MHz, 748MHz worked but after some time the CPU got 'pegged' as said in the logcat
Tried the 825MHz setting that only caused a freeze and boot loop, forcing me to do some fast adb commands to get rid of the overclock
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
To give everyone who wants to start over/underclocking there Razr's a head-start with some values, I think it would be best to gather some real-world data from the XDA community. You can drastically reduce your device's power consumption by undervolting, extending your battery life.
The data presented in this thread should be used as a general guideline, and will not be stable on all devices. At such a small die size (~45nm), imperfections in the semiconductor are unavoidable, and as such, each device will have a (slightly) different stability point. That being said, it's a lot easier to over/underclock properly when you have a set of known, working values on other devices (even acknowledging the fact that all CPUs have different stability points).
I personally have left my phone at stock speeds, but undervolted the CPU drastically to improve my battery life. For the technically inclined, power consumption of a CMOS circuit decreases quadratically as a function of voltage. So for the majority, halving the voltage of a CPU at the same frequency will reduce the power consumption to only one quarter of the original.
So, without further ado, here are my new set V_SEL values (as well as the stock, original ones). I manually tested the undervolted settings using the free StabilityTest application, which cycles through all clock frequencies in the table below, and ensures the CPU is stable at all frequency/voltage combinations.
Code:
Frequency | Stock | Undervolted
[MHz] | [V_SEL] | [V_SEL]
-------------------------------------
1200 | 61 | 45
1000 | 61 | 38
800 | 55 | 31
600 | 43 | 28
300 | 26 | 18***
(aside: does anyone know what units the V_SEL values are in?)
After the change, not only does the phone consume a lot less power (I can manage over 3 days on a single charge now, before it was around 2), it also gets less hot under use as well. Note that the values I got above do have some room for further adjustment, but they're very close to the minimum voltage values (the phone is very unstable when V_SEL = 40 at 1200 MHz).
*** Edit: You need to set the minimum voltage in the Calibration menu in QuickClock Advanced to set V_SEL lower than the stock value of 26 (thanks spikegibeault).
For those who are curious, you can manually set the V_SEL and clock speed values without using a tool by simply executing the following script (must be root, and should be done on every boot since the values revert to the default when the phone reboots).
Code:
echo 1 300000000 26 > /proc/overclock/mpu_opps
echo 2 600000000 28 > /proc/overclock/mpu_opps
echo 3 800000000 31 > /proc/overclock/mpu_opps
echo 4 1000000000 38 > /proc/overclock/mpu_opps
echo 5 1200000000 45 > /proc/overclock/mpu_opps
echo 0 1200000 > /proc/overclock/freq_table
echo 1 1000000 > /proc/overclock/freq_table
echo 2 800000 > /proc/overclock/freq_table
echo 3 600000 > /proc/overclock/freq_table
echo 4 300000 > /proc/overclock/freq_table
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 300000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Note that in the script above, I changed the minimum V_SEL to 26 so most people can just try the script after installing the kernel modules. To go lower than 26, you still need to use QuickClock Advanced to change the Calibration values. If anyone knows what value is modified in the system, please let me know so we can avoid having to use a discrete application (and thus, can simply use shell scripts to set all values).
Thanks, I was weary of changing the vsel of my phone because I didn't want to go through the trial and error of changing over and over again. My phone is underclocked, undervolted and stable.
How can I undervolt my Maxx? I've under and over clocked but I've never messed with voltage. I'm also running eclipse 1.3
Thanks
Sent from my DROID RAZR using XDA
prsterero said:
How can I undervolt my Maxx? I've under and over clocked but I've never messed with voltage. I'm also running eclipse 1.3
Thanks
Sent from my DROID RAZR using XDA
Click to expand...
Click to collapse
Just flash the .zip found here and install Quickclock Advanced. Mess with Vsels.
Leviathan26 said:
Just flash the .zip found here and install Quickclock Advanced. Mess with Vsels.
Click to expand...
Click to collapse
found where? i dont see a zip on this thread and no link haha. just in case your talking about the mo_simp_1.5 zip thats already flashed with the 1300mhz overclock script. i tried undervolting but any values i change when i exit out it reverts back even if i hit save. i tried changing the values in quickclock-advanced-scripter and i tried toggling the fulledit option found in the advanced menu as well.
Edit: now it says vsel unknown and when I go to advanced - scripter the vsel values are listed as null
prsterero said:
found where? i dont see a zip on this thread and no link haha. just in case your talking about the mo_simp_1.5 zip thats already flashed with the 1300mhz overclock script. i tried undervolting but any values i change when i exit out it reverts back even if i hit save. i tried changing the values in quickclock-advanced-scripter and i tried toggling the fulledit option found in the advanced menu as well.
Edit: now it says vsel unknown and when I go to advanced - scripter the vsel values are listed as null
Click to expand...
Click to collapse
Yeah, that is what I meant, sorry, forgot to put a link there. I'm sorry, I can't help you with that problem, I've never had it.
prsterero said:
Edit: now it says vsel unknown and when I go to advanced - scripter the vsel values are listed as null
Click to expand...
Click to collapse
I've noticed that bug on occasion, and was always fixed when I restarted my phone... With Quickclock, once I enabled the Full Edit option, I was able to change the V_SEL values right from the Overclock menu. If you look at the overclocking scripts, try running them manually and then checking back in Quickclock Advanced to see if your changes were made. Once you have a stable and working overclock, you will probably not need Quickclock anymore (and just get an app like ROM Toolbox or a scripting app), and can just set the script to work on boot.
I added my script to the original post, so you can see how it looks (must be run as root).
As an aside, does anyone know why my phone just crashes whenever I set a V_SEL value less than 26? (It never used to before I recovered back to the pre-patch and re-applied it, not sure what else I changed...)
I believe I successfully undervolted now with a 1300mhz over clock 300mhz is set to 18 and seems to be running fine
Edit: I ran the stress test in quickclock for 100 seconds and got 2 lag spikes and reached 91 degrees. Not sure if the lag spikes is a good result or not since this is my first experience under volting
Sent from my DROID RAZR using XDA
1500 MHz at 63 vsel running stable, i havent messed around much. i've beeen keeping it at 1300 at 60 for daily use
also, when using 18 as a vsel for 300mhz my system crashes
i'm running eclipse rom
Edit, after changing the bare minimum under calibration to 20 and setting at 20 i'm running smooth
spikegibeault said:
Edit, after changing the bare minimum under calibration to 20 and setting at 20 i'm running smooth
Click to expand...
Click to collapse
Thank you so much, this is what fixed it. I had to set the calibration value, reboot, and then I was able to set my V_SEL back to 18.
Does anyone know what value is modified when this is set? It would be nice to know, so we can have an initialize script and a boot-up script (so you don't need to keep a discrete application installed once your OC is fine and running).
after a reboot since the values reset i went to change them again and everytime i do the phone freezes up and i have to do a hard shut down. how come it worked before with the same values and now it wont? nothing has changed in the system
edit: i think the problem was it reset itself to a max of 1200mhz when before it was 1300 so the value that i used before at the 1300mhz level wasnt working with the 1200, causing the phone to freeze.
edit 2: actually it just froze again haha. maybe the 1300mhz kicked back in after i did my editing or something.
edit 3: seems like i cant do any undervolting anymore because after about 5 minutes the phone freezes.
prsterero said:
edit 3: seems like i cant do any undervolting anymore because after about 5 minutes the phone freezes.
Click to expand...
Click to collapse
What values are you using? Did you modify the appropriate parameters in the Calibration menu (assuming you're using QuickClock Advanced)? Remember, not all phones are equal, so you might have to raise the voltages I posted a little bit.
I'm still going strong on my posted settings (currently 35 hours on battery, with 40% battery left). Stock speeds but undervolted.
ice9tech said:
What values are you using? Did you modify the appropriate parameters in the Calibration menu (assuming you're using QuickClock Advanced)? Remember, not all phones are equal, so you might have to raise the voltages I posted a little bit.
I'm still going strong on my posted settings (currently 35 hours on battery, with 40% battery left). Stock speeds but undervolted.
Click to expand...
Click to collapse
im using the same values you listed, which before was working just fine. but after that first reboot it wont work anymore. the parameters in the calibration menu are as follows: 18, 300, 1560, 1300, 300. which made me realized the stock max speed was still set to 1300 but i put it back to stock 1200 as im typing this. tried the same values again after changing the max stock speed in the calibration menu and it froze instantly after applying ^_^
edit: just out of curiosity how much have u used the phone for that kinda battery life? and screen on time?
edit 2: i just changed the values to 58, 55, 45, 38, 26 and so far no freezing. to do this as trial and error would i have to keep going down more and more till i freeze to find the lowest values possible? and would i have to do one clock speed at a time or bring them all down 1 unit then test? also, isnt the biggest one the 300mhz voltage since thats where it is most of the time with the screen off? so with it staying the same as stock value, it wouldnt make much of a difference?
ice9tech said:
Did you modify the appropriate parameters in the Calibration menu (assuming you're using QuickClock Advanced)?
Click to expand...
Click to collapse
How are you getting quick clock adv installed, i had purchased for my og DROID, but it says not compatible with my RAZR.
Sent from my DROID RAZR using xda premium
Ronin3178 said:
How are you getting quick clock adv installed, i had purchased for my og DROID, but it says not compatible with my RAZR.
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
I downloaded it on my computer and moved it to the downloads folder then installed from there
Sent from my DROID RAZR using XDA
prsterero said:
I downloaded it on my computer and moved it to the downloads folder then installed from there
Sent from my DROID RAZR using XDA
Click to expand...
Click to collapse
Ok, I went around a long way and installed on my NookColor and then backed up thru TB sync'd to dropbox and my pc, unzipped the apk, shared the apk thru dropbox to my RAZR.......
Anyway, with QC Adv, anytime I try editing or using the auto-cal function, the app freezes and nothing happens. The only way I can get it to do anything is to force stop and clear data -> back to square one.
When I go into CPU Speed scale and hit the calc, this is what populates.
1200 75
1000 64
800 53
600 44
300 29
BTW, just thought of this, what is everyone using GB or ICS? I am on ICS 6.14.75XT912.Verizon (leak from early April/late March) That could be my problem too.
Ronin3178 said:
Anyway, with QC Adv, anytime I try editing or using the auto-cal function, the app freezes and nothing happens. The only way I can get it to do anything is to force stop and clear data -> back to square one.
Click to expand...
Click to collapse
I've noticed the same behaviour, and I think it's fairly well known by most users. I wouldn't worry about it though, it's not difficult to manually overclock/undervolt your phone.
Ronin3178 said:
When I go into CPU Speed scale and hit the calc, this is what populates.
[...]
Click to expand...
Click to collapse
That's what I get as well, and note that they are higher values than even the stock ones! Why, you ask?
Remember, the purpose of QuickClock is to make overclocking easy for most users. Those values are calculated based on predetermined "guaranteed" stable values by the application developer. I would not exceed the stock values I posted on the stock page under any circumstances, unless you are very familiar with overclocking (especially since you should be able to get a decent overclock without modifying the V_SELs). By all means though, if you want to reduce the V_SEL values (and it's stable on your phone), you should - it saves quite a bit of power (hit over 2 days on my last charge).
Also, I'm on GB, but I think you should be fine doing this with ICS (the kernel module should work with both IIRC).[/QUOTE]
ice9tech said:
I've noticed the same behaviour, and I think it's fairly well known by most users. I wouldn't worry about it though, it's not difficult to manually overclock/undervolt your phone.
Click to expand...
Click to collapse
Ok, is there a tutorial somewhere on how to do the undervolting manually? Because QCA is useless on this phone, it doesn't even load the modules for testing vsel or clockspeed on my phone. The script editor only looks like it shows speed.
Sent from my DROID RAZR using xda premium
Ronin3178 said:
Ok, is there a tutorial somewhere on how to do the undervolting manually? Because QCA is useless on this phone, it doesn't even load the modules for testing vsel or clockspeed on my phone. The script editor only looks like it shows speed.
Sent from my DROID RAZR using xda premium
Click to expand...
Click to collapse
In quick clock go into advanced and enable full edit. Then go to over clock and edit the voltage on the right side of the screen
Sent from my DROID RAZR using XDA
can we do this using SETCPU?
Just wondered if anyone can help me with this.
If I have an app open, ie messages and the screen times out, the phone locks and I have to take out the battery to reset. This dones not happen if I am on the home screen though.
I have root and I'm running Foxhound 2.7 I have also tried different ROMs and the same thing happens. I have done a megawipe are reinstalled several times.
Any idea what is going on?
syztemlord said:
Just wondered if anyone can help me with this.
If I have an app open, ie messages and the screen times out, the phone locks and I have to take out the battery to reset. This dones not happen if I am on the home screen though.
I have root and I'm running Foxhound 2.7 I have also tried different ROMs and the same thing happens. I have done a megawipe are reinstalled several times.
Any idea what is going on?
Click to expand...
Click to collapse
try changing the kernel.
Governor Setting
1-) Which governor are you using. I got similar problems with "zzmove battery" governor.
2-) If you are using undervolt (UV) values dont make any change for 200mHz step. (or using standar -50mV, -75mV UV options try lower values)
Now using Googy Max Kernel and pegasusq governor and got no problem again.
kadiremrah said:
1-) Which governor are you using. I got similar problems with "zzmove battery" governor.
2-) If you are using undervolt (UV) values dont make any change for 200mHz step. (or using standar -50mV, -75mV UV options try lower values)
Now using Googy Max Kernel and pegasusq governor and got no problem again.
Click to expand...
Click to collapse
Not undervolting but I'll give that kernel a try as I am using zzmoove at the moment with Boeffla.
Thanks