Related
I haven't fully tested this issue yet mainly because I've only had the phone for a few days... I wanted to check if anyone else had this problem.
Under Settings -> Sound & Display -> Notification Flash
I have all the options ticked.
In theory, whenever I have a missed call or a SMS or email etc, I should be able to tell that I need to check my phone be a little blinking light in the top right corner off the screen. I just came back to my phone and this LED wasn't blinking but when I turned on the phone, there was a missed call and a SMS.
Other times, it seemed to work fine.
Anyone else noticed this problem?
it only flashes for 5 mins and then stops. There is no way to change this without additional apps.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Oh... How disappointing. Pretty useless imo. Thanks for the info. I wonder if they will fix it. My previous phone, Touch Diamond, had something similar but it never stopped flashing until you looked at your missed calls.
Now that explains things. I tend to look for the led after I've not used the phone for a while. In my pocket or elsewhere. Quite a few times I've seen no flashing but have a notification in the top left. I thought it was another one of those little 'features' we keep finding.
Yeh i discovered this awhile back and it's annoying as hell, i just use a app called Missed Reminder which can be configured to allowed it to keep flashing indefinitely
I was just going to make a post about this. I thought the LED notification wasn't working at all on my Desire, since I've never seen it, but perhaps it had just stopped before I had the chance to catch it, then
ardsar said:
it only flashes for 5 mins and then stops. There is no way to change this without additional apps.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
What apps are you referring to? It would be nice to be able to have the LED flash longer.
I'm guessing this is to save battery time, I don't know how much power a small LED uses but it surely can't help with the already abysmal battery life
I first thought the LED was located behind the optical trackpad, because the trackball on my Hero could light up. I think the LED-notification is pretty dumb since it's almost invisible when it lights up. The lighting trackball was much much better
This is a known issue. I thought that did not happen in Android, but I guess I was wrong.
If the phone work in Windows Mobile, there are a registry key to let assign values to the options, so they are usable.
Here: http://forum.xda-developers.com/showthread.php?p=4846399#post4846399
In Android, I have no clue... maybe my info help in any way.
PMoto
It would be nice to be able to change the flash time from the default 5 minutes, or atleast an option for no time limit.
I know it's to help save battery life, but I'm willing to say that the light flashing will use less battery then the back light coming on everytime I'm away from my phone for more then 5 minutes, from me checking to see if I have new messages, email, or missed phone calls.
Same issue with my recently purchased A40.
No blinking at all despite screen flash notification selected.
Hope someone can help
Ive tried several roms and all seem to do the same thing. It may have even done it on the stock rom but I dont remember.
My LED notification when I get txts or emails is not blinking correctly. It will blink very irregularly for the first 15 seconds and then sometimes wont blink at all after that. Ive tried custom apps like go sms and an app that forces the light to come on at fixed intervals but it still wont work right, like something is conflicting with the light coming on.
Has anyone else experienced this or know a fix?
redspeed said:
Ive tried several roms and all seem to do the same thing. It may have even done it on the stock rom but I dont remember.
My LED notification when I get txts or emails is not blinking correctly. It will blink very irregularly for the first 15 seconds and then sometimes wont blink at all after that. Ive tried custom apps like go sms and an app that forces the light to come on at fixed intervals but it still wont work right, like something is conflicting with the light coming on.
Has anyone else experienced this or know a fix?
Click to expand...
Click to collapse
What rom are you running now?
Im on bonsai and my led seems to be pretty good..
davidrules7778 said:
What rom are you running now?
Im on bonsai and my led seems to be pretty good..
Click to expand...
Click to collapse
Im on the latest Frankenstein rom, but Ive tried the latest Bonsai one before this and it did it as well.
Theres others experiencing this as well but I havent found any fixes for it yet, even the apps they recommend dont work for me.
http://www.google.com/search?q=led+...&aq=f&aqi=&aql=&oq=&pbx=1&fp=506afe366bdeb92b
Try Missed Reminder
My configuration:
Start/Stop Service (Check)
Autostart (Check)
Everything else disabled.
Preferences settings for Missed SMS/MMS/Missed Calls/Missed Gmails
Turn the screen on (Unchecked)
Popup (Unchecked)
Vibrate (Unchecked)
Ringtone (Silent)
Blink Led (Unchecked)
Notification Intervals (1s)
Number of repeats (Forever)
I found that by using these settings, it forces the device to keep the LED blinking. I also found that you can then use apps with custom LED settings like Go SMS to change the color and LED blink rate with no problems.
Its always done this. Maybe one day we can get a fix. Sometimes mine works just fine and other times it is very sporadic.
redspeed said:
Ive tried several roms and all seem to do the same thing. It may have even done it on the stock rom but I dont remember.
My LED notification when I get txts or emails is not blinking correctly. It will blink very irregularly for the first 15 seconds and then sometimes wont blink at all after that. Ive tried custom apps like go sms and an app that forces the light to come on at fixed intervals but it still wont work right, like something is conflicting with the light coming on.
Has anyone else experienced this or know a fix?
Click to expand...
Click to collapse
Sent from my Evo Killer!!!
Same here. Always done this from day one. I had a brand new Epic, played around with it, and the LED crap never worked. On that particular phone, the PRL would never update so I took the phone back and got another one. PRL worked fine, and the LED on that phone did the same thing.
I also have the LED to set to keep blinking in Chomp SMS, and it does not work. I have ALWAYS gotten the sporadic LED blinks when I get a message, and then it disappears.
This has happened on the STOCK phone out of the box, as well as with DK28 and Bonsai 2.0.1.
So regardless of the ROM you use, you're still going to be out of luck. Until Samsung can get this fixed...hopefully in the new Froyo build coming out next week, then you are stuck, just like many other people are.
I have not tried that program that was posted by Isira, but you may give it a try and see if that fixes your problem. I tried a program similar way in the beginning and it didn't work.
It's worth a shot though. But Samsung knows its a problem, and that's all there is to it. You're stuck with it, just like me.
UPDATE I just tried the program and so far it seems to work. My SMS is still blinking. Not quite a true second like it is set, but it is blinking. I'll keep testing it, but you may give it a try.
I did try the missed reminder app and messed around with the settings but it still blinked sporadically. On a side note I used the samsung tool to update to EB13 and stock 2.2 and the blinking seems back to normal...
Hi,
Firstly, please don't attack me for not using search. I have spent an hour or so searching these forums for any answers, but there are a LOT of hits for LED-related problems and none seem to match
My G2 was running CM7.0.3 when I got it, and the charge LEDs (both orange and green) were working correctly. Last weekend, I upgraded to CM7.1RC1 using ROM Manager. I did a full wipe of everything rather than just a dalvik cache wipe. Now, I am finding that at night when my phone is charging I am getting no LED lights at all. No orange light or green light. Has anyone heard of a similar problem to mine?
Thanks!
UPDATE: Actually, I don't think my LEDs are working at all. They are certainly not flashing when I receive mail.
try this...its similiar
http://forum.xda-developers.com/showthread.php?t=851685
patch by pershoot. it could also just be a broken sensor.
p.s. its pretty sad when people ask not to be attacked...gives a glimpse of some characters we have on xda
Thanks for the info!
On further investigation, seems my charge LED is working but somewhat intermittently. I thought it might be related to the "Dim LED" option in Quiet Hours, but after toggling it my LED seemed to be working regardless now. I might try the pershoot patch anyway for kicks, but I guess this is one to chalk up to "weird LED behaviour" - seems to be a very common problem
busbutt said:
Thanks for the info!
On further investigation, seems my charge LED is working but somewhat intermittently. I thought it might be related to the "Dim LED" option in Quiet Hours, but after toggling it my LED seemed to be working regardless now. I might try the pershoot patch anyway for kicks, but I guess this is one to chalk up to "weird LED behaviour" - seems to be a very common problem
Click to expand...
Click to collapse
Sorry if I ask, have you had this problem as well? http://forum.xda-developers.com/showthread.php?t=1230776
To be honest, I never let my phone get that low on battery, so I've no idea what it did in CM7.0.3 or what it does in CM7.1. Sorry!
Sent from my HTC Vision using XDA App
my wife has the att nitro hd, when the screen goes off during a call sometimes nothing including power button will turn it back on. Anyone know of a fix? did the ATT small update fix this?
Actually it comes back on after a long minute or two. Not very helpful if you need the dialpad or keys, etc.
I have just rooted it for her and installed CWM.
I have added a few proximity tweaks to build.prop
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
I'll have to take alook into the lg hidden dialer menu to see if I can disable this.
I dont like this sensor on my device either, but I have an option in settings to disable it, which makes it bearable.
thanks for the help guys.
I have noticied LG throws together some junky builds, typos, bad english/grammar. Wonky sensors etc. Incorrect kernel build ReadMe's
I thought I recall someone with another device just placing a peice of tape over the sensor. hmmm..worth a try.
cheers.
chrisrotolo said:
gsm.proximity.enable=false (rebooted twice but screen still goes off)
also used the ro.lg.proximity and the mot.lge.proximity (dont recall exact wording) both were set to a value of 5.
Click to expand...
Click to collapse
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
aremcee said:
Congrats. Today, you learned that most of the "tweaks" found at XDA are utter bull****
Click to expand...
Click to collapse
What about the tweaks that aren't BS? Are they already included in your CM9 builds?
From what I can tell, pretty much the main thing that build.prop is good for is providing information about the system and software (i.e. info about the build). It's not really used much for useful configurations as far as I know.
networks tweaks actually have doubled me download speed.
I still have faith.
but can anyone answer my questions I posted in ICS SLim thread and PM'ed Andasa , no responses yet.
does ICS slim or CM9 have option to keep lcd no during call? and does it work??
what's working not working? I found changelogs but not a working/not working list for CM9.
and has anyone successfully restored a nandroid from ICS to GB without real issues?
thanks guys.
i doubt the ota fixed your issue as the issue is not one that occurs for every nitro.
I can tell you that when I make a phone call they screen stays no.
what's working not working, well, many of us are running it daily with no probs.
as you prolly know, it is a nightly build so a public list of what's working or not isn't rly part of the deal.
i've succesfully restore a nandroid from both slim and cm9 back to the stock att rom and others many many times. dozens.
thanks good enough.
I will have to give it a go.
would you recommend one or the other?
CM9 or slim?
thank you.
well, I like them both a lot. slim is just a trimmed down version of cm9 and i _think_ it does run just a bit snappier........maybe..but it's not wildly different from cm9. I usually switch back&forth throughout the day.
There's no setting in CM9 to disable the proximity sensor, although there may be a way to do it.
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
no driver said:
We just got a Nitro HD for my wife and her phone also has this issue. I have not gotten to know the phone well enough to try rooting or anything else of that nature, it's pure stock.
When she makes a call the screen turns off immediately after hitting the call button and will not wake up. When she receives a call we get a glimpse of the in-call screen with the various buttons etc but then the screen turns off. If the other party hangs up her screen turns back on, but if she calls something automated, like voicemail, she can't do anything except pull the battery to disconnect.
I've tried putting my thumb over the proximity sensor, hitting all buttons including power, and nothing makes the screen wake up or turns the phone off other than a battery pull.
The phone was running a build from last November when we first got it (V10i?) and today prompted us to update, so I did that hoping it would solve the problem. The phone is currently on V10j, but the problem persists.
Any help?
Click to expand...
Click to collapse
If you bought it from a store, get it exchanged for a new one.
actually works much faster on cm9, but therr still should be an optin to keep lcd on during call. i found some free apps that will disable hardware drivers but cant find the name of the proximity sensor driver, only that is named LGE.
Unfortunately it was given to us by a friend after my wife lost her Captivate, so taking it to a store to exchange is probably not going to work too well. As far as I can tell it was never used before we got it--the battery was still in it's own sealed pouch, the texting and driving warning was on the phone, and the phone went through the whole initial setup routine--but they didn't send us the box, I guess to cut down on mailing costs. I was hoping there was a known solution.
Ok, I downloaded two proximity sensor test apps today, but neither showed any activity. On my Captivate I get different readings with Proximity Sensor Finder (market link), but on the Nitro it is stuck at 3cm and it doesn't register anything no matter where I put my hand over the phone.
Can someone whose phone works right try installing this app and make sure that it picks up different readings on this device? OP, if you are still having issues, can you also try this app and see if it is static for you?
Thanks.
Took off the screen protector that they installed at the AT&T store and now the proximity sensor works just fine. OP, do you have a screen protector on your device?
we had an awfully thick one from att. we have since changed it to a super thin one. screen off is not a real problem on cm9, however i feel all devices should have the option to disable proximity sensor/keep lcd on during calls.
It's worth trying to use the warranty on the phone. Even though you dont have the original sales reciept, the phone has been released for less than a year, so no matter when you bought it, it is still within it's year long guaranteed warranty window.
Finished reading the thread, I suppose this post is now irrelevent
hello everyone , so i use to have this bug back to kitkat also but it wasn't happening as often as it doesnt now that i have lollipop rom installed on my galaxy tab s T705 , the issue is with touch key lights which stays on even when i have them always off from settings , they act super weird when they are in that mode , they go off few sec after screen is off and if i shake the device they go on again as it looks like they are connected to accelerator sensor or something lolz ,the solution is super easy tho just hit the power saving on and then off again and they work normally again i heard some other ppl dealing with same issue but i wanted to know if there is a perma solution for it or not , im sure its a software issue but is there a way to fix it ?
Install a custom rom like cyanogen or something stock based.
I have the same problem. I usually have it set to turn the lights off after 6 seconds, but after a couple of days they don't work anymore. I would change the setting to off, then on, then back to 6 seconds, and it'll work again. After a few more days, they stop. I haven't seen a permanent fix for this.
Sent from my SAMSUNG-SM-G925A using Tapatalk
Same for me. Would usually opt to have the buttons backlight always off, but randomly it starts actin like always on, although the settings remains 'always off'. Toggling the setting to anything else and back to always off fixes the problem temporeraly.
Im running stock swiss lollipop on my t700.
Yes, this is driving me nuts too! I hope they resolve this in the next update and soon!
Sent from my SM-T700 using Tapatalk
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
Me too have the touch key settings to always off and found the same problem.
In my case I think it only happens when I plug the Tablet to AC.
Did this happen to anyone under another circumstances?
Thanks in adavance!
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
TLAgnesB said:
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
Click to expand...
Click to collapse
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
TLAgnesB said:
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
Click to expand...
Click to collapse
Yes but you will need root.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
I heard that there's a new update available for the Tab S. (I already returned my tablet before my 30 days to get a full refund.) Did any one get the new update, and if so, did it fix the issues like this touch key light?
Hey,
I had this problem on the original KK software - upgraded to Lollipop a few days back and I still have the bug... in fact, it is even worse! Occurs more frequently than on LP.
I wouldn't mind leaving the lights on all the time, but they're so damn BRIGHT, and there's no way to adjust the backlight intensity!
Cheers,
Su
I found this solution on another forum...
If you enable smart stay, the touch key light duration will work properly.
Any further movement on this?. I've found that if I take my tab out of the book case the problem goes away. Seems like it's a bug with the case sensor.
No movement that I'm aware of. I'm really frustrated that there hasn't been a fix after all this time. I'm holding out hope that if there is ever an update to Marshmallow, that the issue will go away. Interesting observation about the case -I have a book case on mine. I'll remove it and see what happens...