I am back in the game, just copied the files, insert sd, and powerup and i am back... so lucky eheeh
Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
[ROM] OpenELEC for Amlogic-based TV boxes (M8, MXQ, TV110, MX2/G18)
Collapse
This is a sticky topic.
X
X
-
Has anyone tried H265 (HEVC) on this (v6.0.3)?
Got some material, from internet, in 1080p that cannot be played correctly and just tried my own 1080p (16Mbps) and UHD material (46Mbps), both using H265 from Premiere Pro CC2015, with more or less the same results: sound is fine, video with big issues (as if it can only decode parts of the stream).
I'm editing my home videos in UHD and, in complement to a 1080p version, I would like to leave a UHD output version already made for future use. Right now, I would like to test it to see if it serves.
My projector only does 1080p but I expect OE to decode UHD (and 4K) and play it through without a problem.
Same problem occurs with a Tronsmart MXIII+ box with Jarvis (v16.1).120" screen, EPSON 6100W, YAMAHA RX-V775, B&W 603 (front), B&W CC3 (center), B&W DS3 (surround), Boston Acoustics SoundWare XS (front heights), SVS SB-2000 (subwoofer)
M8 TV Box Codesnake's OpenElec 6.0.3
Tronsmart MXIII+ (v108L1) + KODI 16.1 (Jarvis)
Comment
-
Hello! Hope somebody can help me out here!
I've got MX2 boxes. Finally decided to switch back to Linux and found this thread.
I started with CodeSnake's 4.2.1 build in the form of OpenELEC-G18REF_MX2-4-2-1. Worked great! So after a little testing I decided to up to a newer version. Let's face it, there hasn't been anything called XMBC in quite a while now. Need Kodi to support newer addons, etc
I found Nemsis' OpenELEC-Amlogic.MX2.arm-Nemsis72.tar and upgraded with it. It completely froze after a couple of minutes after Kodi launched. I bounced it a few times and every time it would end up freezing. Always in less than 5 minutes. Sometimes within just a few seconds of Kodi launching. So I thought maybe I should stick with CodeSnake's build.
I found CodeSnake's 6.0.3 build as OpenELEC-Amlogic.MX2.arm-6.0.3. First I tried "updating" from my Nemsis build. Once again, frozen every... single... time. So I wiped the cache and the entire box manually and reflashed using the files from the 6.0.3 zip and toothpicking. I was shocked to find the same exact thing. Freezes up every time.
To be clear here, the only changes I've made each time is to set the Time Zone, gone to 1080p, connected to my network (wirelessly), and sometimes installed/configured the Yahoo! Weather addon. In essence, this is as clean as it gets.
Anybody have any ideas here?
Thanks in advance!
ADDITIONAL: I've got 4 MX2 boxes. 2 test, 2 in-use. I've had the same exact result on both of my test boxes.
ADDITIONAL ADDITIONAL: I just wiped one of the boxes fresh again with 6.0.3. This time it froze immediately after connecting to WiFi. In other words, I didn't even get a chance to set my resolution, let alone make any other changes.
Thanks!
So here's yet another update... It turns out it really IS simply connecting to the network that's causing it to crash! I disabled the wireless and just let it sit there for half an hour or so. No issues at all. Menu responsive, etc. So I switched on the wireless. Within about 1 SECOND of it connecting to the network, it froze. What the heck's going on here?
Thanks!
Last edited by Friffy1; 17 July 2016, 00:44.
Comment
-
Originally posted by startreksuite View PostI currently have 5.95.5 installed on my gbox mx2. Can I put Nemesis's build for Jarvis on my box? I am hard wired, so the wifi issue won't affect me. Or do I have to go through the steps of starting from the first version of the matricom firmware on upwards? Thanks in advance.
Comment
-
Originally posted by Friffy1 View PostHello! Hope somebody can help me out here!
I've got MX2 boxes. Finally decided to switch back to Linux and found this thread.
I started with CodeSnake's 4.2.1 build in the form of OpenELEC-G18REF_MX2-4-2-1. Worked great! So after a little testing I decided to up to a newer version. Let's face it, there hasn't been anything called XMBC in quite a while now. Need Kodi to support newer addons, etc
I found Nemsis' OpenELEC-Amlogic.MX2.arm-Nemsis72.tar and upgraded with it. It completely froze after a couple of minutes after Kodi launched. I bounced it a few times and every time it would end up freezing. Always in less than 5 minutes. Sometimes within just a few seconds of Kodi launching. So I thought maybe I should stick with CodeSnake's build.
I found CodeSnake's 6.0.3 build as OpenELEC-Amlogic.MX2.arm-6.0.3. First I tried "updating" from my Nemsis build. Once again, frozen every... single... time. So I wiped the cache and the entire box manually and reflashed using the files from the 6.0.3 zip and toothpicking. I was shocked to find the same exact thing. Freezes up every time.
To be clear here, the only changes I've made each time is to set the Time Zone, gone to 1080p, connected to my network (wirelessly), and sometimes installed/configured the Yahoo! Weather addon. In essence, this is as clean as it gets.
Anybody have any ideas here?
Thanks in advance!
ADDITIONAL: I've got 4 MX2 boxes. 2 test, 2 in-use. I've had the same exact result on both of my test boxes.
ADDITIONAL ADDITIONAL: I just wiped one of the boxes fresh again with 6.0.3. This time it froze immediately after connecting to WiFi. In other words, I didn't even get a chance to set my resolution, let alone make any other changes.
Thanks!
So here's yet another update... It turns out it really IS simply connecting to the network that's causing it to crash! I disabled the wireless and just let it sit there for half an hour or so. No issues at all. Menu responsive, etc. So I switched on the wireless. Within about 1 SECOND of it connecting to the network, it froze. What the heck's going on here?
Thanks!
You should have done a clean install from openelec 4.2.1 to openelec 7.0...not upgrade from tar file.. different system sizes openelec system img is larger now than older versions... hence the fu#$k up... you can try to revert back to android then reflash openelec again.
Comment
-
Originally posted by Nemsis72 View Post
You should have done a clean install from openelec 4.2.1 to openelec 7.0...not upgrade from tar file.. different system sizes openelec system img is larger now than older versions... hence the fu#$k up... you can try to revert back to android then reflash openelec again.
Thanks for the reply! If not upgrading from a tar file, how do I do the clean install to OE 7.0? I've only seen your tar file for it. I haven't seen a zip to toothpick with.
And, are you saying I now need to go back to Android, then go to OE 4.2.1, then OE 7.0?
Thanks!
Comment
-
Originally posted by Friffy1 View Post
Thanks for the reply! If not upgrading from a tar file, how do I do the clean install to OE 7.0? I've only seen your tar file for it. I haven't seen a zip to toothpick with.
And, are you saying I now need to go back to Android, then go to OE 4.2.1, then OE 7.0?
Thanks!
Here it is: https://mega.nz/#!8cgXjRhI!mu8wGyY14...ujItOf8HdrXS2E
Extract all 3 files to a fat32 formatted sd card not usb...
But before you do atemp to clean flash my zip u are going to have to flash this ember zip.. here: https://mega.nz/#!hN5mWShZ!Qnp3RB-Ub...3kgwYBxqjJEzo0
To format your nand to proper sized filesystem after making a mess with ur tar update fiasco.
After a clean boot from ember, turn off then flash my zip file.
And if you want to revert back to stock android you are going to have to flash this zip. https://mega.nz/#!QUhiEQiS!wY-E2uWBk...KOkIkvNHLhBwBc
In order to reformat those same partitions for its included android zip.... Goodluck!!!Last edited by Nemsis72; 17 July 2016, 22:54.
Comment
-
Originally posted by Nemsis72 View Postno u dont have to go to 4.2.1 just clean flash OE 7.0 after flashing ember zip.
Here it is: https://mega.nz/#!8cgXjRhI!mu8wGyY14...ujItOf8HdrXS2E
Extract all 3 files to a fat32 formatted sd card not usb...
But before you do atemp to clean flash my zip u are going to have to flash this ember zip.. here: https://mega.nz/#!hN5mWShZ!Qnp3RB-Ub...3kgwYBxqjJEzo0
To format your nand to proper sized filesystem after making a mess with ur tar update fiasco.
After a clean boot from ember, turn off then flash my zip file.
And if you want to revert back to stock android you are going to have to flash this zip. https://mega.nz/#!QUhiEQiS!wY-E2uWBk...KOkIkvNHLhBwBc
In order to reformat those same partitions for its included android zip.... Goodluck!!!
Appreciate your assistance! Here are my results...
Ember: Everything worked great. Wireless, 1080p playback, everything.
Your ROM: Still experiencing the same issue as I've been experiencing. Flashed fine, as always, everything worked up until the point where I connected to my network. Then Kodi completely froze.
Any ideas?
Comment
-
Originally posted by Friffy1 View Post
Appreciate your assistance! Here are my results...
Ember: Everything worked great. Wireless, 1080p playback, everything.
Your ROM: Still experiencing the same issue as I've been experiencing. Flashed fine, as always, everything worked up until the point where I connected to my network. Then Kodi completely froze.
Any ideas?You may only view thumbnails in this gallery. This gallery has 2 photos.2 Photos
Comment
What's Going On
Collapse
There are currently 1719 users online. 0 members and 1719 guests.
Most users ever online was 63,956 at 18:56 on 20 March 2025.
Comment