Hey guys,
On my OGP, I have noticed that once I press the side button to unlock the screen, the touch keys light up instantly but the actual screen takes 1-2 seconds to light up after the button press. It may have gotten worse over time, or that may just be me being paranoid. Also, in messaging settings I experimented with messaging skins, and those seemed to lag my messages a lot (like when I clicked on a conversation, it took 2-3 seconds for the conversation to load, whereas before it was instant). When I removed the skin and went back to the default one, the lag still persisted. If anyone knows how to fix these issues, I would be grateful! My device is stock unrooted with value pack update, US AT&T. Only settings I changed was turned on quad core optimization.
Thanks,
killer
Fixed the lock screen lag by removing my dewdrop screen animation. Leaving it at basic drastically increased speeds to easily under a second. Now for the messaging lag...
So I tried two different roms that had ChaOS' ActiveDisplay on them (Carbon and DirtyUnicorn). After enabling it on both of them, every time I get a notification, i get it on the ActiveDisplay perfectly fine, but first, when I go to open the notification, it just brings me to the slide lockscreen, and i have to go through that to actually have it work. Is there any way to keep that from happening? When using the app DynamicNotifications, I had needed to enable it as an admin so that that sort of thing wouldnt happen, but nothing related to ActiveDisplay shows up there.
Secondly, as soon as the screen turns off from the notification, the notification goes away. I don't know if that's just how this implementation works, but I was under the impression (again from DynamicNotifications) that it was supposed to essentially replace the lockscreen and whenever I turned on the screen, it should show me any notifications if there were any. So is this how its supposed to work? or am I expecting the wrong thing?
I moved away from DynamicNotifications because it started being very buggy and laggy recently and from looking at ChaOS' video of it, it looked like it was pretty much a better implementation.
My watch was working perfectly before the 5.1.1 update, but ever since the update, it is slow to wake, unable to swipe away cards from the watch face without opening them, the touch sensitivity is TERRIBLE....have to swipe over and over to get it to register, and for notifications I am unable to select "ALL"...can only select "priority" and "none".
Is anyone else having these problems?
5.1.1 problems are being discussed here if you're not aware:
http://forum.xda-developers.com/zenwatch/general/android-5-1-1-ota-files-online-t3109484
No problem in starting a new thread, though.
nhpilot43 said:
Is anyone else having these problems?
Click to expand...
Click to collapse
I noticed that the touch screen seems derpy to me too. Something is definitely weird with the toggle shade thingy. I'm having the same problem with selecting "all". You can get it, but you have to find the exact spot below and to the left and tap frantically like a dozen times. I reccomend using the test app in developer settings and open the touch test. It will display a small grid and it will trace all your touches. Don't worry if it says fail. Just notice whether or not its tracking your finger. To get it to pass you have to turn the lines green by swiping in a certain direction. Mine tracks perfectly so, for me at least, the hardware is fine. Definitely a software issue.
-Andy
Sent from my Apple Newton.
Yesterday I installed the Android M preview on my phone, and so I had to do a reset on my watch. Now all of the touchscreen wonkiness has gone away, and it's working fine!
Before I was unable to get the app list to appear by swiping from the right, but only by tapping once. Also, I couldn't swipe in the center of the screen in the mode selector shade, but only above or below the row of icons. Now that's all working as well.
HI everyone...
Got a bit of an odd one here, hoping someone can help.
For some reason, when the screen on my Sprint S6 is off, any SMS notifications get cut off (or I don't get them at all). I am expecting both an audio and/or vibration notification. If I turn my screen on, I will get the full notification as expected.
I thought maybe this was a problem with the DOZE settings, but I disabled YAATA from Battery Optimization, and it didn't fix anything.
Then I thought maybe it was a YAATA problem, so I went back to the standard built-in SMS app. Same results... either a cut-off, or no, notification when the screen is off, and a full notification when the screen is on.
Anyone have any suggestions on something else I could look at?
(For the record, I'm running stock, non-rooted Sprint S6...)
Much appreciated!
OK, after this has bothered me for MONTHS... I post here, and then figure it out.
I also have Glimpse Notifications installed on my phone. I just opened the app, and saw the following:
"Android Marshmallow sometimes cuts off notification sounds when the display turns on. In this case select Delay Screen On in the Extras menu."
... which, oddly enough fixed it.
I'll leave this here rather than delete it in case it helps others in the future.
I'm having problems with my Fold 4 not registering taps. I tap a space on the screen and nothing happens. I do it several more times, and finally it responds. I haven't seen a clear pattern yet, because it's somewhat intermittent. Has anyone else seen this problem?
I'm slightly suspicious of the Microsoft launcher here., but I suspect that's because it gets the majority of my taps, it being the launcher. I haven't had that problem in the past.
Just a minute ago I sat down to make a video of what I was seeing in case I thought an exchange might help. It happened on the first try, and I wound up having to press it five times with escalating pressure to finally get it to react. For the record, I have not seen a correspondence between pressure and the problem. I think I just naturally start pushing harder and when it works, it feels like it was more pressure. But when the problem isn't occurring, it takes very little pressure to register a tap.
Not using the Microsoft Launcher, but I am using SwiftKey, and I do have the same issue, especially with the space key. Mostly with the outside screen BTW.
Ah, I should have been more specific. Yes, I've only seen the problem on the outer screen so far. And I'm using gboard for my keyboard.
I've had a similar issue but it seems to have gotten better. Being intermittent makes it hard to pinpoint
I initially transferred apps and data from my Note 20 and was having issues on the outside and inside screen of taps not registering. Finally did a FDR and set up from scratch, haven't had the issue again. I always setup from scratch and took a shortcut this time, lesson learned!
ggrant3876 said:
I initially transferred apps and data from my Note 20 and was having issues on the outside and inside screen of taps not registering. Finally did a FDR and set up from scratch, haven't had the issue again. I always setup from scratch and took a shortcut this time, lesson learned!
Click to expand...
Click to collapse
I actually did an FDR last yesterday to try and solve the problem. Naada. It was still there for me.
I'm currently using Samsung's OneHome UI to see if it's something with the MS Launcher. Good god, I hate their launcher!
It feels like the sensitivity on the outer (cover) screen is too low, and combined with much smaller keys on keyboards (I use GBoard) there are plenty of missed hits and no response. Try turning on touch sensitivity and see if it improves ( Setting -> Display -> Touch Sensitivity. Mine went a tad better. I also changed the layout preferences to 'normal' keyboard height and most of my misses are now gone..
I'm having same issue but not with the keyboard but with tapping on apps on the home screen. I'm able to almost reproduce it every time in the middle of the screen. Is there any update on this issue?
I've got same issue that a tap on a app gets no action. Happens occasionally. Must be a bug.
After a factory reset mine has come back too. Hopefully we will get some bug fixes with the September security update.
imanony said:
I'm having same issue but not with the keyboard but with tapping on apps on the home screen. I'm able to almost reproduce it every time in the middle of the screen. Is there any update on this issue?
Click to expand...
Click to collapse
Same. I never have a problem in application, it's only when I'm interacting with the launcher.
I think the issue is with the refresh rate dropping. I used the galaxy max hz app and increased the base hz on the phone and I'm noticing response being much better now.
I also have this issue on my Fold 4's cover screen. I've always used the debug option to show where I touch, and when my touches don't register I still see the touch indicator, so I can only assume this is a software issue not deciding what to do with the touch. I think One UI might be overly sensitive for gestures, and detects taps as drags/swipes. A mini swipe on an app or folder on the home screen for instance won't do anything (which happens to me frequently).
I've had that problem quite a few times as well, not enough to drive me crazy but enough to be slightly annoying. It only happened when taping on the bottom of the screen. It often registered my taps as a swipe up. I saw the homescreen starting to go up slightly as if it was going to enter the drawer. Then one day I realized it was my way of tapping the screen that was the culprit. The way I hold my phone makes me ever so slightly swipe up as I tap the screen, but only when taping the bottom part, if I tap anywhere else, I don't tend to move my finger up as I tap. Of course, I'm talking minuscule amount of swiping here, probably less than a millimeter. It's just the way I hold the phone and move my thumb, it's personal, and I think everyone is going to have a different experience depending on how they hold their phone and tap the screen. Anyway, I'm not saying "you're using it wrong", because I think it's a problem samsung must fix, as I don't have that problem on any other phone. Probably too sensitive. I just tried to reproduce the problem as I write this message, and succeeded twice in less than 20 tries, so definitely the problem is still there. It's just that now I tap straight on instead of "sideways", and it works just fine. Just a workaround, I know...
Edit: on the cover screen, of course. Inside screen works fine with crooked taps.
Glad im not the only one. On the outer screen i have had times where I have to tap something 3 times for it to register... I never had this issue with my Z Fold 2