Database Users

Why does my phone shutoff?

Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.

If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD

patkin said:
Rooted my Hero and it doesn't matter which custom Rom I've tried(Fresh, Damage, others) my phone will shut off most of the time it goes into sleep. I don't know its off until I go to wake it up by hitting the end button. When I restore back to the stock Rom(still rooted) it works fine. I do a wipe and a Dalvick wipe prior to flashing. I'd like to get this figured out so I can use one of the nice Roms. Thanks.
Click to expand...
Click to collapse
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......

kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
I am not positive what A2SD is. I have a new 8MB SD card that came today. If I pop that in what will happen. Should it be partitioned? Thanks.

Chaid said:
WOW! You are the first person that has had the same problem I have...I was never able to resolve the issue. I used that bastard 2.1 test leak.......read my posts and what I went through.
http://forum.xda-developers.com/showthread.php?p=6268366#post6268366
My phone works fine now with gumbo 1.5, but I cant use any 2.1 roms or the problem comes back......
Click to expand...
Click to collapse
Thank God I thought I was the only one. I searched but didn't see your thread. Weird problem.

Same problem here too since the new leaked 2.1 test ruu from damaged. The only 2.1 Rom that works for my needs without rebooting every 3rd or 4th time I wake it using the end call/power button is Damagedtrev 2.01, the updated 2.05 Rom in his thread just makes my phone reboot as described above. I don't have a link to his thread, but it would be interesting to see if it worked on your phone too. Other's have claimed a battery shorting might be causing this issue, but I'm not buying that. I've looked at /proc/lastkmsg for clues, but nothing obvious there. I hope the official Sprint update doesn't have this bug or sprint will be giving me a new phone. /end rant

I can't seem to find Damagedtrev 2.01
So I can't test it.

Here's the link to the thread.
I cannot post links, because of some restrictions,but here is the last part of the url.
forum.xda-developers.com/showthread.php?t=653622
here's the link for the full rom
Oops cannot post link to rom on 4shared, look in the bottom of the first post in the thread for a link to the full rom of DamagedTrev_v201
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.

Ok, downloading......stay tuned.
I really hope this 2.1 ROM works.....I'm kinda sick of 1.5.
Edit:
P.S. I'm reading that there is a battery issue....do you have that?

kyouko said:
If you're running A2SD and you have the Dalvisk on a slow sd card you phone can reboot or shut off. Try moving it off of the SD
Click to expand...
Click to collapse
Hey good news. I put the new SD card in after backing up the other one, partitioned it and copied the files and folders back on then flashed ALOYSIUS and so far so good. I have woken it up about 10 times in a row. Looking good.
I had tried that perticular Rom before with no success.

Interesting.....I'm using the 2 gig sd card that came with the phone....I wonder if that is my problem?

Well it started again. This was right after setting my Gmail and POP3 mail accounts. It shut off on the first sleep after this. Hmmmmm.
I'm re-flashing now and not setting up the mail accounts. Will report back later.

Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.

reboot
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation

kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
It's a full reboot. The phone actually turns off when it goes into sleep. You don't know it's off until you hit the button to wake it up and the phone boots up.
Now for the good news. After re-flashing and not setting up the email accounts it was still shutting downconfused so I started looking elsewhere so I opened up what I thought was a likely culprit in Autokiller and none of the presets where selected so I picked Moderate and haven't had a shutdown since which has been over an hour. Fingers are crossed. I'll report back later.

That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.

patkin, dude, I felt the same...I gave up on 2.1.
download, wipe then flash Gumbo-1.5c-BARE-signed.zip after it reboots, download and flash Gumbo-Sense-signed.zip.
You flash Gumbo-Sense-signed.zip over the Gumbo-1.5. No need to wipe or anything, it just adds to the ROM. Fast as hell and works PERFECT.
http://www.4shared.com/file/217809392/5fcf1f5d/Gumbo-15c-BARE-signed.html
http://www.4shared.com/file/217811195/3afb5fcf/Gumbo-Sense-signed.html
Give it a shot....I think you will like it......let me know =)
Gumbo thred so you can read up if you like. http://forum.xda-developers.com/showthread.php?t=630221

