Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Things that I've learned, and wish to share with other M82 (1G/8G) MXIII Owners

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

    Things that I've learned, and wish to share with other M82 (1G/8G) MXIII Owners

    So first off I'd like to thank Abdul_pt for giving us a working TWRP Recovery. Without which I'd probably would still be on a much broken 113k4...

    Ok I gather that its been suggested before that the Firmwares of late have been taking a bit of a "hit" in either poor spelling, or worse yet an actual performance hit.
    Now that I have the ability of making Nandroid Backups, I've manages to get more of a handle on where things seem to stand. With the Stock Firmwares post 109k4*, and they don't look so great.

    1) Let's look at AnTuTu's Video CODEC Benchmark, (Sorry I dodn't bother to count up which Part it was), but where 109k4 would at least attempt to play (IIRC), the WMV2 encoded Clips, 112k4 & 113k4 would just blank these completely out.

    2) Its not very likely going to apply to most People here unless you use Simple IPTV on XBMC/Kodi... is the complete audio lag in 112k4 & 113k4 in the HD Channels. Neither OpenELEC, or 109k4 suffer from this, and can render such Streams with no problems at all.

    3) That eternal problem of lag... (XBMC / Kodi, Showbox etc...), While 109k4 is hardly "Perfect"... The amount of "lag" on 109k4 seems to be a heck of a lot less then on the newer Firmwares. On 112k4 & 113k4 its basically nothing BUT lag. Where as on 109k4 is almost dare I say lag-free? Certainly nowhere even near as much lag as on these AiO Firmwares of late.

    Which makes me wonder if these AiO Firmwares are tweaked for the 2G Units, and just made to work on the 1G Units without such "tweaking". 'cause right now for everything I need my MXIII to do. is being done with 109k4. Heck even PPSSPP is kinda working better, though I guess it could just be the Game ROM, was untouched.

    As to the Ethernet.. Something that I also wanted to test... It seems that even 109k4 is extremely slow Ethernet, as opposed to Wi-Fi...
    I'd just like to point out Once again that Ethernet is 100Mbit/s whereas Wi-Fi is 65Mbit/s So please save your DUH Comments that Wi-Fi is faster Wi-Fi should never be faster then Ethernet. Save possibly 802.11ac or n (in 40Mhz Channels when you can get it, and the AP-6181 will never get it!), and that only applies to 10/100 Ethernet. Once again 65(Wi-Fi) < 100 (Ethernet), and, so should be slower then Ethernet. So why I'm only able to get ~20Mbits, as opposed to the 47~49Mbits I get over the WiFi?
    I'd still like an answer to that One...



    *I know some People have remarked how much of a downgrade 109k4 was to 108k4, but having a Mk² MXIII with the AP-6181 Wi-Fi Chip, and no stock 108k4 to return to I'm kinda stuck with 109k4 as a Base Firmware.

    #2
    Originally posted by Ichijoe View Post
    So first off I'd like to thank Abdul_pt for giving us a working TWRP Recovery. Without which I'd probably would still be on a much broken 113k4...

    Ok I gather that its been suggested before that the Firmwares of late have been taking a bit of a "hit" in either poor spelling, or worse yet an actual performance hit.
    Now that I have the ability of making Nandroid Backups, I've manages to get more of a handle on where things seem to stand. With the Stock Firmwares post 109k4*, and they don't look so great.

    1) Let's look at AnTuTu's Video CODEC Benchmark, (Sorry I dodn't bother to count up which Part it was), but where 109k4 would at least attempt to play (IIRC), the WMV2 encoded Clips, 112k4 & 113k4 would just blank these completely out.

    2) Its not very likely going to apply to most People here unless you use Simple IPTV on XBMC/Kodi... is the complete audio lag in 112k4 & 113k4 in the HD Channels. Neither OpenELEC, or 109k4 suffer from this, and can render such Streams with no problems at all.

    3) That eternal problem of lag... (XBMC / Kodi, Showbox etc...), While 109k4 is hardly "Perfect"... The amount of "lag" on 109k4 seems to be a heck of a lot less then on the newer Firmwares. On 112k4 & 113k4 its basically nothing BUT lag. Where as on 109k4 is almost dare I say lag-free? Certainly nowhere even near as much lag as on these AiO Firmwares of late.

    Which makes me wonder if these AiO Firmwares are tweaked for the 2G Units, and just made to work on the 1G Units without such "tweaking". 'cause right now for everything I need my MXIII to do. is being done with 109k4. Heck even PPSSPP is kinda working better, though I guess it could just be the Game ROM, was untouched.

    As to the Ethernet.. Something that I also wanted to test... It seems that even 109k4 is extremely slow Ethernet, as opposed to Wi-Fi...
    I'd just like to point out Once again that Ethernet is 100Mbit/s whereas Wi-Fi is 65Mbit/s So please save your DUH Comments that Wi-Fi is faster Wi-Fi should never be faster then Ethernet. Save possibly 802.11ac or n (in 40Mhz Channels when you can get it, and the AP-6181 will never get it!), and that only applies to 10/100 Ethernet. Once again 65(Wi-Fi) < 100 (Ethernet), and, so should be slower then Ethernet. So why I'm only able to get ~20Mbits, as opposed to the 47~49Mbits I get over the WiFi?
    I'd still like an answer to that One...



    *I know some People have remarked how much of a downgrade 109k4 was to 108k4, but having a Mk² MXIII with the AP-6181 Wi-Fi Chip, and no stock 108k4 to return to I'm kinda stuck with 109k4 as a Base Firmware.


    Thanks for the tips.

    I just got my MXiii 1GB in the post today. First thing I did was check the Build and I am currently on 113k4.

    You mentioned anohte ruser helped you flash an earlier, more stable firmware and I wondered if you could direct me to the post? I would like to do the same (been using it about an hour, already had to reboot twice).

    Comment


      #3
      Originally posted by Bazmamfoo View Post



      Thanks for the tips.

      I just got my MXiii 1GB in the post today. First thing I did was check the Build and I am currently on 113k4.

      You mentioned anohte ruser helped you flash an earlier, more stable firmware and I wondered if you could direct me to the post? I would like to do the same (been using it about an hour, already had to reboot twice).


      Ok I don't know what you might have done up to this point... Assuming your still Stock. I'd recommend getting a hold of TWRP Recovery Here: (The Link in Post #53!) You just need to rename this from "k200.img" to "recovery.img", and place it on your MicroSD Card. Then enter Recovery Mode. It will then load up the TWRP Recovery from the MicroSD. This will allow you to make a Nandroid Recovery of your Stock ROM. Which is always a good idea if your can do it! You also have the option to replace the Stock 3e Recovery latter on with TWRP if you wish to. If you leave it on the MicroSD though.. It'll be like having your Cake, and eating it too...

      So after preserving your Nandroid Backup you can start to try some other stuff out.

      I pasted a Copy of the Stock 109k4 (*.rar File so use either 7Zip, or WinRAR to extract it.), on my Google Drive. Its the same Version I'm currently running now.

      Another Version you might want to try is OpenELEC... (Currently at v5.0.6) [url=http://amlinux.ru/image[OpenELEC[/url] make sure you ONLY use the Ones labeled as MXIII though. FYI: You shouldn't need to deal with the *.tar Version(s), the difference between the *.zip, and the *-update.zip, is that the *.zip has the same Three File Format of the MicroSD Updates. So you could just copy them onto a MicroSD and, install it though the Recovery. Where as the *-update.zip. Only has the actual OS install, and you have to directly point either 3e, or TWRP to the File in order to install it. The upshot is that the *-update.zip is a tad smaller.

      You may already "get it" that OpenELEC is NOT Android, but in case you hadn't. Then its not. If all you need is a working XBMC / Kodi with none of the extras of Android. This OS could be a good fit. Unlike Android, I was also able to use If only somewhat... my USB Bluetooth Dongle, to beam small Vids, and Pictures taken with my Camera Phone. Not something your gonna be doing under Android, thats for sure! Sadly I had to give up on OpenELEC for now, as I'm otherwise to dumb for it. (i.e. I want to install Retroarch on it... And, all the info 'round this seems to be for the RasPi only!)
      If I knew it was at least possible to pair up my Dualshock3 and use RetroArch under OpenELEC I'd be back on it in a Second! Well this, and if OpenELEC allowed for the AD2P Protocol of the Bluetooth Spec to work, sadly it doesn't... Yet.

      Comment


        #4
        Originally posted by Ichijoe View Post



        Ok I don't know what you might have done up to this point... Assuming your still Stock. I'd recommend getting a hold of TWRP Recovery Here: (The Link in Post #53!) You just need to rename this from "k200.img" to "recovery.img", and place it on your MicroSD Card. Then enter Recovery Mode. It will then load up the TWRP Recovery from the MicroSD. This will allow you to make a Nandroid Recovery of your Stock ROM. Which is always a good idea if your can do it! You also have the option to replace the Stock 3e Recovery latter on with TWRP if you wish to. If you leave it on the MicroSD though.. It'll be like having your Cake, and eating it too...

        So after preserving your Nandroid Backup you can start to try some other stuff out.

        I pasted a Copy of the Stock 109k4 (*.rar File so use either 7Zip, or WinRAR to extract it.), on my Google Drive. Its the same Version I'm currently running now.

        Another Version you might want to try is OpenELEC... (Currently at v5.0.6) [url=http://amlinux.ru/image[OpenELEC[/url] make sure you ONLY use the Ones labeled as MXIII though. FYI: You shouldn't need to deal with the *.tar Version(s), the difference between the *.zip, and the *-update.zip, is that the *.zip has the same Three File Format of the MicroSD Updates. So you could just copy them onto a MicroSD and, install it though the Recovery. Where as the *-update.zip. Only has the actual OS install, and you have to directly point either 3e, or TWRP to the File in order to install it. The upshot is that the *-update.zip is a tad smaller.

        You may already "get it" that OpenELEC is NOT Android, but in case you hadn't. Then its not. If all you need is a working XBMC / Kodi with none of the extras of Android. This OS could be a good fit. Unlike Android, I was also able to use If only somewhat... my USB Bluetooth Dongle, to beam small Vids, and Pictures taken with my Camera Phone. Not something your gonna be doing under Android, thats for sure! Sadly I had to give up on OpenELEC for now, as I'm otherwise to dumb for it. (i.e. I want to install Retroarch on it... And, all the info 'round this seems to be for the RasPi only!)
        If I knew it was at least possible to pair up my Dualshock3 and use RetroArch under OpenELEC I'd be back on it in a Second! Well this, and if OpenELEC allowed for the AD2P Protocol of the Bluetooth Spec to work, sadly it doesn't... Yet.

        Great, thanks for the extensive response.

        OpenElec isn't an option for me, it's the Android apps I want, rarely even use Kodi. I'll report back after I've tested

        Comment


          #5
          Originally posted by Ichijoe View Post

          As to the Ethernet.. Something that I also wanted to test... It seems that even 109k4 is extremely slow Ethernet, as opposed to Wi-Fi...
          I'd just like to point out Once again that Ethernet is 100Mbit/s whereas Wi-Fi is 65Mbit/s So please save your DUH Comments that Wi-Fi is faster Wi-Fi should never be faster then Ethernet. Save possibly 802.11ac or n (in 40Mhz Channels when you can get it, and the AP-6181 will never get it!), and that only applies to 10/100 Ethernet. Once again 65(Wi-Fi) &lt; 100 (Ethernet), and, so should be slower then Ethernet. So why I'm only able to get ~20Mbits, as opposed to the 47~49Mbits I get over the WiFi?
          I'd still like an answer to that One...
          http://freaktab.com/forum/tv-player-...844#post296844
          Issue 14, but firmware developers just ignored it:
          https://docs.google.com/spreadsheets...kPR00eHVzH4UU/

          Comment


            #6
            Issue 14 IS REAL, and the fixes detailed in the Thread [Here:] can fix this. I've opted to use Android Tuner Free, since unlike the Bionic TCP Buffer Tweak, it doesn't need to be manually reset each time.

            This has been a very LONG STANDING PROBLEM! Reportedly dating all the way back to 104k4 I think the first MXIII's started showing up 'round what 107k4?
            And its an otherwise (For Beelink's Oman) to fix since he has the ability and, moreover the (Linux Permission), rights to get this done!

            If some People think this Fix (or more to the point...) Compliant is invalid, then they must not be trying to stream high-bandwidth Materials. Ex: NFL Football (USTVNow), or any of a host of Sources with 720p/1080p with either DD-5.1 or DTS5.1 because with the former I was a bit skeptical at first (While the last NFL Season was still going on.), Having actually tested the Exact same Episode of House that had the DTS Track (XBMC Plugin "Genesis"), It would splutter and, stall in a never-ending Buffer ~2% @ 15 Minutes!. After this "Fix".... The Stream just worked!! Not even the slightest suggestion of lag.

            I'm of the understanding that this has in fact been fixed in a custom ROM by the name of Finnless. The problem is that, that ROM was only built, and tested to run on 2G Boxes. I've seen a few posts here suggesting that it could work on a 1G Box. Sadly I just don't know if these are Troll Posts or not. Officially we shouldn't use 'em as the Brick potential is high. That said... I'm kinda toying with the idea of trying it. Since I'm fairly sure I can safely recover in the event of a softbrick. (e.g. As long as I can connect the MXIII up to the PC and. "discover" the WorldCup Driver... I'm not so Permabricked as to not being able to recover. Which has happened to me before when I mistook an S82 Firmware for an M82 One.

            But, as Bugs go... This Ones disgraceful! And, the fact that it still hasn't been fixed yet, even though beelink must obviously know about it by now... (See the Google Doc Spreadsheet!), is telling that its no longer in their interest to support this Box, any longer.

            Comment

            Working...
            X