I can't work out if this is a hardware thing or not, it seems to be mainly noticeable in the Twitter app (but can't remember right now if I have seen it in other apps or around the system) so it might be that to blame but I wondered if anyone else had noticed anything similar either in Twitter or other apps.
When swiping through my timeline it sometimes interprets swipes (such as scrolling up through the timeline) as a tap instead which causes the app to either click into a tweet, or retweet/like etc, whatever the beginning of the swipe was over the top of. It is not consistent and I can't force it to do it, it seems very random but when it does it, as you can imagine, its very annoying as I'll either have to press back to go back out the tweet, un-retweet or un-like the tweet. Once it starts doing it, it seems to do it for a while then after the screen has gone off return to normal.
I've turned on the option in developer tools to see touch data, the data shows a swipe when it does this so as far as I can tell, hardware wise, the screen is reporting the correct information on what has happened. So unless I'm understanding that data wrong I don't think the phone is to blame.
Related
Update: Wow I'm an idiot. There's an icon right on the address bar that opens the exact window I'm thinking of. In my defense, I don't think I used to have to access it this way. I seem to recall there being a menu option. Who knows. I bricked my G1 so I can't go look.
On my G1 I could long-press on the Back button and get my browser history. I've read elsewhere that this is the case on other phones. This is mysteriously missing from the Vibrant. Plus there used to be a menu option to see it. I can find no way to access the history using the "Web" app. There is a button in settings to clear the History, but what's the point if no one can ever see it?
Same with Bookmarks. I can create bookmarks, but there don't appear anywhere! The button that normally shows bookmarks (if I recall correctly) is now an "Add RSS Feeds" button. The only way I've been able to access bookmarks is by creating a shortcut on my home screen. That's pretty ridiculous.
I seem to remember bookmarks, history, and possibly the open window list all being in one spot with a tabbed interface. All I can get to now is the open window list. EDIT: No, wait, I think it was bookmarks, history, and downloads all in one place. I was using CM5 at the time if that matters.
Am I missing something obvious here?
Also, does anyone else think it's annoying that the browser has it's own brightness setting and you can't just tell it to use the normal brightness setting? I understand the idea behind the future. You spend a lot of time staring at the screen when using the browser, so it's nice to be able to dim it to save battery power, but I sure wish there were an option to just make it use the normal brightness, because I really don't care. This is especially annoying when I have the brightness in the browser all the way up, and I'm using the reddit app at night in my bed, and I click a link. BAM! I'm blinded by the bright screen and have to keep staring at it to go find the setting to lower it.
I think Samsung made some really dumb mistakes with their version of Android. I know that custom roms solve these problems, but users shouldn't have to hack their phone to get basic features like access to browser history and bookmarks.
This is by far THE most annoying thing I have ever seen forced upon smartphone users, and is actually about to result in me returning an otherwise great phone. Judging from other comments, I am obviously not the only one having this issue, but I have yet to find any good resolution, aside from taking hostages at Google.....
Without fail, when I am scrolling through webpages, e-mails, within apps, whatever, that damned Google half-circle pops up when I stupidly scroll from the bottom of my screen. What an idiot I am. The LG "quickmemo" icon is on the right side of the half-circle, Google search on the left. Being right handed, I am continuously scrolling across the quickmemo icon, which results in me having to hit the back button twice, once to get rid of the red line it drew across my screen, then again to get out of the quickmemo app. I have disabled Google Now in "Settings" to no avail.
I have tried 2 apps from Google Play, "Swipe Launch Disabler" which will not work evidently because my phone has a physical HOME button (no idea why this is the case other than the developer telling me so), and "SwipeUp Utility" which so far will not work either to "do nothing" as the options offer.
My LG L39C did not have this God-awful POS feature and is likely going back into service. Google of course could not care less about what users want or their ability to determine for themselves what to disable or not. I have never even considered switching to iPhones until now, but if this is going to be forced upon Android users from here forward it's a no-brainer for me.
Can anyone tell me how to AT LEAST DISABLE QUICKMEMO COMPLETELY? I shouldn't have to root this [email protected] thing to make it usable and have no intention of doing so.
Any help will get you included in my will.......
Since installing Lollipop 5.02 I notice that when there now appears to be a "feature" that calls in google search when a swiping up from the bottom of the screen in the region of the home button.
I find this to be a flipping nuisance when scrolling through pages of info - I seem to have a tendency to place my swiping finger near the middle of the screen and keep getting google starting up all the time.
I don't recall seeing this in KitKat so I assume it came with Lollipop.
Does anyone know where to disable this "feature", it's driving me up the wall.
wooly1 said:
Since installing Lollipop 5.02 I notice that when there now appears to be a "feature" that calls in google search when a swiping up from the bottom of the screen in the region of the home button.
I find this to be a flipping nuisance when scrolling through pages of info - I seem to have a tendency to place my swiping finger near the middle of the screen and keep getting google starting up all the time.
I don't recall seeing this in KitKat so I assume it came with Lollipop.
Does anyone know where to disable this "feature", it's driving me up the wall.
Click to expand...
Click to collapse
It is extremely annoying. I know some Xposed modules for HTC phones have an option to disable it all together, but so far I haven't seen anything similar for Sony's UI.
I use this app to make it less annoying..it just reassigns the Google shortcut to the app itself, which then makes the swipe up do nothing (except for the brief animation): https://play.google.com/store/apps/details?id=com.AdrianCampos.swipeuputility
Thank you, thank you, thank you for that link.
There has to be an app for everything nowadays!
So it appears the function is baked into the firmware, that explains why I could not find a way of disabling it.
At least this app minimises the disruption to workflow and restores a little bit of sanity.
Anyone being bugged by the swipe up feature - install this app and be happy
Hey Friends,
i noticed, that unlike other phones, I am having the issue of having to tap twice on the screen to get the phone to react.
More specifically, when I am scrolling up (for example the whatsapp contact list) and I tap on a contact shortly after the scrolling has hit the top the app will not go into the contact despite the tap.
I have to wait 1-2 seconds and then tap for it to actually register the tap itself.
I am having a similar tap issue with the nav bar below. I find myself often tapping twice on the circle to get to home. Somehow the hits are not registering in time/correctly.
To my surprise, there are apps (e.g. the home drawer) that react on the first tap.
Anyone with similar issues?
anyone?
exxi said:
Hey Friends,
i noticed, that unlike other phones, I am having the issue of having to tap twice on the screen to get the phone to react.
More specifically, when I am scrolling up (for example the whatsapp contact list) and I tap on a contact shortly after the scrolling has hit the top the app will not go into the contact despite the tap.
I have to wait 1-2 seconds and then tap for it to actually register the tap itself.
I am having a similar tap issue with the nav bar below. I find myself often tapping twice on the circle to get to home. Somehow the hits are not registering in time/correctly.
To my surprise, there are apps (e.g. the home drawer) that react on the first tap.
Anyone with similar issues?
Click to expand...
Click to collapse
Hi I've been have very similar issues with my mate 10 pro may I ask if resolved it,it's very annoying
Luap16 said:
Hi I've been have very similar issues with my mate 10 pro may I ask if resolved it,it's very annoying
Click to expand...
Click to collapse
No problem for me.
Did you do a factory reset ?
No problem for me also
Mate 10 pro and note that am activating gloves mode
No problem on my Pro either!
No issue here,but I'm running newer firmware.
I'm giving this a try.
exxi said:
Hey Friends,
i noticed, that unlike other phones, I am having the issue of having to tap twice on the screen to get the phone to react.
More specifically, when I am scrolling up (for example the whatsapp contact list) and I tap on a contact shortly after the scrolling has hit the top the app will not go into the contact despite the tap.
I have to wait 1-2 seconds and then tap for it to actually register the tap itself.
I am having a similar tap issue with the nav bar below. I find myself often tapping twice on the circle to get to home. Somehow the hits are not registering in time/correctly.
To my surprise, there are apps (e.g. the home drawer) that react on the first tap.
Anyone with similar issues?
Click to expand...
Click to collapse
I'm having similar issues but went to settings/ smart assistance and messed with "touch disable mode and glow mode"
Also try settings/ language and imput/ pointer speed.
I'm giving this a try for a couple of days before my return period expires good luck!
Case closed?
I thought i was the only one since i hadn't seen anybody post about it
I finally decided to remove the "tempered glass" which after removal I realized its not tempered glass, but a very thick screen protector (don't know what brand, I got this phone from a friend). So I was hoping that the screen protector is the culprit and YES, after removal my touchscreen sensitivity is better now. I wouldn't say it's performing perfectly, but it's much better than before. No more typo every now and then lol.
Edit:
Still getting trouble (just less frequent than before) especially when im typing fast, the letter S and A usually missed out. For example, i typed "missed" but result is "mised". And spacebar too! So annoying
Also like OP, nav bar sometimes i hv to tap twice.
i have problem with navbar not responding for about 1.5 sec after doing some stuff on homescreen. workaround for me was to switch to different navbar style after phone reboot. after next one delay returns. reported it to huawei and we'll see what happens. im on 8.0.0.129. to reproduce just tap anywhere on screen and then rigt after try to press any button on the navbar.
Same here, had touch issue since day 1. Sometimes it ignores space, sometimes I have a hard time using gesture with OnePlus gestures and so on. Gloves mode help a bit. Probably some digitiser are worse and the software can compensate only so much. I mean you can always use the warranty...
So, a week or so ago I've been forced to install an OTA update (despite disabling these in settings, because see this thread), and now my navigation is screwed up.
Swiping right on the pill from any regular app correctly switches to the previous one. Doing the same on a home screen (tested with Nova 6 and Total launcher) *seems* to be doing the same, but in reality it enters a fullscreen version of "app carousel" that you normally enter swiping up on the pill.
The easiest way to spot it (and mostly how it screws me up) is that the next pill swipe right won't switch to the next app, but instead smoothly scroll over multiple of them. Another thing is that because it's the carousel and not actual app (despite being properly fullscreen), any iteraction enters the app, showing the fade-in animation. And only then you can normally use it, so it basically eats the first input you do. Except swipe up, which, like on the proper carousel, kills the app.
This DOES NOT happen with the stock Asus launcher, but I don't want to use it. It also was working well before the update, I swipe to get to the last back from home constantly.
In the attached video, you can see me demonstrating the problem:
- [00:01] First there's a regular "swipe pill up" to open the recents carousel, scrol it back and forth, start swiping up some app, this works as expected
- [00:06] Then, back on home screen, I swipe right on the pill directly, entering the bugged state despite it looking like if it just entered the Reddit app
- [00:08] But another swipe right, instead of swapping to the SCP Reader app, just scrolls thorugh a bunch of them
- [00:13] After swiping back to the first on the list, clicking a post makes a weird "pop-in" animation
- [00:15] Because now we're out of the bugged state and entered the app properly, only the next click selects a post like it should
- [00:17] Back home again, swipe right to enter bugged state like I usually get back to an app after unlocking the phone
- [00:19] Click to exit bugged state again
- [00:21] Swiping right on the pill *from an app*, which works as expected
- [00:22+] Swiping sideways on pill a few more times to show that it's *not* in the bugged state and changes one app at a time, also entering these properly right away
Does anyone also experience this? Obv I tried restarting the phone, disabling/enabling the pill and in general messing with as many settings as I could to try and poke it, but nothing still. It's SUPER disruptive in everyday use, I'd be very glad to try any suggestions/fixes.
This has been happening for last 3 updates if I recall correctly. I have switched to stock launcher until it's fixed.
Really sucks, A13 finally fixed issues with 3rd party launchers but after an update this issue appeared.