Guys I initially tagged this as the problem was solved, because a Samsung developer replied and was made aware of the issue. I thought that's all that was required so I assumed a resolution would be pushed on the next update.
I don't think you need to apologize for what appears the Gold Standard of sub par support help. You wanted to believe and they failed you. They ask the stupidest questions IMHO at the start and prolong the inevitable with more stupid questions, the inevitable being no solution whatsoever. Heck they can't even come up with some possible trouble shooting suggestions. Thanks for at least trying to get a solution to a problem many of us have with multiple Samsung devices. Lmao they flagged an error on me for writing he dbl toothpicks instead of heck. Pretty much somes up their idiocy.
So I had no idea, but I am able to go into a post and edit whether a solution is accepted or I can choose "not a solution".
I marked it as "not a solution" and it should show up as unsolved with no solution.
Does it appear that way to you guys?
i have an S8+ but i had this issue on my Note 3 first. it also did after on this phone and then for the past couple months it had fixed itself.
it just started speeding up again today.
Hey Community, can anyone currently in the Oreo Beta check and see if this is still a problem? Thanks!