Remote control trouble

[superfreak79]

Can someone help me with a remote control problem?

I bought a generic ATV1200-like box and flashed XDA version of Linux XBMC. The remote that came with the box only works with the stock firmware though .

I logged the keystrokes of the new box using USB to RS232. I coped the "ircode" and "scancode" for each button (there are a lot of them!). See file here.

I also some information from the box: RM1200 KEY_A; VER1.4 13/C7/15; HX E339169 RoHS; 94-V0 1343.

How would I go about changing the standard remote.conf file to work with my new remote? Is it that simple?

Thanks!

[cde]

Are the ir codes from the stock or xda firmware? Assuming its from the stock since it's all mapped like valid scan codes, you simply need to edit the xda firmware's remote.conf. AFAIK, it's not in the same location as the stock firmwares use.

According to http://forum.xbmc.org/showthread.php...077#pid1315077

Answered my own question - S95xbmc will look for a /etc/xbmc/remote.conf or /root/.xbmc/remote.conf and amremote_config it - so that file overwrites the /etc/remote.conf that is executed on boot?

(The answer to that question is yes. Only the last run of the amremote program will be loaded)
Check to see if either of those exist, and copy the stock firmware /etc/remote.conf to those locations.

The entire thread is pretty good source of info for native xbmc firmwares and remotes.

Edit: This post from Pivos also confirms http://www.pivosforums.com/viewtopic...5&t=1008#p9122

You don't need to build an image for testing. Checkout /etc/init.d/S95xbmc

/usr/bin/amremote_config /etc/xbmc/remote.conf

amremote_config is the binary that reads the remote config and changes how it works.

create your new remote config and feed it to /usr/bin/amremote_config, test. rinse/repeat

[superfreak79]

Are the ir codes from the stock or xda firmware? Assuming its from the stock since it's all mapped like valid scan codes, you simply need to edit the xda firmware's remote.conf. AFAIK, it's not in the same location as the stock firmwares use.

Yes, stock firmware.

