Rooted, unlocked and I can't get CPU settings to stick. They keep reverting back to stock 1300. Tried Aokp, cm10, eclipse and multiple kernels, motley, clemsyn, etc. Used system tuner, setcpu, romtoolbox, etc. You can be in the program and set the frequency and it will work, then push screen off button, and back on and its back to 1300 instantly. Never had this problem before.
Any thoughts on how to proceed here.
Thanks
Sent from my Nexus 7 using Xparent Blue Tapatalk 2
I have the exact same problem. Does anyone have a fix for this? I j am using latest busy box and superuser
bill3508 said:
Rooted, unlocked and I can't get CPU settings to stick. They keep reverting back to stock 1300. Tried Aokp, cm10, eclipse and multiple kernels, motley, clemsyn, etc. Used system tuner, setcpu, romtoolbox, etc. You can be in the program and set the frequency and it will work, then push screen off button, and back on and its back to 1300 instantly. Never had this problem before.
Any thoughts on how to proceed here.
Thanks
Sent from my Nexus 7 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
CPU settings won't stick, revert to stock at screen off
Hi, I'm having the same issue here, running Trinity kernel and CM10, as well as the latest busybox on my Nexus 7. However, I can't seem to get the maximum CPU frequency to stick, it reverts back to 1300MHz when I lock the screen. If anybody has a fix for this it would be really good to have it.
Thanks.
Check out the lean kernel thread. In the downloads there is a powerhal42-lk-nofreq.zip. just flash and you're good to go.
http://imoseyon.host4droid.com/grouper/beta/#!/view=details/lang=en/sort=na
Related
I posted this before but I think it was the wrong forum....so I figured I would try it here.
I have a D2 which I used the Z4root app to root. Everything is working great and I am very thankful. However I am curious what all happens should I hit the unroot button.
Does it wipe the phone?
Does it put it to a state where I could send it to VZW for warranty replacement?
I downloaded that Titanium Back up Pro....so if I run a backup does it get all my apps and settings? Then what when I recieved new phone....root, DL titanium and restore?
I also DL'd SetCPU but am curious if that overclock Dx/D2 app is better as SetCPU doesn't allow me to actually overclock my D2.
Thanks in advance for your assistance. Sorry for all the Newb questions.
I have not tried the Z4 root app but I would assume that when you hit the unroot button that it only unroots and dosn't wipe the phone. You could just flash the stock rom with rsd lite to restore to out of box condition. As far as back up apps are concerned I prefer My Backup Pro, you can back up all app and phone data to an online server and restore on any phone. And the Dx/D2 overclock app is better because it actually let's you overclock, set cpu will only let you under clock.
Sent from my DROID2 using Tapatalk
I had it installed but could not overclock with it. I am thinking it is because I did not do a different kernal or ROM yet.
Just flashed Myn's on my girlfriends phone with the stock kernel and now her CPU will stay anywhere from 600 - 998 but never lower than that. Needless to say it is killing the battery pretty bad. Why is it doing this? Should I flash another kernel?
Is setcpu installed on the device? Is so then what are the settings? Is the set on boot option checked?
Sent from my PC36100 using XDA App
caguirr4 said:
Is setcpu installed on the device? Is so then what are the settings? Is the set on boot option checked?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
No SetCPU. Tried installing it to set a profile but that didn't do anything so I just un-installed it.
Try wiping dalvik and cache and reinstalling the rom of choice.
Sent from my PC36100 using XDA App
I've had this issue before with numerous roms. I'm guessing it's because you either didn't wipe cache and dalvik cache, or that peticular kernel doesn't play nice with your phone. I'd really like to know what exactly is the problem as well....
I wiped data, cache, and dalvik-cache TWICE before flashing the ROM. Ill try wiping cache and dalvik and re-flashing the ROM. If that doesn't work I'll try one of netarchy's kernels.
Tried netarchys kernel and it didnt do anything. Tried to re-flash the ROM and it didnt do anything. Desperately trying to get this ROM to work
You could try the app SystemPanel lite to find what is using the CPU power.
Other than that try a different combo of roms and kernels.
It could just be the phone.
AtiRadeon1 said:
You could try the app SystemPanel lite to find what is using the CPU power.
Other than that try a different combo of roms and kernels.
It could just be the phone.
Click to expand...
Click to collapse
I have the full SystemPanel app. The top apps that use the most battery is of course System and Sense. The weird thing is, when it is at ~600 it says CPU usage is about 10%, compared to my phone that it is at 245 but still 10% usage. Weird. I am going to wait a couple of days and see if it is some sort of glitch and see how the battery is. I have had great success with netarchy's kernels, but I get INSANE battery life with the stock htc kernel.
What recovery are you using? Remember clockwork doesn't wipe correctly
Sent from my EVO at the edge of Hell
If an app is constantly running it could keep your CPU speed up
Last night (after a few drinks) I got playing in kernel manager and decided to flash a dal oc kernel I haven't used in a while. After its done flashing it puts me in a bootloop so I go to recovery (I always nandroid before I do ANYTHING) and go to my most recent back up, only it brings me to the "welcome to the nexxus s press here to get started" (I did the build.prop for Netflix). Any backup I go to its like I've done a full wipe and I'm starting from scratch with my new nexxus s. But here's the kicker.... my NC has NEVER been faster. This thing is lightning quick, no lag, no glitches, just the most responsive its ever been. I'm running cm7 nl 101, stock kernel and obviously nexxus s build.prop. Any ideas why none of my back ups work? And why the drastic change in responsiveness to my NC? I'm happy with the way its running but I put a lot of work into my setups and of course plants vs zombies lol.
Thanks in advance,
Dave
Sent from my Nexus S using XDA Premium App
I have 7 back ups going back to April and none of them work. It wont work via recovery or rom manager.
Sent from my phiremod for Nook using XDA Premium App
Recently my phone has been turning my 3G off by itself. When I turn it on, it stays on for about 10sec and then just turns off. I'm on Clean GB 1.1.2 and running Shadow kernel 3.0. Also I recently used the V6 supercharger. Anyone know anything that might be the problem?
Sent from my SPH-D700 using XDA App
Well I went to cm9 and clean gb back and forth for some time now and noticed that certain apps weren't working and signal was coming off and on solo, with out me pressing "data". And wifi was turning on and off by itself so I just used odin and reverted back to el30 and reflashed cleangb and no problems since than so I would definately recommened it.
And I did never find out why the hell that happened. I always wiped everything and never flashed data back to my calander, or messenger, or email app, etc.
Sent from my SPH-D700 using xda premium
Frostacious said:
Well I went to cm9 and clean gb back and forth for some time now and noticed that certain apps weren't working and signal was coming off and on solo, with out me pressing "data". And wifi was turning on and off by itself so I just used odin and reverted back to el30 and reflashed cleangb and no problems since than so I would definately recommened it.
And I did never find out why the hell that happened. I always wiped everything and never flashed data back to my calander, or messenger, or email app, etc.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Well nothing is turning itself on and off...the only thing happening is after i activate my 3G, it turns back off after a few seconds...i did find out it has something to with the V6 Supercharger, but its not that there is a problem with the supercharger because that runs great. Their is just something else on my phone that isn't playing well with the supercharger. I might just try to revert back to an old backup and go from there.
mrleprechaunboy said:
Well nothing is turning itself on and off...the only thing happening is after i activate my 3G, it turns back off after a few seconds...i did find out it has something to with the V6 Supercharger, but its not that there is a problem with the supercharger because that runs great. Their is just something else on my phone that isn't playing well with the supercharger. I might just try to revert back to an old backup and go from there.
Click to expand...
Click to collapse
Some of the init.d scripts don't play well with all phones and the V6 Supercharger. Use Root Explorer and go to system\etc\init.d folder and delete all scripts in there, reboot then reflash the V6 Supercharger. That should tell you if the V6 is the problem or not.
Make sure you are on the RIGHT version of busybox. Latest CM9's Busybox is too up to date I believe, at least for the Zeppelinrox 3G Turbocharger script I use anyway.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
Some of the init.d scripts don't play well with all phones and the V6 Supercharger. Use Root Explorer and go to system\etc\init.d folder and delete all scripts in there, reboot then reflash the V6 Supercharger. That should tell you if the V6 is the problem or not.
Click to expand...
Click to collapse
Alright i did what you said and before i even reflashed the supercharger, my 3G wasn't working. After I flashed it again it still wasn't working....so idk whats going on. This didn't start happening till I used the supercharger tho...is there anything in the init.d folder i needed that i deleted? I have a backup from earlier today if i need to go to that.
mrleprechaunboy said:
Alright i did what you said and before i even reflashed the supercharger, my 3G wasn't working. After I flashed it again it still wasn't working....so idk whats going on. This didn't start happening till I used the supercharger tho...is there anything in the init.d folder i needed that i deleted? I have a backup from earlier today if i need to go to that.
Click to expand...
Click to collapse
No. Some ROMs don't even have an init.d folder. I recommend Odin to EL30 or FC09 to get your 3G going again and then move forward from there.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
No. Some ROMs don't even have an init.d folder. I recommend Odin to EL30 or FC09 to get your 3G going again and then move forward from there.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Well I would have, but if i wast to go back to EL30 with my 3G, i have a backup from before I ever used the Supercharger...but i just switched to CM9 beta 2 anyway and 3G is working just fine now. Thanks for all the help tho
Howdy all!!
I'm currently running Franco Kernel r111 and the latest CM10.1 Nightly (20130327), and twice now I've woken up and my screen is black and won't turn on. The LED at the bottom is flashing a notification, but I can't wake the device. I have to hold the power button and then turn the device back on. The issue is, that I use this as my alarm clock, so it's made me late a few times now...
Is this the "SOD" that everyone is talking about? I think it's related to this most current nightly, as I've used r111 of Franco's Kernel along with the 23rd and 24th CM10.1 nightly and I didn't see the problem.
I guess my question is, is there something I can do to tell what is causing the crash? It's plugged into the charger, so could I run some app that will take a log that I can check the next morning if it should freeze?
Maybe you have undervolted too much, how much did you UV?. Try raising the voltage and see if that helps.
gee2012 said:
Maybe you have undervolted too much, how much did you UV?. Try raising the voltage and see if that helps.
Click to expand...
Click to collapse
I don't undervolt anymore on top of what Franco does by default.
jsylvia007 said:
I don't undervolt anymore on top of what Franco does by default.
Click to expand...
Click to collapse
Frano default is stock voltages, it is noy UV`d. Then maybe there is an installed app or widget that is going crazy and causes fc`s.
gee2012 said:
Frano default is stock voltages, it is noy UV`d. Then maybe there is an installed app or widget that is going crazy and causes fc`s.
Click to expand...
Click to collapse
That's why I was hoping someone knew of an app that might log things, so I can check after the reboot.
jsylvia007 said:
That's why I was hoping someone knew of an app that might log things, so I can check after the reboot.
Click to expand...
Click to collapse
Try BetterBatteryStatts, it shows activity`s of apps.
gee2012 said:
Try BetterBatteryStatts, it shows activity`s of apps.
Click to expand...
Click to collapse
I'm running that now actually, but I didn't think it's data persisted through a reboot.
Get a logcat via adb.
Sent from my Nexus 4 using xda premium
gravitysandwich said:
Get a logcat via adb.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
So, I assume I would do these steps:
1. When I wake up and notice that the device is "frozen", hold the power button to turn it off.
2. Boot the device into fastboot mode
3. Use ADB to pull the logcat
4. Reboot the phone normally
Forgive me, but I haven't used ADB to get a logcat, and I believe that if I do it after a reboot into the full OS, won't the new boot overwrite the logcat from the frozen state?
jsylvia007 said:
Howdy all!!
Is this the "SOD" that everyone is talking about?
Click to expand...
Click to collapse
Sounds like the "SOD" issue many of us have. It's cause is currently unknown although turning WiFi off may prevent this from happening.
xda6969 said:
Sounds like the "SOD" issue many of us have. It's cause is currently unknown.
Click to expand...
Click to collapse
Ok, this is good to know... I've only JUST started to experience it in the most current CM10.1 nightlies... It happened to me once a while back with a CM10.1 nightly, but the update the next day fixed it, and never showed up again until recently.
same here!
Hey all! havin same issues here! ;( Dont know why is it happenin, and most important, why it only happens sometimes.... :silly:
I attached a logcat to molesarecomming and he told me it is some kind of driver mess up I've done a full wipe and going totally stock with no luck, IDK what to do....
PD: I hav a thread here so if you can just take a look!
jsylvia007 said:
So, I assume I would do these steps:
1. When I wake up and notice that the device is "frozen", hold the power button to turn it off.
2. Boot the device into fastboot mode
3. Use ADB to pull the logcat
4. Reboot the phone normally
Forgive me, but I haven't used ADB to get a logcat, and I believe that if I do it after a reboot into the full OS, won't the new boot overwrite the logcat from the frozen state?
Click to expand...
Click to collapse
what I did: when i noticed my phone its frozen I just connect it to pc and use adb to pull logcat, without reboot.
malavi said:
Hey all! havin same issues here! ;( Dont know why is it happenin, and most important, why it only happens sometimes.... :silly:
I attached a logcat to molesarecomming and he told me it is some kind of driver mess up I've done a full wipe and going totally stock with no luck, IDK what to do....
PD: I hav a thread here so if you can just take a look!
what I did: when i noticed my phone its frozen I just connect it to pc and use adb to pull logcat, without reboot.
Click to expand...
Click to collapse
Why don't you open a ticket with Google support and send them the logcat?
No when its frozen plug it in the computer and type adb logcat in the cmd window. A cmd window should pop up with your logcat.
Sent from my Nexus 4 using xda premium
gee2012 said:
Frano default is stock voltages, it is noy UV`d.
Click to expand...
Click to collapse
The 1026MHz slot is UV'd by default on Franco kernel. Though that won't have anything to do with the OP's problem.
Sent from my Nexus 4
Black screen in morning, flashers take warning
VoiD_Dweller said:
Black screen in morning, flashers take warning
Click to expand...
Click to collapse
This made me LOL so hard...
In other news its definitely some combination of CM nightlies & Franco kernel. I'm now on the newest nightly and r116, and it didn't happen this morning.
When it happens again I will try the adb logcat and see what I can figure out.
Ok... So! I am running Franco Kernel r117 & CM10.1 Nightly 20130403... I had the black screen again for the first time in a few days...
I plugged the phone into my computer, started the Nexus Toolkit, and followed the options to pull a logcat over to my computer. The problem is, the screen stayed at "Waiting for Phone" for almost 15 minutes, and then I had to leave for work...
Any help here?