[Q] Screen goes dark on CM10.x - Epic 4G Q&A, Help & Troubleshooting

So, I've tried CM10.0 and CM 10.1 and I get the same problem a LOT.
When I hit the power button from the screen being off, the screen will stay dark. The softkeys will light up, and in actuality, the entire system still works, but the screen is basically dead. The one tried and true way I've found to restore the screen is this:
1. Take off the cover
2. Eject Battery and Replace
3. Boot into CWM recovery
4. Restart from there
5. Now the phone will show some of the screen in landscape. Hold the Power Button and select the second bar (it's reboot, but you can't see the name of the option. Luckily the selection bars are wide). Hit the Ok bar (again. can't see OK).
6. Now CM runs.
Any ideas as to what causes this and how I can prevent it? Could it be a proximity thing? Note: this does not happen to me in CM7.
Thanks,
Tony

Remove boot animation (/system/media/bootanimation.zip) via any means possible. I wonder why this appears on an official CM build...
Sent from Samsung Captivate Glide @ I927UCLJ3

I think I have the same problem, I´m on CM9, I turn on the phone and the screen and all the system works, but after I turn off the screen with the power button the screen stays black, but the system still works. This happened yesterday.
I have already tried installing another kernel, going back to stock with odin. But even on the stock sprit rom, that still happens.
I will try the CM7 to see if works

Related

[Q] Power button long press causes reboot on ICS-Dinc V.05

I've been running ICS-Dinc AOKP V.05 for a couple days. Great ROM! Since I am testing a couple ICS ROMS, I decided to run them through the Boot Manager App.
I've run into an odd issue. When I long press the power button, say to take a screen shot or power down, the phone does a "hot" reboot. By hot reboot I mean it does not power down, then goto HTC splash screen, then ROM boot animation. It simply goes to the ROM boot animation. All else seems to work as it should based on the change log and known issues. I searched through the development thread and did not find a similar report.
Thoughts?
Check under
System Settings>ROM Control>Powe rmenu Options
and make sure that show torch toggle is not checked. I was having this problem and disabling this seemed to fix it.

[Q] acer a100 update failed?

A friend brought me a tablet at work today and told me that after he received an update the tablet's screen wouldn't unlock and the battery wouldn't charge past 12%. I got the tablet home and turned it on. it let me unlock the screen but kept going to a blank screen with "android system" in the top left corner. I press the home button and it goes to the home screen but all the icons flash on and off the screen. I tired using the hardware reset switch this did nothing. I tried a factory reset by using the volume+, power and screen lock switch. Factory reset went through okay but now when it boots up (after acer and android logos) it immediately attempts to shut down. it will stay on the shutting down screen indefinitely. to my knowledge this tablet has never been rooted.
I searched the forums but couldn't find any info, everyone had rooted then downgraded to get the updates. I do know that the tablet is under warranty still and that it could be sent in for service.
I would also like to note that before the factory reset the tablet would only let me unlock it once, then after i would reboot I was unable to unlock it again until it had set for some time. After the factory reset the tablet come to the blank screen with android system in the top left. the only function that would work was the screen rotation lock switch. after a reboot it would immediately attempt to shut down.
I would like to know if there is anything I can do so that we don't have to send the tablet off for service. I'm sure that I am overlooking something here. thanks.
It sounds pretty screwed. It seems like a bad flash, try running the ICS "leak" available in the dev section, name it update.zip then place it on your external SD card. Power on holding the volume key closest to the lock switch and report what it does next.
Tapatalked from my Thrive - Kuroikaze B13x
pio_masaki said:
It sounds pretty screwed. It seems like a bad flash, try running the ICS "leak" available in the dev section, name it update.zip then place it on your external SD card. Power on holding the volume key closest to the lock switch and report what it does next.
Tapatalked from my Thrive - Kuroikaze B13x
Click to expand...
Click to collapse
Thanks!
Any update on this? I know it's been forever, but I was just recently given an A100 that's doing the exact same thing (sitting at "Shutting Down).
I've been able to reflash via the update.zip, but with no luck.
Nevermind. I was able to fix mine with "SD_Acer_A100_1.014.08_COM_GEN1_full_user.zip" from this link:
http://www.imeiserver.org/download/index.php?dir=Flash Files /ACER/A100/
I renamned it "update.zip", held the left volume button (in landscape mode) while powering it on. The update ran, then it was stuck on the "Android" screen. I powered it off, then held the right volume button while powering it on and moving the screen lock button. After reboot, it was as if it just came out of the box.
I hope this helps someone else.
touch-aaron said:
Nevermind. I was able to fix mine with "SD_Acer_A100_1.014.08_COM_GEN1_full_user.zip" from this link:
http://www.imeiserver.org/download/index.php?dir=Flash Files /ACER/A100/
I renamned it "update.zip", held the left volume button (in landscape mode) while powering it on. The update ran, then it was stuck on the "Android" screen. I powered it off, then held the right volume button while powering it on and moving the screen lock button. After reboot, it was as if it just came out of the box.
I hope this helps someone else.
Click to expand...
Click to collapse
Actual it should be renamed to just "update" because the system adds the .ZIP so if you rename it update.zip it shows up as "update.zip.zip" and that won't work...

Phone turns on 1/20 times

Hi, recently I've been making some modifications to my Samsung Galaxy s3 I747. I am running CM 12.1, with Xposed Framework, and am rooted. Whenever is press the lock button, the screen turns off, then immediately turns back on. The back and menu buttons do not turn off. In addtion, the phone will randomly shut sometimes after just brushing the lock button, and when trying to turn back on, makes it to the cyanogenmod screen then immediately shuts off. I am wondering if this is hardware issue with the my phone, and if it is, how can if fix it? If any of you guys have had the same problem, let me know.
Just don't use xposed.
I stopped using it after switched to 5.0+ roms.
It's still buggy and not finished. (I mean mostly on 5.0+)
Go to recovery, and make a clean install.

screen stays dark with boot sound

dear community
my neighbour gave me his Z1 compact because it did not work anymore.
It was stuck on loginscreen, when i touched the unlock button it vibrated, but nothing else happened.
I could however download all his photos on my Win7PC by just plugging it on USB
but it kept staying unresponsive, no way to get beyond lockscreen
So I used SonyMobileFlasher and unlocked the bootloader without any issues - no errors.
Then I flashed a new firmware obtained through XperiFirm without errors
Now, when I boot, I can hear the boot-melody (??)
but the screen stays dark.
I can connect the phone via flash mode and fastboot mode
I can switch it off by pressing volUp+Power (three vibrates)
from Off i press power, it plays the melody, but the screen stays dark
Is it a hardware damage?
Is there anything I can do for the phone?
thx for ur input
magusberlin said:
dear community
my neighbour gave me his Z1 compact because it did not work anymore.
It was stuck on loginscreen, when i touched the unlock button it vibrated, but nothing else happened.
I could however download all his photos on my Win7PC by just plugging it on USB
but it kept staying unresponsive, no way to get beyond lockscreen
So I used SonyMobileFlasher and unlocked the bootloader without any issues - no errors.
Then I flashed a new firmware obtained through XperiFirm without errors
Now, when I boot, I can hear the boot-melody (??)
but the screen stays dark.
I can connect the phone via flash mode and fastboot mode
I can switch it off by pressing volUp+Power (three vibrates)
from Off i press power, it plays the melody, but the screen stays dark
Is it a hardware damage?
Is there anything I can do for the phone?
thx for ur input
Click to expand...
Click to collapse
Seems like busted display to me. Flash recovery and see if touch screen works in recovery. If not, definitely hw.
thx for ur reply, i flashed TWRP- several trys, now I can see the TWRP lock screen, but when I swipe to log in it vibrates, soon after the screen scrambles away, vertical lines just fade and then crash-off.
seems very much like the screen is defect? not worth replacing, seems like a whole huzzle to replace that screen
pitty, one more device to trash.
i am seriously looking into fairphone2, would be nice to replace the screen so easy.
magusberlin said:
thx for ur reply, i flashed TWRP- several trys, now I can see the TWRP lock screen, but when I swipe to log in it vibrates, soon after the screen scrambles away, vertical lines just fade and then crash-off.
seems very much like the screen is defect? not worth replacing, seems like a whole huzzle to replace that screen
pitty, one more device to trash.
i am seriously looking into fairphone2, would be nice to replace the screen so easy.
Click to expand...
Click to collapse
Maybe not extremely easy, but there are guides in the forum here for screen replacement, if your feel up to it.

Black screen with time and weirdly large notification list.

My girlfriend was trying to turn my alarm off and somehow it got stuck on a screen I had never seen before, all black with white time at the top and a list of the notifications that was oversized, I could scroll through them but not interact with them or turn off the alarm and I could not reset the device by just holding the power button it would turn the flashlight on. I'm running lineage OS the latest build for the 10.
I eventually got it restarted after the alarm stopped by holding every button
Does anyone know what that was?
Extreme power saving mode ?
I am facing same problem. When I first switch to 14.1 Lineage OS ; It was doing it when a new OS update was available , to recover , I had to reboot using power off and volume down, back and home button would flash 15 times , phone would reboot, and all would work correctly. Right after reboot I would see the update suggestion LOS. Clear all and phone would behave ok until same pattern happen. I finally decided to update to latest nightly. Which was at the time 14.1-20170706-NIGHTLY-pme changed the update setting to manual. It still does the same random black screen , showing bold white clock , bold white weather banner , I can see text message notification but no swipe works in anyway shape or form. Simply need to reboot with Power and volume down. Seen details about similar problem on reddit about nexus4 doing similar behavior.
No , because there is no way out other than holding power and volume down to recover the phone. Sometimes it goes to normal restart , sometimes it goes to bootloader.
Have you just tried flashing a different ROM?

Categories

Resources