Support Bluetooth L2CAP [36976247]

Assigned

Feature Request

Status Update

No update yet.

Description

ma...@gmail.com

created issue #1

Jul 28, 2013 08:15PM

In Android versions prior to 4.2 it was possible to do communication using Bluetooth L2CAP by directly patching trough to bluez.

Altough the new bluedroid-Stack seems to include an l2cap implementation (see bluedroid/stack/l2cap) it is not enabled to be used via the android.bluetooth.* API.

Calls requesting a L2CAP Socket are turned down with BT_STATUS_UNSUPPORTED.

L2CAP is one of the building blocks of many Bluetooth Classic services. Please support this in future versions of Android.

Comments

so...@gmail.com <so...@gmail.com> #2Dec 8, 2013 08:49PM

Which version of R8 are you using?

aa...@aarcane.org <aa...@aarcane.org> #3Dec 8, 2013 09:27PM

I have tried the newest commit of main branch, it also has the similar issue.

jo...@gmail.com <jo...@gmail.com> #4Dec 8, 2013 09:39PM

In order to diagnose this we would probably need to be able to reproduce this issue.

Would it be possible for you to share a compiler dump file that contains the inputs to R8 (i.e., the Java class files and the keep rules going into R8)? That way we should be able to reproduce the build. You can generate this as below and could share this privately with christofferqa@google.com and sgjesse@google.com.

./gradlew assembleRelease --no-daemon -Dcom.android.tools.r8.dumpinputtodirectory=/path/to/dumps

Do you know if the class ViewEventSinkImpl is instantiated using reflection? If so, do you know if there is a corresponding keep rule for the class?

Can you try if the following rule "fixes" the issue:

-keep,allowobfuscation,allowshrinking class org.chromium.content.browser.ViewEventSinkImpl

When this rule is present, R8 should account for the fact that ViewEventSinkImpl may be instantiated by reflection, which I suspect may fix the issue you are seeing.

kf...@gmail.com <kf...@gmail.com> #5Dec 9, 2013 02:35AM

Hi! I have also encountered a problem with r8 in --classfile mode incorrectly removing a null check, and curiously enough it also happened in and around ViewEventSinkImpl. I tried with the R8 version in Chromium and also with latest main branch local build from the repo which was be29229a110ce06989f6f3a63b0a83015ed3fefe.

The issue I'm seeing is from code which effectively does

public final class ViewEventSinkImpl ... {
    private @Nullable Boolean mHasViewFocus;  // not written to anywhere else

    public void onViewFocusChanged(boolean gainFocus) {
        if (mHasViewFocus != null && mHasViewFocus == gainFocus) return;
        mHasViewFocus = gainFocus;
        ....
    }
}

and after r8 with --classfile, the null check gets removed and the code is guaranteed to crash. Without --classfile, the null check remains in the dex. Note: for me, the code (with or without the check) was inlined at the only callsite to onViewFocusChanged.

Adding

-keep,allowobfuscation,allowshrinking class org.chromium.content.browser.ViewEventSinkImpl

works around the issue for me. I believe there is some reflection going on as one part of the code that affects that bug is the presence of

    public static ViewEventSinkImpl from(WebContents webContents) {
        ViewEventSinkImpl ret =
                ((WebContentsImpl) webContents)
                        .getOrSetUserData(
                                ViewEventSinkImpl.class, UserDataFactoryLazyHolder.INSTANCE);
        return ret;
    }

I hope the advice to send the repro case directly is still valid, I should have it down to a manageable size soon.

pe...@gmail.com <pe...@gmail.com> #6Dec 15, 2013 06:02AM

Thanks, it would be great if you would be able to share a reproduction for this.

bp...@gmail.com <bp...@gmail.com> #7Dec 25, 2013 05:43PM

I have sent the repro over by email. Can you confirm if the mail has gotten thru spam filters, etc.?

me...@gmail.com <me...@gmail.com> #8Dec 28, 2013 09:55AM

Project: r8
Branch: main
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102400

Reproduce inadequate value propagation in presence of T::new expressions

Expand for full commit details

Reproduce inadequate value propagation in presence of T::new expressions 
 
Bug: b/397737234 
Change-Id: Ia6cbb0ef3366125420afbdfcf3a8f0d228cc2004

Files:

A src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: 0e40b2543f171f14c4727e9673cfbe1581bfb804
Date: Thu Mar 06 08:47:46 2025

fr...@gmail.com <fr...@gmail.com> #9Dec 28, 2013 02:51PM

Project: r8
Branch: main
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102421

Account for T::new expressions in default field value joiner

Expand for full commit details

Account for T::new expressions in default field value joiner 
 
Bug: b/397737234 
Change-Id: Iea344f54fa5a8ac40739a51da5d7e6679d5964b8

Files:

M src/main/java/com/android/tools/r8/optimize/argumentpropagation/propagation/DefaultFieldValueJoiner.java
M src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: faeee0fe013067ef2c1b015822a00ebd999c19c9
Date: Thu Mar 06 09:51:41 2025

kr...@gmail.com <kr...@gmail.com> #10Jan 4, 2014 01:36AM

Project: r8
Branch: main
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102420

Fix BootstrapMethodError from invalid class merging

Expand for full commit details

Fix BootstrapMethodError from invalid class merging 
 
Bug: b/397737234 
Change-Id: Icacf51f06017c50b3448610e8493a225c225c40d

Files:

M src/main/java/com/android/tools/r8/horizontalclassmerging/PolicyScheduler.java
A src/main/java/com/android/tools/r8/horizontalclassmerging/policies/NoMethodHandleFromLambda.java
M src/main/java/com/android/tools/r8/shaking/Enqueuer.java
M src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: 2d3816adfcece78053fbab0a70196dcb9c0b94dc
Date: Thu Mar 06 09:33:32 2025

gu...@gmail.com <gu...@gmail.com> #11Jan 8, 2014 11:26AM

I checked faeee0fe013067ef2c1b015822a00ebd999c19c9 from r8's main (containing all the fixes above) and it also fixes my original issue on the real code I had. The null check is no longer removed and I go the code to start up correctly.

Thanks a lot!

ac...@gmail.com <ac...@gmail.com> #12Jan 11, 2014 03:47PM

Project: r8
Branch: 8.9
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102423

Fix BootstrapMethodError from invalid class merging

Expand for full commit details

Fix BootstrapMethodError from invalid class merging 
 
Bug: b/397737234 
Change-Id: Icacf51f06017c50b3448610e8493a225c225c40d

Files:

M src/main/java/com/android/tools/r8/horizontalclassmerging/PolicyScheduler.java
A src/main/java/com/android/tools/r8/horizontalclassmerging/policies/NoMethodHandleFromLambda.java
M src/main/java/com/android/tools/r8/shaking/Enqueuer.java
M src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: 5cc2d659e1fd08cecbc8f7cfcbfc404d0bc95fa6
Date: Thu Mar 06 12:12:03 2025

li...@gmail.com <li...@gmail.com> #13Jan 12, 2014 10:15AM

Project: r8
Branch: 8.9
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102424

Version 8.9.29

Expand for full commit details

Version 8.9.29 
 
Bug: b/397737234 
Change-Id: I23a0b0f52df1ab2db0b175055ebd78115d407dbc

Files:

M src/main/java/com/android/tools/r8/Version.java

Hash: 3d1fcaa2ff1c9b42f0079ae236c48bff520d64c6
Date: Thu Mar 06 12:12:19 2025

bl...@gmail.com <bl...@gmail.com> #14Jan 13, 2014 01:44PM

Project: r8
Branch: 8.9
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102402

Reproduce inadequate value propagation in presence of T::new expressions

Expand for full commit details

