Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Everything else aside, not sure that's necessarily the case when it comes to this issue (or really a variety of other ones that a variety of people experience).

Ultimately it appears that there is an issue and those who experience it and are negatively affected by it should be reporting it to Apple and following up on it with Apple as best as they can to hopefully get the issue addressed.

Maybe so, but they have said that they're aware that some bluetooth car stereos and speakers will be affected by the changes and that this is expected behaviour. So they clearly don't think it's a big deal, and they certainly aren't going to start making crazy threats to random people on forums over a headphone volume function lol.
 
FWIW my case was escalated to engineering this morning for a response, I'm not expecting much but I did ask "what car stereo can I buy that will not be affected by this feature". I have a call scheduled for next monday.
 
  • Like
Reactions: VSMacOne
Maybe so, but they have said that they're aware that some bluetooth car stereos and speakers will be affected by the changes and that this is expected behaviour. So they clearly don't think it's a big deal, and they certainly aren't going to start making crazy threats to random people on forums over a headphone volume function lol.
Apple discussion forums are kind of a separate thing where a variety of things sometimes happen there to what people post.

In terms of the particular issue itself, it doesn't really seem that all that would be expected as it doesn't really make much sense in different situations. It sounds like there an oversight in design and/or some bug there somewhere in terms of implementation. It's possible they might not consider it something that is of high priority, but it's hard to tell one way or another.
 
Wat? "I was personally threatened to have my apple ID deleted and ISP blocked if I continued to raise awareness in regards to this issue"

Provide evidence or no I am not supporting this petition. Apple isn't in the business of threatening random customers over issues that it clearly considers trivial.
1607983384659.png
 
Apple discussion forums are kind of a separate thing where a variety of things sometimes happen there to what people post.

In terms of the particular issue itself, it doesn't really seem that all that would be expected as it doesn't really make much sense in different situations. It sounds like there an oversight in design and/or some bug there somewhere in terms of implementation. It's possible they might not consider it something that is of high priority, but it's hard to tell one way or another.

I initially figured it was an oversight but I now suspect it's more like this:

1) Everyone the apple engineers know uses CarPlay and AirPlay speakers
2) There's probably no technical way to accurately tell headphones from other bluetooth devices, pretty sure all you can see is a device name and a list of capabilities
3) For those people using legacy bluetooth (LOL are those guys still around??) we'll put "reduce loud sounds" on the headphone safety screen so they can just limit the volume to 85dB and never see the notifications

Assuming this works, and I suspect it will I just don't have enough data to prove it yet, it's not a terrible solution. I'd still prefer not to have to do it but.. meh.
 
@Panzo You haven't shown us what messages prompted that response from Apple. If you were indeed posting "inappropriate" messages as they suggest then perhaps the warning would be justified. It also suggests they've warned you in the past. If all you did was "raise awareness about the issue" then it's hard to believe that was the response. I suspect it's more likely that you've used inappropriate and inflammatory language.
 
I initially figured it was an oversight but I now suspect it's more like this:

1) Everyone the apple engineers know uses CarPlay and AirPlay speakers
2) There's probably no technical way to accurately tell headphones from other bluetooth devices, pretty sure all you can see is a device name and a list of capabilities
3) For those people using legacy bluetooth (LOL are those guys still around??) we'll put "reduce loud sounds" on the headphone safety screen so they can just limit the volume to 85dB and never see the notifications

Assuming this works, and I suspect it will I just don't have enough data to prove it yet, it's not a terrible solution. I'd still prefer not to have to do it but.. meh.
It's possible, but even with that it's an oversight in the assumptions of what impact a decision to not make something work appropriately can have. Aside form that, it's also a possibility that one way or another this wasn't something that was fully considered/designed or perhaps wasn't fully coded/tested. It's also possible it's known and is something that they didn't wrap up in time for the initial release and decided the changes could come in later. One way or another hopefully they'll do something about it rather than either saying "that's just how it is" or letting it just linger in their backlog.
 
@Panzo You haven't shown us what messages prompted that response from Apple. If you were indeed posting "inappropriate" messages as they suggest then perhaps the warning would be justified. It also suggests they've warned you in the past. If all you did was "raise awareness about the issue" then it's hard to believe that was the response. I suspect it's more likely that you've used inappropriate and inflammatory language.
Things on Apple's discussion forums sometimes happen when people complain about issues that no one can really do much about -- they are bugs or something of that nature that only Apple can do something with if they decide to, which isn't really something that's up for discussion there. That said, what happens on those forums isn't all that important in terms of there actually being an issue and what is or isn't being done about it, as that's fairly separate and different from all that.
 
It's possible, but even with that it's an oversight in the assumptions of what impact a decision to not make something work appropriately can have. Aside form that, it's also a possibility that one way or another this wasn't something that was fully considered/designed or perhaps wasn't fully coded/tested. It's also possible it's known and is something that they didn't wrap up in time for the initial release and decided the changes could come in later. One way or another hopefully they'll do something about it rather than either saying "that's just how it is" or letting it just linger in their backlog.

I hope you're right but tbh I'm not holding my breath. I've made my complaints though via as many channels as possible, and was careful to point out to the rep that having to repeatedly reach for a phone to restore the volume while driving is actually a safety issue in itself.
 
  • Like
Reactions: MentalFabric
@Panzo You haven't shown us what messages prompted that response from Apple. If you were indeed posting "inappropriate" messages as they suggest then perhaps the warning would be justified. It also suggests they've warned you in the past. If all you did was "raise awareness about the issue" then it's hard to believe that was the response. I suspect it's more likely that you've used inappropriate and inflammatory language.
totally inappropriate, how dare i!?
1607984182846.png
 
I hope you're right but tbh I'm not holding my breath. I've made my complaints though via as many channels as possible, and was careful to point out to the rep that having to repeatedly reach for a phone to restore the volume while driving is actually a safety issue in itself.
Yeah, there's no good way to tell one way or another unless Apple (and not even just an engineer or customer care agent) actually acknowledges something in some fashion. There are still a variety of other issues that seemingly quite a lot of people have with messaging and the like, some of which are sort of in a similar state where it's not really known if anything is being done, and other's have had some fixes released in relation to them, although perhaps not ones that are fully working for everyone.
 
Yeah, there's no good way to tell one way or another unless Apple (and not even just an engineer or customer care agent) actually acknowledges something in some fashion. There are still a variety of other issues that seemingly quite a lot of people have with messaging and the like, some of which are sort of in a similar state where it's not really known if anything is being done, and other's have had some fixes released in relation to them, although perhaps not ones that are fully working for everyone.
The reason I'm not very hopeful is that I had a pretty severe issue in Messages - SMS was not being forwarded. I spent hours on the phone with their support going through every suggestion they could come up with, all the icloud stuff, checking stuff on their backend etc etc. Eventually they just said "ok we now think this is a bug, several other users have reported it, it will be fixed in a future software update". Several updates came and went with no resolution. Eventually for other reasons I swapped from an E-Sim back to a physical sim and then back to an E-sim again. As soon as I swapped to the physical sim the forwarding started working again and stayed working when I swapped back to the E-sim. If Apple had actually investigated that bug properly they could have told me that would fix it, but they didn't.

Sadly I think it's now a case of unless there are X threshold of users complaining then they won't do anything about it. You need a very loud voice.
 
Because Apple is slowly rolling it out this way there isn't a big outrage all at once against it
I saw in a YouTube video review earlier today somebody’s iPhone 12 Pro Max on the latest iOS version in the US that still had the option to turn OFF the notifications and it just made me mad again.
 
It almost feels like early adapters to 14.3 are getting EU versions of this in the US.

I see screen shots with a toggle to turn this off and I don't have it, and I'm in the US.
 
I’m just shocked that nobody at MR or other media is making any fuss about this. How is everyone just okay with it?!
I'm okay with it.
Screen shots provided match XCode Sim screenshots and not actual iPhones ( that I have ).
Direct troubleshooting responses have not been replied to on this forum.
I have over 100 test iPhones in my office without this issue.

I listen to music 7-14 hours per day on bluetooth headphones with no issues. I'm old and listen to it quite loud.
I read several people complaining on this thread, which I take seriously.
I currently have over 1000 iPhones in the hands of testers and have not had a single complaint about bluetooth headset volumes. My test devices are MDM managed, I may have a setting turned on/off that prevents the headset notification. My current three iPhone12Pros are not connect to MDM and running on default Apple settings. Reported volume issues are not duplicated on any of those either.

