Related
Use this tiny tool to overclock your Prophet!
Just copy and run the tool on your device, the maximum allowable (without crashing) clock for Prophet is at 276 MHz.
The device will stayed overclocked if you use it, it will be changed back to its original speed when you idled for a few minutes.
CPU Benchmark scores up to 1012 (compared to 600 in original)
Cheers!
OOpss... i just found out that this has been posted before...sorry, mods you can delete this if you want
Hi, so I tried xcpuscalar at 624 and i get the crash everyone else get, if you try to scroll down using the scroolbar (say, in roxo explorer, windows folder), it freezed and a soft reset is needed.
HOWEVER, some people have suggested that using xcpuscalar at 520 still hold a performance boost, as somehow the xscale processor would throttle back the cpu to lower speed if it wasn't for that tool.
So my question is, is it true?
The HTC Universal uses the PXA 27x series of Xcales for its running. Yes, it auto-underclocks to save power. However, mine stays on 624 MHz for periods of one weeks, each of after which I give it a one day break at underclocking to 416 MHz. Kinda sluggish, but oh well
ok guys first of all ill start by saying that none of this i mine...its all stuff that i understood from different threads.I am a complete noob so there are gonna be many things ill not be able to understand to you!
i am gonna thank these brilliant people first
-gokhanmoral
-pikachu
-droidphile
-andre
and others(who have started undervolt threads) ive missed!
ok now to the main point!
this works only on ics siyah kernels as currently GM is the only one who supports the following commands!
what you need!!
-terminal emulator
-volt tweaking app (set cpu, voltage control),i wont prefer extweak or xxtweak as you cant edit a perticular freq volt with them
-patience
ok now start by selecting the freq on which you wanna work..undervolt it to your desired volt
e.g ive undervolted my 200mhz to 925mv
now open terminal emulator
type:
su
LVL=`cat /proc/kallsyms|grep " level\."|awk '{print $3}'`;kmemhelper -n $LVL -t int 14
and press enter
ok what this command does is that it changes your touch screen freq to the number last in the command line..in this case 14 it is
you can alter these numbers as follow:
0-1600 6-1000 12-400
1-1500 7-900 13-300
2-1400 8-800 14-200
3-1300 9-700 15-100
4-1200 10-600
5-1100 11-500(stock)
so as you can see the above command line sets my touch freq to 200 mhz.
ok so as soon you press enter in the terminal emulator your touch freq is changed to the freq of your liking..(remember use the above states numbers and not the freq itself in the command line) and some how that perticular freq takes load in such a pattern which i could not recreate with any stress stability test or even mxvideo test( you can find about it in various threads) and hence if the undervolt is below the stability threshold your phone will crash,hang,reboot...but you will get to know which volt value on which freq is unstable.
After setting the touch screen freq try(you can use voltage control to confirm if your touch freq has changed or not) use your phone normally...scrolll between pages..browse..play games..and if the perticular freq volt is unstable your phone will indefinitely crash within 5-10 min..!
do this procedure for every freq and ull definitely will get yourself the most stable UV's your device can handle!
you can read much about this and other stuff in droidphiles thread
http://forum.xda-developers.com/showthread.php?t=1572937
thank me if it helped!!
Hmm... do we really need another one of these threads lol
Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
i jus tought of sharing this as it seems to me that this kinda crash which the touchscreen freq produces isnt reproduced by any stability test..hence another way for testing your stability...besides i myself was facing few crashes with my settings lately and this cured it...!
Your CAPS key is broken ...
haha not really...HERE YOU GO...i had words in caps up there aswell...dun knw what went wrong..btw...love your dp!!
Thanks for the info. I've been having a little trouble with some UV values that I believe should be stable. This might be the fix. I'll report back after I've tested it.
I didn't even know you could do that, learn something everyday.
Interesting because in Siyah I've always noticed the max frequency ALWAYS exceeds whats set in SetCPU etc.
If I set it to 500mhz, it will still jump to 800Mhz momentarily when touching the screen, loading apps, scrolling etc. I've noticed on the latest kernel it hits 1200mhz, no matter what my global max frequency is. On Abyss kernel etc, it behaves normally. Is this 'touch frequency' the reason for this?
I watch the CPU frequency using Cool Tools/CPU spy...
Tye:P said:
Thanks for the info. I've been having a little trouble with some UV values that I believe should be stable. This might be the fix. I'll report back after I've tested it.
I didn't even know you could do that, learn something everyday.
Click to expand...
Click to collapse
yeah i myself was having issues with uv's..found this way indirectly with the help of droidphile...would love to see if it helped you!
busky2k said:
Interesting because in Siyah I've always noticed the max frequency ALWAYS exceeds whats set in SetCPU etc.
If I set it to 500mhz, it will still jump to 800Mhz momentarily when touching the screen, loading apps, scrolling etc. I've noticed on the latest kernel it hits 1200mhz, no matter what my global max frequency is. On Abyss kernel etc, it behaves normally. Is this 'touch frequency' the reason for this?
I watch the CPU frequency using Cool Tools/CPU spy...
Click to expand...
Click to collapse
mate your issue can be solved simply by installing extweak and setting the smooth scaling level to your max freq..on default the level is 1200..but this issue was solved in the 3.2.7.X versions of siyah..which version are you using?
i'll try to UV with xxtweak
doesnt matter what uv tool you use...but i should be an app which uv's indivisual freq's and not all at once as then you wont be able to figure out which volt is giving error on which freq!
I found it!
Recently I was using smartassV2 at 1 Ghz then overclocked to 1.8 without changing the governor and suddenly the screen turned off, rebooted the phone, boot animation appeared then black screen and the phone turned off so I knew that the rom had been corrupted therefore I installed it again. Everything was normal I went again and overcolcked to 1.8 Ghz with smartassV2 governor and the same; the rom had been corrupted so I installed it again. This time I overcolcked to 1.8 Ghz but with ondemand governor and there was no problem.
Now I knew why overclocking to 1.8 is good sometimes and bad another; it has a relation with the governor and I found that ondeman governor is working fine at 1.8 Ghz for .32 kernel.
So try to overclock your phone to 1.8 with ondemand governor or other governors and tell us your experience but be sure to backup your rom, app, data...
I don't know if there is any further problems of overclocking to 1.8 Ghz so do it at your own responsibility.
A couple of notes:
1) Not all chips are created equal; there is slight variance, which means that not all processors found inside U8800 phones can be overclocked to 1,8 GHz.
2) When changing your clock frequency, do not, at first, check the "Set at boot" box. This could send your device into a bootloop, if the setting is not functional.
3) Overclocking and governor functionality may be kernel-specific.
4) I, personally, will not overclock my device to 1,8 GHz, as 1,2 GHz is good enough, in my opinion, but knock yourselves out.
Question: I don't quite understand how overclocking can corrupt a ROM by itself. Could it be that you allowed the non-functional frequency to be set at boot time? (See note #2)
I am using the original U8800 and running dzo's Aurora ICS version 4,1 update 1.
Tonttunator said:
A couple of notes:
1) Not all chips are created equal; there is slight variance, which means that not all processors found inside U8800 phones can be overclocked to 1,8 GHz.
2) When changing your clock frequency, do not, at first, check the "Set at boot" box. This could send your device into a bootloop, if the setting is not functional.
3) Overclocking and governor functionality may be kernel-specific.
4) I, personally, will not overclock my device to 1,8 GHz, as 1,2 GHz is good enough, in my opinion, but knock yourselves out.
Question: I don't quite understand how overclocking can corrupt a ROM by itself. Could it be that you allowed the non-functional frequency to be set at boot time? (See note #2)
I am using the original U8800 and running dzo's Aurora ICS version 4,1 update 1.
Click to expand...
Click to collapse
Thanks for your notes.
No I didn't check the "Set at boot" box and there was no bootloop, the boot animation appeared but in the end the phone turned off.
★HUAWEI IDEOS X5 U8800H★
Hello, I bought a Moto G 2nd generation XT1069 DSTV, and the CPU frequency not lower more than 787 MHz. I used CPU-z to verify. The first boot after removing it from the box, the frequency in idle was 300 MHz, but now is 787 MHz. It's a serious bug. I've done 5 wipe data/factory reset, but this did not solved the problem. Any solution? Someone with this problem too? Thanks. (Sorry for my bad english).
To be honest, I've never seen this before, have you tried flashing the stock firmware to see if it helps?
Y2000 said:
Hello, I bought a Moto G 2nd generation XT1069 DSTV, and the CPU frequency not lower more than 787 MHz. I used CPU-z to verify. The first boot after removing it from the box, the frequency in idle was 300 MHz, but now is 787 MHz. It's a serious bug. I've done 5 wipe data/factory reset, but this did not solved the problem. Any solution? Someone with this problem too? Thanks. (Sorry for my bad english).
Click to expand...
Click to collapse
Check the problem from a command shell over adb. Try this with the screen off and no apps running in the foreground.
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq
Repeat a few times to verify the cpu isn't scaling down. If you have superuser access and busybox installed, you can prefix the command with 'busybox watch -n 1' and it'll print every second until cancelled (CTRL+C). If the frequency never drops below 787200 kHz, use the 'top' command to work out which process is using most cpu time.
Y2000 said:
Hello, I bought a Moto G 2nd generation XT1069 DSTV, and the CPU frequency not lower more than 787 MHz. I used CPU-z to verify. The first boot after removing it from the box, the frequency in idle was 300 MHz, but now is 787 MHz. It's a serious bug. I've done 5 wipe data/factory reset, but this did not solved the problem. Any solution? Someone with this problem too? Thanks. (Sorry for my bad english).
Click to expand...
Click to collapse
on /etc/init.qcom.post_boot.sh scaling_min_freq is set to 787200 :
Code:
echo 1 > /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu2/online
echo 1 > /sys/devices/system/cpu/cpu3/online
echo 787200 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
chown -h system /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# add read permission to max cpu frequency interface
try to set it yourself to 300000 after booting and see afterwards if it sticks, if it does you could just modify the script ...
Solved (or not)
After opening and close the camera app, the CPU goes down to 300 MHz. I need repeat this after each reboot. Is a kernel bug, I hope Motorola fix this. I don't have unlocked bootloader or root on my device for warranty reasons. Thank so much for the support! (again, sorry for my bad english )
Y2000 said:
After opening and close the camera app, the CPU goes down to 300 MHz. I need repeat this after each reboot. Is a kernel bug, I hope Motorola fix this. I don't have unlocked bootloader or root on my device for warranty reasons. Thank so much for the support! (again, sorry for my bad english )
Click to expand...
Click to collapse
Do you have an SD card in? I'm wondering if you still see this symptom with the card removed. I say symptom because I seriously doubt the governor has a scaling bug.
Y2000 said:
After opening and close the camera app, the CPU goes down to 300 MHz. I need repeat this after each reboot. Is a kernel bug, I hope Motorola fix this. I don't have unlocked bootloader or root on my device for warranty reasons. Thank so much for the support! (again, sorry for my bad english )
Click to expand...
Click to collapse
i just noticed i have exactly the same behaviour, thanks for pointing it out. waiting for lollipop and hope it wil fix this problem
same 787 min value
I have the same problem now cpu not going below 787 and tried your trick open camera and closing ,yes it works bt what will be cause how to solve
vaisakmct said:
I have the same problem now cpu not going below 787 and tried your trick open camera and closing ,yes it works bt what will be cause how to solve
Click to expand...
Click to collapse
In kernel ramdisk the cpu is setted to be between 787Mhz and 1.2 GHz, I don't know why opening the camera change this. BTW if you are rooted you can change it using apps like trickster mod and similar
It seems the mpdecision daemon prevents the CPU from scaling right down. Whilst playing around with the Furnace kernel, I discovered that disabling mpdecision allowed me to successfully set the minimum scaling frequency to 300MHz. The easiet way to achieve this is to use the excellent Kernel Adiutor; disable mpdecision,set the min frequency to 300MHz, but don't enable multicore power saving. Leave the governor set to interactive -- the Moto G's kernel doesn't support boostpulse for ondemand.
When set up this way, the benefits to battery life are quite dramatic.
I have unrooted new moto g .how can i underclock the cpu of this phone?
Sent from my XT1068 using XDA Free mobile app
You can't without root
Sent from my XT1028 using XDA Free mobile app
lollipop 5.02 have not solved this problem
Y2000 said:
Hello, I bought a Moto G 2nd generation XT1069 DSTV, and the CPU frequency not lower more than 787 MHz. I used CPU-z to verify. The first boot after removing it from the box, the frequency in idle was 300 MHz, but now is 787 MHz. It's a serious bug. I've done 5 wipe data/factory reset, but this did not solved the problem. Any solution? Someone with this problem too? Thanks. (Sorry for my bad english).
Click to expand...
Click to collapse
i am from india and MOTO g2 updated to lollipop 5.02 in XT1068 and this issue is not yet solved.
I also have this issue on 4.4. Good that there is a work-around. I raised a problem with Moto Support and I suggest more people go this route, so they are aware that this is something they really should fix
I get the impression that is actually by design, rather than oversight. Given the ridiculously aggressive LMK settings, the reduced number of hidden apps (12? On a phone with 1GB of RAM? Really?!) and this scaling issue, it rather looks like Motorola tuned the software for the phone to appear snappy on first use. It looks good in reviews but sucks balls during intensive/extended use.
rufflove said:
It seems the mpdecision daemon prevents the CPU from scaling right down. Whilst playing around with the Furnace kernel, I discovered that disabling mpdecision allowed me to successfully set the minimum scaling frequency to 300MHz. The easiet way to achieve this is to use the excellent Kernel Adiutor; disable mpdecision,set the min frequency to 300MHz, but don't enable multicore power saving. Leave the governor set to interactive -- the Moto G's kernel doesn't support boostpulse for ondemand.
When set up this way, the benefits to battery life are quite dramatic.
Click to expand...
Click to collapse
thanks for this tip, works well! in kernel adiutor there are other settings to change for better performance?