Hello, I have an i605 and have been using CM12 since it has been released and really like it as a daily driver. I have tried many different ROM's all using CM12 as a base and all, without question have had this same issue.
At least once a day (time of day varies) I will pick up my phone and turn on the screen (which button I use makes no difference) and it will be black, I see that the backlight is on but the screen is black. The home button does nothing, swiping left or right does nothing, the status bar shows up just fine, I can swipe down and see notifications and access the quick launch but if I try to access anything, it just returns me to a black screen. The only way I can get out of it is to reboot.
I am currently running the June 16 nightly with the kernel that is bundled with it. I did try a difference kernel before (I cannot think of the name right now) but the problem remained.
I have tried googling this issue to no avail and I haven't seen anything here on the forums.
Any help would be greatly appreciated.
Can you access to the recovery mod ?
Related
OK, so I successfully installed the ROM. It works fine and all until I actually use openscript on the terminal. For example, I wanted to change CPU frequency. I changed it, quit the terminal, and checked the frequency in system information. It was successful. But After about a minute my screen suddenly locked and here is the current situation. The locking screen works fine (I had the pattern lock), I can even open emergency calls. But when I unlock it, the only thing I see is the notification bar (which works btw, clock, wifi , all the icons are there, I can slide it down and up and so on). Everything else is just black. The buttons work - I can quit the notification tab buy clicking back or home or something like that. But I dont see my home screen, menu, buttons - nothing. I can lock it again, and it works fine again in the lock screen but afterwards same black screen again. Reboot does not work.
So I reinstalled the rom. Immediately after installing changed the frequency and waited for a bit. Everything was fine. I installed all the crap I usually have and kept using the phone. But the next day, I got annoyed by the music player and decided to change it again via the openscript. Same thing happened. And this is where I am stuck right now (actually this is already the third time I have this problem in 3 days and it's my third reinstall of the rom, but the first one also happened after using openscript to change frequency.)
So is there a way to fix this without reinstalling the rom again, cause I've customized the **** out of it and I don't wanna do it again. If no, how can I prevent this in the future?
P.S. If this helps, when rebooting, I hear the sound before the android splash screen which is sometimes skipped and sometimes shown for an unusually short time.
P.P.S. Also, I have the apps2sd flashed.
Any help would be appreciated.
Thanks.
Got same problem
Hi,
Even I got same problem when I tried to change boot animation. Just blank screen.
But i realised it is due to, launcher app is not initiated. So tried a trick which worked indeed
Trick is when u are in a blank screen, click "HOME" button which will pop u up the list of launchers u have. Click One of them though they r not visible
Voilaa!!! Your screen is back
Regards,
Murali
Hi all
I've done something stupid to my phone.
Been fiddling with auto-brightness settings, and now the screen won't switch on.
Got CyanogenMod 7.1 stable for the HTC Desire HD, had it loaded for close to a month(been enjoying it).
I've rebooted, pulled battery, SD card, SIM, everything. On boot the display shows the HTC logo, and the CyanogenMod BootScreen, immediately after that, I see the screen off animation, where it would normally go to homescreen. I know the phone is still on, the notification light is flashing, and via USB I can get screenshots of my lockscreen(widgetlocker).
When I click the power button a few times, intervals of ~3 seconds, the screen flashes just quick enough to see my lockscreen, but it really is a split second flash.
I've got Juice Defender Beta, I think the latest, used it for a couple weeks. Today I wanted to test the auto brightness settings it "supports"(beta feature). I noticed no changes, so I skipped over to the custom display settings for cyanogenmod, under Settings/Cyanogen .../display/Auto Brightness.
I fiddled there, as I've so done before, couldn't find the right balance , so I left my phone for a bit, it clicked the screen off, now screen is 'stuck' off.
I understand that this may be Juice Defender's doing, but since I was fiddling with cyanogen settings too, I'm posting here and to JD support, just in case. There might be a conflict.
Anyone know how I would debug this through ADB? I would really like to disable auto-brightness, that would probably eliminate Cyanogen from causing this (as the settings I changed related to Auto-Bright).
I tried this, no luck.
Otherwise, how to reset Juice Defender settings via ADB, or through a USB screenview... thing?
I've got a NANDroid backup, but its a little dusty, I've done a lot of customisation and such since, I'd prefer to avoid using it.
This is, of course, urgent. I can't use my phone at all, so any help is greatly appreciated.
EDIT: Solved it. Booted into safe mode, disabled what I changed, sorted. Still no idea what caused it, but ja, I fixed it. Android has a safe mode? Good to know...
I don't know if this is the right area but here it goes.
The area where the software buttons are located are not being affected by Twilight anymore. I don't know if the problem is with Twilight per se or something else, but I do know the problem appeared right after I tried using Muzei, I was messing around with it, seemed like a good app but I was enjoying the wallpaper I was previously using, but when I went back to it this glitch appeared, I'll link a screenshot of the phone that better illustrates it.
http://imgur.com/chnlK2K
On the lock screen it seems to work without problems:
http://imgur.com/CBWPBHI,uuy5ao4#1
I know it's a minor bug but it's one of those little things that can be very annoying.
I've already tried clearing the data both from Twilight and Muzei, and removing and re-installing them, did not work.
I don't know if it matters but I messed around with the blur and dim settings on Muzei that first time I used it, although since clearing the data and re-installing it they are back to default. Also, the problem persists with other wallpapers, even with the Muzei ones.
Also, using a Motorola Moto G with KitKat, not rooted and stock rom and launcher.
Anyone ?
I really wish I wouldn't have to make a factory reset just because of this but it's really annoying.
Twilight has never covered the software buttons for me on my Moto G. I switched to EasyEyes and it seems to work fine, the brightness of the buttons doesn't seem to change but at least it doesn't look nearly as wrong anymore.
I've had the same thing appear today. Bar at bottom of screen with software buttons undimmed by twilight. No new apps installed & not using Muzei. Phone is Oneplus 2.
I'm at the end of my rope with this. Several days ago my s5 started refusing to drop down the notification panel and the quick settings menu. I'm running stock rooted kitkat 4.4.2. I did a factory reset, disabled xposed (in case some notification bar mod was causing this even though I hadn't changed my xposed settings for months), got a replacement SIM card, went back to an earlier version of google, and now sometimes it will work for a whole day and then stop responding again. I took out the external SD card and it still does it. I uninstalled anything new (not much) that had recently been installed. I have been using Nova as my launcher, so I tried going back to just Touchwiz, but no change.
It's not just the drop down screens, when I open Titanium Backup and try to use the "clear" or "menu" buttons at the top of the screen, they don't respond either. It's like something is freezing the top half inch of the screen (I measured it in frustration).
I went into the diagnostic menu and checked the screen and everything is responding as far as I can tell--the line goes up to about an eighth of an inch from the top of the screen but the pictures for this when I googled looked like that so maybe they aren't supposed to reach the actual top of the screen.
Googling shows that several models at least of Samsung, and even some Sony, are showing this problem and nobody seems to know how to fix it.
Has anyone got any clues they can give me about this? I can't seem to find what the problem is.
Update--I tried flashing Hispasian Kernel but it didn't solve the problem. I tried defrosting everything I had frozen with Titanium Backup and that didn't solve the problem.
Flash latest stock lollipop FOL1 and see if it's still there. If that doesn't work then you have a hardware defect and you'll need to get your phone repaired.
That's a good idea. Thanks!
I am at the end of my rope with this. Several days ago my s5 started refusing to drop down the notification panel and the quick settings menu. I'm running stock rooted kitkat 4.4.2. I did a factory reset, disabled xposed (in case some notification bar mod was causing this even though I hadn't changed my xposed settings for months), got a replacement SIM card, went back to an earlier version of google, and now sometimes it will work for a whole day and then stop responding again. I took out the external SD card and it still does it. I uninstalled anything new (not much) that had recently been installed. I have been using Nova as my launcher, so I tried going back to just Touchwiz, but no change. I unfroze EVERYTHING I had frozen with TiBu and that didn't help.
It's not just the drop down screens, when I open Titanium Backup and try to use the "clear" or "menu" buttons at the top of the screen, they don't respond either. It's like something is freezing the top half inch of the screen (I measured it in frustration).
I went into the diagnostic menu and checked the screen and everything is responding as far as I can tell--the line goes up to about an eighth of an inch from the top of the screen but the pictures for this when I googled looked like that so maybe they aren't supposed to reach the actual top of the screen.
I installed an app (Expand Status Bar) that will let you drop down either the notification bar or the quick settings, and that always works, so the function is still there in the operating system.
Googling shows that several models at least of Samsung, and even some Sony, are showing this problem and nobody seems to know how to fix it.
Has anyone got any clues they can give me about this? I can't seem to find what the problem is.
Update--I tried flashing Hispasian Kernel but it didn't solve the problem. Well, it was worth a try.