Chaid said:
Waldo447
Please let us know if the rebooting stops for you. Maybe one of the devs could find where the problem is. Pretty please!! I could post any info needed.
Well, my friend. You were correct! full rom of DamagedTrev_v201 works on our phones for some strange reason. And updating his ROM caused the re-booting to start again. So whatever was changed from 2.0.1 to 2.0.5 is causing our particular problem. I'm not a dev by any means and don't know much about his stuff, but this is encouraging. Perhaps someone can figure out what it is?
I did notice that ALL the other 2.1 ROM's I have used that cause my phone to re-boot from sleep mode, is that when I hit the menu or power button to turn it on, the lights turn on, then reboot phone. With DamagedTrev_v201 that doesn't happen. The screen just pops up to unlock it.....don't know if that helps, it's just something I noticed.
Heres to crossing our fingers that someone can fix this!
P.S. I wiped and went back to Gumbo 1.5c as that 2.1 ROM was way to slow for me and I couldn't get bluetooth to work and audio would cut in and out.
Click to expand...
Click to collapse
Glad to see your rebooting issue was fixed with this rom even though you went back to gumbo 1.5. In my mind, this just confirms that it is not a battery issue. I never use bluetooth and have never experienced any audio loss with this rom, but apparently even people on the same hardware and firmware versions have different problems.
kwajr said:
i would like to know if its a full reboot or just a soft like where it hes to the sprint or boot animation
Click to expand...
Click to collapse
Full Reboot here too.
patkin said:
That's it I've wasted way too much time on this. Phone works great on the stock ROM. They must have planted some devious anti-flash widget in this phone. I'll leave it rooted for now.
Click to expand...
Click to collapse
Yeah, got my phone beginning of march 2010 and I also think there is something in the 2.1 test ruu or hardware that is keeping the phone from functioning properly with an altered 2.1 rom.

Just wanted to let people know what happened to resolve this. I went back to 1.5 then when 2.1 official came out last week I said what the heck if I can't enjoy a rooted custom 2.1 I'll try the official and guess what. Same problem as the other 2.1's.........phone shuts off randomly! Except this time they are replacing it with a new phone. Yeaaah! I'm probably going Evo now though since I found out I can get a new phone. Anyone need a new Hero?

I'm having the same problem.. One question. Does DarchDroid automatically move dalvik-cache to the sd

[Q] Phone Shuts Down Randomly

My phone will randomly shut down and will not power back on unless I pull the battery, I have 2 batteries and it happens with either one. It does not shut down while on charger/dock. I have wiped the phone multiple times with odin, I've used several different roms/kernals,same results every time. Just curious if anyone else has been experiencing this issue.

I've been experiencing this after I went to eb13 with the custom kernels that are out. But my.phone will either lockup and I have yo pull the battery or it will reboot itself. Never had what happens to u yet.
Sent From My Evo Killer!

This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha

nalewis89 said:
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
Click to expand...
Click to collapse
I'm averaging 10 times a day myself

Permanent sleep
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.

before updating to 2.2 - I did the DK28 and now the EB13 one - with 2.1 I would have my phone randomly reboot - I would be sitting there and here the music it makes when it starts up but I never turned it off?
other times it would just be turned off, but when I turn it back on the abttery is not low enough to cause it to turn off
all this went away with DK28 2.2 and hasnet happened since I installed EB13 2.2

This happeed to me the other morning. I wasn't able to boot until I reflashed the kernel. Twilight frozen btw.
Sent from my SPH-D700 using XDA Premium App

My first epic would randomly hard power off, even running stock ROMs. If you are running a stock ROM and seeing a hard power off at random, I suggest you go swap the phone. It's just broken.

Ive never had this problem and im on my first and only epic and ive had it since it came out,
Ive been very careful with my epic as it has been great to me, it hates me probaly tho for feeding it stuff while experimenting things that make it spit up FCS,
But my phone has been always working perfect, all the way back to d118.

