Post Your Overclock/Underclock/Undervolt Results - Motorola Droid RAZR

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?

Related

CPU Tuner

Has anyone tried this app? I'm getting improved battery life from how it handles the processor in idle mode. After 3 hours I normally would lose 10% being idle, now 2%. Using it the same with same background apps running. Its free too.
Sent from my Dell Streak using XDA App
I'm using SetCPU with similar results
default (1190/245), battery< 66 (768/245), battery < 33 (460/245), screen off (460/245)
also using "juice defender"
Radimus said:
I'm using SetCPU with similar results
default (1190/245), battery< 66 (768/245), battery < 33 (460/245), screen off (460/245)
also using "juice defender"
Click to expand...
Click to collapse
Are you on streak droid 1.5.1?
when I use setcpu it cause my device to reboot on it's own.
I uninstalled it and all is well now but want to put it back because it did really well for my battery life.
Forgot what frequencies I had set in the profiles but I was using on demand scaling.
I had charging/full oc'd, screen off between the lowest and something around 450, batt < 30% same thing, and temp > 50c between lowest and 768
I'll reinstall it now and set your profiles and see if that helps.
Also using adw.launcher
---UPDATE---
So i reinstalled SetCpu and changed the lowest from 128 to 245 and no longer rebooting.. think that was the issue.
fone_fanatic said:
Are you on streak droid 1.5.1?
when I use setcpu it cause my device to reboot on it's own.
I uninstalled it and all is well now but want to put it back because it did really well for my battery life.
Forgot what frequencies I had set in the profiles but I was using on demand scaling.
I had charging/full oc'd, screen off between the lowest and something around 450, batt < 30% same thing, and temp > 50c between lowest and 768
I'll reinstall it now and set your profiles and see if that helps.
Also using adw.launcher
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
...And does it still keep rebooting? I notice that on re-boot, it says max speed something like 768MHz, even though both slider bars are set to minimum.
I set screen on to be performance, put streak into standby and left in my pocket for an hour. I cam back to find my streak pretty warm abd the battery practically flat?? Don't know if this was a setCPU issue as it's never happened before???
odyseus said:
...And does it still keep rebooting? I notice that on re-boot, it says max speed something like 768MHz, even though both slider bars are set to minimum.
I set screen on to be performance, put streak into standby and left in my pocket for an hour. I cam back to find my streak pretty warm abd the battery practically flat?? Don't know if this was a setCPU issue as it's never happened before???
Click to expand...
Click to collapse
stick this file in sdcard
and start setcpu.
then menu device selection
Show other frequency sets
scroll down to Custom Frequencies
ok
ok
and it should work fine from then on in with steves O/C kernels( you only need do it once)
and it will set from 248 -1194Mhz if you want to add the extras over voltage O/C clocks from 1.51 then you can edit the setcpu.txt manually.
I don't use the last two as on mine I get worse scores than with 1194mhz so I didn't include them in that text file
yeaaah
Yeaah, CPU Tuner is awesome app. A set CPU frequency on my HTC Wildfire on 691 MHz and phone is faster

Motorola Atrix - SetCPU issues

Hi Guys,
I need a real problem solver here.
I'm having some issues with with SetCPU on my newly rooted Motorola Atrix (2.2.2 Froyo). It's an Australian model with Telstra branded firmware.
I recently rooted it using this guide.
My SetCPU profiles are as follows:
>90% - 750 max 200 minimum 90 priority
Screen off - 216 max 200 min 85 priority
>75% 600 max 200 min 80 priority
>50% 500 max 200 min 75 priority
>20% 300 max 200 min 60 priority
The problem?
As my battery decreases, SetCPU does not change to the appropriate profile. The "Scaling" option is also greyed out.
I hope someone can shed some light in this for me.
Thank you in advance.
Edit: My friend has an Atrix which is nearly an exact copy of mine without any issues what so ever. I find this bizarre.
Solved.
For anyone who wants to know how, simply reverse the priorities.
i.e Make it so higher profiles have lower priorities, and lower profiles have higher priorities.
Scale Drop-down button greyed out
Did you also find a solution to your scaling button being unavailable?
I'm running HOME BASE MEGA 3.1 - EXT4 1.3GHZ DEBLURRED with 4.5 UPDATE and I the scale button is greyed out.
Any ideas?
marhodges said:
Did you also find a solution to your scaling button being unavailable?
I'm running HOME BASE MEGA 3.1 - EXT4 1.3GHZ DEBLURRED with 4.5 UPDATE and I the scale button is greyed out.
Any ideas?
Click to expand...
Click to collapse
I have the same problem. I searched around a bit and didn't find any answers.
Anyone?
Thanks.
jaideepn said:
I have the same problem. I searched around a bit and didn't find any answers.
Anyone?
Thanks.
Click to expand...
Click to collapse
Scaling requires a scaling governor to be compiled into the kernel. I assume you're using faux's kernel in that rom, and I don't think he has any scaling governers in his kernel.

