Anyone else ever experience a problem with losing the backlighting on the soft keys? This is only happening on the ICS-based roms(CM9 and MIUI). If i go into settings and adjust the brightness either way the buttons light up but then are gone for good once the phone goes to sleep again. Makes no difference if auto-brightness is on or not. Any ideas?
If I'm not mistaken if you turn on auto brightness just once it will turn the lights on, but once you reboot the phone it will turn off again. That's what I remember when i was on CM9, but that was back in alpha.
Yeah I can get them to turn on by adjusting the brightness but they are gone as soon as i press sleep button. Doesn't happen in CM7.2 or stock so I know its not a hardware issue. Only really an issue when its dark.
Try putting it on auto brightness, back out of the settings, and put it in sleep. Idk if that will make a difference, but it's different then just changing the brightness.
Sent from my MB855 using XDA
Yeah I've tried that but thanks FC for the replies.
No problem sorry I couldn't help. I'm not on CM9 right now, so there is no way I can test it myself.
Sent from my MB855 using XDA
:S auto-brightness seems to do the trick for me and most of us out there having this issue, badluck4u.
Related
Is there any program or other way do turn off the screen LEDs for example when docked at night? LEDs Hack from the market has an option for Hero with Froyo. Have tried that and it works except the row of LEDs with the home menu back and search buttons. I emailed the developer, but didnt know if anyone here had any solutions. I'm running KF v35 btw.
sorry double post
Why don't you just turn the face of the phone down? That's what I do and the lights don't bother me anymore. The speaker for the alarm is on the back of the phone anyway.
Sent from my FroyoEris using XDA App
That's what I do now, but I was looking at replacing my clock on my bedside table with a dock that would hold the phone upright so I could see the time. I can keep the display on, but wanted the bright lights on the front off. With the program I mentioned, I can turn off all LEDs except the white ones behind the keys mentioned.
http://www.amazon.com/Seidio-Innodo...UTF8&coliid=I3NXBLD8N3TSV9&colid=R3NHEZ8B3HKA
Oh. I didn't quite understand what you were trying to do. I'll look into it and see what I can find.
Sent from my FroyoEris using XDA App
I was trying to use this app with some success. I tried all the different phones. One of the first times I tried it, the LEDs all went out and would not come back on. Did a reboot and dalvk wipe which restored the LEDs. The Hero version can stop all LEDs except the leds i mentioned. Thanks for the help.\
http://www.androlib.com/android.application.net-geekherd-softbuttonshack-wmjD.aspx
please post if you find a solution, i have the same desire...
Still haven't heard back from the developer. I will let you know if i can find something else online.
also found this program: http://www.andbot.com/apps/tools/simple-led-toggle/com.squakmt.SimpleLedToggle but it states it will not work on verizon droid phones. :-(
my workaround. I can use http://www.androlib.com/android.application.net-geekherd-softbuttonshack-wmjD.aspx to turn off the leds except the lights as mentioned above. under settings->cm->userinterface->auto backlight->use custom to "on" ->edit other levels set all of the buttons column to "0". This will turn off the front lights i was referring to whenever the brightness is set to auto. I use the powercontrol widget and set brightness to auto when I want to have the lights off and to low when I want the brightness down but front lights on. It would be awesome to have an app like a toggle to turn the leds off combining the leds hack and the cm setting. unfortunately, i can only write code in html and some flash and java and even those skills are getting rusty...lol.
edit: with the program listed above, phone set to sprint hero, top led, bottom led, and trackball leds selected the leds will all go out. however, the trackball will not blink with this setting. when option to turn leds on is selected, the leds come on as they should after a few minutes.
I say save your $25 and prop that mofo up, with a sock or something covering the bottom lights.
Sent from my Eris using XDA App
Well, the program is free, but my dock was about $25 and broke after the first day. Lets hear it for poorly made parts. I contacted the seller through amazon. We shall see what happens.
So something I'm noticing is when removing my phone from the charger, sometimes the screen auto off does not work. The screen will dim like it wants to turn off, but then will just sit dimmed and never turn off. Anyone have ideas? I was thinking some sort of app causing it, but I haven't installed anything new.
Only new thing I've done is update to Perfect Storm 1.4.
I've had this issue too. I'm running perfect storm 1.4 aswell. It only happens to mine when Titanium Backup runs a scheduled backup. A restart fixes it. Maybe I'll link to this thread in chingy's development thread and see if he has any thoughts?
travishamockery said:
So something I'm noticing is when removing my phone from the charger, sometimes the screen auto off does not work. The screen will dim like it wants to turn off, but then will just sit dimmed and never turn off. Anyone have ideas? I was thinking some sort of app causing it, but I haven't installed anything new.
Only new thing I've done is update to Perfect Storm 1.4.
Click to expand...
Click to collapse
Did you guys flash the auto brightness zip yet?
Sent from my Incredible HD
Droid_ALM2ND said:
Did you guys flash the auto brightness zip yet?
Sent from my Incredible HD
Click to expand...
Click to collapse
I did not. I like the auto brightness the way it comes in 1.4. The issue (at least for me) is that if TB makes a backup while my phone is plugged in, then the only way the screen shuts off is when I manually sleep it by pressing the power button. Once I restart all is good. Not a huge deal as I only have TB scheduled to backup twice a week right before my alarm goes off in the morning so I just reboot when I wake up. Just thought someone might know how / want to fix the bug...
Yeah mine has nothing to do with auto brightness. Also, mine is not a result of TB, I don't have auto backups set.
It's just randomly, after a full night of charging, certain times it just won't turn off on its own. Once rebooted, working fine as stated above.
i think i have the right idea here. i installed the helly bean rom a couple days ago and absolutely love it so far, however the home, search, menu, back buttons all stay lit if a notification for txt or email happens while its sleeping. for further clarification in case some dont understand what i mean, say i hit the power button to go into sleep mode and someone send me a txt the phone plays the sound and lights the bottom 4 buttons like normal but once done the bottom buttons remain lit and dont turn off until i wake the phone and put it back to sleep.
any ideas on where to change this? or is it part of the rom
mavicious said:
i think i have the right idea here. i installed the helly bean rom a couple days ago and absolutely love it so far, however the home, search, menu, back buttons all stay lit if a notification for txt or email happens while its sleeping. for further clarification in case some dont understand what i mean, say i hit the power button to go into sleep mode and someone send me a txt the phone plays the sound and lights the bottom 4 buttons like normal but once done the bottom buttons remain lit and dont turn off until i wake the phone and put it back to sleep.
any ideas on where to change this? or is it part of the rom
Click to expand...
Click to collapse
It is part of the ROM. It functions as a notification LED to let you know that you have a text/missed a call/etc. You shouldn't worry about it, it doesn't affect battery life.
You can turn off Notification Light in settings.
hongzhou94 said:
It is part of the ROM. It functions as a notification LED to let you know that you have a text/missed a call/etc. You shouldn't worry about it, it doesn't affect battery life.
Click to expand...
Click to collapse
ah ok, works for me then i wasnt to concerned about the battery as its just led so its such a minimal draw. just makin sure its not a bug of some sort
thx
Capative Hardware keys not lit until u press in captivate key area in Helly Bean
Hi There,
I just flashed my cappy to the HellyBean ROM, and everything works great! Thanks for such a nice ROM.
While using it I found one small issue,It could be a setting issue which I'm unable to figure so please help me out.
When i'm using the phone, in gingerbeard, it used to light the bottom 4 capacitive keys(Setting,HOME,BACK,SEARCH) all the time so that I can press them when i'm using the phone in dark. But in Hellybean, those 4 LEDs are not lit when the touch screen is used, those 4 buttons are lit only when I press in the Bottom area.
Please let me know how to make them ON even when i'm using the touchscreen area?
Thanks,
Raj
This is the vibrant section not captivate but I think there is a setting in devil kernel configuration app. Don't know for sure which exact setting controls that but I think there's another setting in display, try both. I don't use any bln because of battery use, plus I'm no longer running HB on my vibe or cappy.
Sent from my SGH-T959 using xda premium
After my phone is running for awhile the screen won't time out, a reboot will fix it but after some time the screen won't timeout again. Also if Quick glance is activated, while the issue is present, the screen will turn on, start to dim and then the lock screen will show and stay until I shut it down. Maybe an app is running in the background and keeping it from shutting down? This is when the phone is not charging so it's not the Stay awake setting. I've also turned various settings on and off as well as changing the screen timeout, which is now set to 15 secs, and the problem still persists.
Anyone with this issue?
I've seen some (Issue 37974) with the GS3 posting about the same issue but never saw a resolution.
Any help or insight would be appreciated.
I've noticed this but it usually was an app that kept it running.
From the Homescreen, try holding down the Home "Verzion" button for a few seconds. Click "Remove All" and then see if it times out. If that doesn't work, try clicking "Task Manager" instead and closing all Active Applications.
If either of these do work, then when you notice it again, be more selective in which apps you close until you find the offending app. I have a few Sound Engineering apps that use the microphone and one of them forces my screen to stay on. I'm assuming to access the mic hardware. It seems to run in the background even when I "close" the app.
I've done the remove all and nada but I'm adsuming it is and app too...
Thanks for the reply...
It must be Stay Awake in developer options that is causing this bug. As stated a reboot fixes the issue temporarily, after the reboot the Stay Awake option gets turned off on its own, If I turn it on again the issue appears again shortly after. So somehow the Stay Awake option must be getting messed up and keeping the screen on even when not charging.
My workaround is turn off Stay Awake and Use Tasker to keep the phone awake while charging. Not what I'd like, I'd prefer the system work correctly, but it works for now.
Thanks
first off are you using a different keyboard other then the Samsung one ?
i had this happen to me using Swift.
just reboot your device and you should be golden.
Dont know why the keyboard would do this to the phone but thats what it was and all i did was reboot and Timeout works fine...
thenuke1 said:
first off are you using a different keyboard other then the Samsung one ?
i had this happen to me using Swift.
just reboot your device and you should be golden.
Dont know why the keyboard would do this to the phone but thats what it was and all i did was reboot and Timeout works fine...
Click to expand...
Click to collapse
Don't think the keyboard is a major issue with this. I've had this issue both when using swift and just the SS keyboard. I am more inclined to think like the other poster said that it has to deal with SmartStay. I haven't tried turning it off then rebooting, going to see if that works now. It sucks because toggling SmartStay is really useful, but i'm concerned with burn-in and especially with a battery that lasts 10hrs+, that could be an issue.
kimdoocheol said:
Don't think the keyboard is a major issue with this. I've had this issue both when using swift and just the SS keyboard. I am more inclined to think like the other poster said that it has to deal with SmartStay. I haven't tried turning it off then rebooting, going to see if that works now. It sucks because toggling SmartStay is really useful, but i'm concerned with burn-in and especially with a battery that lasts 10hrs+, that could be an issue.
Click to expand...
Click to collapse
interesting...
just my 2 cents. When i switched to swift from samsung key i just rebooted and it corrected the issue. Im sure theres a permanent fix but works as a temp one imo
Hello,
the following problem appears when i try to unlock the phone after some hours: i can see my home screen, but the screen stays extremely dim. When i try to start an app (e.g. browser) the screen turns black. I can unlock it again, but the screen stays dim. after some unlocking the screen becomes normal (normal brightness) and also the apps are startable.
i am using autobrightness, the stock firmware, 4.1.1 (i9300xxdlih) power saver is not turned on.
thx, i hope you can help me solving this problem
fanbayer
Fanbayer said:
Hello,
the following problem appears when i try to unlock the phone after some hours: i can see my home screen, but the screen stays extremely dim. When i try to start an app (e.g. browser) the screen turns black. I can unlock it again, but the screen stays dim. after some unlocking the screen becomes normal (normal brightness) and also the apps are startable.
i am using autobrightness, the stock firmware, 4.1.1 (i9300xxdlih) power saver is not turned on.
thx, i hope you can help me solving this problem
fanbayer
Click to expand...
Click to collapse
i updated mobile phone to android versiopn 4.1.2. this morning. Unfortunately the problem still appears.
Maybe its a hardware defect?
Try to disable somehow light sensor and change settings to non auto brightness.
Sent from my GT-I9300 using xda app-developers app
d0hn said:
Try to disable somehow light sensor and change settings to non auto brightness.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
i disabled auto brightness and set the brightness to the highest level. But its still same: very dim and after a while a black screen; after a few times of unlocking, the display works normally
I have just seen the same issue on a friend's S3.
Anyone else? I feel like this is a very big issue that is still lurking in a lot of devices.
I tried it myself and I toggled the power button to turn the screen on and off.
It doesn't take long but sometimes when the screen turns back on, it's super dim and you can faintly see the lockscreen image.
You have to cycle the screen several more times to get it to the 'correct' brightness, and no it is NOT a brightness setting.
It's some hardware issue in the phone.
Sorry for the necrobump, but I only found this thread. I have this problem too since about a week back. It makes my phone useless at times. I first thought it was a software issue. I have an app (called Twilight) for dimming the screen more than normal settings and also toning it, for nightime use, and I thought that was the culprit first, but nope. I have flashed rom, recovery, wiped all caches I can think of. Still happens, just now I was in the middle of installing android revolution hd, and the screen ultradimmed on me so I can't finish the process
Thing is, a few months ago I managed to crack my screen by way of gravity and concrete. I let the samsung brand service centre in Stockholm repair it for me (it is out of warranty) and this issue with the dimming never happened before that. Then again, it didn't happen directly afterwards either... but still. So, I am thinking: either me dropping it caused more damages and this is because of that. Or the service center did a bad install of the new screen. Or, the replacement screen that was installed has a defect in itself. I am leaning a bit towards the third explanation... maybe different batches of screens?
Does anyone have any ideas? If I am to contact the service center and complain about their work I would like to be able to point towards a "known problem"...
8Fishes said:
I have just seen the same issue on a friend's S3.
Anyone else? I feel like this is a very big issue that is still lurking in a lot of devices.
I tried it myself and I toggled the power button to turn the screen on and off.
It doesn't take long but sometimes when the screen turns back on, it's super dim and you can faintly see the lockscreen image.
You have to cycle the screen several more times to get it to the 'correct' brightness, and no it is NOT a brightness setting.
It's some hardware issue in the phone.
Click to expand...
Click to collapse
Take it back, if it didn't happen before then the new screen is most likely.
It isn't a common problem