CLazman said:
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
Click to expand...
Click to collapse
the buttons don't stay lit, i'm using twilight kernal right now but was happening with genocide kernal too, going back to eclair just to eliminate 2.2, ext4, etc.. to see if it's a hardware issue

First try
dk18 update.zip flash
Restored apps and data with my backup pro root
Random reboots, FC
Second try
Odin to dk18
Wipe x3
Restored apps and data with mybackup pro root
FC, music player force closing (doubletwist, stock and musicmod, poweramp worked though?), fc when trying to change ringtone or notification.
Started reading about others with the same issues and thought data backups were a reoccuring theme. Did a third try tonight and so far so good. Music players working, no force closings, keyboards working correctly, gps lock indoors. Its still early, problems might still popup, thought id share...
Latest froyotempt
Fresh backup with mybackup pro root
Wipe x3
odin eb13 prerooted (ctsy xda forum) same file from attempt 2. Did this x3 as well, read it in a thread somewhere...
backup apps only with mybackup pro root
All attempts were with genocide kernal.
So far so good, none of the previous bugs are apparent, so far... Those of you that are on the fence regarding doing the same, so far its worth the time.
Sent from my SPH-D700 using XDA App

I was thinking back-ups were part of the problem also, so I used odin and started all over from dl18 without restoring any data, same problem still occured

Still messing with my phone, everything that was broken seems to be fixed. Hopefully it stays this way...
Sent from my SPH-D700 using XDA App

That used to happened to me on eclair when I set my setcpu profiles too low when screen off. You wouldn't happen to be using setcpu would you?

actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800

I'll add to this thread. I seem to be having the same problem and I believe it started when I installed quantum rom... but I'm not sure. The symptoms i had were random reboots, where the screen would shut off and the 4 lights would stay on. Then I would have the sound of lost signal as if my phone rebooted and was starting over. Also, the most recent problem I get is my phone completely shuts off and I need to battery pull to get it to start up, and it loops on the splash screen of my rom. I have tried doing a complete odin wipe and not restoring anything and I believe it is still happening...

joedig52 said:
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
Click to expand...
Click to collapse
Any update?
Also, make sure the governor isn't "powersave". If you have 100-400MHz powersave governor, it still ONLY runs at the lowest speed (100MHz), even if it's 100-400MHz.

Still happening, not on powersave, doesn't matter what settings I have in set cpu. Did a hard reset back to 2.1 and it still happens, bringing it in for repair.

[Q] SyNthetic_aospX MR1-funny thing just happened

Should I reflash kernal or ROM or what?
At 11pm tonite my screen turned on by itself, it read 7:09pm with 51% battery. When I picked it up to check it the screen was locked up, after 5minutes of letting it sit screen still on did a battery pull. When I turned it back on is when I noticed it wasn't 7 o'clock but 11 showing 41% battery. This is the first time my phone has done this. Have gotten the upside down lock sreen from wake up, and a little hesitation when it rights itself but never this. Not sure if it is my phone or what, but decided to post this info incase it has happened to someody else.
SyNthetic_aospX 1.0.0-MR1 with patched kernal
good screen
"bad" eMMC chip
min freq=268
max freq=1036
gov=smartassV2 switched to this after patch of kernal from interactiveX
recov= 4ext
Going to stick wih this ROM, as my phone has isssues with ICS roms after about a week, this one has broken three weeks smooth as butter(fingers crossed).

