Assigned
Status Update
Comments
vi...@google.com <vi...@google.com>
vi...@google.com <vi...@google.com> #2
Also confirmed issue persists on 4.4.
de...@gmail.com <de...@gmail.com> #3
There are a lot of expensive accessories I've purchased or been gifted that quit workin with android 4.2. Android devs need to get on this. 3 broken versions and numerous minor updates and it hasn't even been triaged yet. Completely unprofessional.
vi...@google.com <vi...@google.com> #4
We are loyal to Android as and they treat us like this.. I have a google device and yet it still is not fixed.
de...@gmail.com <de...@gmail.com> #5
Please fix
vi...@google.com <vi...@google.com> #6
Yes, please fix it. =)
de...@gmail.com <de...@gmail.com> #7
I abandoned iPhone to discover something better, but I'm finding a lot of my Bluetooth paired devices won't work properly on android... I hope this gets fixed soon. I don't want to have to buy an iPhone again and suffer with their long agreements and system restrictions.
de...@gmail.com <de...@gmail.com> #8
[Comment deleted]
de...@gmail.com <de...@gmail.com> #9
fix will ya? make the android better more
de...@gmail.com <de...@gmail.com> #10
Yes, count me as someone who would like to see this fixed. It apparently isn't fixed in KitKat.
ho...@gmail.com <ho...@gmail.com>
sc...@gmail.com <sc...@gmail.com> #11
I have two nexus devices and this is a regular issue. The kid can't play games properly. Way to replace a working stack with a subpar homebrewed one.
de...@gmail.com <de...@gmail.com> #12
Please roll back previous API. This fratura is importante.
de...@gmail.com <de...@gmail.com> #13
Android 4.3 killed my super mario :(
re...@gmail.com <re...@gmail.com> #14
Please fix, pretty please
ma...@gmail.com <ma...@gmail.com> #15
I have a device that worked fine with Bluez and now is broken with Bluedroid. Please add support for devices requiring L2CAP connectivity. From the logs, it seems to try and run L2CAP over GATT/ATT even with devices that are not BLE.
Thanks
Thanks
de...@gmail.com <de...@gmail.com> #16
Please fix this!! We want to play with us wii u pro controller!! C'mon Google!!
de...@gmail.com <de...@gmail.com> #17
PLEASE GOOGLE, LET US HAVE BLUETOOTH FREEEEEEEEDDDDOOOOOOOOOOOOOOOOOOM!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
de...@gmail.com <de...@gmail.com> #18
Google, please fix this issue. many games are unplayable with said issue.
za...@gmail.com <za...@gmail.com> #19
Please google, can someone please fix this issue. thanks
de...@gmail.com <de...@gmail.com> #20
Would love to see this resolved. Like a handful of others on here I just wanted to sync a bluetooth controller to my Android device to play some games. (I'm not very good at Megaman X with the touchscreen). I know it isn't a huge system issue, but maybe it could be changed anyway?
Games already look great on the Note 3, would be better with my controller.
Thanks in advance!
Games already look great on the Note 3, would be better with my controller.
Thanks in advance!
ts...@gmail.com <ts...@gmail.com> #21
Just want to play some Bayou Billy for nes on my Note 3 with wiimote controller please.
Description
I (among others) have reverse engineered airpods, and I am working on implementing features on linux, and android. But there is a bug in Flouride.
In the file , it sends some packet to check for Extended Flow Control, but the airpods will not respond with anything until a specific handshake packet is sent. There is also another check performed for this very thing in l2c_fcr.cc from lines 1605 to 1610 .
l2c_link.cc
, on line 118When I try to create a l2c socket from a user app, it blocks the thread and throws an ANR. So for testing purposes, I commented this line and this check performed for extended flow control too. And I rebuilt the
libbluetooth_jni.so
and replaced it using root. And... It worked, I could create a docket and communicate with the airpods!This, of course, is a temporary fix. Maybe the send packet function shouldn't block if it is sending this particular packet, and should return if no response is received from the peer. But I believe people maintaining the code are much smarter than me, so I'm sure there'll be a better solution :)
Hoping this issue gets resolved quickly!