@DeathMaskSalesman What I miss in the README.md is the section "Requirements & Installation". The description currently sounds as if one should install it on the Android device (with the files then being placed there as well). That would require Python being installed there as well. Doubt that's what you meant :)

Oops confused Checking inside the scripts, it seems indeed to be intended for on-device use (config["aapt"] = "/system/bin/aapt"). That means it requires Python to be available on the device.

Aha, and: print("[ F ] Neither aapt nor aopt is installed. Aborting.") So more requirements. That might frustrate users if they find everything bit-by-bit – up to the point of "had I known before I hadn't wasted my time" and giving up …

I already skip it, as for me TiBu cares for that, and resulting APKs get synced to my computer automatically. Plus, if I need a manual run, I've got my Adebar. So I don't have to figure how to get Python unto my device, etc.pp. #D

But that's me. Looks like a useful thing to those having Python on their devices, thumbs up!

@Izzy It's more like a project I wrote for myself, rather than a serious thing, mind you. #D

Anyways, I'll review the README and update the requirements as per your suggestion. Thanks!

@DeathMaskSalesman That's how most of my projects started – including Adebar :D

@DeathMaskSalesman Cool, and you're welcome! Sorry that I cannot go into depths. Too many other things to do.

@Izzy Don't sweat it. By the way, I just added a workaround for apps with the same label.

Updated.