Does anyone else have very frequent pauses (0.5 to 3 seconds or more), where the screen and haptic response stops, then when it recovers it processes all the touches which happened when it was paused? I'm getting it a lot (pretty much within 10 seconds each time I turn on the screen, then every so often with use).
Do I have some bad bit of hardware in there causing it to stall or is this just the CPU not keeping up?
I have seen it lag a bit once in while, but nothing quite that often. Could be a software issue... I would try to reboot into safe mode first and see if the problem recurs, but I haven't figured out how to do that yet. :/
Related
Hi all,
Kind of a strange issue I'm noticing with my Nexus 4. The phone seems to, by default, have a screen turn-off time setting of "after 15 seconds of inactivity" for the display options. I tend to like to have my screen stay on a little longer especially if I'm in the middle of a conversation or I'm watching something and my attention gets diverted momentarily. 15 seconds is just way too short. So I change it to a larger value, like 2 minutes for example, and the setting keeps, for a while. But every so often it will start turning off quickly again and when I check, sure enough it has reverted back to 15 seconds. I'm not sure what's causing this... an app? An errant setting with the phone? Weird bug that has yet to be fixed? Rebooting the phone does not seem to solve the issue, nor has anything else I've tried to this point.
Any ideas?
Thanks!
I've had a look through the forums for a solution but not sure if any apply to s5. My phone experiences occasional lag on waking up when it rings. It seems to be random, I'm not sure if it's just a deep sleep issue. The amount of lag varies - sometimes the screen won't wake until after the phone stops ringing, other times it lags 2-3s and again other times there is no lag at all.
What could be causing this and how can I fix it?
Lately, I've noticed that my Note 3 won't wake up from a sleeping screen, but it doesn't happen all the time, and I cannot pinpoint what's causing it. If I remove the S-Pen, sometimes it will wake, but not always. I can tell the system is running, because the S-Pen audible notification sounds are working when I remove the pen, or put it back, etc.
If I long press the power, but not long enough to force shut down, sometimes it will wake, but not always. It's so random, that I cannot figure out the cause. It's fine for days, then it happens 5 times in a row, then it's fine again.
Anyone else seen this?
I'm thinking of a reset, but I'd like to ask for suggestions first, because it's a PITA to set up everything again, even with backups, and I might reintroduce the problem, if I restore the cause.
I've had this problem since since the beginning; both on OxygenOS 2.1.1, and 2.1.2 – sometimes, when I click the power button to turn the screen off, and put the phone on a desk, or into my pocket, after a few seconds the phone wakes up by itself suddenly, and most often shows the list of recent apps.
It's only a minor annoyance when it happens after putting the phone on a desk, but it can be a bit more serious when this happens in a pocket. For example, a couple of days ago, I was riding a bike, when suddenly, the phone started skipping through music, and doing who knows what else. (I know it tapped around a bunch in a number of different apps that one time.) Certainly a lot of potential for butt-dials.
At first I thought it was an issue with the DT2W implementation being overly sensitive, so I disabled it, but the problem persisted. Anyone else experiencing this, and perhaps any solutions?
I have a OnePlus 1 (rooted), Exodus ROM 6.0-20160730.
When my Bluetooth disconnects the display comes on but it does not respond to any touches, taps, swipes or anything - it's just on and it never times out. I have no idea what it's doing but sometimes this happens when I am not aware of it and I don't realize it until I feel this burning sensation in my pocket. If I press the power button as if the phone were asleep and I am waking it up THEN it will respond to touches normally.
I'm not sure if this is a BT issue or a ROM issue. Just thought I would throw it out here to see anyone has any ideas. Maybe it's something simple, but it sure isn't obvious (to me).