Nell17 / openeve

Automatically exported from code.google.com/p/openeve
0 stars 0 forks source link

Hardware keyboard lights does not turn on in dark #179

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Slide out hardware keyboard in a dark place
2. Keyboard lights remain off
3.

What is the expected output? What do you see instead?

Keyboard lights should be turned on

What version of the product are you using?
1. gapps-gb-20110828
2. system-gb-20110918-snapshot
3. boot-gb-224
4. ...

On what operating system?

Do you have logcat or dmesg ?
 (adb logcat -d > logcat.txt, adb shell dmesg > dmesg.txt)

What version of the *Official LG* Firmware were before using Custom
firmware ?
(V20G, V20D, V15x, V16x etc. )

Please provide any additional information below.

Original issue reported on code.google.com by iareh...@gmail.com on 27 Sep 2011 at 3:47

GoogleCodeExporter commented 8 years ago
currently Keyboard LED always turn on by sliding out action.
so I can't turn off keyboard LED light.

did you change your settings or the "light.eve.so" light sensor library at the 
/system/lib/hw/ ?

Original comment by wkp...@gmail.com on 28 Sep 2011 at 12:15

GoogleCodeExporter commented 8 years ago
I recently have wiped phone and did a clean install. Keyboard LED turns on on 
sliding out action for 2 seconds. After that it never turns on. Actually it 
should remain on in low light.

Original comment by iareh...@gmail.com on 28 Sep 2011 at 12:39

GoogleCodeExporter commented 8 years ago
Please check your settings.

"Settings"=>"Sound Settings"=>Notifications"
 - Blink notification light [v]
 - Always enable notification light [v]
 - Charging light [ ]

and reboot

Original comment by wkp...@gmail.com on 28 Sep 2011 at 9:01

GoogleCodeExporter commented 8 years ago
problem solved without reboot... thanx wkp

Original comment by iareh...@gmail.com on 28 Sep 2011 at 9:26

GoogleCodeExporter commented 8 years ago
i had the same problem ,  checked the settings and it was solved AFTER reboot 
:).. thanks wkp..

Original comment by elfe...@gmail.com on 2 Jan 2012 at 10:28