Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

iOS 9.0.2

anyone else having issues with iOS 9.0.2? iOS 9.0.0 and 9.0.1 weren't too bad but now 9.0.2 is terrible.


autorotation issues, website search result issues, devices locking up and running slow.


this is terrible! What happened to apples iOS quality control. So disappointe!

iOS 9.0.2

Posted on Oct 2, 2015 2:22 PM

Reply
Question marked as Best reply

Posted on Oct 2, 2015 2:33 PM

you arr not alone Terrible upgrade

72 replies

Oct 12, 2015 3:15 PM in response to LoraxTN

I Was having problems with Safari running slowly and crshing after updating to iOS 9.0.2. I went to Settings. Then on the settings page scrolled down untill I found the listing for Safari. I selected Safari and the turned off Safari suggestions and Search engine suggestions and this seems to have helped with the crashing and freezing, although loading oages is still slower than in iOS 8. I wonder after spending all the money upgrading to iPad Air 2 because it was faster, if it was a waste--iOS 9 seems to have slowed my super machine down quite a bit.

Oct 12, 2015 3:22 PM in response to LoraxTN

iOS devices are computers. You know how both Windows and Macintosh computers seem to run like a champ after you reinstall the operating system? The same is true for iOS devices. Perform a backup of your device and then do a factory reset. Restore that backup and you'll be off and running. I understand that you are having issues with the operating system and can completely see where you're coming from. You install an update and it should make your device run better! Sometimes that isn't the case. I'm sure the Apple engineers are working hard to resolve issues with the software. In the meantime simple troubleshooting steps can help fix these problems! If you are having issues with a specific application remove it from your device and then reinstall it 🙂 Stuff like this helps!

Oct 12, 2015 4:29 PM in response to petermac87

So let me get this straight. If I buy a car, then they do a recall to install some new part ... then the car doesn't work, keeps stalling, stops suddenly, basically undriveable I should just park it and accept that this is just my bad luck. Or as you suggest, just get my hands dirty ... what could go wrong?! Are you frikkin' kidding me!?


Get over yourself! Oooh, you're a tech-God and we should all bow down to your superior knowledge. I guess everyone should be their own Doctor, Mechanic, Computer Programmer, Pilot ... you can't expect someone who is a Doctor to do the Doctoring, Mechanics to deal with mechanical issues, etc.


This is their product. I've heard of this problem from a few dozen I know personally ... not jail-broken, not modded, just straight from their provider. Telling everyone who's been affected by this crappy patch to just suck it up ... or a big list of possible fixes when most users have no technological expertise at all ... Gee, do you think that might be more risky than Apple simply putting out a better-tested product?


My phone like so many others with this patch went from Functional to Frustrating, from something to rely upon to something you have to work around.

Oct 12, 2015 4:41 PM in response to TTakeda

TTakeda wrote:


So let me get this straight. If I buy a car, then they do a recall to install some new part ... then the car doesn't work, keeps stalling, stops suddenly, basically undriveable I should just park it and accept that this is just my bad luck. Or as you suggest, just get my hands dirty ... what could go wrong?! Are you frikkin' kidding me!?


Get over yourself! Oooh, you're a tech-God and we should all bow down to your superior knowledge. I guess everyone should be their own Doctor, Mechanic, Computer Programmer, Pilot ... you can't expect someone who is a Doctor to do the Doctoring, Mechanics to deal with mechanical issues, etc.


This is their product. I've heard of this problem from a few dozen I know personally ... not jail-broken, not modded, just straight from their provider. Telling everyone who's been affected by this crappy patch to just suck it up ... or a big list of possible fixes when most users have no technological expertise at all ... Gee, do you think that might be more risky than Apple simply putting out a better-tested product?


My phone like so many others with this patch went from Functional to Frustrating, from something to rely upon to something you have to work around.

And yet you cannot supply a single link to back up your rant?


Thought not. I think we know who the troll is. 😉


Pete

Oct 13, 2015 5:47 AM in response to LoraxTN

