Also to IL mac and janels1
This would be one heckuva desk check. :-) (Task of checking program logic.)
AS far as the update method goes, I can only repeat in case Apple finds a pattern. I have put in hours trying to build a base. Someone else is just as good as I am with Google with respect to looking for others with technical troubleshooting skills that might have investigated and tested as Ben Collier and his connections did.
If you want to provide usable info for Apple to mine, be very specific, so that the senior level of support can justify the programming hours they will have to allocate. (I know being specific is hard - we are all tired and exasperated.)
So far the only halfway clear and plausible explanation for the hyperlink-related issues is Ben Collier and company's exploration.
To explore the question about upgrade modes well enough to get somebody's attention at Apple we would have to be able to poll with spedific questions and get a graphical readout. If someone would like to brainstorm a draft set of questions for refinement, that would be a start. Perhaps someone else would be willing to trasnform that into a poll at a free service and provide the link to it here.
email/Safari links are *only one issue*. --- Have you gone to the Wikipedia iOS link? Wikipedia only lists an issue of interest for gamers - nothing about links or bricking or ICloud logins (I noticed that in passing when I was trying to answer the question about what the latest build is).
There are at least 20 issues that one party noted, based on a casual Google search:
- an ugly, aggressively popup-ridden site on Chrome - approach with care:
- another site to approach with care and updated anti-virus, and maybe only just scan the list of reported issues and close the window fast:
Meanwhile, Apple is probably still churned up by the pressure from various sources regarding the alleged terrorist's locked phone.
9.3 released on 21 March as far as I understand at this point.." All I am not sure when the various versions were released. Pehaps someone would like to search for an answer. I have a preliminary one, but can't take time to try and find corroboration. I'll try to wind that up, but don't wait on me...I am pretty convinced that only Apple can provide a "real fix."
Our notes here possibly give them a clue why they should spend $ on a fix. Somebody can take a page from me and go though these pages for where people have shared how much time wasted - another category of information for Apple to consider. You will have to make a case that beats the economic impact on gamers, so start with some demographics about iDevice users and uses.
My two cents: To paraphrase, and repeat: they also serve who only weigh in and say, "me, too." But if you were an Apple manager and had to exercise, as IL mac says, "good judgement" about what bugs to risk leaving in, how does "me, too" quantify that risk, beyond a very ballpark number scattered amongst various 'discussion' threads? "Me, too" with a specific device is better. A reproducible set of issues is better still. $$ lost and time lost is even better. One of the Forbes columnists screenshot what is probably a TweetDeck view of Twitter complaints. Comments here quantified the time spent on hold, or at the Genius Bar. Or politely Tweet a picture of yourself as you are at the electronic recycler, making good on your promise to ditch your iDevice.
Experience so far taught me that it's dollars that matter, and the pace of change. People stopped replacing their laptops and bought into smaller devices - several sometimes. Fewer laptops sold overall, plus advances in touch and voice recognition, plus security issues made HP decide that other than compensating people who watched like hawks for an opportunity to recoup some loss on the TX2, It was better to just build a similar package. Lessons learned from the TX-2 made the TM2 much better, but HP did not support all the driver updates necessary for Windows 8 to leave the TM2 fully functional, even in compatibility mode. Technology had marched on. But users' outcry did probably convince Microsoft to keep Windows 7 functional, so I still have my Tm2.
The update method? I don't know. To me, so many say that it goes well and works and then fails. To reiterate how I updated...I held off on 9.2.1 or 9.2 because I read that some who update automatically OTA (over the air) had issues with a corrupt download. I tried to follow that with 9.3, but was concerned about the mounting number of app updates I was seeing. With an update as big as 9.3 and networks as chaotic as they are it is probably safer to eliminate as much wireless as possible as a general rule. And make things go as smoothly as possible. As i said elsewhere, I told iTunes to download, but not then automatically update, the iPhone 6S. I used an account with admin privileges. On an AC adapter on a calm day so power would not be interrupted. I used a wireless connection from the laptop - I would use a wired connection to the modem instead next time. I paused the download with the provided button several times because I kept thinking of things that were probably in need of updates that should precede the iOS update. Next time I will avoid that if possible, and brainstorm things that should be updated first. I cabled my iDevice to the computer, and babysat the computer while the download went on, watching for signs of interruptions, or error messages. There were none. So then I told iTunes to update the device. I babysat that. No apparent issues, and the Assistant ran. The only hitch was that I got the alert popup about signing in to iCloud. I passed on that with the button provided. There were no indications of any hitches. This may seem pretty specific, but I am not using the precise Apple terminology, so whether Apple can use this as input is not 100%. That's how hard and painstaking fixing this is.
Same story for many - everything seems fine, then something starts failing. It's as though there is an interaction or a memory issue from a failure to release memory when it is no longer needed (assuming Objective C requires that as C does). r huge link files and the daemon that chokes on them sounds pretty plausible to me, but I only studied coding in an effort to be able to have a feel for factors that affect projects that include development - I wouldn't presume to call myself a programmer.
The really strange thing is that while I did the update on the 25th or 26th, I wound up with what Wikipedia's iOS table authors listed as the first (...233) build. By then I would think I would have had a later numbered build, unless the builds are for different classes of iDevices. That picture is confusing at the moment, because what I found leads me to believe that the updater may not have correctly detected the build that "fit" my device - but that may be an honest journalistic error.. Someone else can pursue that good question and see what they find.
For now, I absolutely have real life chores to do. 🙂
<Link Edited by Host>
