michelcandido / btstack

Automatically exported from code.google.com/p/btstack
0 stars 0 forks source link

BTstack Keyboard for ATV: PS3 keypad detected but unable to pair to ATV2 #131

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Install btstack from nitoTV
2.Go to Settings -> Custom Settings -> btstack
3.On the "Searching..." page, "Wireless Keypad" appears and I can see its 
address and Device Type (HID Device) on the lower left part of screen.
4.Selecting the Wireless Keypad device asks me to Enter '0000' but anything I 
enter here seems to be "ignored".

What is the expected output? What do you see instead?
Nothing happens.
I get stuck at "Pairing: Enter '0000'" until I hit back to return to the 
BTstack devices window.
I tried entering 0000 [enter] at different speeds, adding more 0s and hitting 
[enter] twice (in case some keys would be ignored or something) & other 
combination without success.
I can see in BTstack logs that some stuff connected, but LEDs are still 
blinking on the keypad showing it still hasn't paired successfully.

What version of the product are you using? On what operating system?
BTstack 1.0.0-4 (installed from nitoTV)
AppleTV2 iOS 4.2.1 (language set to french, although I doubt it matters)
Jailbroken with Greenpois0n RC6
PS3 Wireless Keypad (the small keyboard that clips to the DualShock joypad)

Please provide any additional information below.
The PS3 keypad is detected AND pairs just fine with my iPhone4 (Apple BT stack) 
so I know it can be paired to other devices than a PS3 console.  When pairing 
it with the iPhone, as soon as I enter the keycode and hit enter, the LEDs on 
the keypad stop blinking and the keypad works.

I also tried launching btstack (keyboardd) directly from ssh (comparing to the 
youtube video linked on your 2010-10-31 news link):

AppleTV:~ root# keyboardd
launch_msg("CheckIn") IPC failure: 1BTdaemon started - stdout
BTdaemon started - stderr
Starting BTstack
BTstack working
BTstack working
HCI_EVENT_CONNECTION_COMPLETE from 00:24:33:F7:C8:96
Issuing role switch to become Master.

The last 2 lines appear as soon as I enter the "0000" keycode and hit [enter].  
Same behavior though: the ATV screen stays on the "Enter '0000'" screen and 
LEDs continue blinking (trying to pair) on the keypad.

Original issue reported on code.google.com by michel.l...@gmail.com on 6 Mar 2011 at 6:26

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by matthias.ringwald@gmail.com on 9 Mar 2011 at 10:46

GoogleCodeExporter commented 8 years ago
hi. could you also upload /tmp/hci_dump.pklg which contains the complete 
Bluetooth trace.

Original comment by matthias.ringwald@gmail.com on 9 Mar 2011 at 10:47

GoogleCodeExporter commented 8 years ago
Hi Matthias.  Here it is.  If you need anything else, let me know.

Original comment by michel.l...@gmail.com on 9 Mar 2011 at 11:49

GoogleCodeExporter commented 8 years ago
hi. I need the log after you tried to connect. the one in #3 just shows 
Bluetooth init

Original comment by matthias.ringwald@gmail.com on 9 Mar 2011 at 12:37

GoogleCodeExporter commented 8 years ago
Hi Matthias, sorry about that.

Here's a proper logfile.

Just so you know:
I reset the ATV2 (not sure if that clears the log or not).
Then I immediately launched BTstack from custom settings menu.
it detected the Wireless Keypad and I selected it.
It asked for '0000' keycode, which I entered a couple times (including Enter).
Then I hit "back"*, and selected the Wireless Keypad again.
The 2nd time, it gets stuck on the "Connecting..." screen rather than the 
"enter '0000'" screen that immediately follows it on 1st try.
I'm stuck there until I hit "back"* again to return to the "BTstack devices" 
screen.

*= I forgot which button it is on the original remote, I have it remapped on my 
Logitech Harmony.

Original comment by michel.l...@gmail.com on 10 Mar 2011 at 1:55

Attachments:

GoogleCodeExporter commented 8 years ago
i have the same action - do you know how to solve ?

Original comment by krec...@gmail.com on 11 Mar 2011 at 6:50

GoogleCodeExporter commented 8 years ago
No solution yet.  Hopefully Matthias will find something useful in the logs.

Original comment by michel.l...@gmail.com on 12 Mar 2011 at 5:27

GoogleCodeExporter commented 8 years ago
@michel: (sorry that's a really late answer). In the log, the keyboard declines 
the connection with error 0x0004: Connection Refused, no resources available. 
To be honest, I have no idea why it behaves like that. Maybe it is already 
connected to another device at this time? Can you make sure that's not the case?

Original comment by matthias.ringwald@gmail.com on 8 Nov 2011 at 7:18

GoogleCodeExporter commented 8 years ago
Hi Matthias.  Sorry for my late answer too.

I confirm that the device is not already connected to another devices.  The 
procedure to make new connection is to hold the blue button while turning the 
keypad ON (LEDs then start blinking and they keep blinking until the device has 
successfully paired to something).  The LEDs keep blinking all the time while 
I'm trying to pair it to the Apple TV.  If it had already connected to some 
other device, the LEDs would stop blinking.

I've updated to iOS 4.2.2 (AppleTV2,1_4.3_8F305_Restore.ipsw) and btstack 
1.0.1-1 (I think) since my initial post.  I just retested and got the same 
problem/symptoms though.  Would you like me to send new log files anyway?

I said I "think" I'm using btstack 1.0.1-1, because I'm not 100% sure how to 
confirm: on the NitoTV list of softwares, it says 1.0.0-4 (I thought this 
screen was displaying the current installed version and would say "Update" 
instead of "installed" if a new version is available) and when I select 
BTStack, it says 1.0.1-1 (still shows a "install" button instead of a "update" 
button).  I tried to hit Install anyway to make sure I get the latest version, 
but then it says "org.tomcool.btstack-ui is already the newest version / 0 
upgraded, 0 newly installed, 0 to remove and 11 not upgraded.".

Let me know if there's anything else I can do.

Original comment by michel.l...@gmail.com on 8 Dec 2011 at 3:07