Hacker News new | past | comments | ask | show | jobs | submit login

IIRC Android uses a regular Linux Bluetooth stack.

Also WRT your problems: In case you did not yet, switch to Pipewire. When I did that a couple of years ago, my BT Audio experience went from bad to really good.




I don't think android uses Bluez, android moved away from bluez a long time ago for their own custom bluetooth stack.

https://source.android.com/docs/core/connect/bluetooth


Android uses Fluoride - which coincidently has now come to ChromeOS. And yes, they named the migration "Project Floss".

https://chromeos.dev/en/posts/androids-bluetooth-stack-fluor...


It can be very device dependent, or even on which mode the device is in dependent.

For example, I have JBL headphones, that work perfectly in the A2DP mode; but switch to HFC for the mic, they will work for a few minutes, then drop off and stay that way until reboot.

That's with Ubuntu. With Android, no such problem.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: