Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
I went to use Siri yesterday for the first time since updating, and found that the voice had randomly changed from British to Australian. Furthermore it required a download to get the British voice back. Has anyone else run into that?
 
  • Like
Reactions: dk001
Performance-wise it should run just fine. I run 17.2 on my iPad Pro 11 with a A12X Bionic chip daily and the performance on that is fine.

The problem you’re likely to run into is the RAM. Like my iPad, the SE 3 has 4 GB which isn’t really enough for 17.2 to do all it’s background tasks and have other apps running at the same time. As such you may run into odd things like web pages failing to load at times if you have multiple tabs open and suspended apps constantly being dumped from memory when the phone decides it wants to run background tasks.

Besides that, iOS 17.2 should work just fine.
With the iPhone Pro and the iPad Air/Pro having 8GB of RAM, I completely understand that this could happen, but not as soon as with iOS 17. I would understand that 3GB devices would start to notice the lack of memory, but 4GB devices now? A couple of years ago, iPhone 13 was still using 4GB of RAM… and I think it should be enough even today.

Having such issues in mind, I’ll think about what I do, but I will update to iOS 17 sooner or later, I have that crystal clear. Wether I do it now or next year, is what I have to consider, because iOS 16 runs very smooth and efficiently (the SE3 lasts two whole days if I leave Low Power mode on all time), but I want the features on iOS 17.
 
  • Like
Reactions: ibookemo
With the iPhone Pro and the iPad Air/Pro having 8GB of RAM, I completely understand that this could happen, but not as soon as with iOS 17. I would understand that 3GB devices would start to notice the lack of memory, but 4GB devices now? A couple of years ago, iPhone 13 was still using 4GB of RAM… and I think it should be enough even today.

Having such issues in mind, I’ll think about what I do, but I will update to iOS 17 sooner or later, I have that crystal clear. Wether I do it now or next year, is what I have to consider, because iOS 16 runs very smooth and efficiently (the SE3 lasts two whole days if I leave Low Power mode on all time), but I want the features on iOS 17.

For the most part it’s okay. The 2 big issues I run into is Safari hogging memory and sometimes opening an app, switching to a different app and then going back to the first app and finding it has to completely reload. I can do things like multitasking apps, but switch too many apps and they will unload. It depends on the app though as some use more memory than others.
 
  • Like
Reactions: Populus
I went to use Siri yesterday for the first time since updating, and found that the voice had randomly changed from British to Australian. Furthermore it required a download to get the British voice back. Has anyone else run into that?

Not a direct answer to your question but mine is set to American Voice 4 and didn't change.
 
My original 15PM had some kind of hardware issue (according to Apple - via in store testing) that caused the WiFi to act erratically.

The 15PM replacement I now have, when on WiFI 6, drops to half speed or lower if I am more than 10ft (approx) from my router/modem. I have several WiFI 6 devices and none of them show any kind of speed constraint at that range (line of sight).

That's not good. It feels like a design fault of the antenna array. Have you turned the Mac in such position that the screen is in line of sight? The casing does interfere. I would not erase the combination of router wifi chipset and the one inside the Mac though - some just don't work nice.

Back in 2004 I had the worst wifi combination ever... the first Draytek wifi modem and a Broadcom PCMCIA wifi card for my Powerbook G4. That connection lasted for no more than 15 minutes. After that the wifi chip inside the Draytek would "crash". After a reboot the same thing happend again after 15 minutes... and so on.
Over the years I've seen similar effects; some combination of basestations and Mac's work flawlessly and others horrible. My last Airport Extreme (5GHz model) worked fine but its range was limited. Today I have a Zyxel WAX650S which covers 20 feet in all directions, reaching about 20+ devices spread over 3 floors. On wifi 4 much better than the old AE. And the wifi 6 Mac's have full 1Gbps speed within 10 feet now.
 
  • Like
Reactions: dk001
Stickers prompt form keyboard has a small bug, the X doesn't work (to close it), tested with a bunch of apps, this is with a brand new iphone 15 pm running 17.2 and the latest version of the tested apps (whatsapp, zohomail, outlook, telegram).

1702922978975.jpeg
 
I finally made the jump to ios17.2 my thoughts:

Pros
Battery life is much better than ios 16.

Cons
Everything feels slower (i dont have an iphone 15), buggy text messages, my mothers phone froze while using Duolingo and receiving a phone call at the same time.

The ios doesn't feel finished.

A clean install is a pain they changed the process i had to wipe my devices 2 times in order to perform a "secure installation" on all my devices, annoying.
Sounds like quite a disappointing experience. iOS 16 seems to have turned out much better than 17. I hope it improves soon.
 
  • Like
Reactions: Hans300 and Populus
Thank you for confirming. Appreciate it.

It’s yet another decision by Apple that truly is gobsmacking and unjustifiable. I am pretty vocal about how much I despair when it comes to Apple and this really does not improve my opinion. I know it’s not the end of the world but some of their design decisions are mental in my opinion.
I'll tell you that although I love my Apple Watch, it's the one device that gives me the most trouble. I can't count the number of times I have unpaired and re-paired my watches. If my watch is separated from my phone, for a run as an example, it might not connect back to my phone properly. Even though it's a cellular-based watch, iMessages from the watch go undeliverable -- only solution is to reboot the watch.
 
I'll tell you that although I love my Apple Watch, it's the one device that gives me the most trouble. I can't count the number of times I have unpaired and re-paired my watches. If my watch is separated from my phone, for a run as an example, it might not connect back to my phone properly. Even though it's a cellular-based watch, iMessages from the watch go undeliverable -- only solution is to reboot the watch.
Adding @StumpyBloke

This morning iMessage texts whether via email id or phone number, stopped showing up on my AW.
A reboot has not fixed the issue :(.
pita.
 
  • Like
Reactions: StumpyBloke
There is definitely something fundamentally flawed on this release with the iMessages on Apple Watch. You guys have mentioned it, I’ve had a problem. And a friend of mine has just messaged me to say that they’ve got issues with our conversation being in two separate threads. “It just doesn’t work”
 
  • Like
Reactions: dk001
Encountered the squared notification bug today. The only other time I have come across it was on one version of iOS 16 (I think it was 16.2).
 
There is definitely something fundamentally flawed on this release with the iMessages on Apple Watch. You guys have mentioned it, I’ve had a problem. And a friend of mine has just messaged me to say that they’ve got issues with our conversation being in two separate threads. “It just doesn’t work”
The multiple threads in imessage thing has happened to me in the past. In my experience, it usually has something to do with having different conversations started to/from your email address, and to/from your phone number. iMessage treats those as separate threads even though both are associated with your single Apple account. To avoid it, I change my iMessage "send/receive" setting to only use my phone number.
 
The multiple threads in imessage thing has happened to me in the past. In my experience, it usually has something to do with having different conversations started to/from your email address, and to/from your phone number. iMessage treats those as separate threads even though both are associated with your single Apple account. To avoid it, I change my iMessage "send/receive" setting to only use my phone number.

That absolutely makes sense. However the conversation in question is one that is years old and nothing at either end has changed. And thinking about it, another one of the very strange things that was going on was that some replies to various people were going in my own thread instead of going into the existing conversations. Just a load of crap really.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.