[ROM] Unofficial OpenELEC for MXIII-G & Tronsmart MXIII+

[cwh060]

I have an odd problem which exists in OpenElec 6.0.0 or any Android firmware for that matter. The same problem exists if I load Tronsmart 106L firmware, 113L or Remix
s 115.

My box is an MXIIIG. I can not install any skin.

I can install just about every add on I like and it works without problem, skins; however are just not co-operating. I have uploaded my log files the problems start on Line 222. It's reporting an MD5 issue. I am going to try loading from a zip and see if this works, I suspect not.

Any idea what may be going on with this thing? First time using OpenElec, I like it...although wish I could find a better way to integrate Neflix.

Thanks
cwh

[ricpersi]

Hi wilro,

did you have any time to try booting archlinux on the MX3G? In a previous post you mentioned that amlogic hasn't yet made public u-boot sources for the s812. Is this still the case? Looking at codesnake's repo, I see that one of the latest amlogic u-boot commits ( https://github.com/codesnake/uboot-a...7b99fae52d528c ) has some references to meson-m8m2, is it of any help?
Also it seems that the Wetek Core, that is based on the s812, is capable of dualbooting from sdcard, maybe we could borrow their u-boot?

I'd really like to be of some help. I'm quite familiar with coding, cross compiling, linux and so on, but have never had the chance to put together a full image.

I wonder if you could give me some hints (or point me to some docs) to get things going...

Thanks a lot in advance for your help and sorry for wasting your time.

cheers

[Atreus]

H build here.... I didn't notice this pre-G build but my box has been shutting itself down at overnight. I apologize if there is some setting somewhere I can't find.

I will be setting up remote logging to see if there is anything in the kodi.log but just wondering if anyone has experienced this and might have a quick solution. Thanks in-advance!

[gthebest]

About buffering problems here is the solution

http://kodi.wiki/view/HOW-TO:Modify_the_video_cache

https://www.youtube.com/watch?v=ampUWiAwsEg

And now everything is perfect with the Openelec!!!

[red1928]

A friend has this box and wants to put openelec on it, does anyone know if possible? Thanks. http://m.geekbuying.com/ItemDescription/354930

Sent from my A0001 using Tapatalk

[testbit]

All working nicely here since updating to build g and disabling CEC and wifi interface. The box has been on for days now without any lockups or issues. Video playback is good for the most part with the odd file that stutters.

[gthebest]

Hello. I found an issue in OpenELEC in my MXIII-G. I have problems with streaming videos from my pc. The playback stopping all time an buffering. Can you fix it in the next update? Thank you

[wilro_6276]

Howdy All,

Yet another build update "h" - This incorporates updated packages from OE6 mainline, a few more amlogic specific patches (I missed a couple from build "g" - oops!), a few kernel tweaks for smoother playback (3d *should* behave better).

Optimal playback is now achieved by allowing kodi to switch frequencies to match source material (Even my main TV sees improvements from this now

I have now ported my MXQ-S85 to run off my main branch, as it will allow me to better ID differences/regressions between the new kernel/graphics & the old ones which are rock solid on it.

I have included a couple of kerber's binary addons, but will not include them all, as I see major regressions in kodi when they are included in my default build - Missing ones should be installable from the "unofficial" repo's for the wetek.

PS: Also included the security fix that has been recently lamb blasted all over the media recently, despite the fact it's unlikely to affect OE

[madimitris]

in last build of your openelec the default add-ons missing And can't use pvr iptv add-ons

[wilro_6276]

Unfortunately I can't see any of those logs when I filtered dmesg with "dvb". Some said: on an ordinary openelec device (with 3.19 or 4.04 kernel) just enogh to install tvheadend, restart and usb tuners that supported by openelec works by default.
http://wiki.openelec.tv/index.php/Su...ers#USB_Tuners
I hope the 7.0.0 build will use newer kernels on MXIII as well(the RC1 has been out already). As I read on the forums amlogic should create/support newer kernel for their chips.

To see if your tuner is being identified/configured correctly, you can type in "journalctl" after loading the module.

It's unlikely we will see a newer kernel for any of the current amlogic based devices, as these devices are designed to run android, & we are dependant on their closed source drivers to make them functional under OE. (They just backport drivers what are needed from newer kernels to work with the stable 3.10.33 android kernel tree, & rarely upgrade to a newer kernel (We may see a newer kernel for the S905 based devices, however?)

[wilro_6276]

Does anybody have used TWRP for Amlogic Devices? Does it work?
Thank you

I used this one to create backup's of the original android on my device (Thanks abdul_pt) :

http://www.freak-tab.de/abdul_pt/aml/TWRP_MXIII_Plus_S812.img

(Not sure if restore function works - It certainly backs up the rom sufficiently so I could examine all the drivers

[Fed10]

Does anybody have used TWRP for Amlogic Devices? Does it work?
Thank you

[Teddybee]

The necessary drivers/firmware are certainly there, does your log file indicate it has found the usb tuner after loading the module (much like the log shown @ that link you provided?) - I have no experience with dealing with tuner's on these devices, however, it should be no different than doing so with any other amlogic OE powered device.

Unfortunately I can't see any of those logs when I filtered dmesg with "dvb". Some said: on an ordinary openelec device (with 3.19 or 4.04 kernel) just enogh to install tvheadend, restart and usb tuners that supported by openelec works by default.
http://wiki.openelec.tv/index.php/Su...ers#USB_Tuners
I hope the 7.0.0 build will use newer kernels on MXIII as well(the RC1 has been out already). As I read on the forums amlogic should create/support newer kernel for their chips.

[wilro_6276]

P.S.: Maybe I don't need new kernel, just load the proper modules. Unfortunately I couldn't find those to use our MyGica T230.
This is the tuner's description for linux: https://www.linuxtv.org/wiki/index.php/Geniatech_T230
CONFIG_I2C_MUX is also needed to switched on in the kernel or in a module.
Can anybody help me about use that with TvHeadend?
I can't see the Tv Adapter in it. I have loaded the module si21xx, but nothing happened...

The necessary drivers/firmware are certainly there, does your log file indicate it has found the usb tuner after loading the module (much like the log shown @ that link you provided?) - I have no experience with dealing with tuner's on these devices, however, it should be no different than doing so with any other amlogic OE powered device.

[wilro_6276]

I am up to g build, but seem to be plagued with just basic ssh problem,

running fixed ip,
cannected via wireless or wired with manual or dhcp doesnt seem to matter,

ping replies no issue,

ssh no go at all whatever I have tried,

any ideas or suggestions

A couple of things come to mind here - Make sure your ssh client is up to date (OE runs V7.1, which has many older/insecure protocols disabled), make sure that the MX3G has a working DNS & is able to communicate over the internet (connman has Google's DNS hard coded as a fall back for when it cannot communicate with a local/dhcp assigned DNS), use ipv4 address when communicating (I vaguely remember issues with ipv6, esp. over wireless - Although that should have been fixed a while back, as the box has ipv6 enabled at it's core).

At worst, going into the OE settings & toggling ssh off then on will force it to restart (I've seen issues with ssh when it starts up prior to network connectivity being available - It also has issue when a link dropouts, although this mainly affects wireless connections) - Openssh has just been updated to V7.1p2, which will be included in my next build (I've had no issues with the current one, however, when run purely in lan mode