Related
So just a few minutes ago, I had my phone on my desk and out of the corner of my eye I noticed my screen went from off to on, and not my lockscreen, but the white HTC logo that you get when the phone boots up. It just up and rebooted on its own. The last few things I did was update Kernel Manager and install IP Address Widget. Running 4.4.2 kernel and BAMF 1.5-NTE.
Any Ideas?
are you overclocking at all?
were you tethering?
was the phone hot?
Are you familiar with ADB?
Same thing happened to me a little while ago, BAMF remix 1.5 o/ced to 1.2. Been stable for about 30 minutes since reboot.
Sent from Thor's hammer on a bolt of lightning.
babybacon said:
are you overclocking at all?
were you tethering?
was the phone hot?
Are you familiar with ADB?
Click to expand...
Click to collapse
Didn't have my SetCPU to o/c
No tethering
I'm pretty sure it wasn't hot
I do know how to use ADB
Ive been having this same problem lately. It seems to happen primarily when i have aDownloader running(torrent app). It did happen once though while i was playing Angry Birds. I called Verizon about it but was told the only kkown issue with the TB is the battery issue... An in store rep however stated that he dealt with this problem before and said its an issue with the battery contacts and to clean them. I did give them a cleaning but the phone still reboots by itself. Its only happened about 3-4 times in the past week but still annoying nonetheless.
Had it happen again today on the way home.
BAMF Remix 1.5 o/ced to 1.2ghz.
On 4G
In the car dock on the car charger running nav.
After the reboot I checked the temp in SetCPU and I was running 40c. Turned off the charger and killed Car Home and the temp dropped like a rock to the mid 20s with in 5-10 minutes.
Same thing with 4.4.2 kernel. Maybe just too undervolted for some of our phones.
Sent from my ADR6400L using XDA Premium App
Mine is still STOCK. It does reboot every now and then. So I can proudly say that it isn't just because of the rooted/flashed, OCed and whatnot. I wonder what could be causing it? Oh and my stock text messaging app slows to a crawl and pulls the E-brake. I have to reboot to get it working again.
Most of the people I've seen reporting reboots had it after they updated to the leaked RUU. if it was happening to me on stock I would complain very loudly to Verizon.
I haven't rooted yet either, and the mysterious reboot happened twice.
Sent from my ADR6400L using XDA App
Happened herw too. I had the problem when i first rooted. The phone would restart in bootloader. Now after I applied new RUU and radio I noticed phone restarted but no bootloader just regular. I am not sure if it is now from me killing some app and the phone doesn't like that.
This is a known problem for some people who have upgraded to the leaked RUU. BAMF 1.5 is a rom that is based off of that leak. Some people have reported random reboots, with & without OC'ing. Only other option right now is to use a rom that doesn't use the new base.
I think it may be the radio and not the OS part of the leak... I am using Perfect Storm 1.3 and updated ONLY the radio because I do not have the time at the moment to reset everything the way I like it... and I am getting the random reboots... 3 so far today... ive been trying to find a way to go back to the old Radio until this is sorted out... anyone know where I can find that?
Whatever is causing it its clear that its not a root issue since its happening to people whove rooted as well as people who havent rooted. As my last post stated, its happened to me 3-4 times this week and i havent rooted.
I do feel its b.s. that the verizon rep is blaming it dirty battery contacts.
I really think it's app related. Mine has rebooted twice. My wife's has done it at least 3 times a week. Although I noticed mine will be close to a dead battery when it does it. The wife's is just random. That's why I am leaning on app. I have since rooted mine on stock. I have not seen a reboot yet. Both times mine did it I was watching a long youtube video. Wife's is just sitting there when it reboots.
Sent from my ADR6400L using XDA Premium App
Run "adb logcat" and try to force the issue....If it is the same as mine, coming out of airplane mode causes the problem:
See the last line before the phone powers down:
D/ResourceType( 1757): calling getConfigurations
D/ResourceType( 1757): called getConfigurations size=230
I/CheckinTask( 1757): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
I/CheckinService( 1757): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
W/ActivityManager( 1560): Permission Denial: broadcasting Intent { act=android.server.checkin.FOTA_C
ANCEL } from com.google.android.gsf (pid=1757, uid=10012) requires android.permission.HTC_FOTA_UPDAT
E due to registered receiver BroadcastFilter{47b299c0 ReceiverList{47b29948 1560 system/1000 local:4
7ad5cf8}}
We never set airplane mode. And I haven't had it happen since I rooted last week. The wife has had it reboot again though. One more time and I am taking to the store and making them swap it. I am beginning to think it is an actual hardware issue of some kind in hers.
Sent from my ADR6400L using XDA Premium App
HTC evo has the same problem, I had mine replaced 4 times for the same problem, is HTC radio isue. HTC sucks.
I was reading this forum bc I am thinking to switch from my evo and Sprint buy I see most of the same problems. So I am going to wait.
Sent from my PC36100 using Tapatalk
marvinmadman said:
Mine is still STOCK. It does reboot every now and then. So I can proudly say that it isn't just because of the rooted/flashed, OCed and whatnot. I wonder what could be causing it? Oh and my stock text messaging app slows to a crawl and pulls the E-brake. I have to reboot to get it working again.
Click to expand...
Click to collapse
That's very interesting to hear yours is rebooting while on STOCK. This whole time, we've been under the impression it was our radios or possibly roms. Have you had any more reboots?
I had 4 reboots within an one hour running the latest radio leak and das bamf 1.5 remix.
I'm running Lightning ROM 3.3.1 with Minimalistic kernel extreme for the past 12 hours and haven't had one reboot.
I have 2 of these at work, both stock.
One reboots 3-4 times a week. The other is perfect- 0 reboots.
I replaced the bad one under warranty. The warranty replacement also reboots 3-4 times a week (they sent me a "new" one with no battery/accessories)
So Yesterday I swapped the batteries between my good Tbolt and my new replacement Tbolt to see if its a battery issue.... still waiting on results, so far no reboots on both
I am starting to think that its a charger issue though.
The good phone is charged once per day (overnight)
The bad ones are charged 2-3 times per day with different chargers (home, car, work). We notice that usually it reboots while its being charged or soon after its disconnected from a charger.
Ok, before I get crucified, I have searched and I haven't found anyone having anywhere close to the same issues as I. My last phone lost 4g after rooting. I couldn't get it back till I restored to stock. Flashed radios, roms, and wiped cache, data, and davik cache. Well, I finally raised enough of a stink to get an NIB thunderbolt. Rooted then had the same issues with 4g going out. So finally I tried something I didn't try before, I reflashed the mr1 upgrade rom from J's root thread. I got 4g back, but now I have issues with it shutting down randomly. It's not a reboot, it's more like a sleep of death. I can only fix it with a battery pull and reboot. I'm not overclocked, and I haven't even used setcpu on the mr1 rom. Is anyone else having these issues? Also, when I first received the phone and used it unrooted for two days until I had time to root it, it was plagued with random reboots every hour or so. I loved my new phone and didn't mind it until I started having major usability issues. I can't deal with a phone that can't stay on all day and I'm not sure what to do at this point. Does anyone have any possible explanations for what I'm experiencing?
I have this issue but I am pretty sure it's hardware related. Sometimes if I put pressure on both ends of the phone and bend it a tiny bit, it will shut off. Might not be the same thing as you but that is what is causing it for me.
1454 said:
Ok, before I get crucified, I have searched and I haven't found anyone having anywhere close to the same issues as I. My last phone lost 4g after rooting. I couldn't get it back till I restored to stock. Flashed radios, roms, and wiped cache, data, and davik cache. Well, I finally raised enough of a stink to get an NIB thunderbolt. Rooted then had the same issues with 4g going out. So finally I tried something I didn't try before, I reflashed the mr1 upgrade rom from J's root thread. I got 4g back, but now I have issues with it shutting down randomly. It's not a reboot, it's more like a sleep of death. I can only fix it with a battery pull and reboot. I'm not overclocked, and I haven't even used setcpu on the mr1 rom. Is anyone else having these issues? Also, when I first received the phone and used it unrooted for two days until I had time to root it, it was plagued with random reboots every hour or so. I loved my new phone and didn't mind it until I started having major usability issues. I can't deal with a phone that can't stay on all day and I'm not sure what to do at this point. Does anyone have any possible explanations for what I'm experiencing?
Click to expand...
Click to collapse
Sleep of death? Haha, yeah, I've got the same issue. Screen refuses to turn back on, but I know the device is still running since my notification light keeps blinking. Only solution is a battery pull. Happened twice today.
I'm running dasBAMF 2.0-5.
Ok, well I guess its good to know that I'm not alone.
Well, I guess if its hardware I will whine a little more to Verizon.
Sent from my ADR6400L using XDA App
1454 said:
Ok, well I guess its good to know that I'm not alone.
Well, I guess if its hardware I will whine a little more to Verizon.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Yep. I too have experienced the sleep of death at least half a dozen times. I experienced it a lot on MRs. at the time I was running Gingeritis beta CO and Imoseyans kernel OC to 1403mhz.
I've been running on MR2 for a week now with Gingeritis final and Imoseyans kernel.... and haven't had one spasm.
Rooting doesn't disable 4G. Did you make sure your original TB radio wasn't set to CDMA auto (prl) in settings/network before returning it?
Sent from my ADR6400L using XDA App
Had the "sleep of death" happen today for the first time. Rooted on candy rom 2.0.3. Happened as soon as I got into a 4g area while driving.
sleep of death aswell here. Not often.
there is a new gb radio out MR2.5 ...running great so far..
Sent from my ADR6400L using XDA Premium App
I am running MR2.5 with The Perfect Storm 1.5 with no reboots or problems!!
TwistedX
I've been getting SOD occasionally as well. Happened once on stock rooted, several times on gingerBAMF, and on BAMF 1.7 as well. Often it has happened while asleep to find phone unwakeable in morning, but still on. The last day or so I've had market downloads seemingly trigger it as well. At least it did it while updating apps....No physical triggers have caused it. It's never frozen in my hand as previous poster mentioned.
I'm scared it's increasing in frequency. Guess I'll see how MR 2.5 works when I get a chance next.
I didn't say that rooting was the cause. Just the series of events. It wasn't until I flashed new roms that I started having issues. I have gone back to mr1 upgrade and gotten 4G back, but now I have the sleep of death issue.
Sent from my ADR6400L using XDA App
I may try this setup and see if I still have issues. Thanks for the feedback.
Sent from my ADR6400L using XDA App
Mine has only frozen while using once. Most of my issues with the sod have been after being in sleep for a while.
Thanks for all the responses, maybe one of the devs can chime in with some advice as to what we need to do to fix it.
Sent from my ADR6400L using XDA App
I did have a simi random reboot issue this morning or o think so. I was making coffee and heard the phone vibrate than screen. Went off and rebooted. I was running gingerits with twisted and imo kernel at 1400/184 smartass extreme. I think that was the issue cause I set it to 1400/240 interactivex and have had no issues and got 16hrs outta of my 1700 batt with heavy usage.
Sent from my ADR6400L using XDA App
+1 sleep of death
^_^_^
It's happened to me twice, once yesterday and once today. I have never had it happen until I flashed MR2.5.
i'm 3 days free of any more SODs after wiping to death and flashing MR 2.5 radio. happy days again. I hope. Probably just the wipe and not restoring any app data at all that made it better.
So i have a rooted tbolt with MR2 radio and ive used gingeritis and the newest shooter leak. Every once in a while the screen just wont turn back on. Unresponsive, ive let it sit nights fine and it turns back on no problem. But when its unresponsive the only solution is to do a battery pull and reboot the phone. It sucks cause theres no telling if the phones just sleep or if its dead lol. Has anyone else had this problem?
For what its worth, i do underclock it to 184mhz but never overclock it. Also the voltage is pretty low at 750 when underclocked. Could this be the reason for the freezes? Any insight would b helpful. Thanks all
Sent from my ADR6400L using XDA Premium App
I would do a full 3x wipe and reload the new GB radio and ROM again. I have had some issues that were odd/sporadic like yours and this seems to be the fix.
thanks ill give that a shot
I had that problem too with MR2 and an older radio also. between wiping everything and doing MR2.5 it got better.
That is called the sleep of death coined by some other member that started a similar thread. I've had that problem on mr2. Haven't had it on mr2.5.
Well it did occur for me again this morning 7 days after wipe/update to mr2.5. Very frustrating. At least it's not happening every day like it was prior to this...
For the pass week I have been experiencing screen freezes / screen lock ups......to the point I have to do a battery pull....I never had this issues before til recently I've tried every rom and it does the same thing after a few days or so I've even ran roms that I've never had any issues with before but i still get lock ups....any ideas!!! I don't wanna take it in cuz I don't want to do the HTC unlocking once they send me a refurb!!
Sent from my PG86100 using Tapatalk
Could it be heat related? Mine is.
I am going for a second refurbished e3d and hitting it with a hairdryer first thing out of the box to see if I can get it to reboot due to moderate heat.
A month ago, refurbished phones were 1.4 hboot.
Can't be heat related I watch movies just to burn my battery dry and nothing goes wrong but idk but it possibly could be heat related
Sent from my PG86100 using Tapatalk
M phone was horribly hot this weekend and was perfectly stable. What the heck?!?
Heat is either a necessary precondition or it is humidity related. Those (and updated apps, as they hit the market) are all that have changed between stability and the previous rebooting abyss.
Maybe random really is random.
Oh, I still can't use the walts kernel that comes with CR 2.5. Something about it hates my phone and causes massive random rebooting.
Freeza's stock kernel is a million times more stable, only leaving me with the more minor rebooting topic we are posting about here.
Try this... http://forum.xda-developers.com/showpost.php?p=18246407&postcount=2861
I'm getting freezes also, anytime my phone screen times out. The phone will lock up and you have to hold power button plus volume up and down to reboot or battery pull.
I just did this fix and testing now, not sure if it fixes it yet...
Sent from my PG86100 using Tapatalk
^^^didn't work for me... Getting the lockups.
Sent from my PG86100 using Tapatalk
Questions - Just trying to help
OP :
Are you using any 3rd party roms - mods - themes- etc.
?
If so, I can tell you , from personal experience, that ViperRom seemed to affect my phone (stock kernel, last version, not the latest) in this way. I was not overclocking, nothing special just the basic rom and it seemed to randomly lock up, and get quite warm. Many, many others however are quite happy with his rom without any issues.
Me personally, I have moved to Virus'es (lol) infected rom, Im loving it, stable, fast, beautiful theme, and it seems like the developer is a little more involved than Viper was.
Just my 2c, Not trying to trash any of the dev's I appreciate all of the hard work hobbyists put into this, once again, just trying to be helpful.
--DT
deathtech said:
OP :
Are you using any 3rd party roms - mods - themes- etc.
?
If so, I can tell you , from personal experience, that ViperRom seemed to affect my phone (stock kernel, last version, not the latest) in this way. I was not overclocking, nothing special just the basic rom and it seemed to randomly lock up, and get quite warm. Many, many others however are quite happy with his rom without any issues.
Me personally, I have moved to Virus'es (lol) infected rom, Im loving it, stable, fast, beautiful theme, and it seems like the developer is a little more involved than Viper was.
Just my 2c, Not trying to trash any of the dev's I appreciate all of the hard work hobbyists put into this, once again, just trying to be helpful.
--DT
Click to expand...
Click to collapse
I'm running virus news rev and I'm getting the lockups...
It happens while I leave phone idle and freezes screen up and requires battery yank or power down and volume button reset.
I just flashed back to virus airbourne and no lockups.
Seems to happen on 2.3.4 roms only.
Sent from my PG86100 using Tapatalk
If you are running any of the roms that change the automatic dimming settings than that may be your problem. For some reason, anytime Steel would add that feature to his rom everyone would start having the lockups and screen freezing. Check to see if your rom has altered these settings and if it has remove that update and you should be fine.
Every single kernel I have tried with the exception of netarchy's silverneedle on 2.3.3 has given me random lockups after about a day of use.
I have since reverted back to the Stock kernel on 2.3.4 and all is well.
Yea i have used vipers newest and even went back to the good ol decks ROM and had lock ups I'm on deck now with no custom kernel so i will do more testing then slowly add things to see what the culprit is
Sent from my PG86100 using Tapatalk
Chauleyboii said:
Yea i have used vipers newest and even went back to the good ol decks ROM and had lock ups I'm on deck now with no custom kernel so i will do more testing then slowly add things to see what the culprit is
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Keep us updated, want to figure these lockups out...
I think its probably more hardware related. I'm stock everything and have had this almost catch fire 3 times now. Not like a little hot, but hot to where I have to put it down. I too have had a bunch of screen freezes lately, only a few force restarts. The high temp thing is random. First was taking video. Second time was uploading a few pics to facebook, third time....this last sunday was a good one. Had it plugged in for about 2.5hrs. My dad grabbed it and threw it down because he didn't expect it to be as hot as it was. I was like WTF? He gave me the phone and it was on fire, with only 25-30 charge. This was using the HTC charging stuff that came with the phone. I keep deleting the battery temp app so i didn't get actual temps at the time. I'm gonna try for a new one tomorrow, hopefully get upgraded to 1.40 from 1.50.
gokart2 said:
I think its probably more hardware related. I'm stock everything and have had this almost catch fire 3 times now. Not like a little hot, but hot to where I have to put it down. I too have had a bunch of screen freezes lately, only a few force restarts. The high temp thing is random. First was taking video. Second time was uploading a few pics to facebook, third time....this last sunday was a good one. Had it plugged in for about 2.5hrs. My dad grabbed it and threw it down because he didn't expect it to be as hot as it was. I was like WTF? He gave me the phone and it was on fire, with only 25-30 charge. This was using the HTC charging stuff that came with the phone. I keep deleting the battery temp app so i didn't get actual temps at the time. I'm gonna try for a new one tomorrow, hopefully get upgraded to 1.40 from 1.50.
Click to expand...
Click to collapse
That's crazy I never had heating issues like that before!! But maybe ill do everything to get my phone working harder to see if I can create that issue
Sent from my PG86100 using Tapatalk
I've only had this happen a few times and was wondering if anyone had this happen to them also. I'm rooted and run custom roms, it doesn't seem to be rom or kernel dependent.
For example, I had my phone on since noon and haven't really used it since then except a few times to check the time. I just pulled my phone out of my pocket and hit the power button... nothing. I held it down and it started to boot up. When this happens the battery is never dead (it was at 68% with the ext. battery this time), it just wants to turn itself off. It seems to happen when the phone is "sleeping", it's never done it when I'm actively using the phone so it's not an overheating issue.
It's not really annoying since it doesn't happen often, it just confuses me.
brando56894 said:
I've only had this happen a few times and was wondering if anyone had this happen to them also. I'm rooted and run custom roms, it doesn't seem to be rom or kernel dependent.
For example, I had my phone on since noon and haven't really used it since then except a few times to check the time. I just pulled my phone out of my pocket and hit the power button... nothing. I held it down and it started to boot up. When this happens the battery is never dead (it was at 68% with the ext. battery this time), it just wants to turn itself off. It seems to happen when the phone is "sleeping", it's never done it when I'm actively using the phone so it's not an overheating issue.
It's not really annoying since it doesn't happen often, it just confuses me.
Click to expand...
Click to collapse
still you might want to check the rom and kernel just in case, either re-flash or change.
if the problem still happens, use your warranty and get a new phone.
what rom, kernel, and recovery are you using?
I actually just happened earlier again. Got a text from a friend that she was here, so I went down and let her in, came back up and went to check my phone a few minutes later and it was off. WTF.
I'm currently using Nils newest business sense with the OC'd ICS kernel and the latest Amon Ra recovery. This used to happen on GB also so it's not a rom/kernel problem IMO.
It happens so sporadically (except for tonight apparently) that it's maybe happened 5 times since I got it on release day.
Maybe I have the governor in cpu master set too low? I have it at the lowest of 384 MHz, I've always wondered this: whats the difference between conservative and powersave?
did it happen while you were on stock GB or on a custom rom and kernel? maybe try relocking and running stock for a while and see what happens?
I honestly don't remember, it's been too long lol. It's not worth it to go back to stock and relock considering I like ICS too much.
brando56894 said:
I actually just happened earlier again.
I'm currently using the OC'd ICS kernel
Click to expand...
Click to collapse
that's the issue right there, run the stock kernel at stock speeds.
How could it be the ICS kernel when it's happened on GB also?
Which OC? I've read that the 1.8 causes random stuff like this, but 1.7 doesn't.
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
3.0.16-g4a9c8a3 SebastianFM #1 is what the kernel info says
The zip name is Overclocked_kernel_v1.20_1836_MHz_by_sebastianFM.zip
Not all phones can handle overclocking.
Mine is stable about 98% of the time, it may actually be the extended battery that is causing the issue.
brando56894 said:
Mine is stable about 98% of the time, it may actually be the extended battery that is causing the issue.
Click to expand...
Click to collapse
9x out of 10 random reboots are from either undervolting too low or overclocking too high.
I went back to the stock kernel since it seemed to be a little choppy with the oc'd kernel. That may have been the problem after all.
Sent from my Transformer TF101 using Tapatalk