GronHog said:
Should I reflash kernal or ROM or what?
At 11pm tonite my screen turned on by itself, it read 7:09pm with 51% battery. When I picked it up to check it the screen was locked up, after 5minutes of letting it sit screen still on did a battery pull. When I turned it back on is when I noticed it wasn't 7 o'clock but 11 showing 41% battery. This is the first time my phone has done this. Have gotten the upside down lock sreen from wake up, and a little hesitation when it rights itself but never this. Not sure if it is my phone or what, but decided to post this info incase it has happened to someody else.
SyNthetic_aospX 1.0.0-MR1 with patched kernal
good screen
"bad" eMMC chip
min freq=268
max freq=1036
gov=smartassV2 switched to this after patch of kernal from interactiveX
recov= 4ext
Going to stick wih this ROM, as my phone has isssues with ICS roms after about a week, this one has broken three weeks smooth as butter(fingers crossed).
Click to expand...
Click to collapse
Has it happened again since? If it has try and study your phone's behaviour whenever it happens (does it only happen when plugged in? and so on). Once you manage to get an idea of what actions cause it to happen, start up a logcat and replicate it and send it here. Also, if you've restored anything, downloaded a ton of apps, etc. try a clean install (w/ no restores, minimal apps, and so on) and see if it continues. I don't like to just leave things as "it's a hardware issue" because sometimes it can be difficult to tell.

Hasn't touched the phone for several hours, been on computer, when the incident happened. Had installed a flashlight app earlier in the day, TeslaLED. Also installed Google now M6 offline earlier in the week. Will keep an extra eye open to provide you with any info I can. No TB restore done between BR7 and MR1, as update was done OTA automatically with just ok'ing a cache wipe. The update went smooth, to me, from notification to download to flash and reboot on its own.
sent from Glacier under control of SyNthetic_aospX

again
Well it happened again, this time it didn't wait four hours before screen turn on and freeze, this time was about 15 minutes. Again was not doing anything with phone it was just siting there screen off. This time I have reflashed ROM to get back to original mint choc kernal, and will not reflash google now this time. How long can I run a logcat for? can it run for the day during normal use

GronHog said:
Well it happened again, this time it didn't wait four hours before screen turn on and freeze, this time was about 15 minutes. Again was not doing anything with phone it was just siting there screen off. This time I have reflashed ROM to get back to original mint choc kernal, and will not reflash google now this time. How long can I run a logcat for? can it run for the day during normal use
Click to expand...
Click to collapse
Whoops I meant I'll need a last_kmsg from after you pull the battery. That will tell me the last thing that happened before the battery pull. The op in my thread has a link that shows you how.
Sent from my MyTouch 4G using xda app-developers app

Been two days now, everything running as should, smooth. Reflashed Rom to get back to unpatched kernel, and did not reinstall gNOW. Later will install your patched kernel and keep an eye on it. Still getting the occasional inverted lockscreen, but that is no big deal, as this is the most stable ICS Rom that has run on my phone. All other ics Roms have barely made it past a week, cept Awesome's vanilla ics which hit the two week mark before giving me "unfortunately so an so has stopped working" and would cascade from there with errors. Will post up another logcat and kmsg log for you on the invert screen when I make happen again.
sent from Glacier under control of SyNthetic_aospX

Inverted lockscreen from yesterday, should be towards end of logcat=http://db.tt/YOl1UM78
A freeze up while using XDA app and following a link into Maxthon browser. Touched link in XDA auto launched browser then froze, let it sit there for a minute as back button did not kill app. Then phone rebooted itself, so found last_kmsg and saved it=http://db.tt/767lXrNH
Saved both files to dropbox
sent from Glacier under control of SyNthetic_aospX

Another last_kmsg log=http://db.tt/hTottjoq
Had just updated BeWeather pro and as weather icon was not showing in widget I did a force close to restart app, which I shouldn't of done, the phone froze. after couple of minutes pulled battery.
Had already flashed your overlay for the kernel. I am really thinking having the "bad eMMC" is causing me these issues, hardware issue.
sent from Glacier under control of SyNthetic_aospX

GronHog said:
Another last_kmsg log=http://db.tt/hTottjoq
Had just updated BeWeather pro and as weather icon was not showing in widget I did a force close to restart app, which I shouldn't of done, the phone froze. after couple of minutes pulled battery.
Had already flashed your overlay for the kernel. I am really thinking having the "bad eMMC" is causing me these issues, hardware issue.
sent from Glacier under control of SyNthetic_aospX
Click to expand...
Click to collapse
BeWeather was spamming that last logcat you gave me. That might be a part of the problem.