Reproduce inadequate value propagation in presence of T::new expressions 
 
Bug: b/397737234 
Change-Id: Ia6cbb0ef3366125420afbdfcf3a8f0d228cc2004

Files:

A src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: 7e08f18c401f4d2503ab37f8dbe59f6714ffa7a2
Date: Thu Mar 06 12:11:55 2025

bm...@gmail.com <bm...@gmail.com> #15Jan 13, 2014 05:47PM

Project: r8
Branch: 8.9
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102403

Account for T::new expressions in default field value joiner

Expand for full commit details

Account for T::new expressions in default field value joiner 
 
Bug: b/397737234 
Change-Id: Iea344f54fa5a8ac40739a51da5d7e6679d5964b8

Files:

M src/main/java/com/android/tools/r8/optimize/argumentpropagation/propagation/DefaultFieldValueJoiner.java
M src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: db5ecfb23c380c97fdf9e8562ec7541a9c94ddc7
Date: Thu Mar 06 12:12:10 2025

mr...@gmail.com <mr...@gmail.com> #16Jan 14, 2014 07:15PM

Project: r8
Branch: 8.8
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102404

Reproduce inadequate value propagation in presence of T::new expressions

Expand for full commit details

Reproduce inadequate value propagation in presence of T::new expressions 
 
Bug: b/397737234 
Change-Id: Ia6cbb0ef3366125420afbdfcf3a8f0d228cc2004

Files:

A src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: 674a5456a7f32132fb20c00e543e5a82456a08f3
Date: Thu Mar 06 12:12:45 2025

ha...@gmail.com <ha...@gmail.com> #17Jan 21, 2014 09:56PM

Project: r8
Branch: 8.8
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102406

Account for T::new expressions in default field value joiner

Expand for full commit details

Account for T::new expressions in default field value joiner 
 
Bug: b/397737234 
Change-Id: Iea344f54fa5a8ac40739a51da5d7e6679d5964b8

Files:

M src/main/java/com/android/tools/r8/optimize/argumentpropagation/propagation/DefaultFieldValueJoiner.java
M src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: dff84c28b3884cecf7d816ccb7b7afe862c0f78f
Date: Thu Mar 06 12:37:41 2025

vw...@gmail.com <vw...@gmail.com> #18Feb 2, 2014 11:41PM

Project: r8
Branch: 8.8
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102425

Fix BootstrapMethodError from invalid class merging

Expand for full commit details

Fix BootstrapMethodError from invalid class merging 
 
Bug: b/397737234 
Change-Id: Icacf51f06017c50b3448610e8493a225c225c40d

Files:

M src/main/java/com/android/tools/r8/horizontalclassmerging/PolicyScheduler.java
A src/main/java/com/android/tools/r8/horizontalclassmerging/policies/NoMethodHandleFromLambda.java
M src/main/java/com/android/tools/r8/shaking/Enqueuer.java
M src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: 54f1b29c6d4be82cfb1cf2cbd0483093fc583114
Date: Thu Mar 06 12:12:53 2025

st...@gmail.com <st...@gmail.com> #19Feb 12, 2014 04:11PM

Project: r8
Branch: 8.8
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102405

Version 8.8.37

Expand for full commit details

Version 8.8.37 
 
Bug: b/397737234 
Change-Id: Ibc71b252bb1283074ba65ce92bac26cb0396558c

Files:

M src/main/java/com/android/tools/r8/Version.java

Hash: bc26ca739f0297c4c132feb78d8090b44b6a8b5e
Date: Thu Mar 06 12:38:38 2025

gi...@gmail.com <gi...@gmail.com> #20Mar 2, 2014 06:35AM

Project: r8
Branch: 8.9
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102423

Fix BootstrapMethodError from invalid class merging

Expand for full commit details

Fix BootstrapMethodError from invalid class merging 
 
Bug: b/397737234 
Change-Id: Icacf51f06017c50b3448610e8493a225c225c40d

Files:

M src/main/java/com/android/tools/r8/horizontalclassmerging/PolicyScheduler.java
A src/main/java/com/android/tools/r8/horizontalclassmerging/policies/NoMethodHandleFromLambda.java
M src/main/java/com/android/tools/r8/shaking/Enqueuer.java
M src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: 5cc2d659e1fd08cecbc8f7cfcbfc404d0bc95fa6
Date: Thu Mar 06 12:12:03 2025

ja...@gmail.com <ja...@gmail.com> #21Mar 5, 2014 11:42PM

Project: r8
Branch: 8.9
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102402

Reproduce inadequate value propagation in presence of T::new expressions

Expand for full commit details

Reproduce inadequate value propagation in presence of T::new expressions 
 
Bug: b/397737234 
Change-Id: Ia6cbb0ef3366125420afbdfcf3a8f0d228cc2004

Files:

A src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: 7e08f18c401f4d2503ab37f8dbe59f6714ffa7a2
Date: Thu Mar 06 12:11:55 2025

rd...@gmail.com <rd...@gmail.com> #22Mar 6, 2014 02:47PM

Project: r8
Branch: 8.9
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102403

Account for T::new expressions in default field value joiner

Expand for full commit details

Account for T::new expressions in default field value joiner 
 
Bug: b/397737234 
Change-Id: Iea344f54fa5a8ac40739a51da5d7e6679d5964b8

Files:

M src/main/java/com/android/tools/r8/optimize/argumentpropagation/propagation/DefaultFieldValueJoiner.java
M src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: db5ecfb23c380c97fdf9e8562ec7541a9c94ddc7
Date: Thu Mar 06 12:12:10 2025

bo...@gmail.com <bo...@gmail.com> #23Mar 14, 2014 09:28PM

Thanks for the confirmation and for taking the time to create a reproduction. This should be fixed in R8 versions 8.7.37, 8.8.37, 8.9.29 and 8.10.

as...@gmail.com <as...@gmail.com> #24Mar 18, 2014 02:43PM

Project: r8
Branch: 8.7
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102428

Account for T::new expressions in default field value joiner

Expand for full commit details

Account for T::new expressions in default field value joiner 
 
Bug: b/397737234 
Change-Id: Iea344f54fa5a8ac40739a51da5d7e6679d5964b8

Files:

M src/main/java/com/android/tools/r8/optimize/argumentpropagation/propagation/DefaultFieldValueJoiner.java
M src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: facb83cda9b23e96d13acfb6e61edfe77b754c56
Date: Thu Mar 06 12:47:29 2025

[Deleted User] <[Deleted User]> #25Apr 15, 2014 03:12AM

Project: r8
Branch: 8.7
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102427

Fix BootstrapMethodError from invalid class merging

Expand for full commit details

Fix BootstrapMethodError from invalid class merging 
 
Bug: b/397737234 
Change-Id: Icacf51f06017c50b3448610e8493a225c225c40d

Files:

M src/main/java/com/android/tools/r8/horizontalclassmerging/PolicyScheduler.java
A src/main/java/com/android/tools/r8/horizontalclassmerging/policies/NoMethodHandleFromLambda.java
M src/main/java/com/android/tools/r8/shaking/Enqueuer.java
M src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: f84fe96b65408bc0b38dbed81b95ef3cc8f998af
Date: Thu Mar 06 12:45:35 2025

de...@gmail.com <de...@gmail.com> #26Apr 27, 2014 03:32PM

Project: r8
Branch: 8.7
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102407

Reproduce inadequate value propagation in presence of T::new expressions

Expand for full commit details

Reproduce inadequate value propagation in presence of T::new expressions 
 
Bug: b/397737234 
Change-Id: Ia6cbb0ef3366125420afbdfcf3a8f0d228cc2004

Files:

A src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: 2c63d92a87eafc74b45cba8a5a8f3a013130c653
Date: Thu Mar 06 12:45:27 2025

