I may have asked this before, but I'm not sure.
My A500 has a custom ROM on it, but its had this problem on multiple roms. I haven't tried on stock yet, but that's probably my next step. Anyways, here are my questions:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
When I first got it, I remember leaving my A500 in standby mode (it should automatically go into standby when you idle, right?) and being able to wake it by hitting the power button almost a day later. Now I can only do it for a few hours and then it won't come out of sleep. I'll have to turn it off by holding the power button down (even though there is no indication that it is turning off), then I can turn it on again. Sometimes my battery will be depleted, apparently indicating that it did not properly go into sleep mode?
chairhome said:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
Click to expand...
Click to collapse
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Moscow Desire said:
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
Click to expand...
Click to collapse
erica_renee said:
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Click to expand...
Click to collapse
Thanks to both of you. I needed reassurance that my tablet wasn't just messed up. I have a warranty on it and was thinking about getting it replaced and seeing how the new one behaved, but I'll try the suggestions. I'll probably try to reload my ROM after formatting and start with just the base apps and add one at a time as you suggested. If that doesn't work, I'll try a different kernel or ROM with a different kernel. I've already tried not using SetCPU to under/overclock, but that didn't work. Thanks again!
Another (relatively rare) issue is that the kernel you're using actually is flawed and fails to wake the GPU after it went to sleep (this may be a lot later than the device itself, depending on background services!). In this case using a different kernel will solve the issue (stock kernel is works).
EDIT: Posted at the same time... By all means try another kernel, this is a known evil with custom ones.
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
OK, before you take your tab back, personally, I wouldn't worry about it.
I have noticed, on some occassions, (yes, I do run stock rooted on occasion), that sometimes, the tab will get what we call the sleep of death. And usually, this may occur over a long period of time. Also, sometimes, I have to hit the pwr button several times, before it wakes.
+1 with the PP on overclocked kernels. This happens with the most recent ones.
Fortunately, System Tuner Pro, will increase MB voltages, so you don't get this.
If it does it again, and you are on stock, try to press the pwr button several times.
cool, thanks. I'll try this today.
chairhome said:
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
Click to expand...
Click to collapse
Mine has never worked on any rom with any configuration. Turning off wifi helps sometimes.
Related
Hello all,
Not sure if anyone has had this happened to them as well.
I am looking to root the phone and this is the only thing holding me back in fears that would be a hardware issue and then can't replace. But thing that it is software.
Here is what happens, like in the mourning I will wake up and check time on device by just pressing lock once and put down (has happened even with out doing that) then will see that alarm won't go off and try and wake the phone with power button and will get no response from the device just black screen and phone is getting warm.
I will actually have to remove and reinsert the battery to get to come back on.
Has been doing this since the update. I have tried to go an uninstall all the programs I don't use and don't have anything on it that my mytouch is not running and that device has no problems. Tried master resetting the device a few times.
I have reset from the recover wipe data option and from spl neither seemed to help
Problem only seems to happen after the phone has been on for over 100 hours.
Weird thing I took notice is after a master reset it redownloads all the apps again right away. Don't know how to stop that.
Right now mine is running the stock software the shipped version manually update to official touch update from sdcard.
So my question is there anyway to have the phone keep the logs since logcat is reset when the phone is restarted to find the problem. Or if this something you all have seen. Any ideas would be appreciated.
Hopefully you have a software-only problem... and I don't know how to prevent logcat from resetting after restarting the phone... but I can recommend one possible solution...
1. Get the stock Google/HTC signed EPE54B firmware... http://forum.xda-developers.com/showthread.php?t=642811
2. Rename it to PASSIMG.zip, copy it to the root of your SD card.
3. Reboot in bootloader and select Bootloader from the menu. Your phone should start scanning for the PASSIMG.zip and ask you to apply the firmware update...
And, yeah... no you won't void your warranty by doing this, since this is a stock signed original firmware....
I get this (or a similar) problem too. I'm not yet sure if it's a hardware or software problem, and am therefore avoiding rooting my phone until I'm sure.
I have noticed that this happens more often, or at least seems to be more likely, when the phone is cold... I've not had it happen during the day (when it's nice and warm in my pocket), but when I leave it on my night stand whilst sleeping, or for an extended period on my desk at home, it seems to freeze up then.
I'm an electrical engineer and suspect that this problem may be due to silicon right on the edge of it's qualification range (similar to how some people are able to overclock to 1.2 GHz stably, mine is unstable even at 1 GHz... :-( ), I think my device is unstable at 998 MHz at whatever voltage it's running at currently (looks like Qualcomm changed the recommended voltage from 1.25 to 1.275 and finally to 1.3V over the course of early 2010).
See some of these commit comments for more details:
https://www.codeaurora.org/gitweb/q...it;h=6ede969b4418be5f8f2bd128d0cd4fbd3fd97e72
https://www.codeaurora.org/gitweb/q...it;h=ff61966464a2a2d2da36c0194d326370d3c3caeb
https://www.codeaurora.org/gitweb/q...it;h=a129aec2ec8b0b8ef9943e437415073620f15678
Based on them, I would guess we can expect more stability in the FroYo release (assuming it's using the 2.6.32 kernel, and is coming soon). In which case I'll wait.
I will try that rom next. In my tinkering I went back to erd and let it auto update to ere on its own. and will see how that does. If it fails again I will try the other rom. I can still revert back from that to erd if I want later right?
everything except the radio... i believe the radio can only be downgraded on an unlocked phone... so i've heard...
It happen to one of my nexus one too, the other one never hangs. It happen mostly when i'm charging on the dock with screen on.
I address this problem with HTC once, and they told me to try remove the micro sd card and see if it happen again. So i switch a newer sd into the phone and its running fine waiting to see if it hangs again if it does, HTC say will they come send a carrier over to fetch the phone to check it.
Running fine for 4 days already, just weird tho how can a sd card cause this?
Could also be a low memory issue with the stock ROM. My wife's does that until I kill a bunch of background apps. I look at the available memory and it's at 13MB. She also hasn't reboot her phone in weeks...so that's probably why it was low on memory. I guess the internal Android task killer doesn't do it's job very well!
Anyone have this problem? My iconia a500 constantly wakes itself up for no reason. Doesn't matter what ROM or kernel, it happens all the time and destroys my battery life because the screen will stay on overnight. I'm afraid it might be a hardware problem :/
Sent from my Nexus S 4G using xda premium
No one else has this issue? :/
Sent from my Nexus S 4G using xda premium
Shouldn't be a hardware issue, as something (an app) is causing the display to wake. Think about it for a minute. When hardware fails, it doesn't work, or it gets warm enough, then fails.
So something is telling the display to come on.
Do you have a 500 or a 501?
Which rom/kernel combo?
I'll give a few pieces of advice.
1. Check the display time-out in the settings. Make sure it's not set to "never"
2. Set your wireless to sleep.
3. Uninstall any utility apps (task managers, battery monitors, display enhancements, etc) Anything that "might" cause the display to become active.
4. Turn off notifications and sync's. You can do this for a day and see what happens.
If that doesn't fix the issue, it could also be the fact that the rom wasn't flashed properly. Before you get into a defensive posture let me explain.
When we flash multiple roms/kernels, eventually some code doesn't get wiped fully by just doing the normal 3 wipes. Sure, half the time we can get away with it, depending on what rom we decide to flash.
The next thing we know, some strange things start happening. Usually small things. Like messages that say to insert sim card on a 500 (leftover build.prop from a previous rom). GPS is weak, wifi disconnects, etc.
The proper way to fully get rid of everything is;
1. Do the 3 normal wipes (user, data, and dalvik)
2. Go to Mounts, and do a format on those 3, and also Flexrom.
This ensures there is absolutely nothing internal left. Clean as a whistle.
Then and only then, go back to the main menu, and flash the rom.
As with kernels, never flash a rom and the kernel at the same time. Always reboot after the rom flash, do your setup, then reboot and flash the kernel. And make sure the kernel is fully compatible with the rom.
As I said, whatever it is, it's software related. Install minimum apps, and run it for awhile. Then a couple more apps, till you figure out what causes the display to wake and stay active.
brokentoaster24 said:
Anyone have this problem? My iconia a500 constantly wakes itself up for no reason. Doesn't matter what ROM or kernel, it happens all the time and destroys my battery life because the screen will stay on overnight. I'm afraid it might be a hardware problem :/
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I remember reading something about this from ACER in one of their release notes. They patched it. Because you're running a custom ROM, the patch must be in the boot or something else that typically isn't touched by a custom ROM.
TD
Yesterday I got the ICS update via Kies.
Saw that my CPU was not going into deep sleep.
BetterBatteryStats showed the problem
fuel_alerted is forcing a kernel wakelock.
I tried searching the forums, and there are some fixes in some custom kernels.
However, I could not find out what exactly is fuel_alerted, why does this happen, and does it happen on all phones?
I believe taking out battery and putting it back in should fix the problem. Right?
Will it come again?
Whats the root cause of this problem?
I powered off, removed battery, and then put it in, powered up the phone. Now phone is going into deep sleep.
But I still cant figure out what is fuel_alerted, and whats the issue, why does it come?
i dont have this issue. i flash DDLP8 india yesterday.
tsk1979 said:
I powered off, removed battery, and then put it in, powered up the phone. Now phone is going into deep sleep.
But I still cant figure out what is fuel_alerted, and whats the issue, why does it come?
Click to expand...
Click to collapse
I had this on LPY, Did same as u did and its gone. Now yesterday i flashed LP8, its not yet there. Let us know if it comes again.
weng_cas said:
i dont have this issue. i flash DDLP8 india yesterday.
Click to expand...
Click to collapse
All ICS roms have this issue. You just have not hit it. Its a bug in the kernel. Somebody has fixed it in an open source code. I googled quite a bit, and also found the offending function
https://github.com/CyanogenMod/samsung-kernel-c1/commit/5f6d8422629002c530dcf30891c241fe3ee2e0ab
katyarevishal said:
I had this on LPY, Did same as u did and its gone. Now yesterday i flashed LP8, its not yet there. Let us know if it comes again.
Click to expand...
Click to collapse
Will do
Here is what the bug report says
"However, when the SOC starts rising, the wakelock was only destroyed"
Now what is SOC referring to? System on Chip? Does not make any sense. Can somebody look at the github page?
Try disabling the power saving mode and restarting.
Don't use power saving mode. I've only seen this Wakelock after I've checked the powersaving option.
Ironic. But true.
Sent from my GT-N7000 using XDA Premium HD app
SoC = State of Charge in this case.
It's another classic case of Samsung failing to fix well documented and fixed bugs. Not as severe as the eMMC brick bug (documented since before November by Google during Galaxy Nexus development), but still - documented and fixed by the community for many months.
I fixed this in I777 Gingerbread kernels back in October, I9100 kernel developers pulled in the fix fairly quickly. Despite the bug being documented and fixed by the community for months, it is still present in all of Samsung's ICS kernels.
It has been fixed in the CM9 kernel since the day I9100 Update4 sources were released.
It's also fixed in DAFUQ. (However a lot of other stuff is currently broken in DAFUQ.)
No need to pull the battery when you encounter it, just reboot. Rebooting is the only fix without flashing a kernel that has the bug fixed.
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
tsk1979 said:
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
Click to expand...
Click to collapse
I just noticed this param, I am not sure it was there before (I am on LPY)
Rebooting and it's still there!
Doing Power off now..
tsk1979 said:
Thanks entropy!
Actually reboot did not make the bug go away. I had to pull out battery.
I am on DDLP8(India ICS)
I guess, with kernel source released, we should see everything like FM etc., supported in CM9. I will move to CM9 then
Click to expand...
Click to collapse
No - FM is a userspace issue, as is MHL.
For CM9, the only things the source release affects are:
1) Speakerphone (already fixed)
2) Possibly a more reliable wifi driver (although CM9 may just kangbang pawitp's great work on the Aries kernels)
3) Backporting some performance features such as improved busfreq control
Entropy512 said:
SoC = State of Charge in this case.
It's another classic case of Samsung failing to fix well documented and fixed bugs. Not as severe as the eMMC brick bug (documented since before November by Google during Galaxy Nexus development), but still - documented and fixed by the community for many months...
...No need to pull the battery when you encounter it, just reboot. Rebooting is the only fix without flashing a kernel that has the bug fixed.
Click to expand...
Click to collapse
Found this thread after seeing this causing wakelocks in my i9100 S2. Thanks for the explanation.
However, rebooting - as well as powering off and switching on again still did not eradicate the fuel_alert problem and CPU Spy was showing my phone couldn't enter deep sleep.
Only after pulling out battery (and waiting for 1 minute for good measure) and powering up again did the bug go. CPU spy then reported my phone had entered deep sleep and the fuel_alerted entry was no longer showing in BetterBatteryStats.
Remove the battery and wait for 1 minute and reboot the phone , it will fix the problem.
To avoid it from happening again , remember to wake and unlock the phone every time before removing the phone from charging(Data cable & charger both).
I never unlock the phone before plugging and unplugging, and inspite of that problem is not reappearing.
So it may be completely random. I looked at the github code, but somehow could not figure out any relation to lock/unlock while charging.
It happened to me once and i removed the battery for 15 mins and it disappeared. But today it happened again. I do have power saving mode enabled but i dont want to again and again remove the battery to fix it. I charge my phone by turning it off and once its charged i remove the charger, let the display go off and then only turn on the phone. Do i need to turn on the phone before i remove the charger?
I think the power save mode has something to do with it. I didn't check the battery history before turning it on though but after a few days the Note didn't last 12 hours with only 1 hour of usage. The processor was awake even when the screen was off.
As suggested here I removed the battery for a few mins. I reinstalled the battery and charged it while the phone was still off. After a few hours of charging I turned the phone on and date/time defaulted to base time as expected. I observed battery behavior for a few days and the processor is now sleeping when the display is off and only wakes up every once in a while maybe to sync. BTW I only have Gmail sync on everything else is set to manual. And I haven't touched the power save option since
i'm chasing a battery drain issue.
i can leave my phone at idle even after a reboot and still even after hours of idle it never goes to deep sleep and shows 8 hours in the 384 mhz.
i have deleted apps, factory reset, flashed stock kernel, flashed factory image, NOT loaded the apps from google restore and still it comes up.
i have tried using better battery stats and all it shows is SUSPEND BACK OFF WIFI..
what gives? how do people use BBB when it is never specific with what is causing things, its so vague and generic.
my device SHOULD go into deep sleep if i reboot and leave it at idle right?
nothing?
I just want to know how so many people swear by BBB when all it ever does for me is show generic wake locks and not which specific apps are contributing to those wake locks.
Hi! I just wanted to tell you that this has been haunting me as well during the last 5 days.
Before, I had tremendously good deep sleep. But now I have the same problem. I have tried different kernels, reinstall CM. It must be app related.
Sent from my Nexus 4 using xda premium
nextelbuddy said:
nothing?
I just want to know how so many people swear by BBB when all it ever does for me is show generic wake locks and not which specific apps are contributing to those wake locks.
Click to expand...
Click to collapse
There are 2 fields there. Kernel wakelocks and partial wakelocks.
Kernel ones are those that are held by the OS. Partial are the ones that are held by apps. You can find out which apps are consuming battery by looking into it.
wifi wakelock is held by the OS and not an app. So you'll see it mentioned under kernel wakelocks. Most likely your wifi router isn't allowing your phone to sleep. Try disabling wifi and see if you still get wakelocks.
Sent from my Nexus 4
thanks guys
i tracked it down manually to the app called ULTIMATE ROTATION and ULTIMATE ROTATION LICENSE
as soon as i removed those apps no more wake locks and i can now deep sleep properly.
posted a message on the play store but no response yet
i have the same problem after i reflashed my rom! i didnt have this issue b4! im using the exact same rom with the exact same apps, i just restored my backup... im not sure wat is causing the problem... i tried everything with no luck :S
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