Database Develop

UI stuttering caused by accessibility permissions

The problem
Hi, I've been experiencing significant interface stuttering whenever an application has been granted accessibility permissions.
Video of the problem
Here is a video demonstrating the issue, read below for technical information: https://www.youtube.com/watch?v=wFVKCx5zVmQ
Facts about the problem
Ok so here's what I know so far:
It doesn't matter which service you grant access to, it will lag the same. I've tried LMT, Swipe Navigation, LastPass, TalkBack, and a few more I can't even remember at the moment.
It doesn't matter what ROM or Kernel you are on. I've tried Euphoria with LK and Hydra, rooted stock with stock kernel and LK, and Benzo with whatever the default Benzo kernel is. Doesn't make a single difference.
It does not only affect Relay for Reddit comment collapsing. It also affect Google Newsstand's mini/big card transition, news source transitions, Google Now transitions, basically anywhere there is an animation in the OS I can notice the stuttering.
Anyone else experience this? Any ideas? It is driving me crazy.

I'm not experiencing that
I've used custom roms/kernels almost all of them in the development forum lol
I wonder if maybe it's a particular accessibility itself? I feel like since its needing to be authorized in accessibility that it might be conflicting with something else, who knows?
People usually try booting the phone into safe mode and seeing if maybes its a third party app?
Thats my 2 cents! Hopefully it helps

It has nothing to do with a specific accesibility from what I can feel, stuttering occurs regardless of the app.
I have full wiped several times to test and can't find a solution.
Does anyone else experience this or have any ideas?

Can anybody duplicate this?
Should I RMA?

ggmask said:
Can anybody duplicate this?
Should I RMA?
Click to expand...
Click to collapse
adjust your governor/scheduler. me, i like using ondemand/deadline.

simms22 said:
adjust your governor/scheduler. me, i like using ondemand/deadline.
Click to expand...
Click to collapse
I've done this when using LK/Hydra, but I am not running stock kernel. None of the adjustments made any noticeable difference unfortunately

I really hate to bump this but the video only has 16 views and I'd love someone else to confirm or deny the same behavior when granting an app accessibility permissions.
If this is common behavior I won't RMA, but if no one else can recreate this I'm going to.
Oh, another thing I noticed: you don't have to test it in an app like Relay for Reddit, you can also do it in the Chrome browser on a site that has a lot of information. What I've noticed is that, when accessibility is granted to any app, visiting XDA forums becomes almost unusable. It takes FOREVER to scroll and when I can scroll it is extremely choppy. Disable the accessibility permission? Completely solves the problem.

You are NOT crazy. I have been searching, seeing if anyone else had this problem. I am using a completely stock Nexus 6 (not rooted), and because of the screen size I have been tinkering with apps to help with one handed use (like pie controls, handy soft keys, etc). They also require accessibility to be enabled. Whenever I install them, I notice (about once every 6-7 times) that when I open my app drawer on Nova launcher, it will half freeze, half stutter. Most of the time it's fine, but once every few times it happens. I haven't paid too much higher attention to whether jt causes stuttering in other apps, but it drives me nuts and so I uninstall the app and go back to stretching my thumb to use the stock nav keys. Wish this would get fixed. Kind of unacceptable for a Nexus - that kind of stuttering is why I don't like using Samsung devices.

Here is the Swipe Navigation developer saying it is definitely a thing in Lollipop with accessibility settings. (screenshot from Play Store comments on Swipe Navigation app). I wish someone could figure this out - I guess we have to wait for Google to do that?

I am using PieControl Pro and I do believe it makes the animations in the Play story stutter when I open a page and use the back button to go back to the app overview. The Play store was never completely smooth no matter what, but when I disable accessibility for PieControl Pro, it becomes a little better. So yeah, accessibility does seem to affect UI performance. I'm on stock Android 5.1 with Franco Kernel.

