Database Users

Working solution for random boot issues

So this morning I got a call from a friend who told me that his TF is running like crap after doing OTA upgrade to ICS.
We met up at school and I got to take a look at it. Yes, it was indeed running like crap and it even randomly rebooted while we were eating breakfast. He told me the random reboots were happening every 3-5 hours(that he could notice).
Here's what I did to fix it.
Removed his MicroSD card(not sure if necessary)
Shut down TF.
Hold [volume down] and [power] button together until you get into reset mode with 2 icons in the center of screen. Left icon is Wipe Data. Right icon is Cold boot. Right icon is selected by default.
Press [volume down] to highlight the LEFT ICON, which is Wipe Data.
Press [volume up] to confirm your selection
Go through the process.
Let your TF reboot.
Shut down TF again.
Hold [volume down] and [power] button together until you get into reset mode with 2 icons in the center of screen.
You need to do cold boot. It's already selected by default so just wait like 10 seconds and it will happen automatically. Press [volume up] if you don't want to wait.
Go through the process. Your TF will reboot afterwards.
Done.
It has been over 24 hours and his TF has been running smooth without any glitches or any random reboot. I told him to let me know immediately if a random reboot happens again.
This is simple to do. Worth trying unless you can't read English.
Edit: I didn't include this at first because I thought it would be common sense for everyone but it apparently isn't....
DO NOT JUST RESTORE ALL YOUR PREVIOUS APPS AND WIDGETS YOU HAD FROM HONEYCOMB. THAT DEFEATS THE ENTIRE PURPOSE OF DOING A RESET AND PREVENTING APP INCOMPATIBILITY.

thnx man for sharing . I actually tried every thing to solve this issue but no luck , I'll try your as sson as i go home .

This did indeed work for me as well. I tried this a couple days ago and I have yet to have any freezes or random reboots. I think that not restoring any backed up data, apps or settings is key to fixing the problem. I'm now very happy with ICS- burn in hell Honeycomb.

Shameful bump

When you switch from a version like HC. This is what you exactly should do!
I did this and never experienced random reboots.
My Transformer is running since three days and everything works fine!
Edit:
Another quick hint:
If you want to work with Google Docs, you have to disable Forced Hardware Rendering!

I see on forum the problem is google+
So I removed google+... Wait and see...
Sent from my Transformer TF101 using Tapatalk

billouetaudrey said:
I see on forum the problem is google+
So I removed google+... Wait and see...
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
.....lol, why post in this thread that you are not going to follow the advice of the Op?.......

Sorry to say but this is not working, already done this since the minute it was out and still have so now and then a hang boot
(random reboots that hangs on the boot)

Giving it a try
I am experiencing random reboots after ICS
Wiped transformer, cold booted, and installed the following.
Adobe Reader
Dog Catcher
updated G+ and GMail but have not run it.
Charging now, I will let you know.
Previously I had wiped it and reinstalled all, disabled syncing, disabled location info, adjusted wi-fi settings, and added CPU throttle control obviously none worked.

It might have helped some people, but it did not help me. Unless it was dogcatcher.
5 or so minutes after unhooking it from the charger, I tried to wake it. And it was unresponsive. Was only able to wake it by holding down the vol down and power button at the same time.
I will kill off Dogcatcher and try again but it is not looking so good.

JesterOC said:
It might have helped some people, but it did not help me. Unless it was dogcatcher.
5 or so minutes after unhooking it from the charger, I tried to wake it. And it was unresponsive. Was only able to wake it by holding down the vol down and power button at the same time.
I will kill off Dogcatcher and try again but it is not looking so good.
Click to expand...
Click to collapse
why are you installing dogcatcher? And this does work.. do it again. Don't install your apps.enusre it dos not lock up before you install anything.... If it locks up before you install any apps then call Asus. If not start installing one app at a time. Wait after each install. Ensure that its not doing it, once you are sure install Another ....rinse/repeat....

