Assigned
Status Update
Comments
vi...@google.com <vi...@google.com> #2
Also confirmed issue persists on 4.4.
mh...@gmail.com <mh...@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.
ka...@gmail.com <ka...@gmail.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
an...@gmail.com <an...@gmail.com> #6
Yes, please fix it. =)
cl...@gmail.com <cl...@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.
an...@gmail.com <an...@gmail.com> #8
[Comment deleted]
li...@gmail.com <li...@gmail.com> #9
fix will ya? make the android better more
wh...@gmail.com <wh...@gmail.com> #10
Yes, count me as someone who would like to see this fixed. It apparently isn't fixed in KitKat.
ot...@gmail.com <ot...@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.
ro...@gmail.com <ro...@gmail.com> #12
Please roll back previous API. This fratura is importante.
ro...@gmail.com <ro...@gmail.com> #13
Android 4.3 killed my super mario :(
sc...@gmail.com <sc...@gmail.com> #14
Please fix, pretty please
an...@gmail.com <an...@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
ab...@unmind.com <ab...@unmind.com> #16
Please fix this!! We want to play with us wii u pro controller!! C'mon Google!!
am...@gmail.com <am...@gmail.com> #17
PLEASE GOOGLE, LET US HAVE BLUETOOTH FREEEEEEEEDDDDOOOOOOOOOOOOOOOOOOM!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
ma...@gmail.com <ma...@gmail.com> #18
Google, please fix this issue. many games are unplayable with said issue.
th...@gmail.com <th...@gmail.com> #19
Please google, can someone please fix this issue. thanks
cl...@gmail.com <cl...@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!
mw...@gmail.com <mw...@gmail.com> #21
Just want to play some Bayou Billy for nes on my Note 3 with wiimote controller please.
mb...@gmail.com <mb...@gmail.com> #22
[Comment deleted]
ja...@gmail.com <ja...@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?
gr...@gmail.com <gr...@gmail.com> #24
I, like many others, wish to enjoy computer gaming nostalgia via excellent emulators. Please fix my first world problem...
hu...@googlemail.com <hu...@googlemail.com> #25
Please fix. This is really dissapointing and I think I'm switching to Apple.
no...@gmail.com <no...@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 !!
ka...@gmail.com <ka...@gmail.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.
ne...@gmail.com <ne...@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.
de...@gmail.com <de...@gmail.com> #29
Still don't work...
el...@gmail.com <el...@gmail.com> #30
Please fix this.
el...@gmail.com <el...@gmail.com> #31
Waht is the big deal?
Please fix this already!
Please fix this already!
or...@gmail.com <or...@gmail.com> #32
[Comment deleted]
ry...@gmail.com <ry...@gmail.com> #33
Please fix this. I want to pair my Wiimote with my Android phone and tablet.
l....@gmail.com <l....@gmail.com> #34
Please repair this issue
gr...@denison.edu <gr...@denison.edu> #35
I cant pair my wii remote with my new smartphone android, please fix this. :) thanks
er...@googlemail.com <er...@googlemail.com> #36
Comment has been deleted.
er...@googlemail.com <er...@googlemail.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.
an...@gmail.com <an...@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.
po...@gmail.com <po...@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!!!
67...@gmail.com <67...@gmail.com> #40
Wish my wiimote worked on my droid tablet
mo...@gmail.com <mo...@gmail.com> #41
[Comment deleted]
r....@gmail.com <r....@gmail.com> #42
This bug has been unattended to for over a YEAR. This is COMPLETELY inexcusable.
rr...@docente.ceibal.edu.uy <rr...@docente.ceibal.edu.uy> #43
Solve this problem
ra...@gmail.com <ra...@gmail.com> #44
Can anyone tell us why this issue is still here, or why L2CAP support was turned off in the first place?
er...@googlemail.com <er...@googlemail.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?
gt...@gmail.com <gt...@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?
er...@googlemail.com <er...@googlemail.com> #47
Fix this please. I will have no choice but to switch to another OS if it not fixed.
je...@gmail.com <je...@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.
mp...@gmail.com <mp...@gmail.com> #49
Seems google is getting a reputation for things like this. Hopefully they
work to correct it
work to correct it
pe...@gmail.com <pe...@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?
ap...@gmail.com <ap...@gmail.com> #51
Google! Fix this please! This is ridiculous!
an...@gmail.com <an...@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!
ju...@gmail.com <ju...@gmail.com> #53
Help!
da...@gmail.com <da...@gmail.com> #54
Please fix this issue, thank you
ne...@gmail.com <ne...@gmail.com> #55
Might need at least another 1800 folks before google takes this seriously
he...@gmail.com <he...@gmail.com> #56
Fix it please
br...@gmail.com <br...@gmail.com> #57
Fix please!
bi...@gmail.com <bi...@gmail.com> #58
[Comment deleted]
ka...@gmail.com <ka...@gmail.com> #59
Please work to correct this.
th...@gmail.com <th...@gmail.com> #60
Fix it please.
li...@outlook.com <li...@outlook.com> #61
Though I really want this to be fixed, it probably won't cause Google.
tu...@gmail.com <tu...@gmail.com> #62
Lads(Google), go on and fix this. Would like to be able to use BT devices on Nook again
Description
In Audio Settings on Wear OS, there are 4 different volume controls: Media, Calls, Ringing/Notifications, and Alarms.
The alarm setting controls the volume of both regular alarms and timers. Other than the settings for media and notifications, the alarm setting cannot be completely muted.
It would be a nice feature if it was possible to mute timers and set them to vibrate only, preferrably as a default settings for all timers created on the watch. The same would be really nice for alarms. While it is possible to set an alarm to vibrate only after creating it, there is no option to set a default value (e.g. silent and vibrate only), which means that the setting must be adjusted manually each time a new alarm is created.
Proposed solution: Either make it possible to silence the alarm volume completely in the audio settings or add a toggle in the individual apps (timer, alarm) to silence them by default for all new created timers and alarms.
Thanks for reading my feedback!