HackDaBox
macrumors 6502
Are you comparing 26 beta to 27 beta or 26 release to 27 beta because it’s not a fair comparison if that’s the case as it’s not polished yet and not optimized and logging everything.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 27 Beta 4 ― Bug Fixes, Changes, and Improvements
- Thread starter Banglazed
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
Dust-by-Monday
macrumors 6502a
martin2345uk
macrumors 68000
Have they removed Expressive Voice settings in this Beta? Seems to have disappeared on my 17PM?
roncron
macrumors 65816
I’m having only one problem with db4: CarPlay connection with my 2025 Honda CRV. About half the time, it takes a long time to connect, or it connects quickly but disconnects later. When it disconnects, sometimes it reconnects on its own after a minute or five, other times it never reconnects. I’ve filed a feedback.
During the full run of iOS 26, and on iOS 27 db3, I had CarPlay connection issues but far less serious and less frequent than on db4.
Otherwise, things are great. Speed and stability get an A+ from me. Also, very solid battery life: I’m getting 50 to
70 minutes of active use from each 10% drop in battery charge level. That’s as good as I’ve ever experienced on this 17 Pro.
During the full run of iOS 26, and on iOS 27 db3, I had CarPlay connection issues but far less serious and less frequent than on db4.
Otherwise, things are great. Speed and stability get an A+ from me. Also, very solid battery life: I’m getting 50 to
70 minutes of active use from each 10% drop in battery charge level. That’s as good as I’ve ever experienced on this 17 Pro.
one more
macrumors 603
I have similar problems with a wired CarPlay in DB4. Have tried everything I could think of (IPSW-reinstalling DB4, removing and adding back the car in CarPlay, force restarting the iPhone and checking different cables). No luck! Also submitted a feedback and now am waiting for DB5.
Update: It looks like after all my CarPlay issues were caused by some intermittent issues with the Anker USB A to USB C cable. Yesterday I was driving another car fitted with the same cable, which was bought later and used much less, and had zero dropouts during a long drive. So today I plugged this “good” cable into my usual car (which used to have disconnects) and drove for about three hours with zero dropouts. What is strange, however, is that the “bad” cable had no issues working in my car with an iPhone 15 running iOS 26.5.2, yet would be having lots of dropouts with my iPhone 17 and DB4. Is it possible that iOS 27 feeds more data so my “bad” USB 2.0 cable gets “overloaded” and drops the connection, whereas its younger twin manages to handle it? Anyway, I have now ordered a UGREEN USB 3.0 cable, so it should resolve it.
Last edited:
TheByteSmasher
macrumors 6502
And now my Apple Watch, which is also on the developer beta, is alerting me to the texts that I send and my AirPods even read them to me from my name
Throughout the whole beta cycle thus far I’ve had issues forwarding photos and videos from one iMessage conversation to another. It always appears to be working with the blue progress bar under the photo/video, but ultimately always results in a “Message Send Failure”.
Anyone else?
Anyone else?
I can’t say I agree. The switching threshold was too low, so the constant switching was distracting to me. I couldn’t focus on the content and instead was focusing on the UI.
Is the share button too low, or is it just my eyes?
ProbablyDylan
macrumors 68040
When working on a personal app I noticed this too. The center of the share button isn't the center of the box - it's rectangular.
Jakimo
macrumors 6502a
PigsOnTheWing
macrumors member
Has anyone else been experiencing random reboots since iOS 27 Developer Beta 3?
Mine started with Beta 3 and have continued on Beta 4 (24A5390f).
To rule out software corruption, I performed a complete IPSW restore via Finder, set my iPhone 16 Pro Max up as a new iPhone, and did not restore a backup. Despite that, the phone continued to kernel panic. I have now experienced five kernel panics.
Every panic log has the same signature:
panic(cpu 1 caller ...): GFX crash of unknown type 0x80a
Exception class=0x2f (SError interrupt)
...
agx_scheduler(2)
The panics have occurred both shortly after launching an app and while the phone was sitting idle on my desk with no user interaction.
I never experienced spontaneous reboots on iOS 26, and the issue persisted even after the clean install, so I’m curious whether anyone else is seeing the same agx_scheduler / GFX crash of unknown type 0x80a kernel panic.
I’ve already submitted the logs to Apple via Feedback Assistant.
Mine started with Beta 3 and have continued on Beta 4 (24A5390f).
To rule out software corruption, I performed a complete IPSW restore via Finder, set my iPhone 16 Pro Max up as a new iPhone, and did not restore a backup. Despite that, the phone continued to kernel panic. I have now experienced five kernel panics.
Every panic log has the same signature:
panic(cpu 1 caller ...): GFX crash of unknown type 0x80a
Exception class=0x2f (SError interrupt)
...
agx_scheduler(2)
The panics have occurred both shortly after launching an app and while the phone was sitting idle on my desk with no user interaction.
I never experienced spontaneous reboots on iOS 26, and the issue persisted even after the clean install, so I’m curious whether anyone else is seeing the same agx_scheduler / GFX crash of unknown type 0x80a kernel panic.
I’ve already submitted the logs to Apple via Feedback Assistant.
ghostface147
macrumors 601
According to Siri, this could be a hardware issue considering you've set it up as new.
PigsOnTheWing
macrumors member
Hardware is certainly one possibility, but it doesn’t seem like the most likely explanation. My phone never experienced a single spontaneous reboot before installing iOS 27 Developer Beta 3. Under Beta 3, it was kernel panicking constantly. Beta 4 has actually been an improvement, but I’m still seeing a couple of panics a day.
To rule out software corruption, I performed a complete IPSW restore via Finder, set my iPhone 16 Pro Max up as a new iPhone, and did not restore a backup. The phone still kernel panicked.
I’m now up to five kernel panics, and every one has the same signature:
GFX crash of unknown type 0x80a
agx_scheduler
So it’s definitely a repeatable issue. Whether that’s an iOS 27 graphics regression or hardware that iOS 27 is exposing is still an open question, but the clean install ruled out a corrupted setup or bad user data.
Dust-by-Monday
macrumors 6502a
eveluvsrainbows
macrumors 6502a
This is quite literally a nothingburger. Obviously indexing is going to take time. It is indexing quite literally everything on the device. It doesn’t even really impact performance either and only shows a notice in the settings app. How would this be a drawback?
StumpyBloke
macrumors 603
Indexing still in progress. Is this “normal”?
I’m on a 15 Pro Max. Installed iOS 27 as soon as it was available. So it’s been about 23 hours and my phone still shows that it’s indexing. Also on a side note, I am still in the Siri waitlist. Which I am thinking might have to do with the indexing not being done.
forums.macrumors.com
eveluvsrainbows
macrumors 6502a
That was back with Beta 1. It doesn’t take anywhere near as long anymore, plus 26.6 is being released soon as well to prepare people’s devices for the indexing overhaul in 27.Indexing still in progress. Is this “normal”?
I’m on a 15 Pro Max. Installed iOS 27 as soon as it was available. So it’s been about 23 hours and my phone still shows that it’s indexing. Also on a side note, I am still in the Siri waitlist. Which I am thinking might have to do with the indexing not being done.
StumpyBloke
macrumors 603
I'm not sure why you are saying that. But I was pointing you in the direction of the official indexing thread. This thread is not for indexing.
HackDaBox
macrumors 6502
Negative ghost rider…..iPhone 12 Pro
(1) Do a hard reboot and keep holding power use the hardware test on this recovery menu.
(2) Remove the beta do a clean install of iOS 26 test everything to rule out a hardware issue.
(3) if it still is a problem report feedback and mention all troubleshooting you have tried.
Last edited: