yashsingh1/xdaforums huggingface dataset:
[Android General] bacon612:
Yup. I'm crushed over this.
[Android General] mathsz:
You can always downgrade to 4.1.2. Works very well and it's a very close experience to 4.2.2...
[Android General] Pepelusky:
I've found a solution on some android forums around the internet, dont know if i can post links but you google skillz should help you, there's a workaround using a "HID enabler" on the Bluez IME controller, tested and working for me on a Galaxy tab Plus p6210 running stock and rooted android 4.1.2 jelly bean (the method does not require root)
[Android General] bacon612:
It works beautifully on 4.1.2. Its 4.2 and above that is the sole reason this thread exists.
[Android General] mathsz:
precisely
[Android General] max805:
Question

Do you think it would work if I had multirom and used a 4.1 rom on it?
[Android General] barbonjoe:
Someone have tested the wiimote with the 4.3 galaxy s4 rom?

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Android General] mathsz:
I'm awaiting to see if it works. the wii controler classic is the best, IMO.
[Android General] adam9936:
So I've tried syncing and pairing with my wiimote on 4.3 that I just downloaded (nexus 7) and no dice. I thought enhanced Bluetooth support would be fixing this issue? Does anyone have any input on 4.3 prospects? Thanks.
[Android General] michael13162:
I'm in the exact same boat. 4.3 ota on the original nexus 7 not rooted and I have the same issue of requiring an unknown pin. I'm planning on returning to stock 4.1 just so I can connect...

Someone should just ask the six axis devs how they fixed it for the ps3 controller.
[Android General] pickled-onion:
Does anyone know if dev of the WiimoteController app is anywhere near 4.2 support?
[Android General] michael13162:
I've tried the wiimote ime app, bluez ime with hid enabler, and standard Bluetooth...
[Android General] a8ksh4:
Here's something that sort of works - change the bluetooth MAC address of the android device to "30 30 30 30 30 30" and the pin to pair becomes "000000" when you use the red button on the wiimote. This is confirmed working on my Nexus 7 2013.

To change the android device's bluetooth MAC, first disable bluetooth and then open a shell and do the following:

su

cd /persist/bluetooth

cp .bdaddr .bdaddr.orig

echo -n 000000 > .bdaddr
​

That's six zeros in the echo line. You can compare the old and new contents of .bdaddr using hexdump:

hexdump -C .bdaddr

hexdump -C .bdaddr.orig
​

Turn bluetooth back on and you'll have the updated MAC address and will be able to pair with the wiimote.

It seems that we still need some software to tell android what to do with the wiimote once it's paired... none of the stuff I can find in the market works... they all want to handle the pairing and can't see a controller that's already paired. Does anyone have ideas here?
[Android General] Maui:
You would start to communicate with the paired device using the "hidden" android.bluetooth.hid.HidService.java. Unfortunately they seemed to have deliberately disabled the callbacks for GET_REPORT and SET_REPORT, so the HID Support is of no use in 4.3. It's also lacking L2CAP support and there is no bluez to talk to.
[Android General] a8ksh4:
Maui, does this mean that we need custom kernel or BT kernel module module to support wiimote? What other BT functionality is impacted by this limitation? Thx.
[Android General] bacon612:
Damn. I just read through this. Looks we may have a fix. I'll copy Wiimote software devs on this thread.
[Android General] saikoz:
[MENTION=4429707]bacon612[/MENTION] any updates?
[Android General] ocritocrit:
i am using android 4.3 but not nexus,

I'm typing cd /persist/bluetooth

but they said no direction

sorry for bad English

おはよう, こんばんは :)
[Android General] Angelus89:
Has there been any progress in this, has google realized the problems they have cause? Are any developers on this? I'm a programmer, but in not too good at hardware, im thinking I might take a look at this. Just need to be brought up to date first.
[Android General] ◱ PixelyIon:
Wiimotes should wok as cool joysticks
[Android General] bpsim:
4.2 rom here still waiting better solution to link wiimote.....
[Android General] Angelus89:
It Doesnt look like Google are going to switch the Wifi Back to Bluez, so someone needs to make a new app.
[Android General] mathsz:
unfortunately, bluedroid (new stack)is here to stay. It's in every github repos. For now, unless someone develops it, the only solution is going back to 4.1.x or lower. because the bluetooth hack works with bluez.

I got it to pair (android, not through app) by spoofing (forcing) a mac adress on my phone (00000000). but the app wants to handle the connection and fails.

