Hi,
I have observed in a few apps a certain problem: Some apps don't support the NST side buttons, so I scroll by swiping my finger over the screen. In most apps this works.
But there are a few where it does not work properly: Somehow these apps seem to have a problem interpreting my swipe correctly. Sometimes they correctly interpret it as attempt to scroll down, but very often they will also interpret it as an attempt to scroll up, even though I am making the same movement. This way reading a long article is really annoying because you always get sent back to the top of the article.
Apps in which I have observed this: Wapedia, International Herald Tribune, Read It Later (this last one does not exist anymore, as it has been replaced by "Pocket" which does not work on Android 2.1).
All of these apps seem to show exactly the same problem, so I suspect a common cause.
Did anyone make similar observations or maybe even has an idea for a fix?
Thanks!
I have the same problem for some apps. If I do long swipe up most of the screen there is no problem.
But it is annoying when I forget.
Related
whenever i press the lock button the screen takes like 20 seconds to unlock it really sucks when someone is calling u in uni so can anyone help plz...
You probably have AOU type panel and get the lag associated with that type of panel.
Search for AOU panel, I'm pretty sure there's a fix for the lag included in some if not all of the newer roms.
There's an app that will allow you to find out what type of lcd panel you have, I can't remember it for sure right now, but I think it's something like Android System Information. When you do your search, read up and you'll surely find the name of the app and possibly the lag fix.
If it's not lcd lag, the most likely other thing that could be causing it is a slow or faulty sd card.
I imagine that this, like my other problems with my n4, is likely to be the result of my tinkering more than the phone itself... But seeing as I'm not terribly skilled, and I don't as much time as I'd like to fiddle around with my phone... I'm reaching out to the hive mind.
One of the problems thats annoying me the most right now is the voice to text button on the google keyboard. Namely it isn't doing anything. No error message, no change to the helpful microphone shaped circular button waiting to convert my dulcet tones into words... nothing.
To be honest I'm not entirely sure when this began, because its not a feature that I used frequently, unless alone in my car at a stoplight or something and I want to slam out a quick text. The mic still works fine, and gNow has no problem triggering and responding to me - it just seems as though the action is never triggered by the button.
I'm currently running KK, bootloader unlocked, rooted, xposed framework, gravity box, and a few other smaller modules (dictionary blacklist for example). Minimal rooted applications such as titanium and tasker, but nothing fancy is being done with them (didn't deepfreeze any system apps or set up any related tasks). The keyboard app is the google one with only small tweaks that are built in like the blue trail and shorter longpress time. I have offline voice to text set up, and this issue is present on wifi or network regardless.
Any tips? has anyone had this problem before? can anyone point me to a potential culprit or a way of finding one?
To those who are having trouble with the action memo function of their Note 4, specifically writing a partial memo, then minimizing it to collect more info (or just keep it readily available until the task at hand was completed), and as soon as the note shrunk to that little yellow-ish square, it vanished? As if the system was treating it as a running process but forgot to actually display the minimized memo? This problem prevents you from just opening up another action memo because again, the system thinks "I'm sorry Dave. I know you want to use action memo, but it's already running." in order to get it to come back up again you have to either reboot, or you -might- be able to kill a few S Note-related processes and get it to come back up again.
This problem frustrated me quite a bit and I couldn't figure out what was causing the problem until recently during my toying with the developer settings, I decided it looked and felt much better when all three of the animations were turned down. The phone still showed a little eye candy, but got things done faster at the same time. All three of them set at .5 worked well for me. However, for some reason when those animation settings were set lower than 1, the action memo minimization animation would shrink (pleasantly) quickly into its little square, causing some kind of hiccup with the system and then it poofs. I fixed this problem by changing the animation settings to 1 for all three. Inconvenient, but I get my action memo back, which I use daily.
Just a tip I hadn't seen on the Note 4 forums that I wanted to add for any others experiencing the same issue and wondering how in the world to fix it.
Cheers!
Doesn't work for me on both 0.5/1x
It is an annoying issue.
If anyone else finds a solution to that, please post here.
So it still vanishes when you minimize action memo, even though your animation speeds are set to 1?
Hi anyone else experiencing a bug where it takes like 5/6 trys to slide the lockscreen up. Its like im not sliding up enough but im going off the top of the screen i have to flick like 20 times sometimes.
Indeed Nougat seems to require a slightly different swipe-up-to-unlock action than Marshmallow. If you're going off the top of your screen, though, you are doing it wrong. You're not catching Pokémon, just slowly swipe up about an inch, that should already trigger the unlock. Do a practice run, see how slow and short you can do it, you'll be surprised.
I also have this problem since the update to Nougat, sometimes the screen will unlock with a short swipe and others you have to go the full length of the screen!
I have taken the screen lock off for now as i am fed up with swiping 5+ times to unlock the phone
If you disable swipe to shrink screen in moto actions then it works fine.
Sent from my XT1039 using Tapatalk
Yeah it works fine with swipe to shrink disabled now thanks
Shame that the swipe to shrink is causing the problem.
I can confirm the issue, and for the moment, also the solution! Thanks guys
Enviado de meu Moto G (4) usando Tapatalk
Had same problem but this didn't fix it for me. Ended up disabling/enabling Moto app. Noticed System UI tuner had disappeared so re-enabled that also. So far so good...
This is an old thread, but my findings may be relevant. A short time ago, I also started to have problems with all sort of swiping, on the home screen, but also when swiping away notifications or within apps. (Ironic, since I initially discarded those problems in the first answer here. Mea culpa.)
Eventually, I found the reason for it. I used a small app, "Media Volume Only", which hooked into the special "read phone status" permissions (in this case to monitor and modify volume keys behaviour). I assume in the process of monitoring gestures/keys it interferes with swiping actions. After disallowing, disabling and deinstalling this app, my swiping actions are as responsive as they should be.
So if you still have problems with swiping, it may well worth looking into these apps that carry that special permission.
Disaable all smart lock option.
Mainly on body detection option.
Thanks....
Its working 100%
martinisok said:
If you disable swipe to shrink screen in moto actions then it works fine.
Sent from my XT1039 using Tapatalk
Click to expand...
Click to collapse
You nailed it! Not only does their "Swipe to shrink screen" feature work TERRIBLY, as if that wasn't poor enough execution, it works terribly at the expense of making the swipe to unlock so completely frustratingly UNRELIABLE.
These folks need to take a leaf out of Huawei's book and make the swipe to shrink, work by swiping horizontally across the navigation bar ... (Huawei, incidentally, are FAR from perfect and need to fix their TERRIBLY laggy, sluggish phones) - you can SEE why people side with iPhone, can't ya!
cs5210 said:
Disaable all smart lock option.
Mainly on body detection option.
Thanks....
Its working 100%
Click to expand...
Click to collapse
On body detection is the reason in my case.
Problem solved now
Hi Everyone,
Recently my phone was updated to Android v7 and since then I noticed that the icons for the cursor in text boxes and system dialog boxes have got messed up.
I read on Android central, one user posted that uninstalling Kaspersky fixed the issue, although in my case I don't have Kaspersky, so I can't go about uninstalling all apps, got a hell lot of them!
1drv.ms/i/s!AigR1NGUKZ2stFWGsf_bkkIg_WEa
1drv.ms/i/s!AigR1NGUKZ2stFa4-NP8jEiQCuMs
1drv.ms/i/s!AigR1NGUKZ2stFRZcp6bHn6VE_JE
It's frustrating everytime i see this... Please help me...
I think I'm having a similar issue... the cursor locator (below the cursor which points to it) is the wrong size. I tried changing resolutions, nothing fixed it. This also happens when text is selected by long pressing, the selector graphics are too large and it gets cut off. It was working fine when phone was new, I cannot remember at which point it started messing up. Possibly after Oculus VR first changed the screen resolution to WQHD? I set it back to FHD for normal use, but problem persists.
Pertinent Info:
G930f
G930FXXU1DQD7 BTU firmware
phone not rooted
jivenene said:
I think I'm having a similar issue... the cursor locator (below the cursor which points to it) is the wrong size. I tried changing resolutions, nothing fixed it. This also happens when text is selected by long pressing, the selector graphics are too large and it gets cut off. It was working fine when phone was new, I cannot remember at which point it started messing up. Possibly after Oculus VR first changed the screen resolution to WQHD? I set it back to FHD for normal use, but problem persists.
Pertinent Info:
G930f
G930FXXU1DQD7 BTU firmware
phone not rooted
Click to expand...
Click to collapse
Maybe found a clue.... this problem seems to occur everywhere, except in a few apps, namely Signal and FB Messenger and FB itself. I thought it might be only in Gapps, but it happens in a few apps that are not part of Gapps. I have seen other people had issues with the little on/off sliders for options in different menu screens under setting, but mine all look fine.
jivenene said:
Maybe found a clue.... this problem seems to occur everywhere, except in a few apps, namely Signal and FB Messenger and FB itself. I thought it might be only in Gapps, but it happens in a few apps that are not part of Gapps. I have seen other people had issues with the little on/off sliders for options in different menu screens under setting, but mine all look fine.
Click to expand...
Click to collapse
I have those glitches as well apart from what i posted.
I read online its because of some app messing things up. I seriously don't want to reset and start testing this out one app at a time. It will take at least a few days to get back up to speed.
Thanks :crying: