Hello there,
I got my hands on a M7, which was fully stock and working. It has some minor scratches and damaged material here and there, though it worked fine, except for phone calls only being audible in speaker mode.
I flashed TWRP recovery and installed the latest nightly of Cyanogen mod (cm-12.1-20151005-NIGHTLY-m7). Though to prevent the custom recovery from being patched I unlocked the bootloader (Not sure if that was the solution, though).
It was all fine, until the screen dimmed, and I tried powering on the screen again by pressing the power button. Though it wouldn't turn on. I even tried setting on the option to turn on screen when connected to a power source, though it never powered on again. I also noticed a slight flash of blue light every now and then, and the screen feels too sensitive. It might register a press when you're just scrolling.
Could someone help me out with this? Of course I believe a hardware fix would be appropriate, but as how everything worked until the flashes, I believe it might be fixed with some software.
Any help is much appreciated.
Byrkoet said:
Hello there,
I got my hands on a M7, which was fully stock and working. It has some minor scratches and damaged material here and there, though it worked fine, except for phone calls only being audible in speaker mode.
I flashed TWRP recovery and installed the latest nightly of Cyanogen mod (cm-12.1-20151005-NIGHTLY-m7). Though to prevent the custom recovery from being patched I unlocked the bootloader (Not sure if that was the solution, though).
It was all fine, until the screen dimmed, and I tried powering on the screen again by pressing the power button. Though it wouldn't turn on. I even tried setting on the option to turn on screen when connected to a power source, though it never powered on again. I also noticed a slight flash of blue light every now and then, and the screen feels too sensitive. It might register a press when you're just scrolling.
Could someone help me out with this? Of course I believe a hardware fix would be appropriate, but as how everything worked until the flashes, I believe it might be fixed with some software.
Any help is much appreciated.
Click to expand...
Click to collapse
If you are talking about the screen not turning on (as opposed to the complete phone) Its a known bug of CM roms. The screen can't be turned back on when it was set to minimum brightness, or when the auto brightness set it to minimum. To avoid that, you'll need to adjust the brightness yourself instead of auto mode, avoiding the minimum adjustment. CM is known to be a buggy rom for the M7, you shouldn't have this issue if using a GPE or Sense rom.
alray said:
If you are talking about the screen not turning on (as opposed to the complete phone) Its a known bug of CM roms. The screen can't be turned back on when it was set to minimum brightness, or when the auto brightness set it to minimum. To avoid that, you'll need to adjust the brightness yourself instead of auto mode, avoiding the minimum adjustment. CM is known to be a buggy rom for the M7, you shouldn't have this issue if using a GPE or Sense rom.
Click to expand...
Click to collapse
Thanks for the info. I figured as much, I will try Exodus.
EDIT: I have tried Exodus, XenonHD and Dirty Unicorns. Though no success: none of them were able to turn on the display after it dimmed.
Related
We just picked up a used Droid for the dev department to play with. The backlight comes on during boot up but goes off as soon as it gets into the OS. Settings appear to be normal (full brightness). Any ideas?
hard reset didn't help. The backlight goes off at the exact moment the buzzer announces the os startup. (if that makes sense)
try using other roms..
Working on rooting and loading a rom right now. I took the phone home with me and discovered the backlight isn't out just very dim. It will change slightly when I move the brightness slider around.
OK, it's now running Steel Droid with the same issue. I have a bright screen in recovery and during boot and a very dim one once booted.
try to un-check the automatic brightness, and set it to full brightness...
if that doesnt work... might be a hardware related problem...
Did that already. Seems like an odd hardware issue. I have full backlight in recovery and during boot.
Here is a video of the issue http://www.youtube.com/watch?v=RxHqN_lycG8
Stupid question: do you have auto-brightness active? If so, maybe your light sensor could be broken.
downloadman said:
Stupid question: do you have auto-brightness active? If so, maybe your light sensor could be broken.
Click to expand...
Click to collapse
Auto-brightness is unchecked and the brightness is set to max. There is a very slight change to the brightness when I adjust the slider back and forth.
BTW. It is currently running CM7 with the same issue.
Hey guys so I'm having the following problem, during a call when I put the phone near my ear and the screen turns off, sometimes the phone stucks, what I mean is the after I remove the phone from my ear the screen remains turned Off and the buttons do not respond.. But the call is still working.. I had gueste rom then I changed to cyanogen but the problem is still there...
Unresponsive phone perhaps, because as far as I know, nothing of the sort happened to me ever.
Also, does the screen light up when you end the call...let's say by using power button?
Not likely, but I'll mention anyway, check if anything is blocking the proximity censor - holding habit, cellphone case etc.
Similar issue,any way to disable the proximity senzor?
DrGreem said:
Hey guys so I'm having the following problem, during a call when I put the phone near my ear and the screen turns off, sometimes the phone stucks, what I mean is the after I remove the phone from my ear the screen remains turned Off and the buttons do not respond.. But the call is still working.. I had gueste rom then I changed to cyanogen but the problem is still there...
Click to expand...
Click to collapse
I have pretty much the same problem,the screen remain turned off after i remove the phone from my ear and i can't activate the screen or press any buttons until the other person terminates the call.
I run a proximity test from the Hidden Menu and the sensor detects as NEAR all the time even though nothing is in front of it.
I reinstalled several roms and i still encounter the same issue therefore it must be a hardware problem.
I would like to specify that i don't use a screen protector therefore the senor is not blocked in any way.
Is there any way to disable the proximity sensor completely?is there a application or a setting for that?
DrGreem said:
Hey guys so I'm having the following problem, during a call when I put the phone near my ear and the screen turns off, sometimes the phone stucks, what I mean is the after I remove the phone from my ear the screen remains turned Off and the buttons do not respond.. But the call is still working.. I had gueste rom then I changed to cyanogen but the problem is still there...
Click to expand...
Click to collapse
andreita99 said:
I have pretty much the same problem,the screen remain turned off after i remove the phone from my ear and i can't activate the screen or press any buttons until the other person terminates the call.
I run a proximity test from the Hidden Menu and the sensor detects as NEAR all the time even though nothing is in front of it.
I reinstalled several roms and i still encounter the same issue therefore it must be a hardware problem.
I would like to specify that i don't use a screen protector therefore the senor is not blocked in any way.
Is there any way to disable the proximity sensor completely?is there a application or a setting for that?
Click to expand...
Click to collapse
I have had the same problem, with many roms. I think if you are on some of the ICS roms, you will have to expect some bugs, like this. I am now on Temaseks build 135.1 with his kernel and I dont have any of these bugs. It seems ICS for our P990 is to be expected soon, so try a ROM as close to stock as possible and wait for our ingenious developers to get the last drivers working and you will see a lot of bugs disappearing. I would not recommend you to disable additional hard/software.
One app that has helped me though, with some of the ICS issues, is AnTuTu CPUMaster. A free app in Play and it allows you to set your minimum clockspeed a little higher than standard, I set mine around 400Mhz and it took care of many of the little bugs related to phone not reacting according to expectations.
Good Luck
Have the same problem and man... its a huge pain...
I am on the official CM7 latest release. I used to be on temasek's one and did not encounter the problem. As I can;t change ROMs these days, any quick fix, calibration app that would do the trick? Thanks!
Last night, I decided to check out some of the new roms out for the droid 4 so I downloaded the avatar rom and tried it out. It worked fine except when I would lock my phone and put it into sleep mode, it wouldn't always wake up the screen when pressing the power button. The lights for the hard keys lit up, but not the screen. Then sometimes the screen would light up, but the touch screen wouldn't be active so I couldn't swipe to unlock. It usually takes between 5-10 tries until it finally works. I had the same problem with the AOKP rom as well.
I thought it might be the performance controls keeping the CPU too low when the screen was off and therefore having trouble waking it up so I set the minimum to 600 but that didn't help. Any ideas?
Also, slightly unrelated question but is there a way to turn off the transition animations for 4.2.2? I can't seem to find it :/
nuhusky4 said:
Last night, I decided to check out some of the new roms out for the droid 4 so I downloaded the avatar rom and tried it out. It worked fine except when I would lock my phone and put it into sleep mode, it wouldn't always wake up the screen when pressing the power button. The lights for the hard keys lit up, but not the screen. Then sometimes the screen would light up, but the touch screen wouldn't be active so I couldn't swipe to unlock. It usually takes between 5-10 tries until it finally works. I had the same problem with the AOKP rom as well.
I thought it might be the performance controls keeping the CPU too low when the screen was off and therefore having trouble waking it up so I set the minimum to 600 but that didn't help. Any ideas?
Also, slightly unrelated question but is there a way to turn off the transition animations for 4.2.2? I can't seem to find it :/
Click to expand...
Click to collapse
I have had similar issues with the 4.2.2 ROMs although not as often as you. It would happen to me maybe once a week. I would just hard reboot the phone when it happened. Not sure if it's an issue with the kexec kernel or what.
As for the transition animations I would assume they would be in the launcher settings somewhere.
To keep it short: I have a VZW HTC One unlocked and rooted running a 4.4.2 Nexus 5 port. Everything is fine and dandy until today when the screen shuts off. Phone is still completely responsive in that I can adjust volume, unlock, computer recognizes it, etc. I have found a lot of threads about HTC One black screen and noticed that there were a wide variety of causes and such so I am trying to consolidate information about this particular problem here.
Prior to this issue I had not flashed anything since January, sideloaded any APK's in as long. No problems with the rom, no abnormalities, etc. Was sitting and playing Jetpack Joyride when the screen shut off. The hardware buttons were still on. Rebooting the phone multiple times made no difference. Audio still works (can hear notifications).
What I have tried:
Rebooting the phone while aiming a bright light at the ambient light sensor (assuming the sensor is on the top bezel, I could not find any concrete evidence of the location).
Forcing a reboot through Fastboot.
Reinstalling HTC One drivers and doing it again.
For whatever reason it seems that fastboot can recognize the device but not ADB...
Now if no other solution presents itself, do I need to backup, reroot, relock, and send back to HTC for a replacement?
Hi!
I've installed the CM 12.1 by downloading and following the instructions from the CM wiki page for Moto G 2014, and also by reading threads from XDA. Now I've been using this for the last 2 weeks and this is happening once after every 3-4 calls. Whenever I get a call the whole screen turns black and doesn't respond :/
I've a LG G Watch as my android wear, so I use that to receive the call. After the call gets over, the screen is still unresponsive and I've to restart the phone by holding the power button.
I'm updated to the latest nightly. How do I solve this issue? Any help is appreciated.
Thank you.
This dead screen issue is still not fixed. The screen still dies after a few days of use. And it feels like the backlight of the screen turns off because all of the features of the phone still work. I've to restart the phone to turn the screen on again.
I'm updated to the latest nightly. Any fix for this issue? PLEASE HELP.
Try different ROM remember clean flash
I might have the same problem. I can see the phone is recognized by the computer and the adb command "adb devices" shows it. I also hear the sounds produced by raising the volume buttons. Rebooting it won't bring the screen on. Any idea how to fix it?
EDIT: I Noticed that flashing strong light on it shows the screen a bit. Managed to turn of the live display option and crank the brightness setting to the max like many suggested. No change. Also updated ROM to latest CM12.1 (20150831) tried flashing a strong light into the front camera/sensor and using adb to set the brightness to 200. Still no change
The odd thing that makes me 90% certain this is some kind of hardware failure is that the dark screen persists on recovery and bootloader screens, not just system.
I have same issue, screen not waken up when call comes but just pressing power button shows screen for me