OpenELEC for s82, M8, MXIII, Tronsmart S89

[wpb]

On www.amlinux.ru/image you can find different images for S82 (S89) round devices. Working without problem here (OE 5.0.3).

@MikeD, you had mentioned this before and on your advice I tried them all. I tried every one of their S82 images, including the newest 5.0.5. The S89 remote does not work with any of the Russian S82 releases.

Of course, remote config's do not work for bringing it back from power-save.

@JustMe has a remote-patch he released for several boxes, if there was any way to do this for the S89 (round s802's) it would be excellent.

[ccadi]

@MikeD, you had mentioned this before and on your advice I tried them all. I tried every one of their S82 images, including the newest 5.0.5. The S89 remote does not work with any of the Russian S82 releases.

Of course, remote config's do not work for bringing it back from power-save.

No idea why you remote does'nt work with these releases, my S89 works with them all and brings it back from power save on 5.0.5

[wpb]

No idea why you remote does'nt work with these releases, my S89 works with them all and brings it back from power save on 5.0.5

To confirm, you have the *round* Tronsmart S89 "Elite" box (2 GB / 8 GB), looks like this?

[ccadi]

I have tronsmart vega s89H

[wpb]

I have tronsmart vega s89H

Okay, you evidently got lucky. That is less common (the s802-H chipset) and more expensive.

I am referring to the basic S89 (S89B, using Amlogic s802-B) which is the more common device, by a significant margin.

To summarize for others, the S89 (2GB/8GB aka Elite aka S89B) remotes do not work with @CodeSnake or Russion S82 builds.

I would love/donate for an S89 remote patch.

[MikeD]

I have a clone of this device with 8GB (MEasy) and the remote does work. Btw it's the same remote, so it doesn't matter what device you have.

[wpb]

I have a clone of this device with 8GB (MEasy) and the remote does work. Btw it's the same remote, so it doesn't matter what device you have.

I have four (4) of the actual devices, and while it is indeed the same remote, it is a different chipset (802-H). For whatever reason, that must make a difference. Because on all four devices, I can use the Android ROM just fine, but cannot use ANY version of the OpenElec s82 builds.

If you don't have the actual device, please don't suggest that I'm wrong, simply because you've emulated the partition scheme and noticed the remotes are identical. There are other issues at work. Perhaps the IR-receiver (or way the chipset handles it) is different on the 802-H builds, I don't know. All I do know is that I have four devices and they are not working with the S82 builds.

I also have two S812 devices which work great with the Russian builds, for those interested in which device to buy.

[clarkss12]

I have four (4) of the actual devices, and while it is indeed the same remote, it is a different chipset (802-H). For whatever reason, that must make a difference. Because on all four devices, I can use the Android ROM just fine, but cannot use ANY version of the OpenElec s82 builds.

If you don't have the actual device, please don't suggest that I'm wrong, simply because you've emulated the partition scheme and noticed the remotes are identical. There are other issues at work. Perhaps the IR-receiver (or way the chipset handles it) is different on the 802-H builds, I don't know. All I do know is that I have four devices and they are not working with the S82 builds.

I also have two S812 devices which work great with the Russian builds, for those interested in which device to buy.

Which S812 boxes, and are they much better/faster than the S802 boxes. I have the S89H and it works great, but thinking about getting one of the S812 boxes.

Thanks for the information you gave.

[wpb]

Which S812 boxes, and are they much better/faster than the S802 boxes. I have the S89H and it works great, but thinking about getting one of the S812 boxes.

You know, I was hoping the s812 would be an upgrade, but so far I don't see it. At all. Sometime I feel like the UI is going faster than on the s802 boxes, but then I wonder if it's just a placebo effect.

One thing I've learned about buying Amlogic devices, if you want to run builds of XBMC, I cannot recommend the following enough: buy devices shown on geekbuying.com -- I'm not advocating that you buy from geekbuying at all, I personally buy from Amazon more often. It just seems that the devices sold by geekbuying eventually become the most popular/devices which ROM's are built.

For this reason I had tested two s812's, the geekbuying CX-S806 and the altered M8 (square) box they sell on Amazon, sold under "Tronfy".

I have not been able to get the s806/s812 ROM to install on the "Tronfy". The geekbuying works great.

s812's are about the same price as the s802 boxes, so there really is no down side to buying them, however, I don't really see an upside with one exception, you get a third USB port.

That reminds me, if you buy a s812 box, most of them require a USB-A to USB-A cable in order to get console (one of their USB ports is dedicated to working as a console port). I my case the Amazon "Superspeed USB 3.0 Type A Male to Type A Male" cable was the best quality/price option I could find.

Oh this again reminds me .. the s812's seem to be a bit more finicky to get into recovery-mode, which is why you may need the console cable sooner rather than later!

Hope that helps :-)