Too bad though. Ps3 controller for me at the moment.

by the by, 4.4 will probably have bluedroid too, since they upgraded to fix some stuff. Fixed some, broke some.

---------- Post added at 09:19 AM ---------- Previous post was at 09:16 AM ----------

https://play.google.com/store/apps/details?id=com.dancingpixelstudios.gamepadenabler

wonder if that would work, combined with spoof mac adress. I guessing no since hid is out.
[Android General] bacon612:
Wait.... Are you saying that ps3 remotes pair without issues?
[Android General] mathsz:
https://play.google.com/store/apps/details?id=com.dancingpixelstudios.sixaxiscontroller&hl=en

^This

plus a usb cable to connect to pc to force your phone's bluetooth adress on the controller

bingo
[Android General] sugarfreetargets:
So has anyone tried connecting a wiimote on 4.4 or the Nexus 5 yet?
[Android General] Levistras:
Came to join the party...

So I have a Nexus 7 2013 Wi-Fi 16gb, running Android 4.4 KRT16O (released today).

Apps like Snes9X+, which have built-in wiimote pairing.. aren't working.

I tried the method above, after rooting my device and successfully changing the BT Mac address, I was indeed able to pair the wiimote with the red key using PIN "000000". However.. also as above, I wasn't able to do anything with the Wiimote at this point through the device. The wiimote lights kept flashing as if the pairing didn't really complete.. but Android shows it as paired as an input device.
[Android General] Drahric:
Their is no /persist directory, is there another place where this is?

Let the ring-bearer decide...
[Android General] PortlandKhro:
covering torynlol

Anyone had any luck pairing lately?
[Android General] 150pilot:
I have had complete success pairing my wiimote with my new LG G PAD 8.3 Running 4.2.2 and the Wiimote Controller app from the PlayStore. Works with SNES emulator and Sonic the Hedgehog. However i can't get the wiimote to pair with an Asus Memopad HD 7 that I have here as well running 4.2.2.
[Android General] nucks1000:
partial solution

There's an app that will connect your wiimote to the Android device but once connected its still useless ,hope it works for you as for my all i need is the pin because the kindle fire hd 7 is picking it up as a controller but like you all said the pin is unknown .
[Android General] darren1:
Which app?
[Android General] nucks1000:
WORKS

Sorry ,tried to edit it earlier but the noob restrictions are in place, its called wiimote controller and the mistake i made was i forgot to change the IME-changing from the native key board to the wiimote. The only issue i found in this was that you cant actually type in any thing as it replaces the native key board like i said a minute ago:fingers-crossed:
[Android General] Deozaan:
Supposedly this works, but you may need to connect a bluetooth dongle to your device:

http://xdaforums.com/showthread.php?t=2381953
[Android General] McSwindler:
I know I'm a bit late to the party, but I just recently upgraded to a 4.4 phone (previous 4.0) and discovered this little mishap.

Anywho, I was messing around with an app, trying to see if I could recode it to work at all. (The app was FitScales, not mine but open source)

I was able to pair the balance board successfully and within the bluetooth manager the device claims to be a joystick, I'm then able to connect to the paired device via the new GATT protocol.

Now, I was trying this out because with KitKat a new feature is HID over GATT and I thought I might could get some communication with that. Here's where I hit a wall, with the GATT you have to discover services which then returns a list of UUIDs. Whenever I called that method after a successful connection, the onServicesDiscovered callback never gets called even though discoverServices returns true (the callback is supposed to be called whether it passes or fails). In theory, the wiimote/balance board should have at least 1 service the correlates to the joystick capability.

