I keep getting random lockups, at least more than once a day, and sometimes several reboots in a row.
It appears that i can happen almost any time, whether it be at a lock screen, while titanium is asking for root, or opening twitter or facebook, even the gmail app. It simply freezes, and requires me to long press the off button and reboot.
Unfortunately, i can't get adb via usb to work on the nook, so i can't get a reliable logcat.
Is this common? I have had two nook devices so far, tranferred the rom over through nandroid and have had lock ups on both, I am flashing regular cm7 nightlies now (emmc), but it occured using phiremod too.
Help?
I never had one, maybe I'm lucky
Have you tried fixing permissions in clockwork?
Sent from my LG Optimus V using Tapatalk
I am having the same problem. I loaded CM7 to my emmc yesterday and I have had it freeze on me a couple of times now. All have been random. I do have performance set to 1.1 and on demand gov set.
So I can just go to ROM manager to fix permissions? Hopefully that works.
EDIT**
Did not work. Was fine, then I uninstalled market updates, connected to wifi, opened the old market, searched for flash and it froze up. Any ideas?
EDIT 2**
uninstalled beautiful widgets (read that somewhere), so far no lockups (fingers crossed).
i had mine lock-up twice last night
i was in dolphinHD and i had just installed swype beta
i have only had 1 time that it has locked up before then in the last 1-2 months that i have had it.
im blaming swype, since i havent had the problem in the past
perhaps not your problem, if you dont have it installed.
I get lockups pretty regularly. It's irritating. Not sure what the cause is. I thought overclocking had something to do with it but everyone else is overclocked and this problem doesn't seem to be common.
How low do you have the voltage settings in tweaks? Having a voltage just barely too low for your CPU can cause a lot of weirdness. Also, it could be any one of the stepping voltage settings, not necessarily either the min/max frequency.
Folks, playing with the voltage settings in nook tweeks is not for the average user. These settings can really bork your nook. That's why you get a warning when you open those settings.
That being said, I have been running cm7 on eMMC for months and have never had a lockup. I am overclocked to 1200 mHz but have left the voltages alone.(cm7.1 nightly 160).
If you are running on eMMC,try fix permissions first. If that does not help, start looking at the apps you are running to determine if one of them might be the problem. Several people have reported issues running beautiful widgets. There are other apps that can cause issues. If you have good backups of all your apps, try removing apps one at a time. In the process, you might learn something about your system.
Worst case, reinstall cm7, wipe data, cache, and dalvic cache. Start over with a clean system and add your apps (apps only, not apps+data) one at a time. This will ensure that a possibly currupt data set was not causing the issue.
The key to a fast, well functioning nook is to start slowly and ensure each change works well before moving on to the next step.
While it's true I have more time than most to play (retired), my nook can run circles around most competitors but only because I took the time to set it up right the first time and I am not afraid to wipe everything and start over.
Sent from my NookColor using Tapatalk
I fixed permissions some time ago, seemed to help a bit, but i still get the odd lock up or two. I am running Swype and Beautiful widgets(anyone know a good alternative?)
I had been getting irritated by these these random locks up for a while. It seems that uninstalling beautiful widgets fixed the problem for me. I thought it might be that BW was trying to access the GPS, but it still locked up after disabling geo location in BW.
liam.lah said:
I fixed permissions some time ago, seemed to help a bit, but i still get the odd lock up or two. I am running Swype and Beautiful widgets(anyone know a good alternative?)
Click to expand...
Click to collapse
In case you're still interested, BeWeather is a great substitute for BW and FlexT9 in place of Swype.
Also, I had issues with lockups no matter my overclocking and formatting the eMMC and possibly reseating the SD card fixed it.
Related
I am currently running ViperROM(DK28) version 3.0.3. I followed all of the instructions for fixing GPS on 2.2 and then flashed to this ROM.
Whenever I remove the DRM services I notice 2 strange things that happen:
1. Quadrant is not able to complete, it gets stuck on the first test at the Video Decoding.
2. I'm unable to select a new ringtone notification in handcent, when I press OK for my selection it hangs and I have to FC it.
The reason I want to remove the DRM services is that it appears to negatively affect battery life. I notice an improvement when they are removed. If I restore the DRM services everything starts working good again.
Any ideas?
I wont flame you,but this has been discussed plenty,search please...Anyway,you cant remove any of the 3 without losing some funcionaliy.So the only thing you can do is disable the one that runs at boot,not uninstall.I have tried this tip that orked for a day,once you have a fresh rom installed,play some music,watch a ripped movie,change a ringtone and notification,then remove all 3 services with sdx app removal or any other method you like.But like I said this will not work for more then 2 days at most
Sent from my SPH-D700 using XDA App
You're not the only one running into this issue.
I ended up rooting my Epic to get rid of all the sprint bloatware and what-not. Everything seemed to be going smooth from the stock standpoint. I removed Samsung Media hub first. Rebooted the phone and noticed nothing bad. Played around with the setup like that for a few days with no problems.
I next got rid of both the DRM service .apk's that were still running even after I got rid of the media hub... and then the problems started. For the first couple days I noticed DRAMATICALLY IMPROVED battery life and EXTRAORDINARY performance so I imagined what I did was a good thing: WRONG! A few days later, I noticed that if I assigned a sound to a notification or a ringtone *from the SD card*, that it would not work. I couldn't play sounds anymore and instead whenever I went to adjust the volume with said notes/tones selected, the Sound_service would crash.
However, I'm the only person I knew before now who has reported this issue so I'm sure there's not a lot of hubob to fix it. Every Epic is built different. Same parts or not. It's a mass-manufactured phone and each one will have its own quirks. There's my 2 cents.
I just froze the apps when I rooted with Titanium Backup but I thought I did something wrong and figured out that sound from apps seems to trigger the software crashes. No point if fixing it now. Flash DI18 and get the EC05 update and/or get EB13.
dyehya said:
I just froze the apps when I rooted with Titanium Backup but I thought I did something wrong and figured out that sound from apps seems to trigger the software crashes. No point if fixing it now. Flash DI18 and get the EC05 update and/or get EB13.
Click to expand...
Click to collapse
So can anyone confirm that the EC05 fixes the DRM issue? Otherwise there's no point in upgrading. I saw the release thread on here. Hecka people already having problems with the EC05. To upgrade for the Sprint ID packs? Won't see me do it...
Just let it do its thing. The amount of functonality you lose removing it is not worth the minute amount of battery life you'll save.
stir fry a lot said:
Just let it do its thing. The amount of functonality you lose removing it is not worth the minute amount of battery life you'll save.
Click to expand...
Click to collapse
I have to disagree about the amount of battery life I'm saving being minute. When I had this damned DRM service running, I maybe got 10-12 hours with moderate usage. Without it running and now with SRF1.0.2 running (gets rid of IQ), plus SetCPU to (clocking 200-400 when screen off, undervolting 1.0-1.2 during usage) I'm getting a good 20 hours with heavy usage or I can go 2 days without charging if I only use texting.
I do actually remember getting a good bit more battery from deleting the DRM but at the end of the day I'd rather have my music files and apps work properly. I'm used to keeping a charger on me, its just the nature of owning a smart phone.
Yeah I'm with you on that one. Hopefully this will be one challenge [ACS] will be up to digging into.
I just tried stopping it in the running services menu and tested it on a few things with no issues. Doesn't take more than 15 seconds. I'll probably start incorporating it in to my TWS/Airplane mode routine (which just happens to need around 15 seconds supposedly) whenever I reboot.
That's what alot of other people have been saying too. I guess that's what I have to do.
Some threads on SDX about this say you can use some killers to stop it at bootup (personally I've always hated killers since Android 2.0, you don't need them anymore). As long as the .apk and .odex's are there. It's only when you uninstall or freeze it that you start to run into problems 1-3 days down the line.
I use Startup Auditor and it only kills it briefly. I've read all the arguments against Task Killer but I'm still a fan of it. Its especially useful to see what programs start up on their own and I do notice better performance after killing the ones that have no business being open. For everything else I just set it to ignore them.
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.
I am using CMYLXGO's NAND stock Desire HD build. Its great. However, I am having so many lag issues. I seem to be one of the few that is experiencing this with the build so i turn to some of you to see if you have had similar issues with your phones.
Problems:
1. when auto populating apps (like using installer, uninstaller, managing applications in the system tab) the phone will take forever to pull up all the apps , the screen will cut off (because the screen times out) and when I hit the home button or any button to cut the phone back on it stays black.
2. every action makes the cpu run high. adding a widget to the home screen (apps populating issue again), changing screens really fast and other assorted minor processed.
I have stopped auto sync
I do not use auto rotate any more
I do not have any rogue processes for the most part
I don't understand why I seem to have these lag issues. Everyone else talks about how fast and fluid the build is. I am under the impression that with the build NOT being run from the memory card NAND would add to speed. This is not happening for me. If anyone has any idea why this is happening. I am convinced it is something on my end but I don't know where to start. I am open to suggestions.
I have 2.15 radio, 16 gig class 2 memory card.
Hmmm, not sure but have you tried another ROM similar to see if it does the same? You can also go into MAGLDR and wipe dalvik cache. I used this ROM and all was good for me. I have sense been using this one which is also working very well.
http://forum.xda-developers.com/showthread.php?t=976384&page=1
every version of this build has been tried. That is the part that gets me. differnt kernels don't help either. i have even used SetCPU and overcloced to try and get through some of the lag. it works, but it is only when I play games not when I need to perform uninstall or widget selection for the home pages. I use SeePU which is ususally shows my cpu strain in the bright orange (for high use). most of my processes/actions raise the cpu use to high levels. I never really operate in a green (or low) usage level no matter what the action is. I would really like to capitalize on the speed NAND is supposed to offer.
Personally I would try something else (a totally different ROM) and see if you are still getting the same results, maybe even revert back to a windows mobile rom just to see if you are still getting the hang up. Last option would be to restore your phone to stock and start over, reinstall HSPL 2.08 new radio, etc...etc...
do you use an app killer?
XthelordinatorX said:
do you use an app killer?
Click to expand...
Click to collapse
yeah. but i did not at first. however, it is needed to stop some of the rogue processes. android.process.acore comes to mind.
I personally think this is one of the most stable builds around. I would rarely experience any lag, and if I did it would only last for seconds.
WorldWide60 said:
I personally think this is one of the most stable builds around. I would rarely experience any lag, and if I did it would only last for seconds.
Click to expand...
Click to collapse
Believe me, I know. Everything is working in his build. GPS, MMS, easy to install - the works. This is why i really want this to work properly so I can use it, without the hiccups, as my daily build. It has to be something with my phone but I can't figure out what it is yet....
On Cmylxgo's build, the first time I loaded it, I had the laggy and unresponsiveness you described for the same reasons. What I found is that rebooting the system to off/on a couple of times when I first loaded the build, addressed the first initial lag and unresponsiveness. After doing a couple of reboots, I found the build as smooth as everyone says it is. I am now trying the GL Core v11 kernel and it gives an extra 300 pts to the Quadrant Score and seems to be a bit quicker than the Rafpigna 1.8 kernel that comes with the build. Also, standby battery drain seems to be a bit better with the hourly peaks at half what I see with Rafpigna. If rebooting a couple of times doesn't do it for you, I know trying another build which may not have all the bells and whistles as Cmylxgo, but it is worth a try to see if it makes a difference. For me at least Cmylxgo's stock Desire (HD)2 build is much faster and smoother than any of the MDJ SD builds I was using.
I got my Nexus 7 in the first batch from Gamestop on the day of release. Initially, the performance was very fast, even faster than my Galaxy S2. However, after a couple of weeks now, it has become extremely slow. It is still stock, havent even rooted it. It is a 16gb model, and has close to 10gb free. I have tried clearing cache, closing all running applications, restarting but nothing really has worked.
The problem is almost every app is very slow. I get a notification of an email, i click on it and then stare at the white email screen for almost 10 sec before it opens up (the regular email app). It almost feels like a different device now than what i bought few weeks back. Other applications that run equally slow - Google Reader, Chrome, WSJ (this is perhaps the worst), Fluent News Reader. I am not much into games so havent tried a lot of them.Oh, and it is no match now to my Galaxy S2 Skyrocket or even HP Touchpad Cm9 that i got rid of last week.
I don't want to exchange it as it does not suffer from all the other problems being reported here (and am afraid that the new one might exhibit those). Please help.
Just a guess, but you most likely loaded something on it that is doing that. Check what you have installed on it, perhaps uninstalling some of the larger things to see if you can figure out what is holding it up.
Stock Nexus 7 Image
If cleaning the device does not work, you can always flash back to the stock image, which can be found on developers.google.com
Be sure to backup your apps and data!
or for the most simple of us...
Setting>Privicy>Factory reset.
That will remove any app that might be causing it.
Be warned tho, i think on this device it wipes the internal storage...
how is your WiFi signal?
seeing how almost every app require internet access, the delay could be it trying to connect.
Actually I thought that too... but my wireless signal is very strong in my small apartment and i have 30mbps line. I checked with speednet app and i am getting 13mpbs down, 4 mpbs up on nexus 7.
I am happy that this seems like my issue only - i will try to remove apps one by one to see if it helps or worst case, i will do a factory reset.
I was wondering if there are any known culprit apps responsible for memory leaks or something.
dilldoe said:
how is your WiFi signal?
seeing how almost every app require internet access, the delay could be it trying to connect.
Click to expand...
Click to collapse
I have noticed how mine has been very sluggish when there are apps upgrading in the background or installing, etc. Maybe turn off auto update for play store?
dbjunction said:
Actually I thought that too... but my wireless signal is very strong in my small apartment and i have 30mbps line. I checked with speednet app and i am getting 13mpbs down, 4 mpbs up on nexus 7.
I am happy that this seems like my issue only - i will try to remove apps one by one to see if it helps or worst case, i will do a factory reset.
I was wondering if there are any known culprit apps responsible for memory leaks or something.
Click to expand...
Click to collapse
If you send me a PM, I'll give you my email address and I can help you narrow it down by using screenshots of your app drawer.
install watchdog task manager lite, it monitors app in the background and tells you which one is causing problems.
have you tried turning off gps (location service) and see if hats the issue?
same thing
dbjunction said:
I got my Nexus 7 in the first batch from Gamestop on the day of release. Initially, the performance was very fast, even faster than my Galaxy S2. However, after a couple of weeks now, it has become extremely slow. It is still stock, havent even rooted it. It is a 16gb model, and has close to 10gb free. I have tried clearing cache, closing all running applications, restarting but nothing really has worked.
The problem is almost every app is very slow. I get a notification of an email, i click on it and then stare at the white email screen for almost 10 sec before it opens up (the regular email app). It almost feels like a different device now than what i bought few weeks back. Other applications that run equally slow - Google Reader, Chrome, WSJ (this is perhaps the worst), Fluent News Reader. I am not much into games so havent tried a lot of them.Oh, and it is no match now to my Galaxy S2 Skyrocket or even HP Touchpad Cm9 that i got rid of last week.
I don't want to exchange it as it does not suffer from all the other problems being reported here (and am afraid that the new one might exhibit those). Please help.
Click to expand...
Click to collapse
Just wanted you to know you aren't alone here...I have been seeing the same exact behavior on mine. I have started to uninstall apps one by one. I must be a bad app or something. If not I'm gonna wipe it and start over. It does feel disconcerting to go from easily the best tablet experience I have ever had to it becoming so sluggish.
i have the same problem, mine did the same thing on stock, ran great for a week or two, then became unbearably slow. so i rooted it and it wiped all data and the problem seemed to be fixed. then another week or two passed and its back to slow. i found out after testing with quadrant it has something to do with the i/o on the device, because the i/o score was abnormally lower than all the devices. putting a custom kernel will help, but still the i/o score is still quite low. i dont want to wipe all data again and if anybody knows a fix it would be greatly appreciated
nexus 7 has Kingston eMMC, it is better then the crummy Prime Hynix eMMC, but is eMMC none the less, not proper NAND flash/SSD
Well you could've had a bad app that is bogging your system down. A factory reset may be the only option so you can start fresh
Sent from my Google Nexus 7 using Tapatalk 2
Check the cache size of your Google Playbook or Magazine apps. It keeps downloading large files (400 mb) and may fill up your storage...causing it to slow down?
Having the same issue after owning it for two days. I really wanted to like this tablet,but between the sluggishness, and other various shortcomings, I'm going to be returning mine.
I deleted WSJ app and it seems to have helped a lot - not as fast as new, but a lot better. One thing which still irritates me is email app which just seems to be too slow...
Sorry to say but mine so fast I can't keep it down it trys to fly away lol
Sent from my Nexus 7 using Tapatalk 2
Same
has anyone been able to figure this out? I'm having the same problems and I've been running watchdog but there been no out of control process is on my device. I have wiped the device and the same thing just keeps happening after a little while it'll get very slow. it happens more often than not when there something in the background downloading are using the internet, but it's definitely not my connection because I've had no problems with any other devices.
Been getting similar behavior recently. cm10 euroskank, trinity 7.
Edit: in logcat, getting stuff like
I/Choreographer(10656): Skipped 30 frames! The application may be doing too much work on its main thread.
W/InputEventReceiver(10656): Attempted to finish an input event but the input event receiver has already been disposed.
I think I may have come across a solution. For me, the slowdowns were always connected to when something was downloading in the background, or when a process was using data, so I went through and turned off syncing on any non-essential Google services and other apps, and it seems to be working much better right now.
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