I installed dogcatcher because I needed something to listen to on the way in to work. I have uninstalled it. But I doubt that is the issue.
I have had these sorts of reboots on my Transformer until the third or fourth Honeycomb update. But eventually they fixed it. I suspected this would happen again.
Considering that dogcatcher one of the most popular podcast apps on the market I suspect that there are many people with no problems using it just fine.
But since I need a podcast listener to be able to use the device as I want to, does anyone without issues have a podcast listener that they use?

2 hours into the last experiment and it died again while sleeping.
So that about sums it up. This procedure might help with some issues Transformer's are having but not all.
Recap. Wiped, cold booted, gmail setup, G+ updated still equals failure.

I love how horndroid 'solved' this issue and then goes on the belittle people who are still having it as 'stupid', and probably their own fault. Horndroid, I appreciate your attempt to contribute, but your attitude and stabbing-in-the-dark protocol is not becoming nor helpful to anyone. Definitive statements pertaining to ONE TF101 device that you own are quite naive, there are several different models, and until you have personal access to each model version you should advertise your 'solutions' as "worked for ME", and understand if it doesn't work with others it isn't THEIR fault..this is not a blanket solution for every device's reboot problems. In fact, I am willing to bet the reboots being resolved by this method are of an entirely different genesis than the reboots that I and others are experiencing (hang-boots).

I hear what you are saying I have the reboot issue as well.
I did a reset before and after and only installed xda HD and ran it for 2 days and got 3 reboots so I did the cold boot and then it did it 2 more times that day. Earlier today I almost couldn't get out of the boot loop, so I wouldn't say its a app problem its something wrong with the firmware somewhere
Sent from my SGH-I897 using xda premium

Some aren't too lazy we just don't want to wipe data after every update. I think i have gotten 4? OTA updates and 2 of them screwed up deep sleep while docked. Guess what the first trouble shooting step was...wipe data. Guess what worked...the next OTA. I don't have time to read through all the different threads on the same subject but are people that flashed through cmw instead of ota having the same issue? My buddy went this route and has no issues.
Sent from my SAMSUNG-SGH-I997 using Tapatalk

Can't read horndroid's "advice", because I have him on ignore for trolling, and have done for ages. From the tone of other posts here, it seems the "solution" is to wipe; if that's actually the case, it's total BS.
I wiped immediately before upgrading to ICS, wiped again afterwards, and have put almost no programs back on. I am and always have been on stock firmware and unrooted. I had no problems with boot loops, no problems with lockups, and only extremely rare problems with spontaneous reboots using Honeycomb. With ICS, I have had all three problems in a matter of days, and the lockups / spontaneous reboots are fairly regular (1-2 times per day.)
This is a problem with the stock rom, not a user app problem.

knoxploration said:
Can't read horndroid's "advice", because I have him on ignore for trolling, and have done for ages. From the tone of other posts here, it seems the "solution" is to wipe; if that's actually the case, it's total BS.
I wiped immediately before upgrading to ICS, wiped again afterwards, and have put almost no programs back on. I am and always have been on stock firmware and unrooted. I had no problems with boot loops, no problems with lockups, and only extremely rare problems with spontaneous reboots using Honeycomb. With ICS, I have had all three problems in a matter of days, and the lockups / spontaneous reboots are fairly regular (1-2 times per day.)
This is a problem with the stock rom, not a user app problem.
Click to expand...
Click to collapse
I reported him for verbal abuse and foul language. His attitude is not helpful, and if I were a mod he'd be gone already to think long and hard about his conduct. Anyways, taken your advice and blocked him. It is obviously an issue with the ROM, I'm beginning to think it has something to do with deep sleep, others posited that it may be media scanner, maybe combination of both? Maybe these two events are trying to happen at once and it doesn't like it.. a stab in the dark at least..