wbarnes4393 said:
You are NOT crazy. I have been searching, seeing if anyone else had this problem. I am using a completely stock Nexus 6 (not rooted), and because of the screen size I have been tinkering with apps to help with one handed use (like pie controls, handy soft keys, etc). They also require accessibility to be enabled. Whenever I install them, I notice (about once every 6-7 times) that when I open my app drawer on Nova launcher, it will half freeze, half stutter. Most of the time it's fine, but once every few times it happens. I haven't paid too much higher attention to whether jt causes stuttering in other apps, but it drives me nuts and so I uninstall the app and go back to stretching my thumb to use the stock nav keys. Wish this would get fixed. Kind of unacceptable for a Nexus - that kind of stuttering is why I don't like using Samsung devices.
Click to expand...
Click to collapse
Thank you! I was losing my mind tryingbto figure this out so I opened a support ticket with Google play store and the person who handled my case was able to reproduce it and has made a note of it (whether this means there's an official bug report or not I don't know). He also said this issue cannot be used to RMA, since it wouldn't do anything anyway.
Unless someone can confirm that they DO NOT have this issue.

Im using swipe navigation and I'm noticing stutter as well. Wonder why this happens. Took me a while to figure it out.

Would you mind pointing me to the Google page where you reported this? I would like to star it as well, and follow their updates.

As a follow up, today I decided to tinker around and install pie again. Since the Nova app drawer animation is what I always notice stuttering first, I decided to just turn Nova animations off. Then, I went into Android settings, developer options, and reduced the three animation settings to 0.5x. I may just be seeing what I want to see, but the UI hasn't seemed to stutter with Pie enabled in accessibility (yet). Going to try this for a day or two.

I've gotten the same issues with Lastpass.
Lastpass even states on their site that it's a lollipop issue.
https://lastpass.com/support.php?cmd=showfaq&id=8166

ggmask said:
Thank you! I was losing my mind tryingbto figure this out so I opened a support ticket with Google play store and the person who handled my case was able to reproduce it and has made a note of it (whether this means there's an official bug report or not I don't know). He also said this issue cannot be used to RMA, since it wouldn't do anything anyway.
Unless someone can confirm that they DO NOT have this issue.
Click to expand...
Click to collapse
Sorry if this counts as bringing up an old thread, although it's not THAT old
Anyway, I've come here just to corroborate all your findings and confirm that I am also experiencing this ugly bug. A few days ago I installed Greenify which, among other things, asked to enable Accessibility features for it. Thinking nothing of it I did as requested. Next day I start noticing some UI lagginess and choppiness, which was especially noticeable to me in Relay for Reddit since I use it a lot (too much for my own good in fact) and I distinctly remember it had very smooth scrolling between comments just a few days ago. In the mean time, I completely forget I've granted Greenify accessibility control so I went on a mission trying to fix this inexplainable, sudden UI choppiness, by trying to flash a different kernel, trying different governors, dirty flashing my ROM, trying all the other tweaks, and finally doing a factory reset and flashing the stock ROM all over again (luckly I did make a nandroid). Nothing helped. I was at my wits end when I tried searching the app's subreddit for anyone experiencing the same issue and found a comments saying accessibility features were to blame. I felt stupid for not researching it before. However, this bug is very insidious as it just creeps up on you, with no reason. I also don't know how can accessibility features affect UI smoothness this way.

Yes, hopefully will be fixed in M maybe? I haven't checked around to see if those who have installed M preview have checked to see if the bug has been fixed there. Fingers crossed.....

Not fixed in M. Everyone should go star the issue so it gets fixed!
https://code.google.com/p/android-developer-preview/issues/detail?id=2092

wbarnes4393 said:
Not fixed in M. Everyone should go star the issue so it gets fixed!
https://code.google.com/p/android-developer-preview/issues/detail?id=2092
Click to expand...
Click to collapse
Still isnt fixed ) But my lag rather appears when tapping on any app icon, then it highlights, then go lag, then opening animation starts.

Post this over on reddit and see if you can bring a bit more attention to the issue.

Android 6.0 Marshmallow Apps Blocking MMS

