[Q] Can't Quite Pull Down to Mute/Unmute - Moto 360

This has been an ongoing issue for me since the previous update (not the most recent one from the past couple of days.)
Most of the time, when I go to swipe down to mute or unmute notifications, there is no response until I'm almost half way down the screen.
When I reach the bottom, it just isn't enough to trigger mute/unmute. I have to wildly swipe and after a minute or so I will finally get it to catch.
Normal touch inputs are fine, no matter where I touch the screen. Just this one action seems to be my issue.
Is anyone else having this problem? Any thoughts or ideas?
I've tried factory resetting a few times but that hasn't solved it.
Thank you.

Related

[Q] Notification Screen Flash & Missing Smiles

I have 2 very specific happenings with my Note 2.
1) At (seemingly) random intervals, my phone's screen will fade on and off displaying some sort of notification screen that I can't find anywhere. I must have hit this in some settings menu but don't know where. It has big white notifications for missed calls, emails, and texts, all of which are always 0 on the screen. Again, this screen fades in and out in under a second. I even tried a screenshot, but haven't been fast enough.
2) At one point I noticed the RETURN button from the keyboard was replaced with a smiley button. Now it's gone. How can I get it back or to stay?
Also... I love ellipses (three periods in a row). The stock keyboard auto punctuates after one period and puts a space in there which drives me crazy.
Any fixes or suggestions on any of the above things I've noticed?
Edit: Screen Just flashed at 9:30 - Maybe this happens on the half hour or quarter hours. I'll keep watch
Edit2: HAHAHAHAHA... It just did it one minute later. I've got no clue.
Ok, so I figured out how to activate it.
It's sensor related. I have my phone under a lamp. I move my hand over the sensors and I get this notification screen.
I don't mind it, just want to know where it is in the settings or if this is something you can/can't disable.
My guess is that its for when you take your phone out of a pocket the sensor can show you any missed notifications.
For the record, it's missed calls, missed texts, and battery level.
Found my answer in the General Section for the Note 2
The feature I'm describing is the "Quick Glance"
Now... onto figuring out how to get that smiley button back instead of the return! :laugh:
I know this is an old post but I am so glad I found this. It has been driving me nuts seeing that screen come on and go away. I tried everything to replicate it. It happened 5 times over the last 20 minutes while I was watching a movie so I googled it and found this. Anyways...thank you!

Incoming call screen unresponsive- Missed calls

So this has been happening sporadically over the last few weeks. I get a call, try to slide the answer button to the center to answer it, and other than feeling the haptic feedback, there is nothing responding. Turning off the screen did not help. Neither did trying to ignore button. When the screen comes up as a tap to answer, that works, but the slide one sometimes fails. Anyone else having this issue? Any ideas?
This is still happening on my device. As well as the pop-out, fly-out whatever you call them, menus that pop out from the side of an app with the 3 lines..those are becoming unresponsive and requiring a reboot. I can't seem to narrow down the cause. Still looking for any help on this.

Pull down menu is no longer working while in portrait

Hello has anyone experienced this?
Since last night (1/10/18) I have lost the ability to pull down the top menu using the screen.
I can still bring it up if I use the swiping function of the fingerprint reader though.
If i use the phone in landscape I am however able to pull down the top menu.
I tried rebooting several times, I also tried disabling/enabling the swipe gesture function, nothing helped so far.
Note: I do not use any launcher app.
Any idea as to what could cause that?
Just to update anyone stumbling on this post, the phone actually got worse...
The issue evolved into having the entire area of the touchscreen acting up.
Touch and swipes don't get recognized, and on the top of that the screen is tapping and swiping by itself.
Makes it really hard to use. I tried a factory reset but the issues remain.
The touchscreen digitizer probably failed...
Oh well I started an RMA with Google, should get a new phone with 5 days.
Cheers

Screen sensitivity since 8.1.0 update

My 32Gb N5X has really suffered a loss of screen sensitivity since the last update. Are there any adjustments I can make to fix that? An example is that I have a hard time answering calls with an upward swipe. It'll take two or three swipes before I can pick up a call. Also, on the lock screen, I cannot swipe away a notification on the first swipe, that also takes two or three to make it happen. Anyone else have this problem? Any solutions?
Thanks!
EDIT: looks like I'm not the only one. http://www.androidpolice.com/2018/0...id-8-1-lockscreen-swipe-issues-pixel-devices/

Navbar touch issue

Hello,
Sorry if this has been covered else where. I found stuff that was similar but not quite the same.
I am having an issue with Pixel 2 XL where the touches will not track over the navigation bar. If you tap on the navbar, the touch is forced to the top or bottom depending on if you tap is closer to the top or bottom respectively. If it's pushed to the bottom, it works OK, but taps forced to the top trigger the search bar.
When dragging down, the navbar essentially blocks the drag, then a second tap registers below the bar as you pass over it. Since you're at the end of your drag at this point, you lift your finger and the second tap registers as a button press. This results in accidentally tapping the nav bar buttons when you are just dragging down.
I played with it so much that I found if you get just the right spot you'll, end up with two active tap-spots. If I drag rapidly across the nav bar for like 10-30 seconds, it will return to normal, but the phone gets a bit freezy, and seizes up randomly for 3 to 10 seconds at time. After a while it seems to return to normal.
I have also experienced the "screen freezes for a bit, then suddenly registers 100 taps" issue. I'm not sure if they are related. If anyone has insight into this issue as well, i'd love to hear it.
Is anyone else having these issues? I have a video but I'm not allowed to post outside links.
Thanks very much
marshle said:
Hello,
Sorry if this has been covered else where. I found stuff that was similar but not quite the same.
I am having an issue with Pixel 2 XL where the touches will not track over the navigation bar. If you tap on the navbar, the touch is forced to the top or bottom depending on if you tap is closer to the top or bottom respectively. If it's pushed to the bottom, it works OK, but taps forced to the top trigger the search bar.
When dragging down, the navbar essentially blocks the drag, then a second tap registers below the bar as you pass over it. Since you're at the end of your drag at this point, you lift your finger and the second tap registers as a button press. This results in accidentally tapping the nav bar buttons when you are just dragging down.
I played with it so much that I found if you get just the right spot you'll, end up with two active tap-spots. If I drag rapidly across the nav bar for like 10-30 seconds, it will return to normal, but the phone gets a bit freezy, and seizes up randomly for 3 to 10 seconds at time. After a while it seems to return to normal.
I have also experienced the "screen freezes for a bit, then suddenly registers 100 taps" issue. I'm not sure if they are related. If anyone has insight into this issue as well, i'd love to hear it.
Is anyone else having these issues? I have a video but I'm not allowed to post outside links.
Thanks very much
Click to expand...
Click to collapse
I tried to replicate what your talking about. However, I couldn't do it. Maybe because I'm using Nova launcher, which may be a viable option for you. A factory reset might be helpful, however, we all know how much fun that ISN'T! Definitely an interesting issue your having. Then again, I think these devices have a mind of their own at times ?
Thanks for your reply. Forgot to mention, I have tried safe mode and done a factory reset and it did not remove the issue. It seems after a factory reset you are still on Oreo 8.1, so I'm not able to confirm it the issue exists in 8.0. I also have tried Nova Launcher.

Categories

Resources