Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
For months now my 16pm has issues with carplay after phone calls.
It can be resolved by disconnecting the car and reconnecting.
So zero to do with N1.
This may be your experience with the 16 Pro, but your fix does not work with the 17 series phone. I wiped my 17 phone off the car, and car off the phone, then shutdown the car and the phone. Problem is still there.
 
For what it's worth, I fixed this by giving myself a fixed IP instead of relying on DHCP.

This seems to be related to DHCP -- whenever my WiFi connection dropped, I noticed my phone had a 169.254.x.x APIPA address, suggesting DHCP was failing. Giving myself a fixed IP and fixed DNS entries resolved my problem until Apple can fix their implementation.
 
Scratch-Gate, Wi-Fi Gate, IOS 26 Gate…
Damn is the worst iPhone release ever ever!! Apple is cooked under Tim… Cook!!
 
  • Haha
Reactions: BorisDG
So for my friend and I, this happens with wired CarPlay not working. I have a 2019 Honda, she has a 2021 Toyota. When connecting via Wired CarPlay, it either hangs on "Connecting" or just isn't recognized at all. At one point by deleting the Car from the Phone CarPlay Menu and the phone from the Car menu, I was able to get it reconnected but it stopped on the next time I went in the car. Nasty bug, I hope it gets fixed quickly.
 
For what it's worth, I fixed this by giving myself a fixed IP instead of relying on DHCP.

This seems to be related to DHCP -- whenever my WiFi connection dropped, I noticed my phone had a 169.254.x.x APIPA address, suggesting DHCP was failing. Giving myself a fixed IP and fixed DNS entries resolved my problem until Apple can fix their implementation.
Funny I was wondering if messing with dhcp would fix it. Other odd thing is my 6 month old Asus BQ16 Pro wifi 7 mesh nodes died after having the 17 Pro for 8 hours. Sounds crazy but the coincidence is… odd.
 
  • Like
Reactions: centauratlas
This happens to me every single day when I’m in my bedroom doomscrolling before bedtime. I’m forced to turn WiFi off and use 5G UW.
 
Honestly I probably wouldn't have even noticed if service at my house was decent enough. I also rely on wifi for my Sonos speakers. Hoping iOS 26.0.1 comes soon with a fix!
 
Last edited by a moderator:
17 PM with AWU3 is absolute nightmare. I paired and un-paired the Watch about 10 times now thinking there’s some software issue with it. In my Bluetooth settings on the iPhone it’s not connected to the Watch. The watch is on 5G running by itself even though my PAIRED phone is right next to it. I hope they fix this soon!
 
I had a disconnect from Carplay once. With my Wifi 7 at home I have abslutely no issues.
I read from a few that it is much worse for them. Let`s see how long apple will take to fix that with an update.
Same I had is disconnect from CarPlay once. Wifi has been solid with no drops.
 
It's amazing to me how little testing must have done for this obvious of a bug to get to production. I know this doesn't affect everyone, but it is affecting a lot of people. I am shocked at the poor testing involving such a critical product.
 
A different issue but they still have not fixed wired CarPlay call dropouts. It plays music fine but when on a call it cuts out then will comeback again. My 16 Pro Max did it in my wife’s car and her mother’s car and my wife’s iPhone 15 was also doing it in both cars. Cable replacement has not resolved and either has iOS 26.
 
It's amazing to me how little testing must have done for this obvious of a bug to get to production. I know this doesn't affect everyone, but it is affecting a lot of people. I am shocked at the poor testing involving such a critical product.
And of all things, it's the Wi-Fi/Bluetooth, one of the most critical components. Considering this is the first time they've used their own N1 chip for this, this should have been tested way more thoroughly.
 
I think you’re jumping to conclusions a bit quick here, could be SW related …

Hardware or software, you would expect Tim Cook’s directive to be “pay quadruple overtime if you have to, make sure there are zero bugs so there’s no chance of a headline.”

The mechanical engineering team clearly took the directive to heart with the Air’s bend test. The N1 team seems to have to waved it off.
 
And of all things, it's the Wi-Fi/Bluetooth, one of the most critical components. Considering this is the first time they've used their own N1 chip for this, this should have been tested way more thoroughly.
Exactly...

Potential Customers: I hear you have a new chip in your iphones.
Apple: Yes everyone, check out our new chip. It sucks. It drops connections to wifi and bluetooth. Really, check it out... LOL

Nothing says "flagship phone" like a phone that can't do wifi or bluetooth...
 
  • Like
Reactions: LightsOn45
Has anyone taken a look at the analytics data? If, for example, the Wi-Fi driver crashes, something should be recorded there.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.