Do we really need F‑Droid always running on NSPanel Pro?

NSPanel Pro now includes F‑Droid and its privileged update service, which run in the background and consume system resources. While some users may want to install apps, many NSPanel Pro users never use F‑Droid, so having it always active seems unnecessary.

From what I can see, F‑Droid is not required for MQTT, Cube, or Home Assistant integration, so it adds overhead without benefit for most users.

F‑Droid (with the Privileged Extension) performs background update checks without user consent. On standard Android devices this is normal, but on NSPanel Pro it raises questions about its fit within the eWeLink architecture. The service can only update apps installed via F‑Droid, yet it still runs, wakes the system, and uses resources even if no apps are ever installed.

Since NSPanel Pro is designed as a dedicated automation device with its own eWeLink UI layer, it’s unclear why a background app-store service needs to run constantly, especially for users who do not rely on external apps.

Is there a plan to add an option to disable F‑Droid and its background services? A simple toggle in the settings would help users maintain a lighter and more predictable system.

3 Likes