de...@gmail.com <de...@gmail.com> #27May 1, 2014 03:19PM

Project: r8
Branch: 8.7
Author: Christoffer Adamsen <christofferqa@google.com>
Link: https://r8-review.googlesource.com/102429

Version 8.7.37

Expand for full commit details

Version 8.7.37 
 
Bug: b/397737234 
Change-Id: If19c362aff21345ea0eba68ee01174265aefae4e

Files:

M src/main/java/com/android/tools/r8/Version.java

Hash: 9dd430e92787edf015ce4dbfe5ddb309999758f5
Date: Thu Mar 06 12:47:39 2025

le...@gmail.com <le...@gmail.com> #28May 4, 2014 08:28PM

Project: r8
Branch: 8.10
Author: Rico Wind <ricow@google.com>
Link: https://r8-review.googlesource.com/102409

Fix BootstrapMethodError from invalid class merging

Expand for full commit details

Fix BootstrapMethodError from invalid class merging 
 
Bug: b/397737234 
Change-Id: Icacf51f06017c50b3448610e8493a225c225c40d

Files:

M src/main/java/com/android/tools/r8/horizontalclassmerging/PolicyScheduler.java
A src/main/java/com/android/tools/r8/horizontalclassmerging/policies/NoMethodHandleFromLambda.java
M src/main/java/com/android/tools/r8/shaking/Enqueuer.java
M src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: ad501b1308e3c0d0206bea8111a799f459492135
Date: Mon Mar 10 11:24:46 2025

br...@gmail.com <br...@gmail.com> #29May 27, 2014 05:34PM

Project: r8
Branch: 8.10
Author: Rico Wind <ricow@google.com>
Link: https://r8-review.googlesource.com/102621

Reproduce inadequate value propagation in presence of T::new expressions

Expand for full commit details

Reproduce inadequate value propagation in presence of T::new expressions 
 
Bug: b/397737234 
Change-Id: Ia6cbb0ef3366125420afbdfcf3a8f0d228cc2004

Files:

A src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: b62d995efb1143edee9b2589f3a22f27f1bdd10f
Date: Mon Mar 10 11:24:41 2025

bm...@gmail.com <bm...@gmail.com> #30May 28, 2014 06:27PM

Project: r8
Branch: 8.10
Author: Rico Wind <ricow@google.com>
Link: https://r8-review.googlesource.com/102622

Account for T::new expressions in default field value joiner

Expand for full commit details

Account for T::new expressions in default field value joiner 
 
Bug: b/397737234 
Change-Id: Iea344f54fa5a8ac40739a51da5d7e6679d5964b8

Files:

M src/main/java/com/android/tools/r8/optimize/argumentpropagation/propagation/DefaultFieldValueJoiner.java
M src/test/java/com/android/tools/r8/ir/optimize/membervaluepropagation/DefaultFieldValueJoinerWithLambdaAllocationTest.java

Hash: 56515ee2eca6931b432a0bf373e6d90a486670e3
Date: Mon Mar 10 11:24:54 2025

[Deleted User] <[Deleted User]> #31Jun 1, 2014 03:35AM

Project: r8
Branch: 8.10
Author: Rico Wind <ricow@google.com>
Link: https://r8-review.googlesource.com/102410

Version 8.10.16

Expand for full commit details

Version 8.10.16 
 
Bug: b/397737234 
Change-Id: I8aa6795562027e7b1ecf22d684385b872cd92f86

Files:

M src/main/java/com/android/tools/r8/Version.java

Hash: 77b6af4095578d5ccc62cb8730ba1b9555f059b7
Date: Mon Mar 10 11:25:00 2025

cf...@hotmail.com <cf...@hotmail.com> #32Jun 8, 2014 06:47AM

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

Android Studio Meerkat Feature Drop | 2024.3.2 Beta 1
Android Gradle Plugin 8.10.0-beta01

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

cf...@hotmail.com <cf...@hotmail.com> #33Jun 8, 2014 06:48AM

The fixes for this issue are now also available in:

Android Studio Meerkat | 2024.3.1 Patch 1
Android Gradle Plugin 8.9.1

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

an...@gmail.com <an...@gmail.com> #34Jun 8, 2014 06:42PM

Please repair this issue

ma...@gmail.com <ma...@gmail.com> #35Jun 15, 2014 04:31PM

I cant pair my wii remote with my new smartphone android, please fix this. :) thanks

tu...@gmail.com <tu...@gmail.com> #36Jun 24, 2014 03:00AM

Please fix this if you can.

dk...@gmail.com <dk...@gmail.com> #37Jun 24, 2014 04:28AM

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.

si...@gmail.com <si...@gmail.com> #38Jun 25, 2014 12:37AM

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.

ji...@gmail.com <ji...@gmail.com> #39Jun 25, 2014 06:43AM

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!!!

jd...@gmail.com <jd...@gmail.com> #40Jul 18, 2014 08:50AM

Wish my wiimote worked on my droid tablet

ga...@gmail.com <ga...@gmail.com> #41Jul 30, 2014 12:17AM

[Comment deleted]

au...@gmail.com <au...@gmail.com> #42Jul 30, 2014 12:55AM

This bug has been unattended to for over a YEAR. This is COMPLETELY inexcusable.

th...@gmail.com <th...@gmail.com> #43Aug 1, 2014 11:13PM

Solve this problem

jd...@gmail.com <jd...@gmail.com> #44Aug 1, 2014 11:42PM

Can anyone tell us why this issue is still here, or why L2CAP support was turned off in the first place?

jo...@gmail.com <jo...@gmail.com> #45Aug 2, 2014 12:29AM

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?

jd...@gmail.com <jd...@gmail.com> #46Aug 2, 2014 12:45AM

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?

jo...@gmail.com <jo...@gmail.com> #47Aug 30, 2014 03:32AM

Fix this please. I will have no choice but to switch to another OS if it not fixed.

ty...@gmail.com <ty...@gmail.com> #48Sep 4, 2014 08:31PM

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.

jd...@gmail.com <jd...@gmail.com> #49Sep 4, 2014 10:23PM

Seems google is getting a reputation for things like this. Hopefully they
work to correct it

1l...@gmail.com <1l...@gmail.com> #50Sep 7, 2014 10:05PM

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?

ly...@gmail.com <ly...@gmail.com> #51Sep 11, 2014 09:27PM

Google! Fix this please! This is ridiculous!

di...@gmail.com <di...@gmail.com> #52Sep 12, 2014 09:28PM

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!

[Deleted User] <[Deleted User]> #53Sep 15, 2014 04:55AM

Help!

mt...@gmail.com <mt...@gmail.com> #54Sep 27, 2014 04:14AM

Please fix this issue, thank you

jd...@gmail.com <jd...@gmail.com> #55Sep 30, 2014 02:29PM

Might need at least another 1800 folks before google takes this seriously

ma...@gmail.com <ma...@gmail.com> #56Oct 7, 2014 12:35AM

Fix it please

nh...@gmail.com <nh...@gmail.com> #57Oct 7, 2014 04:48AM

Fix please!

fo...@umn.edu <fo...@umn.edu> #58Oct 15, 2014 11:26PM

[Comment deleted]

to...@gmail.com <to...@gmail.com> #59Oct 15, 2014 11:26PM

Please work to correct this.

ri...@gmail.com <ri...@gmail.com> #60Oct 18, 2014 10:29PM

Fix it please.

te...@gmail.com <te...@gmail.com> #61Oct 19, 2014 02:22PM

Though I really want this to be fixed, it probably won't cause Google.

em...@gmail.com <em...@gmail.com> #62Oct 23, 2014 10:38AM