luna_c666 said:
I reported him for verbal abuse and foul language. His attitude is not helpful, and if I were a mod he'd be gone already to think long and hard about his conduct. Anyways, taken your advice and blocked him. It is obviously an issue with the ROM, I'm beginning to think it has something to do with deep sleep, others posited that it may be media scanner, maybe combination of both? Maybe these two events are trying to happen at once and it doesn't like it.. a stab in the dark at least..
Click to expand...
Click to collapse
It's hilarious how you think YOUR problem is the only problem that everyone is experiencing.
For a lot of people, it was the app incompatibility that was causing them issues.
Obviously you think your problems are caused by something different, but that doesn't mean there are different problems caused by other reasons.
While all of you are speculating, at least I've posted a solution(even though it's merely doing a data wipe and cold boot, pretty much common sense) that has been proven to work for a lot of people. I've never claimed it will work for everyone; just those having problems due to app incompatibility.

I'm pretty sure this is an issue with the update itself and all these "fixes" are going to be pointless in a little while when an actual fix is released by Asus.

[Q] Random Reboots?

Hello everyone, my Nexus 7 (32gb Wi-Fi Model) has been randomly rebooting itself. I have unlocked the boot loader on it, but I have not installed any custom ROMs yet. I've mainly noticed it rebooting when I'm watching YouTube or using Google Chrome. Any idea on how to fix it? Thanks.

Just a test.

same here...
you know...
i would watch youtube, then put it down to go somewhere, when i come back to turn on screen ,
Quick tap of power button, no response... well not reboot but, shut down,
Im guessing it takes time from going back from deep sleep and i have no patience, or when i turn off the screen i push it a little bit too long...
Yours reboot?, like just WOah , rebooting device kind of thing...
unstable? overclocked?

Best app to help figure this out. Go into the options and check the top 3.LINK

Might be a shot in the dark but I had experienced reboots that was caused by HD Widgets (was acknowledged by them) and possibly Beautiful Widgets. uninstalling them cured my nexus 7 rebooting syndrome.

gokart2 said:
Best app to help figure this out. Go into the options and check the top 3.LINK
Click to expand...
Click to collapse
Currently giving this app a try. Hopefully this will shed some light on the situation. Thanks.

Jomari29 said:
same here...
you know...
i would watch youtube, then put it down to go somewhere, when i come back to turn on screen ,
Quick tap of power button, no response... well not reboot but, shut down,
Im guessing it takes time from going back from deep sleep and i have no patience, or when i turn off the screen i push it a little bit too long...
Yours reboot?, like just WOah , rebooting device kind of thing...
unstable? overclocked?
Click to expand...
Click to collapse
On my new 1 week old stock Nexus 7 32GB I've had a few random reboots too. Been reading around and trouble-shooting diagnosing the cause for it the past few days and my findings after viewing my debug log traces shows that the OS will reboot when it encounters a null pointer or invalid argument to a function call (or method call for you java programmers). When this error happens due to what seems to be any old app that was not developed for the new Android v4.2.x OS then the system will reboot itself to clear itself up. Ideally the new OS should be catching (detecting) when this invalid null argument or pointer situation occurs and gracefully clean up and terminate the offending app and the OS should just continue staying alive going along its merry way. But Google's new OS methods are not catching these sorts of errors it seems and thus the error is passed all the way up the chain of command to the main OS critical error handler which forces a reset and reboot. That's what is causing it. The solution I believe for now is to find all the old apps that you loaded onto the new device and by process of elimination remove them all. They are not 100% compatible to run on the new OS as of yet. Also report it to the app developer so that they can update and recompile their apps to work with the new v4.2.x java libs. That's my take and fix for now until Google developers add the try{} catch{} blocks to the proper places in their new OS implementation and release a new firmware to users.

Infobits said:
On my new 1 week old stock Nexus 7 32GB I've had a few random reboots too. Been reading around and trouble-shooting diagnosing the cause for it the past few days and my findings after viewing my debug log traces shows that the OS will reboot when it encounters a null pointer or invalid argument to a function call (or method call for you java programmers). When this error happens due to what seems to be any old app that was not developed for the new Android v4.2.x OS then the system will reboot itself to clear itself up. Ideally the new OS should be catching (detecting) when this invalid null argument or pointer situation occurs and gracefully clean up and terminate the offending app and the OS should just continue staying alive going along its merry way. But Google's new OS methods are not catching these sorts of errors it seems and thus the error is passed all the way up the chain of command to the main OS critical error handler which forces a reset and reboot. That's what is causing it. The solution I believe for now is to find all the old apps that you loaded onto the new device and by process of elimination remove them all. They are not 100% compatible to run on the new OS as of yet. Also report it to the app developer so that they can update and recompile their apps to work with the new v4.2.x java libs. That's my take and fix for now until Google developers add the try{} catch{} blocks to the proper places in their new OS implementation and release a new firmware to users.
Click to expand...
Click to collapse
Awesome! Thanks for the tip! I spent the last week slowly removing apps and re-installing them and I think I've solved the problem.

