Posts: 4
Joined: Mar 2012
Reputation:
0
I'm wondering how you guys where able to pair reliably with your tivo slide.
I'm able to pair with it with blueman, but after 10 minutes, the remote goes to sleep and while it sometimes reconnect, it's not always the case. And when it does reconnect, it takes nearly a minute to do so.
Just to note, I'm not using the supplied usb dongle because I could not make it to work.
I'm using bluez 4.96.
Posts: 4
Joined: Mar 2012
Reputation:
0
2012-03-09, 02:08
(This post was last modified: 2012-03-12, 11:14 by goyman.)
I tried to use the USB dongle but it's not working on my linux box.
It is seen as a normal bluetooth dongle by linux, but when I press the physical button on the dongle, the dongle led never blink.
On my mac, I can use the USB dongle, when I press the button the led starts blinking after 1 second. On my mac the dongle is seen as a bluetooth dongle, and the remote is shown as paired via bluetooth when it is paired using the dongle.
UPDATE: I removed the bluetooth driver from the linux box, and now when I press the usb receiver button, I can pair the remote. But after a few minutes, the pairing is lost.
Posts: 442
Joined: Apr 2010
Reputation:
24
2012-03-26, 05:41
(This post was last modified: 2012-03-26, 05:50 by teaguecl.)
Eden xbmcbuntu update:
I spent all day upgrading to 11.0 Eden, and thought I would share my experience. The easiest way to get this remote working is to:
1. remove bluetooth
- sudo apt-get remove bluez
- sudo apt-get remove blueman
- sudo rm /etc/init.d/bluetooth (this shouldn't be necessary, bluez uninstall is supposed to remove this)
2. disable bluetooth modules
- put these lines into a /etc/modprobe.d/blacklist* file:
blacklist btusb
blacklist bluetooth
At this point, you should be able to reboot, pair the dongle and remote (press Tivo+Blue on remote, then press dongle button), and use evtest to make sure the keys are working.
To get the keys working that are normally mapped strangely, I use keyfuzz. It's very non-standard, I think udev is a better way to go - but I haven't done that yet.
Side note: xbmcbuntu has a lot of unecessary packages with it. If you are using this remote, you don't need lirc for example - I highly recommend removing it.
As a follow up to my experiments today with Eden. There are two ways to use this remote, which has led us to lots of confusion. The two methods are:
1. as a USB keyboard. This means no bluetooth, it uses something called USB HID Emulation. The dongle talks via bluetooth to the remote, but it presents itself to the operating system as a USB keyboard. This is what I describe in my previous post, you need to completely disable bluetooth.
2. as a bluetooth keyboard. The dongle presents itself as a Bluetooth adapter to the operating system, and allows you to connect to the remote as a BT device. This is what most people are trying to do, and I found it quirky and unreliable. To do this I used blueman (which is based on bluez) to pair with the keyboard using PIN 0000. It works, but my experience was that it needed manual re-pair'ing after the remote timeouts (about 5 minutes), and every time you reboot your htpc.
I highly recommend method #1. The only drawback is that you can't use other bluetooth devices - which isn't a problem for me.
Posts: 4
Joined: Mar 2012
Reputation:
0
Deinstalling bluetooth packages and blacklisting kernel module was the solution. It now works, thanks!
Posts: 2
Joined: Apr 2012
Reputation:
0
Thanks for the posting ... with this information I was able to get the tivo slide working with ubuntu 12.04 LTS.
I am having issues with remapping the channelup and down button (402 and 403).
I have modified the /etc/X11/xorg.conf and added the following lines but the remap is not working.. any ideas?
Section "InputClass"
Identifier "tivo-slide"
Driver "evdev"
Option "event_key_remap" "116=1 402=103 403=108"
MatchProduct "HID 150a:1201"
EndSection
here is the output from evtest:
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x150a product 0x1201 version 0x111
Input device name: "HID 150a:1201"
Supported events:
....
Testing ... (interrupt to exit)
Event: time 1334009379.183743, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0030
Event: time 1334009379.183752, type 1 (EV_KEY), code 116 (KEY_POWER), value 1
Event: time 1334009379.183755, -------------- SYN_REPORT ------------
Event: time 1334009379.319668, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0030
Event: time 1334009379.319676, type 1 (EV_KEY), code 116 (KEY_POWER), value 0
Event: time 1334009379.319683, -------------- SYN_REPORT ------------
Event: time 1334009383.325364, type 4 (EV_MSC), code 4 (MSC_SCAN), value c009c
Event: time 1334009383.325371, type 1 (EV_KEY), code 402 (KEY_CHANNELUP), value 1
Event: time 1334009383.325373, -------------- SYN_REPORT ------------
Event: time 1334009383.517252, type 4 (EV_MSC), code 4 (MSC_SCAN), value c009c
Event: time 1334009383.517258, type 1 (EV_KEY), code 402 (KEY_CHANNELUP), value 0
Event: time 1334009383.517264, -------------- SYN_REPORT ------------
Event: time 1334009383.925032, type 4 (EV_MSC), code 4 (MSC_SCAN), value c009d
Event: time 1334009383.925039, type 1 (EV_KEY), code 403 (KEY_CHANNELDOWN), value 1
Event: time 1334009383.925042, -------------- SYN_REPORT ------------
Event: time 1334009384.172884, type 4 (EV_MSC), code 4 (MSC_SCAN), value c009d
Event: time 1334009384.172889, type 1 (EV_KEY), code 403 (KEY_CHANNELDOWN), value 0
Event: time 1334009384.172895, -------------- SYN_REPORT ------------