<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 9/11/2013 12:48 PM, Mike Carron
wrote:<br>
</div>
<blockquote cite="mid:00fc01cedced$ccf1ed90$66d5c8b0$@net"
type="cite">
<pre wrap="">
-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:mythtv-users-bounces@mythtv.org">mythtv-users-bounces@mythtv.org</a>
[<a class="moz-txt-link-freetext" href="mailto:mythtv-users-bounces@mythtv.org">mailto:mythtv-users-bounces@mythtv.org</a>] On Behalf Of Stephen Worthington
Sent: Thursday, November 7, 2013 3:29 AM
To: Discussion about MythTV
Subject: Re: [mythtv-users] Improving the remote control
On Thu, 07 Nov 2013 15:36:43 +1100, you wrote:
</pre>
</blockquote>
<br>
<blockquote cite="mid:00fc01cedced$ccf1ed90$66d5c8b0$@net"
type="cite">
<pre wrap="">
Once you have your remote's keycodes working correctly, there are also two
more steps needed.
You need to make sure that the keycodes your remote is producing are mapped
by lirc. Look in your MythTV user's home directory for the ~/.lirc/mythtv
file (for Mythbuntu). In there, the keycodes are mapped to the keystrokes
sent to mythfrontend. The keycode must match the keycode produced from the
ir-keytables setup, and the keystrokes sent to mythfrontend have to match
those in its Setup pages.
Then, in mythfrontend, go to Setup > Edit Keys > JumpPoints and assign the
jump points you want to have working to have a key combination that works
from the keyboard. When I did this, there were not any values assigned by
default to the JumpPoints. As an example, I have assigned LiveTV to
Ctrl+Alt+T. Test that with your keyboard to make sure it works. Then in
your lirc setup in ~/.lirc/mythtv add or edit the setup so that the keycode
produced by the remote's LiveTV button is mapped to Ctrl+Alt+T. In my case,
this is what I have:
begin
remote = mceusb
prog = mythtv
button = LiveTV
config = Ctrl+Alt+T
repeat = 0
delay = 0
end
Also, go through the settings in that file and put in non-zero settings for
repeat and delay on the keys you want to have autorepeating, such as the
arrow and PgUp and PgDn keys. Then test and adjust those settings.
Remember to restart lirc every time you edit its config files.</pre>
</blockquote>
<br>
On this, I don't use lirc at all for my mce remote. Once it's
working with ir-keytable and a custom map there, lirc isn't actually
needed. If you want to use lirc, then you don't need to change the
ir-keytable map at all. Basically you can use either of these tools
to get the ir event codes into X/myth.<br>
Once I had the map in ir-keytable right, Xorg just picks it up as
another keyboard and the buttons can be used directly in myth.<br>
<br>
<blockquote cite="mid:00fc01cedced$ccf1ed90$66d5c8b0$@net"
type="cite">
<pre wrap="">
_______________________________________________
Thanks very much to both, I got those buttons working just fine and now my
next task is to figure out a clean way to resume from suspend using the
remote.
mike
</pre>
</blockquote>
<br>
I have my second frontend working this way, such that a button press
on the remote wakes it from suspend. I'm using a different remote
there however, one that presents itself as a hid keyboard to the
computer.<br>
Whether this is possible at all for you comes down the the remote
receiver and whether it'll operate in suspend mode. It also depends
on the motherboard.<br>
<br>
I found it took configuration in a few places to get this working
for me. <br>
Bios initially, had to make sure sleep was in the right mode. Not
sure which mode that was though, however for me it is one that's
suspend to ram, so there's no fans or anything powered on.<br>
After that, I went through a few things before getting it going, but
this all looks familiar: <a
href="http://askubuntu.com/questions/152403/how-do-i-make-changes-to-proc-acpi-wakeup-permanent">http://askubuntu.com/questions/152403/how-do-i-make-changes-to-proc-acpi-wakeup-permanent</a><br>
In particular this sort of stuff:<br>
<pre style="margin: 0px 0px 10px; padding: 5px; border: 0px; font-size: 14px; vertical-align: baseline; background-color: rgb(238, 238, 238); overflow: auto; width: auto; max-height: 600px; font-family: 'Ubuntu Mono', 'Ubuntu Beta Mono A', Consolas, 'Bitstream Vera Sans Mono', 'Courier New', Courier, monospace; word-wrap: normal; color: rgb(51, 51, 51); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 18px; orphans: auto; text-align: left; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><code style="margin: 0px; padding: 0px; border: 0px; font-size: 14px; vertical-align: baseline; background-color: rgb(238, 238, 238); font-family: 'Ubuntu Mono', 'Ubuntu Beta Mono A', Consolas, 'Bitstream Vera Sans Mono', 'Courier New', Courier, monospace; color: rgb(34, 34, 34);">echo enabled > /sys/bus/usb/devices/usb3/power/wakeup</code></pre>
You need to find which usb device the receiver is on and enable it
as wakeup device.<br>
You may also still need the /proc/acpi/wakeup stuff to ensure the
pci usb controller still has power to keep the receiver alive.<br>
After all that, there is a chance that only the power button on the
remote may work to wake it, I do remember reference to some
receivers behaving like that.<br>
<br>
If you get stuck somewhere I'll look at the configuration of mine at
home and see if anything there helps, however different
mobo/receiver does make it a bit harder.<br>
<br>
Have fun,<br>
Andrew<br>
</body>
</html>