hi, im an overclocking/underclocking maniac I go with root explorer and change my cpu profile ( interactive ) settings, to respond faster but to stay less time to max value. also i change the settings for the cpu to sleep sooner when the usage is low to conserve battery this way.
But after reboot , my settings are rolled back at their "original" values. I tried to set the permissions only user can write , but it happened again. Does someone know why and how can i make my changes permanent ? thank you in advanced.
forgot to mention. im not using setcpu or anything. i change the system values in the vanir rom i use.
kessaras said:
forgot to mention. im not using setcpu or anything. i change the system values in the vanir rom i use.
Click to expand...
Click to collapse
try using one of the many apps, vanir might not be saving the settings and applying at boot. Or you could write a simple init.d script to echo your frequencies much earlier in the boot process.
JoinTheRealms said:
try using one of the many apps, vanir might not be saving the settings and applying at boot. Or you could write a simple init.d script to echo your frequencies much earlier in the boot process.
Click to expand...
Click to collapse
i cant. using other apps its even harder for me to find the file to edit the profile i want to make it the way i want. i just tried
found it. only using setcpu i can edit governors the way i want them. but still im curious about finding where is the script in rom and reverts back my changes.
Related
HI guys,
i am on twooey 2 with glitch kernel and i am trying to change the governor to conservative.... but it change back to ondemand after few mins... after the screen locks and unlocks, its back to ondemand..
i tried to set it as boot but no luck.. i tried both pimpmy cpu and voltagecontrol.. but no luck
pls help..
thanks
You have to delete a script in /etc/init.d
I dont remember the exact name but its something like "screenstate".
I would advise you to use lippol94's cleaning script, which will reset any kernel settings. Find it here: http://forum.xda-developers.com/showthread.php?p=15609632
Choose the CM7/MIUI one, apply the zip thru CWM, and try to change the governor again and go from there.
Cheers.
go to glitch thread and read, all you need to know should be there
hi..i want to format my phone coz im suspecting a virus. im using floyo 1.0 and tried some other roms,but i usually get random reboot.tried scanning for virus but not working. so i really need any step by step guide or tips on how i can format my phone safely or any of u have tips on how to help me.sorry if im reposting but i cant find any post about this.
any help will be mostly appreciated...
maliceomalice said:
hi..i want to format my phone coz im suspecting a virus. im using floyo 1.0 and tried some other roms,but i usually get random reboot.tried scanning for virus but not working. so i really need any step by step guide or tips on how i can format my phone safely or any of u have tips on how to help me.sorry if im reposting but i cant find any post about this.
any help will be mostly appreciated...
Click to expand...
Click to collapse
Those random reboots can be caused by a number of things, but, in this instance you should put "virus" at the bottom of the list. Since your using customs ROMS, first to check is overclock, you might be pushing your Phone's CPU/GPU too hard.
I would assume you have a rooted phone and using a custom ROM. Reboot to Xrecovery and wipe user data. Next reformat your SDcard. reboot and you'll have a "clean" phone.
ok..i'll try.thanks
viper001 said:
Since your using customs ROMS, first to check is overclock, you might be pushing your Phone's CPU/GPU too hard.
Im using floyo 1.0 so how should i manage to avoid pushing CPU/GPU too hard?
xperia x8 proud owner
Click to expand...
Click to collapse
If you have root explorer. go to system\lib\modules. check and see if you do have the overclock module. also check if you have the undervolt module. Make sure R/W is enable and Move the OC and UV Module to the SDCARD as backup. Reboot and test you phone if its still randomly rebooting.
alternatively, you can check setting >> cyanogenmod settings >>performance >> cpu settings. if there is and you find CPU can be adjusted then reduce the clock to around 691Mhz.
Another option is to install CPUMaster or SETCPU to adjust clock speed.
viper001 said:
If you have root explorer. go to system\lib\modules. check and see if you do have the overclock module. also check if you have the undervolt module. Make sure R/W is enable and Move the OC and UV Module to the SDCARD as backup. Reboot and test you phone if its still randomly rebooting.
i surely have OC no UV module.so must i install UV and then move them to SD..? or i just install UV module and see what happen..?
Click to expand...
Click to collapse
maliceomalice said:
viper001 said:
If you have root explorer. go to system\lib\modules. check and see if you do have the overclock module. also check if you have the undervolt module. Make sure R/W is enable and Move the OC and UV Module to the SDCARD as backup. Reboot and test you phone if its still randomly rebooting.
i surely have OC no UV module.so must i install UV and then move them to SD..? or i just install UV module and see what happen..?
Click to expand...
Click to collapse
try to remove the oc module first. see if that make it stable.
Click to expand...
Click to collapse
i tried benchmark and i get 400+ only. Is that normal?
xperia x8 proud owner
is it an app or a zip to flash it in recovery?
Where can i download it? I cannot find any resources about this
I really want my phone underclock automatically when in low usage
thanks
sonicpeter said:
is it an app or a zip to flash it in recovery?
Where can i download it? I cannot find any resources about this
I really want my phone underclock automatically when in low usage
Click to expand...
Click to collapse
InteractiveX is one of CPU governor, applied inside kernel... it's not an application, it's kernel features...
CMIIW.
redy2006 said:
InteractiveX is one of CPU governor, applied inside kernel... it's not an application, it's kernel features...
CMIIW.
Click to expand...
Click to collapse
Sorry, if I have flashed the NOVA v8 and all the Huexxx stuffs(total number in 5).
would it use the InteractiveX governor automatically? If not, how can it change it?
thanks
You can change via Nova script, access it via terminal.
type su, then nova.
Or you can use setCPU, CPU Master, No-frills CPU Control, or anything related with setting CPU.
CMIIW.
redy2006 said:
You can change via Nova script, access it via terminal.
type su, then nova.
Or you can use setCPU, CPU Master, No-frills CPU Control, or anything related with setting CPU.
CMIIW.
Click to expand...
Click to collapse
thanks.
I found that one of the 5 stuff cannot be flashed and told me "installation abort". the stuff is called "quasar-v8-source.zip". i tried so many time and i nearly give up
I am just wondering the recovery have no enough ROOT permission...any idea?
quasar-v8-source.zip is not compiled kernel for android, that's the source. You can't install it. If you got files like that, perhaps named "source", don't ever trying to flash it to your phone... And that's not the main problem of CWM, it's because you had a mistake by flashing source file..
CMIIW.
Is it just me or minfree values are not sticking on KuyaDROID?
If anyone is running this ROM, I would appreciate if you could do the next:
· Configure the minfree values to anything. To make things easier you could run the V8 SuperCharger Alpha by zeppelinrox found here: http://forum.xda-developers.com/showthread.php?t=1250276. Don't try to update the busybox version or you'll get a soft-brick.
· Restart the system and check the values in terminal with:
Code:
cat /sys/module/lowmemorykiller/parameters/minfree
· Use your phone for a while. Let it go into the lockscreen and come back into the terminal and run the code again.
· Is there a difference for you?
Here's the scenario: the values are loaded at boot, however after some use, the values are changed to something else entirely, specially after exiting the lockscreen.
I want to see if it really is just me or indeed there's a bug that can be hunted down. The strangest part of it all is that the values are not even the ones defined in init.rc.
Now I can set them again and they will stick no matter what, but it's somewhat anoying.
Fortun said:
Is it just me or minfree values are not sticking on KuyaDROID?
If anyone is running this ROM, I would appreciate if you could do the next:
· Configure the minfree values to anything. To make things easier you could run the V8 SuperCharger Alpha by zeppelinrox found here: http://forum.xda-developers.com/showthread.php?t=1250276. Don't try to update the busybox version or you'll get a soft-brick.
· Restart the system and check the values in terminal with:
Code:
cat /sys/module/lowmemorykiller/parameters/minfree
· Use your phone for a while. Let it go into the lockscreen and come back into the terminal and run the code again.
· Is there a difference for you?
Here's the scenario: the values are loaded at boot, however after some use, the values are changed to something else entirely, specially after exiting the lockscreen.
I want to see if it really is just me or indeed there's a bug that can be hunted down. The strangest part of it all is that the values are not even the ones defined in init.rc.
Now I can set them again and they will stick no matter what, but it's somewhat anoying.
Click to expand...
Click to collapse
Did you use build.prop or local.prop??
har****group said:
Did you use build.prop or local.prop??
Click to expand...
Click to collapse
If you're talking about the app_adj and app_mem values; well, the V8 SuperCharger script uses local.prop to set them up, so there. I've also tried to set them up manually using build.prop.
So I've tried flashing a couple of the kernels around that everyone else seems to have no problem with. I just flash the regular way using TWRP bu then after it boots, about 15 seconds after sense loads, it reboots. And it'll just loop like this. Any ideas how I could fix this?
Wipe cache/dalvik
Sent from my HTCONE using xda app-developers app
Thanks for the response. I've tried that a few times to no avail unfortunately.
How about a full wipe>flash rom>wipe dalvik/cache>flash kernel
Sent from my HTCONE using xda app-developers app
TheLeapist said:
Thanks for the response. I've tried that a few times to no avail unfortunately.
Click to expand...
Click to collapse
Most kernels nowadays have mpdecision/thermal support in them. If the kernel that you're flashing has this support, you need to delete/rename these files from your system/bin directory BEFORE flashing. I use ES File Explorer, but any root file manager should do the trick. Leaving these files in the system AND flashing a kernel that has them can cause unusual behavior/reboots. You can also check if your rom has init.d support.......this is a folder in your system/etc directory. It contains scripts that run after boot and sets various parameters for controlling different aspects of your phone. The cpu min/max clock speed and sd card read ahead are two of the most common ones. If that folder is there, check for any scripts that set values for your cpu and rename them with a .bak extension. Also, make sure you don't have any cpu tweaking apps installed that could conflict with each other........such as Kernel Tuner and SetCpu. Make sure you check for ALL of these possible issues prior to flashing. Of course there could be other things causing reboots, but the above mentioned steps will most likely solve them for you. (especially if other user's are not reporting any reboots) Hope you get to the bottom of this and can start enjoying your new toy.
>>If you're unsure about any scripts in the init.d folder, just make a copy of it and upload here. I would be happy to help you out.