I flashed fluxi kernel on CM9, then installed a newer CM9 build which replaced the kernel, and now the capacitive buttons don't light up when I touch them or the screen.
Any solution?
Under Settings>Advanced>Sensors "Enable keys backlight" is enabled?
Bye
itaijac said:
I flashed fluxi kernel on CM9, then installed a newer CM9 build which replaced the kernel, and now the capacitive buttons don't light up when I touch them or the screen.
Any solution?
Click to expand...
Click to collapse
Hold menu button for a few seconds and then let go.
Thanks. It is enabled and holding the menu button does nothing.
Sent from my GT-I9100 using XDA
Did you leave the phone on charger overnight? I did.
Now, most of the times, my capactiive keys do not respond. Sometimes they do.
When they are not working, they do not light up either no matter how many times they are touched. However, if i touch the screen area at that time, they light up according to duration (like 1.5 seconds). But still, touching them does not make them work.
I have tried the screen code *#2660# to update the fw of capacitive soft keys. Made no difference.
I've always been charging it overnight, the lights stopped working after flashing CM9 over CM9+fluxi kernel.
Also, the buttons work, the light behind them doesn't.
Well imo, you should flash stock kernel and start over i.e. root, then flash CM7 latest nightly. Stay with it for a few days.
I suppose full wipe should fix it, I was hoping for something else, like messing with the liblights file
Try siyah kernel. Using ext tweaks you can set a timeout for the capacitive button. It lights up when you touch the screen or the button not like the other kernels where you need to touch the button so that it would light up.
Edit: In case you try siyah kernel, make sure you download the one for sgs2 not sgs3.
Sent from my GT-I9100 using xda premium
Thanks but I might as well flash fluxi kernel. The problem started because I wanted to return to CM9 kernel (hence flashing CM9 over CM9+fluxi). I'm looking for a solution that will allow me to stay 100% CM9, without full wiping my phone.
itaijac said:
Thanks but I might as well flash fluxi kernel. The problem started because I wanted to return to CM9 kernel (hence flashing CM9 over CM9+fluxi). I'm looking for a solution that will allow me to stay 100% CM9, without full wiping my phone.
Click to expand...
Click to collapse
I think with cm9 kernel (for now maybe) you don't have the option to have a time out for the capacitive buttons or similar to what i have explained earlier (the one where when you touch the screen the capacitive button lights up blah blah). Either it is permanently on or it is permanently off (using the 2nd poster's advice).
Sent from my GT-I9100 using xda premium
"Enable keys backlight" is ticked. When I untick and then tick it again, the lights work only as long as I don't turn off the screen. If the screen is turned off and on again, no lights as usual, though the box remains ticked.
itaijac said:
"Enable keys backlight" is ticked. When I untick and then tick it again, the lights work only as long as I don't turn off the screen. If the screen is turned off and on again, no lights as usual, though the box remains ticked.
Click to expand...
Click to collapse
It's been a long time since i tried stock cm9 kernel. During that time the button lights are always on. I think i tried it one time and you're right. Well, siyah is working for great for me.
Sent from my GT-I9100 using xda premium
Update: problem solved by flashing build cm-9-20120709-EXPERIMENTAL-galaxys2-VOLUMEDROPFIX-LUXRANGE.zip
Related
The one thing I've hated about DJ05, DL09, and now our Froyo releases is that the timeouts on the capacitive touchkey backlights have gotten longer and longer. In DI01 it was a couple of seconds, in DJ05 it was the length of your screen timeout, and by EB01 and beyond it's now the length of your screen timeout AND reset every time you touch *anything*.
Well, I've finally gotten around to figuring out where the change was (setScreenOffTimeoutsLocked() in PowerManagerService.smali in services.jar) and modding it back. Now, as in DI01, the keys will only light up for a few seconds after you press one. I haven't reverted the recent change of regular screen touches resetting this time after the touchkeys have gone on, though: since the baseline is very short, this isn't a big issue.
Note that the version of services.jar on which this is based is from Super Clean 2.9.2. However, a diff seems to show that the only difference between adrynalyne's services.jar and the stock EB01 is the inclusion, in the former, of the battery notification/data throttling removal mods. So it *should* work with any deodexed EB01-based framework, though I've only tested on the self-customized SC292 I'm running.
The mod does *not* interfere with BLN.
UPDATE 4/28: I've removed the previous EC01/ED01 versions because they were turning on the lights a bit too often (screen press as well as button press). Instead, here are two fixed Edify-script versions for ED01.
Evil Fascination/stock ED01 folks should use shortlight-evil341, which basically just includes the light fix and the sbrissen mods. Community ROM folks should use shortlight-community12, which has a couple of other options unique to that framework.
The new files include a permissions fix, so just install the zip and reboot. (Those installing the original file -- SC292/EB01 and Amend only -- still need to manually mount /data and /dbdata and run the fix permissions script in CWM 2.5 after installation.) First boot will take a while.
UPDATE 5/17: From version 3.5 forward, Evil Fascination folks should use the community zip as well. Evil341 is still good for stock ROM users.
UPDATE 6/13: New version (shortlight-cROM2) uploaded for Community ROM 2.0. Edify only, like the 4/28 version.
UPDATE 8/31: New version for Powerwashed (ED05). Edify only.
To be honest I like it when the keys are lit up. Especially in the dark and you're trying to hit one of those buttons. But I do agree that they shouldn't be on after you lock the screen....
Syn Ack said:
To be honest I like it when the keys are lit up. Especially in the dark and you're trying to hit one of those buttons. But I do agree that they shouldn't be on after you lock the screen....
Click to expand...
Click to collapse
Do your keys really stay lit up after you lock the screen? What rom are you using these days?
I'm running Adyn's latest superclean (2.92) and jt's ec10 kernel (TW_kernel-0327-2) and haven't seen this issue. I'm wondering if there is a bug somewhere that is causing this issue with other people.
I don't have a problem with their time staying on..I do wish they weren't so bright..
Has anyone noticed that the in-call "buzz" is related to the soft-key lights being on? I haven't used a Touchwiz ROM in a while (including Superclean), but this is something I've noticed running other ROMs.
This fix might help with that.
Awesome!! Thanks, I can't stand the long backlight time. This is perfect!
DeezNotes said:
Has anyone noticed that the in-call "buzz" is related to the soft-key lights being on?
Click to expand...
Click to collapse
Yep.
It's funny, a bunch of people like the long lights -- and it's their complaints, I think, that made Samsung edit the behavior in later firmwares. But I'm also sure there are a bunch of people who don't, so now there's a choice.
I also think if the lights were as muted as they are on, say, a Captivate, things might be different.
I tried this out. If I wake up my phone the lights stay off but as soon as I press one they never go off until the phone goes to sleep again.
Sent from my Fascinate
Superclean 2.9.1
EB16 voodoo kernel
EA28 radio
No current theme
s44 said:
I also think if the lights were as muted as they are on, say, a Captivate, things might be different.
Click to expand...
Click to collapse
Yea, the lights help locate the buttons in the dark, but they are so bright that they almost overpower the screen. As handy as they are, I'd rather do without them all together personally. But this is a great compromise.
scarfman4 said:
I tried this out. If I wake up my phone the lights stay off but as soon as I press one they never go off until the phone goes to sleep again.
Click to expand...
Click to collapse
You sure it flashed? This is basically the standard behavior.
s44 said:
You sure it flashed? This is basically the standard behavior.
Click to expand...
Click to collapse
I believe so. I booted into CWM, wiped data and cache twice, flashed it and rebooted.
Sent from my Fascinate
Superclean 2.9.1
EB16 voodoo kernel
EA28 radio
No current theme
Yikes, you wiped data!
Don't do that, this is a tiny framework change. (I think I'll add that to the OP.)
Not sure what could be off -- I assume the framework didn't change between 2.9.1 and 2.9.2. You used Red clockwork and not Orange, right? Maybe try reflashing...
(Since you're also in the SC thread, note that flashing any ROM will undo this change.)
Thanks! I have been looking for this!
Superclean 2.9.2
EC10 voodoo
s44 said:
Don't do that, this is a tiny framework change.
Click to expand...
Click to collapse
It worked perfectly for me, and I didn't wipe anything - data, cache or dalvic.
thank you very much s44, I've always wanted this!
This by far is the best mod yet. Not to dis the other great developers but I really hate that the backlights are brighter than my screen and always on.
Sent from my SCH-I500 using XDA App
s44 said:
Yikes, you wiped data!
Don't do that, this is a tiny framework change. (I think I'll add that to the OP.)
Not sure what could be off -- I assume the framework didn't change between 2.9.1 and 2.9.2. You used Red clockwork and not Orange, right? Maybe try reflashing...
(Since you're also in the SC thread, note that flashing any ROM will undo this change.)
Click to expand...
Click to collapse
My mistake, I didn't wipe data, only cache and dalvik (that's what I get for typing in a hurry).
I have Red clockwork, the latest from 3/30. I'll try again after my battery finishes charging.
Bizarrely, the lights seem to revert to "always on after touch" mode while the screen is in power-low super dim mode. Not sure if or how I can do anything about this.
s44 said:
Bizarrely, the lights seem to revert to "always on after touch" mode while the screen is in power-low super dim mode. Not sure if or how I can do anything about this.
Click to expand...
Click to collapse
I bet that was why it wasn't working for me. I was only at about 5% battery when I tried this.
Works perfectly for me.
Nice job.
Also just a heads up for any noob. My first reboot after took extra long but went fine. No problems.
Sent through mental telepathy
Tesla works ok.. Except when the screen turns off
When it does, the LED flashes, and then after a few seconds the phone crashes and I have to hold the power button to get it to power back on
Sent from my GT-I9100 using XDA Premium App
Yeah same issue here, I just set the option in TeslaLED to always keep the screen on.
Hi, I'm the dev of TeslaLED. I don't have a Galaxy S2 yet. Can some of you guys test this beta:
http://forum.xda-developers.com/showthread.php?t=1133393
Once installed if Auto isn't working well can you try manually setting the different LED Methods and seeing if any of them work well?
Thanks,
-Kevin
I have a question about the proximity sensor on the galaxy s2, mine is lit all of the time even when I press the power button to shut the screen off. Is this normal? I am running SHOStock 1.9.2 and Slyah 2.6.12 I have reflashed a couple of times and cleared the cache.
One more thing I think I found a possible bug in the flashlight toggle, if you rotate the screen with the flashlight on the toggle shuts off but the light stays on so you have to press the toggle twice to turn the light off.
Sent from my SAMSUNG-SGH-I777 using XDA App
I'm running SHOStock 1.9.2 and have neither of these problems. I even intentionally tried to get the flashlight toggle to break, but it work regardless of the orientation.
I'm not sure how long the sensor has been lit since it is so dim you can only see it in a dark room but I'm pretty sure it wasn't on the stock rom and maybe the first SHOStock rom I loaded which I believe was 1.9.0. The flashlight toggle issue has been there on all three SHOStock roms I have loaded.
Sent from my SAMSUNG-SGH-I777 using XDA App
I can't speak for the previous SHOStock versions as my first was v1.9.2.
I was coming from UCKH7 Stock (w/ Slyah 2.6.12 kernel). I did a full wipe and flashed v1.92.
I've only been running it for 3 days now, but overall i'm pleased. I did notice the following (not really issues, but a little annoying).
1. I had a random reboot within the first 24 hours of flashing.
2. I don't really care for the Auto Brightness changes (Lowered Auto Brightness a little and added 2 levels that make the changes less abrupt). I use Auto Brightness exclusively and it seems to low and a little choppy when changing.
3. I've gotten stuck in screen capture mode (home + power) twice. I know the screen capture is a feature, but I've got it to stick where I only need to press the power key (not the home + power combo). I'm not sure if this is a feature or a bug, or maybe I'm just a noob.
tikcolg said:
I can't speak for the previous SHOStock versions as my first was v1.9.2.
I was coming from UCKH7 Stock (w/ Slyah 2.6.12 kernel). I did a full wipe and flashed v1.92.
I've only been running it for 3 days now, but overall i'm pleased. I did notice the following (not really issues, but a little annoying).
1. I had a random reboot within the first 24 hours of flashing.
2. I don't really care for the Auto Brightness changes (Lowered Auto Brightness a little and added 2 levels that make the changes less abrupt). I use Auto Brightness exclusively and it seems to low and a little choppy when changing.
3. I've gotten stuck in screen capture mode (home + power) twice. I know the screen capture is a feature, but I've got it to stick where I only need to press the power key (not the home + power combo). I'm not sure if this is a feature or a bug, or maybe I'm just a noob.
Click to expand...
Click to collapse
You are not the only person having an issue with screen cap, tho I do believe it is due to the kernel you're running and not the Rom. A quick search should pull up a bunch of info for you
Sent from my SGH-I777
S2monkey,
Thanks for the tip. I'll do a search and see what I can dig up.
Sent from my SAMSUNG-SGH-I777 using XDA App
My phone stopped rotating so I flashed back to 1.9.1 (only version I had on my phone at the time). The orientation problem was fixed and I also noticed the proximity sesor was no longer lit. I flashed 1.9.2 and the sensor is lit again, reverted the kernel back to 2.6.11 with no change then flashed the 1.9.1 ROM and the sensor is still lit. I have no idea what caused it to go out the first time I reverted back to 1.9.1 or how to proceed. Does it really make any difference whether it is lit or not? I would think it would impact the battery life so any thought or ideas would be appreciated.
Sent from my SAMSUNG-SGH-I777 using XDA App
Hey guys
I just recently noticed that my Amaze capacitive buttons light has been staying on all the time. Even when I press the power button once and the screen turns off. Sometimes while the screen is off, the lights in the button seem to flicker. When I power off the phone completely, it turns off but the button lights stay on. Only when I take out the battery do the lights turn off. I tried using the screen filter app that can turn off the backlight for these buttons but it didn't help. This started happening after I flashed the CM10 nightly. When I switched to Speed Rom 8.0, the problem still continued. I installed Android Revolution Rom recently and the problem hasn't gone away. Any one know how I can solve this problem?
On speed rom 8.0 u have a tweak to turn them off completely or download kernel tuner and turn the capacitive light to 0%
I think there is also a modification you can make to turn them off in the build.prop I think. One of those scripts I can't remember which.
Sent from my Amaze 4G using xda app-developers app
lamortcroix said:
I think there is also a modification you can make to turn them off in the build.prop I think. One of those scripts I can't remember which.
Sent from my Amaze 4G using xda app-developers app
Click to expand...
Click to collapse
Already tried the mod and didn't work. Lights remain on. Even did the tweak that Speed Rom has and that didn't do anything either.
OK on speed rom 8.0 here is what you have to do click on energy tweaks, misc, capacitive light, always off, then click on reboot on top right corner check out the pics I made for u...
Sent from my HTC Ruby
ted619 said:
OK on speed rom 8.0 here is what you have to do click on energy tweaks, misc, capacitive light, always off, then click on reboot on top right corner check out the pics I made for u...
Sent from my HTC Ruby
Click to expand...
Click to collapse
appreciate you going through all that work to get the screenshots, but I did exactly that in speed rom and it didn't do anything to the lights. I am running Android Revolution Rom now though.
if you still have the issue try this https://play.google.com/store/apps/details?id=com.deskangel.kblight&hl=es
i use it for remove screen bleeding from capacitive buttons specially in the night or dark places e_e
My 32Gig TF201 is running AndroWook 2.3. I've spent quite a long time on stock (wth root when that was possible) and then tried AndroWook and Pac. One thing I've noticed all through the various ROM versions that I'd love to resolve (but could understand if it ain't) is that its behaviour when opening it when connected to the keyboard dock. Sometimes after a small and acceptable delay the screen comes on, at other times nothing happens until the power button is pressed and even then sometimes a rather long (a couple of second lag) occurs. Every so often while holding the power buttong with no effect the screen will come on with the power menu displayed.
Is there any way to make it come on more reliably, that the screen comes on after a consistent and short period of time when the lid opens and the power button is pressed?
iamroddo said:
My 32Gig TF201 is running AndroWook 2.3. I've spent quite a long time on stock (wth root when that was possible) and then tried AndroWook and Pac. One thing I've noticed all through the various ROM versions that I'd love to resolve (but could understand if it ain't) is that its behaviour when opening it when connected to the keyboard dock. Sometimes after a small and acceptable delay the screen comes on, at other times nothing happens until the power button is pressed and even then sometimes a rather long (a couple of second lag) occurs. Every so often while holding the power buttong with no effect the screen will come on with the power menu displayed.
Is there any way to make it come on more reliably, that the screen comes on after a consistent and short period of time when the lid opens and the power button is pressed?
Click to expand...
Click to collapse
Are you using hunds kernel with 2.3 ?
flumpster said:
Are you using hunds kernel with 2.3 ?
Click to expand...
Click to collapse
Yes, with data2SD, which I'm using now (wasn't with the other ROMs.
iamroddo said:
Yes, with data2SD, which I'm using now (wasn't with the other ROMs.
Click to expand...
Click to collapse
Can you grab the kernel installer from post 2 of the thread and install hunds with data2sd from that. It has a newer kernel in it that should fix that for you.
flumpster said:
Can you grab the kernel installer from post 2 of the thread and install hunds with data2sd from that. It has a newer kernel in it that should fix that for you.
Click to expand...
Click to collapse
It seems to have sorted the issue out. Thanks!