I've been digging into the "touchkey backlight issue" and would appreciate some help understanding how it worked (or didn't) on GB-based ROMs. If you are running GB (rather than "I remember..."), understanding how the proprietary Samsung code handled the backlight, both in auto- and manual-brightness mode, under a variety of screen timeouts, USB plugged, AC plugged, etc., would be great. Information like this can also help me guess where Samsung has their proprietary code, rather than wading through 150 MB of ROM.
Reports like,
The backlights go out after a couple seconds
Click to expand...
Click to collapse
aren't terribly helpful.
The backlights turn on when I tap the screen anywhere, then turn off after a second or two (it seems to vary from time to time), when I'm running on batttery, with auto-brightness on, and in normal indoor home lighting. They don't turn on with the same settings if I am outside.
Click to expand...
Click to collapse
or the like is much more helpful.
(I made that stuff up. I don't remember how they worked under GB.)
Oh, let me know which ROM you are running as well.
No promises, but knowing where we came from can help determine where we might go.
Thanks!
P.S. This is a common problem with Samsung phones -- You'd be amazed at the number of inquiries about the touchkey backlight.
I can check these later again a stock S4G I have still on GB, but on my flashed one with FB's AOKP using your brightness for the screen fixes, this is what I just tested.
-Turn Autobrightness off, screen sleep to 5 mins, brightness about 30%, backlights stay on for the whole 5 mins.
-Turn Autobrightness off, screen sleep to 5 mins, brightness about 100%, backlights stay on for the whole 5 mins.
Turn Autobrightness On, screen sleep to 5 mins, filtered/raw 34/34, backlights stay on for the whole 5 mins.
Turn Autobrightness On, screen sleep to 5 mins, filtered/raw 2000/2000, backlights go out as soon as the raw value hits past 150, your default to turn them off.
When I remove it from a bright light and the raw goes back down to below 50 though, the autobrightness does not dim the screen, I have to put it to sleep and wake it up to get it to actually drop the brightness..
Moving the phone between bright light and dim light, the buttons do go on and off corresponding to the 150, but the screen doesn't dim or go brighter.
If the buttons are off from being in bright light, and I press one, they go on and stay on and moving out and back into bright light, they seem to stay on most of the time.
So it seems your code for the autobrightness can turn the buttons on and off, by the 0 value for the correct RAW value. It's spotty though and the autobrightness doesn't adjust itself to the correct level until I sleep/wakeup again. I can have autobrightness on and move my phone from dark to light and the buttons go on and off by the brightness of the light but the screen doesn't.
I will check this same test against a stock GB and see what happens.
This is for gingerbread:
Sometimes the key lights don't turn on at all while using the keyboard, and even when you are pressing keys in the keyboard. It might not even be caused by the keyboard being out, maybe it's the way I hold my phone while I'm typing that causes the auto brightness to go down.
This doesn't occur all the time though. Also, sometimes it doesn't turn on at all even when touching the screen (maybe for a minute) then they turn back on.
It seems that the key lights have some situations where they decide to ignore touches and stay off, I'm still trying to figure out when this is. Again, it mostly happens when the keyboard is out. Maybe it has something to do with auto brightness. When toggling auto brightness on and off, the key lights immediately turn off and stay off for about 30 seconds. This makes me think that the soft key lights even on stock are buggy
Thanks getochkn; great report for ICS!
That pretty much agrees with what I am seeing on ICS and what I would expect from the code.
The buttons "don't play nice" with the Android world as it seems they turn themselves on when you touch them (probably hardware control), and the present TeamAcid ICS driver turns them on when it (re-)initializes. The Android world won't change the brightness of any of the "lights" if it thinks that the level is already set. For example, if it thinks the buttons are off, it won't try to turn them off again. I believe this is why with auto-brightness on the buttons sometimes won't turn off. I'm still wading through PowerManager service to understand how the code is trying to handle them when in "manual" brightness mode.
Definitely looking forward to your results for GB, though pisherthefisher's report that they seem "buggy" on "stock" for him suggests that Samsung might not have gotten it right even there.
Seems to be no way to fully disable them eh? Then we could just use the JB style nav bar like already in FB's AOKP which lets us set color, brightness, custom icon, etc but with the other buttons still working physically, lights on or not, it seems not worth it as you will still hit the sammy buttons, especially if the light is off but the buttons still physically work.
I can "hack" them off, but I'm trying to solve the problem more generally and in a way that keeps the TeamAcid framework able to easily track the CyanogenMod upstream. I might build a "Hefe Kernel Of Darkness" if I can't find something this week.
Posted from my SGS4G, thanks to Team Acid development
Ah. Might be an option, go all softkeys via the ROM instead.
I know OT, but any idea why the autobrightness doesn't seem to fully kick in sometimes either? I can be in the custom screen to view the raw values and see the numbers drop but not the screen brightness until i sleep/wakeup. The backlights will go on/off according to the raw value but not the screen brightness. lol.
Going to go see how my stock one works and I'll report back.
On the auto-brightness not seeming to work, you might want to check the auto-brightness thread in the dev section. I am guessing it might be related to the "Allow light decrease" and "Decrease hysteresis" settings.
jeffsf said:
On the auto-brightness not seeming to work, you might want to check the auto-brightness thread in the dev section. I am guessing it might be related to the "Allow light decrease" and "Decrease hysteresis" settings.
Click to expand...
Click to collapse
Thanks. I forgot the settings after reinstall.
On GB, the lights seem to go out at some value (no custom, can't tell) but do come back on when you press them and then seem to stay on randomly. lol.
FB's AOKP comes with BLN control which does seem to use the lights as an indicator light for lockscreen notifications, so they seem to be able to be controlled from that SW. Not sure if that helps or not?
Hefe kernel of darkness sounds awesome, it would be cool to use the sgs4g like a galaxy nexus
Setting the backlights to 0 on all light settings, the backlights go out, but as soon as you go to sleep, and wake up, the lights come back on and don't go out even though the custom panel shows the state of them at 0. Turning auto-brightness off/on then turns the lights off, so the state is not being restored at wake. Of course touching one of them turns them on and they stay on again unless i toggle off/on again.
Yes, right now driver resume turns on the backlights, but Android thinks they are already off, so it doesn't turn them off based on the auto-brightness settings. Touching the keys is similar, but it seems to be hardware that is turning them on.
Posted from my SGS4G, thanks to Team Acid development
Well I'll test a darkness kernel if you get one going. lol. Use the softkey feature in AOKP. I've already been playing with and have it setup, I just don't want to hit the sammy buttons which I brush sometimes by accident, nor have the lights come back on after wake up, so if can disable them fully in the kernel, that would be cool.
Hefe Kernel Of Darkness in Post #2 of the Hefe Kernel thread
jeffsf said:
Hefe Kernel Of Darkness in Post #2 of the Hefe Kernel thread
Click to expand...
Click to collapse
no wifi. lol. Doesn't even turn on.
Yeah, something is flaky. I'll look at it again tonight.
Posted from my SGS4G, thanks to Team Acid development
jeffsf said:
Yeah, something is flaky. I'll look at it again tonight.
Posted from my SGS4G, thanks to Team Acid development
Click to expand...
Click to collapse
Works good other than that.
Can the lights be disabled with the keys functional?
Sent from my SGH-T959V using xda app-developers app
m4127440 said:
Can the lights be disabled with the keys functional?
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
The best we can do right is only have them turned on while pressed with the hefe kernel of darkness. Check out the hefe kernel thread in the development section, second post
Sent from my SGH-T959V using xda app-developers app
We?
Related
Anyone else's auto-brightness not working? Mine doesn't
how?
How do you know? Or what have you noticed?
Rio
I don't think that mine works either, one of the first things I noticed.
Sent from my Transformer TF101 using Tapatalk
rio911 said:
How do you know? Or what have you noticed?
Rio
Click to expand...
Click to collapse
Well it never seems to change. To confirm I put it on the lowest and then on auto, it stayed on the lowest. I then tried putting it on the highest setting and then putting it on auto but again it stayed the same.
Surprised it took me so long to realise..
It takes an average reading of the light it senses over about 30-45 seconds when it's on auto and responds accordingly on mine. To check yours put a torch on over the sensor for about 30 secs and if nothing changes yours definitely isnt working properly. However I normally have it set to a manual amount instead of auto to save on battery etc.
Edit: Just tested again with a torch and this time it took 45 seconds to change... odd.
Where is the sensor located? Does it use the front camera?
Sent from my Transformer TF101 using Tapatalk
brachiopod said:
Where is the sensor located? Does it use the front camera?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
It's the thing just over an inch to the left of the front camera.
I see it now. I put a bright LED flashlight over it while in a darkened room for a couple minutes and the screen did not change brightness. However, it does appear to have an IR filter over it, so maybe it is mostly sensitive
Sent from my Transformer TF101 using Tapatalk
Oops not used to the kb, sensitive to Sunlight.
Sent from my Transformer TF101 using Tapatalk
With it on full brightness (before changing to auto) I had my finger over it for a while but it didn't change. Then I left it on full brightness for about 10 minutes in a fairly dim room and no change either.
Just tried with an led torch here as well and it did sod all this time. Nothing changed. Try with another light source if you get the chance. The update rate on the auto setting is too slow really tbh. There are loads of apps in the market to test the sensors too btw.
@Case0
If it's not on auto mode it wont change at all.
Possibly it only checks at certain times, such as when an app starts. I bet that it reads IR so only certain light sources might work.
Sent from my Transformer TF101 using Tapatalk
I installed a couple of sensor tester applications, and none of them can report a value from the sensor. Sensor list 2.1 detects the sensor as a lite-on al3000a ambient light sensor, but no value is returned. Not sure if this means that it is not working, or if these apps just can't read that particular sensor.
It doesn't work for me either, although I haven't tested it since the new firmware upgrade. Maybe we have a bad batch.
I never was a fan from autobrightness. I always set it to middle.
Until I got a Nexus S and noticed how awesome it is that it changes the brightness, since otherwise you can not read the display outside. It also changes instantly.
Try this. Download and install Advanced Task Killer, then Sensor Test by Atmoworker. Kill all processes to make sure the sensor isnt in use by something else. Then run the sensor test. If your value for the light meter doent move, then there's something wrong for sure, or it's in use by some process that wasnt killed by the task killer.
stuntdouble said:
Try this. Download and install Advanced Task Killer, then Sensor Test by Atmoworker. Kill all processes to make sure the sensor isnt in use by something else. Then run the sensor test. If your value for the light meter doent move, then there's something wrong for sure, or it's in use by some process that wasnt killed by the task killer.
Click to expand...
Click to collapse
OK. That app does seem to read the sensor, and it does change. I didn't have to kill any tasks for it to work. It gives three readings labeled 0, 1 and 2.
0 changes from 1.0 to over 100 outside. Probably some log scale. 1 changes from -27 to over 100. 2 sits at a very small number, about 10^-45
So the sensor does work, the tablet just isn't using it properly it appears. Or something.
Ok well yeah sounds like it does work, just doesnt function the way you want it to. There are lots of apps to deal with screen brightness on the market, some free, some not so. And then there are also a few which lets it change using the camera instead of light meter. Here's a link to one to show you what I mean. https://market.android.com/details?id=org.pbxes.light2&feature=search_result I'm sure there are free versions available if you do choose this option. Good luck in finding one you like.
Well, if by "just doesnt function the way you want it to" you mean does not do anything at all ever no matter what, then yeah, it isn't working the way I want it to. Thanks for the tip, I'll see if I can find an app that works.
OK, auto brightness DOES work. I spent some time messing with it to figure it out. The auto routine started working after I did the 10 second power button off on my machine.
1) The level that you set with the slider becomes the minimum level for the brightness under auto. That's also why I didn't think that it was working, I had brightness up all the way.
2) The auto routine will adjust brightness UP within a short period of time, 10-15 seconds, if you move into bright light.
3) The routine will NOT adjust brightness down (you move into dim light) except at three points a) right before the screen saver kicks in (goes blank) or b) right after returning from the screen saver. c) you power cycle the tablet.
This means that it is quick to respond to ambient light and increase brightness, but if you have your screen timeout set long, or you keep using the tablet, the brightness will be very reluctant to adjust down. The brightness will never be adjusted lower than you set with the slider though, but it can go up all the way.
RootDim (formerly known as ScreenDim) lets you set the screen brightness on backlit screens below what the OS normally allows, which is handy for amateur astronomy where the lowest normal OS backlight setting (even with a red nightmode) leaks enough through the black pixels to damage night vision. Moreover, SuperDim lets have several brightness profiles, and to include nightmode settings (enabled by ChainFire3D or Cyanogenmod's render fx) as part of the brightness profile.
Needs root.
Public domain, source code available. In Market (search for RootDim).
Now in Market (free, no ads).
I just uploaded version 1.10, which restores low brightness settings after the screen is turned off and back on (the OS normally was restoring its brighter screen).
Works well, but seems to mess with the functionality of the notification/charge LED (Nexus One, CM7.1)
bobtentpeg said:
Works well, but seems to mess with the functionality of the notification/charge LED (Nexus One, CM7.1)
Click to expand...
Click to collapse
I assume this is when you use the other lights option to toggle these lights, or when you restore a profile, right?
In version 1.11 (just uploaded), I no longer restore other lights when a profile is loaded--this should help with your problem, as long as you don't touch the other lights. Eventually, I may add an option to choose which lights get restored from a profile.
I originally made SuperDim for setting very low backlight settings on LCDs, and so I made it not work on non-LCD screens (e.g., OLED). But I've since realized that the profile feature might be useful for non-LCD users as well, so I've released version 1.20 that supports non-LCD screens. It's in Market. While I was at it, I cleaned up the code a little, made it more javaish (I'm new to java).
My MyTouch 4G just seems to turn the screen off totally if i go below 20 brightness, it dims but then shuts off.
Doesn't work at all with Dell Streak 5
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Awesome, thanks for the Advise!
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Actually, all Screen Filter does is dim the colour of the pixels. This app actually modifies the screen backlight level. E.g. Screen Filter just makes the screen gray-er.
Also, works good on Sony Ericsson Xperia X10, but the backlight completly switches of when set to under 15.
Sent from my X10 TripNMiUI-IRIS using XDA Premium App
fifarunnerr said:
I'm sorry to say, but Screen Filter does the same, but doesn't require root.
Click to expand...
Click to collapse
Screen filter merely adds a black semi-transparent overlay across the screen, making it look dimmer.
This app adjusts the backlight, which means darker black levels on the screen.
Frosty666 said:
Actually, all Screen Filter does is dim the colour of the pixels. This app actually modifies the screen backlight level. E.g. Screen Filter just makes the screen gray-er.
Also, works good on Sony Ericsson Xperia X10, but the backlight completly switches of when set to under 15.
Sent from my X10 TripNMiUI-IRIS using XDA Premium App
Click to expand...
Click to collapse
My eyes don't care. +1 Screen Filter
lownox said:
My eyes don't care. +1 Screen Filter
Click to expand...
Click to collapse
Your eyes would probably care if you were doing amateur astronomy under a dark sky (which is the primary purpose for SuperDim). Screen Filter doesn't turn down the backlight, and on a lot of devices there is enough backlight leaking through even completely black pixels to damage night vision. You can try this experiment. Turn a backlit device to a completely black screen (maybe view a black jpg) and take it to a completely dark room. Let your eyes dark adapt. The "black" screen will in fact probably be quite grey. (If it's really black, that's probably because you have an OLED device.)
When I do amateur astronomy, I am not infrequently looking to see objects way dimmer than backlit black pixels.
I'd like to do something about the screen turning completely off issue.
To that end, I need people to do some experiments for me, and I will be very grateful (I'll also give a free full version of Force2SD as compensation for the first couple of experimenters, if you want it--just email me). The first experiment is this. Download SuperDim 1.22, now up in the Market. Press the menu key, and choose "Turn on safe mode" (you can tell safe mode is on, because next time you pull up the menu, it says "Turn off safe mode"). Now, turn brightness down to 10. Does your screen turn off?
I should warn that very low brightness levels can be very low indeed. For instance, if I am outdoors on a sunny day, I have trouble telling the difference between brightness 4 and off. So you need to be in a dark area--I recommend a room without windows and with the lights off.
If the screen does not turn off at 10, turn it down to 5, and then 1. Let me know if it ever turns off.
I am guessing that in safe mode, it doesn't turn off at all.
What safe mode does is it makes very low brightness settings not persist. So if you are in safe mode and leave SuperDim, you lose your low brightness setting.
I'd also appreciate it if people who can normally turn their brightness down to 1 could do some experiments with safe mode. Specifically, I'd like to know if moving the slider to 1 in safe mode has the same effect on screen brightness as moving the slider to 1 in non-safe mode has. (Again, if you're one of the first few experimenters and want a free copy of Force2SD, email me.)
On my Archos 43, brightness 1 is very, very dim, but the screen is still on. And I can't tell the difference between safe mode and non-safe mode, except that in safe mode, the settings don't persist after I leave SuperDim.
Tried this app on my desire HD.
Great idea, but when I reach 10 and below, the backlight doesn't get lower.
If I use the adb method (don't remember the command), I can set the backlight manually all the way down to 0.
There is no difference with or without safe mode on.
inspire 4g with coredroid V7.0 doesnt work
elmanortega said:
inspire 4g with coredroid V7.0 doesnt work
Click to expand...
Click to collapse
What happens? And does safe mode work?
I agree, doesn't work with Desire HD/Inspire 4G, safe mode only dims the brightness but no lower than normal, and only dims the brightness on the screen, regardless of your settings
kamranh3 said:
I agree, doesn't work with Desire HD/Inspire 4G, safe mode only dims the brightness but no lower than normal, and only dims the brightness on the screen, regardless of your settings
Click to expand...
Click to collapse
I found a bug. In fact, the bug is such that I have no idea how it was managing to work on my device at all! In any case, I think I fixed it. Try 1.23 (should be in Market or here) and see if it does the job. If not, I have some more ideas.
I recently purchased a nexus s and dock. I was under the impression if i used the dock only the time would show up and float around the screen. What i am getting is the dock turns on the clock app that shows the weather and the four buttons (alarm ,music etc). Do i need to download a different app to get just the time floating around? I am afraid of leaving it the way it is because I dont want to ruin the screen having the clock sit like that all night, besides that it is too bright.
I am using stock rooted 2.3.7.
Thanks.
Turns out I was being impatient. After I left it long enough it started working as expected
Evo_Shift said:
Turns out I was being impatient. After I left it long enough it started working as expected
Click to expand...
Click to collapse
For what it's worth, I use Alarm Clock Plus (here) to customize many options of the alarm. You can have it for free (ads) or pay a small amount for it. Enables you to customize a lot of settings (including timeout of screensaver and colors), set mathematical solving alarms and plenty of crazy stuff. I've never looked back since I started using it, and what's awesome is that in appearance it is the same as the built-in alarm.
I also use Alarm Clock Plus and it is highly recommended. I love the "nap" feature to easily set an alarm for a short nap by just touching the onscreen clock and selecting the time you want to sleep. As mentioned above it has a bunch of settings and no attempts were made to look all flashy
I tried out Alarm Clock Plus and really like it, especially the ability to set the screensaver to only 1 minute and that I can adjust the color/brightness of time floating around.
One thing i have noticed is that the 4 capacitive buttons remain lit when it is in the dock. Is there a way to have them off?
Evo_Shift said:
I tried out Alarm Clock Plus and really like it, especially the ability to set the screensaver to only 1 minute and that I can adjust the color/brightness of time floating around.
One thing i have noticed is that the 4 capacitive buttons remain lit when it is in the dock. Is there a way to have them off?
Click to expand...
Click to collapse
Absolutely, if you are using a kernel with one of Ezekeel mods (franco kernel, glados, trinity, steve garon stuff, mathkid's etc) and backlight dimmer you can set a timeout for the capacitive buttons to power down.
polobunny said:
Absolutely, if you are using a kernel with one of Ezekeel mods (franco kernel, glados, trinity, steve garon stuff, mathkid's etc) and backlight dimmer you can set a timeout for the capacitive buttons to power down.
Click to expand...
Click to collapse
Which app did you mean? The buttons are not lit because of a notification, they just turn on for some reason when the phone is docked. The settings in the BLN app don't seem to do anything except time out when you have a notification. I need something that will allow the cap button to turn off when the phone is docked when there are no notifications present at all.
Evo_Shift said:
Which app did you mean? The buttons are not lit because of a notification, they just turn on for some reason when the phone is docked. The settings in the BLN app don't seem to do anything except time out when you have a notification. I need something that will allow the cap button to time out when the phone is docked when there are no notifications present at all.
Click to expand...
Click to collapse
Exactly what I just told you.
If you are using a kernel with Backlight Dimmer from Ezekeel, you should be able to do this.
Kernels from Morfic, Franco, Ezekeel, Mathkid and Steve Garon all offer Ezekeel mods as far as I'm aware.
You can set the Backlight dimmer options manually or using NSTools (Tweak tab).
Ahh, yes. Right in front of my eyes. I was still thinking in my old LCD terms... I thought that meant back light as in the display... Still not used to the SAMOLED screen
Thank you again
No problem. There's a lot of made up terminology and very few guides so it can get confusing at some point.
coming from htc legend and xperia mini, the led notification lights was an important feature, now i really miss it in the note, and using noled app is not the same as having actual led lights.
so i was thinking if there is a possibility to use the menu and back buttons lights as notification light ? i found that they are separate from the screen light .. so can this be done by an app or a custom rom or it can't be done ?
This idea has already been implemented for many Samsung devices. Just find a custom kernel with "BLN" Support (BackLightNotification) and then download the app (info HERE) and away you go.
Hope that helps mate
Sent from my white Galaxy Note, using Tapatalk
ages_devil said:
coming from htc legend and xperia mini, the led notification lights was an important feature, now i really miss it in the note, and using noled app is not the same as having actual led lights.
so i was thinking if there is a possibility to use the menu and back buttons lights as notification light ? i found that they are separate from the screen light .. so can this be done by an app or a custom rom or it can't be done ?
Click to expand...
Click to collapse
check bLED
after i posted this i found out about bLED and bln kernel (i didn't know what bln means) thanks for your help
There is also noLED. Not one i use but you might aswell know all the options
I've read that they all hurt battery life
i tried noLED but i didn't like it
i know that bln might drain the battery faster but it's important for me, and maybe with further development some of the current problems might be fixed
NoLed is good, doesn't require root and only uses about 3% battery when enabled (and nothing if you switch it off). You can also customize the settings for additional power saving and I managed to get it down to 1% by setting the notification to flash on and off.
My only issue with NoLed is that from time to time it gives me the sleep of death. Disable it And my issues go away - haven't had time to test whether or not SoD is down to the power saving settings.
Is there any way to disable the touch key lights on CM7? I know you can disable them with app or editing the wled file but they will turn back on all the time because CM7 ties the touch key light brightness into the brightness settings. So far its the only thing that is driving me crazy with CM7.
me2
Sent from my LG-P999 using XDA
Completely disable, not that I know of.
I know that they reset themselves every time you turn the screen on and off. Out of curiosity, why would you want to turn them off completely? Battery life isn't noticeably better, only on stock because it sets the keys all the way to the highest setting. If you don't have your display set to the highest brightness, you have nothing to worry about with the touch keys.
it is too bright.i like to set auto display
Sent from my LG-P999 using XDA
and i wanna led to be 0.1mA always in cm7
Sent from my LG-P999 using XDA
theking_13 said:
Completely disable, not that I know of.
I know that they reset themselves every time you turn the screen on and off. Out of curiosity, why would you want to turn them off completely? Battery life isn't noticeably better, only on stock because it sets the keys all the way to the highest setting. If you don't have your display set to the highest brightness, you have nothing to worry about with the touch keys.
Click to expand...
Click to collapse
I dont like them on when im playing games andni just dont need them. I know where the buttons are without the lights on.
You should be able to disable the LED touch lights by doing the following:
1. Settings -> Cyanogenmod Settings -> Display -> Automatic Backlight -> Edit Other Levels
2. Click "Edit other levels..."
3. Under "Buttons" set the four values of "255" to "0"
4. Click "Save & apply"
Although under CyanogenMod 7, as soon as you adjust the brightness the LED touch lights will come back on again, though this is fixed by simply turning your screen off and on again.
I have not used CyanogenMod in a while so this is just off hand and could be wrong.
If you set your screen brightness all the way down, that will change the touch key brightness. If you change to automatic brightness it will keep the key brightness but change the display.
Sent from my LG-P999 using XDA
stormageddon said:
You should be able to disable the LED touch lights by doing the following:
1. Settings -> Cyanogenmod Settings -> Display -> Automatic Backlight -> Edit Other Levels
2. Click "Edit other levels..."
3. Under "Buttons" set the four values of "255" to "0"
4. Click "Save & apply"
Although under CyanogenMod 7, as soon as you adjust the brightness the LED touch lights will come back on again, though this is fixed by simply turning your screen off and on again.
I have not used CyanogenMod in a while so this is just off hand and could be wrong.
Click to expand...
Click to collapse
Thats not an option in cm7.2
Joe333x said:
Thats not an option in cm7.2
Click to expand...
Click to collapse
As far as I can tell, not in CM 7.1 either. Unless its just a EB issue.
Sent from my amazing G2x running EaglesBlood and Faux.
Joe333x said:
Thats not an option in cm7.2
Click to expand...
Click to collapse
As I said, I have not used CyanogenMod in a while. It was a stab in the dark. However I did some searching around and found this little app in the Play Store that you might want to take a look at. Here
It does exactly what you want. I tested it and I was able to turn the lights off completely and you can set it to enable on boot.
stormageddon said:
As I said, I have not used CyanogenMod in a while. It was a stab in the dark. However I did some searching around and found this little app in the Play Store that you might want to take a look at. Here
It does exactly what you want. I tested it and I was able to turn the lights off completely and you can set it to enable on boot.
Click to expand...
Click to collapse
I remember this option on stable 7. 1 on the Vibrant, but haven't seen it on any rom on the G2x.
And good job linking to the SAME apps I mentioned. Lmao
Sent from my amazing G2x running EaglesBlood and Faux.
No app can fix this. All the apps do is edit the wled which cyan sets on its own every time you turn the screen off or adjust the brightness. Example: You download an app that adjusts key brightness, you use it to adjust brightness and it works. Now you turn the screen off and on, that adjustment you made is now set back to where cyan had it. Same thing if you edit the wled. This is something that needs to be fix deeper down than an app or editing the wled file. Its something that needs to be edited within cyan it self.
theking_13 said:
I remember this option on stable 7. 1 on the Vibrant, but haven't seen it on any rom on the G2x.
And good job linking to the SAME apps I mentioned. Lmao
Sent from my amazing G2x running EaglesBlood and Faux.
Click to expand...
Click to collapse
Lol, I didn't see you post that. Great minds think alike?
Sent from my LG-P999 using xda premium