Develop Bugs

[Q] Random reboots related to specific ROMs?

I'm a total n00b to the rooting scene - going on almost a week with my rooted DInc - so apologies if this has been addressed (I can't find where its really been addressed definitively). Since I rooted (and only since), I'm occasionally having random reboots while my phone is sitting inactive on my desk. I've only used Sense ROMs (Virtuous, WarmZ, Nil's Business), and they all seem to have it. I have Nil's on now (love it so far!), and for two days, I thought the issue had gone away, but today it has rebooted twice in short order (about 30 minutes apart).
Some things I've observed about this:
- I haven't had it reboot yet while I was using my phone - only while sitting inactive on my desk at work.
- I do have pretty poor signal strength in my office - at rest, it usually shows just a bar, if that.
- The wifi connection I have available is also wonky (router issue, I think); I don't use it (or even have it remembered) because it will connect, but continuously drops and reconnects over and over (not a phone specific issue, used to happen to my BB Curve as well).
This doesn't rise anywhere close to a dealbreaker for me, as it reboots quickly and everything seems to return to normal, but I wanted to ask if anyone had a suggestion to remedy the problem.

Could be a lot of different things. Are you also using custom kernels? Some people will get random reboots when they overclock their processor, but since you say it happens when the device is idle, that sounds unlikely. There was a generation of GB kernels that would cause random reboots if the wi-fi policy allowed the wi-fi to sleep. Switching the wi-fi sleep policy to "never" was the workaround for these, but you are using Froyo and I'm not sure if this same bug ever affected any Froyo kernels.

I know when I ran lou's kernel (don't remember which version) I had a few massive lag moments where the phone was insanely slow and also a couple of random reboots (once was idle and screen off, other was during a phone call).
I didn't continue to run it for those reasons, actually only ran it for 2 days.
You may have better luck just flashing a different kernel with the same ROM you're on, I've had good luck with chad's sense incredikernel (25plusv) - that is, if you're looking for a suggestion for a kernel to flash

Run fix permissions in ROM Manager too.
Sent from my ADR6300 using XDA Premium App

Sleep of death

Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.

Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium

I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.

Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App

Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.

Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.

I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.

ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.

did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.

I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.

how often has the sod been happening? I think i got it yesterday, but not sure.

Do you use setcpu?
Sent from my SPH-D710 using Tapatalk

This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.

Random Reboots. Throw some ideas at me!

Hey guys, I constantly have random hot reboots. No pattern or anything, it just happens. I have asked a few guys in Calkulin's forum... everyone offered help... but no one actually helped me fix the issue.
Basically, I am on Calk's 2.0. Only other thing I flashed was Overstew's ICS theme (I used themeporter). No, my issue isn't the theme. I have had these issues since Calk's 1.5. Theme or no theme.
Here's my routine of setting roms up:
Manually wipe everything -sd card.
Use Calk's Format All.
Flash Calk's 2.0 and Overstew's theme.
Reboot.
Install Titanium, but only restore apps (41 apps), no data.
Set LauncherPro as my default launcher.
Setup my settings.
Just using Calk's stock battery saver script. No overclocking or undervolting.
I have tried wiping and new downloads several times. I wiped my external sd card. I even removed it, for a while.
Any ideas? I had a logcat during the hot reboot too. It had some errors around GPS right before it rebooted.
Thanks
P.S. I also had the same issue on my old Evo 3d. I just thought it was my hardware...

Undervolting is what Calk himself recommends to fix hot reboots. It's in the OP on his ROM threads. Also different kernels. Tried any of that?

wolfkstaag said:
Undervolting is what Calk himself recommends to fix hot reboots. It's in the OP on his ROM threads. Also different kernels. Tried any of that?
Click to expand...
Click to collapse
Actually, he recommends restoring the Stock Voltages to remove the default undervolting.
"Having random reboots or freezes?
Try flashing the Calkulin's_Undervolt_Stock_mV_Settings_for_E4GT zip attached or flash a different kernel

first thing that comes to mind is the viper los script

I don't have the Viper LOS. I have tried different kernels. Plus, isn't 2.0 using Rogue's stock anyway?
I'm not undervolted. 2.0 can't be undervolted without using tegrak :/ all great suggestions... it's driving me insane that I can't figure this out.
Sent from my SPH-D710 using XDA App

I am on Calks 1.5 rom and do not have any reboot issues. The first thing I do when I flash any new Rom is put back the stock pulled kernel and I believe this is the most stable of them all and I also have never seen an LOS on it.
Do you have any battery saving apps or task manager apps running? I know these have caused issues like this as well...

