<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi,<div class="">this time I have some tiny pieces of good news...</div><div class=""><br class=""></div><div class="">1. The first 8 GTA04A5 boards are finished (foto) and finally ready</div><div class="">to be shipped. It did take much longer to fix add all the little</div><div class="">bits and pieces until everything is in place.</div><div class=""><br class=""></div><div class="">One thing was to have the NAND image finished and tested.</div><div class="">It should at least reliably boot with and without µSD installed,</div><div class="">it should load the correct device tree blob and finally the</div><div class="">kernel should be able to mount the NAND as rootfs.</div><div class=""><br class=""></div><div class="">And the rootfs in NAND should at least be some demo when booted.</div><div class="">Please do not expect too much from the NAND rootfs. It is not deeply</div><div class="">tested and configured. Don't expect a fully polished phone GUI...</div><div class=""><br class=""></div><div class="">But we as a community can contribute to improve this GUI if the</div><div class="">basics of the device are working. E.g. by a new Replicant 4.2</div><div class="">image or making Replicant 6 bootable.</div><div class=""><br class=""></div><div class="">Another thing was to make the stickers which indicate serial</div><div class="">number, IMEI, WLAN-MAC address etc. This meant booting and reading</div><div class="">out this information from each board and store it in a database.</div><div class="">And then really print the stickers and put them inside and on the</div><div class="">boxes.</div><div class=""><br class=""></div><div class="">So the next step I will do is to contact the first lucky 8 who have</div><div class="">preordered. To check if their address, contact data etc. is still ok.</div><div class=""><br class=""></div><div class="">Then I can really ship...</div><div class=""><br class=""></div><div class="">3 more GTA04A5 are on the testbench and 3 older GTA04A4 - but the latter</div><div class="">have minor issues. One has USB charging but no USB data. One does</div><div class="">boot but the kernel hangs. And the third one is almost fine except</div><div class="">that the WiFi/Bluetooth chip seems to be broken.</div><div class=""><br class=""></div><div class="">2. Regarding the remaining boards which need some repair, everything</div><div class="">is still stuck in the chewy negotiations about the production</div><div class="">failures. It is not yet completely agreed how much we have to</div><div class="">pay for not produced devices or how much we get back. Therefore,</div><div class="">I do not get the excess components for repair and also no help by</div><div class="">their machines (some repair steps are easier to do on their rework</div><div class="">place than my own).</div><div class=""><br class=""></div><div class="">So repairs are still blocked.</div><div class=""><br class=""></div><div class="">3. I have developed a new idea giving some small piece of hope to reduce</div><div class="">the total loss of money and still get enough devices. The idea is that</div><div class="">if we assume the claim that the production problem is because of</div><div class="">the components we have provided, we just throw those away. And ask</div><div class="">production to buy new replacements which exactly match. Especially</div><div class="">for the OpenPandora type of memory chip. This should solve the</div><div class="">production problem and it should run at the same yield as the</div><div class="">OpenPandora production.</div><div class=""><br class=""></div><div class="">This would have one visible effect on the GTA04A5: we would no longer</div><div class="">have 1GB RAM and 512MB NAND but 512MB RAM and 1GB NAND. This is</div><div class="">not really nice since 1GB is a major feature, but we must do it</div><div class="">the same way as the OpenPandora to get to the high production yield.</div><div class=""><br class=""></div><div class="">On the u-boot/kernel side this raises no problems, since we already</div><div class="">have multiple variants and some things like memory size are determined</div><div class="">automatically. So it is only visible in user-space RAM+NAND capacity.</div><div class=""><br class=""></div><div class="">I do not yet have any feedback on this proposal, so it might</div><div class="">be declined. But if it works out, the total financial loss can be</div><div class="">reduced very significantly. And all preorders could be easily</div><div class="">fulfilled, leaving even some more devices for newly interested</div><div class="">community members.</div><div class=""><br class=""></div><div class="">One snag must also be mentioned: I have no idea about the timing</div><div class="">of this approach. It might need several months to get the</div><div class="">components... Which was the reason to buy them ourselves in</div><div class="">advance.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">So there is good news about shipping the first boards. And let's say,</div><div class="">some atoms of hope that we can rescue the full project.</div><div class=""><br class=""></div><div class="">BR,</div><div class="">Nikolaus</div><div class=""><br class=""></div><div class=""><img apple-inline="yes" id="A9D42F8F-7B7F-4949-A028-B385F44112D9" height="303" width="640" apple-width="yes" apple-height="yes" src="cid:5EC5B534-3C30-4359-A2DC-2A0B0948385E@Speedport_W_700V" class=""></div><div class=""><br class=""></div><div class=""><img apple-inline="yes" id="D46859CF-3C52-4118-8FC6-A6A6DBDBF100" height="289" width="640" apple-width="yes" apple-height="yes" src="cid:49339912-A16C-434C-B634-0BE1008C574A@Speedport_W_700V" class=""></div><div class=""><br class=""></div></body></html>