Database Info

LIGHTS - Trackball, bottom home keys, etc

Search "Covedesign Dev" in the market.
I know since 2.1 has been out, led lights on our phones have been a problem with most roms. Even with new roms, the lights work but they dont shut of during movies and so on. And if using a overclocked rom, you dont have trackball/home key lights at all.
Well I found a program on the Market that lets you disable them or turn them on. I tested them all and they actually work.
Im using Fresh toast v1.1 and I clicked the trackball check mark and the ball lite up.

Jus10o said:
EDIT>> i see the new sections.. Moving thread.
Someone can delete :/
Click to expand...
Click to collapse
yeah man the kernel drivers are creating the nods. its just the lights.msm7k.so isnt using the same nods as the kernel driver produces

toastcfh said:
yeah man the kernel drivers are creating the nods. its just the lights.msm7k.so isnt using the same nods as the kernel driver produces
Click to expand...
Click to collapse
I updated the post above.. Thats what i had typed there... It wasnt directed to the .27 kernel

Does work BUT obviously backlights and trackball will stay lit while screen is on but i guess they don't draw that much extra current. Just a drag to need a program running to have lights but hey it's all part of the fun of getting closer to a perfect cooked rom

Visionikz03 said:
Does work BUT obviously backlights and trackball will stay lit while screen is on but i guess they don't draw that much extra current. Just a drag to need a program running to have lights but hey it's all part of the fun of getting closer to a perfect cooked rom
Click to expand...
Click to collapse
It says will stay lit until you disable. But im sure someone could make a quick widget on the desktop that would disable/enable a certain light on the phone. So if you need it, it would just be a click away.
The main reason why i shared, because back when DC got the leak and the lights started working. There was no way to disable the lights in the dark and during movies the ball would stay lit.

speaking of the trackball, ive been looking for a program that will make my trackball flash when i have a new sms/mms.
any help?

keyofhappy said:
speaking of the trackball, ive been looking for a program that will make my trackball flash when i have a new sms/mms.
any help?
Click to expand...
Click to collapse
The dev of the app has is source code for everyone to get.
Im sure someone could create the app that simply says
if messages received
then flash the ball till button pressed or certain amount of time.
by using the same thing this app does to turn it on
Ask one of the higher devs here.. Flipz, toast, damage, darch, treve, maybe avalanche, regaw.. Im sure there is more

+1 for interest in trackball notifications.

Agreed would love to see flash lights for notification built in not 3rd party i am sure we could intergarte it

<Request> SMS/MMS Alert indictor light

Just putting it out there for a dev to look into it. I am looking for something that would notify for messaging if you miss the initial alert. That is probably the one thing I really liked about the Atrix. Maybe have the bottom soft buttons illuminate and stay lit until its cleared. I know someone had it working on the Dell Streak, but I can't find anything on the market that works in that way.

it was in the works before. BLN but i dont think anybody has worked on it anymore since it wasnt working right.

I really hope someone picks it back up again, or someone can suggest something from the market.

Optimus-Prime said:
it was in the works before. BLN but i dont think anybody has worked on it anymore since it wasnt working right.
Click to expand...
Click to collapse
BLN stands for ???
The lack of any form of notification lights on this phone is one of the few things I don't like about it. That said, I had the same limitation with xdandroid since it didn't support the Tilt2's LEDs for any purpose other than indicating sleep state so I'm kind of used to it.

BLN = backlight notification
It was/is a kernal feature to use 4 capacitive buttons as a notification light.
you can find it in an older Defuse kernal, but I wouldn't recommend it. It was removed due to random bugs.

Install GO SMS. It has an option for repeat alerts for messages. And its free.

[i9020a] Problems with BLN

Hi,
I'm running NSCollab 1.0.50 with franco.kernel from Nov. 8 on a I9020a.
I have a script set to enable blinking backlight notification by do this:
echo 1 > /sys/class/misc/backlightnotification/enabled
echo 1 > /sys/class/misc/backlightnotification/in_kernel_blink
My problems are:
1) Sometimes after I've turned the screen off the soft keys are still sensitive to touch and when I touch one they all light up and stay lit up until i turn the screen on and off again. This seems to only happen sometimes. I haven't nailed down when exactly this happens.
2) Sometimes (more like rarely) the screen will be off and I will have a notification but the power button will not turn the screen on. It seems as if the OS is still running though because I can still hear when a text comes in. I don't know if this is the famed Sleep of Death because it seems like just the screen is off but it might be.
3) This is less critical but ties in to point 2). If I use the app SMS Popup, when I get a text the screen will turn on and then go off by itself, the lights will start blinking but then if I get another kind of notification (like an e-mail) I will hear the notification sound but will not be able to wake up the screen with the power button. Again it seems as if the OS is still running to some extent. This is consistent behavior and I've just uninstalled SMS Popup to avoid the problem.
It seems as if all the problems go away if I turn off BLN. I know the problem in 3) definitely went away because the behavior was consistent and I was able to test. I just love BLN so darn much that it's hard to live without.
So, has anyone experienced similar behavior to what is mentioned above? Does anyone know why this is happening? Is there some problem with my setup?
Thanks in advance.

