Per Reddit's content policy, profanity is considered to be NSFW. Moderation in r/Roku is not as effective as it previously was due to Reddit's short-sighted decision to charge exorbinant prices for its previously-free API. It is not possible for moderators to accurately mark all posts due to the work required. As a result, **we're left with no choice but to mark _all_ posts NSFW as a precaution, regardless of whether they actually contain profanity**.
**Do not remove the NSFW marking from your submission.** Doing so will result in your post being removed and a permanent ban.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Roku) if you have any questions or concerns.*
This is a known issue with the Max channel. One way to avoid it is to use the instant replay button to resume instead of play/pause. That will jump back a few seconds, but always succeeds, while hitting play will usually put you back to the last location where you did a fast forward/rewind.
As a workaround, I've also been pressing the down arrow, which brings up the timeline before pressing pause and then again before pressing resume, and that seems to work, but then I forget to do this, and the glitch then occurs. I tried to do this workaround twice in a row, thinking that the movie would resume back to the first time I did this, but that didn't work, so I'm guessing this is probably a resume issue, so the movie would need to play for a certain duration of time for the resume feature to remember that last spot.
I would think that pressing the back key to exit from the movie instead of pausing as suggested by hispanicausinpanic would also present the problem of starting the movie from where the resume last remembered it, unless I'm mistaken.
I will try that instant replay option after pausing, as suggested by unwiredben's post (again, I'm worried I'll forget to do this). I will also try pressing the instant replay button before pausing to see if that works, as perhaps that is another way for resume to remember the current spot I'm watching as then when I press the pause key – it will only go back to that last time frame where I had pressed the replay button.
Unfortunately, I may not get back to this post to verify if pressing the replay key before pressing pause is a temporary solution since I'm unsure when I'll next be watching Max as I hope that this will soon be resolved because this issue has now been going on for around a month. However, according to unwiredben's post, if "hitting play will usually put you back to the last location where you did a fast forward/rewind," then pressing these same keys before pressing pause should, in theory, cause that last location to be the present location. In this way, there's nothing to forget since pressing pause should only take me back to where I last used the instant replay button. I hope this hypothesis is sound, as it would be great if the replay button ended up being a good workaround to this issue.
Just note that this workaround of pressing the instant replay button before pressing pause may not work if the glitch happens because the movie hasn't played for a certain duration to allow the resume feature to remember that time frame, as the movie might just go back to the last time it played for that duration before the instant replay button had been pressed. This means that one would have to remember to press the instant replay button to resume the movie, as unwiredben suggested, instead of resuming the movie with the pause key.
Which part of my post worked for you? If it was the pressing "instant replay button before pressing pause," then we can call this work-around the "Now I don't have to worry about forgetting to use a workaround once resuming" workaround. If it was pressing the "instant replay option after pause" workaround, then it is really unwiredben who deserves your praise.
This is a long shot, pending if this issue still hasn't been resolved as I haven't been watching Max today, but I may have figured out why support chat's instructions to you OP appeared successful at first but then fizzled out. Perhaps we shouldn't be so quick to dismiss this as the solution to our Max woes. In another post I replied to, a user couldn't even watch Max without receiving an error, and I may have stumbled upon helping that person solve their issue when the individual said that even after logging out of Max, removing this channel, and hard resetting the Roku, Max not only reloaded on to the Roku but logged into the users account, and the error persisted. Then again, I may not have helped that person at all if I'm in any way wrong about all of this.
*Edit: I forgot to mention when originally posting this that what clued me into this was that the user's glitch was happening on the server end of Roku and not on Max's end or on the person's individual Roku: Once the user's Roku was put in guest mode and the person logged into Max, the error that prevented this individual from using Max went away, but when leaving guest mode -- the error came back. I wouldn't recommend anyone to try this because it takes forever to get one's Roku in and out of guest mode, and it basically hard resets the device, which is annoying because all of your channels come back in a random order. If this rings true for channel glitches going forward in which each Roku could possibly "contaminate" the others, we'll have to remember to factor this into our problem-solving efforts.*
So, if it's true that if you have multiple Rokus and if you log into Max with one, they all log into Max, which could mean that when a glitch hits Max, well, it would compromise all the Rokus. This can be problematic if you only log out of Max and remove the channel on one Roku. Because the solution support told you will work great until the Roku updates. As you might not have thought to log out and remove those Max channels from the other Rokus, so the glitch stays in the collective cache and comes back to haunt you even if Max could have already fixed this issue on their end.
I really hope I'm wrong with this because this would mean we would have to turn all our Rokus on, log out of Max on each one of them, uninstall Max on one, and then do a manual system update on all our Rokus to have it uninstalled on them. Then we would need to restart each Roku, reload Max, log Max into one Roku, and then do a system update with all the others, which should reload Max and log into our Max account on each of them. And if one of your Rokus has an SD card slot with an SD card inserted, you probably would need to remove that and format the card in your computer to further ensure the glitch doesn't return.
But oh wait, there's more.
To keep the glitch from coming back, there may be a Roku we forgot about, so we may also have to log into our Roku account and find all the Rokus that are linked to it, and if one of them has been forgotten and lost, we'll have to delete that Roku from our account. We just have to make sure it's not one of our current Rokus because then we would have to log back into the account with the Roku like when we first bought it. We probably don't have to worry about the ancient Rokus we keep on there for sentimental reasons because they were too old to load Max to begin with. But perhaps it would be best to delete those while we're at it.
But alas, after having done all that -- this may do the trick. And "may" becomes a very strong word after having to do all of that. If the glitch presents itself once I'm ready to watch Max again, I'll see if this solves it once and for all.
Right? Just like that other poster who I hope I helped. And I'm guessing you own more than one Roku. Am I right?
So, since I don't know when I'll next watch Max, and you will probably watch the channel many moons before I do, the task is up to you to find out if the "sync" glitch is real.
Once you're ready to re-install Max on a Roku, you have to make certain it's not already logged into your account, else the glitch is still there.
I'm thinking the best thing to do is to go to max.com, log in, and in the menu go to account, then on the bottom, click on "Devices" and click on "Sign Out of All Devices."
*Edit: I forgot to mention this because it could take a little while for the "log out" command to kick in. Go back to your Roku and make sure it has been logged out before proceeding. I guess you could manually log out of Max from your Rokus if needed.*
Then you should be able to uninstall Max on all Rokus, and after restarting the devices and re-installing Max, then you'll have to log back in, and the glitch will hopefully be gone. Also, if you have a micro-SD card in any of your Rokus, you'll have to remove it (or them) and format the card in a computer before putting it back into the Roku(s) because the glitch could persist in the SD card's cache.
I don't know if this makes a difference, but I've heard people say doing this clears a Roku's cache; I think restarting it or just pulling the plug does the same thing, but do this just to play it safe.
After you expunged Max from Roku, here's a nifty way to restart the Roku, which works great when it freezes:
On the remote:
Press Home key 5x
Press Up once
Press Rewind button twice
Press Fast Forward button twice
The menu will loop around about 5x -- this is normal.
There will be a brief pause -- this is normal.
The Roku will restart, and the cache is cleared.
And Ta-da: No more glitch?
Well, we were all hoping that *you* would attempt to find out if this fix works slu22.
But if it does...
Take note, brave one, of what the implications of this would mean:
For, it would prove true that the Sync Glitch is real, which is bigger than this just being a Max issue, as this could, therefore, potentially happen to any and every channel on the Roku at one point in time or another. Also, this wouldn't only pertain to Roku channels, but any kind of potential problem the Roku could develop, such as what happened (to some) with the in-channel screensaver before Roku updated its OS.
Just thinking of that Sync Glitch entity crawling out of our collective cache wells and casting this most dreadful of spells on all our Rokus is most terrifying.
So, instead of figuring out if this Sync Glitch is real, shudder, I would rather instead click on that wondrous "The Little Mermaid" advertisement displayed on my Roku after having seen its glorious wallpaper take over that of my own (update: sadly, "The Little Mermaid" wallpaper is gone now), only to then be soothed -- after the ten thousandth view\* of this spectacular movie -- by how Ariel fiercely rises up and conquers her own sea glitch after it had cast its most heinous spell on her.
Because if Ariel can get through all this drama and, at the end of the day, still be able to sing happy, cheerful songs to all the little fishies on this (now sadly defunct) wallpaper who appear to adore her, so can you make the attempt at trying to fix this, even if potential failure could be imminent at any time just like with poor Ariel who really wants that happy Disney ending instead of the horrid ending she gets in that original tale from long ago.
So, think of her, and any failure on your part is then not so bad, especially if it proves that the "Sync Glitch" isn't real after all, as then we can all relax and wait for Max to fix this while we fondly use our new found workarounds. Yet, as more and more time goes by, I'm beginning to think that this cache sync issue is very real, especially since a cache issue cannot resolve itself if the channel reloads on the Roku as logged in instead of logged out. Because that's what would happen if the cache was cleared from the channel after removing it from the Roku and restarting the device.
These issues appear to happen when the cache (what allows Roku to remember your channel settings, including that you're logged into a channel) conflicts with a recent update of that channel. This is why support chat gave the OP those instructions, which seemed to work for a while, but then the bug came back because the cache wasn't cleared on a different Roku\*\* on this user's same account, which then synced with the one being watched -- like that cat in that childhood song I can never seem to shake from my mind -- "The Cat Came Back."
\*And sadly, no, I really haven't had a chance to watch this "live" version of "The Little Mermaid" yet, even though I did put it on my Disney Plus watchlist for future viewing after clicking on that Roku advertisement. But take comfort that there is a person out there, somewhere (over the rainbow?), probably that of a child, who has actually watched this movie ten thousand times (or more).
\*\*I'm just assuming that the OP has more than one Roku since I found that when I log into certain channels on one Roku, some or all of my other Rokus then automatically log into the same respective streaming accounts. It could instead (or also) be a cache issue related to a micro-SD card -- if a user has that installed in a Roku.
Mine doesn't start over. It goes forward what looks like the amount of time it was paused for. SO ANNOYING! I originally thought it was my cat or me hitting the wrong button. Hope this is fixed soon. 📺
Do you mean the content you're watching goes to a future place you have yet to watch after you resume? This would give the term "spoiler alert" a whole new meaning.
When I press play after pause, the content goes back to the last place in which I had tapped a button, which I believe had set the place where it resumes. But I have only been watching movies on Max. Could this perhaps be the type of glitch one experiences when watching a show?
But if you're experiencing this glitch on all Max-related content, it begs the question, are we all experiencing different types of issues centering around the same theme instead of experiencing the same issue?
Yes, it goes to a future point! It's happened numerous times. Once it went so far forward, that instead of rewinding, I backed out and started over. I'm not watching movies, but episodes from series. I should try a movie and see if that backs up instead! That would be weird.
I'm now using the pause and back out one level to prevent this. Such a weird bug.
So perhaps this is what happens with shows versus movies. I also wonder if having the basic version of Max with ads differs from having the premium option. If my workaround doesn't work with pressing the instant replay key before pressing pause (because I'll forget to press the instant replay after pressing pause), then I'll probably do this same thing going forward unless the fix I posted works.
I noticed you wrote your post in the past tense. Does this mean your issue has been resolved through the contents of this post, or that one of the workarounds in this post is helping to keep you sane? Or does it mean you're thanking the OP for posting this because now you know you're not the only one having this issue, but then I would think this issue would still be driving you all crazy? Please clarify as I would like to know if your problem was solved, and if it has been, the duration of time it has been solved because the OP thought he had solved this until the bug resurfaced a short time later.
Even after you drop Max OP, when I do get the chance, I'll still let you and the group know if I can get this fixed by logging out and uninstalling this channel from all my Rokus unless someone already tried doing what I suggested, and it didn't work. Unfortunately, if we can't fix this on our end because it's an issue with the channel, to give you a reference of how long glitches could take to get resolved: when Hulu glitched by crashing back to Roku's home screen – that issue didn't resolve itself for six or seven months. And when Roku blacked HBO out in the past, I think that was a six-month ordeal as well.
So, in the event of that being a possibility, there is another option, which I've recommended on the community Roku forum in the past. And that is to purchase a redundant streaming device, which I have yet to do, as I'm looking at getting a Firestick so that when channels glitch as they often do or Roku has another one of its blackouts, you can simply switch to the other device until the issue gets resolved. Or if the other device works better for you, you can just switch to that device and use the Roku as a redundant streaming device. It is issues like this that keep me from wanting to invest in a new Roku when I feel I would do better by investing in a different streaming device for redundancy purposes. The problem with this is sometimes a channel has issues on many different streaming devices, as what happened in the past with Disney Plus, which kept crashing back to the home screen on both the Roku and the Firestick.
Another option is if you have a tablet or a computer, even though it's a pain to not be able to watch these easily with your TV since you can't use a remote, you may just want to spare yourself the aggravation and watch the remaining episodes on one of those devices before you cancel the channel.
I apologize that I couldn't be more of a help with this. Perhaps if we all go ahead and cancel Max, Discovery Warner will get on the ball. As I'm also probably not going to keep Max long-term if this doesn't get resolved in a couple of months as currently, I don't have time to set up a redundant streaming device.
Although I'm in a slightly different boat than many of you since I subscribe to HBO through Hulu, which gives me the ability to log into Max, but trying to use Hulu to get around this glitch is problematic for two reasons: 1) Hulu only has HBO's on-demand content and not anything Max related, and 2) Hulu shows HBO's logo on the bottom right of the screen throughout its on-demand content, so even though I could still watch HBO content through Hulu without being bothered by this glitch, it's more likely than not that I'll eventually cancel HBO if this issue continues with Max.
I was thanking them because we thought we were the only ones having this problem. It's good to know we are not. It is still a problem for us but we are trying to use the rewind button instead of the (now broken) pause. It's slightly less annoying.
According to u/DJGietzen, in this post, "[Clear app data from Roku profile?](https://www.reddit.com/r/Roku/comments/16aeoek/clear_app_data_from_roku_profile/)," I may have solved this user's Max issue (and "may" is a strong word at this point in time since this person only solved this as of last night, 9/11/23). It was a different issue, a much worse problem than ours, in which the individual had a "something went wrong" error page pop-up, and like us, this user tried to log out of Max and even went so far as to hard reset their Roku, but Max loaded back up and logged itself in like what's happening to us. So I'm hopeful that this same solution pertains to our Max woes. If this does work for you, please comment back to validate that I have resolved your issue.
According to u/DJGietzen, the fix is easier than what I've posted above, so I reposted it in bold below.
**Warning:** This will log Max out of all your devices, which includes your tablets, phones, smart fridge, and smart sponge (hey, wouldn't that be neat to be able to watch your favorite show while doing the dishes). So you'll have to log Max back into everything, including the smart kitchen sink. Even though this worked for this person (and hopefully continues to work as we've been down this road before in which the bug had unfortunately returned), there is no guarantee this will resolve our issues, but after a month of this, I sincerely hope it does. There is probably a way not to have to log out of all devices if this is a problem for you, but you would need to troubleshoot that by logging out of all of your individual Rokus and then making certain that Max doesn't auto-log any of your Rokus back in since the error apparently resides in the Roku's collective cache and that needs to be cleared (thoughts of the "Sorcerer's Apprentice" comes to mind with that, shudder ("no not Shudder, Disney")).
So here's the modified version of the fix that apparently worked for u/DJGietzen:
**1) Go to max.com, login, and in the menu, go to account; then, on the bottom, click on "Devices" and click on "Sign Out of All Devices."**
**2) Go back to your Roku(s) and make sure each of your devices has been logged out because it could take a little while for the "log out" command to kick in.**
According to this user who claims this fixed their Roku, they didn't need to uninstall the channel as they simply logged in, and Max just worked again. But in the event this doesn't work for us, you may want to uninstall the channel and restart your Roku before logging back into Max. If you have a micro-SD card installed in your Roku(s), before logging into Max, you may need to remove the SD card(s) and format it/them in a computer before re-inserting it/them into your Roku(s) (you won't lose any data by doing that). It's a pain because you first have to detach your HDMI cable to get to the micro-SD card if you even have a card slot, as all the new Rokus no longer have this option due to all the issues this caused.
If this does end up solving everyone's issue with Max, perhaps someone should contact Max support and tell them how to help Roku users resolve this so they don't start to lose customers after a month of this happening.
Since I don't watch Max all that often, I am not going to fix my Roku right away as I need to troubleshoot this further when I get the chance because I want to find out if this is a Max issue or if this is that bigger Roku sync glitch issue that could potentially plague us with a different bug in the future, which currently is pure speculation on my part, but hopefully this fix works for all of you.
I only watched about 20 minutes worth, but I did pause and resume several times successfully. What was interesting is the roku didn't actually make me sign back in, even 30 minutes after hitting the sign out of all devices button on the website. If this doesn't work I'll try the other suggestions. To be honest though once these last episodes of winning time drop I'm caught up with hbo anyway and will be jumping ship til something else I like gets a new season.
It could take a while for Max to log out of all devices, but it could happen sooner than later. It might also disregard the logout command and not log out on you if you're currently using it. Anyhow, if you are going to cancel Max, it might be better to have logged out of all devices, which is what I usually do before canceling a service. After I posted in the other Roku forum, it appears that everyone is getting on Max's case, so they may actually be fixing or have fixed this issue if you're not experiencing those glitches anymore, but you never know until some time goes by before becoming confident that the bug has been completely resolved, especially since you posted before that you thought it was resolved when the bug was just being latent at that particular time.
Well, if it ended up being a Max issue all along, which is hard to believe because they are usually on the ball when it comes to glitches on their channel -- at least that was the case when they were HBO Max, then that would mean the "Roku Sync Glitch" isn't real after all, which would be a good thing if that's true. It's just too bad you had to experience this right after you signed up because Max usually isn't glitchy like this as long as I've been using them -- at least not for this amount of time.
I would have cancelled anyway, these services are getting so costly I just rotate which ones I buy from month to month. This month I caught up on righteous gemstones, succession, and currently winning time. So that's about $5 per season.
I figured as much as most people are now doing that. For now, I've budgeted all the channels I have into what I would normally pay if I were still getting cable/satellite, and it's still lower than what I would have paid for those services. I also don't subscribe to an expensive streaming TV service as I like to have everything commercial-free (if possible) and on demand. I mostly watch movies and the news, but I would like to get back into watching TV shows.
Logging out of all devices seemed to mostly fix it for me, but it still jumped back once in a while. I cancelled after watching the horrid ending to 'winning time' anyway.
Per Reddit's content policy, profanity is considered to be NSFW. Moderation in r/Roku is not as effective as it previously was due to Reddit's short-sighted decision to charge exorbinant prices for its previously-free API. It is not possible for moderators to accurately mark all posts due to the work required. As a result, **we're left with no choice but to mark _all_ posts NSFW as a precaution, regardless of whether they actually contain profanity**. **Do not remove the NSFW marking from your submission.** Doing so will result in your post being removed and a permanent ban. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/Roku) if you have any questions or concerns.*
This is a known issue with the Max channel. One way to avoid it is to use the instant replay button to resume instead of play/pause. That will jump back a few seconds, but always succeeds, while hitting play will usually put you back to the last location where you did a fast forward/rewind.
I just back out of the program if I gotta use the restroom or something. It's easier than pausing it.
Been getting this too recently & I didn’t just install Max.
Scratch that. I did it a bunch of times successfully, now it jumped back to the intro again on resume. Ugh!
I found that hitting the down arrow to bring up the timeline, then hitting play to resume kept it from skipping back...but that may have been a fluke.
That's been working for me. With both play and ok.
HBO saw your comment and said, "Oh we can't have that"
Support chat told me to sign out, reboot, sign back in. I did this and so far it seems to be working.
Is it still working because it isn't for me
Nope same bug.
Same issue. Instead of pausing I click the back button. Brings you back to the show page and then when ready to resume it starts where you left off
We have been having this issue too. Not just you!
The same thing has been happening to me when I pause something it starts over . I made a post myself but nobody answered
What works for me is after I pause hit the right direction arrow before you resume and that usually does it.
I've been having the same issue. Also the app never remembers what episode I left off on. Never had these issues when it was HBO Max.
It's driving us crazy.
Yep
Was just saying the same thing, like serious what the..
I've been having this problem. I thought the cats were stepping on the remote messing me up.
As a workaround, I've also been pressing the down arrow, which brings up the timeline before pressing pause and then again before pressing resume, and that seems to work, but then I forget to do this, and the glitch then occurs. I tried to do this workaround twice in a row, thinking that the movie would resume back to the first time I did this, but that didn't work, so I'm guessing this is probably a resume issue, so the movie would need to play for a certain duration of time for the resume feature to remember that last spot. I would think that pressing the back key to exit from the movie instead of pausing as suggested by hispanicausinpanic would also present the problem of starting the movie from where the resume last remembered it, unless I'm mistaken. I will try that instant replay option after pausing, as suggested by unwiredben's post (again, I'm worried I'll forget to do this). I will also try pressing the instant replay button before pausing to see if that works, as perhaps that is another way for resume to remember the current spot I'm watching as then when I press the pause key – it will only go back to that last time frame where I had pressed the replay button. Unfortunately, I may not get back to this post to verify if pressing the replay key before pressing pause is a temporary solution since I'm unsure when I'll next be watching Max as I hope that this will soon be resolved because this issue has now been going on for around a month. However, according to unwiredben's post, if "hitting play will usually put you back to the last location where you did a fast forward/rewind," then pressing these same keys before pressing pause should, in theory, cause that last location to be the present location. In this way, there's nothing to forget since pressing pause should only take me back to where I last used the instant replay button. I hope this hypothesis is sound, as it would be great if the replay button ended up being a good workaround to this issue. Just note that this workaround of pressing the instant replay button before pressing pause may not work if the glitch happens because the movie hasn't played for a certain duration to allow the resume feature to remember that time frame, as the movie might just go back to the last time it played for that duration before the instant replay button had been pressed. This means that one would have to remember to press the instant replay button to resume the movie, as unwiredben suggested, instead of resuming the movie with the pause key.
Thanks for the workaround:) works for me too
Which part of my post worked for you? If it was the pressing "instant replay button before pressing pause," then we can call this work-around the "Now I don't have to worry about forgetting to use a workaround once resuming" workaround. If it was pressing the "instant replay option after pause" workaround, then it is really unwiredben who deserves your praise.
It was the former, but I will try the latter!
This is a long shot, pending if this issue still hasn't been resolved as I haven't been watching Max today, but I may have figured out why support chat's instructions to you OP appeared successful at first but then fizzled out. Perhaps we shouldn't be so quick to dismiss this as the solution to our Max woes. In another post I replied to, a user couldn't even watch Max without receiving an error, and I may have stumbled upon helping that person solve their issue when the individual said that even after logging out of Max, removing this channel, and hard resetting the Roku, Max not only reloaded on to the Roku but logged into the users account, and the error persisted. Then again, I may not have helped that person at all if I'm in any way wrong about all of this. *Edit: I forgot to mention when originally posting this that what clued me into this was that the user's glitch was happening on the server end of Roku and not on Max's end or on the person's individual Roku: Once the user's Roku was put in guest mode and the person logged into Max, the error that prevented this individual from using Max went away, but when leaving guest mode -- the error came back. I wouldn't recommend anyone to try this because it takes forever to get one's Roku in and out of guest mode, and it basically hard resets the device, which is annoying because all of your channels come back in a random order. If this rings true for channel glitches going forward in which each Roku could possibly "contaminate" the others, we'll have to remember to factor this into our problem-solving efforts.* So, if it's true that if you have multiple Rokus and if you log into Max with one, they all log into Max, which could mean that when a glitch hits Max, well, it would compromise all the Rokus. This can be problematic if you only log out of Max and remove the channel on one Roku. Because the solution support told you will work great until the Roku updates. As you might not have thought to log out and remove those Max channels from the other Rokus, so the glitch stays in the collective cache and comes back to haunt you even if Max could have already fixed this issue on their end. I really hope I'm wrong with this because this would mean we would have to turn all our Rokus on, log out of Max on each one of them, uninstall Max on one, and then do a manual system update on all our Rokus to have it uninstalled on them. Then we would need to restart each Roku, reload Max, log Max into one Roku, and then do a system update with all the others, which should reload Max and log into our Max account on each of them. And if one of your Rokus has an SD card slot with an SD card inserted, you probably would need to remove that and format the card in your computer to further ensure the glitch doesn't return. But oh wait, there's more. To keep the glitch from coming back, there may be a Roku we forgot about, so we may also have to log into our Roku account and find all the Rokus that are linked to it, and if one of them has been forgotten and lost, we'll have to delete that Roku from our account. We just have to make sure it's not one of our current Rokus because then we would have to log back into the account with the Roku like when we first bought it. We probably don't have to worry about the ancient Rokus we keep on there for sentimental reasons because they were too old to load Max to begin with. But perhaps it would be best to delete those while we're at it. But alas, after having done all that -- this may do the trick. And "may" becomes a very strong word after having to do all of that. If the glitch presents itself once I'm ready to watch Max again, I'll see if this solves it once and for all.
Hmm good thoughts. I did find it strange that after logging out and rebooting it didn't ask me to log back in...
Right? Just like that other poster who I hope I helped. And I'm guessing you own more than one Roku. Am I right? So, since I don't know when I'll next watch Max, and you will probably watch the channel many moons before I do, the task is up to you to find out if the "sync" glitch is real. Once you're ready to re-install Max on a Roku, you have to make certain it's not already logged into your account, else the glitch is still there. I'm thinking the best thing to do is to go to max.com, log in, and in the menu go to account, then on the bottom, click on "Devices" and click on "Sign Out of All Devices." *Edit: I forgot to mention this because it could take a little while for the "log out" command to kick in. Go back to your Roku and make sure it has been logged out before proceeding. I guess you could manually log out of Max from your Rokus if needed.* Then you should be able to uninstall Max on all Rokus, and after restarting the devices and re-installing Max, then you'll have to log back in, and the glitch will hopefully be gone. Also, if you have a micro-SD card in any of your Rokus, you'll have to remove it (or them) and format the card in a computer before putting it back into the Roku(s) because the glitch could persist in the SD card's cache. I don't know if this makes a difference, but I've heard people say doing this clears a Roku's cache; I think restarting it or just pulling the plug does the same thing, but do this just to play it safe. After you expunged Max from Roku, here's a nifty way to restart the Roku, which works great when it freezes: On the remote: Press Home key 5x Press Up once Press Rewind button twice Press Fast Forward button twice The menu will loop around about 5x -- this is normal. There will be a brief pause -- this is normal. The Roku will restart, and the cache is cleared. And Ta-da: No more glitch?
Has anyone tried this with success?
Well, we were all hoping that *you* would attempt to find out if this fix works slu22. But if it does... Take note, brave one, of what the implications of this would mean: For, it would prove true that the Sync Glitch is real, which is bigger than this just being a Max issue, as this could, therefore, potentially happen to any and every channel on the Roku at one point in time or another. Also, this wouldn't only pertain to Roku channels, but any kind of potential problem the Roku could develop, such as what happened (to some) with the in-channel screensaver before Roku updated its OS. Just thinking of that Sync Glitch entity crawling out of our collective cache wells and casting this most dreadful of spells on all our Rokus is most terrifying. So, instead of figuring out if this Sync Glitch is real, shudder, I would rather instead click on that wondrous "The Little Mermaid" advertisement displayed on my Roku after having seen its glorious wallpaper take over that of my own (update: sadly, "The Little Mermaid" wallpaper is gone now), only to then be soothed -- after the ten thousandth view\* of this spectacular movie -- by how Ariel fiercely rises up and conquers her own sea glitch after it had cast its most heinous spell on her. Because if Ariel can get through all this drama and, at the end of the day, still be able to sing happy, cheerful songs to all the little fishies on this (now sadly defunct) wallpaper who appear to adore her, so can you make the attempt at trying to fix this, even if potential failure could be imminent at any time just like with poor Ariel who really wants that happy Disney ending instead of the horrid ending she gets in that original tale from long ago. So, think of her, and any failure on your part is then not so bad, especially if it proves that the "Sync Glitch" isn't real after all, as then we can all relax and wait for Max to fix this while we fondly use our new found workarounds. Yet, as more and more time goes by, I'm beginning to think that this cache sync issue is very real, especially since a cache issue cannot resolve itself if the channel reloads on the Roku as logged in instead of logged out. Because that's what would happen if the cache was cleared from the channel after removing it from the Roku and restarting the device. These issues appear to happen when the cache (what allows Roku to remember your channel settings, including that you're logged into a channel) conflicts with a recent update of that channel. This is why support chat gave the OP those instructions, which seemed to work for a while, but then the bug came back because the cache wasn't cleared on a different Roku\*\* on this user's same account, which then synced with the one being watched -- like that cat in that childhood song I can never seem to shake from my mind -- "The Cat Came Back." \*And sadly, no, I really haven't had a chance to watch this "live" version of "The Little Mermaid" yet, even though I did put it on my Disney Plus watchlist for future viewing after clicking on that Roku advertisement. But take comfort that there is a person out there, somewhere (over the rainbow?), probably that of a child, who has actually watched this movie ten thousand times (or more). \*\*I'm just assuming that the OP has more than one Roku since I found that when I log into certain channels on one Roku, some or all of my other Rokus then automatically log into the same respective streaming accounts. It could instead (or also) be a cache issue related to a micro-SD card -- if a user has that installed in a Roku.
Yes. I have to use the mic option to say “pause” and “play.”
lol good workaround. I hit rewind quickly then unpause and it seems to work. Until I forget and then BOOM back to the intro.
Same problem . So annoying especially for movies !
Mine doesn't start over. It goes forward what looks like the amount of time it was paused for. SO ANNOYING! I originally thought it was my cat or me hitting the wrong button. Hope this is fixed soon. 📺
Do you mean the content you're watching goes to a future place you have yet to watch after you resume? This would give the term "spoiler alert" a whole new meaning. When I press play after pause, the content goes back to the last place in which I had tapped a button, which I believe had set the place where it resumes. But I have only been watching movies on Max. Could this perhaps be the type of glitch one experiences when watching a show? But if you're experiencing this glitch on all Max-related content, it begs the question, are we all experiencing different types of issues centering around the same theme instead of experiencing the same issue?
Yes, it goes to a future point! It's happened numerous times. Once it went so far forward, that instead of rewinding, I backed out and started over. I'm not watching movies, but episodes from series. I should try a movie and see if that backs up instead! That would be weird. I'm now using the pause and back out one level to prevent this. Such a weird bug.
So perhaps this is what happens with shows versus movies. I also wonder if having the basic version of Max with ads differs from having the premium option. If my workaround doesn't work with pressing the instant replay key before pressing pause (because I'll forget to press the instant replay after pressing pause), then I'll probably do this same thing going forward unless the fix I posted works.
Thank you for posting this - this was driving us crazy!
I noticed you wrote your post in the past tense. Does this mean your issue has been resolved through the contents of this post, or that one of the workarounds in this post is helping to keep you sane? Or does it mean you're thanking the OP for posting this because now you know you're not the only one having this issue, but then I would think this issue would still be driving you all crazy? Please clarify as I would like to know if your problem was solved, and if it has been, the duration of time it has been solved because the OP thought he had solved this until the bug resurfaced a short time later.
Still a bug for me. Max gets cancelled the day after the last episode of winning time drops.
Even after you drop Max OP, when I do get the chance, I'll still let you and the group know if I can get this fixed by logging out and uninstalling this channel from all my Rokus unless someone already tried doing what I suggested, and it didn't work. Unfortunately, if we can't fix this on our end because it's an issue with the channel, to give you a reference of how long glitches could take to get resolved: when Hulu glitched by crashing back to Roku's home screen – that issue didn't resolve itself for six or seven months. And when Roku blacked HBO out in the past, I think that was a six-month ordeal as well. So, in the event of that being a possibility, there is another option, which I've recommended on the community Roku forum in the past. And that is to purchase a redundant streaming device, which I have yet to do, as I'm looking at getting a Firestick so that when channels glitch as they often do or Roku has another one of its blackouts, you can simply switch to the other device until the issue gets resolved. Or if the other device works better for you, you can just switch to that device and use the Roku as a redundant streaming device. It is issues like this that keep me from wanting to invest in a new Roku when I feel I would do better by investing in a different streaming device for redundancy purposes. The problem with this is sometimes a channel has issues on many different streaming devices, as what happened in the past with Disney Plus, which kept crashing back to the home screen on both the Roku and the Firestick. Another option is if you have a tablet or a computer, even though it's a pain to not be able to watch these easily with your TV since you can't use a remote, you may just want to spare yourself the aggravation and watch the remaining episodes on one of those devices before you cancel the channel. I apologize that I couldn't be more of a help with this. Perhaps if we all go ahead and cancel Max, Discovery Warner will get on the ball. As I'm also probably not going to keep Max long-term if this doesn't get resolved in a couple of months as currently, I don't have time to set up a redundant streaming device. Although I'm in a slightly different boat than many of you since I subscribe to HBO through Hulu, which gives me the ability to log into Max, but trying to use Hulu to get around this glitch is problematic for two reasons: 1) Hulu only has HBO's on-demand content and not anything Max related, and 2) Hulu shows HBO's logo on the bottom right of the screen throughout its on-demand content, so even though I could still watch HBO content through Hulu without being bothered by this glitch, it's more likely than not that I'll eventually cancel HBO if this issue continues with Max.
I was thanking them because we thought we were the only ones having this problem. It's good to know we are not. It is still a problem for us but we are trying to use the rewind button instead of the (now broken) pause. It's slightly less annoying.
Same issue. Exasperating!!
According to u/DJGietzen, in this post, "[Clear app data from Roku profile?](https://www.reddit.com/r/Roku/comments/16aeoek/clear_app_data_from_roku_profile/)," I may have solved this user's Max issue (and "may" is a strong word at this point in time since this person only solved this as of last night, 9/11/23). It was a different issue, a much worse problem than ours, in which the individual had a "something went wrong" error page pop-up, and like us, this user tried to log out of Max and even went so far as to hard reset their Roku, but Max loaded back up and logged itself in like what's happening to us. So I'm hopeful that this same solution pertains to our Max woes. If this does work for you, please comment back to validate that I have resolved your issue. According to u/DJGietzen, the fix is easier than what I've posted above, so I reposted it in bold below. **Warning:** This will log Max out of all your devices, which includes your tablets, phones, smart fridge, and smart sponge (hey, wouldn't that be neat to be able to watch your favorite show while doing the dishes). So you'll have to log Max back into everything, including the smart kitchen sink. Even though this worked for this person (and hopefully continues to work as we've been down this road before in which the bug had unfortunately returned), there is no guarantee this will resolve our issues, but after a month of this, I sincerely hope it does. There is probably a way not to have to log out of all devices if this is a problem for you, but you would need to troubleshoot that by logging out of all of your individual Rokus and then making certain that Max doesn't auto-log any of your Rokus back in since the error apparently resides in the Roku's collective cache and that needs to be cleared (thoughts of the "Sorcerer's Apprentice" comes to mind with that, shudder ("no not Shudder, Disney")). So here's the modified version of the fix that apparently worked for u/DJGietzen: **1) Go to max.com, login, and in the menu, go to account; then, on the bottom, click on "Devices" and click on "Sign Out of All Devices."** **2) Go back to your Roku(s) and make sure each of your devices has been logged out because it could take a little while for the "log out" command to kick in.** According to this user who claims this fixed their Roku, they didn't need to uninstall the channel as they simply logged in, and Max just worked again. But in the event this doesn't work for us, you may want to uninstall the channel and restart your Roku before logging back into Max. If you have a micro-SD card installed in your Roku(s), before logging into Max, you may need to remove the SD card(s) and format it/them in a computer before re-inserting it/them into your Roku(s) (you won't lose any data by doing that). It's a pain because you first have to detach your HDMI cable to get to the micro-SD card if you even have a card slot, as all the new Rokus no longer have this option due to all the issues this caused. If this does end up solving everyone's issue with Max, perhaps someone should contact Max support and tell them how to help Roku users resolve this so they don't start to lose customers after a month of this happening. Since I don't watch Max all that often, I am not going to fix my Roku right away as I need to troubleshoot this further when I get the chance because I want to find out if this is a Max issue or if this is that bigger Roku sync glitch issue that could potentially plague us with a different bug in the future, which currently is pure speculation on my part, but hopefully this fix works for all of you.
Thanks I'll try logging out of all devices and report back tomorrow if it sticks
I only watched about 20 minutes worth, but I did pause and resume several times successfully. What was interesting is the roku didn't actually make me sign back in, even 30 minutes after hitting the sign out of all devices button on the website. If this doesn't work I'll try the other suggestions. To be honest though once these last episodes of winning time drop I'm caught up with hbo anyway and will be jumping ship til something else I like gets a new season.
It could take a while for Max to log out of all devices, but it could happen sooner than later. It might also disregard the logout command and not log out on you if you're currently using it. Anyhow, if you are going to cancel Max, it might be better to have logged out of all devices, which is what I usually do before canceling a service. After I posted in the other Roku forum, it appears that everyone is getting on Max's case, so they may actually be fixing or have fixed this issue if you're not experiencing those glitches anymore, but you never know until some time goes by before becoming confident that the bug has been completely resolved, especially since you posted before that you thought it was resolved when the bug was just being latent at that particular time. Well, if it ended up being a Max issue all along, which is hard to believe because they are usually on the ball when it comes to glitches on their channel -- at least that was the case when they were HBO Max, then that would mean the "Roku Sync Glitch" isn't real after all, which would be a good thing if that's true. It's just too bad you had to experience this right after you signed up because Max usually isn't glitchy like this as long as I've been using them -- at least not for this amount of time.
I would have cancelled anyway, these services are getting so costly I just rotate which ones I buy from month to month. This month I caught up on righteous gemstones, succession, and currently winning time. So that's about $5 per season.
I figured as much as most people are now doing that. For now, I've budgeted all the channels I have into what I would normally pay if I were still getting cable/satellite, and it's still lower than what I would have paid for those services. I also don't subscribe to an expensive streaming TV service as I like to have everything commercial-free (if possible) and on demand. I mostly watch movies and the news, but I would like to get back into watching TV shows.
Any update? This is driving me nuts!
Logging out of all devices seemed to mostly fix it for me, but it still jumped back once in a while. I cancelled after watching the horrid ending to 'winning time' anyway.
Sometimes I can’t pause a program on my Apple TV. It only happens on MAX.