[MikeD]

I have four (4) of the actual devices, and while it is indeed the same remote, it is a different chipset (802-H). For whatever reason, that must make a difference. Because on all four devices, I can use the Android ROM just fine, but cannot use ANY version of the OpenElec s82 builds.

If you don't have the actual device, please don't suggest that I'm wrong, simply because you've emulated the partition scheme and noticed the remotes are identical. There are other issues at work. Perhaps the IR-receiver (or way the chipset handles it) is different on the 802-H builds, I don't know. All I do know is that I have four devices and they are not working with the S82 builds.

I also have two S812 devices which work great with the Russian builds, for those interested in which device to buy.

I use a harmony remote with preset of Tronsmart Vega (now pivos preset). It doesn't matter if I have original remote or harmony which send same ir signals.
You're the only one who said that his remote doesn't work. Everybody else have no problems. I know that in some russian development builds wake up did not work, but in all other releases it does.

Every build uses a remote.conf which defines what remote signals gets recognized from the ir receiver. So it does NOT matter which device is used or chip is built in. You could also use other remotes with same device if you change the remote.conf.
I don't know why it doesn't work for you but don't say that it doesn't work at all.

[wpb]

I don't know why it doesn't work for you but don't say that it doesn't work at all.

It sounds like with your emulated setup you are the definitive expert on the topic.

I'm so glad to run across someone that knows so definitively that these work. What a great relief to learn that it's just my four boxes that are bad, and the entire remainder of the world has no issue.

Being that you've got so much background on this, can you show me the information of all the others ("everyone") posting about how the S89 802B works great with the S82 builds? I didn't realize that everyone is running around posting about how the remote works great on the S802B S89 box and I'm the only one with the issue, and worse yet, that I happened to get FOUR boxes with this same problem.

[clarkss12]

You know, I was hoping the s812 would be an upgrade, but so far I don't see it. At all. Sometime I feel like the UI is going faster than on the s802 boxes, but then I wonder if it's just a placebo effect.

One thing I've learned about buying Amlogic devices, if you want to run builds of XBMC, I cannot recommend the following enough: buy devices shown on geekbuying.com -- I'm not advocating that you buy from geekbuying at all, I personally buy from Amazon more often. It just seems that the devices sold by geekbuying eventually become the most popular/devices which ROM's are built.

For this reason I had tested two s812's, the geekbuying CX-S806 and the altered M8 (square) box they sell on Amazon, sold under "Tronfy".

I have not been able to get the s806/s812 ROM to install on the "Tronfy". The geekbuying works great.

s812's are about the same price as the s802 boxes, so there really is no down side to buying them, however, I don't really see an upside with one exception, you get a third USB port.

That reminds me, if you buy a s812 box, most of them require a USB-A to USB-A cable in order to get console (one of their USB ports is dedicated to working as a console port). I my case the Amazon "Superspeed USB 3.0 Type A Male to Type A Male" cable was the best quality/price option I could find.

Oh this again reminds me .. the s812's seem to be a bit more finicky to get into recovery-mode, which is why you may need the console cable sooner rather than later!

Hope that helps :-)

Thanks for that valuable information. I thought the S812's would be faster, so I will wait for the next generation.

Thanks

[vermillion]

It sounds like with your emulated setup you are the definitive expert on the topic.

I'm so glad to run across someone that knows so definitively that these work. What a great relief to learn that it's just my four boxes that are bad, and the entire remainder of the world has no issue.

Being that you've got so much background on this, can you show me the information of all the others ("everyone") posting about how the S89 802B works great with the S82 builds? I didn't realize that everyone is running around posting about how the remote works great on the S802B S89 box and I'm the only one with the issue, and worse yet, that I happened to get FOUR boxes with this same problem.

As far as I can see MikeD was just trying to help.
Sarcasm will not help progress this thread, we all need to help each other to obtain the best out of our devices.

[MikeD]

It sounds like with your emulated setup you are the definitive expert on the topic.

I'm so glad to run across someone that knows so definitively that these work. What a great relief to learn that it's just my four boxes that are bad, and the entire remainder of the world has no issue.

Being that you've got so much background on this, can you show me the information of all the others ("everyone") posting about how the S89 802B works great with the S82 builds? I didn't realize that everyone is running around posting about how the remote works great on the S802B S89 box and I'm the only one with the issue, and worse yet, that I happened to get FOUR boxes with this same problem.

I know that many people use these S82 builds and nobody had problems so far with RC besides you. They won't say explicitly that their RC works because that should be normal for an image of their devices.

