So for the last couple of days my HTC One M7 would recieve a notification and the screen would just stay on the entire time for no apparent reason. Im on latest OmniROM and its starting to bug me. Like for instance I get new mail on Gmail in the middle of the night. The screen turns on, it show the notification, and it doesnt turn off until I turn it off. If I restart, its fine for a few hours, but as soon as I get a notification, the problem reappears.
Nobody, seriously?
Sinistersky said:
Nobody, seriously?
Click to expand...
Click to collapse
Dude, you took less than 24 hours before bumping. Not everyone checks the forums regularly.
Also, per the FAQ, bug reports belong on jira.omnirom.org
However the behavior you describe is a feature in Omni. Let me guess - you turned on Active Display and forgot about it? (Since it's off by default, and the behavior you describe is not something I've ever seen on any device when AD was disabled.)
Entropy512 said:
Dude, you took less than 24 hours before bumping. Not everyone checks the forums regularly.
Also, per the FAQ, bug reports belong on jira.omnirom.org
However the behavior you describe is a feature in Omni. Let me guess - you turned on Active Display and forgot about it? (Since it's off by default, and the behavior you describe is not something I've ever seen on any device when AD was disabled.)
Click to expand...
Click to collapse
Nope.
Just to note, I am seeing the same thing on my nexus 5 running the 10/13 nightly. AD is disabled and I have never enabled it. I was wondering why sometimes I would pull my phone out of my pocket and the display would be on. Since reading this I have verified that this happens when I get a notification. I will submit a bug report on jira.omnirom.org.
eta: oops, I just realized you need an account for jira.omnirom.org.
VFO said:
Just to note, I am seeing the same thing on my nexus 5 running the 10/13 nightly. AD is disabled and I have never enabled it. I was wondering why sometimes I would pull my phone out of my pocket and the display would be on. Since reading this I have verified that this happens when I get a notification. I will submit a bug report on jira.omnirom.org.
eta: oops, I just realized you need an account for jira.omnirom.org.
Click to expand...
Click to collapse
This doesn't occur on any of my devices, including a Nexus 5.
Are you running some sort of notification customization app of some sort?
Define "screen on" - Lockscreen? Blank with backlight on?
Entropy512 said:
This doesn't occur on any of my devices, including a Nexus 5.
Are you running some sort of notification customization app of some sort?
Define "screen on" - Lockscreen? Blank with backlight on?
Click to expand...
Click to collapse
I am not running any notification customization apps just straight Omni nightlies. It happens with any notification that I receive. It goes to the lock screen and stays on until I unlock it. I am going to wipe and reinstall the ROM and try and determine if it's an app issue.
VFO said:
I am not running any notification customization apps just straight Omni nightlies. It happens with any notification that I receive. It goes to the lock screen and stays on until I unlock it. I am going to wipe and reinstall the ROM and try and determine if it's an app issue.
Click to expand...
Click to collapse
Do you have "screen stays on while charging" enabled? Even then, it shouldn't be turning on for a notification in the first place.
None of my devices turn on for a notification in any situation, and the screen always shuts off quickly (faster than the screen timeout setting) when it's at the lock screen unless "screen stays on when charging" is set in Developer Options.
Related
I'm having a couple off issues with the latest release.
First of all I can't turn Wifi off and keep it off. Everytime I go into the menu to check on it, it's checked, so I uncheck it, and it'll turn off for a minute or two and then all of a sudden turns right back on. This is extremely annoying.
And the other is that it seems like in some apps my touchscreen presses don't keep the phone awake. So I can be interacting with the screen and then all of a sudden it'll go dim. I'll keep pressing on screen buttons and a few seconds later the display will shut off completely. The only way I can jog it back awake in its dimmed state is to move the trackball or press some other hardware button.
Anyone else seen these problems?
LPChris said:
I'm having a couple off issues with the latest release.
First of all I can't turn Wifi off and keep it off. Everytime I go into the menu to check on it, it's checked, so I uncheck it, and it'll turn off for a minute or two and then all of a sudden turns right back on. This is extremely annoying.
And the other is that it seems like in some apps my touchscreen presses don't keep the phone awake. So I can be interacting with the screen and then all of a sudden it'll go dim. I'll keep pressing on screen buttons and a few seconds later the display will shut off completely. The only way I can jog it back awake in its dimmed state is to move the trackball or press some other hardware button.
Anyone else seen these problems?
Click to expand...
Click to collapse
I've seen similar issue with the screen staying awake, thought it's just the phone. Also not sure if it's related sometimes I'll click on a button for example, but it will almost not recognize the spot i'm clicking on and click something else on the screen.
These are the same problems I've been seeing on my phone. I imagine it is due to the multitouch hack, but I haven't gotten the motivation to downgrade my phone back to 1.31.
Do you have anything installed like power manager or locale? One of those progams may be turning on wifi.
Dharkaron said:
Do you have anything installed like power manager or locale? One of those progams may be turning on wifi.
Click to expand...
Click to collapse
Nope, I had installed Power Manager once a while back and didn't like how it worked so I uninstalled it. Don't have Locale installed either. I ran the task manager to see what was running and there was nothing that I could tell that would turn the wifi on.
The touch issues are rather widespread amongst 1.41 users. However, don't know what's up with ur wifi. I have a strange issue with my wifi as well though. Whenever I boot up my phone and wifi was enabled when it turned it off. I get 2 not responding errors. Everytime. Its like clockwork. With 3g? Never. It took me about 20 wipes and 10 or so hours to finally figure it out. Hopefully all these problems will be fixed with rc33
I have also noticed that Applications don't check for new updates anymore. even when I go to "My Downloads", It used to show "free" next to any application that has an update or has been uninstalled. Now it shows "Installed" next to all the applications but when I go to the application by category, It shows up as "Free" meaning that there is a new version.
the case in simple points:
1. when I open the Application..... It doesn't detect the update.
2. when I go to "My Downloads" in the market, It doesn't show "Free" next to any application that has an update.
But if I go to the application by category, It shows "Free".
LPChris said:
I'm having a couple off issues with the latest release.
First of all I can't turn Wifi off and keep it off. Everytime I go into the menu to check on it, it's checked, so I uncheck it, and it'll turn off for a minute or two and then all of a sudden turns right back on. This is extremely annoying.
And the other is that it seems like in some apps my touchscreen presses don't keep the phone awake. So I can be interacting with the screen and then all of a sudden it'll go dim. I'll keep pressing on screen buttons and a few seconds later the display will shut off completely. The only way I can jog it back awake in its dimmed state is to move the trackball or press some other hardware button.
Anyone else seen these problems?
Click to expand...
Click to collapse
i havnt had a problem with it staying on, i noticed that my phone was dimming to quickly. I know theres probably an adjustment somwhere (i think at least) but i havnt had any problems what so ever with it.
Very strange. I haven't had either problem (wifi or touchscreen). I have noticed that my battery drains more quickly than it used to, but I have been blaming this on the DroidSans autorotate feature always flipping the screen everytime I move the phone (I mess with the phone an awful lot).
Droidsan
I can not get auto rotate on JF RC-33. Does anyone have this problem???
another issue with with this version was that all my ringtones were changed for my contacts and stuff
pretty wierd.
i don't have any problems mentioned ATM.
JF RC30 to RC33
stonefurry said:
I can not get auto rotate on JF RC-33. Does anyone have this problem???
Click to expand...
Click to collapse
DroidSans Tweaks checks the version. At the moment it's not going to recognize RC33 as a valid version. Wait for it to be updated.
danguyf said:
DroidSans Tweaks checks the version. At the moment it's not going to recognize RC33 as a valid version. Wait for it to be updated.
Click to expand...
Click to collapse
What he said... But don't forget to enable auto rotate in your browser though. You don't need droidsans for that.
My screen randomly turns on and sits at the lock screen for a few seconds for no apparent reason. There are no pending notifications, etc. I assume there might be a rogue app causing this, but I don't have that many installed and even less apps doing any background tasks. Any idea on how to find the culprit?
I found this bug report where some apps are mentioned, but I'm not running any of them.
https://code.google.com/p/android/issues/detail?id=39625
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
I noticed that the phone wakes up whenever it reconnects to Wi-Fi. I was changing some router settings last night and I constantly saw the phone waking up shortly after the router rebooted. However, this is not the only scenario where it does it.
Mine has done the same, no idea why, only seen it the once, but it certainly happened, sitting three feet away from me, and suddenly Bingo! its on.
Mine wakes every few minutes. Certain apps (tasker, facebook etc) and syncing seem to cause it to happen more often but even if I disable most apps it still happens. I've been unable to identify the source with better battery stats. It happens bone stock and on CM10.1. I'm still getting better battery life than my GNexus but it's maddening.
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
ludovicien said:
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
Click to expand...
Click to collapse
So my Nexus 4 doesn't want to go to sleep.
- I have sleep set to 15 seconds
- Dream is off (just in case)
It just stays on. It doesn't matter if it's on the the lock screen or at the home screen. I'm guessing some app is keeping it awake. It just started last night, but I don't think I have installed any new apps. Maybe it from an update.
solved
My phone's screen also used to wake up randomly. it was very annoying, especially at midnight
finally, I found out the reason by using "Wakelock detector" app which is freely available in market.
here is XDA thread about WLD: WLD at XDA Thread
the cause of problem was ad Notification, it was holding "full wakelock" (you can see it in screenshot)
good Luck!
Refer Wakelock Detector at XDA
Ramdom screen wake up issue solved
Dear all,
I was experiencing random screen wake issue in my XOLO PLAY smartphone.
The problem was with the AppLock software. After upate is this issue appreard. Earlier AppLock was there and no issue was experienced.
I am writing to AppLock team to fix the bug.
:angel:
All the best
Regards
nitin5062
hcedillo said:
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
Click to expand...
Click to collapse
U made an account to post THIS only?
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.
Anyone else having a bug where the screen does'nt turn off after the designated time out is reached? I have set mine to 15 seconds but it only dims down after 7 seconds and remains dimmed forever and ever.
Only way to get phone to work normally is to restart it. But the bug keeps coming back every day, sometimes serveral times a day.
Now I have to turn off screen manually by pressing the powerbutton.
Update Solution:
I actually had locked(in recents) Edge browser into the memory so it always would be available lightning fast. I just unlocked and closed it from recents app, and now the screen shuts off normally. Apparantly there was probably a hidden ads-page active somewhere keeping the screen from shutting off properly.
corb06 said:
Anyone else having a bug where the screen does'nt turn off after the designated time out is reached? I have set mine to 15 seconds but it only dims down after 7 seconds and remains dimmed forever and ever.
Only way to get phone to work normally is to restart it. But the bug keeps coming back every day, sometimes serveral times a day.
Now I have to turn off screen manually by pressing the powerbutton.
Click to expand...
Click to collapse
Any developer options turned on?
dottat said:
Any developer options turned on?
Click to expand...
Click to collapse
Not much, only the Force all apps to be resize:able.
The screen awake while charging is off. USB-debbuging also.
corb06 said:
Not much, only the Force all apps to be resize:able.
The screen awake while charging is off. USB-debbuging also.
Click to expand...
Click to collapse
I have encountered this bug occasionally, a few times this happened some web page was open (No video was playing) not sure if this was the case with you sometimes some ads or something on the web page can keep the browser active. I did not think much of it nor explored it much but will keep an eye out if it reoccurs.
Turn off Developer options for now.
Does it happen in Safe Mode?
Make sure a 3rd party app isn't the cause.
Clear system cache on the boot menu.
.
warriorvibhu said:
I have encountered this bug occasionally, a few times this happened some web page was open (No video was playing) not sure if this was the case with you sometimes some ads or something on the web page can keep the browser active. I did not think much of it nor explored it much but will keep an eye out if it reoccurs.
Click to expand...
Click to collapse
Big Thanks! I actually had locked Edge browser, Telegram and File Manager+ into the memory so they would never be killed off. I just unlocked and removed them all, and now the screen shuts off normally. What a relief [emoji846]!
Using Adguard adblock and Edge content blocker so it might have been a hidden ad of sorts keeping phone screen active.
Sent from my SM-N986B using Tapatalk
corb06 said:
Big Thanks! I actually had locked Edge browser, Telegram and File Manager+ into the memory so they would never be killed off. I just unlocked and removed them all, and now the screen shuts off normally. What a relief [emoji846]!
Using Adguard adblock and Edge content blocker so it might have been a hidden ad of sorts keeping phone screen active.
Sent from my SM-N986B using Tapatalk
Click to expand...
Click to collapse
Glad it worked, I suggest copy paste above text, what you observed the reason was for this to happen and what you did to fix it and add that information to the first post. Trust me it will help many.
Also change the title to: [Solved] - Screen won´t turn off - only dim down