-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Help Post-update BSOD
- Thread starter UncleMike
- Start date
Since you did the reset the hard way I wondered if you had a chance to look at ... BSOD (Black Screen of Death) ... for possible solutions.
Bad SIM card? Bad battery? Bad App? Bad device?
... Thom
Was your battery calibrated properly? Try recalibrating it.
It had been fine until today. But after thinking about it, I think I remember having battery level issues following previous BSOD. I'll keep an eye on it, but I think this BSOD and the other one mentioned were somehow tied to a rogue process with high CPU utilization and/or keeping the device awake (yet somehow unresponsive).
Some people having BSODs have isolated it towards a program. One of them being SetCPU. Some have said that once removing it they stopped having BSODs. Might need to find that rogue app.
zoxxo
Android Enthusiast
Any suggestions for finding the rogue app? I just had my first post-update BSOD a couple hours ago...
johnlgalt
Antidisestablishmentarian
Yes, but you're not going to like what I have to say.
Factory Reset. Run for 12 hours / one full battery charge. Add one of your apps. Run for full battery charge.
Wash. Rinse. Repeat.
That will be the only way to know. ANd even then, you cannot be really sure, because it may not be a single app, but a few apps acting in concert with each other.
If you are running a task manager of any kind to autokill your app, STOP!!! and see if that helps before doing what I outlined above.
Factory Reset. Run for 12 hours / one full battery charge. Add one of your apps. Run for full battery charge.
Wash. Rinse. Repeat.
That will be the only way to know. ANd even then, you cannot be really sure, because it may not be a single app, but a few apps acting in concert with each other.
If you are running a task manager of any kind to autokill your app, STOP!!! and see if that helps before doing what I outlined above.
Since launch day I've had at most 10 BSODs. They don't occur frequently enough for this troubleshooting method the be effective.
One thing I've considered is buying the paid version of System Panel, and setting it up to log running apps, CPU and RAM usage. Checking the logs after a BSOD might reveal the culprit, or at least narrow things down a bit.
The only SetCPU I know of requires root-ing.
Is everyone in this thread talking about root-ed devices after applying the 5.5.893 OTA?
Root-ing doesn't by itself cause problems ... instead it raised the barrier that allowing potential dumb mistakes and malicious attacks to get through.
The un-root-ed solutions to do what John suggested. After proving that a reset doesn't help ... you don't have much to loose ... do a factory reset and the slowly add applications back and hopefully you will get a failure and can zero in on it.
To prove that the foundation is correct ... run un-rooted slowly installing your Apps over days and if that works out ... root and VERY slowly add privileged Apps (if you know them).
... Thom
johnlgalt
Antidisestablishmentarian
0. As in 0 instances of BSODs.
And I've never turned off in pocket detection either.
Since launch day I have had one instance where I was forced to do a reset before the screen would respond. This was during the two week period when the network was going up and down frequently.
I never turned off pocket detection either.
I do not have a screen protector or external case. I was always concerned by the statement in on page 4 of the Users Guide ...
"Don't use covers or screen protectors (even clear ones) that cover this sensor."
... Thom
Yes ... it is that ubiquities phrase for a number of problems that can cause the screen to go unresponsive and require a reset. You can do a reset by holding down the volume up/volume down/power keys until the screen menu appears and then disappears.
(BTW … BSOD was stolen from DOS\Windows … it was Blue Screen of Death that came up when there was a “hard” error like an un-handled interrupt or a faulty driver … or someone in Supervisor State/Protect Key Zero nailing some other application by mistake. We even had to steal the overused abbreviation?)
... Thom
(BTW … BSOD was stolen from DOS\Windows … it was Blue Screen of Death that came up when there was a “hard” error like an un-handled interrupt or a faulty driver … or someone in Supervisor State/Protect Key Zero nailing some other application by mistake. We even had to steal the overused abbreviation?)
... Thom
I am not implying that everyone is rooted. However I was giving an example of a program that I have read causing problems with some users. I know that SetCPU is for rooted phones but I could not think of any app not needing root that causes the phones to hang.
In my experience between the OG Droid and Bionic were apps needing root that caused my hangs and/or glitches in my phone. My selections of apps defer from everyone else so its really hard to determine what may or may not cause our phones to hang.
And yes BSOD was at term used on PCs. I've gotten used to it cause everyone else uses the term.
So maybe we can talk specifics instead of generalities?
... Thom
... Thom
I am not rooted... and neither is my Bionic. 
Re: the BSOD acronym... I've seen it used elsewhere before, and it does fit. When the screen won't respond and you have no notification lights flashing, it's difficult to tell what state the phone is in. Did it somehow shutdown and won't turn on? Did the battery go dead? Is it on and just not responding? Removing and re-installing the battery can identify or eliminate a dead battery as the culprit, but beyond that it's difficult to know what happened. A "catch all" phrase that everyone can identify and search for is better than 10 different wordy descriptions of the same or similar problems which make it difficult to find relevant information.
Re: the BSOD acronym... I've seen it used elsewhere before, and it does fit. When the screen won't respond and you have no notification lights flashing, it's difficult to tell what state the phone is in. Did it somehow shutdown and won't turn on? Did the battery go dead? Is it on and just not responding? Removing and re-installing the battery can identify or eliminate a dead battery as the culprit, but beyond that it's difficult to know what happened. A "catch all" phrase that everyone can identify and search for is better than 10 different wordy descriptions of the same or similar problems which make it difficult to find relevant information.
I am not rooted... and neither is my Bionic.
A "catch all" phrase that everyone can identify and search for is better than 10 different wordy descriptions of the same or similar problems which make it difficult to find relevant information.
Just trying to help out. I think it could be broken up and it would help a lot of people understand.
If you have had 10 since September 8 ... what was the frequency?
Now many apps did you install?
OEM charger and cable?
What was it doing the last time it failed?
Turned on? yes
Battery charged?
Bad charger?
Bad connecting cable?
Bad Battery?
Bad SIM?
Bad App?
App conflict?
Are all your apps from the Market?
If not start looking at the non-Market apps first
Factory reset ... wow that would hurt ...or would it?
Slowly install Apps until it failed (dependent on failure frequency to date).
And ... yes I did notice ... it seems remarkably similar to what John said ...
Good luck.
... Thom