Re: topic for next community update [was Community Update Wed Feb 13 2008]
For apps, personally (ie, this is just my opinion) I think its fine if we target providing solid very minmal apps initially, again we can point at the memory on the device (it is stacked with memory), the standard X and libs provided, and its upgradability with package granularity to convincingly (well it convinces me :-)) say more apps are coming. It convinces me too, and I'm participating in OpenMoko solely for the reason that I want to push out some end-user apps, developed new and fresh, for the platform. When it becomes more widely available, that is, I will be quite happy targetting it as a major platform for my music apps .. as it stands right now, its very rewarding to be doing daily builds that can run on both EEE PC and OpenMoko with very little fuss, and it sure is going to be interesting keeping this party going for the next few months .. ; -- Jay Vaughan ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: topic for next community update [was Community Update Wed Feb 13 2008]
It's always been option i. Hence the release of GTA01. Many apps on that are still not polished. It'll be many months after the release of the Freerunner before the phones are ready for basic end users. -Steven On Thu, Feb 14, 2008 at 2:10 PM, JW [EMAIL PROTECTED] wrote: 2) What is OpenMoko's plan to release FreeRunner i) release when hardware and kernel are solid and before application software is polished. Community helps to polish software prior to full launch to basic end users ii) release when both hardware and software are polished. Will take a little longer but will impress journalists more... ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Community Update Wed Feb 13 2008
Hi everyone, This is actually a recap of last week in the engineering department. I was away at SCALE and am busy catching up. We received our first batch of 10 fully assembled GTA02 A5 boards. There are still some issues with the manufacturing test software that needs to be fixed before we start manufacturing. John got some Processing apps to run on the phone. Performance could be improved with a good Java JIT and better glamo OpenGL support. Wolfgang started the wiki page http://wiki.openmoko.org/wiki/Prototypes to track hardware issues with any non-release hardware we are using internally or sending to people. You can track some progress here. Allen found a GSM power leak in suspend mode. Matt and Allen are working to get this resolved. Graeme got Qtopia to build via OE, and was able to make phone calls on a GTA01 using Qtopia. The bottom line for A5 is that while we have not found a proven A5 hardware bug yet, we ran into a number of uncertainties. Our highest priorities now are to 1. prove that suspend/resume and charging works 2. prove that we can fix hardware quality issues (broken bluetooth, GPS, receiver) 3. improve production testing software (microSD, suspend/resume) We have added a full-time wiki editor. She has been publishing technical books for many years, and we look forward to improved organizing and appearance of all the great content on the wiki. That's all for now. Regards, Michael ___ OpenMoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