Which files do I need to change to make the remote work with new Android firmware and xbmc?
- amremote_config?
- remote.conf (which folders?)
- Vendor_0001_Product_0001.kl (or whatever it's called)

Also, I'm not sure what my remote factory code is... can you help?

Here is all the references to "remote" in my box startup. Do you see it? What else does this tell me?

[    1.752710@1] lirc_dev: IR Remote Control driver registered, major 250 
[    1.758260@1] IR NEC protocol handler initialized 
[    1.762923@1] IR RC5(x) protocol handler initialized 
[    1.767883@1] IR RC6 protocol handler initialized 
[    1.772559@1] IR JVC protocol handler initialized 
[    1.777256@1] IR Sony protocol handler initialized 
[    1.782019@1] IR RC5 (streamzap) protocol handler initialized 
[    1.787758@1] IR LIRC bridge handler initialized  

[    4.129570@1] Remote Driver 
[    4.132494@1] input: aml_keypad as /devices/platform/meson-remote/input/input0 
[    4.140108@1] meson_remote_pinmux_setup() 
[    4.143201@1] Remote platform_data g_remote_base=f3100480 

[    4.148597@1] Remote date_valye======0,status == 8915d20 
[    4.153902@1] remote config major:247 
[    4.158188@1] physical address:0x9f8ee000 
[    4.161741@1] ADC Keypad Driver init. 
[    4.165302@1] chan #4 used for ADC key 
[    4.168994@1] vol- key(114) registed. 
[    4.172623@1] vol+ key(115) registed. 
[    4.176554@1] input: adc_keypad as /devices/platform/m1-adckp.0/input/input1 
[    4.183745@1] adc keypad register input device completed. 
[    4.188793@1] adc keypad major:246 
[    4.192893@1] Meson KeyInput init 
[    4.195599@1] Key 116 registed. 
[    4.198942@1] input: key_input as /devices/platform/meson-keyinput.0/input/input2 
[    4.206643@1] Meson KeyInput register RTC interrupt 
[    4.210853@1] Meson KeyInput major=245  
[   10.896183@0] init: starting 'remote_control'  

[   11.017053@0] init: starting 'remotecfg' 
[   11.256206@1] init: 'remotecfg' (pid: 2409) started 
[   11.435982@0] init: process 'remotecfg', pid 2409 exited

Or is the factory code on the pcb? "RM1200 KEY_A; VER1.4 13/C7/15; HX E339169 RoHS; 94-V0 1343"

Thanks. I'm going to start editing my remote.conf today and assigning keys.

[cde]

Copy the working /etc/remote.conf in the stock firmware to either /etc/xbmc/remote.conf or /root/.xbmc/remote.conf in the new firmware. That's it.

The remote factory code is in the /etc/remote.conf but since you are copying it over and modifying it, you don't really need it.

[superfreak79]

Copy the working /etc/remote.conf in the stock firmware to either /etc/xbmc/remote.conf or /root/.xbmc/remote.conf in the new firmware. That's it.

The remote factory code is in the /etc/remote.conf but since you are copying it over and modifying it, you don't really need it.

Thanks. Your posts were helpful understanding IR codes. Unfortunately, I don't have access to the stock firmware because the proprietary software locks me out (long story short). I had everything working... and now my remote.conf was changed back to stock after a reboot. WTF.

[cde]

Since you already have the ir codes in the dropbox text file, all you need is the factory code.

Edit the /etc/xbmc/remote.conf to turn on debugging. Aim the remote at the box and press a few buttons. Check dmesg for something like:
[ 5094.377000] Wrong custom code is 0xXXYYZZZZ
[ 5095.872000] Wrong custom code is 0xef109c21
[ 5097.694000] Wrong custom code is 0xee119c21

Last four are the code. Factorycode = 0x9c210001 for example.

[superfreak79]

Since you already have the ir codes in the dropbox text file, all you need is the factory code.

Edit the /etc/xbmc/remote.conf to turn on debugging. Aim the remote at the box and press a few buttons. Check dmesg for something like:
[ 5094.377000] Wrong custom code is 0xXXYYZZZZ
[ 5095.872000] Wrong custom code is 0xef109c21
[ 5097.694000] Wrong custom code is 0xee119c21

Last four are the code. Factorycode = 0x9c210001 for example.

Thanks, unfortunately I'm not seeing "Wrong custom code"... only "invalid key is 0x0000". How else might I find the factorycode? Edit: I might be getting "invalid key" because I ran remotecfg again and that means the remote is now recognized again.

[cde]

Thanks, unfortunately I'm not seeing "Wrong custom code"... only "invalid key is 0x0000". How else might I find the factorycode? Edit: I might be getting "invalid key" because I ran remotecfg again and that means the remote is now recognized again.

Oh shiiiiiiiiiiiiiiiiit. I just had custom remote.conf in /system/etc and had been using remotecfg to trigger it. Duh, that's why on reboot it didn't work until I remotecfg again! Sound right?

Back to my previous question, is it possible to have a remote.config for Android actions and then another for within XBMC?

Invalid key means the factory code is recognized from the remote.conf but the key code is not in there. If I remember correctly. But since you found your remote.conf file, that's not an issue.

As for having different actions, no, not this way. remotecfg (or whatever its called in the xbmc firmware) sets it up for all of Android, like if it's a regular keyboard or hardware buttons. There are options to configure the regular xbmc hotkeys, but the special android keys like Media_Next are hardcoded to the android version of xbmc (I can't find where I saw the mappings at).

[superfreak79]

Invalid key means the factory code is recognized from the remote.conf but the key code is not in there. If I remember correctly. But since you found your remote.conf file, that's not an issue.

If I revert back to the old remote.conf for ATV520, then I guess the remote won't be recognized. Maybe that's how I capture the factory code.

[cde]

If I revert back to the old remote.conf for ATV520, then I guess the remote won't be recognized. Maybe that's how I capture the factory code.

If you get "wrong custom code" in dmesg, the factory code in the remote.conf is wrong.

If you get "invalid key" in dmesg, the factory code in remote.conf is the right one,

[superfreak79]

If you get "wrong custom code" in dmesg, the factory code in the remote.conf is wrong.

If you get "invalid key" in dmesg, the factory code in remote.conf is the right one,

If I flash Geniatech firmware (i.e., not stock) and then see "wrong custom code" in debug log, does that spit out the factory code for the remote or the firmware remote.conf? I hope that makes sense.