Assigned
Status Update
Comments
vi...@google.com <vi...@google.com> #2
Also confirmed issue persists on 4.4.
lu...@gmail.com <lu...@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.
ra...@google.com <ra...@google.com>
pa...@google.com <pa...@google.com>
pa...@google.com <pa...@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.
lu...@gmail.com <lu...@gmail.com> #5
Please fix
98...@gmail.com <98...@gmail.com> #6
Yes, please fix it. =)
al...@gmail.com <al...@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.
pr...@gmail.com <pr...@gmail.com> #8
[Comment deleted]
j....@gmail.com <j....@gmail.com> #9
fix will ya? make the android better more
na...@gmail.com <na...@gmail.com> #10
Yes, count me as someone who would like to see this fixed. It apparently isn't fixed in KitKat.
vo...@hotmail.com <vo...@hotmail.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.
ko...@gmail.com <ko...@gmail.com> #12
Please roll back previous API. This fratura is importante.
pi...@gmail.com <pi...@gmail.com> #13
Android 4.3 killed my super mario :(
th...@gmail.com <th...@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
ed...@gmail.com <ed...@gmail.com> #16
Please fix this!! We want to play with us wii u pro controller!! C'mon Google!!
gu...@gmail.com <gu...@gmail.com> #17
PLEASE GOOGLE, LET US HAVE BLUETOOTH FREEEEEEEEDDDDOOOOOOOOOOOOOOOOOOM!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
sh...@gmail.com <sh...@gmail.com> #18
Google, please fix this issue. many games are unplayable with said issue.
em...@gmail.com <em...@gmail.com> #19
Please google, can someone please fix this issue. thanks
mo...@gmail.com <mo...@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!
lu...@gmail.com <lu...@gmail.com> #21
Just want to play some Bayou Billy for nes on my Note 3 with wiimote controller please.
mo...@gmail.com <mo...@gmail.com> #22
[Comment deleted]
bj...@gmail.com <bj...@gmail.com> #23
I was really upset when I went to use a feature that used to work perfectly, this is stupid, what gives Google?
st...@gmail.com <st...@gmail.com> #24
I, like many others, wish to enjoy computer gaming nostalgia via excellent emulators. Please fix my first world problem...
na...@gmail.com <na...@gmail.com> #25
Please fix. This is really dissapointing and I think I'm switching to Apple.
ma...@gmail.com <ma...@gmail.com> #26
Several Android devices and several Android versions from 4.2 to 4.4 : I cannot use m'y game contrôler I bought especially for my first Android phone under 2.2. Please fix !!
vi...@google.com <vi...@google.com> #27
Blue Tooth has been broken for nearly a year. How is that even a thing that is? This is how your lose paying customers, Google.
fc...@gmail.com <fc...@gmail.com> #28
Please support Bluetooth L2CAP. This is important to me. It's hard to believe the famous Android lacks such a basic Bluetooth function.
sa...@google.com <sa...@google.com>
pi...@hotmail.com <pi...@hotmail.com> #29
Still don't work...
es...@gmail.com <es...@gmail.com> #30
Please fix this.
mt...@gmail.com <mt...@gmail.com> #31
Waht is the big deal?
Please fix this already!
Please fix this already!
ra...@gmail.com <ra...@gmail.com> #32
[Comment deleted]
ra...@gmail.com <ra...@gmail.com> #33
Please fix this. I want to pair my Wiimote with my Android phone and tablet.
go...@gmail.com <go...@gmail.com> #34
Please repair this issue
al...@gmail.com <al...@gmail.com> #35
I cant pair my wii remote with my new smartphone android, please fix this. :) thanks
dj...@grailbio.com <dj...@grailbio.com> #36
Please fix this if you can.
be...@gmail.com <be...@gmail.com> #37
I would like see this fixed too. It's extremely poor business practice to break compatibility with a software update and not address it in last three versions.
ra...@gmail.com <ra...@gmail.com> #38
As a fellow Android user interested in this bug, I strongly agree that it should be fixed. However, by starring the issue, you've already expressed an interest in it being fixed, so it's unnecessary to add a comment saying the same thing. None of the recipients of the comments (user or developer alike) benefit from the added noise. I humbly request that instead of commenting, share this bug with your friends and get them to star it as well, or start a petition. Thanks in advance.
lo...@gmail.com <lo...@gmail.com> #39
can't connect almost any peripheral I own VIA BT after the 4.4 update. Hardware supports it, but your software has disabled it at a core level that even root level changes cannot provide a solution. I know you want us all to buy new toys, but some of these don't have proper new replacements!!!
ya...@gmail.com <ya...@gmail.com> #40
Wish my wiimote worked on my droid tablet
rs...@gmail.com <rs...@gmail.com> #41
[Comment deleted]
pe...@gmail.com <pe...@gmail.com> #42
Comment has been deleted.
ze...@gmail.com <ze...@gmail.com> #43
Solve this problem
lu...@gmail.com <lu...@gmail.com> #44
Can anyone tell us why this issue is still here, or why L2CAP support was turned off in the first place?
se...@gmail.com <se...@gmail.com> #45
I poked around with the same question. It seems to be the case that L2CAP
was never officially supported. In fact, in some forums, there were
warnings that non-API calls like this were prone to disappear in the
future. That being the case, this is more appropriately called a feature
request than a bug.
Access to L2CAP disappeared when the Linux Bluetooth stack blueZ was
replaced by the Broadcom-built library, BlueDroid. I couldn't find any
online justification for the library swap. Maybe security, maybe
reliability. It is open source though. You can dig through the source and
find the low-level implementation of L2CAP (RFCOM builds on top of it) and
see what it takes to expose the connection. I did this a few months ago
and saw it promised to be non-trivial.
turned off in the first place?
was never officially supported. In fact, in some forums, there were
warnings that non-API calls like this were prone to disappear in the
future. That being the case, this is more appropriately called a feature
request than a bug.
Access to L2CAP disappeared when the Linux Bluetooth stack blueZ was
replaced by the Broadcom-built library, BlueDroid. I couldn't find any
online justification for the library swap. Maybe security, maybe
reliability. It is open source though. You can dig through the source and
find the low-level implementation of L2CAP (RFCOM builds on top of it) and
see what it takes to expose the connection. I did this a few months ago
and saw it promised to be non-trivial.
turned off in the first place?
lu...@gmail.com <lu...@gmail.com> #46
I know that in in the rest of linux bluez just recently had a major version change and many utilities which worked well with the previous version are broken until their maintainers update their code for the new version.
That being said perhaps this change promised to break a lot of stuff for droid, or at the very least cause power consumption concerns. I haven't looked at bluez code, but it its also possible there might have been some issues with how the new version plays on ARM architecture. (to the best of my knowledge bluez is primarily written for x86 which is found on most PCs but NOT any smartphone and few if any tablets)
This is all purely speculation on my part and would need verification from someone far more knowledgeable than I.
Would anyone be able to shed more light on the issue?
That being said perhaps this change promised to break a lot of stuff for droid, or at the very least cause power consumption concerns. I haven't looked at bluez code, but it its also possible there might have been some issues with how the new version plays on ARM architecture. (to the best of my knowledge bluez is primarily written for x86 which is found on most PCs but NOT any smartphone and few if any tablets)
This is all purely speculation on my part and would need verification from someone far more knowledgeable than I.
Would anyone be able to shed more light on the issue?
al...@gmail.com <al...@gmail.com> #47
Fix this please. I will have no choice but to switch to another OS if it not fixed.
lu...@gmail.com <lu...@gmail.com> #48
I miss this functionality. I used it on my old android 2.1 and it worked fine. I wish it would work with my newer 4.4.2 phone. I don't understand why something that used to work breaks with updates.
ra...@gmail.com <ra...@gmail.com> #49
Seems google is getting a reputation for things like this. Hopefully they
work to correct it
work to correct it
lu...@gmail.com <lu...@gmail.com> #50
Alright so I'm on a nexus 7 rooted and running the latest official build of CyanogenMod 11 and before I flashed cm it always asked for a password when trying to connect a wiimote via straight Bluetooth and now that I'm running cm it connects to on without asking for a pin. So I'm wondering if there's an app on Google play that will make android accept its input as a native gamepad. Anyone know of such a thing?
mi...@gmail.com <mi...@gmail.com> #51
Google! Fix this please! This is ridiculous!
gr...@gmail.com <gr...@gmail.com> #52
wtf
Bought a TabPro 8.4 to play some games only to discover it won't work with my Wii U Pro Controller.
What a waste of money. Come the fuck on, Google!
Bought a TabPro 8.4 to play some games only to discover it won't work with my Wii U Pro Controller.
What a waste of money. Come the fuck on, Google!
gr...@gmail.com <gr...@gmail.com> #53
Help!
je...@gmail.com <je...@gmail.com> #54
Please fix this issue, thank you
ra...@gmail.com <ra...@gmail.com> #55
Might need at least another 1800 folks before google takes this seriously
an...@gmail.com <an...@gmail.com> #56
Fix it please
an...@gmail.com <an...@gmail.com> #57
Fix please!
fi...@gmail.com <fi...@gmail.com> #58
[Comment deleted]
30...@gmail.com <30...@gmail.com> #59
Please work to correct this.
co...@gmail.com <co...@gmail.com> #60
Fix it please.
da...@gmail.com <da...@gmail.com> #61
Though I really want this to be fixed, it probably won't cause Google.
da...@gmail.com <da...@gmail.com> #62
Lads(Google), go on and fix this. Would like to be able to use BT devices on Nook again
jb...@gmail.com <jb...@gmail.com> #63
Does anyone know if this has finally been addressed in Android 5.0 Lollipop?
we...@gmail.com <we...@gmail.com> #64
Please fix!!!!
mi...@gmail.com <mi...@gmail.com> #65
[Comment deleted]
lu...@gmail.com <lu...@gmail.com> #66
Why has this not been fixed??
ta...@gmail.com <ta...@gmail.com> #67
Comment has been deleted.
ta...@gmail.com <ta...@gmail.com> #68
please fix this
ra...@gmail.com <ra...@gmail.com> #69
another fix request!! common google!!
ni...@gmail.com <ni...@gmail.com> #70
kk...@gmail.com <kk...@gmail.com> #71
[Comment deleted]
al...@gmail.com <al...@gmail.com> #72
Please, fix it.
I want use my bluetooth !!
I want use my bluetooth !!
re...@gmail.com <re...@gmail.com> #73
Cant use my wiimote on galaxy s4 due to this issue. :( Hope it gets fixed...
Just happy that i also have an ipad where it works perfectly for the time till here maybe happens something.
Just happy that i also have an ipad where it works perfectly for the time till here maybe happens something.
br...@gmail.com <br...@gmail.com> #74
Any updates here?
jg...@gmail.com <jg...@gmail.com> #75
Come on fix it plz!!!
dn...@gmail.com <dn...@gmail.com> #76
Christmas present for your loyal fans, Google? Pleeeeeeeeeeeeeeeeeeeeeease fix this. Thanks!
an...@gmail.com <an...@gmail.com> #77
Jesus, why hasn't this been fixed already? What are you doing, Google? Why don't you want Nintendo controllers to work on Android? Do you have beef with Nintendo or something? Screw Xbox and Playstation controllers, the Wii U Pro Controller is the best controller ever made. Just take a minute and fix it so we can use this controller on Android.
ga...@gmail.com <ga...@gmail.com> #78
Houhou! Please fix it!
cl...@gmail.com <cl...@gmail.com> #79
Since submitting this issue I've learned how to solder and converted my non-working bluetooth devices into working USB controllers. Thanks for motivating me to better myself, if anything else ;p
da...@gmail.com <da...@gmail.com> #80
Please correct this issue.
ki...@gmail.com <ki...@gmail.com> #81
I Want to use my Wiimotes with my Tablet Expedia Z2.
PLEASE Fix this issue
PLEASE Fix this issue
tb...@gmail.com <tb...@gmail.com> #82
It´s easy earn money when you have your clients happy, for this google you should let they play with the bluetooth divices like in jelly bean. It is ease for you and you can make many people happy and enjoy with his old controllers.
ba...@gmail.com <ba...@gmail.com> #83
I am unable to connect. Wii remote to emulator due to this bug in 4.4 please fix!
ps...@gmail.com <ps...@gmail.com> #84
Please resurrect the fucntion. Google! If not so I have to develop my H/W for ios only.
sw...@gmail.com <sw...@gmail.com> #85
why is this still unfixed ? it seems like many people have such issues with bluetooth; me included?? tried different ways to connect wii controllers to my brand new one plus one and none of them worked... please its my first smartphone which is able to let me play games and i cant even play them with a bt controller... God of Android pleasy dont disappoint us :)
br...@gmail.com <br...@gmail.com> #86
Not impressed with how long google take to fix a defect.
jj...@gmail.com <jj...@gmail.com> #87
[Comment deleted]
pr...@gmail.com <pr...@gmail.com> #88
What they said.
ra...@gmail.com <ra...@gmail.com> #89
Really need to fix this, this is a deplorable state :(
na...@gmail.com <na...@gmail.com> #90
So my options appear to be downgrade to an old version or get an iPad.
cz...@gmail.com <cz...@gmail.com> #91
Please fix this. I want to be able to use my wiimote again and other Bluetooth devices.
ni...@gmail.com <ni...@gmail.com> #92
I echo the sentiments of everyone else. Please fix this issue.
an...@gmail.com <an...@gmail.com> #93
For the love of Linus, Google, fix this nonsense.
em...@gmail.com <em...@gmail.com> #94
please fix it!
jo...@gmail.com <jo...@gmail.com> #95
I want to use L2CAPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP!
ra...@gmail.com <ra...@gmail.com> #96
Yes please!
sh...@gmail.com <sh...@gmail.com> #97
I am amazed this is still an open issue after more than 1 year and a half. Come on Google!
in...@gmail.com <in...@gmail.com> #98
A quick comment on this for everybody here who think this is a defect or a bug, it's not. Google changed the Bluetooth stack(from Bluez to Bluedroid) in 4.2, this stack does not include the L2CAP protocol in Classic Bluetooth but it does in BLE.
Although does is not a bug, it would be very helpful if L2CAP gets implemented again.
Although does is not a bug, it would be very helpful if L2CAP gets implemented again.
co...@gmail.com <co...@gmail.com> #99
Hi Ronald, that is the definition of a regression :-) Functionality was there, now it's not. Plus, as the request shows, L2CAP support is available in the new stack.
le...@60228.dev <le...@60228.dev> #100
Please implement L2CAP
ma...@gmail.com <ma...@gmail.com> #101
Please address this. I want to be able to use my wiimote in the new version of android.
mt...@gmail.com <mt...@gmail.com> #102
Please please Google fix this so it's compatible AGAIN with Wiimotes!
do...@gmail.com <do...@gmail.com> #103
Please add L2CAP support.
ar...@gmail.com <ar...@gmail.com> #104
This is needed badly.
j9...@gmail.com <j9...@gmail.com> #105
iOS can function with peripherals just fine! why does android (OPEN SOURCE) get locked out.
ma...@gmail.com <ma...@gmail.com> #106
Can anyone confirm if this issue is fixed under Android 5.0 Lollipop?? (Although I don't think Samsung Galaxy Note 10.1 will ever get such update :-( GABRIEL
nu...@gmail.com <nu...@gmail.com> #107
still not fixed in the lollipop 5.0 update. Lame Google, very lame.....
cr...@gmail.com <cr...@gmail.com> #108
Can't believe this issue isn't fixed yet...
Google get your crap together!!
Google get your crap together!!
uf...@gmail.com <uf...@gmail.com> #109
STATUS NEW? my balls! wtf
please bring back bluez since it has new nice features!
SWITCH BACK TO BLUEZ AND DROP BLUEDROID, GOOGLE-DEVS!
Fix this triaged FATAL HIGH PRIORITY BUG!
please bring back bluez since it has new nice features!
SWITCH BACK TO BLUEZ AND DROP BLUEDROID, GOOGLE-DEVS!
Fix this triaged FATAL HIGH PRIORITY BUG!
ma...@gmail.com <ma...@gmail.com> #110
Evident on 4.4.2 as well. Samsung tab4 10.1
an...@gmail.com <an...@gmail.com> #111
Is there any form of way to bypass this problem. I dont think that its cool for my old phone to be better than my new phone.
de...@gmail.com <de...@gmail.com> #113
Pleeeeease good google people, fix this issue :(
an...@gmail.com <an...@gmail.com> #114
WEll shit
the link says, merge, build, congratulations.
so next release should have it in? am I reading this correctly?
That would be AWESOME
https://android-review.googlesource.com/#/c/137040/
the link says, merge, build, congratulations.
so next release should have it in? am I reading this correctly?
That would be AWESOME
fr...@googlemail.com <fr...@googlemail.com> #115
I'm also waiting for this fix since version 4.2 came out and I'm now on 5.0.2 with no sign of patch available... and my expensive wiimote controller is getting dust over waiting as well for this!
mt...@gmail.com <mt...@gmail.com> #116
ra...@gmail.com <ra...@gmail.com> #117
Is there any better way to get this to the Android developers? I mean, they haven't even post a reply! :/ As a costumer i'm very unsatisfied with this service.
je...@gmail.com <je...@gmail.com> #118
Please reinstate this much-needed feature.
We are not asking you to create new functionality, just restore what once was available.
We are not asking you to create new functionality, just restore what once was available.
ka...@baastrup.org <ka...@baastrup.org> #119
Please fix so I can use my wiimote to play my games.
da...@gmail.com <da...@gmail.com> #120
Please fix this Wiimote bluetooth sync for NES.EMU
uf...@gmail.com <uf...@gmail.com> #121
It is selfish but I won't lie, I only want this to ve fixed in order to play super metroid on a emulator.
mt...@gmail.com <mt...@gmail.com> #122
This still isn't fixed? I see no reason to stay loyal to a company that removes features.
ro...@gmail.com <ro...@gmail.com> #123
Just amother update to fix please
uk...@gmail.com <uk...@gmail.com> #124
Chrome OS (along with Windows and OS X) supports L2CAP[1], and Google has expressed interest in further feature parity of Android and Chrome, so this should definitely be supported.
Supporting L2CAP on Android would greatly help improve the performance characteristics of an audio app I'm working on.
[1]https://developer.chrome.com/apps/bluetoothSocket
Supporting L2CAP on Android would greatly help improve the performance characteristics of an audio app I'm working on.
[1]
an...@gmail.com <an...@gmail.com> #125
I switched from my old Apple Ipad for a Galaxy Tab 4 November 2014 because I believed it to be an upgrade for many reasons. Well its not for wii remote pairing. I purchased my nes emulator (nes.emu) and downloaded a few classics. I was excited about the Wii controller blue tooth option. So I downloaded the WiimoteControler app to pair it. I had nothing but difficulty. After doing plenty of due diligence I discovered what many on here already know. I have Andriod 4.4.2 and it doest recognize the wii controller the way pre 4.2 versions did. I try pairing it directly also but since I don't know anything about binary code. I was able to find my wii controller ip address and understand the code is translated backwards and in binary....thats as far as I could understand. It seems way to difficult to accomplish something that on my original ipad or previous Android 4.2 users could do in 3-4 easy steps. Fix this by the next update please. If it's not fixed I will transition back to Apple. Thank you.
vi...@gmail.com <vi...@gmail.com> #126
Cmon google get your shit together i wanna play super mario on the toilet with my wiimote!
lu...@gmail.com <lu...@gmail.com> #127
fix pls
kd...@gmail.com <kd...@gmail.com> #128
Please fix this I bought several apps that are now useless because of this issue.
og...@gmail.com <og...@gmail.com> #129
Please fix
de...@gmail.com <de...@gmail.com> #130
Please fix it. Thank you.
kr...@googlemail.com <kr...@googlemail.com> #131
This is not supported in Lollipop 5.0.2 on my Xperia Z3. Wtf, does anyone know how to contact google directly?
lu...@gmail.com <lu...@gmail.com> #132
Please fix this!!!!!
Description
Since android uses software volume control and never touches the hardware volume of USB DACs, the expected behaviour should be to set the hardware volume of USB DACs to the maximum possible value (e.g. in kernel/sound/usb/mixer.c, at some point do snd_usb_set_cur_mix_value(cval, [channel no.], [index no.], cval->max) ) to use the entire supported volume range of the DAC.