From JP1 to Pronto hex

[Barf]

These files are Android configuration files, that at least I do not know how to interpret. Possible here is some Android expert? It is not obvious (at least not to me) how to make map them onto standard IR commands. (For example, some "keycodes" are > 255.)

Possibly you can capture a few commands using for example IrScrutinizer and suitable capturing hardware. We may then be able to make sense of the files. Or you can try to find the codes in some form on the Internet, for example on this site

[binky123]

#amlogic NEC remote
factory_code = 0xFE010001

I believe this means NEC1 device 1.

The key_begin section maps the IR keycode(OBC) into a Linux keyboard function.

0x15 139

This means OBC=31 will map into function 139 which is Menu.

So convert the file into some format that IrScrutinizer will accept and then have it generate an AnyMote file for you.

[The Robman]

#amlogic NEC remote
factory_code = 0xFE010001

I believe this means NEC1 device 1.

Actually, if the keycodes are not comp'd, I suspect that this is really dev 254. Unless, of course, the OBC hex code they give is really the 2nd byte and they comp to generate the first byte.

0x15 139

This means OBC=31 will map into function 139 which is Menu.

Did you mean to say OBC=21 ?

[Barf]

@shanx_verma:
Please upload all your file as a zip-archive (preserving the file names).

It appears that the "remote config" of Android is a established format; that it would make sense to be able to parse, for example as an importer in IrScrutinizer. Stay tuned.

[Barf]

I discovered that the Android remote.config format has been covered earlier, for example here.

@shanx_verma: U still there?