Related
Hi all I was just wondering if someone notified HTC about the bug with the backlight.
Cause when the HD is locked the backlight will dim, but when unlocking the device the backligh will stay dimmed.
This must be some kind of bug so maybe handy to notify HTC ?
well, there is an option on the backlight dimmed？ isn't it
did you try to turn off / on your phone? that happened to me once.. but i didn't even have it locked. it hasn't happened to me since then .. dontk now why it happened since i hadn't done anything to the phone for a couple days. really weird
Aussi said:
Hi all I was just wondering if someone notified HTC about the bug with the backlight.
Cause when the HD is locked the backlight will dim, but when unlocking the device the backligh will stay dimmed.
This must be some kind of bug so maybe handy to notify HTC ?
Click to expand...
Click to collapse
Well did you notify them ?
Well not yet cause I was kinda of intersted if more people had the same problem
And wel turning the phone on and off is a solution , but no THE solution I find it quit annoying.
So do more ppl share this problem?
I did a week ago. Plus a few other bugs
Guess what - no response.
By the way, there must be half a dozen threads now about the backlight not coming back on after auto dimming!
If you're using the TweakHD in this forum, I guess it's the bug inside the software itself. Not the bug in HTC Rom itself.
Coz if I enabled the autolock using the TweakHD, the backlight will not light up after I unlock the phone. To switch on the backlight, I'd literally have to turn off the phone and turn it back on.
Correct me if I'm wrong.
I dont used that software and don't have that bug on my HD
I had this bug before using HDTweak, because i changed my registry settings manually... so it isn´t a bug of the HD Tweak.....
I too recently got this bug, havent had it before but I think it occurred when using autolock in tweak hd. So I turned offthat option but still no go.
You dont however have to reboot the device you could just click the battery and change the backlight setting manually (its alot faster than rebooting atleast).
You can also use Lumos - solved the issue for me
http://forum.xda-developers.com/showthread.php?t=450318
I got my 32GB AT&T Galaxy s4 one week ago today. Had to make an 8 hour road trip to get one but I would say it was very much worth it. I am having this maddening problem where a couple times a day the Display screen timeout keeps re-setting itself to (2 seconds) Unbelievably frustrating considering I can barely get the screen unlocked in 2 seconds and if I blink I have to do it all over again.
But wait, don't walk away just yet, there's more! I have already factory reset 3 stinking times trying to get to the bottom of this and when I woke up this morning it was back to (2 second). Furthermore it shows (2 seconds) in brackets like that so I assumed this was the default value but after checking just now while I was typing this post I noticed after changing it back to my preferred 30 seconds that the 2 second option vanishes. I'll snap a screenshot next time this happens.
Anybody else seen or heard of this problem? I assumed everybodys was doing this until I started searching and found 0 others with the problem. Is my phone The Chosen One?
Yes, i have it also and i found some forums where they discuss same problem, but no solution . Let's think what we have in common..
I have this app called Light Flow, do you?
Also which things you have on?
I have nfc, snart view, smart scroll, air view, air gesture
whatever61 said:
Yes, i have it also and i found some forums where they discuss same problem, but no solution . Let's think what we have in common..
I have this app called Light Flow, do you?
Also which things you have on?
I have nfc, snart view, smart scroll, air view, air gesture
Click to expand...
Click to collapse
Absolutely have Light Flow. I never leave home without it.
NFC. Yes
Smart View. No
Smart Scroll. No
Air View. Yes
Air Gesture. Yes.
I thought for sure it must be Smart Stay malfunctioning but I don't even use that.
maybe it has something to do with Light Flow?? this app caused weird bugs sometimes...
wanna try to turn it off for a while and let me know if it helps?
whatever61 said:
maybe it has something to do with Light Flow?? this app caused weird bugs sometimes...
wanna try to turn it off for a while and let me know if it helps?
Click to expand...
Click to collapse
Worth a shot. I'll play with it and see. Thanks for the idea!
I'm having the same issue and I also use Light Flow - any developments?
Work around
Guys, Did yo get this sorted? I had exactly the same problem which has been driving me mad but managed to sort a workaround which works perfectly. Let me know if this wasn't sorted and I'll post it.
I turned off "Power Saving" mode and it hasn't done it since.
EDIT: Nevermind... just had to give it more time.
Islandguci said:
Guys, Did yo get this sorted? I had exactly the same problem which has been driving me mad but managed to sort a workaround which works perfectly. Let me know if this wasn't sorted and I'll post it.
Click to expand...
Click to collapse
Would you kindly post the workaround? I'm out of ideas at this point.
You all have LightFlow. LightFlow causes other odd issues with Accessibility settings with the S4. Get rid of it and for now use Light Manager. Its much better IMO because it doesn't need to be activated in Accessibility settings, it just works.
Well, I didn't have power saving on and was still getting the problem. I uninstalled light flow and still had the problem. To resolve this for now I use an app called tasker, I had it already because it is a very cool app anyway but once installed if you don't have it just create a rule to deal with the time out issue. My rule for example went like this.
If the time is between 00.01 and 23.59 then set display timeout to 2 minutes. This fixed the problem for me.
In fact you could create other rules to do the same but this does it nicely.
Sent from my GT-I9505 using xda app-developers app
Islandguci said:
Well, I didn't have power saving on and was still getting the problem. I uninstalled light flow and still had the problem. To resolve this for now I use an app called tasker, I had it already because it is a very cool app anyway but once installed if you don't have it just create a rule to deal with the time out issue. My rule for example went like this.
If the time is between 00.01 and 23.59 then set display timeout to 2 minutes. This fixed the problem for me.
In fact you could create other rules to do the same but this does it nicely.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I set my rule to set the display timeout every time the display is turned on. I couldn't make it work the way you did it. I think I need more expertise.
Thanks again.
I haven't seen this issue again since starting this thread. Go figure. I haven't changed anything at all either. Still using lightflow in its entirety just like I was before and never changed anything else that I can recall. Weird.
Ok, I think I have this issue figured out. Here's how I resolved it:
1. Open Light Flow
2. Open Settings
3. Scroll all the way down to the section "Additional LEDs found"
4. Deselect "lcd-backlight control' and exit
I have the same exact problem.. Tried everything but with no luck!! Any one figured it out!??
OutCell said:
I have the same exact problem.. Tried everything but with no luck!! Any one figured it out!??
Click to expand...
Click to collapse
Just to let you guys know, i was able to fix this problem but with a sacrifice.. I reset my phone to factory settings & reinstalled all apps except for Light Flow (The problem did arise after i installed it) and now the screen times out perfectly with the duration i set. :good:
I just hope Light Flow fix this issue soon because i got used to the LED lights indications,, they were very useful.
Solution (I hope)
It's light flow's turn on screen option. They're patching it in the next update, but for now all you have to do is uncheck switch screen on in the notifications.
I tried this tonight. Will post back confirmation from the link
I just registered so I can't post the link to the forum I found it on.
Screen timeout
So I have a Galaxy s4 and started having this same issue with my phone. I would set the timeout for 3 minutes but it would reset back to 0 after so long. I dont have that application you all are talking about. I did root my phone which I do not think matters.
Essentially there are 2 spots to change the screen timeout I found.
My device>Display>Screen timeout
and
My device>Accessibility>Screen timeout (which was set to 0 even though the other was set)
I will let you know if this resolves the screen timeout issue for me.
Thanks
-Jon
goonies83 said:
So I have a Galaxy s4 and started having this same issue with my phone. I would set the timeout for 3 minutes but it would reset back to 0 after so long. I dont have that application you all are talking about. I did root my phone which I do not think matters.
Essentially there are 2 spots to change the screen timeout I found.
My device>Display>Screen timeout
and
My device>Accessibility>Screen timeout (which was set to 0 even though the other was set)
I will let you know if this resolves the screen timeout issue for me.
Thanks
-Jon
Click to expand...
Click to collapse
Disregard....still having the issue.
mharmon said:
I'm having the same issue and I also use Light Flow - any developments?
Click to expand...
Click to collapse
I also was having the same 2 second screen problem and found the unchecking the (turn on screen) to (Switch the screen on for 5 seconds when the notification arrives) in each of the notifications in Light flow has solved my problem. It seems that it was the cause of resetting the screen time out to 2 seconds.
Can someone else try this and confirm that this is the cause???
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Xxxdevilxxx said:
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Click to expand...
Click to collapse
Hi,
Does it always jump to the correct time?
I have seen this on different ROMS on other phones.
Xxxdevilxxx said:
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Click to expand...
Click to collapse
Pretty old. Used to happen on my S2 too.
i guess it is an intent that gets activated upon waking of the phone (by turning on the screen)... when you do that, it updates the screen and thats why.
but then again... that is only what i think.. if it should update it while the screen is turned off it would be an active process and use battery
Does it on mine too but only the clock on the main lock screen, the time on the top bar seems to be correct.
Sent from my iPad using Tapatalk (how ironic is that eh)
malybru said:
Hi,
Does it always jump to the correct time?
I have seen this on different ROMS on other phones.
Click to expand...
Click to collapse
Yes it always jump to the correct & exact time....it seems like a battery saving feature...if it is, other people with S4 should also experience it,no?
Tomo1971 said:
Does it on mine too but only the clock on the main lock screen, the time on the top bar seems to be correct.
Sent from my iPad using Tapatalk (how ironic is that eh)
Click to expand...
Click to collapse
For me i have a pattern Lock with time...so the moment i turn it on this is done on the lock screen clock...and yes the timer on the top bar seems to be correct(as in no jump).
Xxxdevilxxx said:
For me i have a pattern Lock with time...so the moment i turn it on this is done on the lock screen clock...and yes the timer on the top bar seems to be correct(as in no jump).
Click to expand...
Click to collapse
Hi,
I ,too, have the pattern lock screen.
But I have the Lightning Launcher.
So, there is no lag or delay on mine.
Maybe ,try a different launcher and see.
malybru said:
Hi,
I ,too, have the pattern lock screen.
But I have the Lightning Launcher.
So, there is no lag or delay on mine.
Maybe ,try a different launcher and see.
Click to expand...
Click to collapse
oh...will do
New to XDA. Hello all!
I am experiencing this clock lag as well. :/
It doesn't matter if I use a custom lock screen or the Samsung lock screen with "swipe to unlock".
It's easily reproducible, let phone sit for 10-15 min and if you press the unlock button you'll see the wrong time for anywhere from a fraction of a second to a few seconds! and then it will update to correct time. Super annoying if I just want to know the time. Also, I've found that the amount the clock is behind is proportionate to the amount of time the phone as been idle....to a point...
I've seen the clock be over an hour off but it doesn't drift much more than than. Like a few folks mentioned, this should be running in the back ground. What is confusing to me is the clock in the top right is correct, so the phone is monitoring the clock...it's just not updating the lock screen clock.
Hopefully we can find a work around.
Not too keen on a new launcher...at least not until others who have seen that lag switch over and confirm it as a fix...but I don't think it will help, because the lock screen is still a Samsung process not controller by the launcher (i don't think)
Any thoughts?
The clock on the main unlock screen is essentially a widget. As a power saving feature, it only updates as necessary, which would be when you turn your phone on to look at the time. The time at the top of the screen in the notification bar is not a widget, it is a built in process that is always active. That is why it is current and the large clock, "the widget", is off until you turn your phone on to look at it.
My phone does the same thing. As does pretty much everyone's. It is not anything wrong with your phone, it is just the way it is set up. It is usually only delayed by a second or two, at best.
If it is an issue, you can always just remove the widget and use the time at the top of the screen to check. Or try a different app and set the update frequency.
It's not that big of a deal to me, I know it's always off until it refreshes, so I just give it a second to update.
My friend just got a G2 and is having this issue as well. I use a pattern unlock and am running Clean Rom. Some times when I try to unlock the screen it just randomly shuts the screen off while Im trying to draw the unlock pattern. I'm hoping someone has a solution for this.
Thanks
prerunnerseth said:
My friend just got a G2 and is having this issue as well. I use a pattern unlock and am running Clean Rom. Some times when I try to unlock the screen it just randomly shuts the screen off while Im trying to draw the unlock pattern. I'm hoping someone has a solution for this.
Thanks
Click to expand...
Click to collapse
When I use the power button on the back of the phone instead of the knock-on, I had this same problem. I was rooted but on stock rom. I've read other posts about the same problem. I would try to put in my pattern and midway through the screen turns off. Sometimes it would be two seconds, sometimes like 10. Don't know what the problem was.
My knock-on feature was barely working. Some guy recommended getting this case: http://www.amazon.com/gp/product/B00FEQU1NG/ref=oh_details_o01_s00_i00?ie=UTF8&psc=1
I needed one anyway so I got it. Haven't had an issue with the knock-on feature anymore. No idea why haha but whatever, it works. Kind of a ghetto workaround.
I'm having the exact same issue.
Factory reset several times, installing my usual apps or having just the default apps without updating them didn't make any difference.
After a factory reset I disabled the knock knock feature and still, when I try to bring my screen up and unlock, it immediately shuts off, preventing me from swiping.
Another side effect is, when I make a phone call, the screen immediately goes blank and it will never turn back on unless I restart by holding on to the power button, this is especially inconvenient when I need to dial some options (i.e.) voice mail options, corporate automated options.
All of the above happened while I had my Incipio feather shine case. (incipio.com/cases/smartphone-cases/lg-smartphone-cases/lg-g2-cases/lg-g2-cases-verizon/feather-shine-case-for-lg-g2-verizon.html) I took the case off and did another factory reset last night, and so far the knock-on rate has improved from 0% to at least 60-70%... Strangest thing.... If anyone else can shed some light onto what the hell happened/is happening, I'd really appreciate it! It's been a frustrating ride since this problem surfaced about a couple weeks ago. I had this phone for about 2 months now....
I'm having this problem too. It happens with both knock on and power button wake. I have noticed that the screen is not actually immediately turning off, though. In a completely dark room, I can still see faint outlines of my lock screen. Then, after the brief time out for dimming, the screen will go to its dimmed brightness (which is far brighter than what's concurring after waking the phone). I'm able to unlock, reboot, and usually that will solve the problem for a little while, but this is getting frustrating.
Stock rom, rooted, TWRP, Nova Launcher, and xposed. I'm not sure what's causing this.
I know it's been said many times but if you block the sensors with your fingers after waking the device, your screen will turn back off. Its a security feature/bug and I would assume this is what's happening here.
I ended up getting a certified-like new replacement from verizon... While I had the old one, I did a test with that sensor you're talking about and it didn't really make a difference. I made sure the sensor area was clean without anything covering it and the problems persisted. I really hope LG can find the root cause of this and fix it... Very frustrating.
Not a bug. But this is a feature we do not want. It is called proximity sensor. It is sensing too far imo. It is actually the one next to the front cam. Dont block it within 5 inches in front or you phone will sleep again. That should work with flip case. Annoyingfunction imo. Your device is not broken.
yonba said:
Not a bug. But this is a feature we do not want. It is called proximity sensor. It is sensing too far imo. It is actually the one next to the front cam. Dont block it within 5 inches in front or you phone will sleep again. That should work with flip case. Annoyingfunction imo. Your device is not broken.
Click to expand...
Click to collapse
exactly. the sensor in very sensitive to being covered. Because its hypersensitive and having undesireable effects I would consider this a bug since it is buggy.
I figured out what the issue was, at least on my phone.
Lightflow was detecting a bunch of alternate LEDs, which I felt inclined to tick the check boxes for, just to make sure it could control the LED fully. Having those boxes checked caused my phone to do this. Everything is fine since I've unchecked them, though. No sensor issue, no proximity/case issue, just Lightflow (which still works without those alternate LEDs checked).
Having this issue with my G2, its very annoying. Knock on does not work and screen shuts off after about half a second that I press the power button. Had to reflash to stock the first time this happened and fixed it but after about a month the same problem occured. I could however open by pressing one of the volume button together with the power button.
Hoping to find permanent fix for this problem.
thirtynation said:
I figured out what the issue was, at least on my phone.
Lightflow was detecting a bunch of alternate LEDs, which I felt inclined to tick the check boxes for, just to make sure it could control the LED fully. Having those boxes checked caused my phone to do this. Everything is fine since I've unchecked them, though. No sensor issue, no proximity/case issue, just Lightflow (which still works without those alternate LEDs checked).
Click to expand...
Click to collapse
Yeah that's it Lightflow
Disabling all the additional led found resolve my problem
THX
bigiuly said:
Yeah that's it Lightflow
Disabling all the additional led found resolve my problem
THX
Click to expand...
Click to collapse
Please tell me where to find these settings
taqikazmi said:
Please tell me where to find these settings
Click to expand...
Click to collapse
Settings / Led Control
bigiuly said:
Settings / Led Control
Click to expand...
Click to collapse
There is no option in settings like LED.
taqikazmi said:
There is no option in settings like LED.
Click to expand...
Click to collapse
In settings of Lightflow app
bigiuly said:
In settings of Lightflow app
Click to expand...
Click to collapse
I installed the app and fund the settings but all of them are already unchecked
Following the update to 5.1.1, when I switch on the Note 4 using the power button, the display fades in, slowly.
It takes ~1 second and is very annoying. I've been through display settings and a few other things, but nothing I do will make it appear instantly. I've tried a few web searches, but getting nothing relevant.
Anyone else see this? Anyone got a fix?
Thanks
Devany said:
Following the update to 5.1.1, when I switch on the Note 4 using the power button, the display fades in, slowly.
It takes ~1 second and is very annoying. I've been through display settings and a few other things, but nothing I do will make it appear instantly. I've tried a few web searches, but getting nothing relevant.
Anyone else see this? Anyone got a fix?
Thanks
Click to expand...
Click to collapse
Disable finger print lock.
Fingerprint lock was never enabled on the device. I figured that if someone wanted to steal it, I didn't want to motivate them to cut my finger off.
Also, I read the "Lag after 5.1.1 update", but assumed (!) that the fingerprint issue would not affect me because it had never been switched on.
On a hunch, I enabled fingerprint lock, then disabled it... problem resolved. Nasty.
Thanks.
Devany said:
Fingerprint lock was never enabled on the device. I figured that if someone wanted to steal it, I didn't want to motivate them to cut my finger off.
Also, I read the "Lag after 5.1.1 update", but assumed (!) that the fingerprint issue would not affect me because it had never been switched on.
On a hunch, I enabled fingerprint lock, then disabled it... problem resolved. Nasty.
Thanks.
Click to expand...
Click to collapse
Glad your issue resolved.