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

    Originally posted by nighthawk1975 View Post

    Uhm, thanx i will check that option.
    Thx wilro cec is working. Where can i find a good recovery for our mxiii-g box?

    Comment


      @stannoplan: Thank you so much. Went back to Lollipop then reflashed straight to OE. I'm not sure exactly what this reset for me but it's working again.

      @wilro: the latest build 6.0.1a is rock solid for me. I've just tried it with advancedsettings.xml pointing to my NAS and everything works. Previously I only needed to go to Settings and scroll through the options for the box to lock up, now it just works. There's a beer heading your way.

      Comment


        Originally posted by wilro_6276 View Post
        Good to here! (There was a heap of tweaks in video playback in kodi + the kernel in this new build) - There are still major issues with mpeg2+pcm audio (combined) - It irks me that my S805 based devices play them flawlessly.
        Wonder if the mpeg2 issues are why playback from my Hdhomerun is sometimes so laggy

        Comment


          Originally posted by gthebest View Post
          Can we have as basic the Openelec in the device storage and put in SD card the adnroid for dual boot? Now I have installed the Openelec 6.0.0 in the device storage

          Anyway I uninstall Openelec from device(internal) storage and I install again Android Lollipop 107L1 (to my MXIII-G) I follow the instructions from the #2 post and I boot into Openelec from my SD card! My question is : Every time I want to boot in Android I must get out my sd card? Can I do it with easier way? (e.g. When I power on my device there would be an option to select which one of the 2 (android or openelec) want to start.
          Hi gthebest,

          An android rom would need some fairly extensive customisation in order to function running from an sdcard, & even then, I have my doubts about how stable it would be with such hacks.

          kszaq's original dual booting had an option to allow booting to nand from OE, but was dropped with this new method of dual booting (that we also use) - If a non-obtrusive method is developed to do this without removing the sd card, I will certainly incorporate support for it - The only functional menu driven dual boot I've seen/used was on my old Galaxy S2 (which worked flawlessly), although I believe the phone's bootloader provided such support, which is why I haven't seen such functionality since

          Comment


            Originally posted by nighthawk1975 View Post

            Thx wilro cec is working. Where can i find a good recovery for our mxiii-g box?
            Great - I don't have an LG TV either, & my initial testing of these patches caused sporadic prob's with my samsung TV (another reason why I included the addon to enable/disable it - On one of my elcheapo TV's (uses a really weird cec implementation), I have to have this disabled by default, or else the MX3G locks up within minutes of booting (which is why I default to cec being disabled by default
            The best recovery is the one included in the install zip (it's the kitkat one, as the LP recovery won't install OE correctly on these devices) - I also posted link to a link a few pages back to a twrp recovery which mostly works on these devices.

            Comment


              Originally posted by wilro_6276 View Post
              Hi gthebest,

              An android rom would need some fairly extensive customisation in order to function running from an sdcard, & even then, I have my doubts about how stable it would be with such hacks.

              kszaq's original dual booting had an option to allow booting to nand from OE, but was dropped with this new method of dual booting (that we also use) - If a non-obtrusive method is developed to do this without removing the sd card, I will certainly incorporate support for it - The only functional menu driven dual boot I've seen/used was on my old Galaxy S2 (which worked flawlessly), although I believe the phone's bootloader provided such support, which is why I haven't seen such functionality since
              Thank you for your answer. About the way to boot between Android-Openelec and the opposite?
              Every time I want to boot in Android I must get out my sd card? It's not practical to eject the sd card so we can boot in android. Can I do it with easier way? (e.g. When I power on my device there would be an option to select which one of the 2 (android or openelec) want to start.) Somewhere I see an application through android which called "Boot 2 Openelec" . Also I've seen somewhere when in openelec you select power button there is an option to boot into windows.

              Comment


                I tried the 6.01 build (toothpick install) unfortunately without success. The first time it froze on the Kodi 15.2 screen. The second time it froze on the initial screen of the skin (Backrow). After several reboots I could get to the main menu and it froze again and was unresponsive. I have returned to build 'h' and it works without problem. I am happy to help diagnose if others are also having problems with the latest build. Many thanks for all your great work which I really appreciate.

                Comment


                  Originally posted by Bigredfan View Post

                  Wonder if the mpeg2 issues are why playback from my Hdhomerun is sometimes so laggy
                  Hi Bigredfan,

                  Well, this could be related (the file I mentioned above having prob's was actually recorded from FTA - One of the big prob's with this new build/kernel is the entire media device tree has breakages all over the place, which are very hard for me to diagnose, as I don't have anything to test with ;( - There was a massive effort to backport the linux 3.16 device tree late last year, which I've been dabbling with for the last week or so to see if it breaks anything - I'm hoping to incorporate the new device tree into my next build (haven't noticed any prob's yet - but then, as I said, I don't actually use any DVB devices

                  OK, found the problem with the above file - Now the only files I have not playing correctly on the the MX3G (S812) are same ones that don't play correctly on my MXQ (S805) (yipee - Sanity saved

                  Comment


                    Originally posted by gthebest View Post

                    Thank you for your answer. About the way to boot between Android-Openelec and the opposite?
                    Every time I want to boot in Android I must get out my sd card? It's not practical to eject the sd card so we can boot in android. Can I do it with easier way? (e.g. When I power on my device there would be an option to select which one of the 2 (android or openelec) want to start.) Somewhere I see an application through android which called "Boot 2 Openelec" . Also I've seen somewhere when in openelec you select power button there is an option to boot into windows.
                    Sorry, wasn't clearer with my last post - The sd boot function works by detecting the existance of the sd card during device startup - If nothing's plugged in, it reverts to booting the internal system. As this is a very new hack, removing the sdcard is the only way to switch between them. Someone may be able to refine this hack to allow dual booting without removing the sdcard in the future, but at the moment, it is what it is - I'm happy to have *any* sort of dual booting on this device, as it was never a feature that the device maker provided or ever intended to provide...

                    Originally posted by Ozman
                    I tried the 6.01 build (toothpick install) unfortunately without success. The first time it froze on the Kodi 15.2 screen. The second time it froze on the initial screen of the skin (Backrow). After several reboots I could get to the main menu and it froze again and was unresponsive. I have returned to build 'h' and it works without problem. I am happy to help diagnose if others are also having problems with the latest build. Many thanks for all your great work which I really appreciate.
                    This looks like a kodi issue (there was a massive number of kodi patches introduced just prior to 6.0.1's release) - Now that we have the dual boot capability, it may to worth trying the new system without any plugins/addons/skins, to help identify what's causing the problems (It may also be worth swapping the bootloaders, as some things appear to work better with the Kitkat bootloader - All builds > "e" are compatible with both




                    Comment


                      Has anyone here had any success using Retroarch or any other emulation solution with this OE build?

                      Sent from my SM-G920V using Tapatalk

                      Comment


                        Howdy All,

                        Just some thoughts about the 6.0.1a build...

                        In my travels isolating the power led issue, It appears that I've got different problems depending on which bootloader I use:

                        1. Kitkat: suspend/resume works, power led stays blue on power off
                        2. LP : suspend/resume doesn't work, power led turns red on power off. (not working in 6.0.1a - will work in next build

                        Overall, I believe the LP bootloader is the most stable...

                        Scheduler: ondemand vs interactive.

                        The new default interactive scheduler appears to keep the temperature lower, but I get the feeling that the original ondemand scheduler is smoother over all - If anyone would like to try this & weigh in, the scheduler can be changed by adding the following to their "autostart.sh" in the ".config" folder:

                        "echo ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor"

                        (I'm undecided as to which one should be "default" at this stage)

                        My next build will include a massive overhaul of the media device tree (largest set of changes to the linux kernel I've made yet!) - I'm hoping it will improve usb tuner devices, as well as improve general playback.
                        I'm still not happy with the OE 7.0 devel branch, but as kodi 16 has hit "rc" stage, I will either get this sorted or backport it to my current stable branch (I'm a little bit more inclined to work on this now, the sd dual boot is invaluable in this case

                        Comment


                          Originally posted by wilro_6276 View Post
                          Howdy All,


                          Scheduler: ondemand vs interactive.

                          The new default interactive scheduler appears to keep the temperature lower, but I get the feeling that the original ondemand scheduler is smoother over all - If anyone would like to try this & weigh in, the scheduler can be changed by adding the following to their "autostart.sh" in the ".config" folder:

                          "echo ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor"

                          (I'm undecided as to which one should be "default" at this stage)



                          HI, I'd like to test on demand governor but I don't know Linux. Could show me step by step how I can modify autostart.sh? I've already a ssh client but I don't know commands

                          Comment


                            Originally posted by uomoint View Post

                            HI, I'd like to test on demand governor but I don't know Linux. Could show me step by step how I can modify autostart.sh? I've already a ssh client but I don't know commands
                            Ok, from the ssh command prompt:

                            nano .config/autostart.sh
                            paste this in:
                            ---snip---
                            #!/bin/sh

                            echo ondemand >/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

                            ---snip---
                            <ctrl-x> save & exit
                            reboot

                            After rebooting, you can check that it has taken effect by typing:

                            cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

                            Thanks!

                            Comment


                              Howdy All,

                              Just a quick update - I believe I've nailed the mpeg2 playback issue (most likely affected TV tuner stuff as well) - Real pita to isolate the exact issue, but it seems that the problem was very specific to mpeg2 streams (in particular 720x576, 704x576 worked fine??)

                              Sadly, I'm still having major stability issues with runnerway's media tree backport to improve dvb devices (It improves most tuner usb devices, but has horrible side effects with everything else - It's gonna take me a bit more work to get this stable enough for release (I'll have a look at how kszac's going with this, as he's heading down the same path with the MXQ's

                              Still having prob's with the OE 7 build, from what I've read, this is a prob. with the new compiler & the amlogic 3.10.x kernel - I'll have a bash at building it using the older stable compiler from OE6, just to get something out there...

                              Cheers!

                              Comment


                                Hi Wilro, I was wondering if you have a public git repository where you push all the modifications to. If so, do you mind sharing it?

                                Anyway, thanks for keeping us updated!

                                Comment

                                Working...
                                X