This topic is closed.
21 replies2.7k viewsLast reply
Man there are quite a few bugs.
I can’t change the microphone volume/mute when bluetooth streaming but 2.4 ghz streaming is fine…
I can’t disengage the streaming by push button at all.
I can’t change volume or mute the microphone on main program
You’re ignoring this member’s posts.
Are you talking about using fitting software to set the run parameters in a particular program or referring instead to changing things with the Smart 3D app?
My continuing experience with the ReSound Quattros on into iOS 16 on a new iPhone 14 Pro Max is that occasionally things get hung up for some reason. I’m not sure if it’s ReSound’s fault or Apple’s fault but quite a few times I think it’s the latter. To restore whatever’s hung when a problem occasionally does occur, I often find I have to power down and reboot my phone. Just force closing and relaunching the Smart 3D app often does not fix some problems. An example would be that the Smart 3D app shows one of the ’s is not connected to my iPhone even though the aid is on and functioning well.
Maybe it’s just getting a far more powerful phone than my previous iPhone, the wife’s old iPhone XS Max, but the Smart 3D app runs like gangbusters on my iPhone 14 Pro Max. Loads immediately, shows battery states immediately, and switching to any screen in the program is very fast.
I have noticed in iOS 16 that when out walking and listening to podcasts if my phone is in a new holster case at my waist that streaming breaks up more than it ever has with previous iPhones and previous iOS versions. Could be the holster case or the MagSafe Apple phone case I got. But in the past, IIRC, I’ve walked with an earlier iPhone in my back pants pocket and had great BT streaming.
So I think Apple and ReSound might need to work a bit on performance/connectivity in iOS 16.
Perhaps the forum’s Oticon-oriented thread on issues with iOS 16 (and/or iOS 15) is an indicator that even Oticon and Apple are not entirely on the same page as well when it comes to connectivity and firmware, etc.
You’re ignoring this member’s posts.
i’m only talking about the resound 3d app… The audiologist said it a suspected firmware bug i’m not a self fitter and i’ll never be one because I have a very unique config, Nucleus 7 and Omnia 7 UP. If i fuck up the perfect fitting parameter. it throws off my hearing bimodally reducing performance rather than helping performance…
I have a Android device
You’re ignoring this member’s posts.
Perhaps the forum’s Oticon-oriented thread on issues with iOS 16 (and/or iOS 15) is an indicator that even Oticon and Apple are not entirely on the same page as well when it comes to connectivity and MFi firmware, etc.
That what happen when you don’t standardize the bluetooth protocol… you become slave to company lone support on protocol… 
you are watching the downfall of company support on a non standard bluetooth protocol when they put engineering resources into making sure that LEA/: codec is made perfect … i’'m telling you that MFI protocol is deprecated already when they launched the iphone 14 because they are supporting LEA /LC3 codec according to bluetooth sig certification …
You’re ignoring this member’s posts.
i’'m telling you that MFI protocol is deprecated already
Made for iPhone is just a branding term. It doesn’t imply specific technology other than being something “special” that you get when you use hearing aids. Apple is still into using that term. Here’s a link to an Apple support page updated as of 9/15/22 on which Apple is still throwing the MFi hearing aid moniker around. Even if the underlying basis were to become the LEA/ codec, I’d bet that Apple will try to find something in connectivity that you can only get using MFi ’s with an iPhone - it’s their basic walled garden approach.
About Hearing Aid Compatibility (HAC) requirements for iPhone - Apple Support3
While looking for the most recent Apple page touting MFi, I found the following discussion of an Apple patent application that seems to be adding environmental program switching into the basic MFi connectivity features. I wonder how Apple being in charge of what program, directionality, noise features, etc., are activated will go over with ReSound, Oticon, Starkey, etc., ??? Perhaps if they ever implement that sort of feature for MFi HA’s, the HA OEM will have an option to override the basic Hearing Devices settings?
Apple Developing Advanced Features for MFi Hearing Aids - The Mac Observer2
when they launched the iphone 14 because they are supporting LEA /LC3 codec according to bluetooth sig certification
BTW, if you can find anywhere on Bluetooth.com2 that the iPhone 14 is BT certified, folks in the BT LE Audio and The Future of Hearing thread on this forum would probably love you posting a link to such a certification/announcement as one of the conundrums is why Apple hasn’t publicly trumpeted anything about BT LE Audio and the iPhone 14. Folks like me who bought an iPhone 14 with that expectation would love to see something definite on that score.
You’re ignoring this member’s posts.
BTW, if you can find anywhere on Bluetooth.com that the iPhone 14 is BT LE Audio certified, folks in the BT LE Audio and The Future of Hearing thread on this forum would probably love you posting a link to such a certification/announcement as one of the conundrums is why Apple hasn’t publicly trumpeted anything about BT LE Audio and the iPhone 14. Folks like me who bought an iPhone 14 with that expectation would love to see something definite on that score.
See supported layer, you will see codec in the cert
https://launchstudio.bluetooth.com/ListingDetails/1576916
You’re ignoring this member’s posts.
Made for iPhone is just a branding term. It doesn’t imply specific technology other than being something “special” that you get when you use MFi hearing aids. Apple is still into using that term. Here’s a link to an Apple support page updated as of 9/15/22 on which Apple is still throwing the MFi hearing aid moniker around. Even if the underlying basis were to become the BT LEA/LC3 codec, I’d bet that Apple will try to find something in connectivity that you can only get using MFi HA’s with an iPhone - it’s their basic walled garden approach.
what is your point there? I’m well aware of this.
You’re ignoring this member’s posts.
While looking for the most recent Apple page touting MFi, I found the following discussion of an Apple patent application that seems to be adding environmental program switching into the basic MFi connectivity features. I wonder how Apple being in charge of what program, directionality, noise features, etc., are activated will go over with ReSound, Oticon, Starkey, etc., ??? Perhaps if they ever implement that sort of feature for MFi HA’s, the HA OEM will have an option to override the basic Hearing Devices settings?
they can patent whatever they want so they can license the idea to hearing aid manufacture… it is common n in industry to patent whatever they think is a good idea.
You’re ignoring this member’s posts.
That’s interesting as if you search from the main search page on “Apple,” https://launchstudio.bluetooth.com/Listings/Search1, the latest iPhone 14s come up but they’re listed as having only 5.2 (which is BLEA compatible, too, IIRC). Whereas on the page you point out for the host subsystem 192218 (which is used in the iPhone 14), the core specification is listed as 5.3, I’m assuming that’s referring to BT 5.3 - and that’s an earlier posting as of 8/1/22 whereas the Apple search results were posted 9/19/22).
Is the reference to the line under Supported Layers that say “Low Complexity Communication Codec” is supported? Pardon my ignorance!
You’re ignoring this member’s posts.
what is your point there?
The point is the “” is a branding term and just refers to connectivity restricted to iPhones and devices that buy into Apple’s protocol(s). But we have no idea exactly what those protocols are. And there is no reason to suppose they are going away anytime soon. I predict that Apple will offer (BLEA) connectivity but it will continue to offer MFI connectivity. It could offer a version of BLEA that works best with MFi devices but still works with other BLEA devices. And Apple has to keep offering backward compatibility with the previous MFi protocols to avoid pulling the rug out from under hearing aid users hanging on to their older devices. I met an elderly woman at a neighborhood party the other day who was quite happy with her 2014 battery-powered ’s, which she said were working great, and saw no reason to upgrade.
So just because BLEA is coming along doesn’t mean Apple can’t offer a special version of that and brand it as MFi connectivity. And the old MFi is not going away anytime soon. iPhones can have both BLEA and MFi.
ReSound Ones do the old MFi; they’re also claimed by ReSound to be BLEA-compatible (at least in 2021). My iPhone 14 can do MFi with my Quattros but you infer from the search page you referenced that the iPhone 14 is already BLEA-ready, basically.
You’re ignoring this member’s posts.
That’s interesting as if you search from the main search page on “Apple,” Launch Studio - Listing Search, the latest iPhone 14s come up but they’re listed as having only BT 5.2 (which is BLEA compatible, too, IIRC). Whereas on the page you point out for the host subsystem 192218 (which is used in the iPhone 14), the core specification is listed as 5.3, I’m assuming that’s referring to BT 5.3 - and that’s an earlier posting as of 8/1/22 whereas the Apple search results were posted 9/19/22).
i’m really confused here. what is your point here? iPhone 14 and Airpod pro uses / LE audio…
The point is the “MFi” is a branding term and just refers to connectivity restricted to iPhones and devices that buy into Apple’s protocol(s).
Nothing new, Apple is being Apple.
But we have no idea exactly what those protocols are.
We actually know, just ask the hearing device via bluetooth advertising protocol, it will give you a list of supported services… you can actually see in an btle sniffer app…
You’re ignoring this member’s posts.
Hi, @ssa
Instead of just tossing out remarks, perhaps you should illustrate your statements in sufficient detail to demonstrate what you claim. The page you cited for the iPhone 14 supporting doesn’t say anything clearly that you have pointed out specifically in text as having BT LE Audio already implemented. “low complexity codec” to me is not necessarily . BT 5.3 doesn’t mean LC3 is actually up and running on a device. And as a Mac Rumors article pointed out, the status of BT LE Audio for the AirPods Pro 2.0 is a mystery: LE Audio and the Future of Hearing - #488 by jim_lewis.
I have used nRF Connect to look at protocols previously. For proprietary protocols, there is usually only a line describing an available service as such with something like “no further description available.” So, perhaps you could provide a more detailed example from your favorite BT scanner of how it divulges the inner workings of proprietary protocols to you. I could learn something useful from that.
Not to get into a flame war here, but it seems that you make assertions but don’t back them up with detailed illustrations that others can agree, Yep, that’s what it says. Others do not seem to be reaching the same conclusions as you are that BT LE Audio is up and running on the iPhone 14 or AirPods Pro 2.
You’re ignoring this member’s posts.
Instead of just tossing out remarks, perhaps you should illustrate your statements in sufficient detail to demonstrate what you claim
Well I don’t work for Apple first of all and Apple employee are under NDA. Apple said it support the latest 5.3 and the evidence in certifcation back it up …
I have used nRF Connect to look at protocols previously. For proprietary protocols, there is usually only a line describing an available service as such with something like “no further description available.” So, perhaps you could provide a more detailed example from your favorite BT scanner of how it divulges the inner workings of proprietary protocols to you. I could learn something useful from that.
Huh? All i said you can get the different advertising services ID like MFI, , and other resound services
Not to get into a flame war here, but it seems that you make assertions but don’t back them up with detailed illustrations that others can agree, Yep, that’s what it says. Others do not seem to be reaching the same conclusions as you are that BT LE Audio is up and running on the iPhone 14 or AirPods Pro 2.
i’m not trying to start a flamewar, please stop jumping into conclusion? I stand by my assessment. take it or leave it,
Let me ask you this, do you have any evidence of LE audio is not enabled on iphone 14 or airpod pro 2nd gen ? you should be able to see the BTLEA protocol services if the 2nd airpod pro has it enabled…
You’re ignoring this member’s posts.
Let me ask you this, do you have any evidence of LE audio is not enabled on iphone 14 or airpod pro 2nd gen ?
Do you have links to that they are?
You’re ignoring this member’s posts.
A post with a link to the contrary about how why Apple is mum on implementation for now.
Another opinion that BT 5.3 and the new audio in the iPhones and AirPod Pro 2s brings improved listening but no BT LE Audio for now as it’s not as good as Apple’s AAC codec and would only enhance use of the AirPod Pros with non-Apple devices - not a desirable outcome for Apple, for now. iPhone 14 and AirPods Pro 2 support Bluetooth 5.3, but LE Audio support not confirmed (ithinkdiff.com) Also, only BT 5.3, not BT LE Audio, is mentioned in Apple’s tech specs for the AirPods Pro 2 and under Sys…
You’re ignoring this member’s posts.
A post with a link to the contrary about how why Apple is mum on BT LE Audio implementation for now.
There is a bit of negotiation between airpod and iPhone
to name a few codec AAC, Apt X and , the devices determine the link.
The transport medium is the new LE audio link by bluetooth sig authors (LE Isochronous Channels)
They can use any codec on the airpod pro but the base negotiated link must have LC3 for compatibility.
Background: i have experience working on creating protocol level specification
You’re ignoring this member’s posts.
Do you have links to that they are?
I gave you evidence they are using LE audio,via bluetootth sig certification. take it or leave it… I stand by my assessment.
What more evidence do you need? I don’t own an airpod or an iphone…
Certification requires a lot of testing with a certification test box/suite…
You’re ignoring this member’s posts.
You’re ignoring this member’s posts.
Can confirm that LE audio is not enabled in current omnia firmware release but it has a few GATT services for bluetooth 5.2 but it is incomplete
You’re ignoring this member’s posts.
You’re ignoring this member’s posts.
Hearing Aids3 replies
Hearing Aids49 replies
Hearing Aids5 replies
Fitting Software Requests902 replies
Hearing Aids139 replies
Toronto, Canada