I have been having my phone shut off for no reason at least 5 times a day. Even when phone is in sleep mode. When I wake my phone I have the bamf toolkit in my notification bar that says unclean shutdown settings not applied, that's how I know it keeps rebooting while in sleep mode. Only reason I haven't made the jump to 1.7 is because I like the extras that are made for 1.6.3. I didn't wanna try and flash 1.7 and then apply 1.6.3 mods. Running stock kernel that came with Rom. It didn't used to do anything like this when I first installed it. It seems like it's getting worse over time. Anybody else having the same problem or similar? Any ideas or thoughts would be helpful. I'm actually thinking about putting GB back on. I just wish I knew what the odds of me ending up with a expensive brick were before i put it back on.
I had the same problem. Flashing the second radio on the radio thread finally solved the problem for me.
Related
I have a problem where the clock / time will lag behind by a few minutes over time on EB01-based ROMs? I know that there were a few people that posted about this in the custom ROM threads, but I couldn't find any potential solutions.
I have tried auto-syncing the time off of the Verizon network, as well as manually setting the time - same problem in both cases. If it is relevant, I'm using a Blackhole 4.2 ROM.
(1) Does anybody else have this problem? It might help to see how widespread this is.
(2) Does anybody know of a solution to this?
I've had time issues with all of the EB01 roms I've tried. I think it has something to do with not having the original kernal or something (if I was a dev, I could fix it myself, lol). Anyway, the best solution I've found is to install "clocksync" from the market. It's free and you can set it to update every 30 seconds or so.
Hmm I keep hearing about clock lag on Froyo but I haven't had it on any of my roms. I've used stock, deodexed, super clean 2.3, and now black hole 4.21. No clock lag on any of them, my kernal has been switched off and on between voodoo and normal so idk. It's on auto sync from the network too so I'm not sure what the problem is. Maybe try the EB01 Odin package?
I have been running different EB01 releases since it leaked, and I did not have this problem at all until yesterday. It doesn't seem to just slowly drift behind, but it does end up falling behind anywhere from 9-18 minutes from what I have seen so far. Then, it will just sync fine, as it is currently reporting the correct time.
I had the problem for a day and it seemed to go away when I reprogrammed my towers with the *228 function. If you haven't done that already, you should try that.
Never had this issue. Is this happening with the clock in the status bar or a widget? If its a widget it could be a task killer killing the widget and its not restarting. But if its the status bar clock I suggest you use eb01 clock remove.zip. ;-)
I'm with all the others never had batt issues, clock issues, or the infamous sleep of death.
Used my fascinating voodoo powers
I too am having problems. But I also have problems if I turn auto time sync off, so it leads me to believe it is some kernel issue? I've had this issue with Super Clean and Vanilla.
Is that *228 command 2 that you're suggesting?
This is certainly very annoying..
JJRocker said:
I had the problem for a day and it seemed to go away when I reprogrammed my towers with the *228 function. If you haven't done that already, you should try that.
Click to expand...
Click to collapse
Excellent! I'll give this a whirl once wife is back with her phone! Thanks!!!
No issues as stated here. SC2.2.
good day.
Never had any of the EB01 issues till the clock lag. I just did the *228 since going to SC 2.6 so time (HeHe) will tell.
It's not enough to make me go off SC 2.x. It's only my 2nd day on SC 2.6 so I'm still watching the issue.
Have SC 2.7. I had the clock issue once, but it was fine after I restarted the phone and never had it again.
Only rooted/flashed once with Odin with EBO1 Debl/Deodex. Also using PhoneWeaver auto profiling.
I lose about a hour overnight when I let PW turn off the phone at 11:30 PM and back on at 6 AM. Last night, I tried turning OFF Automatic (use network provided values), and the phone lost 45 minutes in 2 hours. Turning Automatic back on manually didn't let the phone catch up until after a reboot.
My temporary solution is to let PW turn the phone back on an hour or 2 early so it will be sure to catch up before I need the alarm to go off, but it is a bit alarming to depend on it so looking forward to more complete Kernels/ROMs that I know are being diligently worked on as we speak.
I recently went from the original leaked froyo rom to super clean 2.9. Ever since I flashed that rom I have had the sleep of death. When I say that my phone has the sleep of death that is Everytime my phone goes to sleep. I have tried many things...I have tried using odin and flashing back to the original and them putting 2.9 and even going to 2.9.1. I have also went as far as not even installing titanium period. I eventually gave up and tried installing DarkRevenge v3 and am having the same results. I guess my only option is to go back to stock non-froyo. I have read that it is a froyo issue, but can't understand why I never had a problem with the original froyo leak. I honestly believe that I had the same kernel every time. I believe that I first had the froyo leak with DL09 then upgraded to the EB01. Let me add that each upgrade I never used voodoo, nor have I ever used voodoo...to my knowledge. I also went into wifi settings and changed the sleep policy to the plugged in option in hopes of saving battery life and thought it might be what was causing the issue, but it is not after switching back and having the same results.
If anybody has any ideas it would greatly be appreciated. I have tried wiping everything and flashing all roms according to instructions to a "T". If my SOD problem with just once or twice a day it would be tolerable, but every time has got to be a pain, especially since I have to take the phone out of the case and do a battery pull. Of course my battery life sucks, but that is acceptable. I am hoping that someone can help me with this issue before I go back to stock. I really like SC 2.9 and DarkRevenge v3 these roms are sooooo awesome. There again I am scared when I go back to stock I will still get the SOD...I hope not.
Thanks,
Leroy \oo/
Having the EXACT same issue ... any success?
I had to go back to a non froyo rom. I went with dl05 super dark with voodoo5 kernel. It runs great with no sod and awsome battery life with no froyo though. I might do some experimenting this weekend and I will let you know if I find any solutions.
Sent from my SCH-I500 using Tapatalk
Ive had a thunderbolt since launch and im aware that the phone has a tendency to reboot itself. I however have not seen it reboot, but just power down. This has happened on CM7, das Bamf, and Liquid Thundersense. It this the same as the rebooting everyone else is having or is my issue something else. It only happens about once a day, sometimes not at all, but it seems to kill my battery dropping it down about 10%. Thanks.
dmrnhs said:
Ive had a thunderbolt since launch and im aware that the phone has a tendency to reboot itself. I however have not seen it reboot, but just power down. This has happened on CM7, das Bamf, and Liquid Thundersense. It this the same as the rebooting everyone else is having or is my issue something else. It only happens about once a day, sometimes not at all, but it seems to kill my battery dropping it down about 10%. Thanks.
Click to expand...
Click to collapse
Go back to stock. If it continues to happen it is a phone problem and you would be eligible for a warranty replacement.
If you are overclocking it, that may be the first thing you want to try and just disable that and see how it goes.
i jus opened a thread 2 days ago about this issue aswell. it might be the stock radio as i was told. flash over it with some of the ones on this forum. happened to me even on mr1 release and its hardly overclocked. when i changed out my radio seems to be fine.
Sent from my ThunderBolt using XDA App
So I've had less than stellar luck with this phone. I purchased it and rooted it pretty much on day 1, (this was back in early May) and immediately started seeing some pretty awful rebooting. I switched kernels from Das Bamf's to Imoseyon's, which helped it go from mind-numbing to merely bad (used to reboot EVERY TIME the screen was slept and turned back on, went to happening maybe once an hour)
I switched back to stock, same problem, rebooting literally once an hour. I called Verizon for troubleshooting help and they immediately had me switch it out for a Hardware version 2.0 phone, which I've now had since May 15th. It does work a lot better, but it's still pretty bad. Here's the timeline:
Ran stock for about a week, was seeing 1 reboot every other day, decided to root. Installed BAMF remix 1.7 with the .7/.6 CDMA/LTE radio, which left it pretty much the same, rebooting every 30 hours or so. It's particularly likely to do it when using Navigation or on phone calls. It's not a stress thing, I can run Linpack, quadrant, make calls and surf, whatever, it runs fine at stock speeds, 1.92, 1.92x... and will do so for hours without rebooting (until it does)
Switched to 2.0 w/ the MR2 radio, and the reboots were even worse. Now more like 1-2 times a day. Thinking this was not a radio issue now, I eased down the clock speed (I was running 1.92x kernel) down to stock speeds, no affect. Upped the voltage by switching to 1.92, still no affect, reboots a couple of times day, ALSO with a few random shutdowns thrown in for fun. I tried Standard as well, letting it top out at 1.4, still having the issue.
MR2.5 came out, switched to that, and it became unuseable. Reboots literally every 5-10 minutes, and I tried running it that way for the better part of a day, thinking it was maybe the kernel settling or whatever, but it stayed that bad. I switched back to 2.0 and kept seeing the reboots a couple of times a day, so since they were worse on GB I figured I'd go back to Froyo.
Loaded 1.8 Remix, and the reboots are still happening a few times day. At my wit's end, I decided to go straight back to stock, no root. It ran fine that way for about a day, then randomly shutdown again. It has seemed good so far today, but the random shutdown happening makes me assume it's still not stable.
I really don't think it's a problem with 2 phones in a row, and there's thousands of posts of people experiencing similar problems, so it's not something weird I'm particularly doing. There seems to be no rhyme or reason to it, as some people are rock solid with Froyo with the .7 radios, or the .6/.7 combo, or some are fine with Gingerbread MR2, or even 2.5. Me, I have no luck with ANYTHING.
Should I start another ticket with Verizon for another dud phone, or is the promised OTA update really going to do something magical that MR 2 or 2.5 haven't already tried to do to fix this thing?
If it were me Id be screaming at somebody at Verizon. If your sure that nothing u did rooting or flashing roms caused the reboots then get a new phone. Rumors say that gingerbread is coming tomorrow but you can't out to much stock in that and even if it does I doubt there is any miracle code written in that's gonna help you.
Sent from my ADR6400L using XDA App
Some people have had random reboots on stock rom. But since you were on stock for less than a day, it's impossible to determine whether the reboots are due to a defective phone or something that happened during/after you flashed the custom rom. You obviously know your way around various roms, radios & kernel/cpu tweaks, and nothing seems to help. If you have the patience, go to the IRC channel for more suggestions. If no one there can help, I would restore to stock & exchange the phone. You may have a defective device that will never work right.
So I was pretty faithful to MIUI because of a lot of reasons, but i couldn't easily switch between 2 calls when i had a couple people on the line... Being that i use my phone a lot for business, I decided to go back to Sense as it's very easy and straight forward in terms of call switching...
I decided on Meanrom because of all the hype about the speed, battery life, etc...
I went to this thread and followed these instructions:
mikeyxda said:
Before you Install, prepare:
2.17.651.5 ROMs need the latest firmware. See freeza's all in one firmware update if you haven't done that already. If you unlocked via the HTC method, you know the drill: you'll have to take the OTA and then re-unlock.
If you are already running an older version of MeanROM, you should be OK just flashing this ROM without a full wipe, BUT...
If you have any trouble at all, do a super wipe and then install the above firmware and this ROM
Go to "Menu", "Settings", "Power" and UNcheck "Fast Boot". When you reboot or power off the phone, you really want it to reboot/power-off. This can save you a lot of headaches.
Click to expand...
Click to collapse
Since then, my phone will randomly lock up completely requiring a battery pull to restart it. (not even vol-up+vol-down+power is working)
sometimes it locks while the screen is on, sometimes while off... red light usually flashes when it locks with screen off....
after a lockup it seems like the battery loses like 25% or more once rebooted.
It seems like its usually after a call, or switching on/off Wifi, etc.
Battery life on this phone has never been worse!
Thinking that my issues were with the rom, i tried infected rom, same issue, then i went back to MIUI.... still same issues...
Anyway.... Different roms, different Kernels, same problems, leads me to think that this is a radio issue... anyone point me in the right direction??
I am on the verge of smashing this piece of **** with a large hammer if i can't get it fixed... so save a phone, and my sanity, please.
thanks!
Unfortunately I don't have any answers as I just s-offed/rooted my phone for the first time tonight, but considering I am planning on installing the same firmware upgrades/rom, you wouldn't happen to know if your Evo is HBOOT 1.3/1.4?
I have read about firmware issues with 1.5 elsewhere, but I've got a Nand backup and HBOOT 1.4 so I'm feeling lucky.
byg.nick said:
So I was pretty faithful to MIUI because of a lot of reasons, but i couldn't easily switch between 2 calls when i had a couple people on the line... Being that i use my phone a lot for business, I decided to go back to Sense as it's very easy and straight forward in terms of call switching...
I decided on Meanrom because of all the hype about the speed, battery life, etc...
I went to this thread and followed these instructions:
Since then, my phone will randomly lock up completely requiring a battery pull to restart it. (not even vol-up+vol-down+power is working)
sometimes it locks while the screen is on, sometimes while off... red light usually flashes when it locks with screen off....
after a lockup it seems like the battery loses like 25% or more once rebooted.
It seems like its usually after a call, or switching on/off Wifi, etc.
Battery life on this phone has never been worse!
Thinking that my issues were with the rom, i tried infected rom, same issue, then i went back to MIUI.... still same issues...
Anyway.... Different roms, different Kernels, same problems, leads me to think that this is a radio issue... anyone point me in the right direction??
I am on the verge of smashing this piece of **** with a large hammer if i can't get it fixed... so save a phone, and my sanity, please.
thanks!
Click to expand...
Click to collapse
if your talking about meanrom's ICS build: Chad had a fix for this that didnt require flasing rogue firmware - but he had to remove it from XDA. some of the newer ics roms may work w/ older firmware.. if not, search for chads ics test kernel.