Workaround for using L2CAP connection

[arandomhooman]

Hello,
Could you implement this workaround, similar to how CApods did? Allow users to provide the Idenity and Encryption key. Link to explanation from CApods: https://github.com/d4rken-org/capod/wiki/airpod-Keys

[kavishdevar]

Hi!

This is just for LE advertisments, not L2CAP. LibrePods gets the keys from AirPoda and uses for automatic connections and battery status when they're connected to another device. CAPod is the way to go for non-rooted devices. You can get the keys from Linux/Mac/Windows.

[arandomhooman]

@kavishdevar Interesting. Have you tried pushing a commit with this change to AOSP and adding everyone in OWNERS file as a reviewer? That could get some eyes on this. The IssueTracker post will liekly never get addressed, it's in the generic framework category, not even the Bluetooth category.

I also emailed some android news publications and messages Mishaal to see if I can get some people to report on this. Long shot, but who knows.

[kavishdevar]

Have you tried pushing a commit with this change to AOSP and adding everyone in OWNERS file as a reviewer? That could get some eyes on this. The IssueTracker post will liekly never get addressed, it's in the generic framework category, not even the Bluetooth category.

Nope, not yet. But only because I don't know much about Fluoride, and I don't know what the best fix would be for this. I am busy with my entrance exams for a few months, I'll see what I can do after that. Though, someone working on LineageOS has suggested a patch, but I don't have the sources downloaded to test it.

I also emailed some android news publications and messages Mishaal to see if I can get some people to report on this. Long shot, but who knows.

Thank you! Hopefully someone at Google decides to take a quick look and makes a very simple workaround, if not a proper fix.

[arandomhooman]

Yep. I may try commiting it to AOSP (with your blessing if you are fine with it, ofc will give you credit). Don't worry about making it the perfect fix, they likely won't accept it anyway because they have to run tons of tests, and need to make sure it works on all devices. However, I very well may put it on the radar of the people who work on Bluetooth.

But yeah, hopefully a publication picks it up. If not, il try a few other things.

p.s. you probably don't remember me, but I remember coming to this repo when it was wayyy smaller and asking you to set up Sponsors lol

[kavishdevar]

Yep. I may try commiting it to AOSP (with your blessing if you are fine with it, ofc will give you credit).

That would be amazing! I don't really mind the credit, I haven't done anything but found the problem, and not the fix :)

Don't worry about making it the perfect fix, they likely won't accept it anyway because they have to run tons of tests, and need to make sure it works on all devices. However, I very well may put it on the radar of the people who work on Bluetooth.

I see. Someone suggested adding this to existing interop logic, I will ask a few people if they can test that.

you probably don't remember me, but I remember coming to this repo when it was wayyy smaller and asking you to set up Sponsors lol

I absolutely do remember (and every other supporter to get to their issues quickly)- thank you very much! :D

[arandomhooman]

@kavishdevar some of my efforts were fruitful: https://www.androidauthority.com/android-bug-breaking-airpods-app-3623860/

"We’ve asked Google about this bug and if it has a timeline for a fix. We’ll update the article as soon as the company responds to our query."

[arandomhooman]

Also, check the email listed in your bio!