With
5.7.3 in the wings, I decided to end my update.bin.tmp.partial experiment since I want to install 5.7.2.1 and have update.bin.tmp.partial loaded against 5.7.3.
Details of my experiment:
- In September 2015, I put an empty folder named "update.bin.tmp.partial" in the root directory of my Kindle Voyage 5.6.5.
- When 5.7.2 was released around 2/2/2016, I turned WiFi on and left it on 24/7. I received no forced update, however, some reports suggest that 5.7.2 wasn't pushed out to all Kindles OTA, but was more of a limited test run.
- 5.7.2.1 was released around 2/12/2016. I continued to leave WiFi on 24/7. In addition, I plugged my KV into a/c for 24-48 hours on more than one occasion to see if it would trigger an OTA update. Nope.
- Today, 3/6/2016, I deleted the update.bin.tmp.partial folder then went to get a snack. When I returned 10 minutes later, I was surprised to see my KV already auto-updating to 5.7.2.1. Was it a coincidence that Amazon chose to push the update to my KV less than 10 minutes after I deleted update.bin.tmp.partial?
- However, I have a friend who also had update.bin.tmp.partial on her KV, and nothing happened after she deleted it, so she updated to 5.7.2.1 manually.
- I now have update.bin.tmp.partial back on my KV 5.7.2.1. The folder survives re-boot. We'll see what happens when 5.7.3 rolls out.