You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have since some times now an issue where my rpi5 fan would spin at 50% (loud noise) instead of 25% (no noise) every 5 or 10 minutes. Initially I thought it was related to the PVR Freebox extension which updates its guide every 5 minutes, but it's not, disabling it still has the issue.
I noticed my fan spinning fast because the RPI reached 60-62° when idling which is weird because to be honest the skin is so simple nobody can imagine that. Then I tested other skins, like the default estuary where the issue disappeared and reached a steady 54-55° when idling and no more issues.
I can't imagine a so simple skin needing so much CPU just to change every 30 secs a background image. Would you mind having a look at this issue?
As of now I returned to estuary because of the permanent noise it triggers, which is very annoying - your skin being so much good!
The text was updated successfully, but these errors were encountered:
I have since some times now an issue where my rpi5 fan would spin at 50% (loud noise) instead of 25% (no noise) every 5 or 10 minutes. Initially I thought it was related to the PVR Freebox extension which updates its guide every 5 minutes, but it's not, disabling it still has the issue.
I noticed my fan spinning fast because the RPI reached 60-62° when idling which is weird because to be honest the skin is so simple nobody can imagine that. Then I tested other skins, like the default estuary where the issue disappeared and reached a steady 54-55° when idling and no more issues.
I can't imagine a so simple skin needing so much CPU just to change every 30 secs a background image. Would you mind having a look at this issue?
As of now I returned to estuary because of the permanent noise it triggers, which is very annoying - your skin being so much good!
The text was updated successfully, but these errors were encountered: