[Q] Soft key back lighting - AT&T, Rogers HTC One X, Telstra One XL

I am currently running CleanRom 4.2 (and this was happening on 4.1 too). My soft keys back lighting seems to be random. Typically the left one is always bright. The right one is sometimes dim and sometimes bright and the middle one is always dim if lit at all.
Any thoughts on how to fix this? Not a big issue just harder to see at night.

Mine have been kind of like that with the cleanrom series but a bit different. Sometimes the buttons dont even light up or come on randomly then shut off again.

Related

keyboard leds stay on after sliding back in

A couple of times I was shocked to notice that the keyboard leds on my TP weren't shut down with the keyboard slid in. Since there is a slight gap between the keyboard and the screen, in a dark environment, looking at the TP's right edge, white light was clearly visible just 1-1.5 cm's above the stylus (display and the hardware buttons were OFF, so no, no light "bleeding" effect).
After promptly sliding the keyboard out and back in, the lights went out; actually they went out right when I started to move the keyboard, possibly indicating that there might be a loose contact somewhere. Once, I actually waited for the light to go out by itself; it certainly stayed on after the regular "timeout" value...
So, I wonder: if the contact that is supposed to cut the power to the keyboard when you slide it back in sometimes doesn't work, but the device thinks it's locked and doesn't "timeout" the leds anymore, can this be the cause of mysterious battery drains reported so many times on this forum? Sure enough it's quite hard to spot, especially if you're using a case for the phone. It would most certainly explain why battery drain varied on my device rather wildly even though the usage pattern hardly changed from day to day.
I tried reproducing the effect but it's quite hard (I'd say for my device it would kill the lights correctly at least 9 out of 10 times) and I didn't want to stress the sliding mechanism too much...
Anyone notice this?
Just so noone thinks I'm seeing ghosts, today, just after unplugging it from my laptop, eventhough the keyboard hadn't even been opened, I saw the leds were on again. Just to be sure this wasn't a "feature" I waited about 5 minutes and they were still ON. So yes, this is most definitely a bug and a quite serious one at that.
I took a photo with a friends phone camera (sorry for the low quality). The bright, white, dots seen in the pic are the leds from the underlying keyboard (the phone had always been shut, keyboard fully slid in: display and hardware keys were completely off and no, there was no light from the D-pad either).
I can now easily understand how, occasionaly, the battery managed to run out so quickly... Has noone noticed this before? Am I the only one with a potentially defective unit/keyboard contact?

[Q] Backlit buttons not working correctly