problems with iPad 2 following iOS 9.0.2 are driving me crazy!!. My battery is draining quickly, the keyboard is very slow, Safari keeps freezing for about a minute, the page keeps reloading on every website,,. hElp-any solutions. Have tried rebooting several times with no success. Not good at internet speak so if you have any suggestions please keep it simple. Many thanks

Oct 13, 2015 12:39 PM in response to Cavcat

Just tried to activate iMessage. Waited a minute or two. Still waiting. Seems to never finish. Just finished with error message "iMessage activation failed. Could not contact iMessage server. Try again"


SImilar experience with FaceTime as with iMessage. "Could not contact FaceTime server. Try again"


Switching from item to item in Settings is very delayed.

AppStore indicates I have 8 updates but when I open it the list of 8 apps all say "open" and cannot update. "Update all" is grayed.

Response is generally slow but is a bit faster than before.


now I am getting error when trying to save this comment.

Oct 15, 2015 1:51 PM in response to LoraxTN

I can watch my battery drain itself and below is the reason why. The tcpdump below shows that even while my iPhone is in "Low Power Mode" it is constantly communicating with Apple servers. In addition to being set to Low Power Mode, the phone is also logged out of iCloud and iTunes and Push settings have been disabled for email. Theoretically, the phone should show very limited network communication but instead, the network traffic is constant and the phone is hot to the touch. I've performed a "Home + Power" hard reset a number of times while watching the tcpdump output. Every time the phone reboots, it starts communicating with Apple's servers like mad...


20:49:29.786927 IP (tos 0x0, ttl 64, id 25941, offset 0, flags [none], proto UDP (17), length 44) 192.168.100.20.16403 > 17.155.127.222.16384: UDP, length 16

20:49:29.788165 IP (tos 0x0, ttl 64, id 49647, offset 0, flags [none], proto UDP (17), length 44) 192.168.100.20.16403 > 17.155.127.222.16385: UDP, length 16

20:49:29.788281 IP (tos 0x0, ttl 64, id 21506, offset 0, flags [none], proto UDP (17), length 44) 192.168.100.20.16403 > 17.155.127.223.16386: UDP, length 16

20:49:29.842063 IP (tos 0x0, ttl 55, id 0, offset 65376, flags [+], proto UDP (17), length 44, bad cksum 8d8b (->8d9f)!) 17.155.127.222 > 192.168.100.20: udp

20:49:29.844403 IP (tos 0x0, ttl 55, id 0, offset 65376, flags [+], proto UDP (17), length 44, bad cksum 8d8b (->8d9f)!) 17.155.127.222 > 192.168.100.20: udp

20:49:29.846038 IP (tos 0x0, ttl 54, id 0, offset 65376, flags [+], proto UDP (17), length 44, bad cksum 8e8a (->8e9e)!) 17.155.127.223 > 192.168.100.20: udp

20:49:30.555692 IP (tos 0x0, ttl 255, id 4133, offset 0, flags [none], proto UDP (17), length 63) 192.168.100.20.54982 > 192.168.100.1.53: 39600+ A? guzzoni.apple.com. (35)

20:49:30.568555 IP (tos 0x0, ttl 255, id 54590, offset 0, flags [none], proto UDP (17), length 55) 192.168.100.20.51639 > 192.168.100.1.53: 29501+ A? apple.com. (27)

20:49:30.570306 IP (tos 0x0, ttl 64, id 49601, offset 0, flags [none], proto UDP (17), length 408) 192.168.100.1.53 > 192.168.100.20.51639: 29501 3/8/8 apple.com. A 17.172.224.47, apple.com.[|domain]

20:49:30.591307 IP (tos 0x0, ttl 64, id 49602, offset 0, flags [none], proto UDP (17), length 456) 192.168.100.1.53 > 192.168.100.20.54982: 39600 3/10/5 guzzoni.apple.com. CNAME[|domain]

20:49:30.848066 IP (tos 0x0, ttl 64, id 54468, offset 0, flags [none], proto UDP (17), length 44) 192.168.100.20.16403 > 17.155.127.222.16384: UDP, length 16

20:49:30.848182 IP (tos 0x0, ttl 64, id 843, offset 0, flags [none], proto UDP (17), length 44) 192.168.100.20.16403 > 17.155.127.222.16385: UDP, length 16

