MOD NOTE: You can close this thread now. I have solved it.
After upgrading to LightFlow 2.8.0 my notification LED seems broken. I tried reinstalling LightFlow, didnt work. Fixing permissions from CWM, and reinstalling LightFlow, didnt work. I found an older version of LightFlow, version 2.7.4, which i believe was the version i used to have, and it used to work, but now it doesnt. I downloaded LED Tester, and it did not light any LED either.
Does anyone have any idea of things i can do to try and get it working again? I sure hope its not broken, i dont want to have to go through a return process...
My GN is rooted, with stock rom.
UPDATE:
After a lot of debugging i solved the problem myself. It turns out i accidentally unchecked the android Settings->Display->Pulse notification light. After enabling that setting LightFlow 2.8.0 works fine now.
Related
The app was working normally when i had it set on 160dpi, though then i got LOS for some odd reason, so i restarted the phone, charged it, then tried to apply the LCD density once more, and not it just says " LCD Resolution got accepted ect." From Super User but the app doesn't restart my phone any more :/..
Im in Stock Rom, and Rooted with LosKernel 10/28 update.
I've tried to uninstall/clear data, even clear super user data, and nothing.
thank you for reading, and hopefully find a way to assist me
Edit- Not sure if the waiting helped, but i did remember there was a new update for BusyBox because i saw it on the market, and decided to update it from 1.18.4 to 1.19.2, and after i updated and installed the latest BusyBox release 1.19.3 right now, it worked... all i have to say is wtf? lmao, what is busy box precisely?
I'm still knew to this whole thing, so I'm not sure if this is the main reason for it to have started to work.
Is it?
Flashtool was working before, but now, the activity log on the UI doesn't display any text, and the flash mode isn't working properly. Before I was able to install from any firmware, but now I can only install one of them. Then the Flashmode button froze and the application couldn't be closed. After that, I restarted my computer, and when I went to reopen the application, I noticed the executables were gone, except for the 64 bit version. So then I reinstalled Flashtools again, and I am still having the same problems... Does anyone know how to solve this? I've already tried uninstalling and reinstalling and I am still getting the EXACT same problem. It's really weird...
bump
Just recieved OTA update on my stock gnex using the google-framework cache clear/close process method.
I cleared cache of google-framework process and then stopped it, rebooted the device and after reboot was done i got the OTA, installed it and phone booted again. update was installed without any problems.
BUT: when going into settings => location access => and then tapping "access to my location" settings force closes.
i rebooted the phone a few times and tried everything that came into my mind, no solution
anybody got the same problem or maybe even a solution?
gaga111 said:
Just recieved OTA update on my stock gnex using the google-framework cache clear/close process method.
I cleared cache of google-framework process and then stopped it, rebooted the device and after reboot was done i got the OTA, installed it and phone booted again. update was installed without any problems.
BUT: when going into settings => location access => and then tapping "access to my location" settings force closes.
i rebooted the phone a few times and tried everything that came into my mind, no solution
anybody got the same problem or maybe even a solution?
Click to expand...
Click to collapse
No problems for me. Ive just got 4.1.2
Anbody else :S
Just to be clear.. i dont mean switching it on and off
Sent from my Galaxy Nexus using xda app-developers app
edit:
seems like light flow is causing the force close...
as soon as i deactivate lightflow from the accessibility settings this doesnt happen anymore
gaga111 said:
Anbody else :S
as soon as i deactivate lightflow from the accessibility settings this doesnt happen anymore
Click to expand...
Click to collapse
Same problem here and that fixes it for me too! Happens on my wife's Nexus 7 too, but she has NoLED there so this may be a bug that has to do with anything enabled under accessibility settings (or at least not ONLY Light Flow).
Edit: I wonder if this is related:
http://forum.swype.com/showthread.p...Swype-Issue-Thread&p=35850&posted=1#post35850
"Note: We have found that this issue is related to running apps that have settings in the accessibility menu in Android settings. In the meantime, you should be able to use Swype by disabling any apps that are in Android Settings > Accessibility."
Sounds like 4.1.2 has some kind of Accessibility bug,
hello my friends
I got the update 4.4.2 official rom
after update my led notifications working only missed call and sms& charging !!!!!!!!! dose not working for other application such as viber-whatsapp- line&....
Is there a way? for fix it?
my phone e988 with Malaysia v20b rom
Have you checked notification settings in these apps? Also, check Home button LED configuration, there should be an option to enable led for downloaded apps, if I remember correctly.
zamajalo said:
Have you checked notification settings in these apps? Also, check Home button LED configuration, there should be an option to enable led for downloaded apps, if I remember correctly.
Click to expand...
Click to collapse
My problem was solved after hard reset
Hi, hope I'm not alone here. I hadn't changed anything on my device, but noticed tonight that cf.lumen simply wasn't running. It always worked great in the past. It still has SU permissions and I can see they are granted on device boot. I'm on systemless 2.61, if that matters. I obviously tried the standard stuff like wiping app data and cache. I even cleared dalvik/cache in twrp. I hadn't seen anything about this issue anywhere else so I thought it would be worth a post. Thanks if anyone can help!
edit: just updated to systemless 2.66, cf.lumen still not working...
i thought to change the driver. so the KCAL driver (which I assume requires root since it doesn't say non-root) is working, so it appears just the cf.lumen driver is not working
Ok so I checked the cf.lumen thread and found that installing busybox to /system/xbin solved it. cf.lumen driver working properly again now. Still not sure why it broke or why this fixed it.