I've had the same issues with some kernels like netarchy. Or matrix. I haven't figured out why it does that. Its weird.
Sent from my Google Nexus S 4G using xda premium

I run CM7.1 and I haven't installed the BLN kernel because for me the soft keys automatically light up and stay on until I turn the screen on. I do also have the problem with soft keys lighting up when screen locked if I bump them but it doesn't happen very often.

Esteway.619 said:
I've had the same issues with some kernels like netarchy. Or matrix. I haven't figured out why it does that. Its weird.
Sent from my Google Nexus S 4G using xda premium
Click to expand...
Click to collapse
Which ROM were you running with those kernels? I'm trying to nail it down to either the kernel or the ROM.

I had the same issue running Gummy with the matr1x kernel. Im trying a full wipe as I installed the kernel just wiping the cache. Might help, might not. Ill post results.

Does anyone know if there have been any solutions to this issue?
I am running the CM9 nightlies on my NS4G and I also find that the soft keys will light up after I turn off my screen. They don't go dark again until I turn the screen on an off again.

Touch key brightness

Hey all, I'm trying to figure out how to get some brightness settings for the touch key brightness to stick. I've used LG 2x Notifications and O2x Touch Key Brightness, and they both work up until the point where i put the phone to sleep by tapping the power button. As soon as I wake it up, the brightness goes straight to zero unless i head back to the app and raise it up again. And if i uninstall the apps, the brightness on my keys stay off until i re-flash or reinstall the app again. Help!

My issue is a little different but similar. It worked fine for me on every basic gingerbread rom, but when I switched to a cm7 based rom the lights change with the brightness of the screen. I turned off all the light notifications but it did not help.
If anyone has any ideas, I'd love to hear them.

What rom?
Sent from my LG-P999 using XDA

redmonke255 said:
What rom?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
On SinghUI but it doesn't have built-in LED notifications, if that's what you're getting at.

If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.

xBIGREDDx said:
If the setting from one of those apps doesn't stick, then it's most likely being set by your ROM or Kernel. Have you tried checking if you get the same issue with other ROMs?
@jcbofkc That's a built-in setting that can't really be changed unless you get a custom ROM or Kernel cooked up to remove the link between the brightnesses.
Click to expand...
Click to collapse
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?

rrroach said:
90% sure the ROM doesn't have built in notifications. I'm noticing now that very rarely the settings do stick. Perhaps there is a way to force the app to stay in memory?
Click to expand...
Click to collapse
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.

xBIGREDDx said:
That wouldn't work. All that those apps do is write a number from 0-20 to the text file:
/sys/devices/platform/star_touch_led/wled
in your root file system.
When you read the file, it shows you the current output to the LEDs (from 0uA to 2000uA).
When you write to the file, it interacts with the Kernel and sets the brightness.
The Touch Key Lights type apps, all they do is when you move the slider they write a value to that file, and that's it. The only reason it wouldn't stick is if your ROM or Kernel is changing the value in the background. For example it will set it to 0 when you turn the screen off, and then it should set it back to wherever it was before when you turn the screen on again.
The closest you could get is to take the source for LG Touch LED Notifications and modify it to set the brightness every few seconds or something, but that probably wouldn't be too good for your battery life.
Based on your symptoms it appears that either your ROM or your phone doesn't really handle the modifying of the brightness very well. It looks like SinghUI does use a kernel from CM7, so I don't think your kernel is the problem. I'd suggest flashing the most recent CM7.2 RC, and seeing if you have the same problem there. CyanogenMod will change your LED brightness based on your screen brightness though.
EDIT: Ignore all that for a moment, try this first. It is a post from January 21st in the SinghUI thread, so it might not work now, but go ahead and try it: http://forum.xda-developers.com/showpost.php?p=21652744&postcount=293
Also I'd suggest posting in the SinghUI thread as everyone there is using your ROM, so they might be able to help better.
Click to expand...
Click to collapse
Thanks for the link. It turns out that the ROM does have led notifications. However, disabling them didn't help the problem. :/ the g2x has just been an awful experience for me! :/

