Related
When i press the power button, there's a 0.5s delay before the screen turns on. Is this normal, or just with mine?
You flashed it with anything or running stock?
Sent from my GT-I9000 using XDA App
running JM2
Any custom kernels for lagfix / oc?
Sent from my GT-I9000 using XDA App
Nope, just flashed jm2, and rooted, nothing else.
Dunno then, might be normal. Its even worse with the lagfix kernel.
Sent from my GT-I9000 using XDA App
Hmm ok, thanks for you fast reply's!
OMG! are you guys for real!
this is >insert slur here<
a fraction of a second for the screen to turn on from off is normal on any phone device.
....
Don't label me with the same brush as the op. I was trying to ascertain if he had the startup lag from the custom kernel used for the lag fix with samset. I said it was probably normal - I refrained from calling him an impatient fussy so and so. Abuse him all you like, leave me out of it.
Sent from my GT-I9000 using XDA App
How is this normal on any device? as my touch diamond didn't have it, my ****ty nokia 5800 didn't have it, my htc artemis, htc tytn II, do i need to continue?
It's 0.5s-1.5s. But mostly 0.5s, that's why i said that.
If you don't have a solution, just don't post , i flashed jp3 to try it out, and the delay i've got from jm2 is gone. Hmmm, guess the delay wasn't normal after all.
Damn, i feel like i'm on a chatbox with 12-year old's.
And no, i don't mean Bynar010 to be clear.
Hello all.
This wake up lag is killing me, coz its 1.5s most of the time.
I did apply the lag fix kernel, and that was worse at times. So now i simply reflashed it (JM5 now) and removed the SD card.
Is there anything else I gotta to to remove this fix, or re-flashing removes it ok?
Thanks in advance
I am also having this problem. It can be anywhere from half to three seconds . I have just flashed to jm5 and applied the one click internal lag fix. Anyone know what I can do to fix this. Thanks in advance.
Same problem here on JM2 + 1 click lag fix. I previously use JM2 + memocan and not found this problem. Wondering why others with 1 click lag fix didn't realize this since it's very longer (mine's about 3 sec).
3 second is nothing...
just pressing the POST button to this took more than 3 sec
In that case not only this phone sux, but your internet connection isn't much better..
Please just reply if you can help us with this problem. I like the phone, but the power-on delay is just annoying. I use it instead of a watch too. Wouldn't you care if you had to look at least 3 seconds at your watch before you could see the time, EVERY time you looked?
As i said, this is just annoying, other phones i've owned didn't have a delay like this, not even the WM ones.
i don't know about you, but the last WM phone and PalmOS phone i've had took at least 1 sec to display
yes i use my phone as a watch as well, i don't carry a watch with me
Just to throw it out there, mine lags about 0.25 to 0.5 seconds on average. I'm on JM5 without root.
Do you mean lag when you press the power button to unlock your phone, or when you switch on your phone? It's of course normal during switching on the phone. But I also experience a lag when unlocking the phone (~1 second). It only happens when I haven't used the phone for 5 minutes or more. Doesn't happen if I lock it and immediately try to unlock it again. I believe it's the chipset waking up from sleep or something.
@ AllGamer:
The ones i had: HTC: S100, Artemis, Kaiser, Touch Diamond.
They all went on faster. I didn't have the problem at first (with stock firmware), guess it started after my first flash (to jm2), but the problem stays when i flash back to the stock firmware, that's the strange part..
@ ssj4Gogeta1:
I mean the delay when you press the power (or home) button when the phone is already powered on, and it happens everytime, even when i press the power button, wait 5 seconds, and press it again. Nowdays, it's at least 1.5s every time.
Lol, would be great if i meant the power-on time.
the thing is, all phones i've had, will go slower and slower the more apps i install into them
the same applies to SGS.
to keep them fast, i always only install apps that i'm really going to use.
i used to clam every single piece of software i can put my hands on into the phone before, that always lags the phone to death.... although so far the SGS is holding quite well
still testing out a lot of software, but once i'm done i'm going to stream line it with only the stuff i want in it.
Regarding the delay with the Home button, that is not the same as Power button.
See now we understand you better, it does takes a split second after you wake up the phone with the home button.
however anything longer than 1 sec is not quite right, if you have that sort of lag, try optimizing the phone.
recent firmware updates like JH1 or JH2 depending where you are, have made vast improvement on performance
in the worse case scenario you can try the one click lag fix from the Dev section of the forum
are you still on the stock firmware?
Im having some issues with my vibrant and since today, everytime I lock the screen, then i try to unlock it, it stays black and nothing comes up or anything i just can seem to unlock it without holding the power button which causes the vibrant to restart. is anyone having this problem? Any solution to it other than formating maybe? Its rooted and I have a lag fix on it.
I'm assuming you've rebooted?
no i didnt. i didnt try to do that because i didnt want to lose everything. i was hoping its some app and i tried uninstalling some apps but still got the same problem. It keeps happing to me everytime since earlier today. you think that would work?
s15274n said:
I'm assuming you've rebooted?
Click to expand...
Click to collapse
I thought the same thing.
Ok. Something must be in the air. Exact same thing happening to me today.
Each time the screen times out the phone becomes unresponsive. Blank screen, soft keys don't light up. If I hold the power button too long it just reboots.
Rooted
Flashed lag fix
Clockwork recovery
Set CPU
Ya know what, as soon as I posted the details on my phones configuration it dawned on me that it could be a setcpu problem... Looking into it.
Set CPU was my problem. When I looked at the min/max they were both set at 19 out something ridiculously low like that. NO MORE SET ON BOOT!
I bought SetCPU but have not installed it on the Galaxy... I really don't see the point right now unless you want to underclock, and yes, it has been reported (perhaps fixed now?) that set on boot could cause issues.
I would just uninstall till we have a kernel we can OC.
OP, what would you lose by rebooting? Yes... I do believe that would work (and uninstalling SetCPU if you have it or change the aforementioned)
Set CPU profiles cause the phone to reboot and or freeze. See this thread forum.xda-developerscom/showthread.php?p=7808723#post 7808723
lagginess
Just to clear the setcpu is useless without a proper kernel i had it everything bogged down badly like reported went down to 19 from 10000. I would just take off the setcpu and wait for a kernel my phone def sped up after but thats my own experience.
Sometimes my phone will get very unresponsive such that any action takes many seconds to show up, and everything is very choppy. Often I see this when I wake up in the morning, but it happens often enough in general. It's so bad that I can't shut it down normally because it would take over 10 min (I've actually never waited to see exactly how long it would take). Thankfully I just found out about the three finger reset (volume up, camera, power), so I shouldn't have to pull the battery anymore, but it's still a problem.
I don't remember this happening before using custom roms. It happens with both DK28 roms I've tried - Bonsai and Viper. I believe it also occurred on the 2.1 Epic Experience, although I'm not sure. I guess I should try flashing to DK28 stock to see if that works, but it's a pain to set up everything each time. I figured I'd ask here to see if anyone else has had this problem and found a way to fix it. Also, I have a feeling this could be related to WiFi being turned on, but can't confirm yet.
My phone was stuttering yesterday.
But that was only after installing smartbench and using theonscreen keyboard.
However, since I've upgraded to dk28, the phone does take (relatively) forever to shutdown.
It'll go black but the bottom lights would still be on and then like a minute or two later it vibrates and actually cuts off
Sent from my SPH-D700 using XDA App
When my phone does this, it reminds me that I like to have SeePU installed. It's pretty useful in pointing out the apps that are hogging CPU and most likely slowing down your phone.
For me it's often Touchdown, and I kill it and things are back to normal.
I have found a few things that are useful. When I need to reboot my phone I use quick boot from the market. Works every time. In between I use fast reboot also from the market. Try them and see how they work.
Sent from my SPH-D700 using XDA App
Thanks for the app suggestions. I like the taskbar icons for SeePU. It's always been useful on my Mac (stats from iStat). Quick Boot makes things easier as well.
Next time my phone hangs, I'll see if some process is taking 100% CPU.
The phone hung again, and it seemed like something was taking 100% CPU, if the taskbar SeePU icon is to be trusted. I wasn't able to figure out what the culprit was though, because the phone pretty much stopped responding. Otherwise I would have loaded Android System Info to check.
can the epic 4g run this lag fix? if not, do we have any other ways to fix the lag?
http://forum.xda-developers.com/showthread.php?t=784691
edit: nvm
So I was able to view Android System Info while my phone was hanging, but it did now show any processes taking 100% CPU, although the total CPU usage was 100%. My guess then is that the Android 2.2 OS is buggy.
However, I did find people who said leaving USB debugging on would fix it, so I'm going to try that.
For reference:
http://forum.xda-developers.com/showthread.php?t=826507
http://androidforums.com/desire-hd-support-troubleshooting/244553-100-cpu.html#post2140890
My phone hasn't hung for a while, so apparently enabling USB debugging prevents the hang / lag / crash / 100% CPU. Weird but I'm glad it works
Now the only problem is kswapd0 eating CPU sometimes. I think this is caused by lack of memory, but I'm not sure what I can do about it.
Hi guys. I've been running the Android Stock Desire build from Cotulla for a few months now. Every once in a while I'd get a freeze, but then a battery in, and out would fix the problem (usually within the first try. sometimes I need to do this a few times, but no more than 5 times)
However, since last Friday my phone has been crashing like crazy! Constant crashes at random stages, and even reboots. Removing the battery also didnt guarantee a fix. I think I may have tried it about a hundred times, and Android just crashed at a random point in time during every boot. Eventually it booted, but since then it has crashed again! I figured that perhaps I should try a newer build.
I've decided to try out this build: [08.MAR.2011][CWM]TyphooN CyanogenMod 7 RC2 v2.5.4[2.3.3][A2SD/RAM][rafpigna OC 1.8]. Since I already have radio 2.15.50.14, these are the steps I've taken:
- Flash Task29 (ShaDrac version).
- Flash MAGLDR 1.13
- Flash ClockworkMod Recovery v1.3 135M System
- Flash CM7
Now, even during the various stages before flashing the CM7 rom, I would get freezes during the MAGLDR 1.13 bootscreen, or recovery won't load and I'll get stuck on the GOGOGO screen. Also, copying the zip file over in the MAGLDR mass storage mode won't work, and causes a freeze when I start the copy. Reset, or Battery removal seems to get me to the next step again.
Eventually I've flashed CM7, but now it freezes at the setup stage.
I'm starting to think maybe its not the various Android builds that I'm trying, but perhaps the problem lies somewhere else on the phone? Any ideas? Is my radio perhaps not the best one for the phone (even though its the latest)?
Any help will be much appreciated.
Regards,
XA83
Shameless bump (hope I'm not breaking any rules!)
I realize this post should have probably been under the CM7 thread as well, but I don't have access to that yet due to my low post count...
Could be:
*Wrong CWM Size, check in the rom thread for information
*leftover data, task 29 and reinstall everything
*Corrupted data on SD card, try booting without sd card to see if this is the case.
Thanks for the reply.
I've removed both the SD card and the SIM card. Phone seems to work flawlessly. Boots CM7 without a hitch. Next step I've added the SD card back, and formatted the card from the CM7 settings page. Still perfect.
I've tried it about 5 times now and every time the SIM card is not present, the phone works like a dream. Every time I put the SIM card in, CM7 crashes within the first few seconds of showing the home screen.
Finally, some progress!! Thanks again for the assistance. However, what dis this mean? Could this be related to the actual SIM card I'm using, or does it have to do with the part where it initiates the network connection and possibly the 3g connection?
*Also, just for information, I believe that I do have the correct CMW size. The build indicates "Flash ClockworkMod Recovery v1.3 135M System" which is the one I've flashed.
maybe reflash back to winmo then do evrything all overagain to android
I doubt it's an issue with the phone and its initiating with the sim card. Just replace the sim card
the SAGA continues
Hi Guys,
So since my last posts I have actually managed to get the phone running Typhoon's CM7 and its been working great... for a while.
I'm currently on version 3.0.4 and I still get:
1) Freezes,
2) Reboots,
3) SOD,
4) This happened today: phone cuts mid-phone call and makes a loud buzzing noise until I pull the battery.
I'm thinking more towards hardware problem at the moment, but please let me know what you think, and what I can do to debug the sitaution. Is there perhaps a hardware monitoring app that I can install that logs the whole system every 1 minute that I'll be able to pick something up.
I was also thinking maybe the phone overheats. As explained in my original post, whenever a crash or reboot occurs, it would sometimes not restart the first time round after pulling the battery out and putting it back in. Sometimes I get crashes even during the MAGLDR stage with "fatal hit" and strange things like that. Or even when I boot into CWM sometimes.
Now, to test this overheating, I've experimented with placing my phone in the fridge for 5 minutes after a crash. Thusfar I've done this 3 times, and every time I get a clean boot when I put the cold battery back in and then the phone functions perfectly for a while.
So, overheating, or do I perhaps need another radio? I'm out of ideas.
Any help will be much appreciated. The problem now is that I'm so used to android that I wont be able to go back to winmo or even blackberry
Regards,
XA83
it happens to my phone, and did on my previous HD2.
I've tried every build, task 29, every radio...new sd card....everything.
matt
Are there any apps we can run to test battery temp, cpu temp, cpu voltage or anything like that? I'm pretty effecient at debugging PC hardware issues, but when it comes to my phone I feel like I'm back in the stoneage!
Please help
I have tried over and over and over and over on this kind of issue.
most if the time was some unfinished coppied file which can;t runs properly on roms.
Try to asks ROM developer.
- SD partition : how many partititons?
- SD partitions : what kind of partitions, is it using etc 2/3/4, does it comes with swap etc?
- Installation method : does it needs to clear phone ROM with cwr ? what is the size?
HD2 usually I will go for 400M size
- config.txt settings for SD/NAND.
A proper guide could helps you on in the installations
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Possible solution, Thanks mate,
I changed the CPU speed to 1036 Mhz from stock 998 Mhz speeds and haven't had a Freeze yet,
before that The touch screen would freeze occasionaly when there was a lot of activity like in games such as fruit ninja ....
a Lower CPU speed such as 806 Mhz also seemed to do the trick ...
I don't understand why the Freezes would occur at stock speeds ...
I'll have to give it a few days though ...
Touchscreen Freezes
huggs said:
If you guys are having overheating problems resulting in freezes, you might want to use SETCPU and set a lower maximum frequency. Something like 800-900 mhz might keep your cpu's from getting too hot. Or maybe setting it to a different governor could help too, idk for sure.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Update:
Tried that with Interactive Governer, it still freezes on odd occasions, and the battery temp shows 33-36 Degrees Celcius on load when running games ...
i'm beginning to think the freeze is temperature related, as it never freezes while it's cool ...
I'm going to try running it with Smartass governer and see if it makes any difference ...
regards.
Yeah, there's been alot of HD2 owners who've had high-temp related freezes, one guy even went as far as to dissassemble his phone, re-bond the cpu to his mainboard, and add a home-made heat sync to prevent further overheating (successfully)
I just figured changing the cpu freq or governor might reduce cpu load, or increase efficiency, resulting in less overheating. But I feel pretty confident in saying that you guys' freezes are very likely coming from heat. It was even a problem in stock WinMo roms
Sent from my HTC HD2 using XDA App
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Touchscreen Freezes
Dylan Wilson said:
Yawp, I can barely charge my phone with the silicone case on anymore and that's in ac (the AC in my house is usually set at 74F) I have noticed I get freezes at 36C however I can go to the beach and get it up to 44C and it runs flawlessly
Click to expand...
Click to collapse
Thats wierd, I'd have thought that such a High Temp as 44 Degrees C would cause more freezes ....
regards.
i'm getting freezes from cyanogenmod android too. i recently restored my ROM to the original 2.13 and believed to have all previous settings related to android deleted.
freezing
i realy didnt undrestand what the exactly means of freeze, my phone freeze after change rom ,i can't use "TyphooN CyanogenMod " becuz my phone freeze at the android logo and it didnt any animation to boot !!!
i have hspl8 , radio 2.15.50 ,Recovery_130M_system_4M_cache[v3.0.2.4],mgldr 13.
i install windows then install android but it steel frezz, i can install just HyperDroid-GBX rom !!
it this problem fix with cpu temp ??
i get it in Refrigerator still feee !!
Temperature
Hi guys. It's definitely the overheating causing all the freezes. I've now succesfully "fixed" my phone 11/11 times by placing it in the freezer and then it works flawlessly for at least a day.
I'll try setCPU to try and lower the CPU frequency from stock and prevent heat issues.
However, ideally I'd like to return the phone to the manufacturer as a defective one! Only problem - how do you convince the 'genius' tech guy that the phone overheats. Last thing I want is to send the phone in, and only get it back after a few months with some response that they found nothing wrong.
Hence, I'm still looking for some sort of app to prove in a way that the overheating is causing crashes... At least in that case they may be more likely to issue a replacement immediately. Any ideas yet?
Regards,
XA83
Just a follow up:
My phone has been sent back to HTC. After a long wait, tech support said they replaced the hardware components - I'm assuming the phone mainboard.
I've reflashed CM7 since, and it hasn't crashed a single time!
Verdict: Random freezes was caused by hardware problems on the phone, and the crashes was most likely due to overheating of the components.
Regards,
XA83
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