[FIX!]Bad Factory Images - Fix Reboots and Bootloops

I've been really interested in finding the cause of these reboots and bootloops that are affecting many people. Right out of the box, the tablet does 2 updates and somewhere things go south. The tablet starts rebooting at random intervals which can lead to further errors and bootloops.
Knowing a thing about Nexii devices, several people now have working tabs. The trick is reflashing the stock image or a CM rom.
My conclusion is that a big batch must have been flashed with a bad stock image. It takes a little know-how to manually reflash stock, but there are 1-Clicker PC apps that make it easier.
Anyone wanna write a little batch file that JUST automates reflashing stock image?
Also for those with rebooting or bootlooping N7s, just factory wiping isn't the fix because the files you are restoring are bad. People are wiping over and over with no better results.
Hope this info helps and I'll try to elaborate with some steps and links. The information is on XDA already, probably to some effect of such a title like "Stock Images".
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

Perhaps you can compare the checksums for all the files in the bad /system against the good /system using some scripts?

An interesting project, and more than Google/ASUS are (apparently) doing for us.
I'll help in any way I can...

I have no problems believing Google will patch this soon, but in the mean time people have rebooting Nexus 7s and eventually it will go into a bootloop which requires a wipe to fix.
If someone could make a quick little PC script to grab the stock and automate the fastboot flash commands. Just a temporarily permanent solution until Google patches it.
The problem is most people using stock probably don't realize it is rebooting. Mine would reboot when idle and I'd never know unless I checked uptime. So people are grabbing their tabs and finding it off because it rebooted, corrupted, bootloops, and runs till the battery dies.
Anyone using straight stock should check their uptime status in Settings. If your Uptime looks low, it is probably rebooting in the night or when idle. If you do nothing, you risk losing your data.
Its best to backup your data files, wipe, flash a stock image, and restore your data.
Sent from my Nexus 7 using XDA Premium 4 mobile app

If you are talking about the random reboots, for most people, that isn't about corrupted images. I thought you were talking about some bootloop problem.
Corrupted user data from those random reboots is a possibility which maybe is what you are saying, but that will only get fixed if you fix the random reboots, which I don't believe are caused by corrupted factory images for most people.
Anyway if it really is about bad factory images, one should be able to compare good and bad and isolate the differences.
If the differences can't be located then it puts to doubt whether the theory is correct or whether one isn't looking in the right places.

sfhub said:
If you are talking about the random reboots, for most people, that isn't about corrupted images. I thought you were talking about some bootloop problem.
Corrupted user data from those random reboots is a possibility which maybe is what you are saying, but that will only get fixed if you fix the random reboots, which I don't believe are caused by corrupted factory images for most people.
Anyway if it really is about bad factory images, one should be able to compare good and bad and isolate the differences.
If the differences can't be located then it puts to doubt whether the theory is correct or whether one isn't looking in the right places.
Click to expand...
Click to collapse
That's exactly what I'm saying. Bad images = reboots = bootloops = wipes = loss of data.
When it reboots 6 times a day, corrupted userdata is going to happen eventually.
I don't really care about "why" as much as just helping people find a solution to fix it while Google makes with a fix. The ONLY thing that fixes the reboot issue is to reflash the stock image. I'm just sharing my findings. This is what I did and with my suggestions, several others are finding success at fixing the reboots.
This fixes the reboots. Which fixes the random bootloops.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Put it this way, I've reflashed stock images from google published tgz file many times and never gotten rid of random reboots. They eventually come back if I use Chrome. If I don't use Chrome the reboots go away. This is for MY usage pattern. Chrome may not be a trigger for everyone and likely isn't even the root cause, however I have flashed the stock images and still get random reboots.
In over 3 weeks of folks experiencing random reboots, I doubt I am the only person to have flashed the stock images and still have been able to reproduce random reboots.
Personally I like to investigate and understand why something fixes a problem. I like to understand why some procedure would fix for one person but not the next.

