If we were able to fence off the offending code paths, and only open them if we detect we're in a system app location, then we could use traditional distribution channels and install methods (F-Droid, Play Store, etc).
That way, we can simply instruct users to use the SystemAppMover to promote it to system. This would still require root, but wouldn't require intimidating adb usage.
It should also be noted that VoicePlus is normally present in /system/app in stock CM, which is a less privileged location, unlike true system apps in /system/priv-app. SystemAppMover currently only moved things in and out of the former. It shouldn't hurt, but it is a more privileged location, and so it increases the attack surface of the device. (Details here)
Currently, trying to install VoicePlus via
adb installresults in:If we were able to fence off the offending code paths, and only open them if we detect we're in a system app location, then we could use traditional distribution channels and install methods (F-Droid, Play Store, etc).
That way, we can simply instruct users to use the SystemAppMover to promote it to system. This would still require root, but wouldn't require intimidating
adbusage.It should also be noted that VoicePlus is normally present in
/system/appin stock CM, which is a less privileged location, unlike true system apps in/system/priv-app. SystemAppMover currently only moved things in and out of the former. It shouldn't hurt, but it is a more privileged location, and so it increases the attack surface of the device. (Details here)This might be something to get into the official CM package.