Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

NEW - Lollipop - wasser firmware 3.0.6 for Minix Neo X7

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

    Originally posted by flhthemi View Post
    henk32211, I'm pretty much a n00b like you are but I believe the only kernel available from wasser for this ROM is THIS one and it might not help your flicker issue but might be worth a try.
    thx fore the support

    Comment


      Originally posted by flhthemi View Post
      So Molle should I click the RUN button?

      Also would henk32211 maybe fix his issue by starting all over and flashing the ROM again?
      try it don't work
      thx for the support

      Comment


        Have you also tried to use a different HDMI cable? It's not likely but worth a try. Oh, and maybe try changing the display settings to a lower resolution? Like instead of 1920X1080 try the next lower one and see if it's gone...I don't know if the X7's do that. Or maybe mess with the TV itself or a different TV or A different HDMI port.

        FLHT = Harley
        HEMI = 2010 Dodge Challenger SRT
        Cause I've been asked.

        Comment


          Hi, Can I flash this rom on minix V7 mini ? I want run lollipop on my V7 mini. Thanks

          Comment


            Originally posted by konnichiwa View Post
            Hi, Can I flash this rom on minix V7 mini ? I want run lollipop on my V7 mini. Thanks
            Basically yes, but you'll most likely lose BT and/or WiFi due to different hardware.
            NVidia Shield TV 2015 16 GB || Stock
            NVidia Shield TV 2017 16 GB || Stock
            Buy me a beer?

            Comment


              Originally posted by henk32211 View Post
              I think I broke it????
              Nothing's broken if you can still flash and different ROMs give different results.
              NVidia Shield TV 2015 16 GB || Stock
              NVidia Shield TV 2017 16 GB || Stock
              Buy me a beer?

              Comment


                Originally posted by flhthemi View Post
                Have you also tried to use a different HDMI cable? It's not likely but worth a try. Oh, and maybe try changing the display settings to a lower resolution? Like instead of 1920X1080 try the next lower one and see if it's gone...I don't know if the X7's do that. Or maybe mess with the TV itself or a different TV or A different HDMI port.
                Excellent advice to all who suffer from display problems.
                NVidia Shield TV 2015 16 GB || Stock
                NVidia Shield TV 2017 16 GB || Stock
                Buy me a beer?

                Comment


                  Originally posted by flhthemi View Post
                  Have you also tried to use a different HDMI cable? It's not likely but worth a try. Oh, and maybe try changing the display settings to a lower resolution? Like instead of 1920X1080 try the next lower one and see if it's gone...I don't know if the X7's do that. Or maybe mess with the TV itself or a different TV or A different HDMI port.
                  (and maybe try changing the display settings)
                  Yes its working great now many thx
                  Last edited by henk32211; 04-08-2017, 09:30.

                  Comment


                    For all the support many thx all
                    greeting
                    its working great now

                    Comment


                      Love success! Glad it was that simple! Now, go enjoy your box!
                      FLHT = Harley
                      HEMI = 2010 Dodge Challenger SRT
                      Cause I've been asked.

                      Comment


                        Even the tool in Finless rom does not seem to work with me. All i set is min freq to 1ghz, altough sub1ghz frequencies are being used, and 1.5 and 1.6 barely make it above 2-3%. 1.7 and 1.8 remain unused.

                        I surely know i dont have the rk3188t variant as i have OCd this one before with the same rom.

                        just in case, have you guys flashed the kernel together with the rom or after?

                        EDIT: attaching a catlog, not sure if helps but...
                        Attached Files
                        Last edited by Pluto; 04-10-2017, 17:30.

                        Comment


                          Originally posted by Pluto View Post
                          just in case, have you guys flashed the kernel together with the rom or after?
                          I usually flashed the ROM and the additions back-to-back. First the ROM with RKBatchTool, then the oc'd kernel (and my modified boot image) with RKDevelopTool. Here's the complete procedure:
                          1. Start RKDevelopTool
                          2. Connect device
                          3. Erase IDB twice
                          4. Disconnect / power off device
                          5. Start RKBatchTool
                          6. Select ROM image
                          7. Connect device
                          8. Flash ROM with "Restore" option
                          9. Disconnect / power off device
                          10. Start RKDevelopTool
                          11. Select partitions and images
                          12. Connect device
                          13. Flash images
                          14. Disconnect / power off device
                          15. Connect device to TV etc, and power on
                          16. Profit...
                          Last edited by Molle; 04-11-2017, 16:16.
                          NVidia Shield TV 2015 16 GB || Stock
                          NVidia Shield TV 2017 16 GB || Stock
                          Buy me a beer?

                          Comment


                            Can anybody point me to a nls_utf8.ko kernel module, which will work with the kernel in Wasser FW 3.0.6?

                            I did a clean install of version 3.0.6 and I'm trying to mount a share via CIFS, but utf8 doesn't seem to work. "mount -o iocharset=utf8" results in "cannot access a needed shared library". When I remove the iocharset=utf8 option, everything works fine, but then some of the file names aren't displayed correctly (I get only question marks). I realise that the kernel is not configured with nls_utf8 and that's why I'm looking for a nls_utf8.ko module, which I can load before mounting a CIFS share.

                            There was a nls_utf8.ko module posted in this thread for an older version of the FW, but I cannot find such module for the 3.0.x series.

                            Any help is much appreciated! Thanks!

                            Comment


                              I have managed to solve the utf8 problem by compiling the module from the kernel sources mentioned in the topic 3.0.101 Kernel Released. I am attaching the file, should anyone else be facing the same problem.

                              On a side note automatic frame rate switching doesn't seem to work in Kodi. I can confirm that it works when a video file is played directly from the pre installed file manger app, but in Kodi it doesn't work.

                              I seems that Kodi 17 doesn't support rate switching on Rockchip any more, but at least Kodi 16.x looks for the file in /sys. It just happens to use a different path, which results in
                              Code:
                              ERROR: RKEGL: no rw on /sys/class/display/display0.HDMI/mode
                              The actual location is
                              Code:
                              /sys/class/display/HDMI/mode
                              and I assume that if /sys/class/display/display0.HDMI can somehow be symlinked (/sys/class/display/HDMI itself is a symlink by the way), then it will fix the frame rate switching problem.

                              Is there another way to work around this?
                              Attached Files

                              Comment


                                Originally posted by Molle View Post
                                I usually flashed the ROM and the additions back-to-back. First the ROM with RKBatchTool, then the oc'd kernel (and my modified boot image) with RKDevelopTool. Here's the complete procedure:
                                1. Start RKDevelopTool
                                2. Connect device
                                3. Erase IDB twice
                                4. Disconnect / power off device
                                5. Start RKBatchTool
                                6. Select ROM image
                                7. Connect device
                                8. Flash ROM with "Restore" option
                                9. Disconnect / power off device
                                10. Start RKDevelopTool
                                11. Select partitions and images
                                12. Connect device
                                13. Flash images
                                14. Disconnect / power off device
                                15. Connect device to TV etc, and power on
                                16. Profit...
                                The IDB erase, i've never done it, EVER. I thought it bricked the boxes...definitely will try again.

                                Is that the same boot.img that you've shared quite a while ago?

                                Comment

                                Working...
                                X