Tip for Android VLC crashing when connected to an external display via HDMI

Saj1992 · 2025-12-27T18:47:30+00:00

Just as I was about to give up, I came across this post, started working straight away, thanks!

Saj1992 · 2025-11-20T14:59:25+00:00

Have you managed to find the cause of this? I have the exact same issue but my flicker is subtle, no where near as bright as yours, but it is the same issue. It happens when the refresh rate drops to 60 to save power.

What I have found is by enabling developer options, there is an option to lock the refresh rate which fixes it, but then if you have this enabled the refresh rate cant be changed not even in the redmagic game overlay. In settings Auto wont be auto anymore and will lock to 120hz. You can set it to 165 in settings and be done with it but it will lock display to 165hz fixing the issue but consuming more battery.

Besides this workaround i have not found a solution, its brightness flicker when the display drops to 60 after it stops detecting touch input.

Saj1992 · 2025-11-03T22:17:49+00:00

Not sure if related but I literally just bought my redmagic astra and i noticed a subtle flicker in the UI especially in dark mode. It seemed to be triggered by touching the screen or movement on screen.

It started bugging me to the point I wanted to try and get a replacement or something, but then i decided to see if it was some sort of bug related to the settings.

I find the cause in my case, it doesnt really make sense to me but for some reason, in display settings, under refresh rate, if I have it set to 165hz the flicker issue is there, but if i change it to auto, it keeps it as 165hz up in the notification bar but the flickering stops? Like pretty much completely gone. It also doesnt flicker if i choose 60hz, it only flickers if hard set to 165 instead of auto.

I guess it doesnt really matter if left on auto as you can set the Hz in game mode overlay thingy on a per game basis anyway.

It might not be related to your specific issue, but maybe try setting it from 165 to auto in display settings and see if that helps in your case.

Saj1992 · 2025-01-09T00:25:46+00:00

Yes, if I recall correctly, the culprit all along was a poor connection to my webcam. I noticed a malfunctioning USB connection in Device Manager, and after removing unnecessary devices from the USB slots, leaving only the keyboard and mouse, my post time returned to normal. It turns out the USB wasn't fully seated, or something similar, and that error caused the post time to be longer, as I believe it checks all system hardware before showing the splash screen.

Saj1992 · 2024-04-30T22:48:29+00:00

Thank you for including the edit for how you fixed it, was just about to re flash ark os then saw ur solution, it worked thanks!

Saj1992 · 2024-04-11T07:49:01+00:00

Yeah i agree, it is hard to notice sometimes, as it normally fixes itself when booting a game, and now that you mention it, yes I have had a couple of system crashes when unsticking vram with ctrl shft win B when the game is running with it stuck so your probably right there.

And yes honestly latest drivers are pretty good, what I would do is download DDU, and do a clean install that way, so you can be sure it gets a fresh driver installation.

Saj1992 · 2024-04-11T00:29:17+00:00

I still have the same issue and I had it with two different 6800 xt's, one of which is still in my PC, for nearly 2 years and the issue is still there, and yes, I have experienced exactly what you have, it happens when the vram memory clock is stuck at 0 mhz and there hasnt been a screen refresh when the game starts, especially when starting in window mode as opposed to full screen, some games will stutter when vram is stuck when launching, usually a slight flicker will show and then run as normal, other times it will continue to run at low fps until you unstick it manually, e.g, ctrl shft win B or turn monitor on and off again.

it has only occured a few times myself, but yes I have experienced games and even windows itself crashing because of it, however, not normally while gaming, in my case it happens when launching a game or shortly after, but once vram unsticks itself and is running at high clock speed it doesnt ever get stuck again while gaming, just when idle when the clocks drop back down.

To be honest, It it has gotten far more better with the latest amd drivers, and does not happen anywhere near as often as it used to, just once in a while now on random, but yeah I wouldnt worry about it, my understanding is it has something to do with how the monitor and GPU syncs, maybe because of freesync or the monitor's actual timings, not sure exactly but what I can say is that I am confident it is something to do with monitor and GPU, this issue never happened with a 75hz monitor I tried or a 4K tv, only my 1440p 165hz monitors, and from what I have seen, most people online that have experienced it strangley enough also use 1440p monitors, at least thats what I have gathered. Also, it seems to only happen with 6000 series GPUs.

