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.
AirPods Max (USB-C version) wired audio impressions
- Thread starter PotentPeas
- Start date
- Sort by reaction score
Two hours charging (one hour in the case, one hour out of the case), no update yet. I just rebooted both my phone and the AirPods Max, played a bit of music to make sure that they are connected and active, and now I'm trying again in the case. Will check in an hour.
Something to keep in mind:
The UK page still shows 7A291 as the latest firmware version: https://support.apple.com/en-gb/106340
Whereas the Canadian page has 7E99 (the USB-C audio firmware, the one that just came out) as the latest one: https://support.apple.com/en-ca/106340
I just think it's not out in Europe yet.
The UK page still shows 7A291 as the latest firmware version: https://support.apple.com/en-gb/106340
Whereas the Canadian page has 7E99 (the USB-C audio firmware, the one that just came out) as the latest one: https://support.apple.com/en-ca/106340
I just think it's not out in Europe yet.
Weird. Don't recall this ever happening before with updates. Wonder when we can expect it, I've had my APMs plugged in for like 2 hours now. This explains it.
Another hour passed and it didn't update.
...At this point I'm going to wait a while before trying again, I think.
(I am in the U.S., not in Europe.)
...At this point I'm going to wait a while before trying again, I think.
(I am in the U.S., not in Europe.)
has this ever happened before for any update (iOS, macOs, AirPods firmware etc)? I can't remember it ever being staggered to different regions like this. Frustrating, Apple or MacRumors should have made that clear.
No one knows if it is really staggered like this. There are no reports of a successful update yet. I am in the U.S. and it is not working for me either.
Has Apple actually officially "announced" 7E99 anywhere? The MacRumors front page only mentions the firmware updates for AirPods and AirPods Pro, not the APMs.
Maybe it's just prematurely been updated on the support page and not meant to be available until early April as was mentioned before.
Maybe it's just prematurely been updated on the support page and not meant to be available until early April as was mentioned before.
About firmware updates for AirPods - Apple Support
Learn about changes and features included in the firmware updates for your AirPods.
About firmware updates for AirPods - Apple Support
Learn about changes and features included in the firmware updates for your AirPods.support.apple.com
They said "Maybe it's just prematurely been updated on the support page and not meant to be available until early April as was mentioned before."
The support page says
"*To update your AirPods Max (USB-C), you need iOS or iPadOS 18.4 or later, or macOS Sequoia 15.4 or later."
That's what was released today.
Also, tomorrow is April. The only mention of "early April" previously was in regards to the launch of 18.4, which was assumed to be "early April."
I know what it says. I'm replying to the other user who replied to another without reading the full post.
There might be some misconfiguration with their servers, both my Mac and iPhone find the pending update, but fail to start downloading the update (in the US):
Code:
accessory = <EAAccessory: ****> {
connected:YES
connectionID:****
name: ****
manufacturer: Apple Inc.
modelNumber: A3184
serialNumber: ****
ppid: (null)
regioncode: (null)
firmwareRevisionActive: 7A291
firmwareRevisionPending: 70.2256000021000000.2341
hardwareRevision: 1.0.0
dockType:
certSerial: 0 bytes
certData: 0 bytes
protocols: (
"com.apple.accessory.updater.app.83",
"com.apple.accessory.updater.app.multiasset.83"
)
delegate: (null)
}
Code:
NDSession <> Task <>.<21> for client com.apple.mobileassetd will be retried after error
Error Domain=_nsurlsessiondErrorDomain Code=6 "(null)"
UserInfo={
NSErrorFailingURLStringKey=https://mesu.apple.com/assets/macos/com_apple_MobileAsset_MobileAccessoryUpdate_A3184_EA/com_apple_MobileAsset_MobileAccessoryUpdate_A3184_EA.xml,
NSErrorFailingURLKey=https://mesu.apple.com/assets/macos/com_apple_MobileAsset_MobileAccessoryUpdate_A3184_EA/com_apple_MobileAsset_MobileAccessoryUpdate_A3184_EA.xml,
_NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalDownloadTask <>.<21>"
),
_NSURLErrorFailingURLSessionTaskErrorKey=LocalDownloadTask <>.<21>
} - code: 6The first one is from the
UARPUpdaterServiceLegacyAudio process both on iOS and macOS:and the second one is from process
nsurlsessiond. Both captured in Console (with private logs enabled).Yep I get the same thing...
Code:
Error code is: 403 descriptor:com_apple_MobileAsset_MobileAccessoryUpdate_A3184_EA.xml with (null) . task BackgroundDownloadTask <04CB30D9-65D4-4B3B-9B4C-19C0AA60183D>.<37>Interesting that Logic didn’t get an update.
I wonder if they are going to continue to use the Apple renderer plugin which would make this kind of a hilarious upgrade over lightning with the audio cable since the fidelity difference would be absolutely minuscule.
Since they’re sending lossless atmos / spatial directly to the headphones via usb-c it is puzzling why they wouldn’t leverage that for Logic… I can’t imagine the updates would be asynchronous.
I wonder if they are going to continue to use the Apple renderer plugin which would make this kind of a hilarious upgrade over lightning with the audio cable since the fidelity difference would be absolutely minuscule.
Since they’re sending lossless atmos / spatial directly to the headphones via usb-c it is puzzling why they wouldn’t leverage that for Logic… I can’t imagine the updates would be asynchronous.