Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

[ROM] QUICKSHOT V3.1 by The Nitro Team for Minix Neo X7

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

    Install

    One quick question, if i install this rom i only have to install the first package "CUSTOM ROM QS 3.1 TO FLASH FROM PC" ?

    Or to have a 1080p real output i have to install a 1080p kernel from the kernels pack? Or theses kernel are only to overclock? If is only to overclock i don't have interest....

    Thanks in advance.

    Fernando.

    PS: The install works normally on Windows 8 x64?
    Last edited by Nando_lavras; 05 June 2014, 15:56. Reason: Add a question about windows 8

    Comment


      Originally posted by xtremeclock View Post
      HDMI, at least with XBMC (13.1 RC) i can correct it with an offset of 250ms (more or less), the only problem is that i have to re adjust the offset every time i open a file, i didn't find a way to make it permanent...pretty annoying to do it every time i want to watch a movie/tv show.
      Is curious because in any version Nitro did not have this problem. Through the HDMI audio in my minix is perfectly synchronized and I have not changed any settings to have it so.


      Try to install a previous version of XBMC without removing the new one that is not overwritten to my knowledge to personal experiences, and see how it goes...

      Comment


        Originally posted by kodikas View Post
        Today I flashed on of my X7 box with QS V3.1. Rom is very fast and everything working perfectly. At the moment I use my box for XBMC iStream and iStream is not very good with XBMC Gotham. Can someone explain step by step how to flash QS V2 from QS V3.1. I was reading here that I need erase NAND first with KitKat flasher but in QS V3.1 flasher you can only do restore and there is no NAND erase function. I really do not want to brick my box Thank you for your help.
        The instructions for flashing are in the front posts... they even made videos to help explain it.

        Comment


          Originally posted by Nando_lavras View Post
          One quick question, if i install this rom i only have to install the first package "CUSTOM ROM QS 3.1 TO FLASH FROM PC" ?

          Or to have a 1080p real output i have to install a 1080p kernel from the kernels pack? Or theses kernel are only to overclock? If is only to overclock i don't have interest....

          Thanks in advance.

          Fernando.

          PS: The install works normally on Windows 8 x64?
          you only need to install the main package.
          The rest are addon ...


          I installed from Win7-64. I do not know if the installation is the same with Win8, but I'm inclined to think it's the same thing, otherwise the developers - so meticulous - would have added specific instructions...


          If you have problems with flickering, which I solved with specific kernels ...I've had them and I solved
          Last edited by kRel; 05 June 2014, 17:53.

          Comment


            Originally posted by rdsok View Post
            The instructions for flashing are in the front posts... they even made videos to help explain it.
            Yes I know how to flash V3.1 but I'm a bit confused how to revert back from V3.1(KK) to V2(JB). I was following post that I need to erase NAND with V3.1(KK) flasher then open V2(JB) flasher and flash without erasing NAND. There is no button on V3.1(KK) flasher to erase NAND.

            Comment


              Originally posted by kodikas View Post
              Yes I know how to flash V3.1 but I'm a bit confused how to revert back from V3.1(KK) to V2(JB). I was following post that I need to erase NAND with V3.1(KK) flasher then open V2(JB) flasher and flash without erasing NAND. There is no button on V3.1(KK) flasher to erase NAND.
              I translated with google translator ... I hope goes well ...

              - Download Quickshot v.2: you will need just the app for the flash from pc (rkandroidtool.exe)
              - Disconnect all
              - Starts rkandroidtool
              - Connect the usb cable-microusb to PC
              - Connects the power
              - Press and hold the reset button
              - Press and hold the power button, do not release the power button until the end of the process
              - When rkandroidtool detects the minix you can release the reset button, but still hold down the power button for the entire process.
              - Click on the button eraseidb
              - Click on start, still holding the power button to flash over. At the end you can release the power button.
              ---
              if the first time it fails ,disconnect, reconnect and do it the second time the same way with both buttons pressed.
              Last edited by kRel; 14 June 2014, 09:39.

              Comment


                Originally posted by kRel View Post
                you only need to install the main package.
                The rest are addon ...


                I installed from Win7-64. I do not know if the installation is the same with Win8, but I'm inclined to think it's the same thing, otherwise the developers - so meticulous - would have added specific instructions...


                If you have problems with flickering, which I solved with specific kernels ...I've had them and I solved
                With my notebook with Windows 8 x64 i don't achieve to install, Windows 8 says about a error with USB descriptors, hapilly i have a Windows XP in my network, with this machine the install runs smootly and in 5 minutes the installation was done....

                After installed go to considerations.... Daammm.... This rom its blazing fast, the access to internal SD is very quickly, much different from the official rom, i've installed all my apps in about 5 minutes, i thinks its not same box as before ...

                For now all its working ok, all my apps install and runs smooth, XMBC now recognize 1080p.

                VERY GOOD ROM! I use more extensively at night, i have to work, but the first impression is very good!

                Thanks.

                Fernando.

                Comment


                  Originally posted by kRel View Post
                  I translated with google translator ... I hope goes well ...

                  - Download Quickshot v.2: you will need just the app for the flash from pc (rkandroidtool.exe)
                  - Disconnect all
                  - Starts rkandroidtool
                  - Connect the usb cable-microusb to PC
                  - Connects the power
                  - Press and hold the reset button
                  - Press and hold the power button, do not release the power button until the end of the process
                  - When rkandroidtool detects the minix you can release the reset button, but still hold down the power button for the entire process.
                  - Click on the button eraseidb
                  - Click on start, still holding the power button to flash over. At the end you can release the power button.
                  Done everything Step by Step. Received ERROR: Download file failed
                  No when I press erase NAND on QS V2 rkandroidtool see only 2048 not 4096. So I think I just bricked my box...

                  Comment


                    Originally posted by Nando_lavras View Post
                    With my notebook with Windows 8 x64 i don't achieve to install, Windows 8 says about a error with USB descriptors, hapilly i have a Windows XP in my network, with this machine the install runs smootly and in 5 minutes the installation was done....

                    After installed go to considerations.... Daammm.... This rom its blazing fast, the access to internal SD is very quickly, much different from the official rom, i've installed all my apps in about 5 minutes, i thinks its not same box as before ...

                    For now all its working ok, all my apps install and runs smooth, XMBC now recognize 1080p.

                    VERY GOOD ROM! I use more extensively at night, i have to work, but the first impression is very good!

                    Thanks.

                    Fernando.
                    On QSv.2 explained something of Win8...


                    I think you should follow the explanations given here, or alternatively wait for the response of daemonium or leolas

                    Comment


                      Originally posted by kodikas View Post
                      Done everything Step by Step. Received ERROR: Download file failed
                      No when I press erase NAND on QS V2 rkandroidtool see only 2048 not 4096. So I think I just bricked my box...
                      I'm sorry...

                      The instructions are the ones who gave me daemonium on my specific request and which are shown in the first pages of the discussion, here

                      The same instructions I have given to a user in another forum and he managed to go back to QSv.2 here... this user shortly after thanked me for to the successful completion of the procedure ... here

                      Repeat the procedure, or waiting for help from the developers ...

                      One question: you pointing to full path\update.img to the rom QSv.2 in the rkandroidtool box above ??
                      Are you certain that the image of QSv.2 is not corrupt? Did you check the hash of your QSv.2 with the original one?

                      Comment


                        Originally posted by kRel View Post
                        I'm sorry...

                        The instructions are the ones who gave me daemonium on my specific request and which are shown in the first pages of the discussion, here

                        The same instructions I have given to a user in another forum and he managed to go back to QSv.2 here... this user shortly after thanked me for to the successful completion of the procedure ... here

                        Repeat the procedure, or waiting for help from the developers ...

                        One question: you pointing to full path\update.img to the rom QSv.2 in the rkandroidtool box above ??
                        Are you certain that the image of QSv.2 is not corrupt? Did you check the hash of your QSv.2 with the original one?
                        Found one post on this forum with same problem. Followed all instruction and my Minix box is alive again Thank you for support. The link to post:

                        Comment


                          Originally posted by kodikas View Post
                          Found one post on this forum with same problem. Followed all instruction and my Minix box is alive again Thank you for support. The link to post:
                          http://www.freaktab.com/showthread.p...l=1#post112509


                          I'm happy for you


                          I suggest - if you like - to describe step-by-step the recovery procedure that you personally made​​, (I read the link you provided). Can be of help to others users...
                          Perhaps it is also the case of put it on the first page

                          Comment


                            Originally posted by kRel View Post

                            QS V3.1 is very good rom, colours and speed is beautiful. I needed to go back to JB because iStream is not working at all on xbmc gotham. After xunity team reales iStream for Gotham xbmc I will switch back to this rom.

                            Comment


                              Originally posted by demasiado View Post
                              Yeah, I know good USB DACs would be the best and reliable way to output
                              audiophile sound from audiophile content...

                              However, I'd be quite satisfied with a HDMI only solution to my A/V Marantz receiver which has good (if not very good) CS42528 DACs (and my Windows/Linux PCs can output very good HD sound to it).
                              I still don't know if 44/16 only over HDMI is a Minix X7/RK3188 HW or/and an Android SW limitation...
                              I would also like to get 24/96 hi-res audio music as wheel as multichannel.

                              I am really bot an expert in android but according to what I have read, audio_policy.conf describe the hardware compatibility of the box. For now, it is set to
                              hdmi {
                              sampling_rates 44100|48000
                              channel_masks AUDIO_CHANNEL_OUT_5POINT1|AUDIO_CHANNEL_OUT_STEREO
                              formats AUDIO_FORMAT_PCM_16_BIT
                              devices AUDIO_DEVICE_OUT_AUX_DIGITAL
                              flags AUDIO_OUTPUT_FLAG_DIRECT

                              So adding 96000 in sampling_rates + PCM_24_BIT and crossing our finger might be a good start...

                              Can someone tell if I am in the wright direction? It seems simple to try but like I said, I am not an expert.

                              Comment


                                Originally posted by SL06 View Post
                                I would also like to get 24/96 hi-res audio music as wheel as multichannel.

                                I am really bot an expert in android but according to what I have read, audio_policy.conf describe the hardware compatibility of the box. For now, it is set to
                                hdmi {
                                sampling_rates 44100|48000
                                channel_masks AUDIO_CHANNEL_OUT_5POINT1|AUDIO_CHANNEL_OUT_STEREO
                                formats AUDIO_FORMAT_PCM_16_BIT
                                devices AUDIO_DEVICE_OUT_AUX_DIGITAL
                                flags AUDIO_OUTPUT_FLAG_DIRECT

                                So adding 96000 in sampling_rates + PCM_24_BIT and crossing our finger might be a good start...

                                Can someone tell if I am in the wright direction? It seems simple to try but like I said, I am not an expert.
                                Maybe first need to look at the specs of the DAC?

                                Comment

                                Working...
                                X