Then, I decided to back out all of the GATT stuff and go back to the classic bluetooth sockets and see if anything changed (it hadn't). But When I get the parcelUUIDs from the bluetooth device it returns one, but then trying to connect to a socket using that UUID still fails.

I was wondering if anybody had any ideas about using GATT? Is it possible at all to communicate to a wiimote with it? This little project is honestly the most I've ever worked with Android, so it's very possible I'm just screwing it :P
[Android General] NMGxda:
I know this may have been done but has anybody checked the wii console code to see how it accepts without a PIN? Maybe if we can simulate the signal the Wii make when you press it's sync buttton and use that. Just a though.
[Android General] LazyCouchPotato:
So I finally made an XDA account just to reply to this thread.

First of all, it's amazing that you guys have put in effort for so long for finding a solution.

I wanted to bring two things to your attention: android-review.googlesource.com/#/c/137040/ and review.cyanogenmod.org/#/c/89843/

I am currently running the second-latest nightly of CM12 (12/03/15) using multiboot and I gave it a try. When I try to connect the Wiimote using my primary ROM I'm asked to enter a pin. However when using CM12 the Wiimote does connect without using any sort of pin.

Imgur.com/AEdq4gm

The four lights on the remote keep blinking. If you read the comments in the CM commit, there's a link that takes you to some kernel related stuff. I don't really all of it, but could this make the Wiimote finally work?
[Android General] mathsz:
This is what will fix it

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

read latest entry

lc2app support was missing in current stack. That should allow older apps to work again because they will allow the bt adress 00:00:00:00:00:00 with a blank pin to connect.

THAT TOOK SO FRIGGIN' long, it's incredible.

now, if you don't have a nexus or update phone : SOL.
[Android General] Acid0057:
Wonder if we can convince Cyanogenmod to merge this into cm11 and 12.1

Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
[Android General] bacon612:
That would be amazing. How do we go about doing that?
[Android General] darren1:
Would anyone be able to make a Xposed mod to apply this fix?
[Android General] Acid0057:
That's an awesome idea! I don't have any experience programming but I'd love to see someone do it.

Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
[Android General] LazyCouchPotato:
Thanks for replying. I am currently running Euphoria ROM based on 5.0.2 on my Nexus 4.

In my previous post I had linked to the CM commit too : review.cyanogenmod.org/#/c/89843/

I gave it a try, by installing CM12 nightly as a secondary ROM using multirom. Like I said in my previous post #79 it does connect, but I tried various apps to try to get it to actually work, it didn't.
[Android General] Acid0057:
Well I was hopeful [emoji20]

Sent from my GT-I9100 flowing on SwiftKey in Tapatalk
[Android General] wyvern5layer:
has anyone applied this?

Has anyone been able to apply this fix and how did you do it?
[Android General] Assassindeity:
Its been two years, finally good to see a fix :)

This would be amazing if its possible for someone to do.
[Android General] Assassindeity:
Same here, I have cm12.1 and am able to connect the bluetooth but it wont work after that with any apps. If you try to set it as an input method it looses connection also
[Android General] LazyCouchPotato:
I'm hoping there's someone still working on this. I got a PSTV and can use the Sixaxis controller which is extremely easy to connect to the phone thanks to the Sixaxis Controller app. I wish we had something that easy for the Wii also, but I don't think there's a cable to connect the Wiimote to a USB port.
[Android General] LazyCouchPotato:
https://www.youtube.com/watch?v=fzM0UXf-bDE

Wanted this to be noticed by you guys. Wiimote support on an Nvidia SHIELD TV. I'm not sure how they got it to work.
[Android General] graveyrd:
I realize this is an old thread but I finally got my wiimote working on CM12.1 tonight and I just wanted to put it out there because I have been reading the internet for the past 2 hours trying to see if this was possible and I almost gave up but LazyCouchPotato gave me hope with a link to review.cyanogenmod.org/#/c/89843/ and sure enough, wiimote pairing works great in Cyanogenmod 12+ with Bluez IME. I ended up more-or-less following the instructions from here: androidforums.com/threads/bluetooth-wiimote-fix-stock-sense.692392/ The instructions are a bit different though because I didn't need to do the quick pairing (it just works automatically).

Hopefully this confirmation helps someone else because I certainly would have loved to read something like this earlier today.
[Android General] mercury201010:
thank you graveyrd. I appreciate the confirmation
[Android General] Saber4life:
can i ask how to use c code?? i really don't speak programmer
[Android General] Curtis428:
Can someone figure out my Wii remote pin for me please?? 00:19:1D:8F: D2: DC
[Android General] Acid0057:
[MENTION=8229012]Curtis428[/MENTION] the pin is always 0000 but some Bluetooth drivers don't support the Wii mote
[Android General] ScottHDev:
I've actually successfully paired (BOUND_BOUNDED) with a wiimote from an android device running android 8 (api26) with c++ JNI and java.

But, I couldn't create the L2CAP connection without crashing when running android.bluetooth.BluetoothSocket.connect(); with the created socket.

Seems like L2Cap api isn't yet supported as the code is hidden : https://android.googlesource.com/pl...a/android/bluetooth/BluetoothDevice.java#1454