I would suggest flashing a CM rom. Test. Then flash back to stock. Test.
Somewhere, something gets fixed.
I also found Next Browser. Its based off Android Browser and much faster with great swipe options. I have been using both simultaneously though without fail... but chrome is going to be uninstalled here soon. Unless you need Chrome for specific purposes, its much slower then others.
Sent from my Nexus 7 using XDA Premium 4 mobile app

FWIW running cm10.2 nightlies and only reboots are those I intentionally do to load up a new nightly. CM's so much better than stock.
Sent from my Nexus 7 using Tapatalk 4

It's unlikely that the stock factory image is the cause of random reboots.
I've flash cm10.2 nightly on mine and it still reboots every 20 minutes whenever WIFI is turned on.

wweeii said:
It's unlikely that the stock factory image is the cause of random reboots.
I've flash cm10.2 nightly on mine and it still reboots every 20 minutes whenever WIFI is turned on.
Click to expand...
Click to collapse
Hold off for the JSS15Q update which may improve your situations...granted its for the multitouch fix but they are reporting it may fix bootlooping, albeit sacrificing custom ROMs and root temporarily. All current ROMs use the (buggy) JSS15J firmware base so when Q hits it may be the fix needed. On another note I doubt it's bad factory images, I've only had 1 random reboot in the 10 days I've had my Nexus 7. That, granted, was a bootloop which I had to factory reset for but it hasn't happened again (touch wood.)

Yeah, this hopefully all disappears after today.
If you use stock and keep track of your uptime, you might notice your N7 is rebooting quite often. I never noticed it until I found the reboot thread, and checked. It said the uptime was like 5hrs but was on all day and night (I was working). I checked again in the morning and it had a 2 hr uptime. This went on for a while. I never actually caught it reboot. It would champ through games and hours of use with no problems, then reboot when idle.
The bootloop you had was probably from the reboot issue. It reboots frequent enough and shuts down during cleanup and corrupts user data.
I've been running CM and no reboot issues/bootloops at all. So whatever it is, it is with the stock rom. Thankfully this patch is sooner then later and hopefully fixes the Multitouch AND the reboots. I think the bootloops are the result of the resets.

player911 said:
Yeah, this hopefully all disappears after today.
If you use stock and keep track of your uptime, you might notice your N7 is rebooting quite often. I never noticed it until I found the reboot thread, and checked. It said the uptime was like 5hrs but was on all day and night (I was working). I checked again in the morning and it had a 2 hr uptime. This went on for a while. I never actually caught it reboot. It would champ through games and hours of use with no problems, then reboot when idle.
The bootloop you had was probably from the reboot issue. It reboots frequent enough and shuts down during cleanup and corrupts user data.
I've been running CM and no reboot issues/bootloops at all. So whatever it is, it is with the stock rom. Thankfully this patch is sooner then later and hopefully fixes the Multitouch AND the reboots. I think the bootloops are the result of the resets.
Click to expand...
Click to collapse
Surprisingly no, I used Reboot Logger and there were no random reboots after I did the factory reset, the uptime was continuous, since the bootloop and factory wipe no reboots were logged (that was 5 days ago).

SlimBean 4.3 Screen Wake on Standby