But here you can see, someone was confirming this who got problems before with codesnakes M8 builds:

http://www.FreakTab.com/showthread.php?p=286938

And what box do you have exactly? In this thread you said Tronsmart and in the other M8:

http://www.FreakTab.com/showthread.php?p=286713

Does your remote really looks like these on your photos?

If you copy the remote.conf from /etc to /storage/.conf, open it and set "debug_enable = 1" you can see after a reboot in dmesg if your box receive any ir signals from your RC. Just start a ssh session, hit some buttons and exec "dmesg".
If debug_enable is already set to 1 you don't need to copy it. I don't know what is standard setting.

The following is an example of remote.conf and should be the original one.
The factory code in first line sets the specific ir code which every RC has. With changing that you can use any other RC you want to. The other codes after "key_begin" define every button on the RC.
So without having a remote.conf for your RC you can just build your one by getting first your factory code and then every button code from dmesg if debug is enabled.

# Visson S82 / Beelink S82 remote
factory_code= 0x7f800001 
work_mode  = 0
repeat_enable = 1
release_delay= 121
debug_enable = 1
reg_control= 0xfbe40

key_begin
0x51 116;POWER
0x4d 66;MUTE
0x09 61;MEDIA
0x11 60;MUSIC
0x56 74;VOL-
0xbd 51;MEDIA_PREVIOUS
0xbb 52;MEDIA_NEXT
0x4e 78;VOL+
0x53 1;HOME
0x1b 14;EXIT
0x25 105;LEFT
0x26 103;UP
0x27 106;RIGHT
0x28 108;DOWN
0x0d 28;OK
0x49 46;MENU
0x31 2;NUM1
0x32 3;NUM2
0x33 4;NUM3
0x34 5;NUM4
0x35 6;NUM5
0x36 7;NUM6
0x37 8;NUM7
0x38 9;NUM8
0x39 10;NUM9
0x30 11;NUM0
0x44 111;DEL   
key_end

[wpb]

And what box do you have exactly? In this thread you said Tronsmart and in the other M8:

http://www.FreakTab.com/showthread.php?p=286713

Does your remote really looks like these on your photos?

If you notice, I posted the exact same image in all cases, that is the box I have, the Tronsmart S89. The problem, when I posted "M8" was that I was going by what others wrote in the post, thinking the term "m8" was the generic term being used for this box. That post was prior to my investigating the nuances between s802 boxes and learning that the S89 is indeed its own beast.

I technically have four S89, which is an s802B, plus two 812's as mentioned previously in the thread.

Prior to you posting, I had setup logging and went through the log to look for any IR codes. I had nothing from the built-in IR. My only codes are from a USB receiver I have plugged-in for an MCE remote.

Fortunately, as part of this process, it occurred to me that I could map the CEC-Power button to disable it. I was able to do that and have disabled CEC power-save. Now that CEC-power save is disabled, I don't need to determine the reason the Russian builds will not work with my S89 boxes. I would continue the fight if it would help others, but you seem to be certain that I'm the only person to have issues with this, so I might as well be happy with disabling CEC.

For anyone that stumbles on this post, my solution to disabling CEC Power-Save was to add a standard keymap ( \storage\.kodi\userdata\keymaps\keyboard.xml ) with the CEC key ID that I found from logging.

After having some trouble with this and talking to others, I tried using the Keymap Plugin for Kodi and that worked as well.

For anyone finding this thread by searching, the following code gives you an example of how I disabled the power-button with a simple keymap. Just keep in mind your "Key ID" will be different. This particular one comes from a 70" Sharp Aquos TV:

[COLOR=#000000][FONT=monospace]<keymap>[/FONT][/COLOR]

[COLOR=#000000][FONT=monospace]  <global>[/FONT][/COLOR]
[COLOR=#000000][FONT=monospace]    <keyboard>[/FONT][/COLOR]
[COLOR=#000000][FONT=monospace]     <key id="[/FONT][/COLOR]61662[COLOR=#000000][FONT=monospace]">Stop</key>[/FONT][/COLOR]
[COLOR=#000000][FONT=monospace]    </keyboard>[/FONT][/COLOR]
[COLOR=#000000][FONT=monospace]  </global>[/FONT][/COLOR]
[COLOR=#000000][FONT=monospace]  [/FONT][/COLOR]
[COLOR=#000000][FONT=monospace]</keymap>[/FONT][/COLOR]

Hope that can help someone else out there with the CEC issue. I see it posted frequently on the Russian forums.

Thanks to @MikeD for his input on the remote issue. Unfortunately for me, the S89 build and debug logs don't show any activity, but I've always used the MCE remote and only needed the native remote for purposes of restoring power, which is no longer an issue now that I was able to use the keymap.