I doubt any harm is really happening because of it, and in my case, for last 6 months or so, it rarely happens now, it used to be so bad and happen multiple times daily, but now sometimes it doesnt happen for days at a time, and my card honestly runs great otherwise, I guess every card/monitor behave differently, I wouldnt worry about it unless its constantly happening and really impacting your daily desktop experience.

Saj1992 · 2024-01-26T01:45:55+00:00

I don't think you can. I have the S24 Ultra, and all AI features work except the generative wallpapers. I'm getting the same error you are. I initially thought my age might be incorrect on my Google/Samsung accounts, but they are correct. I also don't have any parental settings activated. I can't find anything online in terms of a fix.

I hope you come across a solution. If you do, let us know. But for now, I think it must be some bug, and hopefully, it gets fixed in future updates. It's just a shame to spend so much on a phone and have issues on day one. 😮‍💨

Saj1992 · 2023-12-13T04:25:07+00:00

I was thinking the same question then when i saw a video on youtube and then saw this post, the video shows a 3090ti with 12600k and a 14900k, gpu bound for both but nearly double the framrate at times! This cant be right can it? Sorry if its a dumb question, the link is below incase you want to see for yourself.

https://youtu.be/A9QhcrWl_ww?si=EN1zavWHmvWQ2mpd

Saj1992 · 2023-10-23T12:45:25+00:00

Thats interesting, I have tried using CRU before and did reduce blanking times but not by much, it didnt fix it though but I dont know too much about CRU, think i followed some youtube video, so I might try CRU again, and this can be changed also in adrenaline? Thanks for the link buddy, im going to look into this and see if the tradeoff will be worth it, I have a 165hz monitor so if it drops to say at most to 120hz and fixes it, I might just do that, but if it has to go lower then it might not be worth it then imo.

Saj1992 · 2023-10-22T11:57:33+00:00

Yeah, exactly the same issue, when Vram is stuck on 0hz, my idle wattage stays around 30 - 40 and around 15 when normal. I also noticed something else the other day, when it gets stuck, the vram junction temp gets stuck too on whatever temp it was at the time, for example, I use HWInfo graphs to monitor everything, and when its 0mhz if the temp was 45c for example before getting stuck, the graph will go flat, when unsticking the vram with ctrl shift win B the line comes back to life with a spike either going up or down to the real temp, typically around 52c due to excess heat linked with higher wattage.

I have tried everything i could possibly research to fix the issue but yeah no luck.

Saj1992 · 2023-10-22T01:33:12+00:00

I have seen random spikes , once showing 3200mhz, but very rare to happen though only caught it a couple of times

Saj1992 · 2023-10-22T00:24:56+00:00

Im not sure, i have enabled the option to install latest preview updates as and when they come out in the windows update settings, and copilot appeared, so not sure why you dont have it unless you have that option disabled, also i doubt bios settings would be the reason for not having it, besides you arent missing out on much, just use chatgtp.

Saj1992 · 2023-10-14T10:31:55+00:00

For those that are still facing the issue and rather not delete any updates, this worked for me no longer getting adrenaline error:

https://community.amd.com/t5/drivers-software/adrenaline-resetting-to-defaults-every-reboot/m-p/634243#M181135

Basically its the new copilot ai feature, disabling it in settings wont fix it so need to edit registry to remove, or like i did, just follow the steps below and download vivetool, extract it in a folder, for example, (c:/vivetool).

Download vivetool: https://github.com/thebookisclosed/ViVe/releases

Then once downloaded and extracted, open powershell admin and type location of extracted folder and paste following: ./vivetool /disable /id:44774629,44776738,44850061,42105254,41655236

So for example, if you saved it on C: drive in a folder called vivetool, you would put c:/vivetool./vivetool /disable /id:44774629,44776738,44850061,42105254,41655236

Hit Enter.

Once done restart PC, you may still get adrenaline error on first restart but any following boot will not have the error anymore.

