There are systemic unresolved issues going back years, due to this forum auto closing topics after 30 days.
Issue: Youtube stops playing after tabing to another window or locking your screen.
(Look it up there’s about 100 closed threads)
How about addressing the issue instead of closing all the threads?
Please feel free to share the URLs of those threads here. I was able to find a few of them (all of which I’ve re-opened and responded to) but certainly not 100 of them.
Topics on this site auto-close to avoid having too much clutter, as “dead”/“inactive” threads pile up. It is not a perfect system but it does help our [very small] support team view the latest/most pressing issues users are encountering. I can work on adjusting the auto-close function to be more specific perhaps to "only close if user hasn’t responded in X days and that thread has a reply from Brave team member".
As for the actual issue itself I cannot reproduce it on any platform I have (tested on iOS, macOS, Windows and Android) have only seen one user report this in the last few months. I’m inclined to think that whatever was causing that issue was resolved with a browser update.
If you are encountering this issue, please let me know and I’ll be happy to assist you in solving it.
@theArchitecht, one of the main challenges is when users don’t reply with the necessary information. When topics close after no updates or tags for over 30 days, it’s often because either the issue has been resolved through updates or other changes, or users have moved on. In either case, they aren’t providing updates or confirming whether the problem is ongoing. People can’t be helped if they aren’t here to share information and/or aren’t willing to test anything.
With over 200 topics and 2,000 posts in the past 7 days alone, there’s a lot to keep up with. By no means is it possible to constantly track every single topic across time, it becomes quite numerous. The focus needs to stay on current issues where users remain active and provide feedback. It can be tough to help if someone doesn’t return for more than 30 days, especially when the issue can’t be replicated.
So, locking older threads helps keep attention on the active issues and reduces distractions, especially for people who might necro topics that have nothing to do with whatever they are posting about.
This is your first topic/post. You provided absolutely no information on any issue you’re facing. Like let’s say it’s the YouTube not playing. You erased the template and chose not to say any of the following:
@Mattches looking at their phrasing, they are being disingenuous. Rather than speaking of closed threads surrounding one issue, they are just focusing on the idea that any topic has been closed after 30 days of inactivity. Then just trying to blast support for allowing those to close rather than “solve” each and every single issue.
I have thought of suggesting something before, but after seeing a large number of old things get necroed, especially with the person reviving it going off topic, it doesn’t seem worth it. If I were to change anything it might be to have the system send a notification or something to warn whoever opened the topic that it will close if they don’t reply soon. So if closing after 30 days, maybe give them that notice at the 25-28 day mark or something.
Otherwise it just gets a bit crazy.
Im simply looking for resolution to thia issue that has apparently persisted since before 2021. I just updated Brave today and am now experiencing the issue.
@theArchitecht I’m pretty confident you’re not here for help. Know why?
I spend a LOT of time helping people on here and generally keep an eye out for any variety of issues. If I see enough people reporting problems and I can’t help my fellow users resolve things, I reach out to support or developers from Brave to get involved and try to help get things fixed.
Below is a video which has me say some of that and you’ll hear a bit of my frustration, but you’ll also see things work on my Android in a way you claim doesn’t happen. If you sincerely need help, then you need to start providing more details so you can be helped. But at least in testing, it’s clear that this isn’t a Brave issue as it works as expected. It would be something users have changed in settings or is their particular OS settings causing problems.
And example of when I say not true or whatever. Let’s say you were talking about this one:
But then guess what? They responded back to say the issue went away when they reset their phone. In other words, it was something on their settings. But the issue was resolved. So not an ongoing/unsolved problem.
And then another with the same thing.
I’m surprised you guys haven’t closed this thread already. In spite of all your personal attacks on me for simply identifying an issue on this platform, here is some more background on the issue with Brave.
Prior to upgrading to version 1.68.134 (Android 12; Build/SP1A.210812.016 / Samsung Note20) If I was listening to music on Youtube and locked my screen the music would keep playing and the little media player app would persist on the locked screen which would allow you to pause/play ffwd/rwnd.
Now after upgrading when I lock the screen the apps goes away and the music stops. It may be a broken Android setting on my part I don’t know. Was just hoping someone had some insights but all the threads keep getting closed and all you want to do is attack me personally
I do apologize coming off as defensive — though it is easy to be defensive when your first post ends with
That said, lets move passed all that and try and get your issue resolved now that you’ve provided some details surrounding it.
If I understand you correctly, you’re saying that when playing content on Youtube and you lock your screen, the background play feature no longer works properly — correct? If so, then this is something I cannot reproduce on my Galaxy using the latest build of the browser (1.71.114). On my end, YT content continues to play even when the screen is locked.
Can you please confirm for me that you are in fact using the latest build of the browser at this time (1.71.114) when you see this issue? If you are, can you please try downloading the Beta build of the Brave app (you can download this from the Play Store), and test the same functionality there and tell me if it works?
Note that the Beta build will install separately on your device — it will not overwrite any data from the stable build.
I will give this a shot, and post results. Thank you
Installed beta and same result. It must be an obscure Android setting. It may be the
@theArchitech,
I checked on my Android device and couldn’t find anything relevant. I’ll have to ask the Android team about this because I’m unclear on why this might be the case, given that I do not see this behavior on any build of the browser.
Can you confirm for me that at this point your Brave version is the latest build at this time (v1.71.114)?
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
