[Dev Needed] Controlling the notification LED

AlexisTM

Dear,

The notification LED IS working ! The LED is sofware controllable (despite what we said).

Led Problem :

• Be ROOTED
• Have a terminal (on Android or via adb shell)
• $ cd /sys/class/leds/led_G
• $ su
• Now, you are in the real folder (not the simlinked) in /sys/devices/soc.0/gpio-leds-simcom.71/leds/led_G
• # echo 1 > brightness
• Your led in ON !
• # echo 0 > brightness
• Your led is OFF
  

       
The ROM problem should be the wrong folder simlinked to power on/off the notification LED.
Unfortunately, my Android experience is so weak I am unable to "modify" the configuration of the notification LED to simlink the good one.


If someone have the experience, then we should create an XPosed module to modify it or a simple Bash script to execute via ADB to modify the configuration.

Simlink path : /sys/class/leds/led_G
Full path : /sys/devices/soc.0/gpio-leds-simcom.71/leds/led_G



Luminosity problem :
For the luminosity problem : "My screen is not bright enough" or "My screen is too bright at minimum", the only thing to change is the configuration, indeed, the minimum brightness used is 11, we can go to 1, and the highest in use is 160, the maximum is 255.

Simlink path : /sys/class/leds/lcd-backlight
Full path : /sys/devices/soc.0/1a00000.qcom,mdss_mdp/qcom,mdss_fb_primary.129/leds/lcd-backlight

AlexisTM

Indeed, the notification led Driver is messed up, the led is unable to blink because of the driver.

It is possible to controle the led via an Application : Light Flow on Google Play, but impossible to blink it...

Rangarid

As android is case sensitive like linux the directory should be called "led_g" instead of "led_G" or what do you want to say with that?

I dont think its just a wrong named folder/symlink because the charging LED works.

WoRm

AlexisTM replied at 2016-1-10 20:44
Indeed, the notification led Driver is messed up, the led is unable to blink because of the driver.
...

can you give me the configuration of light flow for the led

AlexisTM

Rangarid replied at 2016-1-11 17:59
As android is case sensitive like linux the directory should be called "led_g" instead of "led_G" or ...

By "The simlink is wrong" is for the Notification LED.

I mean : The battery indicator is well simlinked in the kernel. But the notification led is not.
The second possibility is : The folder is well simlinked in the configurations, but notifications are "BLINK" but the blink method do not work (kernel driver chosen is wrong)
You can try by using : echo 1 > blink

AlexisTM

WoRm replied at 2016-1-11 20:22
can you give me the configuration of light flow for the led

Settings :

LED Control :
- check "led_G control"

Devices settings and Root :
- check "Root mode"
- check "Run every command as root"
- check "Show LED while screen on"

In notifications settings, choose a notification, swipe left (right menu) to Light :
- check "Enable light"
- led_G LED : solid
- led_G Brightness : 1

Rangarid

AlexisTM replied at 2016-1-11 21:41
By "The simlink is wrong" is for the Notification LED.

I mean : The battery indicator is well si ...

As far as i know if there is an led android has symlinks like "red", "green", "yellow" or so. Some systems use "led_g" which means green, "led_r" -> red and so on. I dont get it, why the symlink should be wrong? That blink does not work might be another problem. LED itself works from android, as it is on when you charge the phone.

AlexisTM

Rangarid replied at 2016-1-12 16:09
As far as i know if there is an led android has symlinks like "red", "green", "yellow" or so. Some ...

Well, this is the Battery indicator.
If the configuration was well done, the notification LED would be on if we set the Green color as Solid.

It do not.

Then, in the configuration, the notification LED is badly configured, the simlynk exists but Android do not know where the notification LED should be.