Sorry for being out of touch, we are extensively examining all aspects of the product. We had thorough discussions with our manufacturer to make sure nothing is missed.
Testing also took longer than expected. As a result of our exhaustive testing, we decided we will have to do a second D.V.T. We recently had a large and productive meeting with representatives from all the factories involved in manufacturing Pocket P.C.'s parts so make sure that everyone is on the same page.
We made a few mistakes to the PCB design and would feel more comfortable to make sure we correct them in a second D.V.T. before going to the P.V.T. phase.
As you can see below, the keyboard is almost there.
- The status LED is a little too bright which causes the blue to bleed into the main keyboard when itās on.
- A covering is missing over the LED where the newly added buttons are which is why the keyboard is slightly brighter there. We will correct this in the M.P. keyboard covers.
- The keyboard was silkscreen by hand and the black is a little too thin. We will ask them to do two passes in the M.P.
- There was a software file glitch at the factory which caused the right-most button on the bottom to show question marks instead of the actual characters. We will ask them to correct and carefully review the silkscreen stencil against the proof before doing the silkscreen in the future.
- Some characters are hard to read so we will be making them bigger in the final version.
Iāve taken a lot of pictures and videos which we have to edit together and are planning on sharing those soon.
As for the PCB, we made a change log document and have since corrected 90% of the items.
We are commissioning an outside engineering firm to double-check everything They will review the schematic and layout to make sure we donāt miss anything and will give us an outside opinion.
You can view the change log here:
Pocket P.C. Rev 2.1 Change Log
As for software, we will be contracting an outside embedded development firm to upstream everything from U-boot specific changes including Device Tree, Linux Kernel changes including Device Tree, Buildroot configuration and an Armbian build configuration.
This means that we will be supporting Armbian in addition to Debian.
The above is a summary of what will be in our next update. Now that the testing phase is over, I can devote time to writing our newsletter and blog updates.
If anyone has emailed us in the past few weeks, we will respond to all your questions soon, I apologize for falling behind on customer service but please know that we are dedicating all our resources to making an excellent product without blemishes or flaws.
Coolļ¼How did you do that? Can you share it?
Preorder yours at 
