Help GB .596 = no LEDs except BattMonX

[Sokudo Ningyou]

Sooo, yeah. I know I did see some posts about LEDs not working in GB, but third person apps worked. Mine don't. Handcent, LED Me Know, WhoIsIt, Tasker...none of their LED settings work. I get a text, no light. However, BattMonX does work, and has done so consistently. I've uninstalled Handcent, cleared the cache, reinstalled, and still no lights. Has anyone else figured out what to do that doesn't include me having to factory reset?

 

[scary alien]

Sooo, yeah. I know I did see some posts about LEDs not working in GB, but third person apps worked. Mine don't. Handcent, LED Me Know, WhoIsIt, Tasker...none of their LED settings work. I get a text, no light. However, BattMonX does work, and has done so consistently. I've uninstalled Handcent, cleared the cache, reinstalled, and still no lights. Has anyone else figured out what to do that doesn't include me having to factory reset?

Why thank you, Sokudo Ningyou!

The only thing I can think of why this would be is that the LEDs notification directory's did change when GingerBread came out.

The base 2.1 / 2.2 path is: /sys/devices/platform/notification-led/leds

The base 2.3 GingerBread path is: /sys/devices/platform/leds-cpcap-rgb/leds

and there are red, green, blue subdirectories under the leds subdir which contain the actual brightness files that are used to control the intensity of each LED (in combination with all three colors, of course). Just for completeness, there are also sometimes amber subdirectories for phones that support an amber LED.

Now, my app uses these paths for two things:

1. To identify which LEDs and colors a particular Android device has

2. When rooted and when the "LED is always on" option is selected / enabled, the app will control (modify) the various LED color's brightness files in these directories.

Its interesting to note though, that when my app is not run in rooted or experimental mode, the system's notification APIs are used and the location of these LED notification directories are basically unimportant to my app, and should be to the other apps that you mentioned.

Not really sure why these apps might be having issues with their LED behavior though...

Cheers!

 

[Sokudo Ningyou]

Why thank you, Sokudo Ningyou!

The only thing I can think of why this would be is that the LEDs notification directory's did change when GingerBread came out.

The base 2.1 / 2.2 path is: /sys/devices/platform/notification-led/leds

The base 2.3 GingerBread path is: /sys/devices/platform/leds-cpcap-rgb/leds

and there are red, green, blue subdirectories under the leds subdir which contain the actual brightness files that are used to control the intensity of each LED (in combination with all three colors, of course). Just for completeness, there are also sometimes amber subdirectories for phones that support an amber LED.

Now, my app uses these paths for two things:

1. To identify which LEDs and colors a particular Android device has

2. When rooted and when the "LED is always on" option is selected / enabled, the app will control (modify) the various LED color's brightness files in these directories.

Its interesting to note though, that when my app is not run in rooted or experimental mode, the system's notification APIs are used and the location of these LED notification directories are basically unimportant to my app, and should be to the other apps that you mentioned.

Not really sure why these apps might be having issues with their LED behavior though...

Cheers!

To be honest, I'm suspecting that's the case, because why else would the LEDs so spectacularly fail to work after updating to GB? I know yours can find the files directly, so I figured that was why yours is the only one still working, but this is pretty damn annoying.

 

[Sokudo Ningyou]

Trillian's LEDs work too. So apparently some of these apps have updated for Gingerbread properly, and some haven't.