Archive:TiVo Slide - Revision history

Karellen: Text replacement - "{{helix updated}}" to ""

2020-11-14T07:20:32Z

Text replacement - "{{helix updated}}" to ""

← Older revision		Revision as of 07:20, 14 November 2020
Line 403:		Line 403:

	* The Slide has no "Menu" button, which Kodi would normally use to bring up the context menu. A good replacement for this is to use the {{button\|Guide}} button.		* The Slide has no "Menu" button, which Kodi would normally use to bring up the context menu. A good replacement for this is to use the {{button\|Guide}} button.

	~~{{helix updated}}~~

Karellen at 02:27, 10 September 2020

2020-09-10T02:27:45Z

← Older revision		Revision as of 02:27, 10 September 2020
Line 149:		Line 149:
	{{editor note\|This might not be updated yet.}}		{{editor note\|This might not be updated yet.}}

	Create a plain text file called tivo_slide.xml (or anything .xml) and save it in the '''keymaps''' folder inside of the '''~~[[Userdata\|~~userdata folder]]'''. The file should look like this:		Create a plain text file called tivo_slide.xml (or anything .xml) and save it in the '''keymaps''' folder inside of the '''userdata folder'''. The file should look like this:

	<pre>		<pre>
Line 402:		Line 402:
	* The Slide has no "Stop" button, and therefore neither does it's remote. You can either stop playback when {{button\|Back}} is pressed, or use the "slow-mo" button, since Kodi doesn't have a slow-mo function.		* The Slide has no "Stop" button, and therefore neither does it's remote. You can either stop playback when {{button\|Back}} is pressed, or use the "slow-mo" button, since Kodi doesn't have a slow-mo function.

	* The Slide has no "Menu" button, which Kodi would normally use to bring up the ~~[[Basic_controls#Context_Menu\|~~context menu]]. A good replacement for this is to use the {{button\|Guide}} button.		* The Slide has no "Menu" button, which Kodi would normally use to bring up the context menu. A good replacement for this is to use the {{button\|Guide}} button.

	{{helix updated}}		{{helix updated}}


	~~[[Category:Remotes]]~~

Karellen: Karellen moved page TiVo Slide to Archive:TiVo Slide without leaving a redirect: Outdated

2020-09-10T02:26:38Z

Karellen moved page TiVo Slide to Archive:TiVo Slide without leaving a redirect: Outdated

← Older revision	Revision as of 02:26, 10 September 2020
(No difference)

Karellen at 02:08, 23 July 2020

2020-07-23T02:08:52Z

← Older revision		Revision as of 02:08, 23 July 2020
Line 17:		Line 17:

	= Windows instructions =		= Windows instructions =
	{{editor note\|Does someone want to throw in the instructions on how to use ~~[[EventGhost\|~~Event Ghost]] with the Slide?}}		{{editor note\|Does someone want to throw in the instructions on how to use Event Ghost with the Slide?}}

	= Linux instructions =		= Linux instructions =

Karellen at 05:18, 10 July 2020

2020-07-10T05:18:44Z

← Older revision		Revision as of 05:18, 10 July 2020
Line 17:		Line 17:

	= Windows instructions =		= Windows instructions =
	{{editor note\|Does someone want to throw in the instructions on how to use [[Event Ghost]] with the Slide?}}		{{editor note\|Does someone want to throw in the instructions on how to use [[EventGhost\|Event Ghost]] with the Slide?}}

	= Linux instructions =		= Linux instructions =
Line 149:		Line 149:
	{{editor note\|This might not be updated yet.}}		{{editor note\|This might not be updated yet.}}

	Create a plain text file called tivo_slide.xml (or anything .xml) and save it in the '''keymaps''' folder inside of the '''[[userdata folder]]'''. The file should look like this:		Create a plain text file called tivo_slide.xml (or anything .xml) and save it in the '''keymaps''' folder inside of the '''[[Userdata\|userdata folder]]'''. The file should look like this:

	<pre>		<pre>
Line 402:		Line 402:
	* The Slide has no "Stop" button, and therefore neither does it's remote. You can either stop playback when {{button\|Back}} is pressed, or use the "slow-mo" button, since Kodi doesn't have a slow-mo function.		* The Slide has no "Stop" button, and therefore neither does it's remote. You can either stop playback when {{button\|Back}} is pressed, or use the "slow-mo" button, since Kodi doesn't have a slow-mo function.

	* The Slide has no "Menu" button, which Kodi would normally use to bring up the [[context menu]]. A good replacement for this is to use the {{button\|Guide}} button.		* The Slide has no "Menu" button, which Kodi would normally use to bring up the [[Basic_controls#Context_Menu\|context menu]]. A good replacement for this is to use the {{button\|Guide}} button.

	{{helix updated}}		{{helix updated}}

	~~[[Category:How-to]]~~
	[[Category:Remotes]]		[[Category:Remotes]]
	~~[[Category:TiVo]]~~

Davu at 12:03, 10 July 2018

2018-07-10T12:03:02Z

← Older revision		Revision as of 12:03, 10 July 2018
Line 36:		Line 36:
	Disabling bluetooth is necessary to force the dongle into USB HID Emulation mode. There may be another way to do that, but so far this is the only method discovered. From a command line, issue the following commands:		Disabling bluetooth is necessary to force the dongle into USB HID Emulation mode. There may be another way to do that, but so far this is the only method discovered. From a command line, issue the following commands:

	<syntaxhighlight lang="bash">		<syntaxhighlight lang=bash>
	sudo apt-get remove bluez		sudo apt-get remove bluez
	sudo apt-get remove blueman		sudo apt-get remove blueman
Line 72:		Line 72:

	:'''1.''' Open up a terminal command line window or SSH into the HTPC box and type the following command. To make it easy to cut and paste, consider doing this from a desktop interface on the linux box, if you can.		:'''1.''' Open up a terminal command line window or SSH into the HTPC box and type the following command. To make it easy to cut and paste, consider doing this from a desktop interface on the linux box, if you can.
	::<syntaxhighlight lang="bash">sudo nano /etc/udev/hwdb.d/95-tivoslide.hwdb</syntaxhighlight>		::<syntaxhighlight lang=bash>sudo nano /etc/udev/hwdb.d/95-tivoslide.hwdb</syntaxhighlight>

	::{{Note\|For an OpenELEC system, use <code>/storage/.config/hwdb.d/95-tivoslide.hwdb</code> instead of the above file name.}}		::{{Note\|For an OpenELEC system, use <code>/storage/.config/hwdb.d/95-tivoslide.hwdb</code> instead of the above file name.}}
Line 84:		Line 84:

	::{{Note\|Make sure that there is a space at the start of each line that says KEYBOARD_KEY.}}		::{{Note\|Make sure that there is a space at the start of each line that says KEYBOARD_KEY.}}
	<syntaxhighlight lang="text">		<syntaxhighlight lang=text>
	evdev:input:b0003v150Ap1201*		evdev:input:b0003v150Ap1201*
	evdev:input:b0003v150Ap1203*		evdev:input:b0003v150Ap1203*
Line 121:		Line 121:
	:'''5.''' Go back to the terminal command line and enter the following command:		:'''5.''' Go back to the terminal command line and enter the following command:

	::<syntaxhighlight lang="bash">sudo nano /etc/udev/rules.d/95-keymap.rules</syntaxhighlight>		::<syntaxhighlight lang=bash>sudo nano /etc/udev/rules.d/95-keymap.rules</syntaxhighlight>


Line 129:		Line 129:
	:'''7a.''' For the original bluetooth Side remote, add the following to the file:		:'''7a.''' For the original bluetooth Side remote, add the following to the file:

	::<syntaxhighlight lang="text">SUBSYSTEM=="input", SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="150a", ENV{ID_MODEL_ID}=="1201", RUN+="/lib/udev/keymap $name /etc/udev/hwdb.d/95-tivoslide.hwdb"</syntaxhighlight>		::<syntaxhighlight lang=text>SUBSYSTEM=="input", SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="150a", ENV{ID_MODEL_ID}=="1201", RUN+="/lib/udev/keymap $name /etc/udev/hwdb.d/95-tivoslide.hwdb"</syntaxhighlight>


	:'''7b.''' For the newer Side Pro remote, add the following to the file:		:'''7b.''' For the newer Side Pro remote, add the following to the file:

	::<syntaxhighlight lang="text">SUBSYSTEM=="input", SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="150a", ENV{ID_MODEL_ID}=="1203", RUN+="/lib/udev/keymap $name /etc/udev/hwdb.d/95-tivoslide.hwdb"</syntaxhighlight>		::<syntaxhighlight lang=text>SUBSYSTEM=="input", SUBSYSTEMS=="usb", ENV{ID_VENDOR_ID}=="150a", ENV{ID_MODEL_ID}=="1203", RUN+="/lib/udev/keymap $name /etc/udev/hwdb.d/95-tivoslide.hwdb"</syntaxhighlight>


Line 141:		Line 141:

	:'''9.''' Now enter the following command to load these changes		:'''9.''' Now enter the following command to load these changes
	::<syntaxhighlight lang="bash">sudo udevadm hwdb --update</syntaxhighlight>		::<syntaxhighlight lang=bash>sudo udevadm hwdb --update</syntaxhighlight>

Illumilore: /* Re-map problem keys */

2018-05-27T23:36:29Z

Re-map problem keys

← Older revision		Revision as of 23:36, 27 May 2018
Line 85:		Line 85:
	::{{Note\|Make sure that there is a space at the start of each line that says KEYBOARD_KEY.}}		::{{Note\|Make sure that there is a space at the start of each line that says KEYBOARD_KEY.}}
	<syntaxhighlight lang="text">		<syntaxhighlight lang="text">
	~~keyboard~~:~~usb~~:~~v150Ap1201~~*		evdev:input:b0003v150Ap1201*
	~~keyboard~~:~~usb~~:~~v150Ap1203~~*		evdev:input:b0003v150Ap1203*
	KEYBOARD_KEY_000c0041=enter #SELECT		KEYBOARD_KEY_000c0041=enter #SELECT
	KEYBOARD_KEY_000c0046=backspace #BACK		KEYBOARD_KEY_000c0046=backspace #BACK
Line 109:		Line 109:
	KEYBOARD_KEY_ffff0042=pageup # Thumbs Up		KEYBOARD_KEY_ffff0042=pageup # Thumbs Up
	</syntaxhighlight>		</syntaxhighlight>
	::{{Note\|On ~~newer~~ systems, ~~such as~~ Ubuntu 15.10 or OpenELEC 7.0, the udev device matching syntax has changed, and you will need to use <code>~~evdev~~:~~input~~:~~b0003v150Ap1203~~</code> and <code>~~evdev~~:~~input~~:~~b0003v150Ap1201~~</code> in place of <code>~~keyboard~~:~~usb~~:~~v150Ap1203~~</code> and <code>~~keyboard~~:~~usb~~:~~v150Ap1201~~</code> respectively. See https://wiki.archlinux.org/index.php/Map_scancodes_to_keycodes#Using_udev for more details		::{{Note\|On older systems, before Ubuntu 15.10 or OpenELEC 7.0, the udev device matching syntax has changed, and you will need to use <code>keyboard:usb:v150Ap1203</code> and <code>keyboard:usb:v150Ap1201</code> in place of <code>evdev:input:b0003v150Ap1203</code> and <code>evdev:input:b0003v150Ap1201</code>respectively. See https://wiki.archlinux.org/index.php/Map_scancodes_to_keycodes#Using_udev for more details

	:'''4.''' Press {{keypress\|ctrl+x}} to exit editing and then press {{keypress\|y}} to save. The file name should already be correct, so press {{keypress\|return}} to actually save the file.}}		:'''4.''' Press {{keypress\|ctrl+x}} to exit editing and then press {{keypress\|y}} to save. The file name should already be correct, so press {{keypress\|return}} to actually save the file.}}

Xijix: Updated note on udev device matching syntax to refer to OpenELEC 7 as well.

2016-05-28T19:12:11Z

Updated note on udev device matching syntax to refer to OpenELEC 7 as well.

← Older revision		Revision as of 19:12, 28 May 2016
Line 109:		Line 109:
	KEYBOARD_KEY_ffff0042=pageup # Thumbs Up		KEYBOARD_KEY_ffff0042=pageup # Thumbs Up
	</syntaxhighlight>		</syntaxhighlight>
	::{{Note\|On newer systems, such as ~~ubuntu~~ 15.10, the udev device matching syntax has changed, and you will need to use <code>evdev:input:b0003v150Ap1203</code> and <code>evdev:input:b0003v150Ap1201</code> in place of <code>keyboard:usb:v150Ap1203</code> and <code>keyboard:usb:v150Ap1201</code> respectively. See https://wiki.archlinux.org/index.php/Map_scancodes_to_keycodes#Using_udev for more details		::{{Note\|On newer systems, such as Ubuntu 15.10 or OpenELEC 7.0, the udev device matching syntax has changed, and you will need to use <code>evdev:input:b0003v150Ap1203</code> and <code>evdev:input:b0003v150Ap1201</code> in place of <code>keyboard:usb:v150Ap1203</code> and <code>keyboard:usb:v150Ap1201</code> respectively. See https://wiki.archlinux.org/index.php/Map_scancodes_to_keycodes#Using_udev for more details

	:'''4.''' Press {{keypress\|ctrl+x}} to exit editing and then press {{keypress\|y}} to save. The file name should already be correct, so press {{keypress\|return}} to actually save the file.}}		:'''4.''' Press {{keypress\|ctrl+x}} to exit editing and then press {{keypress\|y}} to save. The file name should already be correct, so press {{keypress\|return}} to actually save the file.}}

