The last few days when I wake up in the morning my phone screen won't wake up and when it finally does my phone restarts. I'm trying to find out where the problem might be (Franco kernel, CyanogenMod, random app, etc). Whats the best way to troubleshoot this? Should I turn on logcat before I go to bed so I can see what might be causing the issue?
bump...
Does it do it on other roms?
Revert to stock to troubleshoot that it isn't a hardware problem.
Haven't tried that yet, I was hoping to not have to wipe the phone to restore the stock rom, but looks like I might have to.
Related
The other day I installed the new CM RC2 rom on my HTC Wildfire. Everything went fine for the couple of days until it went into sleep mode and I could not come out of it. I had to pop the battery and when still problems, I re-installed rom - again with flashed kernal 4.1 and up to date gapps.
Managed to get it working. But then same thing again. Overall I had to re-install 5 times yesterday alone!
Out of frustration I tried to re-install my CM RC1 from before with the kernal 4.1. And this was fine again for about an hour, then again, mobile went into sleep mode, and again was left with black screen. Again not able to come out of it.
Am at a loss as to how to get my mobile back up and running. If anybody can help, this would be most appreciated.
Thanks
Does this happen with all ROM's, or simply CM7? Also, what are your overclock values and SetCPU Profiles, if any?
Have only tried cm7 so far. and cpu was not touched. was left at default settings. Am not able now to even boot into recovery. Totally DEAD!
Probably a hardware issue. I doubt CM7 can have such far reaching implications as to make the phone dead. Anyhow, this issue looks uncannily similar to this
Thats worrying.
If I do manage some how to get it switched on, is there anything that you can suggest to stop this happening again?
Also keeping the battery out of the mobile for a 5 mins, SHOULD that help instead of just taking out and imediatley replacing?
Doesnt sound too good. If you manage to switch it on you could try setting your minimum cpu speed to 245mhz+ Although it sounds like you have more serious issues. If its still under warranty I would consider returning it
Thats what I feared.
Thing is, cause it is rooted, it is out of warranty. I dont think I have a leg to stand on.
Its worth a try, they may not even check/notice that its rooted
Well.......
I managed to get it switched on. And decided to try and install Wildpuzzle as I had that on the phone before with no problems. And so all was well......
....untill just now.
Mobile went into sleep mode, and when I pressed the power button to get into it, black screen. Wouldnt come out of sleep mode. So had to pop battery again and after 10 mins, re booted it.
This seems to be the norm now. If it gets a chance to drop off into sleep mode, then I am stuck.
I am starting to pull my hair out.
Have just read on another thread that should try turning off auto rotation and auto brightness.
Fingers crossed this will work.
If the problem occurs throughout various ROMs it could well be hardware related. Flash an RUU (this will get rid of all traces of root) and return it
Will do.
Thanks
cant access cm7 rc2
any ideas why i cannot access or see any file in the website download.cyanogenmod.com regarding cm7 rc2 for buzz/wildfire?
Hi guys,
I really need your help. I have a I9000T on stock gingerbread 2.3.3 :
PDA:I9000TUBJV6
PHONE: I9000TUBJV6
CSC:I9000TUUBJV6
Buld info:May 7 2011
For the last 2 days my phone has been acting weird. I leave it, for some hours without using it, and when I hit the power button, for a split second I see the home screen, but the lock pattern screen is not there then all of sudden the phone just restarts. It did that 3 times in 2 days. When I look at the battery monitoring appl, it says it is missing data. So I am guessing during this time something happens with the phone. Something crashed with the operating system or maybe an app is causing the phone to crash.
Could it be a hardware problem? I don't really want to return the phone and I figure if it is a software problem, then I can deal with it, but it is a hardware problem then I have to return it. I bought the phone on amazon and I have 3 days left for a return, full refund.
If somebody has an idea on what the problem is, or how to reproduce the problem so that I can figure is out, please please help!
reflash the phone with full stock ROM with stock kernal and see if it happens, you can even try a 2.2.1 ROm and see.
I have already a stock ROM and kernel. All my updates have been trhough Kies so far. I was planning on rooting when I started having the problem.
By the way I just did a factory reset, but somehow pictures and songs were still there. How can this happen?
Has anyone been able to find a fix for the sudden screen on issue when you are running a custom ROM? I have found that after updating to a custom ROM after the firmware push from ACER that the sudden screen on issue has returned. I have searched but with no luck. I was just wondering if there has been any new developments on this issue from the DEV's?
It would be nice to not have my tab die after 12 hours of standby because my screen keeps turning on.
Any help?
I have been monitoring Cat Logs with this issue both with WIFI and without WIFI on so if anyone wants those I can save and send them over.
This happens on my OTA ROM as well. I think it is just an issue with the device, or at least something non rom specific.
Hey guys, I got my Nexus 4 about 2 weeks ago. Love the device, and haven't had any problems until recently. I set alarms to wake myself up in the morning. When it comes time for the alarm to go off, the device fails to ring, and when I attempt to turn it on, it fails to work. I have to hard reset it in order for it to turn back on. Do keep in mind, that I use multiple alarms, so the device's screen is always off when this happens. I also have installed JuiceDefender, and I think that might be a possible cause for this crash (I will have to do some trials). I did a search on the forums, and haven't quite found anything specifically related to this, just yet. I've read some things about wake locks, but I don't really know much about them.
Is anybody else experience this issue? I am on 4.2.1 stock everything. I have JuiceDefender Ultimate, and I believe it may be a source for the issue. But I will have to test further. Any ideas?
Thanks, in advance!
6P - Rooted, Stock, Xposed w/Amplify, Greenify, & Gravity Box.
Android v. 6.0.1 w/ 8/5/16 Security Patch.
Build number MTC20F.
Kernel version 3.10.7.-g909746b.
I'm getting 2 or 3 Sleep of Death (SOD) occurrences a day. Fingerprint scanner, nor power button press wakes it. I have to do a hard reset to turn it back on. I did a factory wipe about two weeks ago when it was getting to be that every time it slept it wouldn't wake up and it was better for a short while, but it's popping up again.
My research has shown that apps can cause it, but I have no way of narrowing down what's causing it at all. It's getting super frustrating at this point.
So my questions are:
1) Is there a way to figure out what's causing the SOD? I can't seem to find a pattern or figure out what's triggering it, so it's not like I can turn a logger on to figure it out before it happens.
2) Once I figure it out, what can I do about it? Or is there something I can do to prevent it without figuring out what directly is causing it?
Hopefully there's a solution that's obvious that I'm missing here. I'd rather not go through the factory reset process again, as it happened again after I reset the last time.
Help is sorely needed.
I use gravity box but not greenify. I use Recently instead of greenify with no problems. Not sure what Amplify is but I use the XML hack to raise headphone volume. Hope this helps.
RRuszczyk said:
6P - Rooted, Stock, Xposed w/Amplify, Greenify, & Gravity Box.
Android v. 6.0.1 w/ 8/5/16 Security Patch.
Build number MTC20F.
Kernel version 3.10.7.-g909746b.
I'm getting 2 or 3 Sleep of Death (SOD) occurrences a day. Fingerprint scanner, nor power button press wakes it. I have to do a hard reset to turn it back on. I did a factory wipe about two weeks ago when it was getting to be that every time it slept it wouldn't wake up and it was better for a short while, but it's popping up again.
My research has shown that apps can cause it, but I have no way of narrowing down what's causing it at all. It's getting super frustrating at this point.
So my questions are:
1) Is there a way to figure out what's causing the SOD? I can't seem to find a pattern or figure out what's triggering it, so it's not like I can turn a logger on to figure it out before it happens.
2) Once I figure it out, what can I do about it? Or is there something I can do to prevent it without figuring out what directly is causing it?
Hopefully there's a solution that's obvious that I'm missing here. I'd rather not go through the factory reset process again, as it happened again after I reset the last time.
Help is sorely needed.
Click to expand...
Click to collapse
I think the best way to diagnose and pinpoint the issue would be by obtaining logs. Haven't used xposed in a while though I think it has a log mechanism you can refer to. If you check the logs for keywords such as "error", "reboot", or "restart, etc. that may narrow down the processes causing the issue.
blitzkriegger said:
I think the best way to diagnose and pinpoint the issue would be by obtaining logs. Haven't used xposed in a while though I think it has a log mechanism you can refer to. If you check the logs for keywords such as "error", "reboot", or "restart, etc. that may narrow down the processes causing the issue.
Click to expand...
Click to collapse
Just checked. The logs are automatically cleared when the phone reboots or resets, so no way I can tell to get the logs before the SOD occurs.
RRuszczyk said:
Just checked. The logs are automatically cleared when the phone reboots or resets, so no way I can tell to get the logs before the SOD occurs.
Click to expand...
Click to collapse
Then try to capture a system-wide log instead. This article may help. Do the logcat after you have experienced the bug. I'm sure it will point out what's causing the issue.
Other than taking the logcat approach you can try eliminating possible culprits. If you suspect it may either be amplify or gb then temporarily disable each module within xposed then observe if the problem persists.