Hi, I've got a Xperia Neo V with locked bootloader, I had Gingerbread (compilation 0.42) but yesterday, I decided to install the oficial ICS update. I had installed Setcpu with these values: min245Mhz, max1024Mhz (governor: ondemand) , I updated to ICS and I noticed it was very slow, then I downloaded "Antutu cpu master", and the values were the same I used to use in GB, so I installed Gingerbread again, rooted it, installed setcpu and set these speeds, min1024Mhz, max1024Mhz (governor: performance) and that way I should have those values in ICS, but the problem is when I restart the phone, those values dissapear, and set 245,1024 and governor ondemand. When I select "Set on boot", it still being slow. I updated from GB to ICS (and vice versa) but there is no way to change those values (245,1024) and the governor(ondemand). Is there any way to modify cpu speed? For example modifying a specific configuration file without using setcpu or any other app?
I hope you understand me, and help if you can
Thanks!
Maybe a problem with the stock kernel.
You can try using terminal emulator if you can install the proper scripts.
But acc. to me it needs unlocked bootloader.
Sent from my MT11i
criscracker said:
For example modifying a specific configuration file without using setcpu or any other app?
[/COLOR]
I hope you understand me, and help if you can
Thanks!
Click to expand...
Click to collapse
You could write a script to be run at boot (init.d) that changes CPU speed, however (this might be an obvious question) which kernel are you running??, because AFAIK Sony stock kernel doesn't allow OC/UV, meaning that no matter what you do you won't be able to change CPU speed or governor.
Related
Hello all,
First of all Im not a developer!
After some versions of roms I tried on my phone I had some difficulties with camera, video and contacts and I took the decision to do the following steps after I installed via Sony Ericsson PC Companion the official latest rom of Android 2.1.
1. Root your phone and install also Root Explorer.
2. Delete crap apps and games via Root explorer that SE dont let to uninstall.
3. Install Launcher Pro and 3D Gallery.
The phone after the deletion of some annoying programs of SE was working faster than before. With Launcher Pro and 3D gallery my phone right now is working very fast and faster I can say than Froyo and Gingerbread roms I tested.
The good thing on this is that you have the official rom.. So that means that everything works perfect and at same time with Launcher Pro and 3D gallery you have a different sense from your x10 mini.Until Android 2.2 and 2.3 roms are more stable and everything works great, I think that is a very good solution to give another meaning to your x10 mini and have full functionality.
That's all, I would love to have froyo or gingerbread to my phone too but I also need new roms to be more functional.
The procedure about how to root your phone and follow the next steps are inside the forum.
Final you can overclock your cpu to 710mhz for example (this a good overclocking with the most low risk to brick your phone) with many programs that most of them are in the market too for faster performance.After all you can use many themes and apps that have already posted on x10 mini forum section and use them w/o any problems. xRecovery is a must have to do this right!
Ok as you asked about how to overclock your x10 mini, I will show you the procedure about how to do it:
Intro: (dev post)
Since the X10 kernel is working, we might have a hope that someday we will have our custom kernels. If we can have custom kernels, we can do the overclocking easily.
Until that day, we will still have to overclock with modules. To make overclocking works with our current kernel, as far as I can see, we need to do the following things:
1. Patch cpufreq data to change maximum reported freq (these value will be read by Android for further controls). cpufreq will then call the low-level acpuclock functions to change real cpu freq.
2. Patch acpuclock data + code to change real cpu freq.
Installation:
Manual installation : it will be better if you can do this way.
- Download appropriate x8oc-v004-x10m (for X10 mini)
- Unzip
- Remount /system as rw (Root Explorer app and phone must be Rooted)
- Push x8oc.ko in to /system/lib/modules
- Edit /system/etc/hw_config.sh, add one line at the beginning
# x8 overclock
insmod /system/lib/modules/x8oc.ko
sleep 2
echo xAB > /proc/x8oc
Where AB is your desired code for that frequency. Test the frequency carefully before applying it at boot!
(you can edit hw_config.sh by pulling it to your PC, edit, and push it back)
- Reboot your phone
Frequencies:
20 to change to 614MHz
21 to change to 634MHz
22 to change to 653MHz
23 to change to 672MHz
24 to change to 691MHz
25 to change to 710MHz
26 to change to 730MHz
27 to change to 749MHz
So if you want to overclock your cpu to 710mhz then you have to choose "25" and the following code will be like this:
# x8 overclock
insmod /system/lib/modules/x8oc.ko
sleep 2
echo x25 > /proc/x8oc
After this you can download CPU Master for free from the marketplace and check the speed of your cpu and be able to change also the min frequency for better performance.
Thx to doixanh about this procedure
http://forum.xda-developers.com/showthread.php?t=1020313
You can download the file "x8oc-v004-x10m.zip" from the link above.
more simple... download flastools:http://forum.xda-developers.com/showthread.php?t=920746
This makes root gets you hit and you will also clean the phone from her pc installed xrecovery ... seus or pccompanion or FlashTool
where i can get stable 3D gallery for x10 mini ?
ill try
mariosk1gr said:
Hello all,
First of all Im not a developer!
After some versions of roms I tried on my phone I had some difficulties with camera, video and contacts and I took the decision to do the following steps after I installed via Sony Ericsson PC Companion the official latest rom of Android 2.1.
1. Root your phone and install also Root Explorer.
2. Delete crap apps and games via Root explorer that SE dont let to uninstall.
3. Install Launcher Pro and 3D Gallery.
The phone after the deletion of some annoying programs of SE was working faster than before. With Launcher Pro and 3D gallery my phone right now is working very fast and faster I can say than Froyo and Gingerbread roms I tested.
The good thing on this is that you have the official rom.. So that means that everything works perfect and at same time with Launcher Pro and 3D gallery you have a different sense from your x10 mini.Until Android 2.2 and 2.3 roms are more stable and everything works great, I think that is a very good solution to give another meaning to your x10 mini and have full functionality.
That's all, I would love to have froyo or gingerbread to my phone too but I also need new roms to be more functional.
The procedure about how to root your phone and follow the next steps are inside the forum.
Final you can overclock your cpu to 710mhz for example (this a good overclocking with the most low risk to brick your phone) with many programs that most of them are in the market too for faster performance.After all you can use many themes and apps that have already posted on x10 mini forum section and use them w/o any problems. xRecovery is a must have to do this right!
Click to expand...
Click to collapse
Hi, what did you use to oc it? im using the official 2.1 rooted/xrecovery atm with some stuff removed.
thx
use Set Cpu....for overclocking....gives u a lot of options...nd may improve ur battery life
i agree with you marie but you can try and minicm 6 1.0.1 i use it and i can say that i am content the only thing that i dont like is the camera it's worse than SE
i miss the se stock rom.ill flash back to stcok rom.maybe tomorrow.and put all the features
mariosk1gr said:
Hello all,
First of all Im not a developer!
After some versions of roms I tried on my phone I had some difficulties with camera, video and contacts and I took the decision to do the following steps after I installed via Sony Ericsson PC Companion the official latest rom of Android 2.1.
1. Root your phone and install also Root Explorer.
2. Delete crap apps and games via Root explorer that SE dont let to uninstall.
3. Install Launcher Pro and 3D Gallery.
The phone after the deletion of some annoying programs of SE was working faster than before. With Launcher Pro and 3D gallery my phone right now is working very fast and faster I can say than Froyo and Gingerbread roms I tested.
The good thing on this is that you have the official rom.. So that means that everything works perfect and at same time with Launcher Pro and 3D gallery you have a different sense from your x10 mini.Until Android 2.2 and 2.3 roms are more stable and everything works great, I think that is a very good solution to give another meaning to your x10 mini and have full functionality.
That's all, I would love to have froyo or gingerbread to my phone too but I also need new roms to be more functional.
The procedure about how to root your phone and follow the next steps are inside the forum.
Final you can overclock your cpu to 710mhz for example (this a good overclocking with the most low risk to brick your phone) with many programs that most of them are in the market too for faster performance.After all you can use many themes and apps that have already posted on x10 mini forum section and use them w/o any problems. xRecovery is a must have to do this right!
Ok as you asked about how to overclock your x10 mini, I will show you the procedure about how to do it:
Intro: (dev post)
Since the X10 kernel is working, we might have a hope that someday we will have our custom kernels. If we can have custom kernels, we can do the overclocking easily.
Until that day, we will still have to overclock with modules. To make overclocking works with our current kernel, as far as I can see, we need to do the following things:
1. Patch cpufreq data to change maximum reported freq (these value will be read by Android for further controls). cpufreq will then call the low-level acpuclock functions to change real cpu freq.
2. Patch acpuclock data + code to change real cpu freq.
Installation:
Manual installation : it will be better if you can do this way.
- Download appropriate x8oc-v004-x10m (for X10 mini)
- Unzip
- Remount /system as rw (Root Explorer app and phone must be Rooted)
- Push x8oc.ko in to /system/lib/modules
- Edit /system/etc/hw_config.sh, add one line at the beginning
# x8 overclock
insmod /system/lib/modules/x8oc.ko
sleep 2
echo xAB > /proc/x8oc
Where AB is your desired code for that frequency. Test the frequency carefully before applying it at boot!
(you can edit hw_config.sh by pulling it to your PC, edit, and push it back)
- Reboot your phone
Frequencies:
20 to change to 614MHz
21 to change to 634MHz
22 to change to 653MHz
23 to change to 672MHz
24 to change to 691MHz
25 to change to 710MHz
26 to change to 730MHz
27 to change to 749MHz
So if you want to overclock your cpu to 710mhz then you have to choose "25" and the following code will be like this:
# x8 overclock
insmod /system/lib/modules/x8oc.ko
sleep 2
echo x25 > /proc/x8oc
After this you can download CPU Master for free from the marketplace and check the speed of your cpu and be able to change also the min frequency for better performance.
Thx to doixanh about this procedure
http://forum.xda-developers.com/showthread.php?t=1020313
You can download the file "x8oc-v004-x10m.zip" from the link above.
Click to expand...
Click to collapse
is this the only way to overclock the stock rom? i installed setcpu and others but the max is always 600.
Hello, I have strange x10mp behavior. Tried to OverClock my phone (original 2.1 ROM) with module x8oc.ko. When go to SetCpu I can choose higher frequency than 600mhz, but when try benchmark with quadrant, results are pretty the same as with stock speed. Flashed to MiniCM6_v5.0 and everything is OK I can get ~1000 in quadrant. How OC x10 mini pro with stock ROM?
Overclocking the x10 mini pro proccesor
Move your x8oc.ko at system/lib/modules/
Connect your phone to pc...
Open the command line...
Go to your adb location in command line... (i.e. cd c:/program files/android...etc)
press..
adb shell
su (be sure to accept superuser privillages on your mini pro)
insmod system/lib/modules/x8oc.ko
END
Now you will be able to change frequences in the setCPU....
Good Luck....
diawollo87 said:
Hello, I have strange x10mp behavior. Tried to OverClock my phone (original 2.1 ROM) with module x8oc.ko. When go to SetCpu I can choose higher frequency than 600mhz...
Click to expand...
Click to collapse
Hi diawollo87, can you tell me how you managed to get higher clock setting on SetCPU? Mine is only 600MHz
EDIT: Nvm. Found the answer
u've to change cpu_max frequency like sumthing...
originally by doixanh
Intro: (dev post)
Since the X10 kernel is working, we might have a hope that someday we will have our custom kernels. If we can have custom kernels, we can do the overclocking easily.
Until that day, we will still have to overclock with modules. To make overclocking works with our current kernel, as far as I can see, we need to do the following things:
1. Patch cpufreq data to change maximum reported freq (these value will be read by Android for further controls). cpufreq will then call the low-level acpuclock functions to change real cpu freq.
2. Patch acpuclock data + code to change real cpu freq.
Right now I'm working a proof-of-concept module, with finished 1 and half of 2. I will need to patch acpuclock code in the running kernel to make the frequency applicable.
That means, right now, Android reported that I have a 800MHz MSM7227, although it's running at 600MHz, and cpufreq's governor accepts to change to the maximum 800MHz (it's 600MHz for real). We will need to patch acpuclock code to change PLL and apply the correct divisor.
Click to expand...
Click to collapse
Ok..
I can push the modules into the appropriate folder on the phone and I can run the commands which add it to the cpu governer selection (it took me awhile to realise I had to run 'su' command first ooops!).
However, upon rebooting the smartass governer dissappears from the selection tab and returns to 'ondemand' even if restore upon boot is selected. I assume the module is only temporarily loaded via the 'insmod' and 'echo' commands.
So I pulled the hw_config.sh and added the commands to the end under a new #tag (for ease of keeping things seperate). The same commands listed in the smartass thread. Pushed in back to the phone, But... smartass still wouldn't load and the cpu governer switched permanantly to 'performance' - even when I removed the commands from the config file
Had to restore my cwm backup to fix the issue.
I noticed that the config file makes reference to the ondemand module so wondered if this causes conflict with the smartass one??
I'm fairly new to modding stuff. Anyone got smartass working on gintonic1.3? Can they tell me the proceedure they used?
Sent from my U20i using Tapatalk
sory,i u use minicm7 v7 u can use it w/o problem..just edit hw config.sh
#x8smartass
insmod /system/lib/modules/x8_smartass.ko
azadtaufiq said:
sory,i u use minicm7 v7 u can use it w/o problem..just edit hw config.sh
#x8smartass
insmod /system/lib/modules/x8_smartass.ko
Click to expand...
Click to collapse
I'll give it a go. Thank you very much!
Sent from my U20i using Tapatalk
Hey all - hopefuly this is the correct place for this question. I am developing a custom kernel for the Samsung Replenish baseod off of samsungs open source code. I have thus far gotten the kernel to compile and run just fine on the phone. I have also added the SmartassV2 and Interactive governors. No matter which one i set as default through the phonemodel_defconfig, each time I recompile and load the new kernel, it always default back to OnDemand governor.
I have no problem selecting either of the 2 new governors through SetCPU (and the setting does stick from boot to boot as long as I select "Set at Boot") so I know the governors are properly linked into the kernel. I thought that the kernel would start with the default one I selected, but it does not. Is this how thigs are supposed to operate, or am I missing something. I did update the cpufreq.h file in the include directory.
Any suggestions - is this even the correct place for a post that is this low level.
Thanks!
dmrlook said:
Hey all - hopefuly this is the correct place for this question. I am developing a custom kernel for the Samsung Replenish baseod off of samsungs open source code. I have thus far gotten the kernel to compile and run just fine on the phone. I have also added the SmartassV2 and Interactive governors. No matter which one i set as default through the phonemodel_defconfig, each time I recompile and load the new kernel, it always default back to OnDemand governor.
I have no problem selecting either of the 2 new governors through SetCPU (and the setting does stick from boot to boot as long as I select "Set at Boot") so I know the governors are properly linked into the kernel. I thought that the kernel would start with the default one I selected, but it does not. Is this how thigs are supposed to operate, or am I missing something. I did update the cpufreq.h file in the include directory.
Any suggestions - is this even the correct place for a post that is this low level.
Thanks!
Click to expand...
Click to collapse
As far as i know, cpu scaling governor can also be set by init script in ramdisk and /etc/init.d other than default setting in kernel config. You might need to check if there's any init script that contain a line like :
'write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand '
or
'echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor'
Those lines will set the cpu scaling governor everytime the phone reboots.
In my device (xperia mini pro), that first line is in init.semc.rc in root folder of ramdisk. It should be different in your device
The second line is usually in a script in init.d folder, but stock rom usually doesn't support init.d, so afaik it only exists in custom rom.
greenAlgae said:
As far as i know, cpu scaling governor can also be set by init script in ramdisk and /etc/init.d other than default setting in kernel config. You might need to check if there's any init script that contain a line like :
'write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand '
or
'echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor'
Those lines will set the cpu scaling governor everytime the phone reboots.
In my device (xperia mini pro), that first line is in init.semc.rc in root folder of ramdisk. It should be different in your device
The second line is usually in a script in init.d folder, but stock rom usually doesn't support init.d, so afaik it only exists in custom rom.
Click to expand...
Click to collapse
Thanks for the response. the kernel does support init.d (now, stock did not) but there are not scripts in there as of yet. I also went through all the other startup *.rc scriipts and found one that was echoing ondemand into the scaling_governor file. I tried both comment the line out and reflashing new ramdisk, and chaning it to echo smartassV2 and reflashing new ramdisk. In all cases, Ondemand still comes up.
I've also added a script to init.d that echos governors other than ondemand to scaling_givernors, and still, when the phone is booted, ondemand it is. Note that if I echo some other governor to the file at this point, it does change (I imagine this is what setcpu does in the background anyway).
Could the android system system itself be changing it to ondemand?
Thanks for the help!
dmrlook said:
Thanks for the response. the kernel does support init.d (now, stock did not) but there are not scripts in there as of yet. I also went through all the other startup *.rc scriipts and found one that was echoing ondemand into the scaling_governor file. I tried both comment the line out and reflashing new ramdisk, and chaning it to echo smartassV2 and reflashing new ramdisk. In all cases, Ondemand still comes up.
I've also added a script to init.d that echos governors other than ondemand to scaling_givernors, and still, when the phone is booted, ondemand it is. Note that if I echo some other governor to the file at this point, it does change (I imagine this is what setcpu does in the background anyway).
Could the android system system itself be changing it to ondemand?
Thanks for the help!
Click to expand...
Click to collapse
Well, actually I never try to change the default governor from ondemand before. Partly because I compiled my kernel using official/stock kernel source, so there's only those stock governor options and ondemand seems to be the best option. My phone is SE Xperia Mini Pro / sk17i and currently running Freexperia CM7 rom. The kernel provided has very good performance but seems to cause the battery draining too fast for me, so I compiled a 'stock' kernel to use with it.
After your post above, I tried to add more governor options from freexperia kernel source, recompiled the kernel, edit the init script in ramdisk, and flashed it to my phone.
Here's my result:
- the script in init.d doesn't seems to change the default governor. I don't know exactly why. Other script in init.d seems to run just fine, I can set scaling_min_freq and scaling_max_freq with it. I also check the permission, it's rwxr-x-r-x, but it doesn't seem to be executed at boot.
- in every startup, the rom executes the script in /data/local/userinit.sh too, but setting default governor from that script also doesn't succeed.
- only thing that can change the default governor is adding the line 'write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor smartassV2' in 'on boot' section of the init.semc.rc file.
I'm not a developer and i know every rom might be different. So you might need to ask in your rom specific thread, one of the devs might be able to help you there.
Otherwise, you can always set the default governor at boot using app like 'setcpu' or ' No-frills CPU Control'
dmrlook said:
Hey all - hopefuly this is the correct place for this question. I am developing a custom kernel for the Samsung Replenish baseod off of samsungs open source code. I have thus far gotten the kernel to compile and run just fine on the phone. I have also added the SmartassV2 and Interactive governors. No matter which one i set as default through the phonemodel_defconfig, each time I recompile and load the new kernel, it always default back to OnDemand governor.
I have no problem selecting either of the 2 new governors through SetCPU (and the setting does stick from boot to boot as long as I select "Set at Boot") so I know the governors are properly linked into the kernel. I thought that the kernel would start with the default one I selected, but it does not. Is this how thigs are supposed to operate, or am I missing something. I did update the cpufreq.h file in the include directory.
Any suggestions - is this even the correct place for a post that is this low level.
Thanks!
Click to expand...
Click to collapse
today i was looking for a solution like you and watched this post,finally i could solve the problem.Look at the scripts on /system/etc folder, in my case there was a script located there that changed the governor to ondemand,its name init.qcom.post_boot.sh maybe on your device it has other name.
old thread, i know, but im attempting to root a samsung replenish thats running 2.3.6. can anyone help? nothing is working.
EDIT: LOL. i was thinking "this phone is that old...? this is ridiculous that its running a higher form of gingerbread than my 4 month old phone is......" but i was looking at the join date not the post date, and i thought the thread was 3 years old. LOL
Hello.
I'm having a problem changing CPU scaling governor.
I'm using Jokersax's CM9 build (from 16/2/12) with the 1.3 kernel (stock), had the same problem with CM7 weeklies and any kernel I tried.
SetCPU doesn't allow me to change the governor at all, can't even select it.
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors lists only performance and powersave.
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is an empty file.
Doing "modprobe cpufreq_ondemand" in a terminal as root says that the module can't be found.
Can any one point me in the right direction please?
masmddr said:
Hello.
I'm having a problem changing CPU scaling governor.
I'm using Jokersax's CM9 build (from 16/2/12) with the 1.3 kernel (stock), had the same problem with CM7 weeklies and any kernel I tried.
SetCPU doesn't allow me to change the governor at all, can't even select it.
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors lists only performance and powersave.
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is an empty file.
Doing "modprobe cpufreq_ondemand" in a terminal as root says that the module can't be found.
Can any one point me in the right direction please?
Click to expand...
Click to collapse
I think those are the defaults on most custom Atrix kernels. Clemsyn is the only one who uses interactive instead of performance(that I know of).
If you look in /sys/device/system/cpu/cpu0/cpufreq/scaling_driver you'll notice it says "tegra cpufreq". I think this then uses the Tegra DVFS to scale frequencies using the two governors in scaling_available_governors. Hopefully someone else can jump in and clarify a bit better.
The reason ondemand can't be found is because the kernel probably wasn't compiled with that governor.
Try System Tuner if you want to be able to select between the two available governors (this worked for me when using Clemsyn's kernel on CM7), but I'm not sure what difference it will make. After using System Tuner, it also seemed to "unlock" the governor selection in SetCPU as well.
Thank you.
I didn't realize ondemand wasn't built in because modprobe-ing the other two modules also returned a not found error so I figured something must be wrong.
System tuner did enable me to change the governor in SetCPU, though selecting either of them changes nothing as you said.
Oh well, if there is no ondemand governor then I'll let it do its thing how ever it wants.
Again, thank you for the replay.