I should probably post this somewhere else because I know it's an issue for more than the Nexus 6, but ever since I updated to 6.0 a few weeks ago I keep having issues sending and receiving MMS. It probably took me a week or more to notice the first time, but after a lot of pulling my hair out for almost a week I figure out it was Ad Away. I uninstalled and all was well. I know I could have messed with the ports in the APN profiles but I didn't want to be bothered.
Last week ES File Explorer updated with their terrible update and aside from the annoying new features, once again MMS stopped working. This was a little easier to pinpoint and once I uninstalled my MMS started working again.
Today I'm having trouble with MMS again. I started searching on the topic again, this time focused on Marshmallow and found a lot of people pointing fingers at Pushbullet. Also found people saying that Chrome was not set as the default browser and that assigning it fixed the problem for them. Luckily that was the case for me and I still have pushbullet (phew).
However, I feel like I'm just scratching the surface on this issue. What's up with Marshmallow that apps keep breaking MMS so easily? Is the Chrome default setting the underlying culprit here? I didn't check it the first two times but I'm wondering if I can reinstall other apps now haha. Obviously it'll be the first thing I check the next time this happens -_- but I'd like to understand what's happening better.
So do any of you smarter-than-me people understand this?
Update: I wasn't imagining things haha.
http://www.androidpolice.com/2015/1...s-the-annoying-failed-mms-bug-in-marshmallow/

CLAWHAMM3R said:
I should probably post this somewhere else because I know it's an issue for more than the Nexus 6, but ever since I updated to 6.0 a few weeks ago I keep having issues sending and receiving MMS. It probably took me a week or more to notice the first time, but after a lot of pulling my hair out for almost a week I figure out it was Ad Away. I uninstalled and all was well. I know I could have messed with the ports in the APN profiles but I didn't want to be bothered.
Last week ES File Explorer updated with their terrible update and aside from the annoying new features, once again MMS stopped working. This was a little easier to pinpoint and once I uninstalled my MMS started working again.
Today I'm having trouble with MMS again. I started searching on the topic again, this time focused on Marshmallow and found a lot of people pointing fingers at Pushbullet. Also found people saying that Chrome was not set as the default browser and that assigning it fixed the problem for them. Luckily that was the case for me and I still have pushbullet (phew).
However, I feel like I'm just scratching the surface on this issue. What's up with Marshmallow that apps keep breaking MMS so easily? Is the Chrome default setting the underlying culprit here? I didn't check it the first two times but I'm wondering if I can reinstall other apps now haha. Obviously it'll be the first thing I check the next time this happens -_- but I'd like to understand what's happening better.
So do any of you smarter-than-me people understand this?
Click to expand...
Click to collapse
No0 the chrome issue is not really a big deal. I dont have it set as mine and mms works fine. The pushbullet thing is a known issue. Are you using a 3rd party sms app?

I was having the same issue, nothing exoctic installed, using stock messenger. I played with the apn settings to no avail. I ended up installing chomper and haven't had a problem since

none
[/COLOR]
CLAWHAMM3R said:
I should probably post this somewhere else because I know it's an issue for more than the Nexus 6, but ever since I updated to 6.0 a few weeks ago I keep having issues sending and receiving MMS. It probably took me a week or more to notice the first time, but after a lot of pulling my hair out for almost a week I figure out it was Ad Away. I uninstalled and all was well. I know I could have messed with the ports in the APN profiles but I didn't want to be bothered.
Last week ES File Explorer updated with their terrible update and aside from the annoying new features, once again MMS stopped working. This was a little easier to pinpoint and once I uninstalled my MMS started working again.
Today I'm having trouble with MMS again. I started searching on the topic again, this time focused on Marshmallow and found a lot of people pointing fingers at Pushbullet. Also found people saying that Chrome was not set as the default browser and that assigning it fixed the problem for them. Luckily that was the case for me and I still have pushbullet (phew).
However, I feel like I'm just scratching the surface on this issue. What's up with Marshmallow that apps keep breaking MMS so easily? Is the Chrome default setting the underlying culprit here? I didn't check it the first two times but I'm wondering if I can reinstall other apps now haha. Obviously it'll be the first thing I check the next time this happens -_- but I'd like to understand what's happening better.
So do any of you smarter-than-me people understand this?
Click to expand...
Click to collapse
Are you using the stock message app? not that you should have to put a different messaging app on your phone to fix the issue, but purely from a troubleshooting perspective have you tried that? Personally I didn't care for the stock app so when the Stagefright terror came about I switched to Textra and have been there ever since. It really is an awesome MMS app, maybe give that a go and see what happens, and once you use Textra, I doubt you will want the stock app.

