nguyenhoangs0n / auto-update-apk-client

Automatically exported from code.google.com/p/auto-update-apk-client
0 stars 0 forks source link

silent update mode #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
push link (https://www.push-link.com/index.html) has a "ninja" mode where 
rooted devices can be updated silently... this would be really handy for our 
clients.

Original issue reported on code.google.com by d...@codesushi.com on 11 May 2012 at 9:11

GoogleCodeExporter commented 9 years ago
Rooted devices, obviously

Original comment by d...@codesushi.com on 11 May 2012 at 9:11

GoogleCodeExporter commented 9 years ago
oh nice, sweet.  my clients are all rooted as well.

Original comment by bric...@gmail.com on 12 May 2012 at 12:48

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
Rooted devices cannot be updated "silently", but instead of "Click for Update" 
your users will get scary "Application requires SUPERUSER access: Allow / Deny" 
message box, and there's no way to avoid that.

Personally, I don't see any point why enterprise clients would use rooted 
devices, but I may be wrong and if this issue gets enough stars, it will be 
implemented someday.

Original comment by lenik.terenin on 12 May 2012 at 10:43

GoogleCodeExporter commented 9 years ago
Thank you for considering adding this in the future. For your knowledge, here 
are some reasons my users are rooted.

1. Remote access to the device - with the device rooted, i can troubleshoot 
remotely by using webkey to connect to the device directly.
2. Backups - allows me to take advantage of full backup features on apps like 
my backup pro, so the backups include ALL data. This make my life a lot easier 
when restoring to a new device.
3. Scripts - i can run any script i need.in my case it removed bloatware to 
increase battery life for my users

Also, the scary "application requires SUPERUSER access: Allow / Deny" would 
only come up ONE time. Then moving forward your app is automatically granted 
superuser permissions.

Original comment by bric...@gmail.com on 12 May 2012 at 11:37

GoogleCodeExporter commented 9 years ago
We have devices deployed at retail outlets in a "kiosk" mode (i.e. they only 
run our app) in off hours we would like to be able to push out updates to all 
(or specific) retail locations without user interaction.

Original comment by d...@codesushi.com on 14 May 2012 at 3:17

GoogleCodeExporter commented 9 years ago
@brico84: "application requires SUPERUSER access" comes once, but the Toast 
"application was granted superuser access" shows every time and looks like 
there's no way to get rid of it.

Anyway, SilentAutoUpdate is released. Basically a drop-in replacement for 
AutoUpdateApk -- just change the name to SilentAutoUpdate and don't forget to 
include the .java file. You may also change it back at any time.

If device is not rooted or any other problem occurs (uncooperative user denies 
SU request?), updater automatically fallbacks to Notification mode.

Please, try and report if something strange happens.

Original comment by lenik.terenin on 15 May 2012 at 7:36

GoogleCodeExporter commented 9 years ago
Thanks for the fix.  I am gonna try it out.

The "Application was granted superuser access" is controlled via the superuser 
application installed once a device is rooted.  You simply open that 
application and go to settings, notifications, and disable them (which is what 
I do for my users so they don't see that message EVER).

Thanks again, very excited to try this!

Original comment by bric...@gmail.com on 15 May 2012 at 11:13

GoogleCodeExporter commented 9 years ago
I am happy to report it works as expected! great job and thanks again!

Original comment by bric...@gmail.com on 15 May 2012 at 12:54

GoogleCodeExporter commented 9 years ago
This works great for me! FWIW, On our tablet the user was not asked for super 
user access... thanks!

Original comment by d...@codesushi.com on 15 May 2012 at 3:50

GoogleCodeExporter commented 9 years ago
Thanks, everybody, I'm closing this issue. If something happens, please open a 
new one.

Original comment by lenik.terenin on 15 May 2012 at 9:56