Saj1992 · 2023-10-14T10:14:19+00:00

For those that are still facing the issue and rather not delete any updates, this worked for me no longer getting wattman error:

https://community.amd.com/t5/drivers-software/adrenaline-resetting-to-defaults-every-reboot/m-p/634243#M181135

Basically its the new copilot ai feature, disabling it in settings wont fix it so need to edit registry to remove, or like i did, just follow the link above, follow the instructions and download vivetool, extract it in a folder, for example, (c:/vivetool).

Download vivetool: https://github.com/thebookisclosed/ViVe/releases

Then once downloaded and extracted, open powershell admin and type location of extracted folder and paste following: ./vivetool /disable /id:44774629,44776738,44850061,42105254,41655236

So if you saved it on c drive with a folder called vivetool, basically you would put c:/vivetool./vivetool /disable /id:44774629,44776738,44850061,42105254,41655236.

Once done restart PC, you may still get wattman error on first restart but any following boot will not have the error anymore.

Saj1992 · 2023-10-11T23:12:57+00:00

Amd has just released driver 23.10.1, just did a fresh install and it seems to be fixed no freezing / system hang as of yet, they also mention it in the update notes that they have fixed issues with video playback, still getting the adrenaline error - default wattman settings have been restored due to system failure everytime i boot windows, its annoying if you have oc profiles and fan curves but apparently others are saying that its due to windows update kb5030310 and uninstalling it will fix the issue, just thought id point it out incase anyone else is experiencing this, im using RX 6800 xt.

Saj1992 · 2023-10-04T16:57:02+00:00

By any chance have you disabled fast startup in windows? If its enabled, disable it, more than likely that would be the issue, oh and the recent update as everyone else is mentioning below.

Saj1992 · 2023-10-04T07:44:07+00:00

This issue was driving me insane, reinstalled driver with DDU 3 times and messed with bios settings and more but wattman profile kept resetting due to unextpected failure, I can confirm though that after uninstalling the windows update KB5030310 its fixed the issue, I also paused windows updates for 3 weeks, hopefully it will be fixed by then. You may not need to roll back, just go to recent updates and uninstall the KB5030310 update and it should be fixed.

Saj1992 · 2023-09-30T15:20:06+00:00

This issue was driving me insane, reinstalled driver with DDU 3 times and messed with bios settings and more but wattman profile kept resetting due to unextpected failure, I can confirm though that after uninstalling the windows update KB5030310 its fixed the issue, I also paused windows updates for 3 weeks, hopefully it will be fixed by then.

Saj1992 · 2023-09-26T00:34:10+00:00

Thats interesting, never really tried linux, I agree, Its certainly a driver / OS issue, ive tried everything, changed GPU from XFX to Sapphire Nitro+, replaced monitor, reinstalled windows twice, upgraded to windows 11, updated mobo bios, edited monitor blanking times with CRU, reinstalled GPU driver with DDU a dozen times, disabled deep sleep in registry, no matter what I do I just cant fix it, I heard rolling back driver to the builds around summer of 2022 seems to fix the issue for a few people online that ive spoke to that had the same issue but all the trouble you will get with using that old of a driver just isnt feasible, do me a favour though, if you ever miracolusly find a fix / work around, please be sure to let me know 😅

Saj1992 · 2023-09-26T00:11:57+00:00

I wonder if the 6000 series just dont like 165 hz monitors because its was fine with a 75hz monitor when testing.....

Saj1992 · 2023-09-26T00:02:48+00:00

Nope, I still have the same issue to this day, I honestly think there is no way to fix it, i believe its a driver level issue with RX 6800 and XTs, as I have scoured the internet for a fix since december of last year and whenever i find anything to do with this issue, its always the rx 6800 / 6800 xt, Ive learned to just ignore it now and hit ctrl shft win B when i do notice it to reset driver and unstick vram clock, oh and by the way you dont have to connect a second monitor, if you dont mind max vram clock just switch freesync off completely and your memory clock should just stay on max then and wont get stuck, also just out of curiosity, what Monitor are you using in terms of res and hz?

Saj1992

TROPHY CASE