mirror of
https://github.com/kavishdevar/librepods.git
synced 2026-04-24 23:55:52 +03:00
[GH-ISSUE #227] linux: add hearing aid feature #104
Labels
No labels
android
bug
documentation
enhancement
good first issue
help wanted
linux
pull-request
reverse-engineering
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/librepods#104
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ressiwage on GitHub (Oct 8, 2025).
Original GitHub issue: https://github.com/kavishdevar/librepods/issues/227
i have a small feature request, is it possible to add hearing aid support to linux? for me it is highly important and i think there are many people who suffer from hearing loss but struggle to root their device. As for me cool ui is unneccessary, just sliders or number inputs would be enough. Installing librepods on linux is much easier than install it on rooted android
@kavishdevar commented on GitHub (Oct 15, 2025):
Sure thing! There's just one small caveat- if you change the DID profile info in the BlueZ config to Apple’s, you might get connection issues with AirPods. If AirPods know it's an Apple device, it allows multiple devices to connect and then your Apple device does something that can cause Linux to disconnect unless some specific information is sent to the iDevice.
Also, do you have an audiogram result available? Because I don't have any ideas on how to implement hearing tests as it needs much more precision and accuracy.
@kavishdevar commented on GitHub (Oct 15, 2025):
also, I might be making it a different Python script. I don't want to mess with the main app because this requires a different connection (ATT) than the one used for controlling other stuff (AACP).can't do that because enabling hearing aid needs AACP, and so does "Swipe to control amplification".
@ressiwage commented on GitHub (Oct 15, 2025):
yes i do, from a hearing therapist. it looks like that
If you ask me what is primary, I would say that a hearing test is less necessary than manual hearing aid regulation because, in my opinion, people with hearing issues usually already have an audiogram.
@kavishdevar commented on GitHub (Oct 15, 2025):
Ah, alright. I added the adjustments, and a toggle for hearing aid (linux/hearing-aid branch) because that's what I had already implemented in Android. I am yet to add the loss information. I'll add it in a few (~8-10) hours.
@kavishdevar commented on GitHub (Oct 15, 2025):
Also, I am not sure how the bone and air info is sent to the AirPods. I have seen only a single set of data sent per ear. I am also in a region where the feature's not supported, so can't test myself.
@ressiwage commented on GitHub (Oct 15, 2025):
i heard that you can change the region in apple id just entering some random address, didn't check it out, maybe you can try
@kavishdevar commented on GitHub (Oct 15, 2025):
@ressiwage, done! will add it to the main app later, but for now, it's a python script in the linux folder. Run it with the MAC of your AirPods.
@kavishdevar commented on GitHub (Oct 15, 2025):
forgot to mention this earlier- you need to change the
DeviceIDin BlueZ config at/etc/bluetooth/main.conftobluetooth:004C:0000:0000for this to work.@ressiwage commented on GitHub (Oct 15, 2025):
kinda strange, i do not notice changes with any values of sliders and loss inputs. Tried in different modes (adaptive, transparency, noise reduction), i think the error may be in message "read data too short for sending settings".
log:
@kavishdevar commented on GitHub (Oct 15, 2025):
@ressiwage sorry, forgot to mention- you need to restart the bluetooth service with
sudo systemctl restart bluetooth, and then probably re-pair your AirPods because they cache this information and do not check for it every connection.@ressiwage commented on GitHub (Oct 15, 2025):
@kavishdevar now the output is different, but sadly no changes. the app initializes with 0.00 values every time, which can indicate that settings are not saved
@kavishdevar commented on GitHub (Oct 15, 2025):
Could you please try setting some random values for each, amplification, balance etc. and see what it sends? Not sure why it's sending everything set to zero. For me, I reset the value to all zeroes, and then restarted the script and changed a frequency and it seems to be sending the correct data.
@kavishdevar commented on GitHub (Oct 16, 2025):
closed by #230
@leotor13 commented on GitHub (Oct 26, 2025):
Also having the issue that entering any values return data being too short unfortunatly. Tried setting them all to 0 and also resetting bluetooth adapter and unpairing airpods.
ERROR - Read data too short for sending settings