Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

[ROM] Mecool M8S Pro TVStock Nexus ROM (Android TV 7.1)

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    MAGENDANZ.
    Can you tell me if this ROM it is for the meccol m8s pro of 3gb of ram ddr4 and EMMC Nand Flash "ROM" of 16GB?

    Comment


    • Guest's Avatar
      Guest commented
      Editing a comment
      Yes, it's for all configurations of the Mecool M8S Pro (but not the M8S Pro L, M8S Pro W or M8S Pro+).

    Have just updated. Feels faster and more stable than previous version. No more green artefacts, when playing videos. Thanks!

    Comment


    • Guest's Avatar
      Guest commented
      Editing a comment
      Yes, it's feeling quite stable and snappy. My only frustration is this longstanding problem with wake from sleep causing a reboot.
      Last edited by Guest; 05 November 2017, 21:15.

    Exactly, I agree on size and number with both of you! It's much more stable, and most bugs have been fixed, one or the other with the Google app (sometimes it stops), but it's way better than the previous version. Many thanks Guest for your help with the OTA update! I just moved from M8S_PRO to M8SPRO at the build.prop line you indicated and the update was perfect. My only real frustration is this one of the reboot device when erasing the screen, I am accustomed to other box in which erasing the screen was just deep sleep. I'm pretty sure that this bug not because of its firmware modification, I tested a "Stock" and also had it. It seems that the latest builds released by "Mecool" are coming with this bug. It would be great if I had the sleep options removed from the device. Another even more annoying thing is that when I am using the directional keys quickly device clears the screen and restarts when pressing Power Button. If you removed the possibility of deep sleep, that would be great.

    Comment


    • Guest's Avatar
      Guest commented
      Editing a comment
      I've set "def_stay_on_while_plugged_in" to true in the SettingsProvider. Not sure what else I can do.

    See how "deep sleep" happens or the standby mode for me ... I click the left and down arrow keys several times and this causes the device to turn off the screen. Yes, I know, it's a very ridiculous mistake, I did not extend it because it happens. This caused me some frustration.

    Comment


      Originally posted by Novato View Post
      See how "deep sleep" happens or the standby mode for me ... I click the left and down arrow keys several times and this causes the device to turn off the screen. Yes, I know, it's a very ridiculous mistake, I did not extend it because it happens. This caused me some frustration..
      Not something accurate, sometimes I'm playing or zapping the menus and the screen turns off.

      Comment


        Originally posted by Novato View Post

        Not something accurate, sometimes I'm playing or zapping the menus and the screen turns off.
        It is a defective remote. I have 3 of these Mecool boxes, with 3 identical remotes. One remote from my original Mecool M8S Pro Plus, has this issue, but not the other two.
        MK818B, T428, ATV 1220, CS918S, TV01, S89H, R89, ADT-1, MK808B Plus, MINIX X8-H Plus, Tronsmart Orion R68

        Comment


          Originally posted by Magendanz View Post
          When the 20171005 build was first released, it had the wrong device code. This error was quickly corrected in a subsequent rolling update, but you'll need to make the correction yourself. (The check is critical so that you don't install the update on the M8S Pro L, which will brick the box.)

          Just install a root file explorer like EFS File Explorer and modify the build.prop value for "ro.product.device" from "M8S_Pro" to "M8SPro". After that, the update should pass environment checks.

          Alternatively, you can just flash the burn package (or comment out the check in the updater-script).
          Dear magendaz, could you help me modify the build.prop value and reupload the zip file? Cause I'm a total newbie and I don't understand how to modify it. Please.... Thanks in advance.

          Comment


          • Guest's Avatar
            Guest commented
            Editing a comment
            If you're not comfortable making changes to the bujld.prop on a rooted device, just unpack the OTA update and remove the following lines from updater-script (buried in META-INF):

            (file_getprop("/system/build.prop", "ro.product.device") == "M8SPRO") ||
            abort("E3004: This update package is intended only for the M8S Pro.");

            Once that is gone, it won't care what device it's installing on. (Note that this is very dangerous, which is why I'm reluctant to post the modified .zip file.)

            When you repack as a .zip, it will no longer be signed with the platform key. Just install in TWRP and make sure the Zip Signature Verification option isn't checked.
            Last edited by Guest; 05 November 2017, 22:46.

          @Mag...just curious: " unpacking ota " is only possible when on m.s. platforms?
          Kris....don't forget my boxes! Okay?

          Comment


          • Guest's Avatar
            Guest commented
            Editing a comment
            No, it's just a .zip archive. You can unpack and repack on any platform. Just ensure the file hierarchy remains the same.

          Originally posted by clarkss12 View Post

          It is a defective remote. I have 3 of these Mecool boxes, with 3 identical remotes. One remote from my original Mecool M8S Pro Plus, has this issue, but not the other two.
          Maybe you're right, after posting here I changed Powerkey's default "sleep now" to "shutdown" and when I press the directional buttons on the remote control in some sequence, instead of entering "sleep now" it just shuts off as if I had chosen to hang up. In other words, something causes the directional keys on my control to turn on Powerkey.

          Comment


            Guest it's okay, you're already doing a great job bringing that ATV firmware to our device, I understand you're doing everything in your power .

            Comment


              Has anyone experimented with different settings for config_shortPressOnPowerBehavior? These config settings are defined here and compiled into framework-res.apk.

              <!-- Control the behavior when the user short presses the power button.
              0 - Nothing
              1 - Go to sleep (doze)
              2 - Really go to sleep (don't doze)
              3 - Really go to sleep and go home (don't doze)
              4 - Go to home
              5 - Dismiss IME if shown. Otherwise go to home
              -->
              <integer name="config_shortPressOnPowerBehavior">1</integer>

              You could set this to "0", "4" or "5" to prevent going into sleep via Power button short press. The deeper sleep options will have slower wake, but might work around the reboot bug.

              Comment


              • Guest's Avatar
                Guest commented
                Editing a comment
                Unfortunately, I just tested the deeper sleep (don't doze) and it results in the same reboot on wake. This seems to be an issue with the bootloader.

              Originally posted by Magendanz View Post
              Has anyone experimented with different settings for config_shortPressOnPowerBehavior? These config settings are defined here and compiled into framework-res.apk.

              <!-- Control the behavior when the user short presses the power button.
              0 - Nothing
              1 - Go to sleep (doze)
              2 - Really go to sleep (don't doze)
              3 - Really go to sleep and go home (don't doze)
              4 - Go to home
              5 - Dismiss IME if shown. Otherwise go to home
              -->
              <integer name="config_shortPressOnPowerBehavior">1</integer>

              You could set this to "0", "4" or "5" to prevent going into sleep via Power button short press. The deeper sleep options will have slower wake, but might work around the reboot bug.
              Did you test mode 0 or Nothing? Can you tell me if it works? Since a light touch on the Power button is causing restart or shutdown, then for me it would be more interesting to disable the short press.

              Comment


              • Guest's Avatar
                Guest commented
                Editing a comment
                Yeah, well that does...nothing. PM me if you want a framework-res.apk built with that change. You have to replace the file in TWRP and set the permissions correctly.

              Originally posted by Novato View Post

              Maybe you're right, after posting here I changed Powerkey's default "sleep now" to "shutdown" and when I press the directional buttons on the remote control in some sequence, instead of entering "sleep now" it just shuts off as if I had chosen to hang up. In other words, something causes the directional keys on my control to turn on Powerkey.
              I have to rethink what I said in my statement. I just redid my Mecool M8S Pro PLUS using the burn package with my computer. Anyway, while setting it up, and typing in my email address and password, first remote, caused a reboot. Used my second remote, same thing, got almost through the setup and it rebooted again. Finally, my third remote got me through the setup, but can't say for sure it is a good remote. So, perhaps, it is not the remote, but the firmware.
              MK818B, T428, ATV 1220, CS918S, TV01, S89H, R89, ADT-1, MK808B Plus, MINIX X8-H Plus, Tronsmart Orion R68

              Comment


                Hello Guest , I would like to, because occasionally I have turned off my device on the directionals buttons, so disabling the shortest pressure is the smartest thing to do at the moment. I'm grateful for your willingness to help me.

                Comment


                  Dear magendaz, thank you so much for your advice to remove the lines inside the update script. At last I've succeeded in flashing the OTA update.

                  Comment

                  Working...
                  X