That will be most welcome. Right now I am trying to get a number of things synchronized. We have a new kernel to become stable which will hopefully solve the suspend/resume and Wifi issues. Then there is a virtual keyboard just brought to my attention. Finally, there is some code I use that needs to be open sourced by the owners (which they fully intend to do).
And then there are non-Android commitments I have... Sean Davide wrote: > If you like, I can help you with code > or some other stuff if you wish ... > > > 2008/11/26 Sean McNeil <[EMAIL PROTECTED]>: > >> Davide, >> >> There are a few fundamental things I'd like to pass along: >> >> First, in order to build Android for the Freerunner it takes very little >> effort and the goal is to be able to do so without any modification to >> the sources. >> >> Second, there are two components that I use which are not owned by me >> but are being open sourced. The ALSA library was just recently released >> and I use a multiplexed GSM modem which we are trying to complete GPRS >> support with. This will be open sourced when completed as well. >> >> Third, work that I have done needs cleanup to get past Googles >> high-grade review process. I have other things to do, so I honestly have >> no idea when I'll get around to that. >> >> Fourth, we are working to have everything necessary in the OM kernel to >> support Android. This is almost done. >> >> Beyond that, I have a few small scripts that I could provide that will >> copy over the tree to an NFS mountable directory and create a jffs2 image. >> >> So, as you can see our ultimate goal is to do just as you suggest. >> >> Sean >> >> Davide wrote: >> >>> Very thanks for your very complete and clear explanation. >>> >>> To install android on freerunner it was very nice to >>> have a setup script like for installing debian >>> on freerunner. >>> >>> A script that check all and do all the necessary steps >>> (patch, compile, deploy, ecc) >>> >>> Why not create an open source project for building such >>> script? >>> >>> It is possible to avoid the legal issues of previous >>> portings? Or the legal issues will block any other >>> way? >>> >>> 2008/11/25 Jim Ancona <[EMAIL PROTECTED]>: >>> >>> >>>> On Nov 24, 5:00 pm, Davide <[EMAIL PROTECTED]> wrote: >>>> >>>> >>>>> Anyone can help me? >>>>> >>>>> >>>> Three people that I know of are working (apparently independently) on >>>> Freerunner/Neo ports. (I'm not one of them!) I believe all three have >>>> them have posted on this list at one time or another. >>>> >>>> One of the three, Sean McNeil, has released a couple of sample images >>>> here: http://wiki.openmoko.org/wiki/User:Seanmcneil3 >>>> He removed his latest image because of licensing concerns with MP3 and >>>> video codecs. Some of his patches have been submitted to Google. The >>>> kernel that he has posted does not resume from suspend, and most of >>>> the peripherals (Wifi, GPS, Bluetooth) either don't work or are very >>>> flaky. I have a copy of his image, and it the phone can make calls >>>> using Android, but can't receive them because there's no "answer" >>>> button. >>>> >>>> A second port is being worked on by Brian Code, who has a email >>>> address at Koolu, a Freerunner distributor which has announced a >>>> forthcoming Android port (see http://tinyurl.com/5pnkku). I haven't >>>> seen anything from him since an initial flurry of activity right after >>>> Google released the Android source. Koolu has set up an Android on >>>> Freerunner forum at http://forum.koolu.org/viewforum.php?f=10, but >>>> it's been pretty quiet. >>>> >>>> The third developer working on Android for Openmoko phones is Ben >>>> Leslie (http://benno.id.au/blog/). He says he has an image running on >>>> his Neo (the predecessor to the Freerunner), but I haven't seen >>>> anything from him since he left on vacation three weeks ago. >>>> >>>> Supposedly, Android support has been integrated into the next release >>>> of the Freerunner kernel, and the Openmoko developers are putting most >>>> of their effort into making the low-level functionality (suspend/ >>>> resume, GSM modem issues, etc.) more reliable, which should benefit >>>> all distributions in the future. >>>> >>>> Right now, it's a bit frustrating because there is no visibility into >>>> the state of the various ports. There's no source repository or other >>>> way for anyone to build their own image or contribute to the effort. >>>> Of course it's still just a month since the source was released, so >>>> I'm still cautiously optimistic that a usable port for the Freerunner >>>> will come out, probably from Koolu. They're claiming a beta will be >>>> available in December, so we should know more soon. >>>> >>>> Jim >>>> >>>> >>>> >> > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