20:49:30.848247 IP (tos 0x0, ttl 64, id 25580, offset 0, flags [none], proto UDP (17), length 44) 192.168.100.20.16403 > 17.155.127.223.16386: UDP, length 16

20:49:30.903435 IP (tos 0x0, ttl 55, id 0, offset 65376, flags [+], proto UDP (17), length 44, bad cksum 8d8b (->8d9f)!) 17.155.127.222 > 192.168.100.20: udp

20:49:30.906281 IP (tos 0x0, ttl 54, id 0, offset 65376, flags [+], proto UDP (17), length 44, bad cksum 8e8a (->8e9e)!) 17.155.127.223 > 192.168.100.20: udp

20:49:30.906409 IP (tos 0x0, ttl 55, id 0, offset 65376, flags [+], proto UDP (17), length 44, bad cksum 8d8b (->8d9f)!) 17.155.127.222 > 192.168.100.20: udp

20:49:31.467613 IP (tos 0x0, ttl 255, id 11990, offset 0, flags [none], proto UDP (17), length 142) 192.168.100.20.5353 > 224.0.0.251.5353: 0 [1au][|domain]

20:49:31.946829 IP (tos 0x0, ttl 64, id 25045, offset 0, flags [none], proto UDP (17), length 44) 192.168.100.20.16403 > 17.155.127.222.16384: UDP, length 16

20:49:31.947256 IP (tos 0x0, ttl 64, id 47153, offset 0, flags [none], proto UDP (17), length 44) 192.168.100.20.16403 > 17.155.127.222.16385: UDP, length 16

20:49:31.947379 IP (tos 0x0, ttl 64, id 28130, offset 0, flags [none], proto UDP (17), length 44) 192.168.100.20.16403 > 17.155.127.223.16386: UDP, length 16

20:49:32.001999 IP (tos 0x0, ttl 55, id 0, offset 65376, flags [+], proto UDP (17), length 44, bad cksum 8d8b (->8d9f)!) 17.155.127.222 > 192.168.100.20: udp

20:49:32.003186 IP (tos 0x0, ttl 54, id 0, offset 65376, flags [+], proto UDP (17), length 44, bad cksum 8e8a (->8e9e)!) 17.155.127.223 > 192.168.100.20: udp

20:49:32.003295 IP (tos 0x0, ttl 55, id 0, offset 65376, flags [+], proto UDP (17), length 44, bad cksum 8d8b (->8d9f)!) 17.155.127.222 > 192.168.100.20: udp

Oct 19, 2015 2:48 PM in response to h4170706c655375636b73

***--- MOSTLY SOLVED, No thanks to Apple ---***


4 days ago, I decided to do something contrary to the iOS end-user software license agreement (Wink-Wink, Nudge-Nudge, Say no more!) to see if I could figure out what the problem was myself. Like any good problem, the battery drain was being caused by two things:


1) Game Center

2) WiFi


I tried switching off WiFi a few weeks ago to see if that had any effect on battery life, but it didn't. I now know why. It was because Game Center was in constant, relentless communication with Apple (as can be seen in my previous post). When I switched off WiFi, Game Center just continued using up my battery with it's relentless communication with Apple via 3G.


After performing the contrary action (Wink-Wink), I logged into my iPhone, found the process id for gamed using "ps ax" then stopped the process using "kill -9 ". The constant communication that had been going on suddenly stopped. HURRAY!


To make the change permanent, I deleted the file com.apple.gamed.plist and restarted my phone to make sure the traffic I was seeing didn't start back up again.


I watched my phone behavior over the next day and found that it would stop responding (pressing the home button did nothing) after going into standby mode but it would only behave this way while not connected to a power source (on battery power). It seemed to me to have something to do with WiFi so I switched off both WiFi and Bluetooth.


My phone battery has lasted 12 hours each day for the last 2 days and today, after 6 hours the battery shows 52% left. I can use WiFi as long as I'm actively using my phone but I have to switch WiFi back off as soon as I'm done otherwise it causes my phone to crash when it goes into standby mode.

iOS 9.0.2

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.