Lads(Google), go on and fix this. Would like to be able to use BT devices on Nook again

wa...@gmail.com <wa...@gmail.com> #63Oct 23, 2014 05:16PM

Does anyone know if this has finally been addressed in Android 5.0 Lollipop?

mz...@gmail.com <mz...@gmail.com> #64Oct 26, 2014 04:19AM

Please fix!!!!

on...@gmail.com <on...@gmail.com> #65Oct 31, 2014 03:28AM

[Comment deleted]

on...@gmail.com <on...@gmail.com> #66Oct 31, 2014 03:29AM

Why has this not been fixed??

bm...@gmail.com <bm...@gmail.com> #67Nov 3, 2014 02:38AM

This is the reason why we all love Android... Otherwise We'd just buy and IOS device... Please address this issue.

fr...@gmail.com <fr...@gmail.com> #68Nov 3, 2014 06:35PM

please fix this

di...@gmail.com <di...@gmail.com> #69Nov 5, 2014 03:26AM

another fix request!! common google!!

er...@gmail.com <er...@gmail.com> #70Nov 5, 2014 12:32PM

There are 9 commits that mentions something about L2CAP in lollipop.

http://aosp.changelog.to/aosp-KITKAT-LRX21M.html

ko...@gmail.com <ko...@gmail.com> #71Nov 9, 2014 06:12PM

[Comment deleted]

ga...@gmail.com <ga...@gmail.com> #72Nov 10, 2014 01:46PM

Please, fix it.
I want use my bluetooth !!

ar...@hausic.de <ar...@hausic.de> #73Nov 14, 2014 10:11PM

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.

mj...@gmail.com <mj...@gmail.com> #74Dec 4, 2014 09:44PM

Any updates here?

wi...@gmail.com <wi...@gmail.com> #75Dec 6, 2014 12:50PM

Come on fix it plz!!!

jd...@gmail.com <jd...@gmail.com> #76Dec 23, 2014 04:21AM

Christmas present for your loyal fans, Google? Pleeeeeeeeeeeeeeeeeeeeeease fix this. Thanks!

ma...@gmail.com <ma...@gmail.com> #77Dec 24, 2014 03:00PM

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.

fa...@gmail.com <fa...@gmail.com> #78Dec 26, 2014 09:27PM

Houhou! Please fix it!

gu...@gmail.com <gu...@gmail.com> #79Dec 27, 2014 01:25PM

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

jo...@gmail.com <jo...@gmail.com> #80Dec 28, 2014 11:56AM

Please correct this issue.

lu...@gmail.com <lu...@gmail.com> #81Dec 29, 2014 12:52AM

I Want to use my Wiimotes with my Tablet Expedia Z2.
PLEASE Fix this issue

ra...@hotmail.com <ra...@hotmail.com> #82Jan 1, 2015 01:29AM

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.

da...@gmail.com <da...@gmail.com> #83Jan 1, 2015 02:57PM

I am unable to connect. Wii remote to emulator due to this bug in 4.4 please fix!

ri...@gmail.com <ri...@gmail.com> #84Jan 2, 2015 08:38AM

Please resurrect the fucntion. Google! If not so I have to develop my H/W for ios only.

jo...@googlemail.com <jo...@googlemail.com> #85Jan 3, 2015 02:34PM

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 :)

en...@google.com <en...@google.com> Jan 8, 2015 04:34AM

Assigned to ma...@android.com.

da...@gmail.com <da...@gmail.com> #86Jan 8, 2015 08:10AM

Not impressed with how long google take to fix a defect.

pe...@gmail.com <pe...@gmail.com> #87Jan 8, 2015 09:05PM

[Comment deleted]

dw...@gmail.com <dw...@gmail.com> #88Jan 11, 2015 12:46PM

What they said.

ze...@gmail.com <ze...@gmail.com> #89Jan 12, 2015 02:20AM

