Strange audio routing issue with new Iphone SE and IOS 13.
I'm currently having an issue with my new IPhone SE when making calls with headphones plugged into a standard 3.5 mil jack, going into the phone via a 2-in-1 lightning adapter. All the other audio coming from my phone goes through my headphones just fine, but when I use Siri to make a Facetime audio call, it switches either to the phone speaker, or the ear piece. I’ve selected each of the 3 options in call audio routing with no luck what so ever.
Is this a known bug? Am I missing something? Could it have something to do with the fact that I’m using an adapter? Any and all help is appreciated.
Did you update your iOS version when you got the phone? It was announced the other day that a special iOS 13.4.1 release had been made for the new SE, presumably because the phone had shipped with iOS 13.4. So if you haven't checked for updates, you might want to. Not to say that this will solve your problem, but maybe it will…
I updated to 13.4.1 earlier today, and sadly no luck.
I think is a bug. Using 11 pro max and when I connect my earpodor AirPod no issues.
I have the same problem with Siri when I use it for other commands. I get the wake sound in my headphones, and then the response in my speakers. It does look like a bug. I wonder if other people will start encountering it.
I always assumed this is a bug with a lightening adapter and IOS. I have to plug in the lightening adapter twice until the phone audio goes through my ear piece. Also, if I walk out of range of my wi-fi network and someone is talking to me on my earpiece connected through the lightening port it will automatically switch back to speaker phone.
Sadly that hasn't worked for me. I tried plugging and unplugging both the lightning adapter and the headphone jack itself on all of the settings within Call Audio Routing, and no luck. If it is a bug, I hope it's not around for long. How long has your phone been acting in the way it has?
in my oppinion, the best way to report bugs to Apple is to Beta Test. it's not for everyone. but you have direct contact with Apple engeneers, weither if you are on the public betas or the developer betas. sometimes, they brake things, and things do not work. but if your okay with that, then Apple engeneers will fix them most of the time.
If I had another device that I could use as a backup for when things broke, I think I'd feel a lot less anxious about being a part of a beta program. As it stands, I'm too much of a scaredy cat with only 1 device running 13. My days would be filled with frustration and worry that I wouldn't be able to get my work done efficiently .
I have encountered this as well, although I am not using an adapter. I have had it with the actual lightning earpods. A call comes in while I am on another call, and when I switch over to answer it, it sends the audio to speaker for seemingly no good reason. I also hope this is fixed sooner rather than later.
I've been able to replicate the bug without the use of Siri. How long has it been around for you? I've been able
The problem is with the adapter.
Most lightning to 3.5 mm adapters, (Including the Apple one), only recognise 3 polls of a 4 pole headphone plug. This means that you can listen to audio Fine but you cannot use the Mike of the headphones or indeed any in-line remote-control. It will only use the microphone in the phone.
This was annoying me for weeks after upgrading to my new iPhone 8 and I have been trying to find a Solution.
There are a a few adapters which do utilise all 4 polls of the plug but these are slightly more expensive. The one I have at The moment which works really well is The Opso headphone adapter which you can get for around £15.
This does not let you charge at the same time as the 2 in 1 adapters do however you can get very inexpensive Lightning splitters from Ebay for about £2.50 which allow you to plug the headphone adapter and the charging cable in at the same time. This works with the Opso adapter I mentioned above.
Hope this helps
Hope you have found a solution to this problem. The solution I recommended is still working great for me.