Intermittent problem: Kodi not coming out of screensaver dimming

sstroughair · 27 November 2025 08:48

I’ve recently experienced a problem with my Vero V running Arctic Fuse 2 skin (if that’s relevant): after a period of time my screen dims as per the screensaver setting, but occasionally it won’t return to proper brightness at all and I need to reboot to fix. I can navigate around, play videos, all the usual stuff, it’s just the screen stays dim.

It’s intermittent, seemingly random, and I can’t reproduce it at will. As such I don’t have a log to paste, at least not yet.

Anyone got any ideas? I haven’t seen this before.

JimKnopf · 27 November 2025 08:50

Hi, first question: Does it also stay dimmed, if you use the skins ‘OSMC skin’ and/or ‘Estuary’?

sstroughair · 27 November 2025 09:18

Fair question, and the short answer is I don’t know. It’s so intermittent I could go a week or more without it happening, so I haven’t tried different skins. I guess I should at least try that and see.

I appreciate I’m not giving you much to work with here!

pameijer · 28 November 2025 07:48

Ik have the same problem with my Ugoos with CoreElec, and sometimes with my Vero V. So probably a Kodi-issue, not specific Vero. Reboot always helps, have not found any other way to stop the dimming, starting a movie doesn’t help either.

sstroughair · 28 November 2025 08:51

May I ask what skin you’re using, pameijer?

pameijer · 28 November 2025 09:51

I use Aeon Nox on both devices.

cojms1 · 29 November 2025 19:24

I also use Arctic Fuse 2 and have experienced this. There’s an issue for it which points to it being an issue in Kodi.

github.com/jurialmunkey/skin.arctic.fuse.2

:bug: Kodi screensaver fails to wake when skin updates

opened 05:03PM - 20 Oct 25 UTC

closed 12:01AM - 01 Nov 25 UTC

ryanfelder

bug

### Skin section Other ### Current Behavior Sometimes the screensaver fails t…o activate. Interacting with Kodi appears to behave as expected. This interaction clears whatever issue caused the screensaver to fail to activate. The next time the screensaver activates, it cannot be woken up. The only solution at this point is to restart Kodi. ### Expected Behavior Screensaver should reliably activate and deactivate. ### Steps To Reproduce I do not have clear steps to reproduce this, it is intermittent. I know it's about to happen when I come downstairs to find the screensaver has _not_ activated. I know at that point that if I use my kodi box, the next time the screensaver activates it will be permanent. ### Screenshots and Additional Info I have experienced this across multiple versions of kodi over the years with Arctic Fuse 2 and Arctic Horizon 2. This behavior is the same on both Windows and Linux (LibreElec) This behavior does not occur when using the Estuary skin, but always comes back when I use Arctic Horizon 2 or Arctic Fuse 2. This seems to have been previously reported here : https://github.com/jurialmunkey/skin.arctic.fuse.2/issues/396 but I wanted to add my experience that this does not occur with the default skin. It has been affecting me for a looong time and it always forces me back to Estuary. Then, a few months later I forget and try one of your skins again, get it all setup, and I'm very happy until the screensaver doesn't wake and I remember why I had to go back to Estuary in the first place. ### Checklist - [x] I have made a separate issue for each bug that I am reporting. - [x] I have searched the issues and this bug has not been reported. - [x] I am using the most recent skin version. - [x] I have confirmed that this bug does not occur in the default skin.

I have worked around it by disabling automatic updates to the skin. Since doing this, I haven’t seen the issue and can update the skin when I want to.

sstroughair · 30 November 2025 09:01

Excellent find, thank you so much!

sstroughair · 30 November 2025 17:32

It’s just happened again, and I can see in the log that the skin seemed to load/reload a couple of hours ago. If it’s useful for me to share that log I can do so, but I’m not sure what the rules are here about logs that refer to illegal add-ons…

Either way, this seems to corroborate the suggestion above.

SundayDiver · 2 December 2025 02:01

Has happened fairly often on my vero v too using standard skin. Always just reboot to get normal brightness back.