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

  • emtt_medo
    replied
    The problem xbmc with the addition of ( xbmctorrent )
    Do not work when you try to run a movie or series
    error
    Script failed: xbmctorrent

    Last edited by emtt_medo; 17 June 2014, 13:20.

    Leave a comment:


  • tode
    replied
    Originally posted by Ico747 View Post
    @Tode For you what is better QUICKSOT 3.1 or Wasser v 1.0.3?
    In my opinion they are equivalent, the ROMs are both very good indeed!
    I have two X7 so I'm using QS and Wasser at the same time
    tode

    Leave a comment:


  • Ico747
    replied
    @Tode For you what is better QUICKSOT 3.1 or Wasser v 1.0.3?

    Leave a comment:


  • tode
    replied
    Originally posted by tltester View Post
    Hi. I wanted to report another small glitch on my QS3.1 on X7 - after playing 5.1 with pass-through on XBMC I have no sound on my Pioneer receiver (connected with HDMI) until I turn it off and on. This is quite consistent and happens only with KitKat (was fine with 006c)...
    Same for me, with Onkyo receiver, often when I use MX Player,
    tode

    Leave a comment:


  • tltester
    replied
    Hi. I wanted to report another small glitch on my QS3.1 on X7 - after playing 5.1 with pass-through on XBMC I have no sound on my Pioneer receiver (connected with HDMI) until I turn it off and on. This is quite consistent and happens only with KitKat (was fine with 006c)...

    Leave a comment:


  • zektor
    replied
    Originally posted by leolas View Post
    Sorry but I must ask it, have you installed the neo x7 ROM? some people download the mini version.

    If you use the right version, try this:don't change language in the setup wizard, and pass the initial wifi setup and when wizard ends, wait 5 minutes without try anything. then power off the device and power on again (not reboot) then activate wifi and see if it works and configure the rest of the settings.

    sent by my phone.
    enviado desde mi teléfono.

    leolas
    It was definitely the X7 (not mini) rom. I have both units. I actually got fed up and exchanged the X7 and have another one coming on Wed. If this occurs again I will definitely try you suggestion. Thanks for that. I was just curious as to what I could have done to cause something so strange.

    In any case, I will just be flashing QS3.1 and thats it from here on (and any updates from you as well of course). This is bar none the best rom available. I also have a RKM MK902 coming and was really happy to see QS3.1 available there as well

    Leave a comment:


  • leolas
    replied
    Re: [ROM] QUICKSHOT V3.1 by The Nitro Team for Minix Neo X7

    Originally posted by zektor View Post
    Yesterday I decided to try another rom out of curiosity, so I temporarily left QS3.1 and installed the other rom (Finless). Well, I wasn't happy with the performance and decided to go back to QS3.1. However, when I reflashed and then rebooted it, I could not turn on wi-fi. It would just sit at the setting up wifi screen saying "turning on wifi" and just never would turn on. I reflashed the rom again, thinking maybe a bad flash or something. Same deal. I flashed Finless again just to make sure wi-fi actually works, and it picks up and works fine here. Reflashed QS3.1 *again* and still not turning on. I bypassed the initial wi-fi setup and went into the settings to turn on the wifi. The switch will not move!

    I have never encountered anything like this before. QS3.1 initially (before I did any other flashing) was working fine with wi-fi. Now I simply cannot get this rom to activate/turn on the wifi. What gives?
    Sorry but I must ask it, have you installed the neo x7 ROM? some people download the mini version.

    If you use the right version, try this:don't change language in the setup wizard, and pass the initial wifi setup and when wizard ends, wait 5 minutes without try anything. then power off the device and power on again (not reboot) then activate wifi and see if it works and configure the rest of the settings.

    sent by my phone.
    enviado desde mi teléfono.

    leolas

    Leave a comment:


  • zektor
    replied
    Really weird Wi-Fi issue

    Yesterday I decided to try another rom out of curiosity, so I temporarily left QS3.1 and installed the other rom (Finless). Well, I wasn't happy with the performance and decided to go back to QS3.1. However, when I reflashed and then rebooted it, I could not turn on wi-fi. It would just sit at the setting up wifi screen saying "turning on wifi" and just never would turn on. I reflashed the rom again, thinking maybe a bad flash or something. Same deal. I flashed Finless again just to make sure wi-fi actually works, and it picks up and works fine here. Reflashed QS3.1 *again* and still not turning on. I bypassed the initial wi-fi setup and went into the settings to turn on the wifi. The switch will not move!

    I have never encountered anything like this before. QS3.1 initially (before I did any other flashing) was working fine with wi-fi. Now I simply cannot get this rom to activate/turn on the wifi. What gives?

    Leave a comment:


  • leolas
    replied
    Re: [ROM] QUICKSHOT V3.1 by The Nitro Team for Minix Neo X7

    Originally posted by ilikenwf View Post
    Maybe I should just install finless and wait until minix comes out with a 4.4.x build, and he releases a new version of the finless rom?
    That is the good thing, you have tons of roms to install.

    There are people with problems with some roms, but if we can't reproduce the problems is hard to try to solve them, I tested the rom with all the hdmi cables I have in home and in all the I had before published the rom, and none of them give me problems.

    sent by my phone.
    enviado desde mi teléfono.

    leolas

    Leave a comment:


  • ilikenwf
    replied
    Maybe I should just install finless and wait until minix comes out with a 4.4.x build, and he releases a new version of the finless rom?

    Leave a comment:


  • ilikenwf
    replied
    Originally posted by rdsok View Post
    I had meant to mention trying another cable on my first post... just make certain it's a good quality one and not a cheapy. The one that comes with the Minix devices are good ones, but like any cable they can also fail over time. Also, if you aren't already ( you didn't mention one way or the other )... don't have any other devices connected between your x7 and your TV such as a Home Theater unit or HDMI switch... it's easier to diagnose with fewer components what may be the cause of something that way. Also... try any other HDMI input ports on your TV as well... just in case... again unlikely but still a possibility that could be easily eliminated with a quick test.
    I just now tried another cable and that did not help. No receiver (yet) ...that's next to purchase on my list. 720p at 60hz looks just fine, other than not being 1080p I wonder if the LCD screen density thing mentioned in the top posts may have something to do with it?

    Leave a comment:


  • rdsok
    replied
    Originally posted by ilikenwf View Post
    I wasn't trying to argue, I appreciate the suggestions I was just explaining the situation further. I tried those kernels too...I'm kinda confused. I may try a different HDMI cable and see if that helps...but it sounds like some sort of kernel issue.
    I had meant to mention trying another cable on my first post... just make certain it's a good quality one and not a cheapy. The one that comes with the Minix devices are good ones, but like any cable they can also fail over time.

    Also, if you aren't already ( you didn't mention one way or the other )... don't have any other devices connected between your x7 and your TV such as a Home Theater unit or HDMI switch... it's easier to diagnose with fewer components what may be the cause of something that way. Also... try any other HDMI input ports on your TV as well... just in case... again unlikely but still a possibility that could be easily eliminated with a quick test.

    Leave a comment:


  • ilikenwf
    replied
    Originally posted by rdsok View Post
    My reply listed some possible causes... if they don't apply fine but it wasn't meant to start an arguement or for your to disagree with, just some directions for you to look into. Every situation can differ. justXBMC's ROM is still on Jellybean... if you are going to compare it fairly... compare it to Quickshot v2 since KitKat does work differently. KitKat is smoother and faster than Jellybean but the things that changed to give us those advantages can affect other areas ( perhaps such as those you are seeing ) For most of the people here... in fact all so far up until you... no one else has reported the artifacts you are getting.... If you haven't tried them yet... try the kernels for those that were reporting flashing/blinking on the screen... it may help or may not but until you test, no one can say.
    I wasn't trying to argue, I appreciate the suggestions I was just explaining the situation further. I tried those kernels too...I'm kinda confused. I may try a different HDMI cable and see if that helps...but it sounds like some sort of kernel issue.

    Leave a comment:


  • rdsok
    replied
    Originally posted by ilikenwf View Post
    No OC, stock kernel. This happens on all android screens and any apps that are opened. If I take it down to 24hz or 720p at 60hz, it works fine. My blu-ray player does 1080p at 60 or 120 hz and doesn't have this problem, so I know it is not the TV. The justXBMC default kernel doesn't give me these problems, either.
    My reply listed some possible causes... if they don't apply fine but it wasn't meant to start an arguement or for your to disagree with, just some directions for you to look into. Every situation can differ.

    justXBMC's ROM is still on Jellybean... if you are going to compare it fairly... compare it to Quickshot v2 since KitKat does work differently. KitKat is smoother and faster than Jellybean but the things that changed to give us those advantages can affect other areas ( perhaps such as those you are seeing )

    For most of the people here... in fact all so far up until you... no one else has reported the artifacts you are getting.... If you haven't tried them yet... try the kernels for those that were reporting flashing/blinking on the screen... it may help or may not but until you test, no one can say.

    Leave a comment:


  • ilikenwf
    replied
    Originally posted by rdsok View Post
    There are probably several possible causes... If you've OC'd the system too much for it to be stable... always stress test after selecting an OC kernel. The default kernel shouldn't cause any trouble for a device with good hardware and also runs smoothly. The file in question may be at fault... always do these tests with a file that is on the local drive to make it consistent and to ensure that isn't caused by a bad stream ( which is common with an internet source ). Different players may also be using different codec's to decode the video... so one player may play a particular video that was encoded a certain way just fine and another may not just because the codec being used may not be as good for that file type. As an example... the included MX player ( and codecs ) are probably the best you can get usually... but I do have a file that crashes it on one of my other devices but plays perfect in the XBMC I have on the same device... on my Neo x7... the same file works fine in MX player... In this case there is nothing wrong with any of the softwares or devices... it's just a compatibility that shows up on a particular codec on that one device... so I use a different player to view it.
    No OC, stock kernel. This happens on all android screens and any apps that are opened. If I take it down to 24hz or 720p at 60hz, it works fine. My blu-ray player does 1080p at 60 or 120 hz and doesn't have this problem, so I know it is not the TV. The justXBMC default kernel doesn't give me these problems, either.

    Leave a comment:

Working...
X