(If you ask, I've been able to create the socket with this code :

/**
* Create a BluetoothSocket using L2CAP protocol
* Useful for HID Bluetooth devices
* @param BluetoothDevice
* @return BluetoothSocket
*/
private static BluetoothSocket createL2CAPBluetoothSocket(BluetoothDevice device, int port){
final int TYPE_RFCOMM = 1;
final int TYPE_SCO = 2;
final int TYPE_L2CAP = 3;
int type = TYPE_L2CAP; //L2CAP protocol
int fd = -1; //Create a new socket
boolean auth = false; //No authentication
boolean encrypt = false; //Not encrypted
try {
Constructor<BluetoothSocket> constructor = BluetoothSocket.class.getDeclaredConstructor(
int.class, int.class, boolean.class, boolean.class,
BluetoothDevice.class, int.class, ParcelUuid.class);
constructor.setAccessible(true);
BluetoothSocket clientSocket = (BluetoothSocket) constructor.newInstance(
type, fd, auth, encrypt, device, port, null);
return clientSocket;
} catch (Exception e) {
e.printStackTrace();
return null;
}
}
[Android General] TheIronLefty:
Hey scott the new android 10 has support for L2CAP socket openings can u please test it out and if it works drop us a guide on how to do it as well?
[T-Mobile Samsung Galaxy Note II] whitedavidp:
Hello. I wrote an app to deal with a problem with the SPen on my N7000 Samsung Note. Not sure if it will work on other Note models but would appreciate someone trying it out and telling me if it works on their device as well. Please see my original posting here. Thanks
[T-Mobile Samsung Galaxy Note II] whitedavidp:
Reset Spen Pro Now Available

A low priced version of this app is now available on the Play Market. It offers additional convenience and other features including scheduled background operation and suppression of success messages. If the free version works on your device, I hope you will consider the Pro version. Thanks!
[T-Mobile Samsung Galaxy Note II] My1xT:
Maybe I want to but I cant buy it in Germany...
[T-Mobile Samsung Galaxy Note II] whitedavidp:
Thanks for letting me know. I am totally new to the Google Play thing. Should be available now in Germany and elsewhere. Happy holidays!
[T-Mobile Samsung Galaxy Note II] My1xT:
shouldnt it be play store instead of play market???
[T-Mobile Samsung Galaxy Note II] whitedavidp:
I think technically, yes it is Play Store. Thanks!
[T-Mobile Samsung Galaxy Note II] My1xT:
the free app is available but the pro Still isnt available in German PS
[T-Mobile Samsung Galaxy Note II] whitedavidp:
I have found that the changes I make to my Google Play settings often take several hours to actually take effect. Please check back in a while. I'd appreciate hearing if/when the changes take effect as I have no visibility here except in the US. Sorry for the delay. And thanks again for your help.
[T-Mobile Samsung Galaxy Note II] My1xT:
no problem I like to help, but why didnt superSU ask me if it wants root but granted it anyway and no notification @all

just rooted my N2 today, but i have xPerience with rooting
[T-Mobile Samsung Galaxy Note II] whitedavidp:
I presume that you are speaking to the free version off the Play Store... The only reason I can think of is that SU is configured to globally grant permission under its default access setting and its show notifications is off by default in its settings (or maybe these are just on the Reset Spen app - but I doubt that).
[T-Mobile Samsung Galaxy Note II] My1xT:
I didnt inatall it from PS it came with my root, but however I am clever enought to ensure I like the settings, just after root...
[T-Mobile Samsung Galaxy Note II] whitedavidp:
Sorry, I meant did you get my app (Reset Spen) from the Play Store or from this site?

In my experience, SU does come with the rooting process.

So if you look at the SU settings, what is set for the following:

(a) Enable Super User

(b) Re-Authentication

(c) Default Access

(d) Show Notifications

On My Note N7000 with SuperSu v0.99, I have:

(a) checked/enabled

(b) checked/ask for permission again if app re-installed or upgraded

(c) prompt

(d) checked/show a toast

Then in the list of apps shown in superSU:

1. Do you see Reset Spen in the list?

2. If so, is the right side # green (mine is green) or another color

3. If so, click the its list item and tell me:

(a) the setting for access (mine is now grant)

(b) the setting for notifications (mine is global default - the answer to (d) above)

Thanks.
[T-Mobile Samsung Galaxy Note II] My1xT:
yes you app is the free from PS

well @the settings I know that should be perfect and of course they are set (the note is my 2nd device, 1st had superuser, so it may be my 1st time with sSU, but I have xPerience)

and the list was the 1st thing I checked...

green # and grant (that's why the # is green) and global def...
[T-Mobile Samsung Galaxy Note II] whitedavidp:
Thanks. I am sure you are actually more experienced than I am. I just wanted the details so I could help see what is going on.

So Reset Spen has been granted su access (green).

Are you getting a success popup after tapping the Reset Spen icon? You should always get one (success or a failure error message). If you get the message and it is success, then the app should have done its thing. There is no other user interface than the popup message. If you get success, the question remains - did it help your SPen situation? Has has for many others (but not all).

Thanks for your patience in trying to help me figure out the issue(s).
[T-Mobile Samsung Galaxy Note II] My1xT:
the thing is that it works fine, but somehow it got root before sSU even asked, and thats what confuses me...

and I get your success msg but nothing from sSU
[T-Mobile Samsung Galaxy Note II] whitedavidp:
Ah, ein Licht aufgeht! I am sorry but I have no idea why that would be if the global grant of access is not enabled in superSU. I am glad though that my app at least produces its success message. Does it help at all with your SPen's situation? Thanks
[T-Mobile Samsung Galaxy Note II] My1xT:
well, I didnt got this becuase I HAD problems, I got this, coz, I stumbled upon it, and when that occurs I have something...

but really, when you write German, do it right, it should be "Ah, ein Licht geht auf!"
[T-Mobile Samsung Galaxy Note II] whitedavidp:
Funny, that is how I recall the phrase from my high school German classes some 40 years ago. But doubting myself, I used Google Translate and this is what it gave me. Sorry. I meant to show off, not insult. But it back-fired :)
[T-Mobile Samsung Galaxy Note II] My1xT:
well, ok I didnt insult you, just forgot an emoticon...

