Quote:
Originally Posted by odamizu
Thanks for this intriguing list (which I understand pretty much not at all  ). However ...
Is it safe to use ;chkup if you do want to update your Kindle but are too lazy to download the update and transfer it manually, and too impatient to wait for Amazon to push it to your Kindle automatically? |
It seems to be.
My AP has blinking lights to indicate use and uses WAP2 to be certain I am the only one using it.
So I feel I can trust the lights to indicate my KT3 (5.8.5).
I am also using ;dm plus transferring over USB the four message logs produced (to where I have a larger screen).
I have a couple of potential update blockers that I am testing.
So far:
*) Blockers in place.
*) Put online
*) KT3 tried (and failed) to do a silent OTA update.
*) Wait a week (there is a time delay between schedule retries).
*) Put online
*) Nothing - logs show delay was checked but I didn't have it on-line long enough for it to get organized.
*) Wait a few days
*) Put online
*) Nothing, not even had the delay checked
*) Offline
*) Enter: ;chkup
*) logs confirmed an update check was scheduled with the todo handler
*) Wait a few days
*) Online
*) Lights show more than usual activity
*) Offline
*) One of the OTA blockers being tested had been cleaned up (not all of them).
*) Logs show that an update check had been made and a download started.
And that the download had been interrupted by a Wifi disconnect (me).
So that seems to indicate to me that in the case of a device that requires an update, the ;ckup is working as described in the scripting.
Other cases not yet tested, but the scripting does seem to be written to safely handle other cases.
Such as:
;ckup on a device with same or newer than posted by Amazon firmware.
Various other failure path combinations.
= = = = =
I really don't want 5.8.8 on any of my devices, so testing this is not one of my top todo things.
But sure, give it a try, keep good notes, keep the logs and let me know what happens as an end result.