today i noticed an odd issue with the lights on the navicap on my TP, When the screen switches off the lights on the navicap stay illuminated (The home, back, answer and hangup buttons) the light round the dpad/scroll wheel dont light up tho, i dont know how long this has been going on though as i have only just noticed it
does anyone know why this mite happen or any ideas to solve it
cheers
I also can confirm this issue.
Seems to happen only when the light has been activated in landcape mode.
I can recreate this failure every time I reply to a SMS:
Slide open keyboard
Keyboard and navipad lights come on
Reply to sms
Press power button
...and tada! The light is stuck on
The light will go off if I press the center dpad button before I turn off the device, or if I turn back on the device and tap the button.
This problem has followed me through 3 ROMs: the stock ATT Fuze ROM, the new ATT ROM, and an older EnergyROM (8/11/09, not sure which version anymore).
I can also confirm that this problem exists across multiple phones running stock software. My first Fuze had this problem, my current Fuze has this problem, and my friend's Fuze does too. Very odd.
Not a showstopper, but I figure it's the only annoyance I really have to put up with day to day, now that I've got the phone configured the way I like it.
Anyone have any ideas?
Thanks in advance!
My screen would not wake up, I flashed Cyanogen Mod, the latest version, but as soon as my screen goes off and I tried to wake it, it'll just stay in a lighted black screen forever, nothing happens, it wont wake or respond to buttons so I have to pull battery. It didn't happen on just this rom, I tried other roms as well. And same results, is it my phone or rom? I just got the phone today.
Which rom are you running? And did you flash a custom kernel?
Try a complete wipe and reflashing, but don't restore any apps, if you do, and see if the problem persists.
buru898 said:
Which rom are you running? And did you flash a custom kernel?
Try a complete wipe and reflashing, but don't restore any apps, if you do, and see if the problem persists.
Click to expand...
Click to collapse
I was running the latest version of Cyanogenmod. And no, I did not flash a custom kernel. I've already tried a complete wipe and flashed the rom like so many times. Like Cyanogenmod would install, but as soon as I put the phone to sleep and I hit the home button to try to wake it, it would be stay as a lighted black screen. The phone is responding to the button but it seems like the screen would not go on, the light for the 4 buttons lights up, but the screen doesn't display anything, just backlight. Please help, this is confusing me.
Set the phone to not sleep, it will just dim the light to near 0% brightness. I used to have this problem too on some nightlies and stable cm releases even and doing the above worked for me. I also bumped minimum cpu speed to 500-800 instead of 300, which lagged too much imho.
Sent from my LG-P999 using xda premium
NekoNyapii said:
I was running the latest version of Cyanogenmod. And no, I did not flash a custom kernel. I've already tried a complete wipe and flashed the rom like so many times. Like Cyanogenmod would install, but as soon as I put the phone to sleep and I hit the home button to try to wake it, it would be stay as a lighted black screen. The phone is responding to the button but it seems like the screen would not go on, the light for the 4 buttons lights up, but the screen doesn't display anything, just backlight. Please help, this is confusing me.
Click to expand...
Click to collapse
You say you press the home button when you turn the screen off and the buttons light up? Or did you mean when you pressed the power button?
When I press on the power button to wake it up, it just gives me a black screen. However the buttons light up when I touch them just the screen wont display anything.
Sent from my LG-P999 using xda premium
NekoNyapii said:
When I press on the power button to wake it up, it just gives me a black screen. However the buttons light up when I touch them just the screen wont display anything.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
That happened to me once. Did you wipe "system" in CWM before installing the rom?
Same Issue
Did you ever find a fix for this problem? My G2x just stopped coming on and I never changed any settings or anything. I've wiped davlik & user data; installed stock and custom roms, but every time the screen turns off the power button fails to wake the phone up. No lights flash or anything. I've found others who have the same problem but I haven't discovered any solutions. I'm guessing this must be a hardware problem since the power button does work to initially turn on the device and lock it but can't wake it. Any help would be greatly appreciated.
I'm currently running a rooted stock rom with the v21y BB that's been ICS-ified
r3sidual said:
Did you ever find a fix for this problem? My G2x just stopped coming on and I never changed any settings or anything. I've wiped davlik & user data; installed stock and custom roms, but every time the screen turns off the power button fails to wake the phone up. No lights flash or anything. I've found others who have the same problem but I haven't discovered any solutions. I'm guessing this must be a hardware problem since the power button does work to initially turn on the device and lock it but can't wake it. Any help would be greatly appreciated.
I'm currently running a rooted stock rom with the v21y BB that's been ICS-ified
Click to expand...
Click to collapse
I've found this issue to exist of literally EVERY build of CM that I've every used on ANY android device. I can't stand it. I finally stopped flashing CM all together because I hate not being able to wake up my device. NO OTHER ROM has done this before. Doesn't matter the model. Here's all the models that exibit this behavior that I've tested with.
Kindle Fire - CM9, CM10 and CM10.1
Galaxy 7 tab 2 - CM10, CM10.1 and CM10.2
Samsung Epic 4g (Galaxy S1) - CM7, CM9, CM10, CM10,1
Galaxy S3 Sprint- CM10, CM10.1
Galaxy S4 Sprint - CM10, CM10.1 and now CM10.2
That's very interesting. CM... I ended up sending the phone to LG to fix. I have a GS2 now so I gave the phone to my father. It runs great now.
sulotion to screen not waking up on cyanogenmod
I was having the same problem on my Samsung Galaxy note 2. I'm running cyanogenmod 11. I solved the issue by going into setting then display and lights and unchecking proximity wakeup. I hope this can help someone else.
Thank you a lot man! I was really in panic mode.
Not Waking up
This problem started once I have upgraded to official Lollipop. When I press the power button, the screen doesn't wake-up immediately. I had to press many times the power button to get the screen comes.
I have installed the latest CM9 nightlies.
I have turned BLN off but have other settings to leave the capacitive buttons on.
However, whenever I turn on the screen, it has random on/off of capacitive buttons.
Sometimes it would turn on, and sometimes it would be off and all of a sudden it would turn on.
Anyone with this problem and know the solution to it?
It wasn't like this for TW.
Also happening to me on every build of CM9 since a while now, and also AOKP if I recall. I'm using the rogers model.
Just flashed Paranoid Android 2.13 to my ATT Skyrocket. Everything went fine but the capacitive buttons will not light up. I can go to settings-advanced and turn them off and then back on and they start working until the phone goes to sleep. Is there a fix for this or anyone else have this problem on 2.13?
I've the issue that with some nightlys between CM11 M9 am M10 my One S has got issues with the capacitive buttons. After the first screen off they completly stop working. No light and no reaction. If I prevent the screen from turning of all is fine.
I'm currently running M9 with Bubba kernel, but as Bubba isn't working for me with the new nightlys or milestone releases, I'm currently stucked at the M9 impossible to update.
I've tried M10, M11 and some nightlys between without success. The One S is S-OFF but I've also flashed the included boot.img in fastboot without no help. Even a clean system/data wiped installation immediately reveals this issue after the first screen off.
Does someone else have this problem or know possible fixes I can try?
I've encountered the same problem. There used to be somewhere in settings where you can turn capacitive buttons on and off. I've previously set my capacitive buttons off, but after an update, the onscreen nav buttons aren't showing after the screen turns off, and the capacitive buttons remained at their disabled setting.
I need to figure out how to turn capacitive buttons back on at least.
I think I've got a kind of insane hardware issue with my ville.
Tried CM12 yesterday with the same behavior. Then decided to do an RUU and tested in the original HTC Sense rom.
And I've still got the same issue in the original rom.
Now only my CM11 M9 backup with the Bubba kernel is working for me.
As I also noticed some screen burn-in from Google Maps on the AMOLED I think the time for a new mobile has come.