apple doesn't allow much customization, only the 9 presets under accessibility>hearing>headphone accomodation. this eq then also applies to the audio played and transparency settings both. maybe one of those nine presets suits your needs?
setting up hearing aids is a one time thing. then, the main adjustment is the amplification, which can be controlled by swiping on the stem. there is no need for an iphone for using it as hearing aids.
The developer here- I didn't plan to release an app for android, or even linux. The android app just started out as a personal project. My plan was to make a service for linux that can talk to various headphones, and any UI can talk to the service. And this was supposed to be under AGPL. But, as I graudally reverse-engineered most of the protocol from the bluetooth stack on macOS, I decided to release the app for Android and make one for linux as well.
Going to change it to GPL, though. never paid attention to the license in use as I developed.
Thanks for the direct reply. I didn't consider the SaaS angle when I wrote my original post. As a result, your initial license choice makes sense. Also, if you are in control of copyright for all of the source code, then you can easily change the license. I am still blown away by how you did it. It must have been a lot of reverse engineering! Hats off -- keep up the good work.
the head gestures is something i couldn't quite figure out, so the gesture logic is completely AI generated. i don't know how to get the actual values from the sensors. but there sure is a use in gaming.
i don't think macos allows l2cap connections (the protocol that airpods use), at least pybluez doesn't support that on macos which would've made making a simple script a lot simpler.
see MagicPods. although, it's paid, and requires windows to be in test mode to install a driver for L2CAP support. microsoft has decided to not allow l2c for userspace applications.
hey, do you have the 'act as apple device' hook enabled perhaps? that sometimes causes connections to drop. other than that, i believe i refactored the background service to store metadata about the airpods and support various model types recently which can make the app a bit unstable, hence no new release yet- the build is available to download from Actions. if you're facing unstability on the latest (pre)release, v0.2.0-alpha open a issue, i will have a look whenever i get the time.
about the configs not being saved- do you mean the conversational awareness, adaptive volume etc.? those should be saved, and sent from airpods every time you connect. so if you change the config from any other device, and connect to your phone then the app should show the new config.
you can contirbute by supporting the development, of course! :)
