I have searched through XDA and read all the threads regarding the 'suspend process' issue. The specific issue is outlined in Issue # 11126 on the Google Code/Android project home...
http://code.google.com/p/android/issues/detail?id=11126
I am trying to get to the bottom of this, as best as possible. For all intents and purposes, this really appears to be a mystery. Ultimately, it appears as though there is (currently) absolutely no specific reason a to why 'suspend' runs wild until the device is rebooted.
My question is (I know we can all only speculate):
Is there any chance that this could be Google account-specific?
The reason I ask is, I've been doing some "testing," just to try and make sense of this for myself. Here is what I've done/come across thus far...
- My fiancee's first MT4G was a black one manufactured in Taiwan. It had the inferior LCD-SH-C2 screen. Her battery was draining VERY quickly - i.e. before noon, without using the phone for much else other than texting.
- I enabled USB Debugging for her, to "rule out" the init process issue.
- Even though she only had Handcent, Facebook and Angry Birds installed, I removed all of them, leaving only Watchdog.
- I factory reset her phone, twice.
- For all of the above, the device was not rooted. I have since rooted her phone via the steps in this thread.
I'm in the process of creating a new Gmail account for her, exporting ONLY her contacts and then using that account for her new MT4G (Plum) that's scheduled to arrive today. I'm actually thinking of NOT using her new Gmail account at first though, so I can use her original Google account on this new, clean device and see if the suspend issue persists.
I might just be wasting my time, but I enjoy doing this and I don't think it's a complete waste to try and find SOME constant here. Am I nuts for thinking it's tied to the Google account? The Google account seems to be a black box of sorts. There is more than just contacts, apps and settings, yet there is no "window" into everything else that comes down - e.g. I can't log in to Gmail and "configure" it to not restore her wallpaper or WiFi settings. So that's why I say it's a black box of sorts, since it's doing more in the background than we have control over.
Nothing is truly random, at least not in the context of Android and the hardware affected. There has to be some reason why users of various devices, either do or do not experience this issue. Whether it's a specific action or the something that differs between one person's action vs. another person's, there has to be SOMETHING that's triggering this on her device, yet never triggers it on mine. I guess I'm just trying to flush everything out and hope that discussing it will help rule out/rule specific variables.
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
mwelliott said:
Let me know what you find. This is driving me crazy! I charge my phone at night, so when I head to work it's at 100%. By the time I'm heading home (4-430pm)... the phone is around 15% battery.
Watchdog tells me suspend ranges from 5%-49% at any given time. I've never had suspend drop below 5% except on fresh reboot. I've noticed, though, after a reboot that the suspend process will slowly work its way back up to using lots of CPU cycles (it starts at, say, .2%, then 10 minutes later its 3%... 30 minutes later its 5%... an hour later its 9%). Battery just gets hotter and hotter due to this.
I'll be checking back to see what you find! Thanks!
Click to expand...
Click to collapse
According to XDA and Issue #11126, you're not alone.
What's really bugging me is that neither my first MT4G, nor its 1st replacement or its 2nd replacement, have ever done this. My fiancee's first phone did this. She is now using my 2nd replacement while she waits for hers to arrive (today). So a device that never exhibited this issue, over the course of at least a week of normal-for-me use, started exhibiting this issue for my fiancee maybe a day or so after using the phone.
I thought I had "solved" it when I didn't see it crop up the first day she used my replacement phone. She was quick to let me know I was incorrect.
So I've got serious pressure here - all of my MT4G's haven't exhibited the out of control 'suspend process' issue while I was using the devices, but with her, it does. <queue the jokes>
We own our own business, so we're in the same room all day long while we use our phones. I was the first to tell her, "it's something you're doing." I'm only repeating myself by saying that I blamed it on an app she installed or something she "did" to cause it. After factory resetting, what...2, 3 times...I'm starting to forget; after checking the apps that are installed (and removing all of them); after verifying every setting from USB Debugging, screen brightness, account sync, etc. I seem to at least be able to say, "every single setting, shortcut, widget, app or usage pattern, does not produce the issue on any device I have used with my Google account, whereas it does with my fiancee."
That's the most difficult part to get absolute - the usage pattern. She's doing such basic things though, but I know that even the slightest of difference can produce different results.
I will most certainly report my results, futile or not.
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Chadastrophic said:
The only common denominator I've noticed so far is that it only affects Sense UI devices.
Click to expand...
Click to collapse
That seems to be the constant, to a degree. I'm seeing people state that they're having this issue on anything from the Samsung Galaxy S (i9000) to a Nexus running Cyanogen 6.1. That's people stating it though, so I'm not sure if they're actually experiencing the same issue or not.
I am biting my tongue, but I think I found another common denominator...I am going to post back in a coupla days once I've seen it last for this entire week.
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
zero_oli said:
hi,
i'm running cyanogenmod 6.1 on a desire hd and have been experiencing the suspend process problem exactly as described in this thread a nubmer of times now over the last week. so its definately not limited to devices running sense.
the only circumstances this behavior hasnt shown is when running 2g only with all other sorts of communications and sync off
Click to expand...
Click to collapse
Yeah, it didn't seem 100% related to devices running Sense, so thanks for posting back to this.
My fiancee was experiencing this across her first two MT4G devices and has yet to experience the issue on her third and final MT4G. I want to see it run the rest of the week though before I share, but the issue did pop-up for her pretty much within 24-48 hours on her first two MT4G's.
Shlongwoodian: I have been following your posts as the "suspend" process has been affecting me since I received my phone the first day available. However, I am reluctant to send for a replacement as all else is great on the unit I have and there seems no gaurantee that a new phone fixes this issue.
I have tried Tmo and HTC and both seem clueless; therefore, I appreciate your research and look forward to any "fix" short of waiting for Gingerbread.
Anyone have any wisdom to pass on? This issue is driving me crazy! I've noticed it most on my black MT4G (w/the good screen) after browsing the web, youtube or using the media player. My wife's red MT4G (w/the inferior screen) has had no issues and her battery is amazing! The first day she got her phone her battery lasted 24 hours without even conditioning it! Granted she doesn't use it like I do mine, but it is still a huge difference. When this issue comes up on mine, I'm dead within 3-4 hours. I have Watchdog set so when it alerts me I just soft reset. That clears it up until it decides to come back at random intervals. It usually doesn't come back until I open the browser, etc. With as much as I use my phone (I am constantly on the road), it becomes a major pain to have to constantly monitor battery life. Any help is greatly appreciated!!!
Man, I am sorry to report that I gots nothin'. Ok, here was my original theory...
I was speculating that "something" inside the Google/Gmail account was the cause. My reasoning being, essentially, your info is stored in a database. When you get an Android device, that online database is synced locally with the phone's database. We each have different databases and there is more than just your apps, Market links, contacts, etc. I never exhibited the /suspend issue on phones that she experienced the /suspend issue on. I figured it was database-specific.
If a table contains a value, or rather, does not contain a specific value (or if columns are missing, etc.), it can cause an application to respond in a negative way. Sometimes, this causes an error to bubble up in an application. Other times, it doesn't. In my experience, I've seen much more subtle issues in databases, that don't cause errors or a crash, but instead just cause "undesirable results."
When my fiancee got her final, good replacement Plum Glacier, we started with a completely new Google account. We thought we nailed it, when a handful of days passed without seeing /suspend get out of control, leading to Android System and/or OS sucking down battery life. I think it was nearly a week into it and one day while she was out, she realized she lost battery life really quickly - i.e. left the house with 90% and by the time she got to the store, shopped for a bit and looked, her phone was down to like 30-40%. She knows how to check for /suspend and it was, of course, back.
It's still not something that can be completely ruled out, since it's not a very air-tight test. There could be something about my Google account (which I've had pretty much since Gmail beta was available) that's keeping me (and others like me) from getting it or that idea could be crap.
For some reason, I have never, ever seen this happen on my Glacier(s) running stock 2.2.1. Phones that I never saw the issue on, she saw the issue on. There is so much speculation around it, but it just seems like "some people" don't experience it and "some people" do. It's all over different devices, different skill levels, etc. No apps, same apps, whatever and it happens to some but not others.
Sorry to get anyone's hopes up. I'll keep looking for differences/similarities though and if I find anything at all I'll - or if anyone else finds anything, no matter how ridiculous it sounds (yes, we've tested the 'rock' and it doesn't appear to suffer from the /suspend issue) - post it here.
Thanks for trying! It was a good theory. So . . . now what? Is there any way to get this ranked higher with Google, HTC, etc. to get more people working on it? It is really driving me nuts! It mainly happens after I use the web browser, then put the phone on standby for some reason. I can't even use the browser any more without needing to reboot it to save battery life. There is another thread, but specifically for the Evo and I think one for the Nexus one, all with the same problem. What if a new thread were started that is not device specific? That way we can get more people to star it and maybe Google or whoever will pay more attention to it! I would hate to think that we are stuck with this problem until when and if we get upgraded to 2.3. I would suggest rooting and flashing a new ROM, but even those with custom ROM's are having the same problem, so that's not going to help. Thoughts???
jpiano said:
It mainly happens after I use the web browser, then put the phone on standby for some reason.
Click to expand...
Click to collapse
It truly is a mystery to this day. I've seen people say, "it happened right after I installed Handcent" or "it happens as soon as I do..." No one has come up with any concrete evidence thus far.
My fiancee has Handcent, I have Handcent. I used Handcent heavily, never had an issue. She stopped using Handcent - still has the issue. We've gotten so granular in our troubleshooting, we're literally tracking every step. LOL i.e. I pressed the trackpad to wake the phone, once; I unlocked the phone, I swiped my thumb once to view my Watchdog Widget on the screen to the left of my homescreen, etc., etc., etc.
So, for now, we just wait? My phone (and all previous phones) have been just fine. My fiancee however...yeah, I'm trying to find a fix pretty quickly.
One common theme that I've seen with this issue is that it only happens after I put the phone to sleep. I have never seen it crop up while actually using the phone. Maybe we're going about it the wrong way in trying to identify an app, etc that's causing the problem... perhaps it is simply the code involved in putting the phone to sleep and that's why there hasn't been any consistency with what one does to make it appear. In your experience, have you ever seen or heard of it showing up while the phone is being used? Perhaps it's just on mine that it works that way, but I thought it was worth mentioning. I know nothing about code or how android works so please forgive the noob comment if this is an obvious one. Merry Christmas!
I've got this problem big time. Returned my first phone because I thought it was the phone. First few days were good but lately its back and as bad as ever. First thoughts were angry birds twitter or wifi but I have no idea. If I can't figure this out I might have to sell this phone.
I will try to post some more thoughts. I think you're onto some good ideas here.
Sent from my HTC Glacier using XDA App
(Re-posting from the developer's Google blog where others are following this issue): Interesting about using the phone without a Google account. Not sure if this is relevant or not, but I've noticed something else with consistency. Granted I wasn't able to document the behavior through system panel at the time, but this has consistently happened. When suspend goes crazy, I can get it to stop simply by charging the phone! Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot. Noob speaking here but perhaps the part of android that actually logs the battery usage is suspending when the phone goes to sleep? When it us charging, this log is reset and clears the process from running. If this is even possible, then could someone write an app that clears this system log? Maybe by mimicking what happens when the phone is charging, we can at least temporarily clear the issue without the need tovl reboot? Again, I know nothing about all this so sorry if this is all irrelevant. Just sharing what I've noticed to be consistent. Thoughts??
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
jpiano said:
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I wonder if you're on to something with the SD card. I've been thinking I haven't seen the suspend issue return on my phone in quite a while. I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems. For those who are having the problem still, I wonder if removing or formatting their cards would show any improvement? Worth a shot if at least to eliminate another possible factor.
Sent from my HTC Glacier using XDA App
That's cool that this thread is flushing out other ideas and possible variables. I like the idea of connecting it to the charger for a couple of seconds, but my fiancee is so used to just rebooting her phone each morning and sometimes again by mid-day, that it's easier for her to do just that.
jpiano said:
Even if I charge the phone for a few seconds, then unplug, it stays dormant without having to reboot.
Also, I saw on another xda blog (http://forum.xda-developers.com/showthread.php?t=870557&page=2) that someone linked this issue to a corrupt photo on the sd card. After formatting the card and restoring some files, says the issue has not returned!
Click to expand...
Click to collapse
I like the microSD Card notion. This is such a weird issue, that it's so easily associated with other items - e.g. applications, usage patterns, etc. This seems feasible though, but the only way to know for sure is to reproduce it. My fiancee experiences the suspend issue daily, if she doesn't reboot regularly. So, I should be able to take her microSD card and use it in my phone and get the suspend issue. I don't want to 'muddy' up by swapping microSD cards, so I'll try reformatting her card and see if that makes any difference. She usually sees the issue within 24-48 hours of a fresh boot, so it shouldn't be long before we see if that fixes it or not. I can check the card for errors, etc. as well.
werk said:
I just realized that the only thing I've really changed is installed a new 16 gb SD card. Since then, no suspend process problems.
Click to expand...
Click to collapse
I'll be upgrading to a 16 GB Class 10 soon, so I can give her my Samsung if need be. I'd really like to see if this is it though. It would explain the "some people get it and some people don't" pattern.
I also noticed that the minute I plug the phone in the problem goes away. Not sure why, just confirming it happens to me too. I also should note that when I returned my phone, they popped my old SD card into my new phone. So if there is an SD card issue with a corupt file/photo that could be something as well. I wonder woody if your girlfriends phone has had the same SD card after how many times did you say you traded it in? BTW, a side note, how did you exchange it so many times? After I took mine back to the store on day 14 they told me I wasn't able to exchange it again.
I do have a 16GB SD card but just haven't had time to install it. Wanted to double check which things I need on the new one from the old one, but it might be a good way to test this issue. Let me know some ideas before I swap the cards and maybe I can help test this.
Also, one more thing, what is the app you're using to log stuff? I'm just using Watchdog Lite right now.
I've got to figure this out or this is a dealbreaker for me. I have waited 3 years to upgrade phones, first time on Android, really wanted iPhone but wanted to stick with month to month from TMob. If this continues I think I will move to Windows Phone 7 or iPhone if I have to, but I really like this phone when the battery is not draining like a leech.
Thanks.
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
royhobbs said:
werk,
Just wondering what process you went through when you upgraded SD cards. Did you copy any files over to the new one or just start blank?
Thanks.
Click to expand...
Click to collapse
Just straight copied the existing files over from the old card to new one (new one in phone connected via USB, old card in SD adapter in my laptops SD card slot). I think some Angry Birds files didn't make it due to long paths, but reinstalled it and no problems since then.
Hi Everyone, I've owned my TF w/ dock for a few months now, and sometimes it just frustrates me...
I know i'm not alone on that one, but man it sure is dissapointing. Things are getting better with each honeycomb update, but we all paid quite a bit of money for this experiment.
Anyways, the latest issue i have is that Pandora will randomly start playing. As in, i used it on sunday for a few hours, and it randomly started monday morning some time. I didn't do anything to the tablet, besides have it on the charger over night, and it randomly started playing again this morning. I hadn't even opened it up in the time between. This time it woke my girlfriend up and she has to work tonight overnight.
Anyone else have this issue or something similar? Is it a random reboot? I really haven't opened it up so i haven't checked the status/runtime.
ugh. I'm really trying to like this thing and there things that i think are great, but some things that i didn't expect to be an issue are. Random pandora playing and a crappy browser are not things i expected...as well as docking station battery drain issues.
Ok, i just checked my system status and it's been up for over 171 hours, so no reboot. Any thoughts on what could be going on?
First of all, considering running on that many hours, I would suggest rebooting. Android is built on Linux and all PC platforms requires an occasional reboot. I would try uninstalling Pandora, reboot and then reinstall. Also, its goes without saying that when you buy a device when it first comes out, you are taking a risk of the increased possibility of faulty equipment as the manufacturer isn't aware of the faults yet.
Sent from my Inspire 4G using XDA App
i agree, give it a fresh boot and see if it helps
cavsoldier19d said:
First of all, considering running on that many hours, I would suggest rebooting. Android is built on Linux and all PC platforms requires an occasional reboot. I would try uninstalling Pandora, reboot and then reinstall. Also, its goes without saying that when you buy a device when it first comes out, you are taking a risk of the increased possibility of faulty equipment as the manufacturer isn't aware of the faults yet.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
I know a reboot may be necessary from time to time. I generally do it with mobile devices when something starts to act up while i'm using it or it appears sluggish. This wasn't the case so i hadn't done it. The first time it had done it was probably after 5 days of being online. It just seemed odd that it decided to start playing while shut with the screen off. I will also make sure i quit the app before leaving it overnight.
It only did it while the unit was asleep and pandora was alive in the background. it didn't start up pandora and start playing.
Just because bugs can be expected, doesn't mean i can't be frustrated
True. Well the main benefit to rebooting is that it allows the system to purge and reallocate memory, which memory is usually the main culprit of alot if minor issues. Its possible that for whatever reason, when you exited the app, if it didn't fully clear all processes and services out of memory, for all intents and purposes, the app could still be running to an extent in the background, causing anomalies like such. Not saying that this explains your issue, but its plausible.
Sent from my Inspire 4G using XDA App
Here's the rundown ...
Last night I was playing a little Nimble Quest before bed. I started to get tired so I quit out of the game and as I was turning the phone back into portrait mode the screen went black (still on) and seemingly froze. I let it chill for a bit, then it vibrated and I heard my notification sound. I let it go again and a few seconds later it did it again (vibrate/sound). This happened a couple more times before I decided to hold down the power button and attempt to shut it down. After holding the power down for about 5-6 seconds, the phone rebooted itself. It stayed on the CM boot screen for what seemed like 5 minutes--long enough for me to think it was bootlooping. Finally I saw the screen brightness lower and the lockscreen came up. My background was there but all of my homescreen icons were gone. All of my apps were there, but all of the data was gone. Rather than deal with it at 1AM, I put it on the charger and let it go.
This morning I did a full wipe and restored a nandroid backup from the 20th. Everything seemed back to normal. When I got to work I reflashed the CM10.1 stable that just came out and faux's mainline 16 kernel, effectively bringing my phone back to the state it was before last night's drama. I got up from my desk to get coffee and when I returned I noticed my phone was on with a yellow screen that read:
HW reset was detected!
---------------------------------------------------
DemiGod Crash Handler : HW reset was detected!
There was some other stuff too but I decided to Google it before I did any of the things listed on the screen. I found a post in the Optimus G forum describing the same thing. One of the members said to hold down the power button until the phone shuts down, then restart and everything would be cool. No one else in the post seemed to see it as a big deal.
I went ahead and did what was recommended and my phone seems to be OK. Nothing weird has happened since then.
I guess my question is: what could've caused this? Is it my ROM/kernel combo or is it more likely the actual hardware? Should I be alarmed? My phone is less than a month old. Any help would be appreciated. Thanks!
I'm not an expert here, so I might not be the best source of advice, but I'll try.
The 'HW reset' message is kind of weird. I assume it means hardware reset. Out of curiosity, are you playing with the voltages or clock speed of your processor? Maybe it went out of the fringes of usability and crashed. Although if that happened, I'm not sure if the system would realize it and automatically recalibrate it (hence the 'HW reset').
You said you were playing a game called Nimble Quest when you first had issues? Is that a really resource-intensive game? Maybe your chip overheated, and the system freaked out and reset something. Then again, there was plenty of time between that and when you actually saw the screen so I doubt that.
I couldn't tell you, OP. That is very strange indeed. Did anyone in the thread you found about the Optimus G have any suggestions as to the cause?
Johmama said:
I'm not an expert here, so I might not be the best source of advice, but I'll try.
The 'HW reset' message is kind of weird. I assume it means hardware reset. Out of curiosity, are you playing with the voltages or clock speed of your processor? Maybe it went out of the fringes of usability and crashed. Although if that happened, I'm not sure if the system would realize it and automatically recalibrate it (hence the 'HW reset').
You said you were playing a game called Nimble Quest when you first had issues? Is that a really resource-intensive game? Maybe your chip overheated, and the system freaked out and reset something. Then again, there was plenty of time between that and when you actually saw the screen so I doubt that.
I couldn't tell you, OP. That is very strange indeed. Did anyone in the thread you found about the Optimus G have any suggestions as to the cause?
Click to expand...
Click to collapse
At the time I was using faux's kernel and his FauxClock app. Processor speeds were set to his recommended for good battery life (384 min 1512 high, intellidemand). Also, I can't imagine Nimble Quest being very demanding. It's a 2D, 16bit style snake-type game. No one in the Optimus G thread had another other suggestions than holding power down to restart.
So the night before last I had another episode with soft reboots. I couple in a row. No data loss, but still annoying. This morning I decided to ditch faux's kernel and flash the latest CM nightly (people have been saying the nightlies are pretty much just as stable as the RC/stables). Just about 15 minutes ago, I was playing Nimble Quest again and had the same problem. I quit out of the game and the screen went black, but still on. I felt a quick vibe and heard my notification sound. Count a few seconds and it happened again. I held down power for a few seconds and the phone shut down. I booted back up and everything seems to be there except for my wallpaper. I've tried setting a new wallpaper and it's not working. I just get a solid black background.
At this point I'm really worried that it's my hardware and not the ROM/kernel/software. How should I go about testing this? I assume the most foolproof way would be to flash the factory image and run it stock for a while to see if I have problems. Before I go that route should I try a full wipe, CM install and forego restoring my apps with TiBu? Could it be a corrupt app or data causing this issue?
Again, any help is appreciated.
I used to have it too when I was using Faux kernel. Turning off C3 and C4 in FauxClock fixed it for me.
daewond3r said:
At the time I was using faux's kernel and his FauxClock app. Processor speeds were set to his recommended for good battery life (384 min 1512 high, intellidemand). Also, I can't imagine Nimble Quest being very demanding. It's a 2D, 16bit style snake-type game. No one in the Optimus G thread had another other suggestions than holding power down to restart.
So the night before last I had another episode with soft reboots. I couple in a row. No data loss, but still annoying. This morning I decided to ditch faux's kernel and flash the latest CM nightly (people have been saying the nightlies are pretty much just as stable as the RC/stables). Just about 15 minutes ago, I was playing Nimble Quest again and had the same problem. I quit out of the game and the screen went black, but still on. I felt a quick vibe and heard my notification sound. Count a few seconds and it happened again. I held down power for a few seconds and the phone shut down. I booted back up and everything seems to be there except for my wallpaper. I've tried setting a new wallpaper and it's not working. I just get a solid black background.
At this point I'm really worried that it's my hardware and not the ROM/kernel/software. How should I go about testing this? I assume the most foolproof way would be to flash the factory image and run it stock for a while to see if I have problems. Before I go that route should I try a full wipe, CM install and forego restoring my apps with TiBu? Could it be a corrupt app or data causing this issue?
Again, any help is appreciated.
Click to expand...
Click to collapse
Hm, this is an interesting bug indeed. I guess first, I would try
illhangon said:
I used to have it too when I was using Faux kernel. Turning off C3 and C4 in FauxClock fixed it for me.
Click to expand...
Click to collapse
.
If that doesn't work, I would at least try a different kernel. If that does nothing, I would try changing ROM, and without restoring any apps or data. Is the only time you can get this problem with that specific game? If so, the game itself might be a faulty-coded game. If you get this problem elsewhere, try messing around on the newly-flashed ROM in the other areas you can replicate this. If you can't get it to soft-brick, try downloading that game and playing it on the fresh ROM/kernel. If you still get it, try flashing another kernel again. Basically, try 2 different ROMs, each with 2 different kernels, with and without Nimble Quest. Might seem like overkill, but I'm just trying to completely eliminated ROM/kernel problems, and any app problems. If none of that works, I really don't know what to say, maybe it really is a hardware issue.
Tonight, I'll try downloading Nimble Quest and playing it for a bit to replicate the issue. Is it just playing the game in general that crashes, or is it specific actions that you've found that really trigger it? From what I've read, the issue seems to pop up when you quit the game. I assume that just means hitting the Home key? I've read the reviews on the Play page and can't find one that complains about system-wide problems. I have a feeling it isn't the app, but it doesn't hurt for me to try and replicate the issue. If I get it, that means it's either the game, or specific settings both you and I share, and we will need to dig a little deeper to find out what it could be. Anyway, I'll mess with it a bit tonight and get back to you tomorrow if you haven't already found the cause/solution.
It happens every time the modem crashes. Earlier it just used to reboot without giving the message.
Sent from my Nexus 4 using xda premium