zelendel said:
No0 the chrome issue is not really a big deal. I dont have it set as mine and mms works fine. The pushbullet thing is a known issue. Are you using a 3rd party sms app?
Click to expand...
Click to collapse
Was just curious if something was clearing Chrome and causing this to happen, and if maybe I had known about this and tried it the last two times I wouldn't have had to uninstall anything.
Gage_Hero said:
I was having the same issue, nothing exoctic installed, using stock messenger. I played with the apn settings to no avail. I ended up installing chomper and haven't had a problem since
Click to expand...
Click to collapse
USMC retired said:
[/COLOR]
Are you using the stock message app? not that you should have to put a different messaging app on your phone to fix the issue, but purely from a troubleshooting perspective have you tried that? Personally I didn't care for the stock app so when the Stagefright terror came about I switched to Textra and have been there ever since. It really is an awesome MMS app, maybe give that a go and see what happens, and once you use Textra, I doubt you will want the stock app.
Click to expand...
Click to collapse
Using the stock Google Messenger app. I tried using Hangouts as the default SMS app but it happened there too. I hate SMS/MMS so I really want to avoid downloading any additional apps haha. I usually try to force people into using an instant messenger but you know how people can be. It's just annoying because I usually don't even get a notification that I'm missing messages. I just open conversation and it says "tap to download" or "downloading..."
I'm working fine now so maybe the next time it breaks and Chrome as the default browser isn't the fix it I will explore some third party apps, it just seems like this is a "thing" with Marshmallow.

http://www.androidpolice.com/2015/1...s-the-annoying-failed-mms-bug-in-marshmallow/

I had the same issue. Got my nexus 6, before even setting it up, I rooted and installed marshmallow pure nexus. I'm on T-Mobile. I had 3 apn's under settings. The fast-tmobile had mmsc blank. The 3rd apn had T-Mobile mmsc filled. I copied that, pasted it into the fast-tmobile apn, clicked save, then deleted the other 2 apn's. I use hangouts, and since doing that, I've had zero issues at all. If I change roms, its the first thing I do. I'm more inclined to believe it's in your apn. Many people have had the same issue. I went back to 5.1.1 and took the ota. Mms was broken and I had to apply the same fix. Still on the stock ota, and all has been well. Good luck
Sent from my Nexus 6 using XDA Free mobile app

Google Photos Issue

Anyone else having this issue? I prefer to use Google Photos as my default but I keep getting this message when I do either of two things:
1. try to delete photos
2. try to set a wallpaper
I've already given all permissions to Google photos and have even set it as the default gallery app. is there something else I'm missing?

nop
mine works fine

Yeah that bugs me, can't delete any image in Google Pics. Have to open Gallery to perform the deletion .

retsilred said:
Yeah that bugs me, can't delete any image in Google Pics. Have to open Gallery to perform the deletion .
Click to expand...
Click to collapse
YES! I have to do the same thing. It's annoying. at least I'm not going crazy thinking I'm the only one having this issue.

I'm guessing there's an obvious setting some where that we've missed as no one else has replied!

no use of the camera by apps

