EDIT: Just fixed permissions via Rom Manager and rebooted they seem to be functioning properly now. In low lighting situations they now come on.
I just updated to the newest radio and for some reason I'm not sure if its related but my capacitive buttons don't seem to be consistently lighting up. This may be a stupid question but when are they suppose to come on?
Related
I am OMJ's Rom on my EVO rooted with toasts method plus the radio update and the led's under the front buttons are not working. Has anyone else had this problem? Is there an app that controls them that was removed?
The lights will be off when the phone is plugged in and charging.
When exactly are the lights under the four soft buttons supposed to be on?
On my EVO (novatec 003, stock) I have noticed an inconstancy in when they light up. Sometimes they light up when I unlock my phone, sometimes they don't. Sometimes they turn on later, sometimes they don't turn on at all.
This doesn't seem normal to me. What are other's experience with this?
Thanks
they are controled with the light sensor and should be on in low light situations and off in bright lights. you can test this by covering the light sensor to the right of the HTC logo on top of the device.
Thank you @peepeesea that was it exactly. Which is more hi-tech that I gave them credit for.
Also as a side note, since I've been reading the xda forums I feel like a phone hypochondriac. Everythings broken!!
My wife's evo is running stock rooted 1.47 with some basic battery saving tweaks.
I noticed today that her capacitive buttons aren't lighting up. Anyone else had this issue? Is there a setting somewhere that controls them?
EDIT:
Seems like they sort of work. Sometimes they light up sometimes they don't. I'll try to figure out if there is a pattern to it.
DanBergundy said:
Seems like they sort of work. Sometimes they light up sometimes they don't. I'll try to figure out if there is a pattern to it.
Click to expand...
Click to collapse
Yes, as even a cursory search would have told you, they are controlled by the light sensor.
I believe i have a problem with the ambient light sensor on my G2 for what ever reason my back-light on the capacitive keys on the bottom of the screen when in a decently lit room keep coming on or off its work fine in a dark setting as it should but when i have both of my g2's side by side in the same room one stays on and the other keeps going on and off. I know this may be and most likely is a hardware issue but i purchased the phone on ebay so t-mobile will not let me exchange and HTC currently does not offer repair for the device yet. I was wondering if an RUU has been released yet and maybe flashing the phone would solve if it a software issue. I have factory reset the phone multiple times but it does not remedy the problem. does any one have any suggestions?
Is the RUU released yet?
Any one? ?
Sent from my PC36100 using XDA App
This is linked to the keyboard backlight, they both go on and off at the same time. I'm getting the same problem too on my DZ, the light sensor doesn't seem to be setup properly because it keeps going off and back on again (even if auto brightness is set to off).
I have a G2 running CyanogenMod 6.1rc1. It was working wonderfully until this morning, when it stopped displaying any image/video on the screen. The backlight still works, and I can unlock it (and turn on the LED flashlight) by memory, so the touch sensor is working, but I get no video at all (even in hboot/usb-fastboot).
I talked with a couple of guys in #cyanogenmod, and they say it's probably a hardware problem (damage to screen's ribbon cable), and needs to be RMA'd. I'd like to get CM off of the phone before sending it off, just to be on the safe side. Is there a way to do that without being able to see the phone screen (i.e., via ADB and/or specific keypress sequence for Clockwork Recovery)?
Thanks in advance!
The backlighting on my keyboard hasn't worked since I rooted. Is there any kind of mod or kernal to flash to get it working again? Or maybe a setting I am missing somewhere? I know it is tied to the light sensor.
[EDIT: FIXED]
It ended up being the light sensor. It somehow got set to custom values, which were all set too low.