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.
Related
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
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.
sooo, yeah. my wife has the t959v. the screen cracked months ago, replaced it with one from ebay, works fine. a few weeks ago, it was involved in an accident and needed yet another screen replacement; ergo, back to ebay i go. installed the new screen yesterday, turn it on, all is well. for a bit.
now, the phone isn't currently, nor has it ever been rooted; pure stock tmo us 2.3.6. during boot, the splash screens and boot animation are gorgeous and perfect in appearance. the recovery menu is exactly as expected. android boots as you'd want it to, and then the display will do one of the following:
-work properly (rare)
-automatically turn off, capacitive buttons still lit, touchscreen unresponsive - turning it "off" darkens the cap buttons, turning it back on flashes the screen on for a half-second, then off, with cap buttons still lit (common)
-graphical corruption ("solarized" colors, completely wrong colors, pixel vomit in essence) (fairly common)
-screen tinting, blue most often, followed by pale yellow, then greenish, then red (almost constant)
-screen inversion - the display will show as rotated 180 degrees; grabbing a framecap in ddms shows it right way up. touches are also inverse; you have to touch where the onscreen element would be if it were displayed properly instead of where the element is; e.g. a button on lower-left will display in the upper right, upsidedown, but the screen registers the button when you touch the lower-left portion of the screen. (quasi common, equally infuriating and hilarious)
none of these problems will show up in a screenshot at all.
i can reliably reproduce any of the above by simply adjusting the screen brightness. this will, quite literally, cycle through every possible defective display mode randomly for a split-second before moving on to a different one as long as you move the brightness slider.
MOST of these issues are transient and are either fixed (temporarily) or replaced with a different listed issue if you lock/unlock the display. it feels like a hardware issue what with the solarizing and color horrors, but is acting like a software issue, considering that recovery and boot are perfect and have never displayed any of these issues. i tried gently flexing and stressing the case in areas that might be a weak connection point, but can't get it to bug out that way.
in no way am i suggesting that i didn't screw something royally in the reconstruction stage, but i tore down and rebuilt that phone 4 times with identical results, so i can guarantee it's not some loose ribbon connector or zif socket.
i beg of you, great minds of xda, what the balls did i muck up this time? any hope for a fix? are there different panels, drivers, something?
thanks in advance
OK, if your screenshots appear normal, then your phone appears to be working correctly!
or at least it thinks it is we can conclude that it isn't the rom, kernel, or anything that you can blame the phone for going screwy.
Try buying another screen??
The ribbon connector might be broken?
yeah, these were what i figured what my options were. it just seems odd that the boot process and recovery menus have error-free displays while only the full android os doesnt. oh well, i'll probably just have to make a stink about it on ebay or something.
thanks for reading
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
lumin30 said:
You might try a fresh flash before getting a new screen to see if it is indeed a hardware issue. If you want to try that follow the second link in my signature. You will not need to flash bootloaders since you are currently on KJ6.
Click to expand...
Click to collapse
hell, warranty's void at this point anyway, right? may as well thanks much!
welp, all went well, screen was perfect through the whole heimdall/recovery process, but the problems still exist in the os c'est la vie. at least my wife's phone is finally rooted, i suppose. thanks anyway!
Have you tried opening it back up and reconnecting?
yup, 4 times, but i guess one more wont hurt
[edit]
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
zero01101 said:
it definitely seems to be related (if not related, exacerbated by) changes to screen brightness. turning off autobrightness has helped minimize the issue, but it still presents itself semi-often during screen-off/on events. obviously nothing useful in logcat.
Click to expand...
Click to collapse
That's interesting and could very well be a hardware problem with the screen. You wouldn't see that in recovery as the OS isn't loaded to mess with the brightness in that mode.
Does it do it on-demand if you mess with the brightness slider?
stephen_w said:
Does it do it on-demand if you mess with the brightness slider?
Click to expand...
Click to collapse
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
zero01101 said:
you better believe it does. rapid fire cycles through every color until it can't take it anymore and turns off. if i take/refresh a screenshot through ddms and poke blindly at the screen at that point, it'll still take input which is a curious, difficult game to say the least.
Click to expand...
Click to collapse
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
stephen_w said:
It's that Pink Floyd screen. You're supposed to drop acid & watch the wall when that's going on. LOL j/j
Given that you're on a fresh ROM & the problem persists, I'm leaning toward a hardware issue man. Sorry.
Click to expand...
Click to collapse
as fun as that sounds, unfortunately i bet i'll end up just getting my wife a used phone on ebay or somewhere similar and using this one as a development monkey. i was assuming that it wasn't something i could fix but hoping otherwise... yeah, that worked out
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
kristoper said:
I just started having this problem. It wasn't too bad at first, just the color changes, but then it started not showing a screen at all. Changed to three different roms, even back to the stock non-rooted KJ6 and gave up. Keeping it on a steady brightness is the only way to minimize the color changing. I thought your thread had a solution but...
I may try opening it up and fixing the ribbon. But otherwise I'll keep using it as long as I can tolerate it until an S3 or a new Nexus.
Click to expand...
Click to collapse
nawp, nothing even close to a solution here i did end up buying my wife a whole new replacement phone and turned the broken one into my api10 development device. for what it's worth, yeah, autobrightness off does help a bit for when the phone is actively displaying content, but after you put it to sleep/screen off and try to turn it back on, it's a crapshoot. for a few horrifying hours, the screen was upsidedown even in recovery/boot animation and would NOT flip back to right-side-up until i ran the battery completely flat.
is no fun, 'tis truth. sorry for your troubles.
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.
Hi all. Currently running the 10.25 nightly, and I have noticed a couple strange bugs. I would have posted in the big CM10 question thread, but it seems sort of dead at this point.
First, when I turn the screen on when the phone is locked, it starts off dim for a couple seconds and then goes to the correct brightness. Not a huge problem, but definitely annoying.
Second, when scrolling through tabs or windows, and sometimes swiping up and down, I see flashses on the screen of what looks like code or the matrix or something. This is especially pronounced when using Handcent, where whenever I push a key I see the keyboard flash on the screen above the normal keyboard, making scrolling through messages and the message list quite annoying.
Any help would be greatly appreciated.
Are you using auto brightness?
And, is the second thing you are talking about screen tearing?
Are you using a custom kernel or stock
Sent from my HTC One XL
ul49 said:
First, when I turn the screen on when the phone is locked, it starts off dim for a couple seconds and then goes to the correct brightness. Not a huge problem, but definitely annoying.
Click to expand...
Click to collapse
I'm mostly a Sense guy. But the AOSP base ROMs I've tried all do this. When you turn the screen on, it kinda "fades in" instead of turning on right away to the set brightness (this is with auto brightness turned off). Seems completely intentional, and I personally couldn't find a way to turn it off (as I don't like it either).
absolutelygrim said:
Are you using auto brightness?
And, is the second thing you are talking about screen tearing?
Are you using a custom kernel or stock
Sent from my HTC One XL
Click to expand...
Click to collapse
Yes I am using auto brightness. I'm using the custom kernel that comes with CM10. It's sort of like screen tearing, but it's more of a flicker in the background and is not always noticeable. Much more obvious in Handcent, though that might be a separate issue since it's the keyboard flashing in the background.