Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • red-i
    replied
    Originally posted by stannoplan View Post
    there is a version in wilro's test build folder, it seems to work ok with the only real issue for me is it fails to boot occasionally. OE7 and Kodi16. http://5.189.137.29/Openelec/MX3G/test_builds/
    the community build i am using has moved to 16 so i am using this every day.
    tried flashing to this, as downgrading from 6.0.3 to 6.0.1 via the update method just resulted in freezing on the openelec splash screen.

    issue is, i was running the amber skin, so after flashing to oe7 test build, it would boot to the menus and then trigger a reboot (endlesssly). I wish flashing via the toothpick method would just completely wipe everything, is there a way?

    i'm going to try to flash 6.0.1e via the toothpick method next. i really hope i haven't bunked up my box :O

    Update: back to 6.0.1e. Can confirm that 6.0.3a does not use remote conf from system/.config. Wilro is this something you can possibly address? Unsure if it's also the case with the 7.0 test build as my amber skin mucked things up.
    Last edited by red-i; 09 March 2016, 05:27.

    Leave a comment:


  • red-i
    replied
    So I updated to 6.0.3a via the tar update method. Now my Harmony remote won't work. The tronsmart remote works. I still have my remote.conf file in the config files folder. That's where I had it sitting before the update and it worked. Any ideas? Its as if openelec isn't using the file anymore.

    Leave a comment:


  • stannoplan
    replied
    there is a version in wilro's test build folder, it seems to work ok with the only real issue for me is it fails to boot occasionally. OE7 and Kodi16. http://5.189.137.29/Openelec/MX3G/test_builds/
    the community build i am using has moved to 16 so i am using this every day.

    Leave a comment:


  • red-i
    replied
    Originally posted by Bigredfan View Post
    Wilro when should we expect the first stable build that is running kodi 16

    You rock keep up the good work
    no openelec release yet for 7.0. i think 6.0.3 was just released a few days ago.

    Leave a comment:


  • Bigredfan
    replied
    Wilro when should we expect the first stable build that is running kodi 16

    You rock keep up the good work

    Leave a comment:


  • vn800art
    replied
    You are welcome, cvo123 , I would like to know more too, particularly about remote.config and a browser of any sort!
    Happy I have been helpful!
    Alessandro

    Leave a comment:


  • cvo123
    replied
    Originally posted by vn800art View Post
    I must then ask people and You Wilro to excuse me, but me and cvo123 will stop I think briefly to be OT on here, but, as I told im my msg, newer sd installation procedure is so simple that one barely understand something is happening and is cross device ( my experience ) and build compliant ( Kszaq words) starting from release 6.0.0.0 ( if I remember well ). So, I will copy and paste Kszaq word for sdcard installation and add my experience with aml.autoscript : QUOTE
    1. I'm testing a new method of updating uenv variables that won't need flashing, one time toothpick and you'll be good to go. To try it, download this file and unpack it to SD card. You should have three files: kernel.img, SYSTEM and aml_autoscript. Delete any other files if they are present. With card made that way inserted, use a toothpick ou have to have only two files method to power on the box. It should boot straight to OpenELEC. Toothpick is only needed for a first boot.
    @Everyone I read your posts and work hard to fix bugs that you report, I don't reply to every single one to not make this post a few pages long.



    Yes, it worked!
    I add the new aml_autoscript file to 6.0.1.3 files and boot with toothpick method and instantly I am booting in OpenElec
    Wifi works flawless with my RTL8723BS also!
    Thanks kszaq for your hard work and four your patience with newbies like me.
    UNQUOTE
    To arrive to this point you know you have to use Wilro build nr. 6.0.1.A ( see my test ) with the end of the file description named img.gz . You have to use some tool to extract the image from that zip ( I use winrar ) then you have to write the extracted image on a fresh formatted microsd hc or better, but class 10 to assure speed. To do this you use win32disk imager. After this tool has done its work ( be carefull, check your correct drive to write to ( your sdcard inserted in the PC ), you check if in there there are 5 files ( as in the old risky business procedure!!!! ), you have to take off everything ( recovery, factory update param, OE Bootloader if any [or dualboot bootloader]), leaving only Kernel and Sistem files. To this card that you have burnt you will extract the aml.autoscript , so in the end you have three files ( in the test build 7 freshly published from Wilro, in the img.gz file once extracted and burnt on a sdcard, You will find three files as I said, You can take aml.autoscript from there and put it in the release 6.0.1A, once you have burned it to the card, taking out the other files I mentioned ) . Disconnect device from mains, take the card, insert in the little slot on device, take a cotton fioc ( for girl's use ) cut one end taking off the part covered with cotton, keep button inside AV port pressed, insert mains, press the button to switch on, continue to keep cotton fioc pressed inside till you see the great red circle with the B ( eelink ! @"$%& ), release the cotton fioc. You must wait the magic happen now !
    Let us know
    Thanks for your patience, my friends and Wilro !
    Alessandro
    I streamed a few video addons last night and they worked great. As you already mentioned on your test (6.0.1a), both ethernet/wifi is working fine except there's no bluetooth. I tried to copy the remote.conf file (from android OS) onto the ../storage/configfiles/, but still could not be able to use the remote. I don't know much of this stuff so I guess there could be more to it. USB keyboard works perfectly fine in this case. Thanks Alessandro for all the detail instructions for the newbie like me to be able to do it. Of course many thanks to Wilro and whoever to contribute to this fantastic work here.
    By the way, can I install any internet browser in OE? Thanks

    Leave a comment:


  • wilro_6276
    replied
    Originally posted by slippery49 View Post
    toothpick install on 6.0.3a link no go

    had to use


    thanks for the great work
    Oops! Thanks - Files moved to correct folder

    Leave a comment:


  • slippery49
    replied
    toothpick install on 6.0.3a link no go

    had to use


    thanks for the great work

    Leave a comment:


  • wilro_6276
    replied
    Howdy All,

    I have uploaded build "6.0.3a" (1st post), & a new test build HERE

    These are based off codesnake's Febuary kernel release, with various patches required to allow our little box to behave - Openelec 7.0 is approaching feature freeze, so we will hopefully start seeing 6.95.x releases shortly. This development release is already better in a lot of ways on this box than OE6 - Kodi 16 in particular appears a lot smoother overall (sadly, I'm sure we're going to see more addon breakages initially, various regressions due to it's freshness, but for myself, the smoother/consistant behaviour trumps that

    Enjoy!

    Leave a comment:


  • t0mekk
    replied
    [QUOTE=wilro_6276;n558431]
    I have had a look at the sample you sent me, & unfortunately it does appear to be a problem upstream (Either in OE or kodi, I'm not sure - doesn't worked on any of my OE 6/7 based boxes)


    Thanks, the problem is sure in OE, cus ive tried almost all firmwares. In firmwares which pvr addon is not from OE the categories are working...but other problem is that i have a stutterin problem on live tv channels...anyway, slowly and this will be perfect thanks

    Leave a comment:


  • vn800art
    replied
    Well wilro_6276 , thanks for your time ! I will try to test more ( starting without ethernet connected ? disconnect ethernet while connected ? ) and report back. I have red something about correct remote behaviour in setting device ON depend on bootloader ( which in my case is correct BUT the light remains blue ! even if shutoff ) the important part is all the three main connections working ! Will try to fix remote config, too !
    Regards
    Alessandro

    Leave a comment:


  • vn800art
    replied
    I must then ask people and You Wilro to excuse me, but me and cvo123 will stop I think briefly to be OT on here, but, as I told im my msg, newer sd installation procedure is so simple that one barely understand something is happening and is cross device ( my experience ) and build compliant ( Kszaq words) starting from release 6.0.0.0 ( if I remember well ). So, I will copy and paste Kszaq word for sdcard installation and add my experience with aml.autoscript : QUOTE
    1. I'm testing a new method of updating uenv variables that won't need flashing, one time toothpick and you'll be good to go. To try it, download this file and unpack it to SD card. You should have three files: kernel.img, SYSTEM and aml_autoscript. Delete any other files if they are present. With card made that way inserted, use a toothpick ou have to have only two files method to power on the box. It should boot straight to OpenELEC. Toothpick is only needed for a first boot.
    @Everyone I read your posts and work hard to fix bugs that you report, I don't reply to every single one to not make this post a few pages long.



    Yes, it worked!
    I add the new aml_autoscript file to 6.0.1.3 files and boot with toothpick method and instantly I am booting in OpenElec
    Wifi works flawless with my RTL8723BS also!
    Thanks kszaq for your hard work and four your patience with newbies like me.
    UNQUOTE
    To arrive to this point you know you have to use Wilro build nr. 6.0.1.A ( see my test ) with the end of the file description named img.gz . You have to use some tool to extract the image from that zip ( I use winrar ) then you have to write the extracted image on a fresh formatted microsd hc or better, but class 10 to assure speed. To do this you use win32disk imager. After this tool has done its work ( be carefull, check your correct drive to write to ( your sdcard inserted in the PC ), you check if in there there are 5 files ( as in the old risky business procedure!!!! ), you have to take off everything ( recovery, factory update param, OE Bootloader if any [or dualboot bootloader]), leaving only Kernel and Sistem files. To this card that you have burnt you will extract the aml.autoscript , so in the end you have three files ( in the test build 7 freshly published from Wilro, in the img.gz file once extracted and burnt on a sdcard, You will find three files as I said, You can take aml.autoscript from there and put it in the release 6.0.1A, once you have burned it to the card, taking out the other files I mentioned ) . Disconnect device from mains, take the card, insert in the little slot on device, take a cotton fioc ( for girl's use ) cut one end taking off the part covered with cotton, keep button inside AV port pressed, insert mains, press the button to switch on, continue to keep cotton fioc pressed inside till you see the great red circle with the B ( eelink ! @"$%& ), release the cotton fioc. You must wait the magic happen now !
    Let us know
    Thanks for your patience, my friends and Wilro !
    Alessandro
    Last edited by vn800art; 03 March 2016, 08:00.

    Leave a comment:


  • wilro_6276
    replied
    Originally posted by vn800art View Post
    First report: MXIII Plus ( old Beelink model ) => SUCCESS ( for the large part ): 6.0.1A ! All networks working, blazing fast! BT turns on but doesn't find anything. Remote works only for resume from stand by - light on the device remains BLUE even if OE has shut down ( no Red light doh ! ). I charge a large wizard and system is snappier than my NVIDIA SATV ! As I had used aml.script for the previous test, recovery refused to work this time ( no usb working, mose and Logitech k400 dead ! ), so I unplugged and replugged AC, OE started after the second boot ( just like the first time with release 6.0.1e and toothpick method working ! ).
    Coming back soon !
    Edit 1 : 6.0.1D: no WiFi, no BT working as before, remote works only as before, light becomes RED if in suspend !
    More to come
    Edit 2: 7 devel from 1/3 ( today !) only Ethernet working ( well, must say ), no Wifi, Bluetooth works and hold connection, but I haven't find a way to make it play from TV loudspeakers or send smtg outside ! Stock remote work as before, RED light comes out when shut off.
    Edit 2/a : I have seen You put aml.autoscript in the file, but OE booted without toothpick method!
    Thanks again for Your work, Wilro !
    If You want me to check something I can test in the mornings ( Central European time, btw ) , much easyer than in the afternoons !
    Alessandro
    Thanks for the breakdown between versions! It kinda raised more questions for me than answer's, unfortunately - I can't see why wifi only works on 6.0.1a (wifi hasn't really changed since 6.0.1a & the new kernel
    What's really curious is BT working but NOT wifi in the test build (same chip controls both functions, & my wifi is far more stable in the test build!) - Bluetooth+OE in general is quite limited on these devices, as originally, the only way to get it to work was to lose all audio pass-thru capabilities - Having the ability to at least output audio to a headset now is a nice improvement on this situation
    The led issue is also really strange, although it did take a fair bit of effort to get consistant behaviour for the MXIII-G with the newer kernel's. (My all black MXQ's refuse to turn the led red, but then, the original android firmware didn't either, so I'm not that fussed

    I will have a bit more of a poke around to see if I can find out which wifi options could possibly stop it from working in the newer builds...

    Leave a comment:


  • wilro_6276
    replied
    Originally posted by t0mekk View Post
    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..
    I have had a look at the sample you sent me, & unfortunately it does appear to be a problem upstream (Either in OE or kodi, I'm not sure - doesn't worked on any of my OE 6/7 based boxes)

    Originally posted by t0mekk View Post
    Hello, i tried this lateet and kszaq, in kszaq hdmi cec working..on this one not..anybody with same problem?
    The latest test build *doesn't* include any of kszaq's patches at the moment, as I am trying to isolate a number of stability/temperature problems with this kernel - I will start re-introducing them once I find the culprit.
    It seems that the OE team have skipped over 6.0.2 (now at 6.0.3!), & there is mention of cec with LG TV's (My samsung TV works fine) - I will be putting up another test build shortly.

    Still testing OE6.0.3, as I'm not happy with the wifi stability in this build - Wifi appears a lot more stable in the test builds, so I'm going to try kodi 15 on top of it to see if the problem is related to kodi 15 or my OE6 build environment.

    FWIW: My MXQ & mk808b+ devices are back to running kszaq's 5.95.5.2 build, as the newer builds appear less stable in my environment

    Leave a comment:

Working...
X