I believe there may be an issue, I just cannot duplicate it to solve it.
 
stumbled across this thread as I have the same issue. I don't mind it being there for "safety" - but give us the option to turn it off. I mean, i can turn the music up again straight away (as much as a pain as it is!) but it kinda makes no sense that the option isn't there to disable it! APPLE - sort it out.
 
  • Like
Reactions: VSMacOne
I'm okay with it.
Screen shots provided match XCode Sim screenshots and not actual iPhones ( that I have ).
Direct troubleshooting responses have not been replied to on this forum.
I have over 100 test iPhones in my office without this issue.

I listen to music 7-14 hours per day on bluetooth headphones with no issues. I'm old and listen to it quite loud.
I read several people complaining on this thread, which I take seriously.
I currently have over 1000 iPhones in the hands of testers and have not had a single complaint about bluetooth headset volumes. My test devices are MDM managed, I may have a setting turned on/off that prevents the headset notification. My current three iPhone12Pros are not connect to MDM and running on default Apple settings. Reported volume issues are not duplicated on any of those either.

I believe there may be an issue, I just cannot duplicate it to solve it.
It’s very inconsistent. The Apple explanation for which devices have this “feature” enabled is junk.
 
I'm okay with it.
Screen shots provided match XCode Sim screenshots and not actual iPhones ( that I have ).
Direct troubleshooting responses have not been replied to on this forum.
I have over 100 test iPhones in my office without this issue.

I listen to music 7-14 hours per day on bluetooth headphones with no issues. I'm old and listen to it quite loud.
I read several people complaining on this thread, which I take seriously.
I currently have over 1000 iPhones in the hands of testers and have not had a single complaint about bluetooth headset volumes. My test devices are MDM managed, I may have a setting turned on/off that prevents the headset notification. My current three iPhone12Pros are not connect to MDM and running on default Apple settings. Reported volume issues are not duplicated on any of those either.

I believe there may be an issue, I just cannot duplicate it to solve it.
Try setting iPhone volume to 100%. When I did that, using it for the first time in the week having not been out due to covid, it only took half an hour for the volume to reduce.
The issue primarily effects people who need to set the volume to 100% on iPhone and control the actual volume on the bluetooth device.
 
Not sure this is among the many pages of threads but I have a sort of similar issue. If I use carplay then the ringer volume on my phone gets reduced to almost nothing and I have to raise it after I leave car or I won't hear any notifications. Very frustrating

ACTUALLY found this happens with Bluetooth connection and not just car play - almost as if it is lowering to match volume control on car and then leaving it there
 
Last edited:
Not sure this is among the many pages of threads but I have a sort of similar issue. If I use carplay then the ringer volume on my phone gets reduced to almost nothing and I have to raise it after I leave car or I won't hear any notifications. Very frustrating
That’s a whole different problem. Nonetheless a frustrating one, it’s been like that for me since the 3G. Obviously not with CarPlay, but in general when switching output devices connected to an iPhone. I’ll just wait another decade, maybe, who knows. 😂😂😂
 
I live in the USA. My wife and I purchased the iPhone 12 Pro Max 512gb phone. The only difference is hers is blue and mine is gold. We are both running 14.3. Her phone has the ability to turn off the notification and mine does not. We purchased at the same time, had them shipped at the same time and activated them at the same time. This is OBVIOLUSLY NOT regional. Unless you are claiming one part of my house is in a different region then the other! LOL I do NOT listen to my headphones loud enough to have this happen. It happens every time I listen to music in my car or over bluetooth speakers.
 
I live in the USA. My wife and I purchased the iPhone 12 Pro Max 512gb phone. The only difference is hers is blue and mine is gold. We are both running 14.3. Her phone has the ability to turn off the notification and mine does not. We purchased at the same time, had them shipped at the same time and activated them at the same time. This is OBVIOLUSLY NOT regional. Unless you are claiming one part of my house is in a different region then the other! LOL I do NOT listen to my headphones loud enough to have this happen. It happens every time I listen to music in my car or over bluetooth speakers.
Were both set up the same way (backup restored, iCloud, etc.)?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.