Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Stock Firmware - Beelink S82/M8 - MXIII 1/2G - Official FW Releases from Beelink - user feedback thread

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



    firmwarew 113k4 mxiii

    Comment


      Does your 113k4 have the misspelt "Dobly", for Dolby in the Advanced Settings?
      As a side note could you try installing the AnTuTu Video Benchmark and report back on how... i.e. if the WMV2 & RMVB Formats even playback on your Firmware...

      On my 1G MXIII these Formats only render.... More so then actually play on Firmwares >110k4. And only as Black Screens on anything <110k4. i.e. 111~114...k4)

      So if These Devices are still being sold (From China...), with the (And I use the term loosely here....), "recent" Firmwares on then, why is it so hard for these Cats to do up a quick Three File Zip File? So to allow anyone who wanted to update... Assuming that these past few Updates are at least good for the 2G owners? (I only have a 1G Device), and I find that the Best Firmwares are either 109k4 or 110k4. When it comes to such things as the amcodec. See my request above!

      P.s. Should you be unable to download the AnTuTu Video Benchmark from the PlayStore, I pasted a copy of it on my Google Drive. https://drive.google.com/open?id=0B1...WGc&authuser=0


      Originally posted by londonshore View Post
      I can do you One better.... 114k4

      Again the only "difference" is that this Update has Kodi v14.1 on it... And, outside of being able to run some reverse engineering magic on it, was about the only difference I was able to make off of it, over 113k4. That is.
      Last edited by Ichijoe; 15 April 2015, 14:26.

      Comment


        Originally posted by Ichijoe View Post

        Ok this used to be complicated, but since about a Month ago now its gotten a lot simpler.
        You just need to download the k200.IMG Version of TWRP, and rename it as recovery.IMG, and then place this on your MicroSD Card. Essentially replacing the recovery.img from the Three File's Zip File. You can also delete the aml_pram File as well since it won't be needed.

        All you'd need is the 1xxk4.zip File that you're trying to downgrade to, and the renamed k200.img File (i.e. renamed to recovery.img). This should then boot you into the TWRP Recovery... And yes you WILL NEED A USB MOUSE from this point on! Otherwise it should be as simple as Install -> (Selecting the Location of the *.zip File), -> Selecting the 1xxk4.zip File.

        Otherwise you'll need a Windows PC, to install the Amlogic USB Burner Tool, to flash the 1xxk4.IMG Files back to the Box. Which depending on which version of Windows you might be running. May prove more challenging. *cough* Windows 8.x *cough*. The trick here is to deactivate the requirement for ONLY Signed Drivers. I have enough sence to NOT get involved with Windows 8.x. So you'll have to go ask Uncle Google on how that's done.

        Given how superior TWRP is to the Stock 3e Rcovery, and how much simpeler it is to deal with I'd highly recommend using this method instead.
        Thanks for that, I flashed it and is working great on 108k4. Anyone any ideas where the audio sync issues on everything but XBMC/KODI comes from on later versions?

        Comment


          Originally posted by JCN77 View Post

          Thanks for that, I flashed it and is working great on 108k4. Anyone any ideas where the audio sync issues on everything but XBMC/KODI comes from on later versions?
          No... And since you bring up 108k4, do you have the 2G version? or the older RTL8188 1G Version? Its worth mentioning that if you install the stock 108k4 on a Device with the AP-6181 Wi-Fi Chip, in it... You will lose the Wi-Fi Chip, since the Drivers were either in the very Stock Firmware 108k4 (That I utterly failed to back up!), or from 109k4 onwards.

          In attempting to use a TRWP Recovery (I think it was for the S82 IIRC), I just about managed to brick my MXIII, after my first ~20 Minutes with it. Took me the rest of the Day, and well into that night to finally figure out how I could recover it. At which point 108k4 became a distant memory, for me.

          As far as I can tell the further back you can go... Oddly enought the better the amcodec gets.... If you scan back a few Pages ~ around the 70'ies (In this thread!), you'll find numerus Posts complaining about bad the 109k4 amcodec is (or was...), over the older 107 & 108 (k4) Firmwares... Which they say just worked!

          To answer your other Question... My guess is that these Firmwares are starting to take a real AiO approach, in that the Code gets written Once, and likely then compiled for each Device. before release. Which in turn leaves older devices such as the MXIII without anyone to tighten up the Code. Best example of this is the TCP Large Buffer bug. You have a lage-ish pipe 5MB (50Mbps+) Connection, and still have to deal with lag? Chances are good that this could be corrected by just enabling Large Buffers... Its a known bug that dates as far back as 103k4..... (As I gather this would still be MXII era!), and that bug still lives TO THIS DAY!* So if they utterly refuse to fix something as trivial as this.... Do you really think they'd give a toss about something more complicated like the amcodec? 'cause I don't, and the latest Firmwares prove it. If need be run the AnTuTu Video Benchmark on your 108k4 sometime, and then run it again on anything, above 111k4 and tell me if you can't notice the differences. Notably where the windows Media and Real Video Cooker Parts are either skipped in their entirety, are only shown as a Black Screen. TBF these Bits don't exactly run like Water on 109k4 either but, they do at least render a few... Frames.

          *You can read more about that here...


          Comment


            I have the 2G version, wifi is working fine. I only use the box for kodi v15 and Netflix, both of which are now working fine, so I will try and resist all the petit urges I have to keep playing with my setup.

            PS I bricked it too trying to install TRWP and 108 was the stock version on GeekBuying

            Comment


              You might want to really go though the 70's of this thread again... if you think 108k4 is that great, you might find... According to those Posters that 107k4 was reportedly somewhat better still. Actually with what I'm seeing it could well be true!, but, I can't go any further back then 109k4 though.
              But you'd do well to download the Ookla Speed Test (Google PlayStore), if you haven't and test your Device against it. Both Wi-Fi, and Ethernet. Chances are that the Ethernet is NOT at its full 100Mbps, because the Device (As Stock), is NOT set to use Large TCP Buffers over Ethernet.

              And, since I live in a Flat with a lot of other 802.11b/g/n noise its not really possible to use Wi-Fi where I am. So Ethernet is the best option. (Or so I thought), till this explained why it wasn't working. As Ethernet should almost always be faster then Wi-Fi... the exceptions here being a, n and ac MIMO Mode. Something the AP-6181 doesn't do MIMO Mode that is

              Comment


                QUESTION FOR ROM DEVELOPERS.

                I have problem with CPU temp since aml change the way how kernel manage virtual CPU temp. Since 105k4 my CPU temp is 5%- 75°C and 95% 80°C and my box runs on 1,2 GHz most of the time with any CPU setting or governor even in standby . Before was real temp 42, 47,51... now is 75,80. To be clear I know why. My CPU is not trrimed shown by dmesg and now kernel manage CPU temp depending on CPU usage, number of the processes ...... This aml thermal control optimization is good for maybe newer CPUs like 802b, 802h or others but I have tronsmart Vega one of the first from preorder . I must say many things are better now but since then mine problem is TEMP.

                MY QUESTION IS: which file to change with root explorer from earlier ROM like 104k4 or even 100k4 to have normal CPU temp reading ( normal for my box) and

                IS THIS EVEN POSSIBLE. I have found thermal folder and aml_thermal, virtual_ thermal but they have many files in it . THAT'S WHY I ASK SOMEONE WITH MORE EXPERIENCE IN ROM DEVELOPMENT.

                I know that you are bussy now with new boxes like pipo x7 , draco ... but if you can please share your knowledge with me. My box is tronsmart vega 2G16G same as beelink s82 currently on 109k4(best ROM ever) with 2 extra fans and bigger aluminum cooler on the CPU + OCZ FREEZE thermal paste . Box is allways cold and it's shows 80°C. Help please.

                Comment


                  Originally posted by ivanrandjelovic View Post
                  QUESTION FOR ROM DEVELOPERS.

                  I have problem with CPU temp since aml change the way how kernel manage virtual CPU temp. Since 105k4 my CPU temp is 5%- 75°C and 95% 80°C and my box runs on 1,2 GHz most of the time with any CPU setting or governor even in standby . Before was real temp 42, 47,51... now is 75,80. To be clear I know why. My CPU is not trrimed shown by dmesg and now kernel manage CPU temp depending on CPU usage, number of the processes ...... This aml thermal control optimization is good for maybe newer CPUs like 802b, 802h or others but I have tronsmart Vega one of the first from preorder . I must say many things are better now but since then mine problem is TEMP.

                  MY QUESTION IS: which file to change with root explorer from earlier ROM like 104k4 or even 100k4 to have normal CPU temp reading ( normal for my box) and

                  IS THIS EVEN POSSIBLE. I have found thermal folder and aml_thermal, virtual_ thermal but they have many files in it . THAT'S WHY I ASK SOMEONE WITH MORE EXPERIENCE IN ROM DEVELOPMENT.

                  I know that you are bussy now with new boxes like pipo x7 , draco ... but if you can please share your knowledge with me. My box is tronsmart vega 2G16G same as beelink s82 currently on 109k4(best ROM ever) with 2 extra fans and bigger aluminum cooler on the CPU + OCZ FREEZE thermal paste . Box is allways cold and it's shows 80°C. Help please.
                  Well it could either be a Kernel Problem... Seems possible in which case, not only would you need to recompile it again, you'd also have to have the Source Code as well. Possible? perhaps though I haven't been able to find the "Trick" to that yet myself. Or more likely its a defective / misaligned Sensor? That's giving you incorrect readings. If you fire'ed up CPUz (Grab it on the PlayStore if you don't have it!), how many Cores does it report going off? In reality it should only likely be the One. (At stock!), unless you used some tool like KernelToolkit (Also in the PlayStore!), to run all Four Cores at Max at Once. I think I might have my Box setup like that just to try and see if I could get a better score in the AnTuTu Video Benchmark. I also noticed that its now JU-JU-JU-JU--- Jumping after about an, hour or so, and has even had a hard crash. So I think I'm gonna reset that App and get rid of it. Since I find, (Or, found), this Box to be ok without it. Its certainly no better with it, thats for sure.

                  Comment


                    Originally posted by Ichijoe View Post

                    Well it could either be a Kernel Problem... Seems possible in which case, not only would you need to recompile it again, you'd also have to have the Source Code as well. Possible? perhaps though I haven't been able to find the &quot;Trick&quot; to that yet myself. Or more likely its a defective / misaligned Sensor? That's giving you incorrect readings. If you fire'ed up CPUz (Grab it on the PlayStore if you don't have it!), how many Cores does it report going off? In reality it should only likely be the One. (At stock!), unless you used some tool like KernelToolkit (Also in the PlayStore!), to run all Four Cores at Max at Once. I think I might have my Box setup like that just to try and see if I could get a better score in the AnTuTu Video Benchmark. I also noticed that its now JU-JU-JU-JU--- Jumping after about an, hour or so, and has even had a hard crash. So I think I'm gonna reset that App and get rid of it. Since I find, (Or, found), this Box to be ok without it. Its certainly no better with it, thats for sure.
                    Everything is OK with CPU it runs on 1.6 GHz on 75° c and 1,2ghz on 80°c all 4 cores. Box is fast I see slowdowns and hick ups only when temp is 80. It is kernel problem finless Bob talk about that and just with newer roms, since 105k4, see first post "thermal control optimization". I am not only one my friends have that problem too we all have boxes from preorder first 1000 from factory with older not trrimed CPU( this CPU can't measure temp 100% accurate , that's why is on my box active aml_virtual thermal instead of thermal probe)

                    See this http://freaktab.com/forum/tv-player-...r-to-consumers

                    Again I know why is everything is like it is but a ask this: I want newer firmware like 109k4 with thermal control from 104k4 because for me that's work great. Is this possible? I want to patch newer ROM with older files I just don't know which files.

                    With 104k4 my CPU temp reading is normal 39 -54° C 54 on antutu stability test CPU settings max 1992mhz min 408mhz governor interactive.
                    But so many things are not good on that ROM to get back on it.

                    Comment


                      Hello possible to have 114k4 version for sd card thk's for help

                      Comment


                        Originally posted by michael67260 View Post
                        Hello possible to have 114k4 version for sd card thk's for help
                        Not sure if it has already been posted previously, but you a look here.

                        Comment


                          i have a strange problem with my MX III (1 GB) Box. Often it gaves beep sounds through the soundspeaker out. I use the spdif sound output.

                          How to solve the Problem?

                          Comment


                            Originally posted by watson007 View Post
                            i have a strange problem with my MX III (1 GB) Box. Often it gaves beep sounds through the soundspeaker out. I use the spdif sound output.

                            How to solve the Problem?
                            Beeping? Or you sure its not more of a chime? I assume you setup a Google PlayStore Account on the Device. Perhaps, its an eMail alert? Depending on how many emails you get though say your GMail Account. It could happen every few hours or, every 10 minutes. Posting comments on YouTube doesn't help. Though finding a way to either mute, or remove GMail from the Device altogether might stop all the alerts from happening.

                            Originally posted by Morfic View Post
                            Not sure if it has already been posted previously, but you a look here.
                            Its not exactly Stock, and to be honest unless you have 2G Box... Probably not even worth the bother. I can NOT attest to how it works on 2G Devices, since I only have the 1G Version. But, on the 1G Version the amcodec is even more broken then it was reported to have been back on the 109 / 110 -k4 Firmware(s). Which is why I'm willing to update to say 115k4 (if it ever hits...), but for the Moment, I'm sticking to 110k4... SINCE IT WORKS! And everything from 111k4 on hasn't!

                            Comment


                              Originally posted by michael67260 View Post Hello possible to have 114k4 version for sd card thk's for help
                              Not sure if it has already been posted previously, but you a look here.

                              hello,

                              This version is not original firmware i like 114k4 original firmware update version from sd card thk's for reply

                              Comment


                                nein Ichijoe, ein Piepen das aus dem Lautsprecher kommt - Störgeräusche. Alle paar Stunden kommt es wieder.
                                irgendwo habe ich gelesen dass das davon herkommen kann wenn die Geräte schlecht geerdet wurden.... ob es daran liegt?
                                mein Englisch ist nicht so gut und du kommst ja auch aus Deutschland.

                                Comment

                                Working...
                                X