Really need to fix this, this is a deplorable state :(

da...@gmail.com <da...@gmail.com> #90Jan 12, 2015 09:56AM

So my options appear to be downgrade to an old version or get an iPad.

js...@gmail.com <js...@gmail.com> #91Jan 13, 2015 05:07AM

Please fix this. I want to be able to use my wiimote again and other Bluetooth devices.

cr...@gmail.com <cr...@gmail.com> #92Jan 18, 2015 10:53PM

I echo the sentiments of everyone else. Please fix this issue.

le...@gmail.com <le...@gmail.com> #93Jan 20, 2015 04:52AM

For the love of Linus, Google, fix this nonsense.

wi...@touchhk.com <wi...@touchhk.com> #94Jan 22, 2015 03:57AM

please fix it!

[Deleted User] <[Deleted User]> #95Jan 22, 2015 03:59AM

I want to use L2CAPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPPP!

je...@gmail.com <je...@gmail.com> #96Jan 22, 2015 07:56AM

Yes please!

al...@gmail.com <al...@gmail.com> #97Jan 22, 2015 09:39AM

I am amazed this is still an open issue after more than 1 year and a half. Come on Google!

ro...@gmail.com <ro...@gmail.com> #98Jan 22, 2015 09:41AM

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.

wo...@gmail.com <wo...@gmail.com> #99Jan 22, 2015 12:10PM

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.

dr...@gmail.com <dr...@gmail.com> #100Jan 25, 2015 03:25AM

Please implement L2CAP

go...@gmail.com <go...@gmail.com> #101Jan 25, 2015 05:48AM

Please address this. I want to be able to use my wiimote in the new version of android.

an...@gmail.com <an...@gmail.com> #102Jan 26, 2015 11:41AM

Please please Google fix this so it's compatible AGAIN with Wiimotes!

jt...@gmail.com <jt...@gmail.com> #103Jan 27, 2015 06:41PM

Please add L2CAP support.

mi...@gmail.com <mi...@gmail.com> #104Jan 28, 2015 07:23PM

This is needed badly.

he...@gmail.com <he...@gmail.com> #105Jan 30, 2015 01:49AM

iOS can function with peripherals just fine! why does android (OPEN SOURCE) get locked out.

ga...@gmail.com <ga...@gmail.com> #106Feb 2, 2015 03:37PM

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

js...@gmail.com <js...@gmail.com> #107Feb 4, 2015 02:59AM

still not fixed in the lollipop 5.0 update. Lame Google, very lame.....

ni...@gmail.com <ni...@gmail.com> #108Feb 9, 2015 09:27AM

Can't believe this issue isn't fixed yet...
Google get your crap together!!

di...@gmail.com <di...@gmail.com> #109Feb 17, 2015 06:43PM

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!

om...@gmail.com <om...@gmail.com> #110Feb 26, 2015 01:55AM

Evident on 4.4.2 as well. Samsung tab4 10.1

xf...@gmail.com <xf...@gmail.com> #111Feb 26, 2015 08:55PM

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.

jr...@gmail.com <jr...@gmail.com> #112Mar 1, 2015 01:34PM

https://android-review.googlesource.com/#/c/137040/

ve...@gmail.com <ve...@gmail.com> #113Mar 18, 2015 06:04PM

Pleeeeease good google people, fix this issue :(

ma...@gmail.com <ma...@gmail.com> #114Apr 4, 2015 01:00PM

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/

al...@gmail.com <al...@gmail.com> #115Apr 14, 2015 12:51PM

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!

jo...@gmail.com <jo...@gmail.com> #116Apr 28, 2015 02:25PM

Nice. Hopefully it works for the wii u pro controller.

https://android-review.googlesource.com/#/c/137040/

na...@gmail.com <na...@gmail.com> #117Apr 30, 2015 02:01AM

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.

st...@gmail.com <st...@gmail.com> #118Apr 30, 2015 12:20PM

Please reinstate this much-needed feature.

We are not asking you to create new functionality, just restore what once was available.

no...@gmail.com <no...@gmail.com> #119May 10, 2015 04:31AM

Please fix so I can use my wiimote to play my games.

jm...@gmail.com <jm...@gmail.com> #120May 11, 2015 01:19PM

Please fix this Wiimote bluetooth sync for NES.EMU

jm...@gmail.com <jm...@gmail.com> #121May 14, 2015 09:21PM

It is selfish but I won't lie, I only want this to ve fixed in order to play super metroid on a emulator.

co...@gmail.com <co...@gmail.com> #122May 20, 2015 09:11AM

This still isn't fixed? I see no reason to stay loyal to a company that removes features.

de...@gmail.com <de...@gmail.com> #123May 30, 2015 04:48AM

Just amother update to fix please

is...@gmail.com <is...@gmail.com> #124Jun 4, 2015 09:14PM

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

lo...@gmail.com <lo...@gmail.com> #125Jun 14, 2015 04:06PM

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.

ma...@gmail.com <ma...@gmail.com> #126Jun 14, 2015 04:59PM

Cmon google get your shit together i wanna play super mario on the toilet with my wiimote!

tr...@gmail.com <tr...@gmail.com> #127Jun 21, 2015 12:15AM

fix pls

da...@gmail.com <da...@gmail.com> #128Jun 22, 2015 04:14AM

Please fix this I bought several apps that are now useless because of this issue.

mu...@gmail.com <mu...@gmail.com> #129Jun 27, 2015 03:22PM

Please fix

ra...@gmail.com <ra...@gmail.com> #130Jun 29, 2015 01:51AM

Please fix it. Thank you.

[Deleted User] <[Deleted User]> #131Jul 6, 2015 04:21AM

This is not supported in Lollipop 5.0.2 on my Xperia Z3. Wtf, does anyone know how to contact google directly?

ca...@gmail.com <ca...@gmail.com> #132Jul 7, 2015 07:12AM

Please fix this!!!!!

jw...@gmail.com <jw...@gmail.com> #133Jul 8, 2015 02:14AM

Please fix the bluetooth stack to support wimotes!

al...@gmail.com <al...@gmail.com> #134Jul 13, 2015 01:27AM

C'mon google just do it return the support!

er...@gmail.com <er...@gmail.com> #135Jul 26, 2015 07:00PM

Please. Fix this problem with BT.

pa...@gmail.com <pa...@gmail.com> #136Jul 31, 2015 01:18PM

Please fix this bluetooth problem asap.

al...@gmail.com <al...@gmail.com> #137Aug 1, 2015 03:23AM

very disappointed Google decided to break functionality like thiss, I don't suppose android 5.1 has fixed the issue. seems like a major blow to Bluetooth being useful for anything other then audio or mice and keyboards

be...@gmail.com <be...@gmail.com> #138Aug 19, 2015 04:52PM

Please add support for Wiimotes!

vi...@gmail.com <vi...@gmail.com> #139Sep 4, 2015 05:35PM

Greetings.

I’ve developed mesh networking library for Android that uses Bluetooth in such way that it doesn’t need Discoverable confirmation from the user each 5 minutes. It also allows background connection between devices thus allowing true seamless mesh networking.

You can try it here:

http://underdark.io

ni...@gmail.com <ni...@gmail.com> #140Sep 12, 2015 02:03PM

Place fix that =(

ar...@gmail.com <ar...@gmail.com> #141Oct 3, 2015 07:24AM

please fix this motherfuckers!!

ca...@gmail.com <ca...@gmail.com> #142Oct 3, 2015 03:44PM

Please ix this issue!

ss...@gmail.com <ss...@gmail.com> #143Oct 30, 2015 10:45PM

Why the shit don't you fix this? PORCODDIO!

cr...@gmail.com <cr...@gmail.com> #144Nov 7, 2015 07:44AM

Seriously fix this issue. It's mind boggling that it's been known for years now.

lo...@google.com <lo...@google.com> Nov 7, 2015 08:08AM

Reassigned to ei...@google.com.

ca...@gmx.de <ca...@gmx.de> #145Nov 7, 2015 04:41PM

Please consider working on it. Imagine all the sad dusty wiimotes.

ei...@google.com <ei...@google.com> #146Nov 9, 2015 10:25PM

If this is still relevant, please let us know what would constitute a "fix" here.
It's not clear to me from the bug description which public API is no longer working as expected?

Thanks

ka...@gmail.com <ka...@gmail.com> #147Nov 12, 2015 08:30PM

Yes, it is still relevant!

To put it short: most people posting here (like me) just want to connect their good old handy WiiMote to their Android devices.

This worked fine for a lot of devices until Android 4.2 (like on my Galaxy S3mini GT-I8190 @ Android 4.1.2).

I wrote a longer text but lost it due to google re-asking my pswd, so this one won't be as elaborated - sorry...
I am not a BT-pro, so here is what I've read: The issue arose with the switch from Bluez to the BlueDroid BT stack on Android JB 4.2. There seems to be no (or no working?) implementation of the L2CAP protocol used to connect to the WiiMote by some apps (see below), since the WiiMote is a "pairless" BT-HID device BUT it's not abiding by the std. BT HID protocol. I'll cite "

wiibrew.org/wiki/Wiimote":

- Show quoted text -

There are at least two apps providing access to the WiiMote on pre-4.2 devices:
- Android-BlueZ-IME - (

https://code.google.com/p/android-bluez-ime/)
- WiimoteController - (

http://android.ccpcreations.com/wiicontroller)
*Both do work on my aforementioned S3Mini@4.1.2

As far as I understand, they had to use the L2CAP protocol, since Android devices were unable to cope with the WiiMote's non-standard way of (ab-)using BT HID.
For further information, please, be so kind to check the repo/issues of android-bluez-ime (link above). Maybe you can even contact one of the above devs - at least the bluez-ime guy somewhere expressed interest in fixing his app if Android's BT stack would properly (re-)implement L2CAP again.

A great bunch of Android gamers would really appreciate your efforts! We do not want to buy a new BT gamepad. This is your possibility to become a real hero ;-)

For my current device (Galaxy Tab3 10.1 @ 4.4.2) it is possibly to late for a fix. But I'd really like to use my handy WiiMote + its Nunchuck companion on my next Android tablet (then running Android 6.x/Android N). Maybe it would even be possible to compile custom kernels and ROMs to backport these fixes to 4.4 - just dreaming...

Big thanks for reviewing this issue and considering a fix/patch/implementation.

kLik (kaelka)

ri...@gmail.com <ri...@gmail.com> #148Nov 28, 2015 02:09PM

Still not fixed???? This is the
Shittiest inconvenience ever.

mi...@gmail.com <mi...@gmail.com> #149Dec 1, 2015 09:50AM

Can this please be fixed already. Holy crap!! We're on android 6 now and I still cannot connect my Bluetooth device to my phone!! Comon Google, get your crap together please.

fl...@gmail.com <fl...@gmail.com> #150Dec 8, 2015 02:49AM

Please please fix!

me...@gmail.com <me...@gmail.com> #151Dec 15, 2015 06:43PM

would be awesome if this get fixed. annoys me that i can not use my wiimote =/

ie...@gmail.com <ie...@gmail.com> #152Dec 19, 2015 07:45AM

Just purchased my first application from Google Play store, and find out my Wii remote can not connect as it can on the same application on other platforms.

jo...@gmail.com <jo...@gmail.com> #153Dec 21, 2015 02:20AM

[Comment deleted]

jo...@gmail.com <jo...@gmail.com> #154Dec 21, 2015 02:21AM

Please fix

ed...@gmail.com <ed...@gmail.com> #155Dec 22, 2015 12:49AM

Please fix this

jo...@gmail.com <jo...@gmail.com> #156Dec 22, 2015 06:07AM

I noticed in the below link it says "needs code review" in the top beside the change number. But I also see it has a reviewer. Sites that mean it needs a certain amount of reviewers, a certain type of reviewer (Google employee) or am I misunderstanding this?

https://android-review.googlesource.com/#/c/137040/

sk...@gmail.com <sk...@gmail.com> #157Dec 22, 2015 08:18PM

fix this!!!

lo...@gmail.com <lo...@gmail.com> #158Dec 30, 2015 04:11PM

People have been waiting for this to be fixed since 4.2 and there's more than enough information in the comments to understand the issue. Please read the comments more thoroughly before asking if this is still relevant, as many people have been waiting over two years just to get back something that was perfectly fine before 4.2.

mo...@gmail.com <mo...@gmail.com> #159Jan 3, 2016 06:01AM

Google are bloody fucking dumbshits for not fixing this.

ba...@gmail.com <ba...@gmail.com> #160Jan 4, 2016 11:15PM

Please fix.

ge...@gmail.com <ge...@gmail.com> #161Jan 4, 2016 11:50PM

I guess if your a multi-billion dollar company like google you don't have to give damn if there's a problem a group of customers want or need fixed.

lu...@gmail.com <lu...@gmail.com> #162Jan 27, 2016 02:55AM

Please fix this. The issue is still relevant . there are plenty of people now with newer versions of Android who would like to use their wiimotes for apps. We've been waiting for about 3 years now. Make this happen

ha...@gmail.com <ha...@gmail.com> #163Jan 28, 2016 08:49PM

Android 4.4.4
Same Problem. Time to fix it!

mo...@gmail.com <mo...@gmail.com> #164Feb 2, 2016 03:14PM

Android 6.0 have BLE with min conn interval of 11.25, done some search and i think this could be usefullhttp://

stackoverflow.com/questions/34617061/android-6-0-marsmallow-ble-connection-parameters

qu...@gmail.com <qu...@gmail.com> #165Feb 21, 2016 01:40PM

They really need to fix this! Now it is impossible to use some game pads at all!

xx...@gmail.com <xx...@gmail.com> #166Mar 9, 2016 02:16AM

Still no fix. Thanks for fucking nothing.

mh...@gmail.com <mh...@gmail.com> #167Mar 9, 2016 12:29PM

Just tested on Androind 5.0.1. Galaxy S4+ still does not work :(

I expect google is not gettin this to work ever. What are they scared about? Or at least tell us the reason why this will not be solved and why complaining users are ignored?

[Deleted User] <[Deleted User]> #168Mar 11, 2016 06:37AM

Well, at least tell us the reason why took it out or whether you are gonna put it back or not.
Don't you?

ko...@gmail.com <ko...@gmail.com> #169Mar 12, 2016 01:43PM

Just updated my phone to S7 Edge and was really disappointed to notice that my wiimote won't work on it. Guess i have to Root the phone to get it to work. Shame on you google!

v0...@gmail.com <v0...@gmail.com> #170Mar 24, 2016 09:05PM

Root breaks Samsung Pay and won't fix the problem. You have to install a custom ROM with a different Bluetooth stack... Or Google gets it together and enables L2CAP in the newer (open source) BT stack...

pi...@gmail.com <pi...@gmail.com> #171Mar 26, 2016 06:13PM

Please fix it! Android 4.2.2 has the same problem

is...@gmail.com <is...@gmail.com> #172Apr 15, 2016 10:57AM

This prevents me from directly emulating an A2DP receiver. If I had access to raw L2CAP I could capture and mux audio from other devices and route it through my phone's own DAC.

L2CAP support enables many new peripheral use cases.

ca...@gmail.com <ca...@gmail.com> #173Apr 17, 2016 02:24AM

[Comment deleted]

em...@gmail.com <em...@gmail.com> #174Apr 18, 2016 10:05PM

This is a little bit of a "me too" post, but I thought perhaps I could supply additional details for devs.

I'm trying to create an app that will connect with a wiimote, but there are problems.

The first is the pairing issue which this change partially addresses:

https://android-review.googlesource.com/#/c/137040/

I say partially because on a phone running Cyanogenmod 12, which incorporates this change, I can pair older wii remotes, but not more recent ones. So there's still some bug there, but I don't know what it is.

The second is that, once the device is paired, I need to be able to connect to it and communicate with it. It's an HID device, so it expects to speak L2CAP, but the API doesn't offer support for this--there are two methods for creating BluetoothSockets, and they are createRfcommSocketToServiceRecord and createInsecureRfcommSocketToServiceRecord. Obviously, both create RFCOMM sockets. Thus, it's necessary to use reflection to create a workaround, as per:

http://stackoverflow.com/questions/16882628/android-wiimote-socket-fails-to-connect

Next, when you want to actually connect this socket, there's a further problem:

https://android.googlesource.com/platform/external/bluetooth/bluedroid/+/master/btif/src/btif_sock.c

Note at line 138, it checks if you're trying to connect an L2CAP socket, and if you are, it gives a BT_STATUS_UNSUPPORTED error. This also happens for SCO connections.

Cyanogenmod 12 also has a workaround for this--it's all in

https://github.com/CyanogenMod/android_external_bluetooth_bluedroid

I don't know what the licenses are for that, but perhaps it'd be possible to incorporate those changes into main line Bluedroid. (For direct comparison, their version of the same file:

https://github.com/CyanogenMod/android_external_bluetooth_bluedroid/blob/cm-12.0/btif/src/btif_sock.c
although I'm pretty confident that other changes are required as well--e.g., they have a file called btif_sock_l2cap.c that's also not present in the Google version.
)

It'd be really nice to have direct API support for creating L2CAP sockets, too, though. It currently takes quite a lot of digging to figure out how to make it work, since many posts simply say "that's not possible since Android 4.2."

Hope this helps clarify the issues.

em...@gmail.com <em...@gmail.com> #175Apr 19, 2016 01:12AM

I should point out that the pin/pairing issue affects only the wii remote, but the rest of the L2CAP stuff affects an entire category of bluetooth devices, including every HID device as well as some bluetooth audio, etc.

ga...@gmail.com <ga...@gmail.com> #176Apr 26, 2016 07:50PM

Please fix it !! It's a major issue !

fr...@gmail.com <fr...@gmail.com> #177Apr 29, 2016 11:42PM

I just tried it with Android 5.1 and it asked me for a PIN when I attempted to pair. Couldn't pair :-(

deleted

Restricted

0 B

da...@gmail.com <da...@gmail.com> #178May 24, 2016 03:10AM

Still have this problem

ha...@googlemail.com <ha...@googlemail.com> #179Jun 3, 2016 05:53PM

Why is this still an issue?

ir...@gmail.com <ir...@gmail.com> #180Jun 22, 2016 01:53AM

This is still an issue, Google should respond with an official statement on the outcome it's been almost 2 years now.

tm...@gmail.com <tm...@gmail.com> #181Jun 25, 2016 12:16AM

This is still a HUGE issue, I recently got a Google cardboard and would love to use the Wii remote that is gathering dust in the corner as a peripheral for movement. Pls fix this issue.

br...@gmail.com <br...@gmail.com> #182Jul 4, 2016 02:45PM

How am I supposed to play Pokemon Snap with onscreen controls?

pc...@gmail.com <pc...@gmail.com> #183Jul 18, 2016 08:49AM

Sue these ridiculous motherfuckers.

1. You paid for the phone.
2. Price includes 'support'.
3. I see no support here.
3. That's honest services fraud.
4. Android 'supports bluetooth devices': false-statement/advertising. Wiimotes are Bluetooth devices, so are heapdphones and speakers.
5. L2CAP is a part of Bluetooth.
6. No warning labels advise purchaser of the Bluetooth compatibility defects. This is dishonest and misleading information.
7. This voids all disclaimers and warranties from google and the manufacturers. (They don't exist, it's a false agreement for even saying 'bluetooth').

This should never have been a problem. I think google owes restitution to everyone (including manufacturers) for these inconveniences. It might be legal fees, a new phone, or new bluetooth devices to replace the ones you cant use. This much is certain. There is no way to fix all the phones and agreements that ARE broken.

No amount of legal arguing can justify selling almost-bluetooth as Bluetooth. It would be perjury in a court of law to say it is bluetooth because everyone here testifies its a false-statement: they can't use their bluetooth-devices with their "bluetooth" phone.

Piss me off again Google. I'm already working on another legal-angle to cut you down to size: smaller than us. Services serve the users. Get your ass on the job or quit. The fruits of my labor will not be taken for granted.

pc...@gmail.com <pc...@gmail.com> #184Jul 18, 2016 09:32AM

Apple and Nintendo (as well as all L2CAP device manufacturers) stand a chance to claim reparations for unfair market practices on behalf of google for these actions. It cannot go unsung that the fraud in marketing and production has had negative outcomes for these parties as well.

If we do not find corrective-action on the issues, we will have to convince the legal departments of these parties as well as our fellow device-users to pursue action against Google.

te...@gmail.com <te...@gmail.com> #185Aug 30, 2016 04:41PM

NEed to connect My wiimote on my Samsung S7 please UPDATE THIS.

ib...@gmail.com <ib...@gmail.com> #186Sep 3, 2016 03:54PM

And another one hoppin' on the win10 train soon :)

bo...@gmail.com <bo...@gmail.com> #187Sep 28, 2016 04:04PM

C'est dommage de ne pas avoir intégré un bluetooth oùl'on ne peut pas connecter de manette.

cl...@gmail.com <cl...@gmail.com> #188Oct 19, 2016 12:42AM

This is insane. 2 years and still no fix. I expected a fully functioning bluetooth service. This is a disgrace.

ro...@gmail.com <ro...@gmail.com> #189Oct 19, 2016 05:33PM

Seriously, still no fix for this?

ha...@gmail.com <ha...@gmail.com> #190Oct 21, 2016 10:49PM

Same issue here on practically every device I own. Can confirm issue does not exist in ice cream sandwich but does on marshmallow and nougat. Others untested.

wi...@gmail.com <wi...@gmail.com> #191Oct 25, 2016 10:27PM

I can confirm that Android 4.2 somewhat broke it, then 4.4 fully made it not work, I need some confirmation on this

pe...@gmail.com <pe...@gmail.com> #192Nov 21, 2016 09:55AM

FIX THE DAMN L2CAP SUPPORT!!!!!!!!!!!!!!!

lu...@gmail.com <lu...@gmail.com> #193Dec 7, 2016 09:21PM

Seriously, fix this already. If the security is such an issue just require a user interaction to confirm a pairing, problem solved. Ridiculous.

pe...@gmail.com <pe...@gmail.com> #194Dec 22, 2016 11:38PM

Bring back L2CAP, please!

ma...@gmail.com <ma...@gmail.com> #195Dec 30, 2016 06:21PM

If it is not possible to return L2CAP support to Android in the near future, please release instructions on how to find the correct PIN address for pairing a Wii Remote (or a Wii Remote w/ MotionPlus) over Bluetooth to recent Android versions (I'm using 6.0.1, for instance). I'm sure this would make a lot of people happy.

ru...@gmail.com <ru...@gmail.com> #196Feb 6, 2017 12:35AM

And still we yet to have a fix or even a response. It's this kind of stuff that makes me feel unimportant and makes you guys look like you don't give a shit about your customer base.

ge...@gmail.com <ge...@gmail.com> #197Mar 5, 2017 09:33PM

Any news?

as...@gmail.com <as...@gmail.com> #198Apr 4, 2017 04:24AM

Please fix and support L2CAP on all Android devices

fn...@gmail.com <fn...@gmail.com> #199Apr 30, 2017 03:13AM

Gonna throw in some support for this, would like to see better Bluetooth compatibility.

jb...@gmail.com <jb...@gmail.com> #200May 3, 2017 04:45PM

Hey devs, at least say something, we asked for this fix years ago and people have been reminding you at least once a month since then. Is this whole thing just for show? Because it looks like you will run out of letters for android versions before we get a fix or a response at the very least.

na...@gmail.com <na...@gmail.com> #201May 3, 2017 04:52PM

Yes, the issue tracker is just for show.

ma...@gmail.com <ma...@gmail.com> #202May 3, 2017 04:58PM

That's reassuring. :/
The last dev response was just about 1.5 years ago, and it wasn't even anything worthwhile.

sh...@gmail.com <sh...@gmail.com> #203May 3, 2017 04:59PM

Please remove my email from this issue or list, I am not involved or even
know what this is about

On May 3, 2017 12:52 PM, <buganizer-system@google.com> wrote:

- Show quoted text -

jr...@gmail.com <jr...@gmail.com> #204May 3, 2017 05:02PM

Please remove me from this list as well. I don't know how my email got on
this list.

Thank you,

Jason

On May 3, 2017 12:59 PM, <buganizer-system@google.com> wrote:

- Show quoted text -

10...@gmail.com <10...@gmail.com> #205May 3, 2017 05:09PM

Same here, please remove me from the list.

Thanks

vi...@gmail.com <vi...@gmail.com> #206May 3, 2017 05:10PM

Please stop spamming and just click yellow star in top left corner on this issue's page.

na...@gmail.com <na...@gmail.com> #207May 3, 2017 05:10PM

If you read the bottom of the email, it will tell you why you're getting
notifications. Most likely: you starred this issue. Click the link to open
it and choose unstar.

On 3 May 2017 18:09, <buganizer-system@google.com> wrote:

- Show quoted text -

ro...@gmail.com <ro...@gmail.com> #208May 3, 2017 05:11PM

This is just great...

Op 3 mei 2017 19:09 schreef <buganizer-system@google.com>:

- Show quoted text -

aa...@gmail.com <aa...@gmail.com> #209Sep 9, 2017 07:08AM

Please fix this thank

ke...@gmail.com <ke...@gmail.com> #210Apr 29, 2018 06:52PM

pls help to fix it. we need some entertainment with bluetooth gamepad. thank you !

cl...@gmail.com <cl...@gmail.com> #211Jun 12, 2018 05:45PM

Please fix this I can see it but can't pair it! It's a shame...

wi...@gmail.com <wi...@gmail.com> #212Jul 9, 2018 07:52AM

Making a final decision on this issue sometime soon would be appreciated. At the very least, this kind of backwards-compatibility could cut down on e-waste by allowing the use of old bluetooth devices that would otherwise end up in landfill. I'm sure Google cared about that sort of thing at some point.

[Deleted User] <[Deleted User]> #213Jul 9, 2018 08:04AM

They dropped the "Dont be evil" slogan a while back

bl...@gmail.com <bl...@gmail.com> #214Oct 13, 2018 10:44PM

Por favor Reparar esto en una versión futura. Deja Inhabilitados los dispositivos bluetooth clásicos y no hay manera de conectarlos.
Gracias

ei...@google.com <ei...@google.com> Sep 26, 2019 10:25PM

Reassigned to an...@google.com.

sa...@gmail.com <sa...@gmail.com> #215Oct 9, 2019 10:34AM

Google still not willing to fix this?

ni...@gmail.com <ni...@gmail.com> #216Oct 9, 2019 01:52PM

Lol I commented in 2015, now 2019 still not fixed <.<

st...@gmail.com <st...@gmail.com> #217Oct 9, 2019 01:59PM

Google are about to come out with a game streaming service and want you to buy their controller. Why would they support all bluetooth gamepads?

sh...@gmail.com <sh...@gmail.com> #218Sep 22, 2020 12:52AM

Shlelhazen@gmail.com

th...@gmail.com <th...@gmail.com> #219Sep 23, 2020 04:15AM

Wow, I starred this 6 years ago. Still no fix. Thanks google. I've thrown my WiiMote out by now.

Issue 36976247

Description

Issue summary

Comments

so...@gmail.com <so...@gmail.com> #2Dec 8, 2013 08:49PM

aa...@aarcane.org <aa...@aarcane.org> #3Dec 8, 2013 09:27PM

jo...@gmail.com <jo...@gmail.com> #4Dec 8, 2013 09:39PM

kf...@gmail.com <kf...@gmail.com> #5Dec 9, 2013 02:35AM

pe...@gmail.com <pe...@gmail.com> #6Dec 15, 2013 06:02AM

bp...@gmail.com <bp...@gmail.com> #7Dec 25, 2013 05:43PM

me...@gmail.com <me...@gmail.com> #8Dec 28, 2013 09:55AM

fr...@gmail.com <fr...@gmail.com> #9Dec 28, 2013 02:51PM

kr...@gmail.com <kr...@gmail.com> #10Jan 4, 2014 01:36AM

gu...@gmail.com <gu...@gmail.com> #11Jan 8, 2014 11:26AM

ac...@gmail.com <ac...@gmail.com> #12Jan 11, 2014 03:47PM

li...@gmail.com <li...@gmail.com> #13Jan 12, 2014 10:15AM

bl...@gmail.com <bl...@gmail.com> #14Jan 13, 2014 01:44PM

bm...@gmail.com <bm...@gmail.com> #15Jan 13, 2014 05:47PM

mr...@gmail.com <mr...@gmail.com> #16Jan 14, 2014 07:15PM

ha...@gmail.com <ha...@gmail.com> #17Jan 21, 2014 09:56PM

vw...@gmail.com <vw...@gmail.com> #18Feb 2, 2014 11:41PM

st...@gmail.com <st...@gmail.com> #19Feb 12, 2014 04:11PM

gi...@gmail.com <gi...@gmail.com> #20Mar 2, 2014 06:35AM

ja...@gmail.com <ja...@gmail.com> #21Mar 5, 2014 11:42PM

rd...@gmail.com <rd...@gmail.com> #22Mar 6, 2014 02:47PM

bo...@gmail.com <bo...@gmail.com> #23Mar 14, 2014 09:28PM

as...@gmail.com <as...@gmail.com> #24Mar 18, 2014 02:43PM

[Deleted User] <[Deleted User]> #25Apr 15, 2014 03:12AM

de...@gmail.com <de...@gmail.com> #26Apr 27, 2014 03:32PM

de...@gmail.com <de...@gmail.com> #27May 1, 2014 03:19PM

le...@gmail.com <le...@gmail.com> #28May 4, 2014 08:28PM

br...@gmail.com <br...@gmail.com> #29May 27, 2014 05:34PM

bm...@gmail.com <bm...@gmail.com> #30May 28, 2014 06:27PM

[Deleted User] <[Deleted User]> #31Jun 1, 2014 03:35AM

cf...@hotmail.com <cf...@hotmail.com> #32Jun 8, 2014 06:47AM

cf...@hotmail.com <cf...@hotmail.com> #33Jun 8, 2014 06:48AM

an...@gmail.com <an...@gmail.com> #34Jun 8, 2014 06:42PM

ma...@gmail.com <ma...@gmail.com> #35Jun 15, 2014 04:31PM

tu...@gmail.com <tu...@gmail.com> #36Jun 24, 2014 03:00AM

dk...@gmail.com <dk...@gmail.com> #37Jun 24, 2014 04:28AM

si...@gmail.com <si...@gmail.com> #38Jun 25, 2014 12:37AM

ji...@gmail.com <ji...@gmail.com> #39Jun 25, 2014 06:43AM

jd...@gmail.com <jd...@gmail.com> #40Jul 18, 2014 08:50AM

ga...@gmail.com <ga...@gmail.com> #41Jul 30, 2014 12:17AM

au...@gmail.com <au...@gmail.com> #42Jul 30, 2014 12:55AM

th...@gmail.com <th...@gmail.com> #43Aug 1, 2014 11:13PM

jd...@gmail.com <jd...@gmail.com> #44Aug 1, 2014 11:42PM

jo...@gmail.com <jo...@gmail.com> #45Aug 2, 2014 12:29AM

jd...@gmail.com <jd...@gmail.com> #46Aug 2, 2014 12:45AM

jo...@gmail.com <jo...@gmail.com> #47Aug 30, 2014 03:32AM

ty...@gmail.com <ty...@gmail.com> #48Sep 4, 2014 08:31PM

jd...@gmail.com <jd...@gmail.com> #49Sep 4, 2014 10:23PM

1l...@gmail.com <1l...@gmail.com> #50Sep 7, 2014 10:05PM

ly...@gmail.com <ly...@gmail.com> #51Sep 11, 2014 09:27PM

di...@gmail.com <di...@gmail.com> #52Sep 12, 2014 09:28PM

[Deleted User] <[Deleted User]> #53Sep 15, 2014 04:55AM

mt...@gmail.com <mt...@gmail.com> #54Sep 27, 2014 04:14AM

jd...@gmail.com <jd...@gmail.com> #55Sep 30, 2014 02:29PM

ma...@gmail.com <ma...@gmail.com> #56Oct 7, 2014 12:35AM

nh...@gmail.com <nh...@gmail.com> #57Oct 7, 2014 04:48AM

fo...@umn.edu <fo...@umn.edu> #58Oct 15, 2014 11:26PM

to...@gmail.com <to...@gmail.com> #59Oct 15, 2014 11:26PM

ri...@gmail.com <ri...@gmail.com> #60Oct 18, 2014 10:29PM

te...@gmail.com <te...@gmail.com> #61Oct 19, 2014 02:22PM

em...@gmail.com <em...@gmail.com> #62Oct 23, 2014 10:38AM

wa...@gmail.com <wa...@gmail.com> #63Oct 23, 2014 05:16PM

mz...@gmail.com <mz...@gmail.com> #64Oct 26, 2014 04:19AM

on...@gmail.com <on...@gmail.com> #65Oct 31, 2014 03:28AM

on...@gmail.com <on...@gmail.com> #66Oct 31, 2014 03:29AM

bm...@gmail.com <bm...@gmail.com> #67Nov 3, 2014 02:38AM

fr...@gmail.com <fr...@gmail.com> #68Nov 3, 2014 06:35PM

di...@gmail.com <di...@gmail.com> #69Nov 5, 2014 03:26AM

er...@gmail.com <er...@gmail.com> #70Nov 5, 2014 12:32PM

ko...@gmail.com <ko...@gmail.com> #71Nov 9, 2014 06:12PM

ga...@gmail.com <ga...@gmail.com> #72Nov 10, 2014 01:46PM

ar...@hausic.de <ar...@hausic.de> #73Nov 14, 2014 10:11PM

mj...@gmail.com <mj...@gmail.com> #74Dec 4, 2014 09:44PM

wi...@gmail.com <wi...@gmail.com> #75Dec 6, 2014 12:50PM

jd...@gmail.com <jd...@gmail.com> #76Dec 23, 2014 04:21AM

ma...@gmail.com <ma...@gmail.com> #77Dec 24, 2014 03:00PM