Related
Weird problem, had my Evo for a couple of days now and everything seemed fine for the first day but now when I run certain apps like google maps for pandora my Evo will reboot. This doesn't happen all the time but will eventually happen after an hour or two of usage. I did buy a case for my phone, maybe it's a heat issue?
taziz23 said:
Weird problem, had my Evo for a couple of days now and everything seemed fine for the first day but now when I run certain apps like google maps for pandora my Evo will reboot. This doesn't happen all the time but will eventually happen after an hour or two of usage. I did buy a case for my phone, maybe it's a heat issue?
Click to expand...
Click to collapse
I've had this happen on my hero. It is just clearing memory are you using autokiller ? It started on my hero when using autokiller. It's not a heat issue the led will flash red and green when the phone is hot.
I'm using advanced task killer but I don't think it's set to autokill apps. A hard reset has seemed to fix this issue for now, how do I ensure it doesn't happen again in the future?
It might help to check your preset in autokiller and set to moderate or optimum but some apps use more memory than others so you might see it from time to time. I still use autokiller set on extreme and would only see that once every week or two on the hero. So it's not that big of a deal. You could just uninstall it if it bugs you or to see if it stops. I have not seen it on my evo yet but I am just rooted no custom ROM yet (Waiting for fresh ROM with espresso theme). That might help contribute to it as well.
taziz23, I don't mean to hi-jack your thread but I've been chasing down the cause of random reboots also. I've been searching around for someone with a similar issue and all I've been finding are people talking about the reboot loop caused by an exchange account. I'm not using exchange at the moment so I know that's not what's affecting me.
It sounds similar to what you're talking about. About 30 minutes to an hour apart regardless of whether I'm using the phone or not. It just did it while sitting on the desk next to me with the screen off for at least 15 minutes.
I've hard reset a few times to see if it was related to the OTA, and turns out it happens to both .1 and .6
I've found out that if I don't associate my google account during the initial setup (or any other accounts like facebook, twitter, etc.) it doesn't seem to reboot anymore. Once I do setup an account and set it to auto sync, I start seeing the reboots happening. So I've been playing with different combinations of disabling calendar sync, contacts sync, etc. to narrow it down but so far, I've come up with nothing.
I've even exported my contacts to a .cvs file using my desktop browser and cleaning out any of the <HTCDATA> stuff that links facebook and twitter to make sure nothing is corrupt and reimported them, but as the reboots are still happening, it looks like that might rule out contact corruption.
I had made it through most of Friday before the reboots started. I recall installing the update to Facebook and TasKiller just before it started happening, but have hard reset since then and have not installed either of these again.
Has anyone else seen anything like this?
Two words: Kernel Panic.
Actually, that's just a guess. I'd imagine anything else would cause some kind of error message to show up like a force close for example.
It has happened with my Evo a few times so far. It also happened with my Hero when I use to use that.
It's probably just a module misbehaving which confuses the OS and causes the kernel panic, so I imagine it's nothing more than a software bug.
Yea... I was thinking some KP's might be happening, but if the release build is dated in April, I must have some fluky hardware right?
Maybe I'll run an `adb logcat` and just wait.
I remember the hard crashes on some of the early donut and eclair builds for the Vogue (CDMA Touch) and these are pretty much the same deal. Just drops out and goes straight to the bootsplash.
Regardless of the phone or OS, I've seen this happen on all the phones I've owned. Android is at least open to allow normal people to debug and fix these problems though.
Me too!
I had a seemingly random reboot happen today on my EVO as well... then it happened again.
Both times, I had Waze and Pandora running and was about 30 seconds into a phone call.
Advanced Task Killer is installed, and is set to kill "when screen off".
I'm pretty new to Android based phones, so I'm not even sure where to start with troubleshooting... but found this thread, and thought this info may help.
Krissy
(P.S. I love this phone so much, right now - I don't even care that it has rebooted on me twice in the middle of a phone call... but eventually the honeymoon will be over, and I'll want this figured out. LOL)
I am having an exact same ISSUE i got it from google I/O its just happened suddenly while you are using it I have no Idea .. Search is also not that great .. Platform need lot of work until it get mature .... I was definately enjoying 1st 2 weeks but not anymore its just killing me now ... Issues after Issues so many Bugs I have start noticing now.. I am not complanning but its just not solid they need to fix this asap... I was enjoying Pre it was slow but I like that OS .. not too much buggy... some apps just Crash randomly .. I was huh .. and its doing more and more now ..
After my hard reset a couple of days ago I haven't had any reboots. I do think it was related to the task killer I think it might have caused some data corruption possibly when killing an application. I set the auto killer to safe in the meantime. If it stats happening again I'll try uninstalling the task killer before I hard reset.
I had the same thing happen, but only once. I was using google maps I think. I also have advance task killer installed. Does the ignore list in advance task killer and setting it to auto kill, kill everything except for what's in the ignore list?
I'm not sure but I did notice that most of my reboots were happening when running google maps..
My Evo rebooted most days 4 or 5 times, day or night, in use or not. The store where I purchased it refused to replace it since I couldn't duplicate the problem to the local technical store. They acted like I needed someone to talk to and not like I had a problem needing resolution. After about 20 calls to customer support they told me to return it where I purchased it and they're sending me out a new one. Apparently no one at Sprint has ever heard that there's this issue. Mine was stock. Period.
I have had some reboot issues that I can't explain. I removed Advance Task killer and it seems to happen less frequent. Maybe once every two days, but never during a call. Waiting to see if this stops with Froyo.
Used to have similar, but less frequent, reboot issues and an occasional "frozen" screen with my previous Blackberry 8830.
I've only had it reboot once or maybe twice for no reason but When I use advanced task kill I almost expect it to happen. And I only use it to kill whatever app I was just using and any other ones Ive downloaded that have no business running.
I have had the same issue, only I am using the full version of Memory Booster..I am going to uninstall it and see if that helps, I also notice that my phone was very hot. It rebooted about 3 times before letting me use the phone again.
Any other suggestions?
Sent from my PC36100 using XDA App
Have a VERY weird issue going on. I've been using Burnt Droid 1.4.2 by Netarchy since it came out. I decided to flash his new 4.3.4 CFS-NoHavs,noSBC, with static undervolt (i wanted to try and see if it was stable since I had success using undervolted kernels last year). I used proper procedure and cleared cache/dalvik-cache before flash. I downloaded the new Angry Birds from amazon and started playing it for a few minutes phone started lagging very bad, then had to restart. I said forget this; undervolt is probably causing this, and reverted back to the original 4.3.1-cfs-nohavs-nosbc which I never had a problem with(used proper procedure above to flash back kernel as well).
Now a day later at night, I decide to run my phone down because I'm trying to recalibrate my battery(I'm at less than 10% at this point). So I load up Wifi, turn on Pandora, and browse the internet. Not even 5 minutes into it, here's whats occuring in order:
1) Bad lag.. Pandora starts stuttering, so I hit the home button
2) HTC Sense restarts, It doesn't even force close, or at least it's not telling me
3) a Hot restart occurs a few moments later... (no white boot screen, just starts bootin from ROM screen)
4) At this point, sometimes its still laggy, sometimes it's fine. If it's laggy I must do a battery pull because It will keep looping to this point.
I can rinse and repeat this running pandora + browsing the web, and the same 4 steps above will happen within moments of eachother. I've been using this ROM since January with no major problems like this
A few side notes:
-I have Evo hardware 0002 (launch day evo)
-Rooted with Toast's original root method, eng .76 boot loader
-Newest radio/PRI/NV/Wimax
-My phone does not randomly reboot on me normally. Reboots only occur when following the above steps.
-I do not use Set CPU
Here is where I am very superstitious. I've been closely monitoring the "Boot looping + no Recovery Access" forum, and similar forums to this. Within the past few months I have tried out a few different CM7 nightlies. I have never flashed RC2 but I have flashed some after and before and tried those out for a while. I just hope my phone isn't starting a dying phase in relation to the problems people are having now.
Is there anything else recommended before I end up doing a full wipe and reflash the rom?
bigblueshock said:
Have a VERY weird issue going on. I've been using Burnt Droid 1.4.2 by Netarchy since it came out. I decided to flash his new 4.3.4 CFS-NoHavs,noSBC, with static undervolt (i wanted to try and see if it was stable since I had success using undervolted kernels last year). I used proper procedure and cleared cache/dalvik-cache before flash. I downloaded the new Angry Birds from amazon and started playing it for a few minutes phone started lagging very bad, then had to restart. I said forget this; undervolt is probably causing this, and reverted back to the original 4.3.1-cfs-nohavs-nosbc which I never had a problem with(used proper procedure above to flash back kernel as well).
Now a day later at night, I decide to run my phone down because I'm trying to recalibrate my battery(I'm at less than 10% at this point). So I load up Wifi, turn on Pandora, and browse the internet. Not even 5 minutes into it, here's whats occuring in order:
1) Bad lag.. Pandora starts stuttering, so I hit the home button
2) HTC Sense restarts, It doesn't even force close, or at least it's not telling me
3) a Hot restart occurs a few moments later... (no white boot screen, just starts bootin from ROM screen)
4) At this point, sometimes its still laggy, sometimes it's fine. If it's laggy I must do a battery pull because It will keep looping to this point.
I can rinse and repeat this running pandora + browsing the web, and the same 4 steps above will happen within moments of eachother. I've been using this ROM since January with no major problems like this
A few side notes:
-I have Evo hardware 0002 (launch day evo)
-Rooted with Toast's original root method, eng .76 boot loader
-Newest radio/PRI/NV/Wimax
-My phone does not randomly reboot on me normally. Reboots only occur when following the above steps.
-I do not use Set CPU
Here is where I am very superstitious. I've been closely monitoring the "Boot looping + no Recovery Access" forum, and similar forums to this. Within the past few months I have tried out a few different CM7 nightlies. I have never flashed RC2 but I have flashed some after and before and tried those out for a while. I just hope my phone isn't starting a dying phase in relation to the problems people are having now.
Is there anything else recommended before I end up doing a full wipe and reflash the rom?
Click to expand...
Click to collapse
I'm not really sure what's causing your problem, and If i was in your situation, I'd most likely do a complete wipe, including calkulin's format all, and either restore a good nandroid, or reflash the rom from scratch.
That said, I don't believe CM to be 'dangerous' to run or anything like that. Yes, it is odd that an increasing number of people are reporting somewhat major issues, with boot looping the splash screen, and being permanently stuck there. However, that doesn't mean CM is the cause. It does seem to be a common denominator in the people that this has happened to, but there are soooo many other variables that come into play with something like this. There is no proof that CM caused it, but it does seem odd that everyone it happened to was running CM. Also, I'm sure there are thousands of CM users, and a select 8-10 people have reported these issues on here. That's a very low percentage, overall. With all that said, I myself won't be running CM in the near future, either until it's confirmed or denied that it has anything to do with these issues. I'll just be playing it safe, just in case.
I'm stock everything, no root or mods and it restarts at the 4g screen skips everything else...
Sent from my PC36100 using XDA Premium App
I think I will do the format all and completetly wipe it and reflash the rom from scratch. Thank you!
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Saturn2K said:
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Click to expand...
Click to collapse
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
bootny said:
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Click to expand...
Click to collapse
Next time it happens I will, I'm just afraid it will break Facebook/SMS integration like I've had happen before.
It's just so weird since it breaks everything. The lockscreen, the options, Pandora's station list, the browser, and it goes on and on. It's like there's some sort of display mode that gets screwed up.
dom085 said:
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
Click to expand...
Click to collapse
What version are you using. I'm going to try to install nightly 77 today after a fresh wipe.
I was seeing the same thing. Now I'm trying to figure out why my data speeds are so painfully slow on CM7 so I can't offer a fix. Flashing back to Warm to troubleshoot 3G.
I get these issues all the time no matter what kernel or nightly I'm running. It has forced me back to sense roms lol
Same problem here. I updated stable mod from stable mod. Reinstalled. Going on 4 days, no issues so far.
Sent from my PC36100 using XDA App
I have the same exact issue. This never happens on a sense rom. I did some tweaks to my system over the past week and I haven't had to reboot since this past Saturday or Sunday. I thought I had fixed it!
Then...
My phone started doing it this morning after I turned on 4G at work, literally as I was writing this post it started doing it. I then turned off 4G.. and it instantly went away. Turning back on 4G and it isnt doing it right now. Now my phone is doing something weird with go sms pro... when I get a text and I respond via the pop up message.. once my text moves to a second line I dont see what I am typing anymore... and now it has progressed to where the pop up box isnt refreshing after I send a message (this is all happening while I am typing this post). Now the phone has become laggy and somewhat unstable... rebooted! All is well. So I went roughly 4-5 days without a reboot... where as before I had to reboot at least once a day.
Thats about the best I can get with these settings:
CM7 7.0.3.1
Savaged Zen 2.6.38.5 CFS > Using SavagedZen Governor, min 384 max 998
Displaying some animations (read somewhere that is a "fix".. or helping extend the time it takes for the Black screen of death to appear).
This is after several full wipes, several when I was running Amon RA recovery 1.8 then updated to the latest and did it two more times. After upgrading Amon and wiping I did not use any backups and started completely from scratch.
So I am not sure what else to do. Some people are getting this, some are not.
Hey,
I know theres a lot of threads about htc/android phones freezing and crashing/rebooting but none of them really described my exact situation. And since it's getting worse and worse and driving me crazy, I wanted to ask for help.
As the title suggests my HTC Desire keeps freezing and crashing (sometimes rebooting, too).
It all probably started shortly before I first rooted my device, following the great sticky noob-tutorial. First problem was, that sometimes my phone wouldn't wake up from standby, especially after I a missed call (rooting didn't solve that problem).
Some time later, now rooted and with a custom ROM, I noticed, that sometimes when I wanted to use my phone, it showed the PIN-screen, which obviously means, that it rebooted quietly (don't remember if this also happened before rooting).
A few days ago it started to completely freeze, when connected to the charger. Orange LED showed it was charging but no reaction to pressing any buttons or disconnect the charger.
Since yesterday it also crashes randomly in standby mode (can't wake it up) or e.g. when watching a video (just freezes the device, no reaction to button-pressing, screen stays on etc.)
now I am running the stability test with the charger connected - no problem for 1h10min til now...
The ROM I am running is the latest cool sense (problems also existed before the latest update)
No modification of CPU (I used to use SetCPU but since I thought that would cause the problems I uninstalled it -> no improvement)
What could be the problem here? (And how can I solve it, of course?)
Anything else than a full wipe, which could help? (that would be my last option...)
Thanks for helping...
it just happened again -.-
I was just backing up some apps with titanium backup and in the middle of scrolling through the list - freeze!
dunno what to do...
is this hardware or software related?...
Hello.
It would be pretty easy if it is a soft problem. This kind of problems are usually dealt with by installing another ROM and see if the problems persist. So if you want to try and eliminate the last option, go and install another ROM, it can be a Stock ROOT-ed ROM, Sense or anything.
The fact that you mentioned your phone was crashing even before rooting got me thinking it is a motherboard fault. I've read some threads in which people had the same problems, and in the end they all got to the same conclusion: motherboard fault. The only resolve with this is to get it to guarantee.
So first of all try installing another ROM and if the problems persist, you will need to install a RUU and see if this one eliminates your problem. If not then I don't know if there is anything else you could do, besides getting it to the guarantee.
I wait for your progress.
Hi,
thanks for your reply.
The funny thing is, that I didnt have those problems with this ROM in the beginning. Everything was fine, that's why I was using it the whole time. But as I said before, it became worse by and by... thats why I thought it could be an app or so...
that would be a recent list of apps: appbrain.com/user/marioiram/
Cannot even sync my newest list, because after freezing while watching a video, it froze again shortly after reboot... still getting worse
Try reinstalling the ROM or installing another ROM.
hm.. just when I was thinking about following your advice, my desire stopped freezing xD
no crash, no freeze oder reboot since my last post.
I even tried to force it by watching videos, playing games, connect to the charger etc.
everything is fine... strange.
Will see for how long
Well this is good news. Just keep in mind what you can do if the rebooting comes back. Hope it doesn't
Well, it did xD
Now even shortly after reboot. I'll try ROM changes as soon as I get home but there's something I noticed: it often freezes when it's supposed to display a whatsapp notification and sometimes it seems there's a problem with the sdcard (just bought a new one because my old one went nuts). Sometimes the notification 'sdcard was removed unexpectedly' (translated from German) is appearing, but after waiting a few minutes everything is fine again...
Well I'll try some stuff when there's time...
Sent from my HTC Desire using XDA App
Hi:
I just wanto to let you know that I had the same issue, so I decided to send it to SAT, they changed the motherboard...
my problem now (with the new motherboard) is everytime I root my phone and use a cooked ROM, then freezes/crash again... ONLY works with the official ROM...
please let me know if you solved you problem pls... and how? of course...
I copy the link of my post (just in case helps to you)
http://forum.xda-developers.com/showthread.php?p=15103560#post15103560
best
SCeesarin
Hmm... I don't know what i did (nothing, actually) bit since my last post it runs stable... Absolutely nothing like freezing or crashing... Strange
Sent from my HTC Desire using XDA App
This is a long post, but I need assistance trying to get to the bottom of the random reboot and Black Screen of Death (BSOD) issue on the P93x series phones. Random chatter and dismissals are getting us nowhere, we need some structured approach.
I've submitted a CM bug report, and got Issue 6762 assigned. Feel free to star and follow there as well.
General Background Info
This seems to be a polarising issue: people who are in the know (technically) have devices without this problem, and people with this problem think the sky is falling and wondering why no fixes are coming. So before you jump all over me and tell me your P93x is fine and the problem does not exist, a little background is in order. I have two P930’s, one is humming along just nicely, thank-you-very-much, the other is experiencing the random reboot issue as well as the bsod, as validated by others in this forum.
Kernel OOPS on P930
Issues
First, I believe there are three issues at play (likely separate)
Random reboots especially when scrolling. Likely a kernel panic;
and, as per a good classification here
BSOD-A: Screen remains black, hardware buttons light up and touching buttons gives haptic feedback
BSOD-B: Screen and buttons remain black, no response to power button. Phone may become hot AND battery has taken a large hit when finally rebooted.
Scenarios for the above:
Using “heavy” apps like Google Maps, Waze, etc.
scrolling on lists or typing in some apps
device goes to sleep mode, can’t wake up the LCD. Keys light up, system up and running (background apps & loggers continue to operate) .. but can’t get to them.
devices reboots (often is is unseen since device is charging) and goes dead, can’t wake up. No lights, system down.
Both BSOD-A and BSOD-B require battery pull or long press of power button to restart device.
I am focusing on BSOD-B since ATM that's the bulk of empirical data I have at hand and it's a notoriously reoccurring problem.
If I manage to capture some good logs for BSOD-A (which are very rare for me), I will submit a separate bug report.
Troubleshooting BSOD-B
Here is a list of things I tried to narrow down where the problem may be:
wipes, full wipes, cache wipes, formats, etc.
nandroid clone of the stable P930 to the unstable P930
go through the unbrick process
flash back to Gingerbread
flash back to factory ICS
disable HW overlays in Developer Options
Here is what the effect these things had:
wipes stabilize the system for about a day or two before the problem reoccurs
nandroid clone had no effect. The unstable one still reboots/bsod
Unbrick process gives temporary relief. Problem still comes back after a day or so,
Gingerbread seems to be completely stable. No reboots or BSOD’s after a week of running it and incredible battery life.
ICS introduced random reboots, but no BSOD.
that seems to take care of the reboots while scrolling.
Observations
So first obvious observation: solution d) seems to fix all the problems. Buuuut … anyways moving on.
Second observation, solution f) seems to take care of vast majority of problem #1 under scenario 1b), so IMHO it’s a viable workaround, even though disabling HW overlays increases CPU usage and reduces battery life.
Third observation, BSOD-B most frequently occurs when under power, either AC or USB.
Fourth observation, based on analysis of kmsg for BSOD-B, the battery drain is due to a kernel fault, followed by a reboot, followed by CPU0 stall (after trying to initialize the LCD?). Here’s the kmsg related to this:
Code:
[ 2.021728] lm3530_probe: i2c probe start
[ 2.022369] mipi_lgit_lcd_probe: mipi lgit lcd probe start
[ 2.022521] setting pdata->panel_info.fb_num to 3. type: 8
[ 2.022979] mdp4_dsi_vsync_init: ndx=0
[ 2.029266] FrameBuffer[0] 720x1280 size=11304960 bytes is registered successfully!
[ 62.040008] INFO: rcu_sched_state detected stalls on CPUs/tasks: { 0} (detected by 1, t=6002 jiffies)
[ 62.040344] Backtrace for cpu 1 (current):
[ 62.040435] [<c010cf9c>] (unwind_backtrace+0x0/0x12c) from [<c010b1f4>] (smp_send_all_cpu_backtrace+0x60/0xc4)
[ 62.040618] [<c010b1f4>] (smp_send_all_cpu_backtrace+0x60/0xc4) from [<c0214fe8>] (__rcu_pending+0x43c/0x5e0)
[ 62.040802] [<c0214fe8>] (__rcu_pending+0x43c/0x5e0) from [<c02152fc>] (rcu_check_callbacks+0x170/0x1e0)
[ 62.040954] [<c02152fc>] (rcu_check_callbacks+0x170/0x1e0) from [<c01cec1c>] (update_process_times+0x38/0x68)
[ 62.041107] [<c01cec1c>] (update_process_times+0x38/0x68) from [<c01f2798>] (tick_sched_timer+0x98/0x258)
[ 62.041290] [<c01f2798>] (tick_sched_timer+0x98/0x258) from [<c01e6930>] (__run_hrtimer+0x1c0/0x304)
[ 62.041381] [<c01e6930>] (__run_hrtimer+0x1c0/0x304) from [<c01e6da8>] (hrtimer_interrupt+0x168/0x2f8)
[ 62.041564] [<c01e6da8>] (hrtimer_interrupt+0x168/0x2f8) from [<c0117b54>] (msm_timer_interrupt+0x18/0x20)
[ 62.041717] [<c0117b54>] (msm_timer_interrupt+0x18/0x20) from [<c020f51c>] (handle_percpu_devid_irq+0xfc/0x1a8)
[ 62.041870] [<c020f51c>] (handle_percpu_devid_irq+0xfc/0x1a8) from [<c020bb74>] (generic_handle_irq+0x2c/0x40)
[ 62.042022] [<c020bb74>] (generic_handle_irq+0x2c/0x40) from [<c0106ea0>] (handle_IRQ+0x7c/0xc0)
[ 62.042205] [<c0106ea0>] (handle_IRQ+0x7c/0xc0) from [<c01003b4>] (gic_handle_irq+0x80/0xac)
[ 62.042297] [<c01003b4>] (gic_handle_irq+0x80/0xac) from [<c0853754>] (__irq_svc+0x54/0x80)
[ 62.042388] Exception stack(0xda65ff98 to 0xda65ffe0)
[ 62.042541] ff80: 00000020 c0c23fb8
[ 62.042633] ffa0: da65ffd8 00000000 da65e000 c0c2d5c8 c0cb4124 c086e55c 4020406a 510f02d2
[ 62.042785] ffc0: 0000001f 00000000 00000000 da65ffe0 c0106fdc c0107384 60000013 ffffffff
[ 62.042968] [<c0853754>] (__irq_svc+0x54/0x80) from [<c0107384>] (cpu_idle+0x84/0xe8)
[ 62.043121] [<c0107384>] (cpu_idle+0x84/0xe8) from [<40a4b754>] (0x40a4b754)
[ 62.043212]
[ 62.043212] sending IPI to all other CPUs:
Why battery discharge
Gist of the problem: pm8058-charger driver and related infrastructure - like USB - is not loaded yet, CPU0 is hung, CPU1 observes that its colleague is hung and faults, re-tries, and the party continues until the battery is dead.
Possible Workarounds
The only way to avoid to BSOD-B while charging is to shut down and put phone in power-off charge-mode. This is not completely viable since BSOD-B also occurs in the car when navigating or any time USB power is on.
Improving empirical data
Challenges and roadblocks
Hanging this way and so early during boot presents a problem when retrieving kmsg. The new kmsg with the CPU0 stall replaces last_kmsg on reboot thus wiping any evidence of the real kernel panic which caused this whole thing in the first place.
To make it even more fun, there is a non-zero probability that a kernel panic followed by a reboot does not hang CPU0 .. meaning you’ll never know if a kernel fault will cause CPU0 to hang until it hangs by which time it’s too late to recover the all important last_kmsg. Dead end.
For further kick in the nuts, when the CPU locks and drains the battery down to zero (or is powered off) the device turns off and boots to charge mode (since it’s under power), now wiping the CPU0 stall kmsg and stuffing last_kmsg with charge-mode messages, this time wiping evidence of the CPU0 lock described above. This can be avoided by catching the device early in the discharge cycle and unplugging the device before forcing a reboot .. but still that only gets us to read the CPU0 lock kmsg but not what caused this whole mess in the first place.
Next steps
Any ideas on how to backtrack and get better logs of the initial crash? Logcat appears useless here since it's a userspace process which gets yanked the moment a kernel oops occurs. Even piping kmsg to a file does not work due to the same problem (ie. userspace). Is there a way to tell the HW to shut down on kernel oops rather than reboot? Do I really need to disassemble these two phones in order to compare and determine differences?
Any constructive ideas, suggestions, or thoughts will be greatly appreciated.
EDIT: As of April my P930 which exhibited this behaviour is in the hands of tdmcode. This way he has something to test on and hopefully at some point he'll be able to figure out a workaround for this issue.
Finally!
Finally!
Thanks for officially posting the bug. Some of us didn't have the ability to technically describe the problem and now you have done it for us. Hopefully some fixes will come so that we can all start getting normal usage of our phones, which are powerful when working reliably.
Thanks again!
I'm glad you reported it. It's probably a combination of more than one bug, though, so hopefully it gets resolved. I'm mostly hoping CM10.1 somehow resolves the bugs in CM10 when Ricardo gets around to working on our phone.
Sent from my LG-P930 using Tapatalk 2
Very nice summary.
However, given your own experience with two of them, and the "polarising" experiences, it seems to imply a hardware issue for at least one of the three situations, for example, a chip was revised at some point in production, or there was poor quality control on chip or component manufacture, etc.
I never had BSOD-B. The other two, well ... :crying:
Some other observations:
- P935, i.e., Telus, users seem to be more affected (or more proportionally more vocal) than Nitro HD users. Telus was/is offering affected users a new One X (or equivalent) as a straight swap. This is not typical carrier behaviour in my experience, especially after one has had a phone for over six months ...
- P936 users seem to be less affected.
Good luck on your quest, I hope it is successful!
I definitely agree with your hypothesis that it's hardware related. I suspected this when HONO first released an overclocked kernel for gingerbread. Some people could overclock to 1.8GHz without issue, and my phone would crash randomly and during benchmarks whilst underclocked massively. Same thing happened with Full Throttle for CM9.
Glad that someone actually submitted a bug report, thanks a lot!
Agree, this definitely presents itself like a QC or product rev issue. Based on how LG has handled it, it would seem it's a Qualcomm issue tho - otherwise I am sure LG would address it in their ROMs. This is why I don't hold out much hope ever seeing a fix/workaround for this.
I have no issues running the LG ICS releases (bell and att), except for an issue where the bluetooth driver becomes unresponsive. My head unit still reports being connected, but my phone will not turn off bluetooth or route audio through bluetooth OR speakers.
Sent from my LG-P930 using XDA Premium HD app
Blue tooth is your only issue? You sir are quite lucky.
Sent from my LG-P930 using xda app-developers app
Reboots and BSOD
Thanks for this post. I can add a couple of things, I have an AT&T LG Nitro, and as you say with GB work just fine, I can add that with v18f (ICS Leak) phone also works fine, no reboots or BSOD. I really think that this problem it's related with video, when I first installed stock v20c I had a very curious (and as far as I know common) problem, I have BSOD and after the phone reboots, a red halo appears on the screen, weird, it was solved after 3 or four reboots.
Another thing that I notice is that when I use Dolphin browser (it also happens with waze) and watch a site with flash content, and close dolphin, a strange drawing problem appears on screen, some kind of flicker, it can be solved reentering dolphin and close it.
I've been used liquid nitro for almost a week, after 6 hours of the installation I have the first reboot, then, I have 4 days without reboots or BSOD, incredible, but the fifth day the problem reappears, 2 BSOD.
Returning to what I think it's the root cause, maybe it could be related with video hardware acceleration, that could explain why v18f works, I think HW acceleration it's not complete implemented in this version, that's why it's not as smooth as v20c and works fine.
fguzmant said:
Thanks for this post. I can add a couple of things, I have an AT&T LG Nitro, and as you say with GB work just fine, I can add that with v18f (ICS Leak) phone also works fine, no reboots or BSOD. I really think that this problem it's related with video, when I first installed stock v20c I had a very curious (and as far as I know common) problem, I have BSOD and after the phone reboots, a red halo appears on the screen, weird, it was solved after 3 or four reboots.
Click to expand...
Click to collapse
Oh man, I've had the halo thing appear once as well and it would not go away .. that was a scary moment as I thought the LCD got fried for some reason. Very very weird effect.
fguzmant said:
Another thing that I notice is that when I use Dolphin browser (it also happens with waze) and watch a site with flash content, and close dolphin, a strange drawing problem appears on screen, some kind of flicker, it can be solved reentering dolphin and close it.
Click to expand...
Click to collapse
Did you try disabling "HW overlays" under Developer options? I have had weird drawing problems for graphically advanced apps, but disabling HW overlays seems to fix that up for me. Also, the overlay issue went away for me in the latest nightly CM10 builds .. no drawing artifacts, and no reboots I can link to video acceleration issues. Wish I could say the same thing about the BSODs ...
fguzmant said:
I've been used liquid nitro for almost a week, after 6 hours of the installation I have the first reboot, then, I have 4 days without reboots or BSOD, incredible, but the fifth day the problem reappears, 2 BSOD.
Click to expand...
Click to collapse
This is the other weird part about these BSODs .. they takes time to build up. When I do a full wipe, I will be OK for a few days, then BSOD hell begins.
Yes, I get the red halo effect too randomly after a BSOD, sometimes it has gone to the point of taking up the while screen with the red, and somewhat flickers as well. However it doesn't usually get that bad.
Sent from my LG-P930 using xda app-developers app
miji2 said:
Did you try disabling "HW overlays" under Developer options? I have had weird drawing problems for graphically advanced apps, but disabling HW overlays seems to fix that up for me. Also, the overlay issue went away for me in the latest nightly CM10 builds .. no drawing artifacts, and no reboots I can link to video acceleration issues. Wish I could say the same thing about the BSODs ...
Click to expand...
Click to collapse
Sadly, liquid nitro or v18f does not have that option. My experience with CM10 was a BSOD nightmare.
I too have gotten all three types of hangs:
1) Reboot to CM logo (every couple days)
2) Can't turn screen back on but other buttons working and responsive (rare)
3) Reboot to LG logo followed by black screen and battery drain (every couple days)
I don't believe I ever had 2 and 3 happen on CM9 FT though, just CM10.
Thanks for submitting a report!
Sent from my LG-P930 using Tapatalk 2
On Official ICS, CM9, and CM10 I always have the random reboots. Doesn't happen in Gingerbread. I have tried every work around that I could find and the random reboots continue. I only started experiencing the wake locks in the newest CM10 nightlies. For now I have gone back to stock rooted gingerbread. At least until the reboot issue is resolved, if it is.
ahdoublexl said:
On Official ICS, CM9, and CM10 I always have the random reboots. Doesn't happen in Gingerbread. I have tried every work around that I could find and the random reboots continue. I only started experiencing the wake locks in the newest CM10 nightlies. For now I have gone back to stock rooted gingerbread. At least until the reboot issue is resolved, if it is.
Click to expand...
Click to collapse
Did you try ICS Leak v18f, I can confirm that there's no reboots or BSOD in this ROM, the problem with this it's battery life, but with setcpu and juice defender I can manage to survive a day.
OK, new theory to test: cache partition corruption causing BSOD
Background:
I observed several times that BSOD type B does not occur until the phone starts to reboot randomly (due to scrolling or otherwise). Same this time: after running the 20121201 nightly (+ reset) smoothly for the past 3 days, I got a reboot due to kernel oops, then my BSOD-B started.
Recovery
This time I was able to fix the Random reboot while charging leading to BSOD-B by just formatting the Cache partition from recovery. I am not sure if I tried that before, but it worked this time. But this kind-of explains why a factory reset would stabilize the phone for a bit ...
Testing
I need others to test so we can confirm this. To help, please try latest nightly, and watch the BSOD causing the phone to get hot. If you get it, format your cache and let me know if it made any difference.
Follow-up
Note, we still don't know what patterns of use cause the random kernel oops .. but at least we would not have to endure dead phones first thing in the morning.
miji2 said:
OK, new theory to test: cache partition corruption causing BSOD
Background:
I observed several times that BSOD type B does not occur until the phone starts to reboot randomly (due to scrolling or otherwise). Same this time: after running the 20121201 nightly (+ reset) smoothly for the past 3 days, I got a reboot due to kernel oops, then my BSOD-B started.
Recovery
This time I was able to fix the Random reboot while charging leading to BSOD-B by just formatting the Cache partition from recovery. I am not sure if I tried that before, but it worked this time. But this kind-of explains why a factory reset would stabilize the phone for a bit ...
Testing
I need others to test so we can confirm this. To help, please try latest nightly, and watch the BSOD causing the phone to get hot. If you get it, format your cache and let me know if it made any difference.
Follow-up
Note, we still don't know what patterns of use cause the random kernel oops .. but at least we would not have to endure dead phones first thing in the morning.
Click to expand...
Click to collapse
Tried the procedure above with todays nightly. So far only one reboot but that was due to the camera bug. No BSOD so far.
Will see if it happens overnight
EDIT: charged overnight and still no BSOD. So far so good. :thumbup:
Edit 2: just got BSOD, so I guess its back to the drawing board.
Sent from my LG-P930 using xda app-developers app
khanfed said:
Edit 2: just got BSOD, so I guess its back to the drawing board.
Click to expand...
Click to collapse
Same here
khanfed said:
Tried the procedure above with todays nightly. So far only one reboot but that was due to the camera bug. No BSOD so far.
Will see if it happens overnight
EDIT: charged overnight and still no BSOD. So far so good. :thumbup:
Edit 2: just got BSOD, so I guess its back to the drawing board.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Wasn't the whole point to clear cache after any sort of crash-reboot? The idea was a crash-reboot will corrupt the cache and then cause the BSOD.
Sent from my LG-P930 using Tapatalk 2
Yup the procedure above was done after a crash/reboot, but in the end it didn't resolve the issue, since I got the BSOD again.
Sent from my LG-P930 using xda app-developers app