***TL;DR***I know now that 4.3 has this bug and it is something we will deal with. I understand the causes, but the problem is buried in the kernel vs the ROM, you can still read my semi adventure but I wanted to make this edit to save you time if you think I found an answer. Overall WIFI is a huge trigger for screen wakes along with shotty or chattery reception.***
First off SlimBean is pretty much the best ROM I've dealt with, so many options, faster then I've ever experienced, and sharp looking. I've been sharking around these forums for 2 years afraid to ever make a name and post due to my lack of knowledge. I love the search options for finding answers that this forum offers to visitors and I've surely used it to root an old AT&T Atrix 4G and now my current DD the Glacier. Now I feel as though I have a little bit of sense of what the heck I am doing and would like to share my path to figuring out how to make SlimBean 4.3 work for me. Who knows maybe this may help some people that have similar problems.
The problem::: On a SEMI clean install of [UNOFFICIAL]SlimBean 4.3 \\ Nightly \\ 22.08.2013 I noticed the Glacier in standby would suddenly illuminated with light although the screen was black. It was enough to light to catch my eyes as I was starting to fall asleep. I ignored it until morning then paid attention to it happening all day at work on and off constantly with the WIFI off and just mobile network, then mobile network off, reboot, nothing seemed to help and I couldn't bare the thought of the phone's screen just on all the time.
After reading threads about HTC's possibly having bad screen made from Taiwan I was in disbelief that it was the Hardware as coming from a year old version of MIUI, I never had a problem with the screen. Leading to the idea it must be a software issue / user issue in which I must of rushed the install of the ROM or it's a quirk in 4.3.
Prior to reinstalling the same ROM, I went with trying other similar ROM's finding [UNOFFICIAL] Carbon 4.3 \\ Nightly \\ 26.08.2013 literally was just released, also a super customizable fast ROM. Everything went smooth until I played music through headphones and the illuminated black screen was back. Now I'm definitely convinced it's the software so I move on to the source code of these ROM's ev_glacier-nightly-2013.08.27.
Ev_glacier-nightly-2013.08.27 Had no screen wakes after 2 hours idle on mobile network only. I wasn't in a location with WIFI as I believe a network with a lot of information chatter may be causing these standby black illumination wakes. Back to SLIM.
SUPER clean install. 1) Format SD card completely 2) fresh download w/ checked md5 of Slimbean 3) Full Wipe "wipe data factory reset" "wipe cache" 4) format/system & format/cache manually just in case 5) Clear Dalvik 6) And fix permissions since although I believe it has no point but it's just so easy to click just in case. Probably doing things double.
Here I am now.. Slimbean is back and nothing but the .zip has been installed along with updating Nova Launcher. I am waiting to reinstall GAPPS so I can first isolate this problem within the ROM itself. What I am noticing is on just mobile network 2g/3g/2g+3g I do not get the phantom wakes, but with WIFI on it so far is only happening about 20-30 seconds after the phone drops into Standby and at least now it's not long lasting, just a few screen black flashes and it's gone. The entire 20 minutes or so I've been typing this, keeping an eye on the screen it's been quiet. Progress is being made.
Now I have thoroughly read up on and used Better Battery Stats, Wakelock detector, and Greenify to help isolate problems prior to the clean install and am waiting to install any Google apps (play store) up until tomorrow so I can pay more attention to my phone and make sure it's just a WIFI wake lock causing the screen to illuminate black. Also was toying with the idea of installing 3.0.64 kernel. I'm curious as to see if it's not just the WIFI wake lock, but all wake locks that actually wake the screen. Once I'm ready to install the play store I'm going to start combing through the device using these fantastic guides and the aforementioned apps...
[GUIDE] The Total Newb's Guide to Wakelocks ::: [HOW TO] Fix Your Skyrocket's Battery Life ::: [GUIDE] Insanely Better Battery Life When Idle
My goal with this long post is to share my experience and also commended these developers on these awesome ROM's. I will post much shorter updates on how I fixed or found the exact problem. Mainly after searching I saw similar issues but not this direct "random black illuminated screen" problem. Thanks, and be sure to call me out on anything contained in this post.

the waiting game
At 9 hours from 100% charge, I'm at 40% battery with on 1.5 hours of screen time. I went through all my settings and disabled all sounds and haptic feed back. I have yet to install any apps and am running off the bare bones of just the ROM. WiFi & 4g mobile data were on all night with the screen flashing only if I used it then locked it with the power button.
Thinking I can live with these timeout 2-5 flashes, I start browsing the forum from my phone, put it down to get ready for work, look back at the phone as it is flashing black screen rampantly on it's own. Then it holds the black screen for a solid minute or two.
WiFi chatter wake lock must be doing this... Reboot to recovery - wipe dalvik - wipe cache - reboot phone. Now to test just 4g network, flash happens on first screen lock, but not as rampant. Hmmm. My next step will be to wait for full battery drain / charge then I want to try the kernal I mentioned above. 3.0.64 kernel.

Funny stuff
Realizing the Kernel I wanted to flash doesn't work with 4.3, I hope at least some of the 86 people that viewed my post got a laugh. Even the older version of SlimBean causes the random screen flashes and the screen on while charging even with the ROM settings for such off. WiFi seems to be the greatest cause. It's as if wakelocks are actually being represented as screen flashes since the kernel is so powerful.
I just don't want to use the CM ROM...
I'm going to dig around the forums further and type in different key words of my problem just to make sure I didn't miss someone already answering this question. Slim has all the functions I always wanted out of my droid and I'm dead set to make it work...or just live with screen flashes I guess.
Hope this is a comedy for someone.

only other link
I've found on the issue I have.
http://forum.xda-developers.com/showthread.php?t=1148057

Non-Stop ROMS
1) SlimBean 4.2 & 4.3 Both have this black screen flicker / black screen wake / black screen on while charging.
2) Carbon 4.3 Had it black screen on while listening to music / black screen constant while charging
3) Evolve 3.3 based of 4.3 seemed to work fine, but I wasn't a fan of the larger Icons and screen, similair to CM 4.3 so I didn't leave it long enough to test...
4.3 CM 4.3 black screen wake almost constant / black screen on while charging... also didn't last long to really test everything.
I am down the river if I want this to just go away. I have installed all these ROM on a completey clean formated SD card each time
I'm sticking with SlimBean as it has the looks and reacts like I expect my phone to. After doing some more searching and after a little time has passed for more 4.3 development there may be a kernel that will work better for me.
Oh here is another dead end I've found... http://forum.xda-developers.com/showthread.php?t=2185747&page=3 [KERNEL] Fixed the flickering screen problem,CM10,CM10.1,SENSE3.6 4.0 4.1 That goes no where...

wifi
WiFi is the biggest culprit for the random screen wakes. I've just been living with it since I dig the slimbean 4.3 ROM so much. Thought I might pop back on here to make some closure. I worked on removing some apk's from the already minimal gapps I installed and will soon start a separate thread on just that. As long as after searching I don't find the same info I figured out.

I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app

thanks for the response
N_otori0us_ said:
I think you've got the screen flicker bug.
Try flashing the .69 kernel, it claims to stop the flicker.
Also I know it's got something to do with the WiFi. I know a little about it though.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I see you all over the place when it comes to Glacier threads. Today at work I was searching around for a download link. I read through a ton of other ROMS threads hoping it was buried in the comments somewhere. So far I only turned up and old thread with a dead link and a couple of other threads you mentioning to other people to download the .69 KERNEL which I am guessing the full version number is 3.0.69, if it's not then there may be my first problem in finding the link...
*edit
this is the main thread I keep finding, you have so many other kernels on there
http://forum.xda-developers.com/showthread.php?p=43983635&highlight=+69#post43983635

I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app

reading about kernals
N_otori0us_ said:
I have a little idea about the screen flicker.
A member called zyGh0st told me. I've pmed Elgin but no response.
I'll pm coderzs too Lil.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
All the Kernels in the Glacier Bible page you have been keeping up seem old. I'm nervous to try one since they obviously seem like they won't work. I'm game to try what ever and post on here my progress so if anyone else stumbles upon the issue they can guide their way through it.
I've been searching "kernel 3.0.69", "kernels 4.3 roms", "jb rom kernel", "4.3 jb kernel", sometimes including the term "glacier" or "MT4G" with little to no luck between XDA and just google itself. I always just find ROMS that just mention the kernel but have no downloads.

Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app

K is for kernel
N_otori0us_ said:
Reading your older posts I see that youve already tried the kernel.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
I tried 3.0.64 kernel, not this mysterious .69 kernel you have mentioned. If you have a link or mirror of it I'll be glad to give it a go.
___________________________________________________________________________________________________
Found how you added the 2 kernels to the Bible page, I just flashed .64 again and I'm nothing but bootloops. I'll give .62 a chance since now I'll have to re-flash Slim.
___________________________________________________________________________________________________
make the double bootloops with either of those 2 kernels. I waited like 5 minutes, restarted the phone to see if it would boot and it just stayed on the slim splash screen. Of course I wiped dalvik and cache before installing either.

Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app

addiction
N_otori0us_ said:
Bottom of your 5th post
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
Oh yes, I head that already downloaded on the SD but the name CM_SENSE made me think it was a ROM not a kernel. The .66 kernel link is dead, but the .58 flashed & works but there is still the flicker on 4.22 SlimBean. 4.22 is so lame compared to 4.3. Even if there wasn't a flicker on 4.22 I don't think I'd keep it. Those big ICONS are just too much. I think that's why I like Carbon also. Anywho...
My addiction to messing with my phone is always in conflict with work. As if I don't have enough problem solving to deal with outside of cell phones.
I am going to try out the recovery I see in your signature, Recovery : 4EXT 1.0.0.5 RC8, just to see if it makes a difference. If you have the same phone without the same problem I must then eliminate the different variables to find the true problem. I found a "how to" and am either going to put in the time in a couple of hours or tonight. Then I'm going to start the rounds of testing ROMS / KERNELS all over again and I'll post my findings here.
I appreciate the back and forth, I actually got a can't thank anymore message because I used up my 8 yesterday~

Living with it
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!

tonyMEGAphone said:
I've been just living with the screen flash. The ROM is just to sweet to give up. At some point if there it a completely stable 4.3 I may upgrade.
On a regular work day I don't have any available WIFI, so I toggle it off then reboot the phone every morning. I usually get a random screen flash everytime I manually lock / turn the screen off and that's it. With WIFI on I get random flashes at random rates and for random lengths.
Playing music invokes these random black screen wakes also, I've stuck to my old blackberry as my MP3 player...I know that statement seems extemely wrong and against all sciences, but the 9780 bold works perfect as a music player. They had the long-press song skip in the volume button well before anyone added it to Android.
If ever I find the correct ROM / KERNEL combination, or someone else figures out the problem and I find it, I will post it here. This winter I am going to get more into understanding & compiling roms + digging through code so maybe I'll find it myself...ha!
Click to expand...
Click to collapse
Have fun man, and If you ever need help or guidance just tell us, we'll be here

Freeze on charge

I recently rooted and unlocked the bootloader on my Razr M and installed a nightly build of CyanogenMod (I like to live on the edge, I guess.) The first week or so with it was going great, no issues as far as I could tell.
Then I installed a social application that requires GPS location. I noticed that the first time after enabling this the phone would freeze when plugged in to charge. It would freeze to the point where hitting the wake up button wouldn't even activate the screen. Not always, but it has happened on several occasions. So now whenever I charge it (daily), I have to force reboot (hold down Up, Down, Power in that order.) Sometimes it'll even go through the process of "Optimizing Apps" as if they were all just installed.
Firstly, has anyone else experienced this? And if so, is there an "easy" workaround? I can't quite pinpoint how to reproduce the bug, though I've got 3 different Cleaning applications installed that are used daily. That in mind, it's unlikely this is a memory leak bug.
Second, if there's no "easy" workaround, when can one expect the next Stable build of CyanogenMod, if ever? Is it still in development? I see that the last Stable release for this phone was in 2013. It seems like I'll have to downgrade to an earlier build, but just want some input before I do it.
Thanks much in advance

Sounds like an issue with the app, not the ROM. You said yourself that the issues started AFTER installing that app. So, delete that app and report back. Also, a lot of those cleaner apps out there will just bork your phone if you're not careful.
Sent from my Nexus 5