Skip to content

Lollipop support#1

Open
nuclearmistake wants to merge 2 commits intoGSamLabs:masterfrom
VanirAOSP:lollipop-support
Open

Lollipop support#1
nuclearmistake wants to merge 2 commits intoGSamLabs:masterfrom
VanirAOSP:lollipop-support

Conversation

@nuclearmistake
Copy link

Works when compiled inline with AOSP 5.1.1 directly to /system/priv-app/GSamBatteryMonitor-RootHelper/GSamBatteryMonitor-RootHelper.apk, but I haven't verified its ability to transplant itself to that location conditionally when initially installed as a non-privileged data app

The second commit is just renaming things to avoid an ambiguous "/system/priv-app/companion/rootcompanion.apk" destination for lollipop+ pathing, and is probably not "necessary".

On Lollipop, the path to the Settings app is /system/priv-app/Settings/Settings.apk
This commit copies the data APK to a similarly-named path on devices with their ro.build.version.release's X.Y[.Z] version number's X
     greater than or equal to 5 (lollipop and up).
This is build property MAY not exist or have values of the nature assumed by this commit for all OEMs, but this definitely covers
     AOSP and popular open source derivatives there-of.

The backup script's list-files function now has BOTH possible priv-app paths listed.
This works because backup_file and restore_file no-op in the case that a file does not exist.
…ic+appropriate (so the lollipop path isn't /system/priv-app/roothelper/roothelper.apk)

And remove spaces to prevent issues when compiling inline with AOSP
@nuclearmistake
Copy link
Author

Prolly worth testing on lollipop when compiled traditionally before merging... I've been testing with this compiled directly to /system/priv-app inline with a lollipop ota zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant