lets you remap buttons on your remote.
Simple example: in RF mode "Repeat" launches Music Player and "Aspect" launches Gmail, but this app lets me change it to launch MX Player and BlackBerry Inbox, respectively. More complex example: these buttons function differently in IR mode than in RF mode. With this app, I can make a single click of the REPEAT button perform the default IR function, and a double click perform the default RF function (launching MX Player), regardless of the actual current mode.
Unfortunately there are some limitations. In IR mode, some buttons seem to emit codes that are only recognized by the DTV app and are not assigned to any of the 283 standard Android button codes or to custom codes. Therefore this app cannot remap them
; nor can it perform these buttons' functions when pressing another button. Thus, this app can't make the DTV app fully functional in RF mode, as I'd hoped
. Edit: See the edit in the next paragraph. There may be a way to do this after all.
The buttons that are "limited" this way are: HDMI, TV/RADIO, USB, FAV, CC, ASPECT, and AUDIO.
Also, there doesn't seem to be a fix for the RETURN button acting like the EXIT button. In IR mode, these two buttons appear to send exactly the same code, so they cannot be distinguished. In RF mode they can, but the standard Android button code for "Previous Channel" doesn't work. Edit:
I FOUND THE CODE FOR PREVIOUS CHANNEL! It's listed in /etc/remote_key_config.xml, which appears to define the key codes for the DTV app. It's 2032, which is way beyond anything Android uses - but it works! Now my "RETURN" button functions correctly, at least in RF mode (still can't do anything about IR mode though).
Hint: if you install this, click "More Options" and turn on "Alternate button handling" in the options menu. Otherwise the Cyberbox will perform the button's original function as well as its reassigned function!
Originally Posted by Chut Mingy
Also plan to check if the irfake module will run on this box, or if the remote control codes can otherwise be altered.
Looks like irfake was written for a different chip. Might be possible to recompile from source targeting the S9xx family, but the irfake project is long gone from Google's site and the source was never archived.
Originally Posted by JHBrandt
Files remote_key_config.xml and remote.conf in the /etc directory look promising....
I ran into an annoying problem of remote interference with my Cyberbox this week: turns out the Cyberbox responds to the remote control used by both the CM-7004 and DVR+. Even worse, it responds in an unhelpful way: for example, the "up" button moves the cursor down, while the "down" button acts like OK on the Cyberbox remote. So, having earlier determined that the remote_key_config.xml file is only used by the DTV app, I decided to investigate the remote.conf file to see if I could find a way around this. And I ended up spending Saturday learning all the intricacies of remote.conf, only to finally discover that the Cyberbox doesn't even use it!
You can do anything you want to that file, even delete it entirely! It makes no difference. The Cyberbox always responds to its remote (and to the DVR+ remote) exactly the same way.
So I spent today trying to figure out why, and finally found the answer in this article: https://www.cnx-software.com/2017/03...st-quick-look/
Developers will also need to be aware the way to handle remote control codes has changed. The /system/etc/remote.conf is gone [except on the Cyberbox, where they apparently left it as a placebo], and instead Amlogic defines the codes in a specific DTSI (Device tree) file for remote code that includes definition for 3 remotes....
That led me down yet another rabbit hole, trying to figure out what the heck a "DTSI" file was and where it's stored on the Cyberbox. And it turns out, it's not
stored on the Cyberbox at all; instead, it's compiled into a "DTB" (Device tree BLOB) and stored in the boot/kernel partition. So the only way to change remote codes now is to patch the kernel!
Who the heck thought this was a good idea?
So after all that research, it turns out the only reasonable way around this remote interference problem is to block the IR receiver and use the remote exclusively in RF mode. Thanks to the Button Mapper app mentioned above, that's almost
feasible. Unfortunately one function still requires IR mode: turning the box on! If it's in standby the power button will work in RF mode, but if it's totally powered off, you must use IR mode to turn it on
I think that's because the RF dongle itself has no power if the box is off. Maybe I need to plug the dongle and my thumb drive into a powered hub?