Hi when I flashed CM9 my LED flashlight no longer works. I don't have a problem with it I was just wondering if other people have this problem too. I love cyanogenmod and it would be better if everything works.
Sent from my SPH D700 ICS 4.0.4
certifiednoob93 said:
Hi when I flashed CM9 my LED flashlight no longer works. I don't have a problem with it I was just wondering if other people have this problem too. I love cyanogenmod and it would be better if everything works.
Sent from my SPH D700 ICS 4.0.4
Click to expand...
Click to collapse
I use Tiny Flashlight from the market and it works just fine.
Thanks it works like a champ now
Sent from my SPH D700 ICS 4.0.4
Flashlight Issue
I tried CM9 and had no problems except the flashlight. I upgraded to CM10 with Jellybean and it's flawless except NONE of the flashlight apps will work with the LED light. The tiny flashlight app works with "Strobe" mode, but not LED continuous mode... Has anyone else experienced this issue, or have any insight on it? Any help would be greatly appreciated!
-Shawn
Maybe a reflash
from my phone
Related
My led isn't flashing when I receive a text, it stays on solid with a quick off then back on for a split second, every so often. It happens kind of randomly. Anybody else have this problem or find a fix? I'm running starburst 1.9 with the lost kernel. I've tried more than one rom and. Kernel and I still have the issue even after factory wiping. Any help is greatly appreciated..
Sent from my SPH-D710 using xda premium
no issues here. running viper 2.2
no issue here either viper 2.2 also. You can try no led from the market.
Thanks for the feedback guys... Seems like such a simple fix but I just can't figure it out..
Sent from my SPH-D710 using xda premium
Not to resurrect this thread (well, yes actually.. that is my intent )
But I seem to be having the same issues. The LED only seems to work when I'm charging the unit. It doesn't work for any other type of notification.
I'm running Calkulin's FC18 ROM. However, it hasn't really worked before then as well. I'm not sure if it worked with the stock ROM when I first bought it as I didn't have the stock ROM on it but for maybe 30 mins after I bought the phone .
Any ideas?
cshoffie said:
Not to resurrect this thread (well, yes actually.. that is my intent )
But I seem to be having the same issues. The LED only seems to work when I'm charging the unit. It doesn't work for any other type of notification.
I'm running Calkulin's FC18 ROM. However, it hasn't really worked before then as well. I'm not sure if it worked with the stock ROM when I first bought it as I didn't have the stock ROM on it but for maybe 30 mins after I bought the phone .
Any ideas?
Click to expand...
Click to collapse
Pretty sure it's an ICS problem with FC18 in general because tons of people are getting it. Try upgrading to FC22 (not sure if its been fixrd) or just wait
Edit: Ignore what I said, since you said the LED ONLY works when it's charging. For me, the LED works only when it isn't charging .
Sent from my SPH-D710 using XDA
Hello,
My Sprint GS3 works fine under cm9 and paranoidandroid cm10 but I have the same problem, the camera works fine until I tap 2 or 3 times to focus on the far left. Now I know they are both nightly (not sure about paranoidandroid though) but everything else seems to work fine. Could this be an issue on my side with my phone? Thanks
vinayts96 said:
Hello,
My Sprint GS3 works fine under cm9 and paranoidandroid cm10 but I have the same problem, the camera works fine until I tap 2 or 3 times to focus on the far left. Now I know they are both nightly (not sure about paranoidandroid though) but everything else seems to work fine. Could this be an issue on my side with my phone? Thanks
Click to expand...
Click to collapse
I can confirm that I have this same issue. Have you tried Odin to stock, and did it continue then?
I just got my S II a few days ago and I flashed CM9. I've noticed the soft key back light is messed up and won't turn on after I get a notification, I read a post where someone suggested an app but that didn't work for me. Does anyone else have a suggestion? Is there a similar problem with other AOSP roms? Thanks
ponygon101 said:
I just got my S II a few days ago and I flashed CM9. I've noticed the soft key back light is messed up and won't turn on after I get a notification, I read a post where someone suggested an app but that didn't work for me. Does anyone else have a suggestion? Is there a similar problem with other AOSP roms? Thanks
Click to expand...
Click to collapse
I am running Cm9 stable and I haven't had any issues, make sure its enabled in settings/display and play around a bit with the settings. Otherwise I would recommend a reflash. That is all I can really think of.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Octane70 said:
I am running Cm9 stable and I haven't had any issues, make sure its enabled in settings/display and play around a bit with the settings. Otherwise I would recommend a reflash. That is all I can really think of.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Its actually pretty much a common issue. With both CM10 and CM9, i had only heard of it being perfect on AOKP ICS. I too had this, i ended up disabling BLN due to a wake lock drastically draining the battery. I miss the old static BLN cause that didnt use a wake lock. It just woke it once to allow them to come on then went back to deep sleep.
elesbb said:
Its actually pretty much a common issue. With both CM10 and CM9, i had only heard of it being perfect on AOKP ICS. I too had this, i ended up disabling BLN due to a wake lock drastically draining the battery. I miss the old static BLN cause that didnt use a wake lock. It just woke it once to allow them to come on then went back to deep sleep.
Click to expand...
Click to collapse
Well I installed AOKP ICS, and it works like a charm with the exception that it still doesn't really work with BLN but I didn't realty care much for that.
hello i recently flashed this version of cyanogen-mod on my Samsung s2 and am having an issue. First of all, i used a non-touch CWM but it was confirmed to work as long as you use super swipe, so i did that and it worked no problem. However the back-lighting on my buttons will not come on. It is not broken because it sometimes works but mostly does not. i am wondering if there is a fix or a setting i need to use to get it to work.
Thank you
heatpro said:
hello i recently flashed this version of cyanogen-mod on my Samsung s2 and am having an issue. First of all, i used a non-touch CWM but it was confirmed to work as long as you use super swipe, so i did that and it worked no problem. However the back-lighting on my buttons will not come on. It is not broken because it sometimes works but mostly does not. i am wondering if there is a fix or a setting i need to use to get it to work.
Thank you
Click to expand...
Click to collapse
have you tried "settings > advanced > sensors" and checking the backlight and notification settings?
yes I have tried it, it fixes the issue but once I lock the phone and then unlock it it does not work anymore.
heatpro said:
yes I have tried it, it fixes the issue but once I lock the phone and then unlock it it does not work anymore.
Click to expand...
Click to collapse
It's a known issue with any aosp builds such as cm or aokp. No one has gotten it to work consistently yet with ics or jb
Sent from my SAMSUNG-SGH-T989 using xda premium
yoft1 said:
It's a known issue with any aosp builds such as cm or aokp. No one has gotten it to work consistently yet with ics or jb
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
i think ill just re-flash to dark-side evolution. can you please explain to me what the MD5 keys mean since there are like a few download mirrors and i an not sure which one to get.
i am having this problem on every version or CM9 past RC2 and CM10 i really would like a fix
i looked into this a little and it seems that it's a problem from the moment you turn off the screen until the first hard light timeout afte the screen is turned back on
Apparently the bug is also in Miui and AOKP
I've been ignoring custom roms for about 6 months after I tried one previously and found the bluetooth bug. Just curious if this has found a fix at this point? I'd love to run a CM10.1 rom, but bluetooth audio is a must have for me.
cegna09 said:
I've been ignoring custom roms for about 6 months after I tried one previously and found the bluetooth bug. Just curious if this has found a fix at this point? I'd love to run a CM10.1 rom, but bluetooth audio is a must have for me.
Click to expand...
Click to collapse
the issues from 6 months ago have been gone for sometime now.
fantastic, thank you.
Life's been pretty crazy so i'm out of the loop on where everything has progressed. Once i get AT&T to warranty my phone for the GPS issues i'm having i'll try out one of the new builds.
Bluetooth audio has been working fine
But from my experience there have been problems with Bluetooth dialing.
A recent update of slimbean (version 6) seems to have corrected the problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I don't know that the issue really is fixed in 4.2.2. Doesn't seem to matter what ROM I run (I've tried CM, Carbon, AOKP), I can't get Bluetooth to work at all. It won't scan/find any of my devices or even turn on. I've resorted going back to stock rooted.
Has anyone found a work around or fix?
If bluetooth worked, it wont be 4.2.2. Best to go back to 4.1.x.
Sent from my SAMSUNG-SGH-I747 using xda premium
kt314 said:
I don't know that the issue really is fixed in 4.2.2. Doesn't seem to matter what ROM I run (I've tried CM, Carbon, AOKP), I can't get Bluetooth to work at all. It won't scan/find any of my devices or even turn on. I've resorted going back to stock rooted.
Has anyone found a work around or fix?
Click to expand...
Click to collapse
once in the past, when the CM roms were having bluetooth problems, I tried a different kernel and that fixed issues. The BMS Kernel is pretty stable and great performance/battery. you might give that a try.