[Q] Soft key backlight? - HTC One S

The lights for my three softkeys don't always turn on, unless i cover the front cam/light sensor with my finger. any way to fix this so that the backlight turns on when i'm using the phone?

usmelllikecheez said:
The lights for my three softkeys don't always turn on, unless i cover the front cam/light sensor with my finger. any way to fix this so that the backlight turns on when i'm using the phone?
Click to expand...
Click to collapse
its automatic with light sensor

yeah, i get that...
but, i'm sitting in complete darkness right now, and the soft key lights aren't coming on. the only way it does is if i cover the front camera with my finger.
does that mean it's faulty? or is there something i can do to make the lights come on when they're supposed to?

Mine are hit or miss. Most of the time I find myself covering the sensor like you said. Didn't see an option to adjust sensitivity or anything. Pretty lame.

I noticed this too. They should make settings option to be selected by user...miss the perfection of the NEXUS one

usmelllikecheez said:
yeah, i get that...
but, i'm sitting in complete darkness right now, and the soft key lights aren't coming on. the only way it does is if i cover the front camera with my finger.
does that mean it's faulty? or is there something i can do to make the lights come on when they're supposed to?
Click to expand...
Click to collapse
I think it is faulty, my key light is on whenever the surrounding light condition is poor. Don't think there is a setting for this but I might miss something here.
Bottom line, if you fully checked the setting cannot find anything, just exchange it.

Mine also seem to be inconsistent. Sometimes they come on immediately (like they should), sometimes I have to open an app, and sometimes they won't come on at all.
One wacky theory that I have is that the sensor is getting tricked by the reflection of the screen from my glasses. It may be in my head, but I feel like the issue comes up less when I am wearing contacts.

Maybe a solution
Have you tried this one? I did on my cm9-ed U8160, maybe it works on your devices too.

Mine are perfect, never have to cover the proximity sensor. Probably just a thing with different batches of devices. Got mine early summer around June.
Sent from my HTC VLE_U using xda app-developers app

Related

Huge proximity sensor problem