Illumilore: /* Re-map problem keys */

2015-11-19T00:22:54Z

Re-map problem keys

← Older revision		Revision as of 00:22, 19 November 2015
Line 109:		Line 109:
	KEYBOARD_KEY_ffff0042=pageup # Thumbs Up		KEYBOARD_KEY_ffff0042=pageup # Thumbs Up
	</syntaxhighlight>		</syntaxhighlight>
			::{{Note\|On newer systems, such as ubuntu 15.10, the udev device matching syntax has changed, and you will need to use <code>evdev:input:b0003v150Ap1203</code> and <code>evdev:input:b0003v150Ap1201</code> in place of <code>keyboard:usb:v150Ap1203</code> and <code>keyboard:usb:v150Ap1201</code> respectively. See https://wiki.archlinux.org/index.php/Map_scancodes_to_keycodes#Using_udev for more details

			:'''4.''' Press {{keypress\|ctrl+x}} to exit editing and then press {{keypress\|y}} to save. The file name should already be correct, so press {{keypress\|return}} to actually save the file.}}
	:'''4.''' Press {{keypress\|ctrl+x}} to exit editing and then press {{keypress\|y}} to save. The file name should already be correct, so press {{keypress\|return}} to actually save the file.

NedBot: Bot: Automated text replacement (- XBMC + Kodi )

2015-05-04T08:55:16Z

Bot: Automated text replacement (- XBMC + Kodi )

← Older revision		Revision as of 08:55, 4 May 2015
Line 144:		Line 144:


	{{bluev\|So why did we do this?\|There are several reasons why you need to re-map keys on the Tivo Slide remote. First, due to a limitation of X.org no keycodes with values larger than 255 can be used. There are several such keys on this remote. Therefore they need to get re-mapped from large keycodes (>255) into smaller ones so that applications like ~~XBMC~~ can use them. Second, you may want to re-map some keys to do something more useful than their default.}}		{{bluev\|So why did we do this?\|There are several reasons why you need to re-map keys on the Tivo Slide remote. First, due to a limitation of X.org no keycodes with values larger than 255 can be used. There are several such keys on this remote. Therefore they need to get re-mapped from large keycodes (>255) into smaller ones so that applications like Kodi can use them. Second, you may want to re-map some keys to do something more useful than their default.}}

	== Further map keys using a Kodi keymap ==		== Further map keys using a Kodi keymap ==