> I will write results here. I think it will be interesting for someone.
So, this is the result:
1. We've made "Market-like" architecture: "Installer" and "Updater".
2. "Installer" has system permissions to install packages and reboot
device. It does only one work - installing prepared package an
> You will still want to find out what happens when you attempt an update
> while the application is running.
There are internal detailed logging in app. Every step will be written
in file.
Kostya, big-big thanks for so detailed answer. I think that dialog
with vendor is better way in this situat
> How about "adb install -r" over adb/WiFi? I understand it requires
> rooting, but that's a hell of a lot easier than creating a custom
> firmware build.
Thank you very much! We'll try this. In another words there two ways:
1. Get root permissions. And than "adb install -r".
2. Ask vendor create
> There's a user interaction required. Installing an APK is done by
> means of an activity, requiring user interaction.
Exactly! And this is the problem. We've trying to find solution...
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To p
4 matches
Mail list logo
