Negative for me.
This is what I mentioned above: I’m wondering if the laxness that Apple showed during the beta about allowing users to switch regions will be going away with the public release.
Negative for me.
Looks like the WatchOS 11.1 RC is out. I really wish Apple could make watch updates download at a decent pace.....
There are too many variables with these types of comparisons: how many apps are running in the background, how much usage is occurring, and what kind of apps are used during that time. I know there are mornings when I get up and scroll on social media, and my battery drops quickly. If I am listening to a streaming podcast or something, it is far less. It will drop quickly if I use CarPlay, stream music, and use the GPS in a low cell area. We are all not Apples to Apples. But on any update, it takes a few days for things to settle down and for you to understand better. I have also listened to our boy @Pearsey, and I often will do a couple of hard reboots, which has resolved and smoothed out many of these software updates. I will back that up by having family do the same when they hit "bugs" in the software, and they, too, have found this resolves the issues (not a single one has ever needed to go to Apple or start over on a fresh install).This is wild to me. I only wish. I was off the charger at 4:15am this morning at by 6:30am I was down to 90%.
It is awful. But not near as bad as in the first few WatchOSes. It use to take multiple hours. Not sure why.
It is saying 688 MB and it is saying 30 to 45 mins. Horrible........
I really prefer wired updates as opposed to OTA - at least, as long as the wired update actually works, which they always did until iOS 18If you’re having issues with IPSW, why don’t you try OTA instead?
Haven’t had any issues on my 13P besides the ones listed as bugs.
OTA is the intended primary method thoughI really prefer wired updates as opposed to OTA - at least, as long as the wired update actually works, which they always did until iOS 18
Regardless of the fact that there’s an alternative, the primary method of updating should at the very least be functional and not brick devices. No excuses!!
Yes, I completely agree with you. I've been participating in the iOS 18 battery life thread to address my issues. I've turned off almost everything, and I rarely use my phone. This morning, I used it for just 15 minutes and sent two messages, and it dropped to 90%.There are too many variables with these types of comparisons: how many apps are running in the background, how much usage is occurring, and what kind of apps are used during that time. I know there are mornings when I get up and scroll on social media, and my battery drops quickly. If I am listening to a streaming podcast or something, it is far less. It will drop quickly if I use CarPlay, stream music, and use the GPS in a low cell area. We are all not Apples to Apples. But on any update, it takes a few days for things to settle down and for you to understand better. I have also listened to our boy @Pearsey, and I often will do a couple of hard reboots, which has resolved and smoothed out many of these software updates. I will back that up by having family do the same when they hit "bugs" in the software, and they, too, have found this resolves the issues (not a single one has ever needed to go to Apple or start over on a fresh install).
That's just my $0.02
OTA didn’t even exist at first, OTA updates were introduced years into the iOS ecosystem already being a thing, and it was introduced as an alternative. Maybe it is more popular now. That’s not my problem nor is it the point.OTA is the intended primary method though
Maybe we should all just move on from this? 🧐OTA didn’t even exist at first, OTA updates were introduced years into the iOS ecosystem already being a thing, and it was introduced as an alternative. Maybe it is more popular now. That’s not my problem nor is it the point.
Primary or not, any official method Apple offers for completing routine device maintenance tasks should NOT be this broken.
I’d rather see it get fixed than pretend the problem doesn’t existMaybe we should all just move on from this? 🧐
OK…. Looks like we aren’t moving on from this. Maybe you should write Tim a strongly worded email? Because repeating it over and over in here isn’t going to fix the issue that apparently only you are having!I’d rather see it get fixed than pretend the problem doesn’t exist
Yes, I completely agree with you. I've been participating in the iOS 18 battery life thread to address my issues. I've turned off almost everything, and I rarely use my phone. This morning, I used it for just 15 minutes and sent two messages, and it dropped to 90%.
I hope the battery life improves as we continue to use iOS 18. So far, my experience has not been good.
I’m not sure I have put forward correctly what I was originally trying to say. I was merely saying that for me the my default voicemail greeting remains in US voice. Only was for me to change this to a UK voice is to change regional setting. I can however use UK voice elsewhere for siri when still having USA as my regional setting.This is what I mentioned above: I’m wondering if the laxness that Apple showed during the beta about allowing users to switch regions will be going away with the public release.
It’s a brand new iPhone 16 Pro. This hasn’t been an 18.1 issue. The problems began after the first minor update that came out of the box. The version installed on the phone worked well initially, but that first update triggered all the issues. The same pattern occurred on my 14 Pro. It was great on the last beta of 18.0, but the RC and subsequent versions were terrible.If it’s doing things like that on a new/ish phone and you haven’t got the screen up full brightness and updating 30 apps whilst on iMessage, then I would reinstall the iOS. Pretty confident that will sort out the issue. There’s a guide on the first page of this thread.
It’s not me that’s only having the issue. There have been other reports of Apple Devices updates bricking other people’s devices as well. They are out there on this forum. But sure let’s just excuse the trillion dollar tech company and allow them to keep distributing broken software that’s putting people’s hardware and data at risk.OK…. Looks like we aren’t moving on from this. Maybe you should write Tim a strongly worded email? Because repeating it over and over in here isn’t going to fix the issue that apparently only you are having!
No one’s making any excuses.It’s not me that’s only having the issue. There have been other reports of Apple Devices updates bricking other people’s devices as well. They are out there on this forum. But sure let’s just excuse the trillion dollar tech company and allow them to keep distributing broken software that’s putting people’s hardware and data at risk.
Looks like the WatchOS 11.1 RC is out. I really wish Apple could make watch updates download at a decent pace.....
It is awful. But not near as bad as in the first few WatchOSes. It use to take multiple hours. Not sure why.
It is saying 688 MB and it is saying 30 to 45 mins. Horrible........
It’s not me that’s only having the issue. There have been other reports of Apple Devices updates bricking other people’s devices as well. They are out there on this forum. But sure let’s just excuse the trillion dollar tech company and allow them to keep distributing broken software that’s putting people’s hardware and data at risk.
For all the back and forth that my simple post started, not one person has managed to actually answer the question: is it still broken? But there’s no shortage of people outright denying the issue or downplaying its severity.
Well the people who are installing this update would fall into one of 3 camps, correct?I don’t think anyone is discrediting those of you who are having issues with your iPhone and I don’t think anyone is trying to side with Apple. Having said that, how do you expect the people who aren’t experiencing any issues on their iPhone respond to the question, “Is it still broken?”
You can’t get mad at people who are informing you that they aren’t having any problems with their iPhones.
It’s a brand new iPhone 16 Pro. This hasn’t been an 18.1 issue. The problems began after the first minor update that came out of the box. The version installed on the phone worked well initially, but that first update triggered all the issues. The same pattern occurred on my 14 Pro. It was great on the last beta of 18.0, but the RC and subsequent versions were terrible.
Edit: To add, I did the RC update using the IPSW.
Clearly, nobody on here has the answer for you.Well the people who are installing this update would fall into one of 3 camps, correct?
1. Updated OTA
2. Updated via IPSW on a Mac
3. Updated via IPSW on Windows “Apple Devices”
We have plenty of people chiming in that 1. Is functional
We even had one person upthread chiming in that 2 is functional
So, people in camp 3 are being very quiet. And I am asking because I genuinely want to know how it is going for these people. It is either still bricking devices or the problem has been fixed. There are only so many choices here.
“hi everyone! I updated via Apple Devices, and my iPhone is working! I’m on iOS 18.1 now!”
Or
“Hi everyone, I have bad news. I tried to update to iOS 18.1 in Apple Devices, and my iPhone is bricked now”
I’m asking because these people are not sharing their experiences unprompted. I’m only getting frustrated at those who are basically saying “who cares, I did things a different way and you can too”
Maybe no news is good news...Well the people who are installing this update would fall into one of 3 camps, correct?
1. Updated OTA
2. Updated via IPSW on a Mac
3. Updated via IPSW on Windows “Apple Devices”
We have plenty of people chiming in that 1. Is functional
We even had one person upthread chiming in that 2 is functional
So, people in camp 3 are being very quiet. And I am asking because I genuinely want to know how it is going for these people. It is either still bricking devices or the problem has been fixed. There are only so many choices here.
“hi everyone! I updated via Apple Devices, and my iPhone is working! I’m on iOS 18.1 now!”
Or
“Hi everyone, I have bad news. I tried to update to iOS 18.1 in Apple Devices, and my iPhone is bricked now”
I’m asking because these people are not sharing their experiences unprompted. I’m only getting frustrated at those who are basically saying “who cares, I did things a different way and you can too”
Well the people who are installing this update would fall into one of 3 camps, correct?
1. Updated OTA
2. Updated via IPSW on a Mac
3. Updated via IPSW on Windows “Apple Devices”
We have plenty of people chiming in that 1. Is functional
We even had one person upthread chiming in that 2 is functional
So, people in camp 3 are being very quiet. And I am asking because I genuinely want to know how it is going for these people. It is either still bricking devices or the problem has been fixed. There are only so many choices here.
“hi everyone! I updated via Apple Devices, and my iPhone is working! I’m on iOS 18.1 now!”
Or
“Hi everyone, I have bad news. I tried to update to iOS 18.1 in Apple Devices, and my iPhone is bricked now”
I’m asking because these people are not sharing their experiences unprompted. I’m only getting frustrated at those who are basically saying “who cares, I did things a different way and you can too”