Howto create a linux kernel IR remote keytable for Jivelite on piCorePlayer 5

[Hinguy]

The contents of the file is based on the procedure in the first post.

Please post your full config file.

The content of my file is:

#table: apple, type: nec
0x87eee50a KEY_UP
0x87eee50c KEY_DOWN
0x87eee509 KEY_LEFT
0x87eee506 KEY_RIGHT
0x87eee505 KEY_SPACE
0x87eee503 KEY_ENTER

As stated before, the file itself works like this, and even loads into jivelite after reboot, but doesn't get recognzied somehow. I've also checked the /opt/.filetool.lst in diagnostics and the file /usr/local/etc/keytables/jivelite is also listed in there.

I've also attached a screenshot of the scancodes sent by the white apple remote.
I am using the upload function and the file is simple named apple.conf.

Thank you very much.

[paul-]

After a reboot, what is the output of this command.

sudo ir-keytable -c -v -w /usr/local/etc/keytables/jivelite

[Jeff07971]

If you are loading manually, your file must be called /usr/local/etc/keytables/jivelite

The upload script will automatically rename whatever you upload to the above name. As jeff mentioned, keep spaces out of your upload name.

For backups, look on the diagnostics page and make sure that file is listed the section for /opt/.filetool.lst

Hi Paul-

I think it is something deeper than just not being backed up.

usr/local/etc/keytables/jivelite IS being backed up just not working after reboot

Default SB3 remote does not work after reboot either.





After reboot:-



File uploaded (via GUI) is this and appears to be backed up

RMTB119A.conf

table: RMTB119A, type: sony
0x1ae216 KEY_S
0x1ae215 KEY_POWER
0x1ae200 KEY_1
0x1ae201 KEY_2
0x1ae202 KEY_3
0x10012 KEY_EQUAL
0x1ae203 KEY_4
0x1ae204 KEY_5
0x1ae205 KEY_6
0x1ae206 KEY_7
0x1ae207 KEY_8
0x1ae208 KEY_9
0x10013 KEY_MINUS
0x1ae209 KEY_0
0x1ae269 KEY_D
0x1ae22c KEY_LEFTBRACE
0x1ae239 KEY_UP
0x1ae229 KEY_RIGHTBRACE
0x1ae23b KEY_LEFT
0x1ae23d KEY_ENTER
0x1ae23c KEY_RIGHT
0x1ae243 KEY_T
0x1ae23a KEY_DOWN
0x1ae23f KEY_GRAVE
0x1ae242 KEY_LEFTBRACE
0x1ae257 KEY_Z
0x1ae219 KEY_SPACE
0x1ae256 KEY_B
0x1ae21b KEY_E
0x1ae21a KEY_X
0x1ae21c KEY_R
0x1ae24b KEY_DOT
0x1ae218 KEY_G
0x1ae24c KEY_COMMA

Jeff

[Hinguy]

After a reboot, what is the output of this command.

sudo ir-keytable -c -v -w /usr/local/etc/keytables/jivelite

That's actually a good hint. Somehow the protocols get disabled after reboot. I attached the output BEFORE and AFTER reboot.
But what causes the protocols to be disabled?

BEFORE:


AFTER:


Thanks for helping

[paul-]

It is normal for all protocols to be disabled, it only enables the ones that you request....... The last line of output from

sudo ir-keytable -c -v -w /usr/local/etc/keytables/jivelite should be
......
Protocols changed to sony, or whatever you have in your keyfile.


I just missed this on first scan of your file, but. This line must start with a comment "#"

#table: RMTB119A, type: sony

[Hinguy]

It is normal for all protocols to be disabled, it only enables the ones that you request....... The last line of output from

sudo ir-keytable -c -v -w /usr/local/etc/keytables/jivelite should be
......
Protocols changed to sony, or whatever you have in your keyfile.


I just missed this on first scan of your file, but. This line must start with a comment "#"

#table: RMTB119A, type: sony

Ooooh great! Thank you so much. That was actually the problem :-)
It now works even after reboot!

I just took it from the very first post by Ralphy, and he also didn't put the "#" in the first line. Maybe it would be good to change it, so that no other dummies like me fall into that trap :-)


But again thank you very much!

[Jeff07971]

It is normal for all protocols to be disabled, it only enables the ones that you request....... The last line of output from

sudo ir-keytable -c -v -w /usr/local/etc/keytables/jivelite should be
......
Protocols changed to sony, or whatever you have in your keyfile.


I just missed this on first scan of your file, but. This line must start with a comment "#"

#table: RMTB119A, type: sony

Thanks Paul-

As Hinguy said all works now !

Jeff

[paul-]

Hey Hinguy.,

Can you edit your post to remove the incorrect version (or fix it)...I'm sure Ralpy will see this and correct the OP.

But glad it's working now.

Paul

[Hinguy]

Hey Hinguy.,

Can you edit your post to remove the incorrect version (or fix it)...I'm sure Ralpy will see this and correct the OP.

But glad it's working now.

Paul

Sure, already done! :-)

[ralphy]

I'm sure Ralpy will see this and correct the OP.
Paul

Sorry for the confusion. Fixed.