[Q] Setcpu Script commands???

I have a script that i use in the init.d folder to keep some apps in memory i was wondering what the commands are to set the cpu frequency's and governor.
Im just trying to keep it simple i just want a the text for a startup script to set the minimum cpu freq and the gov state
example
Min 450
Max 1000
Gov: Performance
Im assuming this would be a busybox script im using zepplins bulletproof app code and i just wanted to throw some more code in there to play with cpu speeds. In a file with no extension in init.d folder.
Would this work?
Code:
#!/system/bin/sh
#
# By Mike Lierman
# www.mikelierman.com
#
# You may use, reuse, and modify freely.
#
# This script sits in the background and waits for Android to tell it that the phone is sleeping. It
# will then set a gentle 456MHz max cpu frequency, and turn off the second core; which cures insomnia.
FREQENCY_MAX="1000000" # 1GHz
FREQENCY_MIN="250000" # 250MHz
do
echo $FREQENCY_MIN > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo $FREQENCY_MAX > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
echo $FREQENCY_MIN > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq;
echo $FREQENCY_MIN > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq;
fi
done
no it wouldnt work because in the 2.3.3 kernel, it ignores what ever you tell it and does what ever it wants. you can try it but then look at the frequencies and see that it went back to 216 and 1ghz. in addition if you are using the performance governor it will run at max 100% of the time. thats just how the governor works
Just wanted to say if u take 03cpufreq from navens init.d hack and put it in init.d folder. Change permission and owners and edit the values to what u want in the script for min/max and go to setcpu u CAN use the slider bars to hold a min/max and change governor from performance/powersave and it WILL hold the value u set. I have been doing this.for over 5 hours now and it hasn't ONCE dropped below the 456 I set it at for min.
ashclepdia said:
Just wanted to say if u take 03cpufreq from navens init.d hack and put it in init.d folder. Change permission and owners and edit the values to what u want in the script for min/max and go to setcpu u CAN use the slider bars to hold a min/max and change governor from performance/powersave and it WILL hold the value u set. I have been doing this.for over 5 hours now and it hasn't ONCE dropped below the 456 I set it at for min.
Click to expand...
Click to collapse
ive been playing around with all those scripts for a day or 2 and i have been using cputuner to track what freq im at. it will stay until the kernel disables the 2nd core then it goes back to normal. i just did what you said and put it at 608 (its just what ever i clicked on) watch it stay up there until # of cores was 1 then i did something and back to 216. use cputuner to check your freq stats. im willing to bet that you have time spent in 216 and 312. i even used both the script to use performance governor and it runs it at what ever freq it wants. who ever set up this kernel was a ****tard
gnuworldorder said:
ive been playing around with all those scripts for a day or 2 and i have been using cputuner to track what freq im at. it will stay until the kernel disables the 2nd core then it goes back to normal. i just did what you said and put it at 608 (its just what ever i clicked on) watch it stay up there until # of cores was 1 then i did something and back to 216. use cputuner to check your freq stats. im willing to bet that you have time spent in 216 and 312. i even used both the script to use performance governor and it runs it at what ever freq it wants. who ever set up this kernel was a ****tard
Click to expand...
Click to collapse
Ill check that out. There gotta be a way to set both cpus. Some type of script or something. Maybe im wrong tho.

[FIX] Screen Brightness lowered due to temperature

Hi guys,
I did a bit of looking around for a way to fix the problem I am having and some others may have as well. It seems like my screen brightness is turned down CONSTANTLY due to temp of the phone. Well not anymore!
***I AM NOT RESPONSIBLE FOR YOUR PHONE CATCHING ON FIRE AFTER YOU DO THIS. It has worked for me but could potentially damage your phone.***
I am assuming you need to be rooted at the least.
METHOD 1 Safest for now!
1. Download a file manager that lets you have access to the root directory IE: /
2. go to /ETC and find a file named thermaled.conf
3. open the file in a text editor.
4. Raise the values of the thresholds as shown in red
5. Reboot your phone and enjoy!
[pa_therm0]
sampling 5000
thresholds 49 52 55 59
thresholds_clr 49 52 55 59
actions cpu+lcd+gpu+battery cpu+lcd+gpu+battery cpu+lcd+gpu+battery cpu+lcd+gpu+battery
action_info 1512000+255+400000000+0 1512000+237+325000000+0 1188000+215+200000000+1 1188000+202+200000000+1
METHOD 2 (not as safe as Method 1
1. Download a file manager that lets you have access to the root directory IE: /
2. go to /ETC and find a file named thermaled.conf
3. open the file in a text editor and remove the LCD references in the file and save.
4. Don't forget to remove the extra "+" symbol so you don't have two "++" together.
5. Reboot your phone and enjoy!
[pa_therm0]
sampling 5000
thresholds 35 42 44 46
thresholds_clr 34 40 43 45
actions cpu+lcd+gpu+battery cpu+lcd+gpu+battery cpu+lcd+gpu+battery cpu+lcd+gpu+battery
action_info 1512000+255+400000000+0 1512000+237+325000000+0 1188000+215+200000000+1 1188000+202+200000000+1
Would a better solution be to edit the values higher, and leave the lcd references ?
adfurgerson said:
Would a better solution be to edit the values higher, and leave the lcd references ?
Click to expand...
Click to collapse
You are probably right. However I haven't the slightest idea on how much to change the values. Someone smarter than me can pick it up from here lol or at least more willing to tinker with the values. I am not a dev nor claim to be. I am just trying to make our experience with this phone a bit better. I haven't had any adverse effects by doing this YET.
Actually I think I may have figured out how to just change values! Raise the threshold values in the "pa therm 0" column from 35 42 44 46. Add maybe 2-3 on top of those numbers? I am not sure but it may work?
Looks like it would be easier/safer to change the temperature thresholds (35C seems low) to be higher so that it doesnt start throttling until a higher temp. It seems that the throttle is CPU Freq, then display brightness (0-255), then GPU freq (with extra 0's) and I am not sure what that battery 0 or 1 does..
UPDATED OP!!!! Safer method!!! Send thanks if this works for you!
Think I can get this thread in the Android Development section Mods?
59C seems pretty high, especially for the battery. Might want to lower that upper limit a bit.
I get an error when trying to save the changes. Any reason for that?
SkriblZz said:
I get an error when trying to save the changes. Any reason for that?
Click to expand...
Click to collapse
Did you enable R/W for that folder? Or is it still showing RO? RO= read only; RW= read/write
Nastybutler said:
Did you enable R/W for that folder? Or is it still showing RO? RO= read only; RW= read/write
Click to expand...
Click to collapse
Ah. I've been using a file manager app, haven't seen an option for such. I assume then I need to access the file on a computer. Quite honestly, not sure how to access the root from a computer.
SkriblZz said:
Ah. I've been using a file manager app, haven't seen an option for such. I assume then I need to access the file on a computer. Quite honestly, not sure how to access the root from a computer.
Click to expand...
Click to collapse
Never mind. I edited the file via Android commander.
Well.. I have used the Method 1 but still feels like it is not working. Though it changes the brightness, but I personally think brightness adjustments were much better in galaxy devices than in Optimus G. Is there anyway to change it to those of Galaxy devices?
woopsgoops said:
Well.. I have used the Method 1 but still feels like it is not working. Though it changes the brightness, but I personally think brightness adjustments were much better in galaxy devices than in Optimus G. Is there anyway to change it to those of Galaxy devices?
Click to expand...
Click to collapse
Figuring this is an LG device with totally different sensors...no. This just allows no thermal throttling
Sent from my LG-E970 using xda app-developers app
Anyone else got this working? Especially the safer method.
Shadow on the screen by means of temperature
Thanks for the input. I live in Dominican Republic, here enough heat, now decreased enough temperature, before they burned my fingers, now gets less than before. Only thing is that I to become spots on the screen that were formed by medium to temperature, think they are deleted eventually, because it avece when hard a time without using my device feel they removed a little
I've got thermal-8960.conf and two other numbered thermal files in addition to thermal.conf
Is that normal anyone else verify? One for each core maybe?
OG e970 stock+
mystery emotionz 5.1
1.72 GHz oc/uv
Try this http://forum.xda-developers.com/showthread.php?t=2296447

Lollipop Stock CPU min stuck @ 787MHz? WTF?

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?

Categories

Resources