[Q] Control touch key backlight effectively?

Hi all It might not sound wise but I just got myself an second hand Infuse 4G for a nice price, and like every device I've owned, got CM running on it in hours. However, there's something that bugs me for a bit, and that is the touch key backlight.
On other devices I have, CM's Settings-Buttons part controls touch key backlight well, leaving it on for whatever duration or turning it off. But on all ROMs I've tried till now (CM10, CM10.2, CM11), either this option is absent (CM10's Infuse Settings is incomplete), or the option doesn't work properly:
1) When I set the keys to light up, they don't light up automatically when I wake the phone up from sleep, I'll have to press the keys to activate them.
2) When I turn the light off, the light indeed goes off immediately, but when I press any of the keys, they come back to life again and simply stay on, ignoring the settings.
I remembered that on many HTC phones there was a way to manually control button backlight behavior by altering values of a certain file in /sys/class/..., so after some work, I found the file: /sys/devices/virtual/misc/melfas_touchkey/brightness, and indeed, setting it to 0 will make the light go off. The thing that doesn't work out is that it won't persist - pressing any of the keys still make the light come back. I've set the permission to 0444 and even made a init.d script for that, and I can guarantee that the script itself is working properly, but still it can't keep the light under control... And now I'm stuck.
1) Is there a way to make the option in Infuse Settings or Settings-Buttons work as they should?
2) Any separate app that could also do this?
3) Why won't my manual adjustment persist?
Answering any of these questions would be of help, thank you in advance!

AndyYan said:
Hi all It might not sound wise but I just got myself an second hand Infuse 4G for a nice price, and like every device I've owned, got CM running on it in hours. However, there's something that bugs me for a bit, and that is the touch key backlight.
On other devices I have, CM's Settings-Buttons part controls touch key backlight well, leaving it on for whatever duration or turning it off. But on all ROMs I've tried till now (CM10, CM10.2, CM11), either this option is absent (CM10's Infuse Settings is incomplete), or the option doesn't work properly:
1) When I set the keys to light up, they don't light up automatically when I wake the phone up from sleep, I'll have to press the keys to activate them.
2) When I turn the light off, the light indeed goes off immediately, but when I press any of the keys, they come back to life again and simply stay on, ignoring the settings.
I remembered that on many HTC phones there was a way to manually control button backlight behavior by altering values of a certain file in /sys/class/..., so after some work, I found the file: /sys/devices/virtual/misc/melfas_touchkey/brightness, and indeed, setting it to 0 will make the light go off. The thing that doesn't work out is that it won't persist - pressing any of the keys still make the light come back. I've set the permission to 0444 and even made a init.d script for that, and I can guarantee that the script itself is working properly, but still it can't keep the light under control... And now I'm stuck.
1) Is there a way to make the option in Infuse Settings or Settings-Buttons work as they should?
2) Any separate app that could also do this?
3) Why won't my manual adjustment persist?
Answering any of these questions would be of help, thank you in advance!
Click to expand...
Click to collapse
As far as I know, the Infuse hasn't had effective backlight control since Gingerbread. If you wanna go back to that, it should work fine. Otherwise, all of the newer ROMs are using an outdated kernel that doesn't support backlight control. I highly doubt we will see it working again since very few people are still using the Infuse.

niral7 said:
As far as I know, the Infuse hasn't had effective backlight control since Gingerbread. If you wanna go back to that, it should work fine. Otherwise, all of the newer ROMs are using an outdated kernel that doesn't support backlight control. I highly doubt we will see it working again since very few people are still using the Infuse.
Click to expand...
Click to collapse
I can bear returning to GB and I did, but I've tried both stock UCLB3 and CM7, and neither contains any settings about button backlight...
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

AndyYan said:
I can bear returning to GB and I did, but I've tried both stock UCLB3 and CM7, and neither contains any settings about button backlight...
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
The Infuse supports backlight control in gingerbread. In order to use it, you'll have to download a third party app in the play store. I don't think CM7 will support it either.

niral7 said:
The Infuse supports backlight control in gingerbread. In order to use it, you'll have to download a third party app in the play store. I don't think CM7 will support it either.
Click to expand...
Click to collapse
Not even CM7? No dice then, I guess... Thanks for the tip anyway.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]