I foolishly set my kernel to OC to the max in CM7, with "Set at boot" checked (stupid, stupid, stupid...), and now LPP keeps crashing on boot, so I am unable to get to Performance Settings to reset the clock speed. I was running the Tiamat kernel at the time, but have since flashed stock over it to no avail.
Short of a full wipe, what can I do to get my CPU back to a more sane speed? I haven't done a full TiBackup in a few days, so I'd like to avoid the nuclear option if I can.
Try booting it in safe mode.
Hold the menu button while you turn the device on. (I think that's how you do it.)
It should let you fix SetCPU.
godsmacked4653 said:
Try booting it in safe mode.
Hold the menu button while you turn the device on. (I think that's how you do it.)
It should let you fix SetCPU.
Click to expand...
Click to collapse
I wasn't using SetCPU; I was using the Performance Settings within CM7. And as it turns out, my problems weren't related to overclocking: I was running at 998MHz once I flashed back to the stock kernel.
Regardless, I ended up being able to get into TiBackup to get an up-to-date backup set, then wiped and reinstalled. Much better now.
Related
Hey guys, little issue that I can't figure out.
If I flash a rom with a kernel included of course I do not have any issues.
As soon as I try changing the kernel this is where I have issues.
The issue is that when I turn the screen off and the phone sleeps, after about 5 minutes it will not wake back up. I have to do a battery pull and eventually reflash the rom due to improper shut down/corrupt file system.
I have even tried flashing the rom and the kernel in the same recovery session to no avail.
I wipe cache and dalvik any time I flash something.
Running SRF 1.1.0 and have tried numerous kernels including twilight and genocide.
Did this also on SRF 1.0.2
Does your screen flash during the kernel flash process? It should show blue letters.
063_XOBX said:
Does your screen flash during the kernel flash process? It should show blue letters.
Click to expand...
Click to collapse
Yes it flashes and shows the random misplaced words. The kernels flash just fine but they all give me the screen of death after sleeping for 5 minutes or so.
Are you doing any over/underclocking using SetCPU or Overclock widget?
063_XOBX said:
Are you doing any over/underclocking using SetCPU or Overclock widget?
Click to expand...
Click to collapse
No, it will do it without changing anything. I do not have to even have setcpu or anything installed.
Then I think it might simply be that you have one of the poorer quality processors that don't handle undervolting well.
or its set to 100 as low and some phones dont wake from that...get setcpu and change it to 200 - whatever...or /system/etc/init.d and edit the 24-cpufreq file..
scroll down and it should say
echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governer
Here you can change the governer..from conservative to on-demand wtvr..
and here:
#echo "100000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
change the "100000" to "200000" and your phone should have no problem waking.. you can also overclock (if the kernel has the options) by changing the lines above:
#echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
change "1000000" to "1200000" or the freq you want and kernel can achieve..
I have tried installing setcpu and setting minimum to 200mhz, tried conservative and ondemand with same results.
I have 1 time successfully ran vision kernel. Even at 1.4ghz it ran fine for 3 days.
Isn't the default with SRF already underclocked? It runs fine on the default kernel.
I was having the same issues as you as well. I ODIN'd back to EB13, rooted using CWM 2.5.5, stayed on RFS, and I haven't experienced that issue yet. I am currently running the Viper 5.0 ROM. Performance isn't where I would like it, but it's running fine. I wonder if it is an EXT4 issue on some phones.
Hey!
My Defy stopped working with any Overclock app. With 2.1, it started failing yesterday, I don't remember why, I guess I installed something (i think defy2ndinit) and since then every time i try to OC with Setvsel ou Milestone Overclock the phone reboots.
I looked into the 2ndinit boot and found some OC settings, I tried to OC through those options but it loops at the M logo.
Today i upgraded to 2.2, did a factory reset, reinstalled everything, rooted, etc etc, and still, it's not working. It Keeps rebooting everytime I apply any new OC setting.
Guess I need some help.
Thanks!
EDIT: I was able to OC it with a 58vsel @1000Mhz, lower than this setting, it reboots (Only via Setvsel, using "APPLY + QUIT").
Any clues, please?
Changing my brightness in the settings doesn't do anything.
It seems like its stuck on auto brightness but its turned off?
I am on the latest jugg rom and kernel
you have to turn off auto, before you can change brightness
I know.
I unchecked it in settings than i start moving the slider for the brightness and nothing happens! I noticed this a few days back.
Are there any adb commands i can run thru shell for screen brightness?
check to see if you have enabled power saving mode
AllGamer said:
check to see if you have enabled power saving mode
Click to expand...
Click to collapse
its disabled
edit: just downloaded some app called screen brightness off the market, doesnt do a thing! i just hope its not a hardware thing.
It used to work just fine im not sure what happened. I read on beastmod thread that melvin included "auto brightness to save battery" but after a complete wipe and fresh install of a different rom wouldnt that go away?
if you're on Juggernaut 2.5 this is normal... update to Juggernaut 2.6
if you are on 2.6 did you wipe everything?
Yes running latest jugg gear. Full wiped & fixed permissions.
Anyone have any suggestions? I've never had this problem before and I've been an android user for 3 years.
This is very strange to me. I wonder if i should go back to stock to see if the issue still persist.
I had the problem for the first time on 2.5 no matter what kernel I used. The problem is gone now on 2.6 with it's stock kernel.
life02 said:
I had the problem for the first time on 2.5 no matter what kernel I used. The problem is gone now on 2.6 with it's stock kernel.
Click to expand...
Click to collapse
interesting.. i might try and flash the stock kernel to see if it fixes the issue.
I've been having a problem with my phone hot rebooting every 30 seconds to 5 five minutes. It's driving me up the wall. I can barely even use it, since half the time I have no data, and the other half by the time I can get anything open, the phone is rebooting.
I've tried:
- Changing ROMs (Juggernaut 2.5 to 2.6 and back to 2.0; Bombaridier; EagleBlood; Streamlined)
- Changing kernels (stock, Jugs, Bullet, whatever kernels come with the ROMs mentioned above)
- pulling the SD card
- formatting the SD card
- fixing permissions
- factory/data reset, wipe cache, wipe Dalvik every time I flash
One thing I did notice... the last ROM I tried was EagleBlood, and it was fine for half a day. I charged it overnight, and, thinking my problem was solved, I decided to calibrate the battery. After wiping battery stats, it's rebooting over and over again.
I just unrooted and took it back to stock to see if that does anything.
In the meantime, any ideas? Please help... I'm getting ready to tear my hair out.
normally the reboots are due not Wiping, but you did say, you Wiped, so it should be fine
did you OVER Volted the CPU at any point?
No. I overclocked and undervolted when on Juggernaut/Jugs, but at no point did I ever overvolt.
how aggresive were your overclocks. because that could be the problem itself
or if the kernel is undervolted and the cpu's dont like it .
Max 1.89/min 384 and UV -2500 when on Juggernaut, but after I started having the problem, I didn't even install SetCPU anymore. When I was on EagleBlood, it wasn't OCed or UVed at all, didn't have SetCPU installed, and it still rebooted all the time.
OK, I've been unrooted for a couple of hours and no rebooting. But being unrooted sucks! I don't even want to think about re-installing all my apps without Titanium Backup.
So I just Odin flashed CWM and am flashing the SGH-T989 // UVKID // Stock // Deodexed // Rooted //Busybox ROM so I can at least run TB and get all my apps back. Then we'll see what happens.
I'm afraid to calibrate my battery though... Haha... I think the FIRST time I started having this problem was after a battery stats wipe. And then after running EB with no problems for several hours, after wiping battery stats... BOOM! It started happening again. But why would wiping battery stats make this happen?
your using CWM for everything? or RM?
CWM. I've never used RM... Should I?
OK, after restoring everything with Titanium Backup, it's doing it again. So it's gotta be an app... right...? How on earth do I figure out which one?
this is why i never use Titanium backup
your going to have to install each app one at a time to see which is causing conflict
I just have the same problem, keeps rebooting basically every 30 seconds to a minute... and it is not rooted, no new apps but I did update the firmware via Kies in the morning, it only started rebooting in the middle of the night, had to shut it down to be able to sleep.
No idea what to do...
The phone is useless as it is.
Any hints are welcome, thanks.
Something new has developed with an otherwise trouble free device!
It started about a week ago. I use Drudge Report app which is buggy (will cause device to stop responding before box "Drudge Report has stopped responding, close/report) and I always close, everything is fine. Well until this last time, it did not close and device locked up before rebooting on its own.
It keeps rebooting so I pull battery. Still in a boot loop!
I boot to recovery, clear cache/Dalvik, still no go.
Download and flash EFS fixer, still stuck!
Finally wiped device, reflashed DarthStalker 6.0, everything seems good.
Restored TiB and rebooted and now the device will get to the unlock screen, then reboot. It will do this 3X before working normally.
No instability at all, just a 3X boot cycle when rebooting.
Tried Compulsion Standard, Ultimate, Sabre, etc. All custom kernels will do this!
The Stock Samsung kernel, however does NOT do this!
Weird isn't it?
I'd prefer to run one of the custom kernels due to better performance and battery life, however.
I don't restart the device that often, however I am concerned that doing this means something is wrong and thus raises concern.
Anyone else have this issue?
I do use TricksterMOD pay version and checked to make sure it was not applying some defunct settings at boot and it was not. Not sure why only the stock kernel does not result in what I'm calling the "triple pump boot" though!
You probably fried something man. Or who knows these phones are soo sensitive dude. All I do is mess with some tweaks with wanam and it causes my phone to bootloop 1x then reboot like nothing. Pin pointing what causes it.
Sent from my SM-N900T using xda app-developers app
possiblebootloop fix
Look for the thread that has the zip called bootloop fix. it worked for me. i was sweating bullets.
cpufrost said:
Something new has developed with an otherwise trouble free device!
It started about a week ago. I use Drudge Report app which is buggy (will cause device to stop responding before box "Drudge Report has stopped responding, close/report) and I always close, everything is fine. Well until this last time, it did not close and device locked up before rebooting on its own.
It keeps rebooting so I pull battery. Still in a boot loop!
I boot to recovery, clear cache/Dalvik, still no go.
Download and flash EFS fixer, still stuck!
Finally wiped device, reflashed DarthStalker 6.0, everything seems good.
Restored TiB and rebooted and now the device will get to the unlock screen, then reboot. It will do this 3X before working normally.
No instability at all, just a 3X boot cycle when rebooting.
Tried Compulsion Standard, Ultimate, Sabre, etc. All custom kernels will do this!
The Stock Samsung kernel, however does NOT do this!
Weird isn't it?
I'd prefer to run one of the custom kernels due to better performance and battery life, however.
I don't restart the device that often, however I am concerned that doing this means something is wrong and thus raises concern.
Anyone else have this issue?
I do use TricksterMOD pay version and checked to make sure it was not applying some defunct settings at boot and it was not. Not sure why only the stock kernel does not result in what I'm calling the "triple pump boot" though!
Click to expand...
Click to collapse
He said he tried that EFS fixer
Sent from my SM-N900T using xda app-developers app