APK Cloner #26
Replies: 4 comments 3 replies
|
I already done this on my private repo. I will merge it soon after advanced features are completed |
|
Now since apkeditor uses smali, will this feature be extended to smali classes? (in a way its easier because you dont need to pay attention what start with ., if you will anyway change all classes to match package) |
|
Any updates on this? |
|
Notes:
Factors challenging for renaming package:
Plans/Progress:
FYI: I've experimented and gave up AI assisted package renaming with GPT-4o, by creating string chat interface. Ignoring heavy token usage, this resulting worst to none and i don't know if better result could be achieved with custom trained data or model. |
Uh oh!
There was an error while loading. Please reload this page.
The user should specify the new package name and it should modify the APK to have the new package name. Maybe it should have a default value which is to update the last character by one (for example, com.example would become com.examplf).
This is confusing and requires correct logic. The java classes will stay the same, so activity names cant be modified. and any activity, service, receiver etc that begins with a
.in the manifest will need to be edited to include the original package name, because those classes wont exist anymore once the package name is changed.This can be useful for installing multiple versions of an app on your phone or for changing the package name in general (I can list a few use cases if you want).
All reactions