That thought popped into my head, don't know what the logcat was saying but seeing that much from BeWeather didn't look right. Thank you again for t the work you have put into this Rom.
sent from Glacier under control of SyNthetic_aospX

Self wake and freeze happen again, checked for last_kmsg there wasn't one, just last radio. Removed BeWeather widget, and unchecked auto update in the app this morning. I installed the kernel overlay last night, two days without overlay since reflash. Going to leave phone as is for now and run kernel log to see if it happens again.
sent from Glacier under control of SyNthetic_aospX

Phone just rebooted by itself, had kernel log running while it slept. Was also able to get last_kmsg log too. So here's a before and after self reboot.
KMSG= http://db.tt/u2tFjwTm
Last_kmsg= http://db.tt/E8F9ORUq
sent from Glacier under control of SyNthetic_aospX

GronHog said:
Phone just rebooted by itself, had kernel log running while it slept. Was also able to get last_kmsg log too. So here's a before and after self reboot.
KMSG= http://db.tt/u2tFjwTm
Last_kmsg= http://db.tt/E8F9ORUq
sent from Glacier under control of SyNthetic_aospX
Click to expand...
Click to collapse
Okay. Now bear with me on this one. Because it may seem odd... but try getting a new sim card (it's free) and see if it works. I noticed your logs were different but both had to do with ARM9 crashing due to WCDMA (both times with varying feedback after ARM9 crashing, but both keeping WCDMA common in the kmsg). I looked it up and came across THIS in the cyanogenmod forums. It worked for both of these guys and the other dude basically flipped out on the other because he thought he was dumb, but it worked and ended up looking like a jerk lol.

Another log= http://db.tt/0dfJ4nYJ
Thank you very much for even bothering with my issues. Not to long after my last post the phone froze with screen off and did battery pull. Was able get another last log. I have done a format of everything and reflashed. Installed a few apps and did not do titanium restore. Going to look into getting new sim. Again I thank you and bow to your superior intellect:beer:
Sent from my MyTouch 4G using xda app-developers app

[Q] PLEASE HELP my nexus 4' touchscreen stopped working

I am pretty knowledgeable concerning android phones and have never had an unfixable issue with one until today. My Nexus 4 will wake up by pressing the power button, but the touch screen is completely unresponsive. Please help
you need background info you say.....
* yes my phone is rooted
* no I haven't dropped it ever
* no I haven't exposed it to water or anything else that is abnormal ever
* yes I flashed a custom ROM (last night) .... AOKP jbmr1 from the AOKP website
* yes the MD5 matched
*yes I flashed a custom Kernel (last night) ......... Matrix 4.5 from the XDA website
* no I didn't have any issues afterwards and have even used the phone last night and half of today after flashing the ROM/Kernel with no issue until this
* yes I have flashed plenty of things prior all without incident
* yes I fully wiped prior to flashing
* yes I am completely sure I didn't drop the phone and/or expose it to anything specific
* yes I had a skin from BSE on the phone
* yes I removed said skin from the phone once I noticed an issue
Basically, I was using the phone as normal. Checked a text message. Placed the phone back into my jacket pocket. (fast forward 2 minutes). Heard the SMS notification sound. Pulled my phone out. Pressed the power button to wake the phone........and voila..........completely unresponsive to all forms of touch. Nothing abnormal and I haven't had any issues with the phone prior to this.
Would someone please help
Oh.......one last awful lazy piece of information. In flashing the newest AOKP and fully wiping before........I did not turn developer options on in the settings menu and I don't think USB debugging is checked...........SO........just using wugsfresh to solve my issues hasn't been so easy either. I guess that would have been a superb idea post flash but I am past that.....
Ive literally tried everything but nothing is working. I would gladly accept any and all suggestions. Please and thanks
-AK

AlphaKoi said:
I am pretty knowledgeable concerning android phones and have never had an unfixable issue with one until today. My Nexus 4 will wake up by pressing the power button, but the touch screen is completely unresponsive. Please help
you need background info you say.....
* yes my phone is rooted
* no I haven't dropped it ever
* no I haven't exposed it to water or anything else that is abnormal ever
* yes I flashed a custom ROM (last night) .... AOKP jbmr1 from the AOKP website
* yes the MD5 matched
*yes I flashed a custom Kernel (last night) ......... Matrix 4.5 from the XDA website
* no I didn't have any issues afterwards and have even used the phone last night and half of today after flashing the ROM/Kernel with no issue until this
* yes I have flashed plenty of things prior all without incident
* yes I fully wiped prior to flashing
* yes I am completely sure I didn't drop the phone and/or expose it to anything specific
* yes I had a skin from BSE on the phone
* yes I removed said skin from the phone once I noticed an issue
Basically, I was using the phone as normal. Checked a text message. Placed the phone back into my jacket pocket. (fast forward 2 minutes). Heard the SMS notification sound. Pulled my phone out. Pressed the power button to wake the phone........and voila..........completely unresponsive to all forms of touch. Nothing abnormal and I haven't had any issues with the phone prior to this.
Would someone please help
Oh.......one last awful lazy piece of information. In flashing the newest AOKP and fully wiping before........I did not turn developer options on in the settings menu and I don't think USB debugging is checked...........SO........just using wugsfresh to solve my issues hasn't been so easy either. I guess that would have been a superb idea post flash but I am past that.....
Ive literally tried everything but nothing is working. I would gladly accept any and all suggestions. Please and thanks
-AK
Click to expand...
Click to collapse
Power button works. Can you hard reboot(hold power for 10sec)? can you get into recovery and flash a different kernel? from looking through the dev section they have been some touchscreen lockups on Matr!x, faux, and bricked I think with some of the latest versions(newer commits). If you have an older Matr!x or other kernel, try flashing that from recovery.

eep2378 said:
Power button works. Can you hard reboot(hold power for 10sec)? can you get into recovery and flash a different kernel? from looking through the dev section they have been some touchscreen lockups on Matr!x, faux, and bricked I think with some of the latest versions(newer commits). If you have an older Matr!x or other kernel, try flashing that from recovery.
Click to expand...
Click to collapse
Lifesaver you are. Evidently I work too much and didn't even know you can hard reboot this phone like that. I haven't ever needed to. Hard rebooted it and it totally worked. I think I will leave this forum open for a bit and not change anything just to see if it is a kernel issue. I was thinking that may be it myself given the Nexus 7's issues with kernel stuff. I appreciate the assistance. Much thanks
FYI to anyone with similar issues or an issue that seems unfixable......this hard reboot would get you to recovery and I didn't need it but have a feeling it would have worked unless it was a hardware issue.
Thank you again man.
Ill check back in with this thread in a few days with updates

Are you, by any chance, running Matr1x's kernel?..

Dr. Hax said:
Are you, by any chance, running Matr1x's kernel?..
Click to expand...
Click to collapse
I am running Matrix 4.5 I just read the thread and saw something about S2W. was news to me.....I am a lazy themer and I work waaaay too much LOL

AlphaKoi said:
I am running Matrix 4.5 I just read the thread and saw something about S2W. was news to me.....I am a lazy themer and I work waaaay too much LOL
Click to expand...
Click to collapse
Same kernel, but with Brainmaster's Stock, and all day it's been fine, but in the last hour, the screen refused touch input twice, forcing a restart. The phone itself remained responsive in every other area (volume rocker, power button..)

I have changed to Faux123's most recent kernel (have used his kernels mostly) and will report back in time

eep2378 said:
Power button works. Can you hard reboot(hold power for 10sec)? can you get into recovery and flash a different kernel? from looking through the dev section they have been some touchscreen lockups on Matr!x, faux, and bricked I think with some of the latest versions(newer commits). If you have an older Matr!x or other kernel, try flashing that from recovery.
Click to expand...
Click to collapse
Had the similar issue with my Nexus 4 - Paranoid android ROM. Your post helped me to get out of that. Thanks!

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