Ok,
So my home row buttons (Menu, Home, Back, Search) do not light up as they should! if the room is dark they will not work at all! and ive never seen them work in a dark room! However every day in the late afternoon when im in my living room and the phone is charging they will just light up! (at first i though it was a refection or just ambient light in the room so i grabbed the phone and ran into my closet and WOW they light up!) so i figured it was something with my settings so i reset my phone to new and still same problem, then said WTH and rooted and updated to 2.3.4 (best thing ive done with it so far!) and have the exact same problem... So then i decided to try another charge (brand new out of the box 1 day old!) and the lights will do the same and light up when its moderately light in the room but then they wont turn off...
So a chat with samsung and they tell me that these phones dont have that feature! so off to verizon and lets test a few more devices!!! and what? at some point they lit up also in inappropriate lighting conditions, so after puzzled VZW people i consult samsung again and they tell me yet again that the featured isnt offered on this phone, so my guess is that its a software flaw?
any ideas?
anyone having lighting issues?
thanks
Wow, that's a lot of exclamation points. I don't know what you're talking about, mine work fine
Sent from my Droid Charge running Humble 1.4
Pictures
Here are 2 pictures that show what im talking about, i will try to get a few more
Odd, works fine for me. Is it possible that you have a screen protector covering your light sensor? In the day time the back lights are off, then if I cover the light sensor they come right on.
mtmcghee said:
Ok,
So my home row buttons (Menu, Home, Back, Search) do not light up as they should! if the room is dark they will not work at all! and ive never seen them work in a dark room! However every day in the late afternoon when im in my living room and the phone is charging they will just light up! (at first i though it was a refection or just ambient light in the room so i grabbed the phone and ran into my closet and WOW they light up!) so i figured it was something with my settings so i reset my phone to new and still same problem, then said WTH and rooted and updated to 2.3.4 (best thing ive done with it so far!) and have the exact same problem... So then i decided to try another charge (brand new out of the box 1 day old!) and the lights will do the same and light up when its moderately light in the room but then they wont turn off...
So a chat with samsung and they tell me that these phones dont have that feature! so off to verizon and lets test a few more devices!!! and what? at some point they lit up also in inappropriate lighting conditions, so after puzzled VZW people i consult samsung again and they tell me yet again that the featured isnt offered on this phone, so my guess is that its a software flaw?
any ideas?
anyone having lighting issues?
thanks
Click to expand...
Click to collapse
The light sensors (which controls auto brightness and the backlights on the hardkey) is broken in the kernel for Gingerbread..
If this is a huge issue for you you might want to consider going back to Froyo
kejar31 said:
The light sensors (which controls auto brightness and the backlights on the hardkey) is broken in the kernel for Gingerbread..
If this is a huge issue for you you might want to consider going back to Froyo
Click to expand...
Click to collapse
But he said it happened with the new phone and the verizon display one...?
Sent from my Droid Charge running Humble 1.42
It might even be broken on the stock Froyo. All the people who said it's working fine for them right now are running custom ROMs, kernels, firmwares and all that jazz. Maybe it was fixed through one of these custom updates. I dunno.
I just got a brand new Charge (thanks to the Fascinate swap program).
The bottom buttons do not light up. This is fresh out of the box.
I also do not see any way in which they would light up - the icons appear to be painted on to the physical buttons. No underlay for LED backlight.. but I suppose there is one if custom ROMs allow for it.
Which I will know shortly
reply
blarrick said:
Odd, works fine for me. Is it possible that you have a screen protector covering your light sensor? In the day time the back lights are off, then if I cover the light sensor they come right on.
Click to expand...
Click to collapse
there is no screen protector or case on either of the phones, and both phones were cleaned well to make sure nothing was hindering the sensors.
[/QUOTE]The light sensors (which controls auto brightness and the backlights on the hardkey) is broken in the kernel for Gingerbread..
If this is a huge issue for you you might want to consider going back to Froyo[/QUOTE]
The problem is not only to the one that is rooted and flashed but also happens to the 2 at verizon that i inspected (brand new out of the box) and the 2nd one that i have that is also brand new with no mods
[/QUOTE]It might even be broken on the stock Froyo. All the people who said it's working fine for them right now are running custom ROMs, kernels, firmwares and all that jazz. Maybe it was fixed through one of these custom updates. I dunno.[/QUOTE]
I think that the kernel for this phone was just snatched and quickly edited (by samsung) from another product and this is one thing that they havent been able to fix and figure out, because the woman at samsung told me
(Ruby: As your phone has physical keypads, there is no light feature available for keys.
Visitor: the small row of buttons (4 to be exact) at the bottom of the phone should be back lit in low light situations, however they occasionally light up but only in moderately to brightly light rooms
Ruby: I am sorry, there is no feature available on your phone.
Visitor: im sorry but i can prove that this phone does have back lit keys
Ruby: I am sorry, your phone home key rows do not have light option)
but we all know that the button do actually have a lighting option and samsung is just trying to delete the function but isnt 100% successful..
I don't know what to say, they work properly for me. This includes when I was fully stock EE4, as well as now (deodexed, rooted ROM, PBJ kernel, voodoo enabled).
droid charge doesnt have backilights in the keys.. wth are you all talking about... no wait there they are! barely. what th! where did they go again?
Stock froyo from the factory... Daylight = button lights off; sensor covered (night) = button lights on.
Sent from my SCH-I510 using XDA App

capacitive buttons not lighting up

I find with my phone that the capacitive buttons do not light up all the time, it seems from boot to boot that it will sometimes work and sometimes not but with bricked kernal it works all the time and in the recovery it works all the time as well.
Anyone else getting this problem ??.
By design, they turn on and off depending on the amount of the light in the area. If you were to be in a dark place, then they will light up. If you were outside during daytime, then they would turn off as you can see the buttons just fine without them lighting up.
that doesnt seem to be the case for mine, its either on or off, i have not noticed it dynamically change depending on the condition of lighting.
Have you flashed a custom rom? If so, consider reinstalling the rom or swapping it altogether. If you've modified any system files or flashed any customization zips, that could be the culprit too. I know some roms out there offer "tweaked brightness thresholds", I believe this could contribute as well.
yea its ARHD i update every couple weeks or so.
Are you on ICS? If so playing around with the brightness settings should fix it, put in on auto brightness as well.
Sent from my TripNiCE Pyramid using xda premium
I think i have figured it out, it seems that if i boot or reboot my phone in the light it will be off but if it put it under a blanket or somewhere dark it will switch the capacitive lights on. It only seems to switch between on and off when booting/rebooting so do other peoples switch on and off dynamically while the phone is still switched on ??.
I have tried all roms including ICS and the same scenario happens with all.

[Q] Dead screen now dimmer with vertical lines / banding

Hello. The screen on my wife's S4G today suddenly started acting funny. First, it wouldn't display anything, but it seemed the phone was still functional. Then, with fiddling on my part, I got it working again, first fully and now in a sub-par way. The phone boots fine - and I actually unlocked the bootloader and rooted, and in the process went through a full reset, just to see if that would help anything - but the screen appears dimmer than before and there's vertical banding across most of it. The banding doesn't completely obscure the screen, but it looks bad. One other thing I notice, and this is reported in other places, is that there's backlight bleed in the lower left corner, even when you just insert the battery, and often on booting, there's a flash of pixelated "dust" across the screen, that's brightest in that corner and fades as it spreads out.
Anyway, TMI probably. Does this sound to anyone like a bad screen, bad connector, digitizer, or something else? I'm totally new to any of these kinds of issues, but would like to save the phone, if possible. TIA.

