Since I cant post in the development thread and ive seen all these people posting about the backlight not working on the buttons all you have to do is turn on automatic brightness for display and they will turn on. Hopefully someone will read this from that thread and put it over there.
Projectsk26 said:
Since I cant post in the development thread and ive seen all these people posting about the backlight not working on the buttons all you have to do is turn on automatic brightness for display and they will turn on. Hopefully someone will read this from that thread and put it over there.
Click to expand...
Click to collapse
This is not a permanent fix. It only works while screen is on. You have to do this every time you turn the screen on and it is extremely annoying.
and there's the fail haha. just wait for the end of the day today and there should be a fix out through either euroskank's cherry picked nightly builds or else steve himself. it's been fixed on the sprint version already so its just a matter of waiting for our turn.
Related
I have a serious problem.
I have HTC Evo 4G, My screen is getting dim (NOT BLANK), I cant see screen in bright sun, It's really dark.
But this happen only Sense based ROMs, but this doesn't happen with Cyanogen or MIUI.
I have tried many sense-based ROMS ( Infected, Runny, MikG, ICS,...etc).
With every Rom, I flashed it many times, sometimes with wipe everything. I though it's hardware problem why this doesn't happen with ASOP ROM. (I don't like Cyanogen, or MIUI... LOL), Also, I tried every setting related to brightness But the problem still.
I've read every thread, article about similar problem, but useless.
For additional info about my problem: after starting up my phone, Every thing is OK, but after screen off for first time the screen getting so dark.
(Only one workaround I found, Just set "Screen always on") I'm going to kill my Evo.
Please Help me, I'm getting Crazy.
Forgive my week English.
I'm not going anyway, I'll stay here, Refresh this page every 5 Seconds, till i get a solution.
Please help me.
menu-settings-display-turn off automatic brightness and turn brightness all the way up....?
Thank you for your replay.
Sorry I forget to tell you I tried this, I set brightness so high, but nothing happen.
beezy69 said:
menu-settings-display-turn off automatic brightness and turn brightness all the way up....?
Click to expand...
Click to collapse
Sorry I forget to tell you I tried this, I set brightness so high(100%), but nothing happen.
Please help me, I still waiting for replay
What kernel are you using with the sense ROMs? Have you restored any apps after flashing the ROMs? Sounds like either an incompatible kernel, or a restored app limiting brightness to save battery, although it could be hardware related(LCD or a sensor) but since you said AOSP works fine it sounds like a software issue over a hardware issue. I replied to your other thread as well and copied the response here as well in case you didn't check the other thread, for future reference one post is enough and double posting will more than likely end up getting your flamed and trolled pretty hard
-EViL-KoNCEPTz- said:
What kernel are you using with the sense ROMs? Have you restored any apps after flashing the ROMs? Sounds like either an incompatible kernel, or a restored app limiting brightness to save battery, although it could be hardware related(LCD or a sensor) but since you said AOSP works fine it sounds like a software issue over a hardware issue. I replied to your other thread as well and copied the response here as well in case you didn't check the other thread, for future reference one post is enough and double posting will more than likely end up getting your flamed and trolled pretty hard
Click to expand...
Click to collapse
sorry for double post, I thought the other place is better, and I really suffer from this proble.
It's Ok, the other post is enough.
http://forum.xda-developers.com/showthread.php?p=21324350#post21324350
Yea always remember to only post once and in the proper section or some ppl will flame you up and troll your thread ;-)
I installed cm9 after using cm7 and cant get the four buttons on the phone to light up. They are accessible but not illuminated. has anyone else encountered this problem.
Also I was wondering if the Cm7 uses more battery than cm9
You have to use auto brightness.
cm9 illumination
If you mean display auto brightness ok but when I'm outside I can't see the screen...guess ibhave to toggle back and forth. I had switched back to cm7. In your opinion is 9 worth changing to. It seems like in 7 everything is working pretty well.
Thank you for the reply
pmpic said:
I installed cm9 after using cm7 and cant get the four buttons on the phone to light up. They are accessible but not illuminated. has anyone else encountered this problem.
Also I was wondering if the Cm7 uses more battery than cm9
Click to expand...
Click to collapse
Toggling auto brightness on and off solves it. Just tinker with it..
Sent from my Incredible 2 using xda premium
cm9 illumination
Thank you....I appreciate it
Menu keys...
Ive been using the dinc2 since last July and I got used to the buttons to the point that I noticed they didn't light up, but until I saw this post, I never considered it a "problem". Since I knew where they were and didn't need to see them to use them. If they ever do "fix" this issue I hope they allow for a settings option to keep them turned off. I actually enjoy them off, in my mind its just one more security feature. I know when my wife tries to use my phone she needs to see them, and since recently rooting to CM9 I don't want her bricking my phone. Because of the unlit buttons she has stopped using my phone (she uses some cheap AT&T phone, refuses to switch to Verizon). Just throwing my opinion in the mix. Thanks for the post as well I wasn't sure it was intentional or not.
atomwes said:
Ive been using the dinc2 since last July and I got used to the buttons to the point that I noticed they didn't light up, but until I saw this post, I never considered it a "problem". Since I knew where they were and didn't need to see them to use them. If they ever do "fix" this issue I hope they allow for a settings option to keep them turned off. I actually enjoy them off, in my mind its just one more security feature. I know when my wife tries to use my phone she needs to see them, and since recently rooting to CM9 I don't want her bricking my phone. Because of the unlit buttons she has stopped using my phone (she uses some cheap AT&T phone, refuses to switch to Verizon). Just throwing my opinion in the mix. Thanks for the post as well I wasn't sure it was intentional or not.
Click to expand...
Click to collapse
I believe in the advanced brightness settings under CMSettings you can do just that. Whenever I run a CM rom, I always go to the brightness settings under edit Other Levels and set all the softkey values on the far right column to 255 so they're always the same brightness and look nice. I like the sheen they have, but I can only see it when they're close to full brightness.
If you did the opposite, set all the values to 0 and then click Save and Apply Values at the top of that screen, they should, theoretically, never turn on.
Thank you ....as I am new to a rooted phone and this forum I didn't know those adjustments were available...learn something new everyday ......
Does cm9 drain the battery alot quicker or is it unnoticeable
pmpic said:
Thank you ....as I am new to a rooted phone and this forum I didn't know those adjustments were available...learn something new everyday ......
Does cm9 drain the battery alot quicker or is it unnoticeable
Click to expand...
Click to collapse
Unfortunately, I can't answer that question for you, as my phone doesn't like our ICS builds. Until we get a leaked official kernel and some source, I'm SOL.
RegnierD said:
I believe in the advanced brightness settings under CMSettings you can do just that. Whenever I run a CM rom, I always go to the brightness settings under edit Other Levels and set all the softkey values on the far right column to 255 so they're always the same brightness and look nice. I like the sheen they have, but I can only see it when they're close to full brightness.
If you did the opposite, set all the values to 0 and then click Save and Apply Values at the top of that screen, they should, theoretically, never turn on.
Click to expand...
Click to collapse
Where exactly are these settings? Running CM7 with the same problem as the OP and can't find it anywhere. Edit: found the settings and putting them all at 255 didn't do anything. Any other ideas?
I still saw a lot of people asking about a fix for this issue on the AOKP thread. I would post this there, but I don't have the privileges as of yet. Anyways for those of you that want the physical lights on, pull down your notification bar and set the brightness on max. Press/toggle the auto brightness button on and off several times. Saw a few people say 20 times. On your last press make sure you toggle the auto brightness on, then very quickly press the power button to turn the screen off, and then quickly press the power button again to go to your lock screen. Afterwards your physical lights should be working normally again. You have to repeat this step over again if you reboot your phone, but atleast this is a temp fix for those of you that want the lights on. I did not come up with this as I found it through a search, but a lot of people are still asking for a fix so I figured I'd post it.
+1 op
Confirmed working on CodeName.
Awesome. +1
Sent from my Epic Touch using XDA Premium App
Didn't even realize they were even broken. Fixed it for me though
Thanks man I'll try it out . I've been looking for a fix for that and haven't seen one till now. I've posted a few questions in the general thread but I never seem to get an answer. Thanks for helping another noob ! I've been experimenting quite a bit with AOKP, CM9, and Codename and I was wondering why the stock task killer isn't included in neither of the 3. They are amazing especially AOKP but my battery doesn't last me through work and I'm assuming its because I have some apps running in the background. Anyone know why the devs didn't include it or know how I can install it ? Just to be clear I'm looking to install the stock task manager w/ program monitor not the task killers from the market that don't work. Any help would be appreciated. Thanks guys !
So i have been reading here alot on the Q&A and seem to have found relevant posts/threads mentioning this issue..i don't exactly know if this is isolated or its from a faulty batch or its really a stupid feature of the One X..currently i am pissed so great on this phone..sorry to some who loved this phone but this phone is PITA for me..
here are the relevant threads i have gathered..and some people discussing the same issue i have..
thread 1
thread 2
thread 3
on those threads the issue of "Sensor still staying up even the call is already done" is imminent and in one case it is using VIBER that this issue arises..well on my issue i don't have anything installed on my Phone so i am just using my stock Call app(HTC one..)and when i make calls this issue just repeats is self..
to be more precise
-when i make a call, it will turn on sensor then it will immediately turn off screen even if the phone is not even near my ear..
-after the call the sensor is still lit up so i have to make a dummy call to turn it off and on this instance the screen again shuts itself off and sometimes its hard to wake it up..
if someone can provide a solution to this much better..or can explain to me what the heck is this phone made off..and what the heck this phone is doing..i have tried almost every kernel and reverted to stock via RUU still the same friggin issue persists..
hello everyone , so i use to have this bug back to kitkat also but it wasn't happening as often as it doesnt now that i have lollipop rom installed on my galaxy tab s T705 , the issue is with touch key lights which stays on even when i have them always off from settings , they act super weird when they are in that mode , they go off few sec after screen is off and if i shake the device they go on again as it looks like they are connected to accelerator sensor or something lolz ,the solution is super easy tho just hit the power saving on and then off again and they work normally again i heard some other ppl dealing with same issue but i wanted to know if there is a perma solution for it or not , im sure its a software issue but is there a way to fix it ?
Install a custom rom like cyanogen or something stock based.
I have the same problem. I usually have it set to turn the lights off after 6 seconds, but after a couple of days they don't work anymore. I would change the setting to off, then on, then back to 6 seconds, and it'll work again. After a few more days, they stop. I haven't seen a permanent fix for this.
Sent from my SAMSUNG-SM-G925A using Tapatalk
Same for me. Would usually opt to have the buttons backlight always off, but randomly it starts actin like always on, although the settings remains 'always off'. Toggling the setting to anything else and back to always off fixes the problem temporeraly.
Im running stock swiss lollipop on my t700.
Yes, this is driving me nuts too! I hope they resolve this in the next update and soon!
Sent from my SM-T700 using Tapatalk
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
Me too have the touch key settings to always off and found the same problem.
In my case I think it only happens when I plug the Tablet to AC.
Did this happen to anyone under another circumstances?
Thanks in adavance!
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
TLAgnesB said:
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
Click to expand...
Click to collapse
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
TLAgnesB said:
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
Click to expand...
Click to collapse
Yes but you will need root.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
I heard that there's a new update available for the Tab S. (I already returned my tablet before my 30 days to get a full refund.) Did any one get the new update, and if so, did it fix the issues like this touch key light?
Hey,
I had this problem on the original KK software - upgraded to Lollipop a few days back and I still have the bug... in fact, it is even worse! Occurs more frequently than on LP.
I wouldn't mind leaving the lights on all the time, but they're so damn BRIGHT, and there's no way to adjust the backlight intensity!
Cheers,
Su
I found this solution on another forum...
If you enable smart stay, the touch key light duration will work properly.
Any further movement on this?. I've found that if I take my tab out of the book case the problem goes away. Seems like it's a bug with the case sensor.
No movement that I'm aware of. I'm really frustrated that there hasn't been a fix after all this time. I'm holding out hope that if there is ever an update to Marshmallow, that the issue will go away. Interesting observation about the case -I have a book case on mine. I'll remove it and see what happens...