if this is the wrong place, please point me to the right one.
Background
I recently bought 2 Fairphone 6 for my parents and while I myself use LineageOS quite heavily, I decided on /e/ for them, mainly due to the fact that there is no current LineageOS version supporting FP6. So while I’m generally willing and able to use non-stock ROMs, I lack experience with /e/
Problem
On his previous phone (a Pixel 3XL with LineageOS) my dad heavily used the ASHA feature, unfortunately this doesn’t seem to be supported by /e/ right now.
Possible Solution
I respectfully request that /e/ developers take the time to implement this important accessibility feature into the OS so that devices that support it (as the FP6 arguably does) can be fully used.
Thank you very much for taking the time to consider my request.
The situation is a bit complicated by the fact that my dad lives > 100km away so I’ll have to try to guide him through this via phone but I’ll have him check and report back.
Here we can’t change anything except allowing access to contacts and caller list or changing the device name.
So far we have confirmed, that the hearing aids can be coupled via BLE and are recognized (correctly) as hearing aids. However, no sound gets transmitted to them, if he receives a call or wants to listen to music the sound comes out of the phone’s speaker instead of the hearing aids.
Right now I’m hoping we just overlooked some kind of setting telling the phone how to route audio signals.
We also disconnected and reconnected the hearing aids, to no avail. (By me giving him instructions via Threema messenger app. I must have sinned horribly in a previous life…)
If you have any idea what we could try next I’d be grateful.
Edit: I got basic permissions so I could edit in the missing images
Hi @laird_dave have an update from the developers. As mentioned, we are working on this issue.
It is related to the LE audio which is a next gen wireless Bluetooth audio standard designed for superior audio quality, ability to stream on multiple devices and battery efficient. The core reason is LE audio not working properly when access through the code in the phones.
For now, there are no ETAs. Will share the dates when I get some updates from the team.
Thank you @Manoj, I’ll be looking forward to this. I found another possibility and now I’m waiting on my dad checking it out and getting back to me with this info, potentially there is a workaround for the time being. No clue if this works out so I’ll post an update once I hear back from him.
The GitLab issue was raised 7 months ago and there doesn’t appear to be any developer comments there at all yet. It’s unfortunate, but this limited feedback from the developers, and no ETA, feeds the impression that it’s not seen by them as a priority, not good considering the negative impact on hearing aid users.
Have posted the comments on the shared links. I would like to reassure all that the developer is working on this. The no ETA part is because we have multiple tasks assigned and some which need detailed testing on different devices like ASHA implementation can take extra time.
Will share updates. You can always ping me for latest status in case I miss sharing about the progress.
Search 
