I have CM7.2 installed and my soft key lights have a mind of their own. They turn on every few seconds and it isn't because of a notification. The only suggestion I have found is to install an app that turns off the lights. I tried a couple and they don't work. The lights still come on. I have tried reflashing and I don't think an app is causing this.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Soft key lights keep turning on
- Thread starter tmpearson
- Start date
-
- Tags
- samsung galaxy ace
Hi. I got the same problem. Using cyanogenmod 7.2.0 RC1 cooper version on samsung galaxy ace. It's a bit annoying that the soft keys are lighting up in every 10-15 seconds. It's a bit annoying, however it doesn't consume much battery as i heard... i would really welcome some good advise how could i fix this bug.
Oh and the cam has no zoom!
I am using the old grifs version and i haven't seen the softkey lightening up on its own, atleast not during standby. While operating the handset it does come on without touching it, but not anything noticeable.
On stock sometimes the keys would just light up on their own and won't turn off even on standby, the only solution was to reboot.
Ya LED and zoom doesn't work for me too...
I think slaid480 is the CM maintainer now, i am not sure.
On stock sometimes the keys would just light up on their own and won't turn off even on standby, the only solution was to reboot.
Ya LED and zoom doesn't work for me too...
I think slaid480 is the CM maintainer now, i am not sure.
I got the same issue now.
When I get a missed call BLN pro is configured to do this and worked perfect on stock rom.
Light up for 3 seconds.
Go off for 2 minutes
Light up for 3 seconds
Off for 2 minutes and repeat forever until I acknowledge it.
On CM7.2 the LED's come on for the 3 seconds, then go off but then 1 second later come back on and then stay on.
The problem is I cant find a way to contact CM rom developers, it seems no email address etc. Last rom was 3 weeks ago.
From what I can see it appears to be using the force LED's on when is setto use application setting. So is a bug. I have a growing list of niggles with CM at the moment.
When I get a missed call BLN pro is configured to do this and worked perfect on stock rom.
Light up for 3 seconds.
Go off for 2 minutes
Light up for 3 seconds
Off for 2 minutes and repeat forever until I acknowledge it.
On CM7.2 the LED's come on for the 3 seconds, then go off but then 1 second later come back on and then stay on.
The problem is I cant find a way to contact CM rom developers, it seems no email address etc. Last rom was 3 weeks ago.
From what I can see it appears to be using the force LED's on when is setto use application setting. So is a bug. I have a growing list of niggles with CM at the moment.
I have an update.
On XDA another user of BLN pointed out the problem appeared when BLN introduced the proximitiy sensor feature, prior to that BLN was 100% working with CM7.
So I uninstalled BLN pro and installed BLN free, BLN free has not been updated in a while and doesnt have any proximity sensor feature.
I did this test.
BLN pro I disabled all blinking and set to the LED just stays on for a notification. When I did a missed call or just a BLN led test the LED would mostly stay on but randomly go off for a second beforce coming back on, sometimes moving the phone triggers it but not always.
BLN free configured the same way (cant be configured another way is restricted), the LED stays on 100% as it should do. Since CM has a missed call LED feature for now I am using BLN free and accepting I cant use the blinking function, however I will only do this temporarily.
Here comes the problem as I see it.
Android developers are different to windwos developers, they seem to get offended on things like asked for ETA etc. The accepted motto on XDA is if you use software then you are expected to accept thaty the developer may stop supporting it and you cant ask for things like progress reports, eg. the last CM update was many weeks ago and it could be months before another update or it could be a day, we dont know. There is no email address to contact them and I havent seen one post on any of the CM threads on forums, this to me is not a good way to develop and communicate with your users. Instead there is the bugtracker which however makes it clear if there is no logcat or whatever its called they will reject the bug report, so there is clear barriers to reporting bugs. Which goes some way to explaining why CM is so buggy.
I have however left a post on the BLN XDA thread but its worth pointing out the BLN dev ignored the other guy who posted about CM weeks ago on it. BLN is a paid app so I do expect a reply and fix of him as I have paid for it. Whether I get one I dont know. My gut guess is its a proximity sensor issue and if the BLN dev releases the old BLN version again (before he added the sensor code) it will work fine. Ultimately its a CM bug tho.
Also to add CM7.1 has the same issue as well, I thought it didnt at first but it does. Plus it behaves better when the usb is plugged in for some reason.
On XDA another user of BLN pointed out the problem appeared when BLN introduced the proximitiy sensor feature, prior to that BLN was 100% working with CM7.
So I uninstalled BLN pro and installed BLN free, BLN free has not been updated in a while and doesnt have any proximity sensor feature.
I did this test.
BLN pro I disabled all blinking and set to the LED just stays on for a notification. When I did a missed call or just a BLN led test the LED would mostly stay on but randomly go off for a second beforce coming back on, sometimes moving the phone triggers it but not always.
BLN free configured the same way (cant be configured another way is restricted), the LED stays on 100% as it should do. Since CM has a missed call LED feature for now I am using BLN free and accepting I cant use the blinking function, however I will only do this temporarily.
Here comes the problem as I see it.
Android developers are different to windwos developers, they seem to get offended on things like asked for ETA etc. The accepted motto on XDA is if you use software then you are expected to accept thaty the developer may stop supporting it and you cant ask for things like progress reports, eg. the last CM update was many weeks ago and it could be months before another update or it could be a day, we dont know. There is no email address to contact them and I havent seen one post on any of the CM threads on forums, this to me is not a good way to develop and communicate with your users. Instead there is the bugtracker which however makes it clear if there is no logcat or whatever its called they will reject the bug report, so there is clear barriers to reporting bugs. Which goes some way to explaining why CM is so buggy.
I have however left a post on the BLN XDA thread but its worth pointing out the BLN dev ignored the other guy who posted about CM weeks ago on it. BLN is a paid app so I do expect a reply and fix of him as I have paid for it. Whether I get one I dont know. My gut guess is its a proximity sensor issue and if the BLN dev releases the old BLN version again (before he added the sensor code) it will work fine. Ultimately its a CM bug tho.
Also to add CM7.1 has the same issue as well, I thought it didnt at first but it does. Plus it behaves better when the usb is plugged in for some reason.