The last couple of weeks I have been having problems with the phone randomly shutting off and power cycling. I had been using CM6 for a long time with no apparent problem till this started happening. So I unrooted and flashed back to stock and dl'ed current updates OTA...To no avail it was still happening....I brought it into Sprint and the tech determined that it is a safety feature cause the phone was overheating...And that it is a known issue that has to do with the last current update... I also use the silicone case so I know that is keeping it warmer than normal. I usually have these random resets when using apps for along time...They said HTC knows about it and trying to come up with a different update to fix it. I had asked the tech about rooting which he said corporate frowns on but would be nice to have it unrooted when you bring it in...I am just curious if anyone else is having this problem...The tech also suggested to flash a different kernel and that should take care it or wait for the OTA. Anyone have a suggestion for a good kernel?...And now i have to root again dammit...ughh..
Is there any way at all to disable the Fascinate from ever loading into safe mode again? It's really annoying when it happens because I have to reset all my widgets.
I've flashed my phone several times and it happens with every rom that I've had on it so is it part of the baseband kernel?
Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.
johnnyplaid said:
Get rid of the conflict that puts you in safemode. Safemode has to be better than your phone bricking.
Click to expand...
Click to collapse
X2
List off the steps you used when flashing these last few roms (and what rom specifically) that you say are making you boot into safe mode...I've only seen it once on my phone and 1 reboot fixed it and I never seen it again, but that was months ago and I just chalked it up to me missing a step?! I have flashed many roms since and never see safe mode again.
Sent from my SCH-I500 using XDA App
Im starting to think that it's more a problem with my Fascinate than anything else. It usually happens when I have to pull the battery due to it locking up. Sometimes pulling the battery out a second time still doesn't get me out of safe mode and I have to continuously do it until it does.
For the past few months I've been using CM7 and updating with nightlies. On Monday I updated to the stable GLITCH kernel and so far it seems to be running much better. It's always had a problem with randomly bringing up my keyboard and backing out of apps and I have not had that problem yet since putting the GLITCH kernel on it.
Figured I'd also note in here that the GLITCH kernel is not currently working with the newest Cyanogen nightlies. It bootloops and I found that out the hard way.
For now im running GLITCH v11.1ML and CM7 Nightly 35 and it's been great so far.
so glad I havent run into safe mode
I have two Nexus 4 phones and both are 100 % stock but have unlocked bootloader. Both at random get the black screen of death and I have to reboot by holding both volume buttons and power. Is this a known bug with stock?
Are you on lollipop? From what I can gather, this is a known issue among some of the lollipop users.
lolcakes203 said:
Are you on lollipop? From what I can gather, this is a known issue among some of the lollipop users.
Click to expand...
Click to collapse
Yes stock 5.0.1 thank you I was afraid it was a hardware issue
Same happened to me twice already
Zehlek said:
Yes stock 5.0.1 thank you I was afraid it was a hardware issue
Click to expand...
Click to collapse
did you got OTA or flashed factory image
If you got it through OTA then do a factory reset..it is even recommended by Google..
Factory reset will NOT wipe your rom back to kitkat.
I flashed factory images
Yeah, Google should be coming out with a fix soon, until then I'm afraid the only options are to roll back to KitKat or live with it. Perhaps try experimenting with a custom kernel designed for AOSP like Franco or matr1x?
My advice is flash a good custom ROM & kernel, then wait for the 5.1 update
There is a list of known bug with 5.0.2, 5.0.1 and 5.0.0 ?
You should flash CM12, no black screen of death here, i had it on Stock Lollipop like you
Mashed_Potatoes said:
You should flash CM12, no black screen of death here, i had it on Stock Lollipop like you
Click to expand...
Click to collapse
Flashing now
https://code.google.com/p/android/issues/detail?id=79942
This is the issue that is raised in the issue tracker. I have this problem, the only way to stop it from dying is to keep a constant wake lock on the device which drains battery. I might have to try a custom ROM over the weekend to see.
---------- Post added at 05:57 PM ---------- Previous post was at 05:57 PM ----------
https://code.google.com/p/android/issues/detail?id=79942
This is the issue that is raised in the issue tracker. I have this problem, the only way to stop it from dying is to keep a constant wake lock on the device which drains battery. I might have to try a custom ROM over the weekend to see.
Same problem on mine. Sleep of death at random, especially when charging the device. Also, rebooting while doing onerous tasks (such as time lapse recording or GPS navigation).
v5.1.1 seems to have reduced the chances for these problems to occur, but I still happen into them. And if you set a wake up alarm on the phone and it goes into sleep of death during the night, it is not pleasant at all.
I've sent the Nexus 4 to LG tech support because of the power button that is not working correctly, and mentioned the other two problems, even if I don't think LG can do anything on issues that seem to be software related.
Thank you, Lord! I though it was just me. The bug can be reproduced if you try to upload a video in Facebook Messenger app. The black screen is 100% guaranteed.
Mavasilisk said:
Thank you, Lord! I though it was just me. The bug can be reproduced if you try to upload a video in Facebook Messenger app. The black screen is 100% guaranteed.
Click to expand...
Click to collapse
I've just done that a hour ago, that didn't happen.
BTW in the meanwhile since my last reply I've sent my Nexus 4 to customer service two times, the second time was because LG Italia didn't fix the button issue, while they replaced mainboard and battery. During that week before sending the smartphone back to CS for the second time, I've never experienced a SOD (updated via OTA from 4.3 to 5.1.1, being under Lollipop for the whole week).
I've had it back two days ago, chart saying battery and mainboard have been replaced again, button has (finally been fixed) and... ta-dan! Another SOD yesterday, after 24 hours of activity (after a while afternoon of OTA updates from 4.3, again.
I'm glad to see that in the meantime the Issue 79942 has been moved to requesting more info first and assigned then. But that Priority-small makes my nose writhe...
I'm wondering if one can fix it by flashing a different kernel. I can't read of people suffering from SOD on, say, CM 12.1, so it's likely that a different ROM won't have this issue, who knows about only switching kernel.
I had stock SOD for a while, keeping a wake lock active stopped it but did eat through battery. Flashing hells-Core kernel (leaving the rest stock) fixed the issue for me, no wake lock needed.
I am currently using hC-b83-L with no issues, and no SOD.
You can pick it up here if you are interested:
https://drive.google.com/folderview...sharing&tid=0B77BTW0zStYCSTRIYWpZQS1nOWs#list
I've had this happen a few times. Also I've had a few reboots while listening to music using Google play music.
I've been using LMY48I for a long time now and just dirty flashed the system.img of LMY48T 2 days ago. Will have to see if this has solved it.
What bugs me alot more is how the Google camera still does not work...
Sent from my Nexus 4 using XDA Free mobile app
It's been a couple of days since I've removed all of the widgets from the desktop and no SOD since then. Will post updates about this and then try to re-insert widget one by one.
Someone else ever tried this yet?
I recently rooted and unlocked the bootloader on my Razr M and installed a nightly build of CyanogenMod (I like to live on the edge, I guess.) The first week or so with it was going great, no issues as far as I could tell.
Then I installed a social application that requires GPS location. I noticed that the first time after enabling this the phone would freeze when plugged in to charge. It would freeze to the point where hitting the wake up button wouldn't even activate the screen. Not always, but it has happened on several occasions. So now whenever I charge it (daily), I have to force reboot (hold down Up, Down, Power in that order.) Sometimes it'll even go through the process of "Optimizing Apps" as if they were all just installed.
Firstly, has anyone else experienced this? And if so, is there an "easy" workaround? I can't quite pinpoint how to reproduce the bug, though I've got 3 different Cleaning applications installed that are used daily. That in mind, it's unlikely this is a memory leak bug.
Second, if there's no "easy" workaround, when can one expect the next Stable build of CyanogenMod, if ever? Is it still in development? I see that the last Stable release for this phone was in 2013. It seems like I'll have to downgrade to an earlier build, but just want some input before I do it.
Thanks much in advance
Sounds like an issue with the app, not the ROM. You said yourself that the issues started AFTER installing that app. So, delete that app and report back. Also, a lot of those cleaner apps out there will just bork your phone if you're not careful.
Sent from my Nexus 5
Hi all,
Sorry if this has been answered already.
I am currently running no limits on my 6t with the smurf kernel. Everything is running okay but every now and then, i'll try to unlock my phone by switching on the screen and there will just be a black screen.
I have to hold the power button and vol+ key for awhile and it will restart. It has done this 4-5 times this week.
It has not crashed whilst I am using the phone. Only when the phone's screen has been switched off or when its on charge during the night.
I am running 9.0.12 with no limits 5.1
Has anyone else come across something similar or knows what to do to fix this issue?
Any help is appreciated.
Thanks.
This is a mod issue (if I see right, you are on the magisk mod with 9.0.12 OOS, not on no limits ROM), not a phone issue, find the mod's topic and ask there. We all know these risks when we root and use any mods or custom ROMs.
Possible solution: uninstall that mod and check again.
Anyway you are killing your phone with charging overnight, it needs one and a half hour from 0 to 100% battery.
I don't run No Limits, but I did have Smurf kernel for a short while. I would have random device lock ups and it would only happen while on that kernel. Happened to me about three times before I decided to give up and go back to RenderZenith. Ever since switching back to RZ, I've had zero freezes or lock ups.
I'm not trying to bash the kernel, just sharing my experience with it in terms of the issues I had, since they seem to be similar to yours. The kernel otherwise was a beast. Extremely fast and snappy but I couldn't handle those occasional freezes.
Try removing No Limits as the user suggested before me, but the main point of my post is to try reverting to stock or another kernel as well.
Should probably do one thing at a time though, to help determine which was causing the issue.