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

[t0mekk]

Thanks for this, but it have a bug. On pvr iptv simple client, the client doesnt show channel categories...i see there is same bug on codesnake release, so probably something wrong in openelec addons..

[vn800art]

Quote:
I'm fairly sure the MXIII+ works, My original port for the MX3G was based off of kerber's S82 OE build, so I suspect it will also work - The good news is that it's a fairly painless process to give it a try using dualboot/sdcard - The only gotcha's could be the wifi/ethernet. I have included most of the amlogic device drivers in this kernel, including the ap6335e driver/firmware.

Cheers,

[/QUOTE]

Hello! Wanted to tell You I used Your build 6.0.1e in it , adding last Kszaq aml.autoscript! One clean Sdcard installation! Great!
Btw, some problems. WiFi not even starting ( it is showed and enabled, but no lan discovered). Ethernet showed, dhcp connected, but I think is very very slow (it is only a FAST one, not Gbit).
Remote doesn't work ( slim one with 8 buttons and the four directional arrows) - works fine in Android.
Only one freeze when entering number of seconds to delay Kodi start (waiting for network). The device has been abandoned from Beelink three months after start ( they started producing mxiii-G) and this is a good way to give it a bit more all round use!
Some test I could perform?
Anyways, fine build !
Thanks for your work, wilro_6276 !

Edit: remote works only for resuming from standby ( red light on device ), not for a fresh start ( I have to push the botton on the box if no light ), neither for shutdown !
Adjusted everything and it works, still NO WIFI ! Will try another build and report.
Edit 2 : and if there is a "/etc/wifi/config.txt" missing or wrong for my chipset ? But I lack the knowledge to even imagine how this should be done !!!!

[ilfrance]

anyone else having problem with 3d switching? for me it crashes and reboot the box

EDIT: actually is not a crash and a reboot, it's the tv that it's losing the signal after kodi tries to switch it to 3d mode, but the only way to restore the signal is to reboot

[red-i]

Hmmm... Something doesn't sound right - It could be simply the powerpack for the device (My supplied one was absolute garbage, luckily a had an old 5V/3A from another failed device lying around, which has worked faultlessly , my other thought would be heat related.

I've just started playing with codesnake's latest kernel release, I'm thinking I may just strip everything back to the bare essentials for my next build - OE 6.0.2 is getting close to release, & the 1st official OE 7.0 test build (6.95.1) is slated for release on the 28th - I'm undecided about the new cec drivers, as they don't work at all on my TV (whereas the existing ones mostly do - My preliminary testing on my next build shows a smoother kodi experience overall, which should also reduce the occasional freezes (most notable using wifi, Gig-E seems rock solid

You know that's a good point about the power supply. I think I'll just order a 5v 3a for kicks. They're only a few bucks.

This build is running really well though. And the gig e is blazing fast

[wilro_6276]

Reset to openelec defaults. Now it's stuck at network setup rebooted again and Stuck at confluence background with no menus. Considering it came with lollipop and I had some freeze-ups in Android kodi, and then I just flashed directly with the toothpick method, is it possible something is up with the box? I got it from Amazon so exchanging would be easy.

Hmmm... Something doesn't sound right - It could be simply the powerpack for the device (My supplied one was absolute garbage, luckily a had an old 5V/3A from another failed device lying around, which has worked faultlessly , my other thought would be heat related.

I've just started playing with codesnake's latest kernel release, I'm thinking I may just strip everything back to the bare essentials for my next build - OE 6.0.2 is getting close to release, & the 1st official OE 7.0 test build (6.95.1) is slated for release on the 28th - I'm undecided about the new cec drivers, as they don't work at all on my TV (whereas the existing ones mostly do - My preliminary testing on my next build shows a smoother kodi experience overall, which should also reduce the occasional freezes (most notable using wifi, Gig-E seems rock solid

[red-i]

Reset to openelec defaults. Now it's stuck at network setup rebooted again and Stuck at confluence background with no menus. Considering it came with lollipop and I had some freeze-ups in Android kodi, and then I just flashed directly with the toothpick method, is it possible something is up with the box? I got it from Amazon so exchanging would be easy.

[red-i]

Hi red-i,

OK, 2 different prob's here:

The freezing can be attributed to 1 of 2 things:

