View Single Post
Old 11-17-2019, 08:29 PM   #674
galneon
Member
galneon began at the beginning.
 
Posts: 10
Karma: 10
Join Date: Jul 2014
Device: KV
I updated my jailbroken Voyage to 5.12.0 (or something late in the 5.11.x series) before it was known, or widely known, that the usual method of blocking updates had been deprecated. Several weeks later, I was automatically updated to 5.12.1 to my surprise. The hotfix worked and I'm still jailbroken, but my Voyage never leaves airplane mode now and I miss Wikipedia lookups a bit. :/

I apologize if I've overlooked something here, but is there a new method for blocking updates yet? I've read of the speculative less than 200 MB free fix, but this is less than appealing for a few reasons. I'm used to blocking updates in hosts at the router level for gaming consoles and other things I don't want updating themselves, but I'm concerned the Kindle might not bother with hostname resolution and connects directly to a specific IP. That's not a very practical method for most auto-updaters, but a corporation the size of Amazon can hold a static as long as it wants... I'm not willing to risk my jailbreak as the screen savers plugin is a must for me--the Amazon screensavers are revolting. None of those images translate well to eink. For me, it's cover mode or another brand of reader.

Last edited by galneon; 11-17-2019 at 08:34 PM.
galneon is offline   Reply With Quote