Hi, got a strage problem with my Nexus 6, runnig with 7.1.1.
Altough the camera app itself works fine, any other app interupts with an error massage when the app tries to use the camera (eg WhatsApp or CamCard). Don´t know the message in english, translated form german, the message should be "can´t connect to the camera". Ok, I´ve done a factory reset, I booted into the recovery mode, wiped the cache and did a reset with no success. Trying to make a photo eg. with WhatsApp doesn´t work .
I´ve read, that should be a hardware problem. I can´t imagine that.... As I remeber, the first time I recognized the problem was after I installed an app for the vector smartwatch. This app sould be a remote to initiate a pictute shot from the vector watch (The app didn´t work, I deleted it). After that, I tried to make a picture with WhatsApp and the camera failed the first time. An accident? And the camera still works fine with the camera app.
However, I don´t know any further doing. Do you?
Thanks for any support .....

Back up your data and perform a factory reset. What happens?

Strephon Alkhalikoi said:
Back up your data and perform a factory reset. What happens?
Click to expand...
Click to collapse
I already did that. No effect, same problem ....

Sorry to ask the obvious question, but you did grant camera permissions to the other apps?

dahawthorne said:
Sorry to ask the obvious question, but you did grant camera permissions to the other apps?
Click to expand...
Click to collapse
I would say YES. After the factory reset, the only app I installed was CamCard with all permissions. Starting the camera out of this app causes the message "couldn´t start the camera".
But I think, you´re right, my fault must be something like "basic" or "fundamental". I´ll try a second time.....

Multifreak said:
I would say YES. After the factory reset, the only app I installed was CamCard with all permissions. Starting the camera out of this app causes the message "couldn´t start the camera".
But I think, you´re right, my fault must be something like "basic" or "fundamental". I´ll try a second time.....
Click to expand...
Click to collapse
Instead of playing the guessing game why not pull a logcat and know for sure what is causing it. If you tried on a completely new setup then I would say the issue is with the app.

zelendel said:
Instead of playing the guessing game why not pull a logcat and know for sure what is causing it. If you tried on a completely new setup then I would say the issue is with the app.
Click to expand...
Click to collapse
The issue is with all apps using the camera (eg. WhatsApp, CamCard and so on..)! But thank you, I will try to pull a logcat (after figering out, what that is... )

Multifreak said:
The issue is with all apps using the camera (eg. WhatsApp, CamCard and so on..)! But thank you, I will try to pull a logcat (after figering out, what that is... )
Click to expand...
Click to collapse
If you are messing with your device and dont know what a logcat is then STOP. This is basic troubleshooting 101 and many want even look twice or offer any help without one.
Also with the recent update it could be that google changed something with the camera and the apps need to update it. I cant really test either of those as I have no use for camcard and I wouldnt be caught dead with wahtsapp installed on my device.

"logcat ... This is basic troubleshooting 101"
I have to disagree. I've been playing with Android for several years and I have little idea (not "no idea", since I read a description recently) what a logcat is or how to get one, but most people's queries here are answered without logcats. To tell someone to STOP (unnecessary caps) is unhelpful, and I say that with respect, given your very large (and very impressive) number of thanks votes.

dahawthorne said:
"logcat ... This is basic troubleshooting 101"
I have to disagree. I've been playing with Android for several years and I have little idea (not "no idea", since I read a description recently) what a logcat is or how to get one, but most people's queries here are answered without logcats. To tell someone to STOP (unnecessary caps) is unhelpful, and I say that with respect, given your very large (and very impressive) number of thanks votes.
Click to expand...
Click to collapse
Trust me man. It really is. They are so important that many devs refuse to even look at a question without it. The questions that popup normally go through about 6 pages of try this or try that when a logcat will tell you exactly what is wrong.
I only say stop like that because things like this carry very real risks. You could easily brick your device and if you dont know how to do the basics then there is nothing anyone can or will do to help. It is also the main reason devs hate toolkits that do nothing but make matters worse.