No. Nothing! I had stock pulled kernel before. Maybe I will try it again. But isn't it the same as Rogue stock + boot animation and init.d?
Sent from my SPH-D710 using XDA App

I used to have random reboots with different lockscreens from the AIO mod. Had no lockscreen and had no reboots.

Definately recommend stock kernel and restoring stock volt settings. As for Los, ek02 fixes it
If I was helpful, give thanks
Sent from my Epic 4g Touch

Hey I remember chatting with you in the Calk rom thread. "OP"
As a update to my situation. I was also having random hot reboots on EVERY rom I was on UNTILL my latest combination of Kernal / Rom.
My current setup is Kernal: EK02 and my rom is Calk v2.0 which is built on the EK02 stock build.
I have yet to have any hot reboots. My current Up Time is 38:58 which means I have not did a battery pull or reboot in 38 hours.
I also use Titanium Backup to restore about 30 apps + data on my end, and MyBackup Pro to restore bookmarks / texts
For the first time it looks like my hot reboots are currently fixed. I dont use any undervoltages and no SetCPU no custom launcher and no custom lockscreen. Everything Stock and all 7 home screens nearly filled with icons and picture frames ect...

I was using Rogue's kernel and was going to switch to stock today, as that was the only thing I didn't do... but I was in the middle of calibrating my battery this morning and I was getting great battery life. Well, 15 hours later, not one hot reboot, light usage (lots of texts through google voice and xda, and a little browsing) with a screen on time of 1:45 and I'm at 54%. Has my issue been fixed? I have no idea. Am I happy at the moment? F*ck yeah.
hypersonicx said:
Hey I remember chatting with you in the Calk rom thread. "OP"
As a update to my situation. I was also having random hot reboots on EVERY rom I was on UNTILL my latest combination of Kernal / Rom.
My current setup is Kernal: EK02 and my rom is Calk v2.0 which is built on the EK02 stock build.
I have yet to have any hot reboots. My current Up Time is 38:58 which means I have not did a battery pull or reboot in 38 hours.
I also use Titanium Backup to restore about 30 apps + data on my end, and MyBackup Pro to restore bookmarks / texts
For the first time it looks like my hot reboots are currently fixed. I dont use any undervoltages and no SetCPU no custom launcher and no custom lockscreen. Everything Stock and all 7 home screens nearly filled with icons and picture frames ect...
Click to expand...
Click to collapse
Sent from my SPH-D710 using XDA App

Moose8106 said:
I was using Rogue's kernel and was going to switch to stock today, as that was the only thing I didn't do... but I was in the middle of calibrating my battery this morning and I was getting great battery life. Well, 15 hours later, not one hot reboot, light usage (lots of texts through google voice and xda, and a little browsing) with a screen on time of 1:45 and I'm at 54%. Has my issue been fixed? I have no idea. Am I happy at the moment? F*ck yeah.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
After jumping to the EK02 Rom and Kernal Im also a happy camper now.
No reboots / No los / No lag / No dieing battery.
Now if only Sprint could fix there slow 3G that be great.
On the topic of battery, I never calibrated or did anything special but I noticed my phone can last 12hours + without charge if I turn off 3G when Im not using it. For example I work in a warehouse where I get good signal for calls and texts but 3G is mad slow, so I turn 3G off but am still able to recieve texts and calls and my battery life doubles in that period of time. Soon as I turn 3G back on, battery starts to die faster.

Torch + Full brightness = instant phone shut down

Ever since I got the Desire HD (which is a little over a week now), I am running MIUI on it as my daily ROM. I replaced the Torch.apk with the one from CyanogenMod 7.1 (just like I did with my old Desire), so I can have the Full brightness mode.
The Full brightness mode never caused any problems. I could use it, and also with strobe -- I was avoiding using it for extended periods of times, to not harm the LEDs. It was not on for more than 30 seconds continuously.
Now, it seems to be causing problems. I try to turn on the LEDs, on full brightness, and the phone would instantly shut down. Same happens with strobe. It's all good if I don't use full brightness, though.
It doesn't reboot or freeze or anything. It just SHUTS ITSELF DOWN!
I tried this with : MIUI with original CM kernel, with LorDModUE kernel, and also with CyanogenMod 7.1.0. I wanted to try with CyanogenMod 6.1.0, to see if that helps (yeah, silly), but it seems like the ROM isn't booting at all.
I went on ROM Manager, in the section for CyanogenMod, and saw some comments of other people who were experiencing the same problem. Some guy was saying that this is because of the battery. Well, I know this for sure : my battery is as good as new.
Anyone... any ideas...?! :/

which MIUI are you using. If you're using freshly sqeezed then i get no problem like that but if you're using other custom ones, it is possible that the customization done to the stock MIUI can cause problems, some scripts maybe? you should try using other MIUI versions..

shad0wboss said:
which MIUI are you using. If you're using freshly sqeezed then i get no problem like that but if you're using other custom ones, it is possible that the customization done to the stock MIUI can cause problems, some scripts maybe? you should try using other MIUI versions..
Click to expand...
Click to collapse
I'm using the UK variant (MIUIAndroid). Since I also tried with CyanogenMod 7.1.0, and it was the same issue... I doubt that matters.
Right now, I am having more serious problems. Phone shuts itself down after boot... It doesn't do that when it's in Hboot or Recovery. I even flashed 3 other ROMs upon full wipe.
Battery : 49%. Phone shuts down.
Going into Hboot. 5 minutes, no shut down.
Going into Recovery. It shows battery is at 25%.
Reboot.
Now it shows that I have 11% left.
I guess LorDModUE's overcharging thing kind of messed up with this battery. Otherwise, I see no reason for it to act like this, since I barely used the phone today, and it was at 80% when I left home this morning (GMT+2, that is).
I'll just charge it now... then I'll have to go out. I'll flash Tiamat kernel, see how it handles THAT.

My battery is very faulty, alright. I'll buy a MOMAX X-Level battery (of 1150 mAh) next week.

what rom are you on?
i had the same problem on a previous rom, i changed over and it was sorted.
not to sure why it happens though.

MrLarner said:
what rom are you on?
i had the same problem on a previous rom, i changed over and it was sorted.
not to sure why it happens though.
Click to expand...
Click to collapse
I am on the latest MIUI (MIUIAndroid, not US). I also tried with CyanogenMod 7.1. I believe it's the battery, which barely holds half of the charge... I'm going to replace it soon, see if THAT solves the problem.
As I originally said, it didn't cause any trouble at all the first few days... just like the battery...
--
EDIT. It really was the battery. Got a new one now and it works to have Torch on full brightness.
I still don't get why it would turn off the phone even with the battery ~fully charged and the charger still connected.

can someone tell me please, where to get this torch-app with full brightness. I've tested it on jellytime, but now I'm on a different ROM.
Loved this heavy brightness... :cyclops:

Sleep Of Death

I don't know if this possible but I really like to find out if there is something causing the SOD that we can actually do something about(as in it isn't hardware causing it). I get SOD's on some repack kernels but not on others. When I get it has quite frequently. I am not running setcpu nor do I have any other software controlling the cpu. I have however been using juice defender. I like the product. I am going to remove it and flash a repack kernel that I know gives me SOD's and see if something in the power saving on the JD might be contributing to it. I would like to hear from others that have this issue and see if you are running anything like setcpu or JD.

I've been thinking of something. I don't have sod at all. For those that do have sod how good is your phone at overclocking? Meaning can it run stable at like 1.6 or where does it freeze at?
I'm wondering if its something to do with the difference of processors.
If anyone needs any help with the epic touch hit me up on Gtalk @musclehead84

I dont really overclock anymore but when i used to, my phone froze at 1.6. This was back when i was on calk eg30 rom. Idk what would now if i tried again
Sent from my SPH-D710 using xda premium

I haven't oc'd mine so I am not sure what it is capable of. Tomorrow I will disable the JD and flash a repack and see if that has any effect. It is frustrating because I love the repack rom's. For now I use mobile odin to flash a repack and boot to recovery if I want to nandroid then flash the stock kernel back again.

I had it until I updated modem, and when I say had it I mean right after flashing an ics rom, and every time after the phone sat with screen off for more then a minute, can run at 1.6 no problem, don't see a point though
Sent from my SPH-D710 using Tapatalk

badname said:
I had it until I updated modem, and when I say had it I mean right after flashing an ics rom, and every time after the phone sat with screen off for more then a minute, can run at 1.6 no problem, don't see a point though
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I was just curious because on the original epic I had sod on some kernels and that phones processor was terrible. It froze when I tried to overclock it. The next one I got I wad able to overclock and I never had sod. Just seeing if phones with not being able to overclock might have an issue right now.
If anyone needs any help with the epic touch hit me up on Gtalk @musclehead84

Are you using SetCPU? If so, don't fix screen off at 200-500.

Yeah we really meed to figure out what the heck is going on. For the last few days i've been trying to figure out why i've been having SoD. Im on blazer ROM and ive found out that if I don't flash a new kernel i'm fine. But as soon as I flash rouge 1.4.1 or 1.4.0 I get an onslaught of SoD. Things ive tries to fix it are:
-Installing set CPU and raising the voltage and changing gov. to on demand.
-taking all the init.d scripts out of the blazer ROM zip before flashing.
-I find that when the phone is on the charger it never gets SoD
That last point leads me to believe that it has something to do with deep sleep. Because when the phone Is plugged in it isnt allowed into deep sleep mode and idles at 200Mhz. Ill be looking into this more tonight. If anyone would like to work with me i'm always in the e4gt ics dev channel on freenode.
Sent from my SPH-D710 using XDA

Do you run Juice Defender or any other power saving app? I am on an ICS rom and when I flash the repack, almost everytime I power off the screen I get an SOD. I am getting ready to disable JD and flash the repack and see if that makes a difference.
UPDATE: I disabled juice defender and flashed the repack. Have gone for 40 minutes without an sod. I am going to enable the jd but change several of the settings to see if that will allow me to run it with the repack and not get frequent sod's

ElAguila said:
Do you run Juice Defender or any other power saving app? I am on an ICS rom and when I flash the repack, almost everytime I power off the screen I get an SOD. I am getting ready to disable JD and flash the repack and see if that makes a difference.
UPDATE: I disabled juice defender and flashed the repack. Have gone for 40 minutes without an sod. I am going to enable the jd but change several of the settings to see if that will allow me to run it with the repack and not get frequent sod's
Click to expand...
Click to collapse
you know....oddly enough I did install juice defender a few days ago....then flashed the 1.4.0 kernel and thats when everything started.....BUT ive since reflashed the rom a million times without re installing JD and i still get SoD with the 1.4.0 kernel
If you continue to not get Sleep of deaths...will you try flashing 1.4.1 or 1.4.0?

Just to clarify, does the SOD issue include texts/calls not going thru whatsoever while phone sleeping on or off charger for more than ten minutes? I get this with any ICS up to 06, when people call me it goes to VM directly, texts go to sprint limbo. Or, do these leaks just horribly handle low signal areas? I was on stock 85 prl, and signal was about 0-1 bar sprint and force roamed on 1xrtt for 2-3 bars... since this screwed me on a couple important calls I reverted to EL29 and flashed 111115 PRL... anyone have these issues with ICS, or is it just my **** reception and network issues?
Oh, and I SWEAR... no conspiracy theory... but anyone notice pretty much all samsung leaks have issues that are magically fixed for final release? Epic froyo, GB, now ICS on the Epic Touch... just sayin... its like they dont want us daily driving these... just use em enough to beta test (really this site should be renamed XDA Beta Testers)?

The issue you are talking about sounds more like the loss of service bug that has plagued some of these phones. the sleep of death is when the screen turns off and then you can't get the phone to come back on with out holding the power button for 10 seconds or pulling the battery. I am still doing fine. I enabled juice defender but selected advanced settings and disabled jd from controlling the auto sync. I set the controls options to default. So far I haven't had an sod. I will see if I can flash those repacks but I am not sure if it will work right since I am on an ICS rom.

SoD almost certainly involves the cpu going into deep sleep and not coming out. I have never experienced this issue on the E4gT on any rom/kernel combo, but I dealt with the issue extensively on the nook color it it's early days. I can definitively say that because a large number of users are using the repacked kernels and are not having SoD issues, then it is 100% NOT repacked kernel related. SoD is caused by voltage issues or cpu step switching problems. The repacked kernels are identical in these regards across all users, therefore the repacked kernels are not causing the SoD issues.

I've had the SoD a few times on FC05 and FC06 - I'm in the process of downloading FC07 right now. It doesn't happen often (3, maybe 4 times in a few days) and I cannot pinpoint any actions preceding it. I no longer have Juice Defender installed. It's odd though, I've also had problems receiving Kik messages after a reboot. My girlfriend sent me a few messages 6 hours ago that I didn't get until I opened the app, then it's back to normal. This is a pretty regular problem. It's like I have to kick start the app before it starts. But over that 6 hours I streamed Pandora just fine and Gmail has been syncing as normal.

It is a puzzling issue. I also don't think the repack kernels acutally cause it to happen but there is something about the issue that causes it to happen frequently when using a repack. I can go back to any of the stock kernels and it works fine even with juice defender running. That is why I thought perhaps it was some app like juice defender that was causing it but people still have the issue without juice defender. Fortunately for me it seems the fix was to disable juice defender. Unfortunately for my battery though.

Well so far it seems that ive found my solution. All i did was grab the 1 click Odin to Stock Rooted EL29 and wiped everything. I wiped internal storage and flashed back to rooted stock with odin. Then i Odin'd a kernel and flashed back to blazer rom and then had to re odin the rouge kernel that was originally giving me issues. So far all is well. I suggest giving it a shot