---------- Post added at 08:22 PM ---------- Previous post was at 07:42 PM ----------

it can be used in Germany, but it shows compatibility with non-note devices, could you fix that???

I have no dev xPerience, so I am truly sorry that I cant help...
[T-Mobile Samsung Galaxy Note II] whitedavidp:
That is odd/interesting. I actually had to write some Javascript code to execute in Firefox to manually exclude all of their listed devices from the compatibility list and then manually put the Note devices back. Can you give me 1-5 examples of devices they show as compatible that are NOT Note devices? Thanks.
[T-Mobile Samsung Galaxy Note II] My1xT:
I can only give you one, coz the only device other than my Note2 is my Huawei Ideos x3 (U8510) with CM7.2
[T-Mobile Samsung Galaxy Note II] whitedavidp:
Interesting. Thanks for the report of what you see. I have triple-checked my device exclusions for both free and paid apps and the U8510 is shown in both as excluded. You can see this is the attached screen print. Not sure what to do.
[T-Mobile Samsung Galaxy Note II] My1xT:
when did you do that???

maybe I check tomorrow again...

but I saw on your shot that also enough devices which definitely arent Note are enabled. ist it able to make it the other way. Whitelisting the working devs, instead of Blacklisting all the non-working devs???

or is it able to set some reqirements for the devices which "kill" all the others???
[T-Mobile Samsung Galaxy Note II] whitedavidp:
I did this yesterday, I think. But perhaps things have not yet updated.

Amazingly you can only manually exclude one at a time. There are almost 2000 devices on the list. You cannot exclude by manufacturer. And for each manufacturer you must press the show more button to make sure you have seen all the devices offered. I have submitted a change request on this but doubt it will come soon. Meanwhile, my crude Javascript made this tolerable but still not fast. I ran it to exclude ALL then manually remove the Note devices from the excluded list.

It is true that some devices are automatically excluded based upon some properties of the app itself. But the list of those was quite small indeed.
[T-Mobile Samsung Galaxy Note II] My1xT:
for starters you can exclude all non JB devices, Note1 and 10.1 just got the JB Update...

and 2 has jb out of the box

I mean the N2 was exluded for some reason at some apps even though some app was comp. with it
[T-Mobile Samsung Galaxy Note II] whitedavidp:
1. My Note has no official JB yet. I read it is coming and there are leaked versions that I am avoiding (enough troubles as it is).

2. Why does JB have anything to do with it? I haven't got it so I cannot test it. But I presume the SPen issues are on JB as well as the earlier versions of Android for the Notes. It certainly is a problem on my ICS 4.0.4.
[T-Mobile Samsung Galaxy Note II] My1xT:
ok, in Germany JB was rolled out recently, but the fact is, with Jelly bean as requrement you can rule out most of the devicesor try ICS for starters, that should rule out MANY devices too...