[Q] Screen Issue? (XT926)

I received my XT926 as a refurb and I have been experiencing a strange screen issue.
I will often have my phone on a dock, charging and sometimes I will notice the screen is black like it's off, but the touchscreen is responsive. Hitting the power button does nothing but it makes the sound as if I had locked the phone. Hitting the power button a second time will turn the screen on like normal operation.
Very rarely I have noticed the screen will turn off while I'm actually using the phone and it's a weird effect. The easiest way to describe it is that it looks like entire lines disappearing randomly over a period of 1-2 seconds, going from all visible, then to all black, kind of like slatted blinds being closed, but at random. After this, it displays the same symptoms as if I had found the screen off while in a dock/charging.
Now, I don't want to say it's related, but I first started experiencing this on the Stock KitKat update from Verizon. I am currently using Cyanogenmod 12 nightlies and I am experiencing the same issue. It seems to be happening with greater frequency.
I have also experienced the blue screen effect when certain animations/elements/apps are up on my screen, but I think they are unrelated.
Also, there is a faint discoloration bar about 2/5ths of an inch thick uniformly vertically from top to bottom of my phone on the righthand side (just under where the notification bar would be if turned horizontal).
I've tried to find more information about this but my search results have been relatively lackluster (90% of the results are trying to sell me the phone or specification pages)
So I'm breaking down and turning to here. Does anyone know what's going on here? My current theory is that my screen is going bad. I have no intention of replacing the screen on this phone (would rather just buy a new one), so any suggestions that don't involve physical hardware repairs would be appreciated.
I thought i was the only one experiencing it.
The screen turning off with a weird effect happens rarely but yeah it happens. And the blue screen effect, i noticed it only happens when im on the youtube app when the video stops working because of my connectivity issues.
Im not rooted nor is my bootloader unlocked. On the latest system version. Sounds like a software problem but hey im no expert.
kayonesoft said:
I received my XT926 as a refurb and I have been experiencing a strange screen issue.
I will often have my phone on a dock, charging and sometimes I will notice the screen is black like it's off, but the touchscreen is responsive. Hitting the power button does nothing but it makes the sound as if I had locked the phone. Hitting the power button a second time will turn the screen on like normal operation.
Very rarely I have noticed the screen will turn off while I'm actually using the phone and it's a weird effect. The easiest way to describe it is that it looks like entire lines disappearing randomly over a period of 1-2 seconds, going from all visible, then to all black, kind of like slatted blinds being closed, but at random. After this, it displays the same symptoms as if I had found the screen off while in a dock/charging.
Now, I don't want to say it's related, but I first started experiencing this on the Stock KitKat update from Verizon. I am currently using Cyanogenmod 12 nightlies and I am experiencing the same issue. It seems to be happening with greater frequency.
I have also experienced the blue screen effect when certain animations/elements/apps are up on my screen, but I think they are unrelated.
Also, there is a faint discoloration bar about 2/5ths of an inch thick uniformly vertically from top to bottom of my phone on the righthand side (just under where the notification bar would be if turned horizontal).
I've tried to find more information about this but my search results have been relatively lackluster (90% of the results are trying to sell me the phone or specification pages)
So I'm breaking down and turning to here. Does anyone know what's going on here? My current theory is that my screen is going bad. I have no intention of replacing the screen on this phone (would rather just buy a new one), so any suggestions that don't involve physical hardware repairs would be appreciated.
Click to expand...
Click to collapse
i also have this with my referb i made moto give me my money back and they let me keep the phone for me it was very rare but my new phone also had a really bad screen all yellowish and bad white balance in low light if you are unhappy with it call them and say you are unhappy with the replacement here is the white glove number 800-653-7185 they are more understanding and nice but you may lose you ability to unlock your bootloader on the new phone if it comes with the latest software just a warning
I have that screen off with lines slowly disappearing thing, too And, yeah, it's also a refurbished one, bought from one of the sellers on aliexpress... I thought Lollipop was the culprit or something like that. Oh, well... It rarely happens. And luckily I only have that, not the second issue you mentioned
I am having this exact same issue. The weird lines-to-black screen thing, and the flickering blue screen when watching video. Are you saying the solution is to call Motorola and ask for a new phone?
The blue flickering can be prevented by going into Developer Options and checking "Disable HW Overlays".
The discolored stripe on the screen sounds like burn-in; these AMOLED screens are much more susceptible to burn-in than the LCD screens used in older phones. Whomever owned the phone before it was returned to Motorola probably had something running on their screen continuously with a bright-colored bar at the top, likely in a car or desk dock. The screen is very easy to replace yourself with an eBay part, if you're inclined; it involves 2 screws and 2 connectors.
I've seen the lines-to-black thing exactly twice since I got this phone refurb two months ago. Sorry, I don't know what causes it or how to avoid it, but the workaround is quick and simple enough that I'm not worried about it, yet.

Categories

Resources