Guys, I have a problem with the proximity sensor on my Captivate.
The issue is that while on a call, when holding the device between my ear and my shoulder, the proximity sensor causes the screen to turn on, and starts randomly hitting buttons. So I tested it.
The proximity sensor works perfectly when the phone is "standing" on end and the proximity sensor is covered. It does NOT work (the screen does not turn off) when the phone is laying flat and you cover the sensor.
So bottom line, when the phone is standing 90 degrees, the proximity sensor turns the screen off when there's no light. When the phone is 180 degrees (or anywhere near it), even when there is no light, the sensor does not turn the phone off.
Is there any way for me to tweak the sensor at all using an app? Or is my phone defective?
Thanks.
With the phone flat on the table and I make a call, using my finger to cover the sensor the screen goes off. I try to twist and turn the phone in all angles and the screen is still off. Not sure if it's related but I had the same problems with the screen coming on when using my shoulder and cheek to hold phone.
My hair was a little longer and I think the hairs blocked the sensors.
baseballfanz said:
With the phone flat on the table and I make a call, using my finger to cover the sensor the screen goes off. I try to twist and turn the phone in all angles and the screen is still off. Not sure if it's related but I had the same problems with the screen coming on when using my shoulder and cheek to hold phone.
My hair was a little longer and I think the hairs blocked the sensors.
Click to expand...
Click to collapse
I just did the same thing. With the phone flat on the table and I make a call, cover the proximity sensor with my finger, the screen stays ON. The minute I put the phone up 90 degrees, the screen shuts off.
What's going on?
ajm786 said:
I just did the same thing. With the phone flat on the table and I make a call, cover the proximity sensor with my finger, the screen stays ON. The minute I put the phone up 90 degrees, the screen shuts off.
What's going on?
Click to expand...
Click to collapse
Perhaps you are running a different combination of kernel/rom? One that takes into account the devices orientation when engaging the proximity sensor?
I've never actually tested this, but I know I had various degrees of proximity sensor problems running certain ROMs. So maybe try a different combination?
Shammyh said:
Perhaps you are running a different combination of kernel/rom? One that takes into account the devices orientation when engaging the proximity sensor?
I've never actually tested this, but I know I had various degrees of proximity sensor problems running certain ROMs. So maybe try a different combination?
Click to expand...
Click to collapse
I'm running Cognition 2.3b, if that helps.
ajm786 said:
I'm running Cognition 2.3b, if that helps.
Click to expand...
Click to collapse
Doesn't actually sorry...
Haven't used any of the Cognition ROMs in quite a while. DesignGears has a nice IRC channel though where lots of people tend to hang out. Maybe hop over there and politely ask around to see if anyone else has had the same problem? Asking within a group of Cognition users might get you more help than the XDA population in general.
All I can say is that with my i9000 kernel/radio/rom combo, my proximity sensor is not affected by the device orientation. Also, you could try running a proximity sensor test and see what happens, just to rule out defective hardware.
*#*#0588#*#* – Proximity sensor test
Hope that helps.
Shammyh said:
Doesn't actually sorry...
Haven't used any of the Cognition ROMs in quite a while. DesignGears has a nice IRC channel though where lots of people tend to hang out. Maybe hop over there and politely ask around to see if anyone else has had the same problem? Asking within a group of Cognition users might get you more help than the XDA population in general.
All I can say is that with my i9000 kernel/radio/rom combo, my proximity sensor is not affected by the device orientation. Also, you could try running a proximity sensor test and see what happens, just to rule out defective hardware.
*#*#0588#*#* – Proximity sensor test
Hope that helps.
Click to expand...
Click to collapse
I can confirm using the proximity sensor test that it works fine. Proximity sensor only has two states, 1 and 0, correct? No matter the way I hold the phone, the proximity sensor test shows it running perfectly.
Does this mean that there's a problem with the ROM? Is it possible for me to simply replace the phone.apk?
Edit: Here's the EXACT problem I'm having. http://code.google.com/p/cyanogenmod/issues/detail?id=1916
I have this same issue!! I HATE IT! I have considered going BACK to my iphone because of it! I get tired of muting people and ending calls
ETA: I am using the leaked 2.2 Froyo not cognition
Does anyone know how to fix this? It's getting REALLY annoying!!
Does anyone know if dg is going to fix this in Perception?
ajm786 said:
Does anyone know if dg is going to fix this in Perception?
Click to expand...
Click to collapse
Does it work if you flash back to the stock ROM? If it works on stock then it's a problem with the ROM, If it doesn't work on stock then it could be a problem with your phone...
jhernand1102 said:
Does it work if you flash back to the stock ROM? If it works on stock then it's a problem with the ROM, If it doesn't work on stock then it could be a problem with your phone...
Click to expand...
Click to collapse
Yes. Flashing back to stock ROM it works perfectly. Any of the Froyo ROMs, it does not work. Cyanogenmod fixed this in his ROMs, but I am not sure if dg plans to implement this in his ROMs. :-( Unfortunately, this behavior is by design in Froyo. Google decided that during a call, it makes more sense that as soon as your phone is put in a horizontal position, that the accelerometer overrides the proximity sensor and disables it. Their decision makes no sense, because it then invalidates the need for a prox sensor in the first place.
ajm786 said:
Guys, I have a problem with the proximity sensor on my Captivate.
The issue is that while on a call, when holding the device between my ear and my shoulder, the proximity sensor causes the screen to turn on, and starts randomly hitting buttons. So I tested it.
The proximity sensor works perfectly when the phone is "standing" on end and the proximity sensor is covered. It does NOT work (the screen does not turn off) when the phone is laying flat and you cover the sensor.
So bottom line, when the phone is standing 90 degrees, the proximity sensor turns the screen off when there's no light. When the phone is 180 degrees (or anywhere near it), even when there is no light, the sensor does not turn the phone off.
Is there any way for me to tweak the sensor at all using an app? Or is my phone defective?
Thanks.
Click to expand...
Click to collapse
i think its cognition. i didnt test it but i had the problem during calls, i figured it was sesitivity not position but like i said i never tested it . i think its a jj4 bug. now im using perception and it works better.
Dani897 said:
i think its cognition. i didnt test it but i had the problem during calls, i figured it was sesitivity not position but like i said i never tested it . i think its a jj4 bug. now im using perception and it works better.
Click to expand...
Click to collapse
It's not Cognition. It's Froyo. Google made the choice to have the accelerometer disable the prox sensor as soon as the phone was oriented horizontally. I can't see in what situation that would make any sense at all.
Still no answer for fixing this? I am not using cognition, I am using the leaked Froyo...
FYI, im in stock eclair. I have this issue.
sent from my Captivate
I'm running cognition b7 and have the same issue but just hit the power button to manually toggle the screen in a horizontal position during a call. Hardly an inconvenience.
fooldog01 said:
FYI, im in stock eclair. I have this issue.
sent from my Captivate
Click to expand...
Click to collapse
Eclair does not have the problem at all. Tried, tested and true. If you have the problem with stock Eclair, something is physically wrong with your phone.
silver2wind said:
I'm running cognition b7 and have the same issue but just hit the power button to manually toggle the screen in a horizontal position during a call. Hardly an inconvenience.
Click to expand...
Click to collapse
That's not the point. The point is that they gimped Froyo on purpose, and for what, I don't know. It's counter-intuitive.
Just so you know, my co-worker has the Nexus S, which is basically the exact same phone as ours, except with Gingerbread. Guess what? It's FIXED on Gingerbread. Figures.

Enable proximity sensor

I am looking to find out how to enable the proximity sensor. When I take my ear away from the handset (e.g. calling a call sensor), it isnt detecting it. I therefore need to press the power button to wake the screen.
Any ideas?
Cheers
aidanbree said:
I am looking to find out how to enable the proximity sensor. When I take my ear away from the handset (e.g. calling a call sensor), it isnt detecting it. I therefore need to press the power button to wake the screen.
Any ideas?
Cheers
Click to expand...
Click to collapse
If you hold your thumb/finger over the top of the screen to the left of the HTC logo, do you find that the buttons light?
Just a thought here, but isn't this the feature of the light sensor? There are two of them in that particular area....
Dr.Romca said:
Just a thought here, but isn't this the feature of the light sensor? There are two of them in that particular area....
Click to expand...
Click to collapse
Opps, my bad, you're right I'm confusing the two...
Although I don't believe that I've seen any settings that dictate whether the proximity sensor is on or off, on my device it just worked out of the box, switching screen off during call when phone is lifted to ear and back on automatically when pulled away
Sent from my HTC Desire S using XDA App

[Q]Two LEDs on the front of phone?

There are two leds on the front of my inspire i obviously know what the one that is under the speaker mesh is for (lights up during notifications) But what is the one to the right for? Iv never seen it light up and i searched and couldnt find any thing about it.
Im basically just wondering, Thanks for any help in advance.
It is a proximitiy sensor, turns the screen off while your in a call. So while its up against your ear, you dont press buttons with your face.
Not 100% on this but Im guessing its used for the automatic screen brightness.
Oh ok, I honestly didnt even think of that lol. It just looks so much like an LED to me atleast lol.
Thanks for the quick answer.
slipmagt said:
It is a proximitiy sensor, turns the screen off while your in a call. So while its up against your ear, you dont press buttons with your face.
Not 100% on this but Im guessing its used for the automatic screen brightness.
Click to expand...
Click to collapse
Yes, it also controls auto brightness.
Success!
Plus I need 10 characters.

Capacitate buttons ?

OK guess in having my first problems? Today my capacitate buttons at the bottom of the phone have just started going out on there own. Literally while I'm typing this they have come on and went out like 5 times now. Is anyone else experiencing anything like this? Weird cause up until now I have had zero problems with my phone. Maybe a sensor having glitches?
Are you typing in landscape mode?
Sent from my MB865 using XDA App
No portrait ...right now they won't even come on? Like they all of a sudden have a mind of their own LoL
have you tried covering the light sensor by the speaker grill? The button lights are brightness sensitive, so by covering the sensor, they should turn on. Otherwise, I would guess there might be a problem with your auto brightness or the sensor itself. When I first got this coming from a captivate, I was confused since the captivate turned them on when you touched the screen.
Sent from my MB865 using XDA App
Yep tried the light sensor and a battery pull as well. Now they won't even light up? Not like its a killer dealbreaker for me or nothing. Just weird they all of a sudden went crazy?
Now that you mention it I've been experiencing the same issue with my atrix2. Its like the buttons have a mind if their own.
Sent from my MB865 using xda premium
Yeah, mine come on when they want to. Right now they are off.
Sent from my mAtrix2!!
All moto phones do this. The software for the light sensor is just REALLY bad, so there is really nothing we can do about it, unless a dev wants to help us out.
Well it really just started doing this today. But after playing aroung with the display settings I'm thinking the light sensor is either going bad or is bad. When I set it to auto brightness it gets dimmer then the lowest manual setting in a completely dark room. Oh well, like I said not a killer deal for me. Just never had one fail quickly like this.
try turning off auto brightness and see if they still do it
svtfmook said:
try turning off auto brightness and see if they still do it
Click to expand...
Click to collapse
I never use auto brightness its always set at about the lowest brightness on manual. I've played with it back and forth and think the light sensor is just acting up.
Wow, I hope that's not a widespread issue.
My A2 doesn't have that problem. It's quite new but I think it's my 4th now (I've lost count of how many times I've seen a dead pixel on that otherwise gorgeous screen) and I do remember the capacitive buttons' backlight doing weird things on my other Atrix(es). I can't remember if that was on my OG Atrix, or if it was on one of my A2s in a car and the lighting kept changing, or if it was an actual problem.
But anyways, the light sensor works pretty well for me on my current A2. I usually have it on auto-brightness.
Mine work perfectly on manual or auto.

Anyone else having this problem?

When I try to pull down the notification bar on the right the screen goes black. Also turns off the always on display. I'm assuming it's something with the Proximity sensor. Tired of all the little bugs and problems with this phone. I’m returning it. Just curious if anybody else is having this problem.
https://youtu.be/moTuJP06JCw
alnova1 said:
When I try to pull down the notification bar on the right the screen goes black. Also turns off the always on display. I'm assuming it's something with the Proximity sensor.
Click to expand...
Click to collapse
No, mine isn't doing that. You might have a dud.
alnova1 said:
When I try to pull down the notification bar on the right the screen goes black. Also turns off the always on display. I'm assuming it's something with the Proximity sensor. Tired of all the little bugs and problems with this phone. I’m returning it. Just curious if anybody else is having this problem.
https://youtu.be/moTuJP06JCw
Click to expand...
Click to collapse
I've had that happen on my Pixel 2 XL. Only once or twice and restart fixed it every time.
It's definitely the prox sensor. Always On Display shuts off when the phone is in your pocket or face down, which is detected by the proximity sensor, so that's totally normal. As far as it happening on the home screen, it seems like the phone thinks you're in a call, which would use the proximity sensor to turn the screen off near your head. I would reboot as @jimv1983 suggested and see if that works.
Are you using a screen protector? Sometimes those can cause issues with the proximity sensor, but usually it just causes the screen to shut off and not come back on during a call as it senses the protector at all times instead of your face.
fury683 said:
It's definitely the prox sensor. Always On Display shuts off when the phone is in your pocket or face down, which is detected by the proximity sensor, so that's totally normal. As far as it happening on the home screen, it seems like the phone thinks you're in a call, which would use the proximity sensor to turn the screen off near your head. I would reboot as @jimv1983 suggested and see if that works.
Are you using a screen protector? Sometimes those can cause issues with the proximity sensor, but usually it just causes the screen to shut off and not come back on during a call as it senses the protector at all times instead of your face.
Click to expand...
Click to collapse
I had a case with a built-in screen protector on it and I thought that might be what was causing it but after taking it off it still did it. Weird thing though once I put it on the wireless charger it stop doing it. Hasn’t done it all day even with case on. Weird. Still thinking about taking it back to Best Buy and swapping it out.
I've had a similar issue where the proximity sensor will not deactivate as long as a call is going (can't hangup, can't unlock, can't speaker phone, can't mute, etc.). I have to wait for the other person to hang up. Get an automated robo-call you accidentally answered....oh well, guess you have to listen to them. I have never been so angry at a phone as I am with this one. Especially as expensive as it is. I absolutely would NOT have bought this phone if I knew ahead of time how aggravating this would be! Thinking of sending it back. BUYERS BEWARE!
tonic1080 said:
I've had a similar issue where the proximity sensor will not deactivate as long as a call is going (can't hangup, can't unlock, can't speaker phone, can't mute, etc.). I have to wait for the other person to hang up. Get an automated robo-call you accidentally answered....oh well, guess you have to listen to them. I have never been so angry at a phone as I am with this one. Especially as expensive as it is. I absolutely would NOT have bought this phone if I knew ahead of time how aggravating this would be! Thinking of sending it back. BUYERS BEWARE!
Click to expand...
Click to collapse
Had this very issue with my pixel XL and blowing on the top speaker grille of dust with compressed air solved it.
But if this is out of the box that sucks. It should not be like that. My pixel was approaching two years when that happened.

Categories

Resources