Hi
I post my comments here, thought it wasn’t necessary to bump the other thread again when we have this about the DSO Quad, the main category is still the nano.
I got my sample today, thanks!
First, the plastic isn’t a perfect fit (neither front or back), draws the impression down a bit but you already write that you have made corrections to the mold. Next, I had some trouble connecting the battery, the connector just didn’t want to slide over the pins for some reason, after a few minutes of struggling it finally snapped in place.
Now turning it on for the first time, the first thing I notice is that the screen view angle isn’t the best, the eyes is a bit too far away from each other when viewing the wide screen so the backlight shines trough very different for each eye making it a bit hard too get the eyes comfortably focused on the screen. Holding the device standing up like a mobile phone in hand makes it clear that the screen was probably made to be viewed that way on a mobile phone or something.
Then comes the most tricky part, navigating, I still havn’t figured all out yet (20 mins of play). The firmware is even more illogical then the first DSO nano versions. And I really think the interface could be navigated with only one left/right switch but I may change. The old DSO nano with BenF’s firmware can very easily be used in complete dark with only a minute or two of traning. You won’t do that with the quad, thats for sure 
And then you got the SINGL (DSO nano “SING”) wrong this time again. It will capture one buffer right ofter you press the key and stop directly after that even if no trigging occurred.
With this many settings to play with I think you must add some kind of profile support so you can save all the settings if you use it frequently in the same application.
I will write more but that is all for tonight. In short the quad is 4 steps forward in hardware and 3 steps back in firmware. A really interesting thing would be how compatible the hardware in the quad would be with the old nano? Could BenF’s firmware be loaded on this too and detect the hardware and adapt to it and make the extra channels and features visible? Would be best if it could be maintained in one code base and not forked I think if they are not to far from each other. I guess the screen resolution is a hard thing to cope with, I guess it’s 480×240 so it’s wider but not higher.
BTW I really like the buffer display at the bottom, if I just could figure it out how to scroll it, the best I have managed is the white box jumping back and forth a few pixels without the screen moving, don’t ask how I did that 
Btw, what dows the M and F buttons do? S is for select I guessed.