1. If installed on sdcard, try a different/faster sdcard (I had lotsa freeze issues using an older 16G sdcard
2. Addon/skin related - Try using the bog stock kodi skin - It has many patches to it to allow mostly smooth operation, which I doubt third party ones would include.

The "E: Cannot load volume /misc!" problem is a problem with the new LP recovery, Use the 'recovery.img" from one of my non-sdcard install images (As you are running a MXIII+, you could just install my L106 bootloader on your device, as it installs the latest tronsmart bootloader + the older recovery that works with non-LP roms . I do *not* recommend using recovery, except as a last resort (OE has a setting to reset/wipe everything to factory defaults, which is far safer) - Remember, the "recovery" mode on these devices are designed for dealing with Android installations, & should really only be used in order to switch between OpenElec & Android

YMMV: I haven't had a need to use the default recovery.img since installing dual boot stuff

hey thanks for the detailed reply

so firstly, I installed using your toothpick zip, so I didn't install to SD card, i installed over the android firmware.

secondly, I did try reverting back to confluence skin, but still got the same freezing. What I might try then is using OE to reset to factory defaults, and i'll test some reboots without doing any kodi config and see if i'm still getting freezing on boot.

I'll do some tests and report back. appreciate all the hard work dude!

[wilro_6276]

hey guys i'm getting some freezeups on boot, either at the kodi isengard splashscreen or just after as the skin is loading. anyone else? seems to happen randomly (update, pretty often, every other boot or so)

something else I noticed. if i boot to recovery, i have the menus, but a red exclamation mark in the middle, and at the bottom it says "E: Cannot load volume /misc!"

i'm not able to wipe cache partition or wipe data/factory reset. I can't select anything.

Hi red-i,

OK, 2 different prob's here:

The freezing can be attributed to 1 of 2 things:

1. If installed on sdcard, try a different/faster sdcard (I had lotsa freeze issues using an older 16G sdcard
2. Addon/skin related - Try using the bog stock kodi skin - It has many patches to it to allow mostly smooth operation, which I doubt third party ones would include.

The "E: Cannot load volume /misc!" problem is a problem with the new LP recovery, Use the 'recovery.img" from one of my non-sdcard install images (As you are running a MXIII+, you could just install my L106 bootloader on your device, as it installs the latest tronsmart bootloader + the older recovery that works with non-LP roms . I do *not* recommend using recovery, except as a last resort (OE has a setting to reset/wipe everything to factory defaults, which is far safer) - Remember, the "recovery" mode on these devices are designed for dealing with Android installations, & should really only be used in order to switch between OpenElec & Android

YMMV: I haven't had a need to use the default recovery.img since installing dual boot stuff

[loki7777]

Yes.That what you should do.

[red-i]

What box and did you flash it before with different rom? If yes then flash it with stock fw.

it's the tronsmart mxIII+ 2gig. never flashed it before openelec, it came with the stock lollipop firmware from tronsmart. So i assume others can get into recovery and have no errors displayed? perhaps i'll flash it back to android with the tronsmart firmware and then boot to recovery to see if the error goes away? if not, possible that there's an issue with the box itself?

[loki7777]

What box and did you flash it before with different rom? If yes then flash it with stock fw.

[red-i]

hey guys i'm getting some freezeups on boot, either at the kodi isengard splashscreen or just after as the skin is loading. anyone else? seems to happen randomly (update, pretty often, every other boot or so)

something else I noticed. if i boot to recovery, i have the menus, but a red exclamation mark in the middle, and at the bottom it says "E: Cannot load volume /misc!"

i'm not able to wipe cache partition or wipe data/factory reset. I can't select anything.

[vn800art]

Flashaholic, just like me!
@wilro_6276: great news, thank youuuu! Will report back!

[red-i]

been fiddling around with this 6.0.1e build. really nice job! fluid, fast and stable. looking forward to OE7 Thanks wilro, my wife thinks I'm smart just because I flash awesome firmware that others like you have built

[wilro_6276]

Will try and report back the soonest! Thanks for your time and good work-time!
Edit: everything back to normal! Yeahhhh! As with Kszaq builds BT pairing but not connecting, even if devices exchange pairing codes!
More than happy till here!
Thanks for your work, Wilro!

Hello Alessandro,

Yes, BT is next to useless in OE at the moment, however, OE7 at least gives us the ability to pair audio headsets (I tested this a while back, but it was a little too flakey to leave in my builds at the time) Now that BT is basically working in my builds, my next OE7 test build will include it, & I will most probably backport it to OE6.

Do You know if these builds work with the two old (beginning of 2015) S812 Beelink devices S82 Plus (2/16 GB) and/or MXIII Plus (2/8 GB), both of them with KK rom and FAST Ethernet and Ap6335 WiFi chip?
Or, where else I have to look for?
Thanks for your interest!
Btw, I owe a MxIII Plus, but explaining in depth I think is better!
Alessandro

I'm fairly sure the MXIII+ works, My original port for the MX3G was based off of kerber's S82 OE build, so I suspect it will also work - The good news is that it's a fairly painless process to give it a try using dualboot/sdcard - The only gotcha's could be the wifi/ethernet. I have included most of the amlogic device drivers in this kernel, including the ap6335e driver/firmware.

Cheers,