Hey guys, I'm currently running CM6, and when I tried to upgrade to CM7, from the version with overclocking and undervolting added, my fone always reboot and lag continously, unusable until i restore using factory reset.It never happened with any previous version of CM7. A couple day back, I tried the overclocking tweak for CM6, and the same thing happens. I have to restore using Xrecovery. Does anyone knows what the problem is ? I really want overclocking function
stable overclocking is 768 or less.... this much i knw some dev will help you
You did say that you used the overclocking patch , but did not tell did you use SetCPU with set on boot option ? Also what is ur max and min settings in setcpu ?
Anyways , not sure if you will now be able to go inside setcpu , since ur phone is restarting.
On mini pro , for me 780+ Mhz caused reboot. And if you have setcpu set to set it on each boot , then u will end up in infinite loop. For me it happened , but luckily if you do not touch ur phone (touch screen touch ;-) ) after a reboot , it wont reboot (atleast for me).;
So after a reboot :
1. connect phone to PC
2. use adb to uninstall the setcpu
3. reboot again.
This time you should not be having trouble as your phone should behave normally.
Again install setCPU (if you are interested still !!) and set the max to anything below 760Mhz.
What should we do if there is the reboot loop but setcpu is already uninstalled? Or if its installed but overclock is not set on boot?
Hey thanks for the help, but I can't do anything at all with the phone after the patch, with or without setcpu. It booted up, on lockscreen, lag for 30sec and continous reboot then -.-''
Sent from my U20i using XDA Premium App
will make much more sense letting people know what you have done. Just the normal OC module should not have ur phone rebooting.
Does the phone reboot if you do not touch it but just keep it connected to PC ? please answer or else its very hard to try and figure out an answer.
if you feel its causing an issue , then u got to figure out a way to disable that module.
The module gets loaded as x8oc.ko.
In CM6 - v4 , this is not there by default but will appear in hw_config.sh if you have patched it.
So u got to get /system/etc/hw_config.sh and comment out the line insmod for x8oc.ko and anything associate with it .
Did fresh install of v4 after factory reset, resulted in no overclock options and completely stable. Installed oc zip from cm6 oc thread which resulted in infinite reboots even when attached to pc, was not able to touch any settings. Reflashed v4 without factory reset and am back to no overclock and completely stable. Setcpu was not installed, recently installed on fresh v4, no options beyond 600mhz.
yep ..if u did a fresh install of v4 , it means the overclock is not functional as the module is not loaded in it.
Changelog for v4 says overclocked and undervolted, but never mind that. Installing oclock.zip as per instructions in that thread results in infinite reboot, does not stay up long enough to use adb shell or access setcpu. The fresh install of v4 does have overclock options in cyanogenmod settings, but values cannot be edited.
Are you implying that v4 will not support the oclock.zip or simply replying only to first sentence of explanation?
Any help is appreciated.
ok . so let me explain ( i know its quite hard on both ways ) . The overclock module (x80c.ko) is NOT loaded by the default V4 version. So if the module is not loaded Cyanogen setting will only show you the max (600 Mhz i thnk) and min (122 Mhz - I think). I did not find that module to be loaded in any of the init* scripts or in hw_config.sh. But the module is present with the build in the modules folder (but not active as its not loaded with insmod).
So if you just coming just after applying V4 - with no other patch. Then you do not have active overlocking module - hence overclocking wont work with SetCPU. Cyanogen does NOT provide you a scope to change the frequencies - you need setCPU - (you can change the max thru command line after enabling the module).
Now if you have patched the same with the oc patch , you have the module active (insmod works) , but another line of it in the hw_config.sh (patched one) does not become effective for me (some people reported it worked for them though).
The constant reboot which i faced was because i (with the help of SetCPU) had set very high frequency (causing the system to become unstable).
So inorder to fix it , you can do the following:
1. Full wipe through xrecovery
2. Apply V4 again.
3. Change hw_config.sh to add the insmod command to load x8oc.ko module.
4. Reinstall setcpu and see if you can set the max/min to safe values (say around 719 Mhz max and min as 300 or 400 Mhz).
5. If you see the system to be stable , well and good.
If by above , setCPU does not detect max/min (max should be 825 Mhz) , then you need to add the echo x27 > /proc/x8oc to hw_config just after the insmod line of x8oc.ko. (you will see some threads where sleep 2 or sleep 4 is also asked to be put in , but for unknown reason it did not work for me).
Whew!! that was long . But thats the way it worked for me.
For me when the reboots were happening , i had my phone connected to PC , but i was not touching the phone at all (if i touch , it used to reboot - but adb shell was working if i do not touch it).
If any further clarificaiton required , i would be glad to assist.
But before puting in a query , please try and give as much information was to what you did after which the reboots started (not just saying that i did the OC patch - cos for me just the OC patch never resulted into the reboots).
Thank you for that awesome explanation and sorry for the lack of relevant information earlier in the thread.
Should be able to do as you have suggested when I get home and will report back, either way your explanation has made it all clear and I can see where I have missed important steps. Many thanks.
Edit: edited hw config.sh, inserted insmod, sleep and echo lines. Stable ay 729, reboots at 748. Thanks again
good to know it worked !
same problem with my minni.... reboot again and again
Check your baseband, it must be xxx15 or it won't work because of different kernel
Nah got everything rite, basband and kernel, just when I apply the OC tweak, the fone would boot up, but freeze at lockscreen. IT DOES BOOT UP, BUT STUCK AT LOCKSCREEN !!! So bloody annoying, then stuck on bootloop until restore /system using xrecovery
Sent from my U20i using XDA Premium App
Don't apply the oversclock tweak from xrecovery, instead try editing hw_config.sh to have:
# x8 overclock
insmod /system/lib/modules/x8oc.ko
sleep 2
echo x27 > /proc/x8oc
I believe i had the same issue until i did this, then it was stable.
my mini max cpu is only 691 mhz or else the reboots and its laggy as hell. LIKE all your work every wear
have your lovely MDDI on to it help alot but still scrolling lag. maybe fresh install via seus?
wrong thread
Hi all,
My phone has been performing very slow since the past 2-3 months,it behaves like ancient symbian phone from 2003.Phone is rooted and boot loader is unlocked.I have tried installing custom rom but the problem still persists.I have only 400 mb space in card and about 100mb in phone memory.Applications installed are 60-70.
Install CPUspy and look haw is processor in a pressure first. And try of course some task killer.
isthisreallife said:
Hi all,
My phone has been performing very slow since the past 2-3 months,it behaves like ancient symbian phone from 2003.Phone is rooted and boot loader is unlocked.I have tried installing custom rom but the problem still persists.I have only 400 mb space in card and about 100mb in phone memory.Applications installed are 60-70.
Click to expand...
Click to collapse
how much RAM free do you have. Also as heliumX10 sais some task killer should be used. Try to move most of the apps to sdcard
Sent from X10
Use this tool forum.xda-developers.com/showthread.php?t=1415600
Try some of these things
1. charge phone to 100%, wipe/format everything, & make a clean installation of FeraLab v18
2. Use a task killer
3. Flash another kernel.
get no frills cpu app from market and check your min/max frequency and governor which is maybe set to conservative and that could be the reason of the slowlines, if it is, change it to smartass v2 and rise the min/max frequencis a bit, and you will feel the difference
Sent from my X10i using XDA
Hi all
I learned a lot about android when I unlocked the bootloader of my xperia sola, flashed TWRP and various ROMs, installing GAPPS etc. BUT! I still dont have a clue of how to work with ROM Toolbox Pro for setting Minfree Values or Freezing System Apps I do not need (like Bloatware or NFC etc). Setting Minfree Parameters wont change a thing experience wise or looking at the memory (RAM) gauge. Freezing System App marks it as "freezed" but is still shown in running tasks. This said the RAM gauge of ROM Toolbox shows different values than android´s own (settings/apps).
So what am I missing here? Maybe someone can tell me (hopefully in simple words).
Cheers,
Rogurt
(xperia Sola, TWRP, CarbonROM-KK-unofficial-20141017-0647)
Hello
I installed the latest version on my Surface Pro 3 in hard drive mode (it works flawlessly btw)
Only problem : battery is draining very very fast.
The cause is propably that the CPU run @2,6Ghz (=turbo mode on the i5) no matter what I do with it (the loading is @50% in idle....)
Is there a way to fix it ?
Thank
Download this and then change the governors that worked for me.
well, i need Root access, any way to tweak that without root?
Raon said:
well, i need Root access, any way to tweak that without root?
Click to expand...
Click to collapse
Nope. Android doesn't allow you to change governors without root.
Ok i'll do it so
Did you manage to use Android app like Greenify or Amplify ? How Remix OS react to this ?
There is a built in one. Once your rooted. Edit build.prop.
It looks like there are only two governors in the kernel. powersave and performance. The default is powersave so right now you won't get any better power consumption than the default.
change screen brightness setting
if you installed playstore and auto sync is enabled
Hey everyone, I just wanted to make a guide on how to improve your battery life on a custom nougat rom with solid performance and little to no heating issues. I use this method after many trials and errors after I only got 2.5-3hrs of SOT after leaving stock and flashing custom roms. However, after Magisk 14.3 I no longer got the frequent safety issue that plague me for months and I also notice my battery life starting to improve.
Please Note: I have not tested this on marshmallow custom roms or any stock Moto G4/G4 Plus rom (6.0 and above) but feel free to try and let me know if it works. Also this method could be duplicated on other devices.
Disclaimer: I'm not responsible for any bricked or damage device you used my method. I give all credit to the developers who does a fantastic job creating all the things they do for the root community. Thank you!
Follow the following tips if your on a custom nougat rom (Ex: LineageOS, Resurrection Remix, InvictaOS, etc.).
1. Download a custom Nougat (7.0+) rom for your device and go through the initial set up as normal. (I personally use InvictaOS for my device which is very stable). Note: Do not install any root app that modifies system files!
2. Download the following files: Ex kernel , Addon-su- remove-14.1.zip , Magisk 14.3 (1437).zip.
2. Reboot into recovery and install the latest Ex kernel for nougat. This kernel is quite stable and works universally with most custom roms. (It also keeps the phone sightly cooler during heavy usage).
3. Next, flash the addonsu-remove.zip file to remove any traces of root from your room as it will interfere with Magisk which could result in your device randomly rebooting. Afterwards, flash magisk 14.3.zip (This version of magisk pass safetynet on a consistent basis in my experience). You can now reboot your device.
4. Once your back into your phone, launch magisk manager and check if your pass safetynet (which means you did it right) now head to the download section of the app and install the module for "Sysconfig Patcher". A solid tweak improves screen off time by putting the battery hog known as Google Play Service into doze.
This is a bonus step but it's well worth it if you want to maximize battery life:
5A. Buy the official Ex kernel app from the play store. This allows you more power over your kernel settings than the alternatives. Next download the kernel turnables "lightning blade" in addition to our device, this works on allow phones using a snapdragon 617 processor like the G4/G4 Plus. Download the zip file and follow the instructions in the thread very carefully. This will give you much improved screen on time by using less cores unless necessary to maintain a smooth experience. Additionally, It keeps the phone cooler during heavy usage coupled with ex kernel.
5B. Now you can play around with the kernel settings if you like. My personal settings is more gear to my average daily use. Under CPU tab I change my governor turnable to lightning blade from the previous step, under GPU tab I use Simple_ondemand as the gpu governor. Under memory tab, I disable both KSM and KSM Deferred Timer and enable Low Memory Killer. Then under miscellaneous I change TCP to Westwood, increase the i/o schedule read ahead time to 512, and press wake blocks to toggle all three wake blocks. If you want to keep these changes make sure to hit apply on boot for every changes made within the app. You can undo all this to return to ex kernel's stock settings by clearing ex kernel manager's app data and rebooting.
Important: If you follow my steps above you should have better battery life. Try not to install Magisk modules what is not compatible with Magisk 14.0 and above as it may cause your device to randomly reboot and bootloop when powering on.
Please share your battery stats!