Device|Bloat B' Gone about raccoon4 HOT 3 OPEN

Vendor bloat might be difficult to handle simply because there's so much of it out there. Individual models from the same vendor can have 2 or 3 sets of completely different packages, some vendors integrate their bloat into the System UI, and so on. You'd have to find which device model + firmware version you're working with and provide the bloatware list for that specific combination (you could probably share lists between devices in the same "generation"), but that'd be Sisyphean work.

A solid alternative would be to provide a list of all system packages and hide the ones known not to be bloatware or essential for Android/Google Play Services to work properly, then let the user pick what he wants to disable, with a large warning that this might break his device and that a factory reset might be required if something goes wrong. (Full ADB backups would be useful to help the less cautious users there, but that's probably stretching the definition of Raccoon as a "package manager" of sorts.)

from raccoon4.

hm ... I had this (probably) naive idea of simply querying the packagemanager via ADB to list all system apps. Then check those packagenames against a list of known bloatware apps.

from raccoon4.

This would be okay, just that having a reliable list of known bloatware isn't "just", but is rather complicated.

from raccoon4.