Related
I've been experiencing lockscreen lag on all of the froyo ROMs I've flashed so far.
Tazz
KaosFroyo
etc...
Is anyone experiencing this, and have you found a work around?
Yes, I have been experiencing a lag on tazz. I just flashed it yesterday.
Sent from my Eris using XDA App
I have noticed that since the adw launcher/launcher pro type launchers rotate when you unlock the screen in a different orientation, the unlock is delayed because the phone is busy re-orienting the home screen. I've turned off the home screen rotation (I use Launcher Pro) and the lag is gone.
I actually don't have any lock screen lag with Tazz. The only time I notice a lag is when I am getting an incoming call. It takes awhile for the answer button and caller id to show up on my screen. I always think I am going to miss the call.
I am using ADW and I don't have homescreen rotation on.
I get the lag on Tazz Froyo.
Absolutely no lag on Kaos with stock launcher (not an ADW fan here). Also, no lag on CELBfroyo with launcherPro.
Folks that report lag issues coming out of sleep should report their sleep profile used with SetCPU - that's a huge wildcard that is more about the kernel's variable-frequency clock stepping behavior than the ROM.
Particularly if you are using minimum clock speeds less than 245 Mhz, or if you are also restricting the max clock to a low value.
There seem to be some pathological behaviors (even in the 2.1 OC kernels) if you use too low a clock speed, where the kernel gets temporarily "stuck" at low frequencies - and they can happen even if you have set up a reasonable max frequency with the "ondemand" governor.
Not saying that's what is happening here - but it is a huge wildcard when folks start comparing their results.
bftb0
Remove SETCPU widget and turn off homescrren orientation, it stops launcher lag.
Turn up your screen off clock settings, you wont lag when getting a call either.
Sent from my FroyoEris using XDA App
sanpellegrino said:
I get the lag on Tazz Froyo.
Click to expand...
Click to collapse
what is the eris's stock speeds(non-root) sleep speeds
theboo7 said:
what is the eris's stock speeds(non-root) sleep speeds
Click to expand...
Click to collapse
I'm fairly certain it is 245min, 528max. It doesn't actually have profiles set up, just a running min-max.
Sent from my FroyoEris using XDA App
AdhvanIt said:
I'm fairly certain it is 245min, 528max. It doesn't actually have profiles set up, just a running min-max.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Oh okay Thanks. So that means we could set the sleep profile to 528 max, On Demand 40% threshold and 200 powersave bias, would make it do even better than stock eris? Concerning battery life
Try TazzFroyo v6 that was released yesterday.
redhooka said:
Try TazzFroyo v6 that was released yesterday.
Click to expand...
Click to collapse
Slightly lag but nothing unbearable by any means. The Eris hardware isn't cutting edge you know.
I have 160min on tazz for when I'm asleep and 486 or whatever max... 0 lag ever.
I use the SetCPU settings in the following link with my Eris running the Tazz Froyo ROM and have no lockscreen lag.
http://forum.xda-developers.com/showpost.php?p=7528238&postcount=4
I have my screen off settings at 122mhz - 528mhz lol no lag and I save so much battery.
I've had no lag issues with Tazz's Froyo. I'm using LauncherPro with no orientation (I hate landscape anyway) and the following SetCPU profiles:
Temp > 50 C 480 Max/122 Min
Battery < 40 % 480 Max/122 Min
Screen Off 480 Max/122 Min
Charging\Full 768 Max/528 Min
My linpack scores aren't very good, but everything runs quite snappy for me.
rycheme said:
I've had no lag issues with Tazz's Froyo. I'm using LauncherPro with no orientation (I hate landscape anyway) and the following SetCPU profiles:
Temp > 50 C 480 Max/122 Min
Battery < 40 % 480 Max/122 Min
Screen Off 480 Max/122 Min
Charging\Full 768 Max/528 Min
My linpack scores aren't very good, but everything runs quite snappy for me.
Click to expand...
Click to collapse
Not to mention he has fixed the camera and will be releasing v7 soon
When I get a call, my Eris 'lags' or is really slow to pull up the 'caller id/answer' screen...aka-my phone starts ringing and they screen doesn't show anything until it has rung 2-4 times. At that point, I have only one or two rings to answer it until it goes to VM. I can answer with the hard button just fine, but can't see who it is calling when I do that...I am in marketing and it's VERY important for me to see who is calling before I answer.
Eris on Cricket service:
KaosFroyo V30
EPST settings have not changed since I rooted (the day root was discovered)
PRL is known good and has produced no issues until Froyo...
The first place to look is your setCPU profiles and settings. What are they?
710/122 on demand
Charge:
528/122
Failsafe:
480/122
That is it.
Have you tried bumping up your bottom line speed to like 250mhz?
meanm50 said:
710/122 on demand
Charge:
528/122
Failsafe:
480/122
That is it.
Click to expand...
Click to collapse
Priority values would be useful, but then again your low values don't seem that bad.
You are not using the SetCPU widget on one of your homescreens, are you? (A number of people have reported that causing problems, whereas just using setCPU with profiles and no widget use, things were fine).
I'm downclocking to 19 Mhz in KFV31, but I am using some of the setCPU advanced tweaks, and I probably also get fewer calls than you. (So far, no sluggish behavior on inbound calls when the phone is sleeping).
bftb0
I'm having the same problem but I do have the setcpu widget running. I'm going to remove it and see if that helps.
Sent from my Froyo Eris using XDA App
I will disable the widget and see if that helps. Thanks!
My lag got better when I turned launcher rotation off.
Wife has rotation turned off period, and there is no lag to speak of.
KaosFroYo on Eris with Ming font.
ADW rotation was already off...I actually don't like rotation. It always flips when I don't want it to.
I turned up my MIN cpu speed and that made the phone wake from sleep a little quicker, but the call issue is still there. I am thinking it has something to do with the actual dialer .apk used. I think it's Dialer One?
meanm50 said:
ADW rotation was already off...I actually don't like rotation. It always flips when I don't want it to.
I turned up my MIN cpu speed and that made the phone wake from sleep a little quicker, but the call issue is still there. I am thinking it has something to do with the actual dialer .apk used. I think it's Dialer One?
Click to expand...
Click to collapse
I'm not using the same rom, but i've had the same problem before. In setcpu, try these settings:
Max:748, min:604 - userspace
Screen off max: 604, min: 604 - performance
Macrodroid said:
I'm not using the same rom, but i've had the same problem before. In setcpu, try these settings:
Max:748, min:604 - userspace
Screen off max: 604, min: 604 - performance
Click to expand...
Click to collapse
The DEV doesn't even recommend using the "userspace" setting. And 604 as a minimum? Wow.
KaosFroYo on Eris with Ming font.
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
i am using set cpu...and i set cpu frequency to 800, but sometimes i find the cpu frequency 1200...rebooted but still no use...i think task manager is killing set cpu...anyone can help me to stop setcpu from getting killed? or should i use some other app for underclocking?
kryptoner said:
i am using set cpu...and i set cpu frequency to 800, but sometimes i find the cpu frequency 1200...rebooted but still no use...i think task manager is killing set cpu...anyone can help me to stop setcpu from getting killed? or should i use some other app for underclocking?
Click to expand...
Click to collapse
Use tegrak. Set cpu seems to get ignored
thanks a lot...i'll try it now
kryptoner said:
i am using set cpu...and i set cpu frequency to 800, but sometimes i find the cpu frequency 1200...rebooted but still no use...i think task manager is killing set cpu...anyone can help me to stop setcpu from getting killed? or should i use some other app for underclocking?
Click to expand...
Click to collapse
SetCPU isn't even worth of that US2. Seriously I thought it'd help me save my battery life by setting the clock rate at wanted rate, but it's doing nothing but under clocking the CPU whole time and instead of saving battery it's draining it. I have tried every profile, still. I'd NOT recommend SetCPU to anyone.
I have tried Tegrak too, the free version, not for overclocking, but that thing doesn't even show at status bar, it's hard to find if it's running it not, let alone it's performance. After trying both these I found it better to have nothing installed but to Enable the inbuilt Power Saving feature of the phone.
Regards.
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?