-
All replies
-
Helpful answers
-
May 11, 2016 3:00 AM in response to davecwby android351,The way I stop the downloads from happening is to put my iPad in flight mode before charging. The downloads won't happen then. This is the only practical way I know of to prevent unauthorized download of point release iOS updates. Still a pain, because sometimes I forget to put it in flight mode and I must then delete the update manually.
The principle annoys me more than anything. It's my device, and my bandwidth. Apple should not be sneaking behind my back with 300+ MB downloads in the background when I have auto-updates disabled.
-
Sep 8, 2016 5:54 AM in response to android351by Oregonuser,A SOLUTION:
Apple's daily iOS update reminders nagging device owners to update *their* devices to the latest iOS iteration, as evidenced by the postings on this site, have more than a few users frustrated with Apple's apparent "nanny" sandbox approach to mobile computing. This post is to share a problem specific solution that I have successfully applied for about a month now following a lot of reading through many posts (found at the "How To" channel on YouTube (link is in the next paragraph). It is titled: " How to stop your iphone ask for update "
Here's a link to the two minute instructional YT video fix:
( https://www.youtube.com/watch?v=Kw-7heNMtSQ )
which presents a *working* (so far) step-by-step, simple, and easily reversable solution for blocking both the big A's intrusive automatic downloads of their "wonderful" new iOS updates onto *my* device and also blocking their daily dunning nag notification to install it.
It's worth noting that this fix has a downside but for me it's not a significant problem: One of the steps requires enabling adult restriction mode in device settings and that will spur the ongoing need to *one-time* authorize various sites you may visit via mobile Safari that are on the big A's master list of restricted sites.
If readers of my post are interested, I suggest you invest the two minutes to watch the video. I will try to update this post if it turns out to only have been a temporary workaround but for now, I am optimistic.