The new repo is here Repository for Amlogic & Meson IR Remote Controllers
Please follow the protocol to upload new remote files.
sorry, but canât you make something more with the remote itself. So like a picture of the remote and a download link to it if you press the picture? Then you can just search more easy for your remote, since a remote can be compatible with more boxes. You could just as well name the remote file zip and the jpg the same and throw them all into one big folder.
*after some research, might be not a good idea. Although some remotes might look the same, internal they arenât. Maybe the remote must look exactly the same, so all the same buttons at the same place. Some remotes have some buttons right at another place but further look the same. Then itâs still a total different remote, so the remote.conf wonât work. Canât you make the folders remotebased or add a remotebased folderstructure? So, like the folder has a jpg on it you can click on to open the folder. Inside that folder all the remotes that lookalike.
Then thereâs something else, it seems some buttons of a remote wonât be scanned by the box coreelec. So i guess thatâs a bug that needs to be fixed in a later version. @anon88919003
The problem with that is that most of the remotes look the same but still require different configurations, that idea is far too complicated for most people because it means multiple rounds of testing to find the correct one, there is no one size fits all solution here due to the shear plethora of devices that exist.
Also please donât hijack threads, if you have a bug to report then do it in an appropriate thread where it can be explored properly.
I wouldnât have a scooby how to do that. (clickable link on picture)
I think, trying a couple of remote configurations with the same name is a small price to pay. People can always customise the buttons on their particular remote.
Betamaster has done all the hard work for this new repo, but Iâm sure he would be open to offers of help.
probably if the remote looks total the same, it is the same and it works with the same remote.conf. But it happens that some buttons are at a different location on the remote control, then it sudden is a completely different remote and doesnât work with that remote.conf. So, downloading a remote.conf according to jpg of remotes does help.
No it does not, the vendor codes are different and it results in the rest of the codes being different.
are you saying you canât configure different remotes using the same box?
No? I said remotes that look the same do not always have the same remote codes.
Your suggestion that remote configs be grouped simply by the pictures of them would not work because the remote codes are sometimes different even for remotes that look the same, this would result in users having to test multiple configs in order to find the correct one.
Not everybody has the same technical skill level and would find such a task very cumbersome, people want to be pointed to the exact config for their device, which is exactly what the op has done in his remote repo.
so itâs the remote thatâs different, not the box. In other words, the remote.conf is remotecontroldependant.
Exactly.
The boxes are almost identical hardware wise with just different emmc/ram/wifi chips and remotes being used.
ok. The trick with scanning the buttons of a remote, is to keep one scancode with function(button) uncommented and the rest commented. And to remove the rc_keymapssample file. This way the box only takes the buttons from your remote. This way it works.
Hereâs the remote.conf file for the U2C ZPRO (S905X): remote.conf (717 Bytes)
The âstopâ button is under the mouse, fastforward is the 3 button, fastback is the 1 button. 
@bubblegum57 or @Betatester could you please upload my remote.conf files in this topic?
While I appreciate you creating this, we would like people to follow the guide lines for submitting a remote. So from here
Package submission guidelines:
- Before submitting, first research if the RCU is already listed in the repository
- Include the full name of the RCU (
ex: L8star G30)
if the RCU came with a TV Box, the name of the TV Box (ex: Xiaomi Mi Box S) has to be included - Include a picture of the RCU
if the RCU came with a TV Box or USB Dongle, they have to be included in the picture - The minimum picture size is 500 x 500 pixels with the unit and its peripherals clearly visible. JPEG format is preferred
- The files are to be archived in zip format and should include a completed CREDITS.TXT file
mark1978 @bubblegum57 or @Betatester could you please upload my remote.conf files in this topic?
We greatly appreciate your enthusiasm to contribute.
Unfortunately, your submissions are not meeting the requirements for acceptance into the repository.
We encourage all contributors to follow repository guidelines.and post their files in the repository forum thread located at: Repository for AmRemote & Meson IR Remote Controllers
For your review and consideration, I have re-posted the repository guidelines bellow:
Contributing
We envision this project to be community supported under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported (CC BY-NC-SA 3.0) license agreement, therefore a few guidelines have been established.
Those who wish to contribute can do so by:
-
reporting inconsistencies within the repository
-
submitting configuration files for unlisted units
Package submission guidelines:
-
Before submitting, first research if the RCU is already listed in the repository
-
Include the full name of the RCU (
ex: L8star G30)
if the RCU came with a TV Box, the name of the TV Box (ex: Xiaomi Mi Box S) has to be included -
Include a picture of the RCU
if the RCU came with a TV Box or USB Dongle, they have to be included in the picture -
The minimum picture size is 500 x 500 pixels with the unit and its peripherals clearly visible. JPEG format is preferred
-
The files are to be archived in zip format and should include a completed CREDITS.TXT file
Currently, contributions are only accepted by posting them in our CoreELEC Forums Thread
After submitting the package, its contents will be scanned for viruses and reviewed for compliance and integrity.
Once approved, the package will become available at our repository.
Successfully contributions will be credited by having the contributors CoreELEC Forums screen name listed in the package documentation.
Non-compliant contributions and duplicates will be rejected
2 Likes
does anyone already have a remote.xml for the firetv v2 with the volume buttons?
The remote control actually works fine. it only bothers me when I press the power button. The Odroid N2 goes off and when you change the volume, the volume changes in the Kodi itself and not just on the TV (soundbar).
Deutsch
hat schon jemand eine remote.xml fĂŒr den firetv v2 mit den Volume tasten?
die Fernbedienung funktioniert eigentlich ok. mich stört es nur das, wenn ich auf die Power taste drĂŒcke. Der Odroid N2 mit aus geht und wenn man die LautstĂ€rke verĂ€ndert, dann verĂ€ndert sich auch die LautstĂ€rke im Kodi selbst und nicht nur TV(Soundbar)
@bubblegum57 and @Betatester adamg said in this forum, that even though the remote might look the same, it still can be a completely different remote and that you should focus more at the combination of box and remote together. People just want to search on their box and download the according remote.conf next. So, could you put my remotes also to the repo?
Gooddday, if you could upload the remote.conf and tell me what buttons do the false actions, i could edit the file for you.
deutsch
Ich habe keine remote.conf Datei.
Die Fernbedienung funktionierte sofort, nachdem ich es ĂŒber Bluetooth verbunden habe
I donât have a remote.conf file.
The remote worked immediately after I connected it via Bluetooth
and it works with a remote.xml? Then you should edit that file.
You need to try to connect via blue tooth
The way I understand it, is that remote files use Infra Red signals.