Sorry, I wasn't very clear. It's not currently possible to run Android "as is" on a FreeRunner.
I meant that it would be nice to be able to download the official Android source code on a PC (and nothing else beyond the tools that are normally needed to compile Android), and to be able to compile a full configuration that would run on the FreeRunner and handle the concerns that were expressed. I believe that this would be a nicer experience for people who want to experiment with Android on FreeRunner than having to work with multiple separate open-source projects. In order to get there, though, someone has to make all the relevant changes in the official Android source code. JBQ On Tue, Nov 25, 2008 at 2:05 PM, Davide <[EMAIL PROTECTED]> wrote: > > I am very new to android, do you mean that is possible to > download and run make android on a freerunner? > > I have downloaded the source code, there are any gb > of code. > > It is possible to make on pc with target a freerunner > system? > > I think isn't easy to make on freerunner direct, there > is less space and tools. > > > > 2008/11/25 Jean-Baptiste Queru <[EMAIL PROTECTED]>: >> >> I don't see any fundamental reason why building FreeRunner images >> couldn't be done from within the existing Android build system, and I >> believe that the existing configuration system should be able to >> exclude parts that might be undesirable (or could be reasonably easily >> extended to add that ability). There might not be a need to create a >> separate project for this. >> >> JBQ >> >> On Tue, Nov 25, 2008 at 11:50 AM, Davide <[EMAIL PROTECTED]> 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 -~----------~----~----~----~------~----~------~--~---