zelendel said:
Trust me man. It really is. They are so important that many devs refuse to even look at a question without it. The questions that popup normally go through about 6 pages of try this or try that when a logcat will tell you exactly what is wrong.
I only say stop like that because things like this carry very real risks. You could easily brick your device and if you dont know how to do the basics then there is nothing anyone can or will do to help. It is also the main reason devs hate toolkits that do nothing but make matters worse.
Click to expand...
Click to collapse
Sorry, in my perception, the "sound of your speech" is unreasonable too... Sure, I don´t know every detail, but I´m profesionally about IT for 25 years... and this with a impressive success. So if you advise me to stop, it feels a little disrespectful. But, let´s stop... as soon as possible I will pull a catlog and I´m grateful for this attempt.

Gallery Scrolling Bug [SOLVED]

Well Read the orig. Post for the back store and at bottom ive included the user who supplied the right awnser and resolved the issue;
Im kinda disappointed in the note 8's stock gallery and really just fed up with the lack of options here to get it working correctly.'
I was just going to keep my issue to myself until i check reviews under the Gallery app via Samsung and seen that its not just me effected by this annoying as H3LL scrolling bug.
Anyone who has a good amount of pictures should be able to re-create the bug themselves.
Pretty much in a nut shell if you open a ALBUM and slowly scroll down the entire screen shakes violently like its having a seizure.
I contacted the other Dev i work with and he wasn't able to duplicate but also doesn't have nearly as many photos on his device as I do.
This really just ruins the gallery for me personally whenever I try to show someone a beautiful photo this device takes and it just represents the entire phone like crap IMO. Let me know if you guys have the same issue and your thoughts behind this one,
and i'm sorry to anyone who finds the bug and annoys the h3ll out of them as well. I guess sometimes ignorance is bliss.
***************Solution*******************
Awnser: Provided by
Originally Posted by*@djlee0314*
Do you have Bixby Button Remapper installed (or similar app)? I saw in another forum a user had this same issue and turned out that app was the culprit.
**
As well as another source I don't have from another forum/post
**
The remapping apps like Bixby remapper are causing the overlay issue with gallery for whatever reason. I feel a little bit silly now but atleast there is a response. Thank you everyone this made my day a ton better not having to deal with the darn shuttering gallery!

To point out you ususally have to be scrolling near the top half of the screen to cause it but it's done it to me at all locations on the screen randomly. Just slowly drag up (to scroll down through your photos inside a album) and near the top it will start to shutter heavily and if you stop scrolling and just leave finger on screen it just shakes like a earthquake.. ughh.. contacting Samsung today for a resolution time frame here. Just super annoyed at this point.
And yes I fully wiped my device and restored with the stock Odin img as well to fully verify it wasn't a app or defect in the Initial install.

I have seen it on youtube, I have more than 30 albums with up to 900 pictures each on SD card and so far I have not been able to reproduce it and I tried for good few min. Actually it is surprisingly smooth and extremely fast considering it is reading from 256 GB Samsung Evo SD card.

I cannot reproduce this bug. Glad I don't have it.
Sent from my SM-N950U using Tapatalk

Team DevDigitel said:
Well,
Im kinda disappointed in the note 8's stock gallery and really just fed up with the lack of options here to get it working correctly.'
I was just going to keep my issue to myself until i check reviews under the Gallery app via Samsung and seen that its not just me effected by this annoying as H3LL scrolling bug.
Anyone who has a good amount of pictures should be able to re-create the bug themselves.
Pretty much in a nut shell if you open a ALBUM and slowly scroll down the entire screen shakes violently like its having a seizure.
I contacted the other Dev i work with and he wasn't able to duplicate but also doesn't have nearly as many photos on his device as I do.
This really just ruins the gallery for me personally whenever I try to show someone a beautiful photo this device takes and it just represents the entire phone like crap IMO. Let me know if you guys have the same issue and your thoughts behind this one,
and i'm sorry to anyone who finds the bug and annoys the h3ll out of them as well. I guess sometimes ignorance is bliss.
Click to expand...
Click to collapse
Are your pics on internal memory or an sd card?

And videos? 8 can scroll throught over 1000 photo without seeing anything but pop in loads

xxx42069 said:
Are your pics on internal memory or an sd card?
Click to expand...
Click to collapse
On a class 10 64gb Samsung sd card
Both photos and videos. About 2500 files in my camera album.
Zooming in or out the gallery view makes no change

Team DevDigitel said:
On a class 10 64gb Samsung sd card
Both photos and videos. About 2500 files in my camera album.
Zooming in or out the gallery view makes no change
Click to expand...
Click to collapse
Interesting. I would try moving them to internal memory and see if the problem persists. That might narrow it down a bit as to whether it's a problem with your device or the sd card.

Do you have Bixby Button Remapper installed (or similar app)? I saw in another forum a user had this same issue and turned out that app was the culprit.

djlee0314 said:
Do you have Bixby Button Remapper installed (or similar app)? I saw in another forum a user had this same issue and turned out that app was the culprit.
Click to expand...
Click to collapse
You sir.. I love you haha
Little shhhh.. it seems like that has done the trick.. darn it.
I'm gonna test some more.. looks like bbr is gonna have to stay gone. Great catch man. I will move your awnser to the op and change the info to direct towards this as well to help others!
So glad its simple as this... I tested without apps and it worked fine but once I let smart switch restore and my gallery app updated it came back. I guess I should have done more testing!

Team DevDigitel said:
You sir.. I love you haha
Little shhhh.. it seems like that has done the trick.. darn it.
I'm gonna test some more.. looks like bbr is gonna have to stay gone. Great catch man. I will move your awnser to the op and change the info to direct towards this as well to help others!
So glad its simple as this... I tested without apps and it worked fine but once I let smart switch restore and my gallery app updated it came back. I guess I should have done more testing!
Click to expand...
Click to collapse
Haha! Glad I could help and that was the simple fix. As you can tell I'm more of a lurker here in the forums but glad my first post actually helped!

djlee0314 said:
Haha! Glad I could help and that was the simple fix. As you can tell I'm more of a lurker here in the forums but glad my first post actually helped!
Click to expand...
Click to collapse
i would def agree. Glad you took the time to supply the much appreciated answer. I've also added this info to Samsung site to help other users.
sadly Samsung probably knows its there and intended it to be there to make you not re-map the button. Grr.. they should allow remapping to whatever app you wish!

Weird. I don't have this issue, have bxactions installed, have >26xx images on my SD card.

I had the bug, Samsung 256 GB sdcard and over 5,000 pics and videos. I did have a Bixby remap installed...uninstalled the app, reset cache on the gallery, no issues so far. the stutter would accur no matter my scrolling location. I will further test to see if the stutter comes back

Interesting. There was another thread unrelated to this but was causing lag and stutter issues. The culprit: a bixby remapper app.
Perhaps once Sammy releases an OTA (since the official device release date is near) this may fine a lot of little bugs (for example, some are having issues posting videos to instagram)...

djlee0314 said:
Do you have Bixby Button Remapper installed (or similar app)? I saw in another forum a user had this same issue and turned out that app was the culprit.
Click to expand...
Click to collapse
omfg THANK you. I thought I was the only one going through this as I haven't been able to find anyone else experiencing this until today. And then I nearly ordered a warranty replacement when I read the top post and saw that no one else was able to recreate the bug. It's a good thing I kept scrolling through and reading more comments. If I had done a warranty exchange, I would have just kept experiencing the same issue, never knowing that it was the Bixby Remapper causing the issue

My sd card will arrive in a few days, so all internal. I didn't have a lot of pictures (below 500). One of the first things I did was to install Bixby Remapper, so from my point of few, the bug there from the beginning. Removed it, seems to be working normally. Bought my Note8 from T-Mobile Austria.
Thank you for the solution.

Whew i was wondering what was up & was waiting to the next update in hope that it would be fixed. I never knew until i read hear that it was down to Button remapping.....:good: thanks for making this post (Very annoying issue resolved) helpful indeed....:good: