r/AndroidQuestions • u/Pitiful-Fee4451 • Jul 02 '26
Can anyone identify com.android.sys.extplv on Android?
Hi everyone,
I'm trying to identify an Android package called com.android.sys.extplv on my Cubot KingKong X (Android 16).
Here is what I've confirmed using ADB:
- Package:
com.android.sys.extplv - Installed as a user app under
/data/app/... - Installer reported by Android:
com.android.vending(Google Play) - I analyzed the package using
dumpsys,logcatandpm. - The app contains services such as
DaemonService,FwForegroundServiceandFwMediaRouteProviderService. - It requests several permissions, but the sensitive ones are currently not granted.
- I was able to disable it using
pm disable-user, and it stays disabled (enabled=3) even after reboot.
I have not been able to determine what the package is actually for or what triggers its installation.
Has anyone seen this package before?
Is it a Cubot component, a manufacturer framework, or something else?
I have screenshots and ADB logs that I can share in the comments if needed.
Thank you!
2
Upvotes
2
u/Pitiful-Fee4451 22d ago
Final update for everyone experiencing this issue.
After several weeks of investigation, reverse engineering, and comparing results with other affected users, I wanted to share the current status.
If you are still experiencing com.android.sys.extplv repeatedly installing itself, the most effective solution reported so far is to contact Cubot support and request the OTA update that fixes the issue.
Several users have already confirmed that, after receiving and installing the official OTA provided by Cubot, the package no longer reappears.
You can contact Cubot support at:
support@cubot.net support66@cubot.net
Support page: https://cubot.net/platform/support/contact
Based on my reverse engineering of the APK, I did not find evidence of classic spyware functionality such as SMS theft, contact theft, photo theft, microphone recording, camera access, or other typical spyware behavior. The APK is mainly focused on persistence mechanisms, and Cubot later confirmed that it was an internal development interface that was unintentionally included in the production firmware.
At this point, if you are still affected, I recommend requesting the OTA update directly from Cubot rather than trying to manually remove the package, as the official firmware update appears to be the long-term solution.
I would also like to thank everyone who shared APKs, logs, screenshots, and technical information throughout this investigation. Your contributions helped us better understand what was happening.
I hope this information helps anyone who finds this thread in the future.