A brief How to can be found here :-
http://labs.embinux.org/android-porting-on-beagle.html

You may also browse the kernel modifications at :-
http://labs.embinux.org/git

We will come up with more updates very soon..
Enjoy Androing.

Regards,

--
Rupesh Gujare
http://embinux.com

Please find below video showing Android on beagle board. It demonstrates
navigation on Android, sample applications, and browser.

http://in.youtube.com/watch?v=nADn_vNVEKw

Regards,

--
Rupesh Gujare
http://embinux.com

archan.paul wrote:
> Anil,
>
> Android on Beagle supports display. You can connect display through
> DVI-D/HDMI interface.
>
> You can refer to - http://dkc1.digikey.com/us/mkt/beagleboard.html
>
> - Archan
>
> On Dec 17, 8:41 pm, "Anil Sasidharan" <anil...@gmail.com> wrote:
>  
>>          Does Android on Beagle support display and touch? This
>> question is based on the fact that there is no hardware support for
>> display and touch on Beagle board. I'm more curious to know the exact
>> external hardware modules used in this regard.
>>
>>
>> On Wed, Dec 17, 2008 at 8:13 PM, Rupesh Gujare

On Dec 17, 11:43 pm, Rupesh Gujare <rupesh.guj...@embinux.com> wrote:
> Hi,
>    We are releasing source code for Android port on beagle board. So far
> we have tested input device(keyboard/mouse), network(over USB) and sound
> (*.mp3).
>

> Hi,Rupesh,
> i don't have USB Mini-A connector, so i connected USB-OTG 4thpin(id) with
> ground on the board and using Mini-B connector,but it didn't work as host
> what is wrong in my connection.
>
> Regards
> Rao
>
> On Sun, Dec 21, 2008 at 12:02 AM, Rupesh Gujare

>
> >  Rao,
> >       With which USB connector you are connecting to beagle board. You need
> > to connect with USB Mini-A connector to beagle board, for it to work as a
> > host.
>
> > Regards,
>
> > --
> > Rupesh Gujare
>
> > padmarao edapalapati wrote:
>
> > Hi Rupesh,
> > Thanks for your help. I able to get the android command prompt as well as
> > GUI.
> > But when i am trying to connect my USB otg to self powered hub(only
> > keyboard connected to hub),
> > not getting power to keyboard.
> > how can i know whether OTG is working as host or not  ?
> > Is there any code modification is necessary to make it as host ?
>
> > Thanks & Regards,
> > Rao
>

>
> >> Rao,
> >>    Is "$mkimage" command available on your development machine? If it is
> >> there, then you should get uImage in arch/arm/boot/
> >> I dont think if you use "zImage" or "Image" will work with u-boot.
>
> >> Regards,
>
> >> --

>
> >>  padmarao edapalapati wrote:
>
> >> Hi,
>
> >> Thanks Rupesh.
> >> we followed the sequence provided by you. In the first step of compiling
> >> the linux omap kernel,
> >> its giving uImage build ready message but we are unable to get the uImage
> >> in arch/arm/boot folder.
> >> we got  zImage and Image.
> >> Do we need to rename the zImage to uImage ?
> >> if so u-boot will recognize the format ?
>
> >> Thanks & Regards
> >> Rao
>
> >> On Thu, Dec 18, 2008 at 2:28 PM, Syed Mohammed, Khasim <

> >> sm.kha...@gmail.com> wrote:
>
> >>> This is really great effort and thanks a lot for releasing the sources.
>
> >>> Regards,
> >>> Khasim
>
> >>> On Thu, Dec 18, 2008 at 11:54 AM, Rupesh Gujare

> >>> <rupesh.guj...@embinux.com> wrote:
>
> >>> > Hi All,
>
> >>> > Please find below video showing Android on beagle board. It
> >>> demonstrates
> >>> > navigation on Android, sample applications, and browser.
>
> >>> >http://in.youtube.com/watch?v=nADn_vNVEKw
>
> >>> > Regards,
>
> >>> > --
> >>> > Rupesh Gujare
> >>> >http://embinux.com
>
> >>> > archan.paul wrote:
> >>> >> Anil,
>
> >>> >> Android on Beagle supports display. You can connect display through
> >>> >> DVI-D/HDMI interface.
>

On Dec 17, 7:43 am, Rupesh Gujare <rupesh.guj...@embinux.com> wrote:
> Hi,
>    We are releasing source code for Android port on beagle board. So far
> we have tested input device(keyboard/mouse), network(over USB) and sound
> (*.mp3).
>

Howard wrote:
> I tried the HDMI on my TV and it didn't work, but it does work well on
> my both LCD computer monitors I tried.

Take care - Even though the BeagleBoard uses a HDMI connector (for space
saving purposes), the output is really DVI-D and not HDMI... You can
therefore not expect it to work with your TV HDMI input...

Best regards
  Søren

It will, however, work with just about every HDTV if properly  
configured for that TV.  The code used in most of the popular demos  
today does not utilize the proper pixel clock for standard 720P.

There is no audio connection, which is a reason it is not real HDMI.

http://labs.embinux.org/wiki/index.php/Android_Porting_Guide_to_Beagle_Board

Regards,

-- Rupesh Gujare http://embinux.com

--

Rupesh Gujare
http://embinux.com

On Jan 8, 4:16 am, Rupesh Gujare <rupesh.guj...@embinux.com> wrote:
> Hi,
>   We are upgrading our source code with latest Android cupcake release.
> Release Features:-
> 1. Android kernel is upgraded to 2.6.27, with new functionalities.
> 2. Fixed broken ALSA sound for Android build.
>
> We have moved our "Android Porting Guide to Beagle Board" page to new
> wiki page for easy maintenance and future release modifications.
>

I'm currently hunting this in Angstrom.  Any hints?

--
Justin Love

Creative Electronics & Software
650 Sundown Road
South Elgin, IL 60177

Phone (847) 695-0023
FAX   (847) 695-0483

On Jan 8, 3:42 pm, Howard M Harte <hhar...@gmail.com> wrote:
> Hello Rupesh,
>
> I tried following your new Wiki page, and it works well.  One  
> correction: I had to chmod -R 777 the filesystem to get it to work.  
> After that, it works well. I was able to get the Amazon MP3 app  
> (pulled from a G1) to work, and even could preview the songs.  So  
> sound is working.
>
> I was not able to get your patches for the kernel, remote disconnected  
> unexpectedly, or some message like that, but I just used the kernel  
> you posted in December, and it seems to work ok.

>
> Most other proprietary apps like Market will not run, but I guess that  
> is some sort of signing issue.
>
> Thanks for the great work.
>
> -Howard
>

On Jan 8, 11:24 pm, Rupesh Gujare <rupesh.guj...@embinux.com> wrote:
> Hi All,
>   We have fixed git issue, It was a problem with our git server. Now it
> should work fine, please let me know if you are still facing any problems.
>
> Regards,
>
> --

>
> Howard M Harte wrote:
> > The GIT remote update problem was due to my firewall, I guess.  I  
> > changed git:// to http:// and it works fine now.
>
> > I hacked some of the system/bluedroid code in Android, and got  
> > Bluetooth to sort of work, but eventually the kernel panics, either  
> > because of the USB host driver or the btusb driver.  Given the  
> > problems I've had with USB memory stick and USB Ethernet on Beagle,  
> > I'd guess the usb host driver is the problem.
>
> > -Howard
>

> I'm having some problems with the patches from the new site.   I cut-
> paste the text into patch files.  I think it would be helpful if you
> can provide a link to them as a tar image or individually.
>
> 1. The libC patch fails to add the "arch-arm/bionic/ffs.S \" entry to
> Android.mk.  I did this one manually.
>
>  

> 2. The alsa_sound patch fails:
>
> jayw@kittredge:~/alsa_sound$ patch -p1 < /home/jayw/Android/
> beagleboard/Patches/Alsa_sound.patch
> patching file AudioHardwareALSA.cpp
> Hunk #2 FAILED at 187.
> Hunk #3 FAILED at 218.
> patch: **** malformed patch at line 107: //
> ----------------------------------------------------------------------------
>
> I haven't tried to figure this one out yet.  I think I will wait to
> hear you response.
>  

> Here are some suggestions for the build instructions:
>
> 1. I think the instructions would flow better if you move alsa_sound
> path to the ALSA Support section.  Currently, you have the LibC patch
> following the ALSA Support.
>  

> 2. The initrc.patch is broken into multiple blocks.  Kinda of confused
> me at first.
>  
> 3. The qwerty.kl.patch is also broken into multiple blocks.
>  

> 4.  In the instructions for applying the patches.  I would be helpful
> if you could specify the root directory for which to execute the patch
> command.
>  

> Once again, thanks for all the hardware work you put into this
> document.    If you update them, I'm more than happy to run through
> them from beginning to end to help you iron out the details.
>
> Cheers,
> Jay
>
>
>
> On Jan 12, 3:04 pm, JayBird <jayje...@gmail.com> wrote:
>  
>> Hi Rupesh,
>>
>> I'm not an expert with git, but I think the
>> omap3_beagle_android_defconfig file is missing.  I did the following:
>>
>>     $git clone git://source.mvista.com/git/linux-omap-2.6.git
>>     $cd linux-omap-2.6
>>     $git remote add labs.embinux git://labs.embinux.org/linux-omap-2.6
>>     $git remote update
>>     $git checkout -b beagle.android-2.6.27 labs.embinux/android-2.6.27
>>     $make ARCH=arm omap3_beagle_android_defconfig
>>
>> Afterwards, I get the following error
>>
>> ***
>> *** Can't find default configuration "arch/arm/configs/
>> omap3_beagle_android_defconfig"!
>> ***
>>
>>    

On Jan 13, 8:38 am, Rupesh Gujare <rupesh.guj...@embinux.com> wrote:
> Jay,

Cheers,
Jay


On Jan 13, 8:38 am, Rupesh Gujare <rupesh.guj...@embinux.com> wrote:

On Jan 14, 3:52 am, Rupesh Gujare <rupesh.guj...@embinux.com> wrote:
> JayBird wrote:
> > Hi Rupesh,
>
> > Thanks for response.  I will try running through the instructions
> > again:)
>
> > Note, I was going to try to compile using the 2.6.27 Kernel.  Did I
> > miss a step, there is no config file for
>
> > omap3_beagle_android_defconfig
>
> > in branch "beagle.android-2.6.27" (See previous post for steps I
> > executed).
>
> No you didn't missed any step, "omap3_beagle_android_defconfig" file was
> missing, I have corrected it.
>
> Regards,
>

mount -t vfat /dev/mmcblk0p1 /sdcard
$setprop EXTERNAL_STORAGE_STATE mounted
$am broadcast -a android.intent.action.MEDIA_MOUNTED --ez read-only false -d  file:///sdcard

> Jay,JayBird wrote:
> > Hi Rupesh,
>
> > I did a repo sync on my cupcake branch, and I'm still have problems
> > with the ALSA.  Could you be more specific on what I need to do to
> > sync up my Android environment?
>
> We tested ALSA patches on master branch and not on cupcake, as it is a
> development branch and stable features of cupcake are merged regularly
> with master.
>
> ie.working with a branch obtained by:-
> $ repo init -u git://android.git.kernel.org/platform/manifest.git
> $ repo sync
>

> $ repo init -u git://android.git.kernel.org/platform/manifest.git -b cupcake
> $ repo sync
>
> Are you facing problems with master branch ? We have compiled build
> successfully with ALSA patches on master branch.
> You can try cleaning build and recompiling or take fresh build and try
> again, we have observed that sometimes if you repo sync precompiled
> build, then it do not get compiled unless you clean it.
>
> $make clobber  -> cleans build
> $repo sync
> $make
>
> Regards,
>
> --

 
kozak wrote:
> Hi all,
> I have a couple of doubts on adding the patch for BB to the android
> baseline.
>
> 1. I have downloaded the latest baseline from the android git
> following the instructions in the page
> http://source.android.com/download.
> can anybody tell me which is the version of kernel that gets
> downloaded after this?
>  

> From some of the posts I guess it might be 2.6.27. I would like to
> confirm on that so that I can take the appropriate branch from the
> patch as well.
>
> 2. Is there a file in the kernel source that stores the version
> number? Can someone tell me which would that file be in case it
> exists?
>
>  

On 1月15日, 上午5時23分, Howard M Harte <hhar...@gmail.com> wrote:
> If you press return at the serial console, do you get a # prompt?  You  
> should, and if so, you can take a look at the log using the 'logcat'  
> utility. Also do a 'ps' and see that zygote and a bunch of Android  
> processes are running.  Also make sure your display is working  
> properly.  You can do 'cat somefile > /dev/fb0' and you should see  
> some junk on the display.
>
> I ran into a similar problem with Android on a different platform.  
> Android was running properly, but the LCD was not initialized properly  
> by the bootloader.
>
> -Howard
>

>
> eleganc...@gmail.com wrote:
> > Hi Rupesh,
>
> > i follow the Android Porting Guide to Beagle Board (checkout the
> > 2.6.27 kernel source) to port Android on my Beagle Board.
>
> > After all the things are done, I copy the uImage and root file system
> > to different separations (fat32/ext3) in a SD card.
> > Then use this SD card to boot the Beagle Board. Following is my boot
> > arguments:
>
> > console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2 video=omapfb:mode:
> > 1024x768@60 init=/init rootfstype=ext3 rw rootdelay=1 nohz=off
>
> Try out with
>
> console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2 video=omapfb:mode:

>
> > mmcinit; fatload mmc 0 0x80300000 uImage; bootm 0x80300000
>
> > The teraterm console will display much information, but the LCD can
> > not show anything which said that it is it is out of the range.
> > (Neither Android booting screen nor Android robot are shown)
>
> > It seems that the "video=omapfb:mode:1024x768@60" does not work.
> > (After booting, I can access the file system via teraterm console.)
>
> We have tested it with video=omapfb:mode:1280x720@50. It is working for us.
> I am not expert to comment about whether "video=omapfb:mode:1024x768@60"
> is supported in our code base. But i definitely find support for this
> mode present. Please check.
>

> > (When typing the booting arguments, the beagleboard.org LOGO is shown
> > correctly on LCD)
>
> > BTW, I found a Linux OMAP repository that adds a list of common video
> > modes and allows one to be selected with video=omapfb:mode:name on the
> > command line.

> > The source code on embinux git seems not add this function?
> > Hope this will help you.
>
> > Sincerely,
> > Ken
>
> Regards,
>
> --

On Mar 8, 7:36 am, ILKYOUNG KWOUN <hl1...@gmail.com> wrote:
> Hello, Rupesh,
>
> I'm a newbie and I have been watching this thread for a while. I gave a try
> to build the image by myself last night.
>
> First, I downloaded the binaries you posted in the wiki and saw the android
> working on my BB. Great!
> Next, I followed instruction in the wiki to compile the image on my
> computer.
> Until to the step '8-Compile build', it was fine. I got the following
> messages and prompt back.
> ===================================================================
> Target system fs image:

> Install system fs image: out/target/product/generic/system.img
> Target ram disk: out/target/product/generic/ramdisk.img
> Target userdata fs image: out/target/product/generic/userdata.img

>
> ===================================================================
>
> However, I found that I don't have anything in the directory
> 'out/target/product/generic/data'.
> ===================================================================

> ls -l
> Total 52500
> -rw-r--r--  1 hl1oap hl1oap        7 2009-03-08 10:37 android-info.txt
> -rw-r--r--  1 hl1oap hl1oap       75 2009-03-08 08:50 clean_steps.mk
> drwxr-xr-x  2 hl1oap hl1oap     4096 2009-03-08 09:03 data
> drwxr-xr-x 12 hl1oap hl1oap     4096 2009-03-08 10:37 obj
> -rw-r--r--  1 hl1oap hl1oap   145383 2009-03-08 10:37 ramdisk.img
> drwxr-xr-x  8 hl1oap hl1oap     4096 2009-03-08 10:37 root
> drwxr-xr-x  4 hl1oap hl1oap     4096 2009-03-08 09:39 symbols
> drwxr-xr-x 12 hl1oap hl1oap     4096 2009-03-08 10:37 system
> -rw-------  1 hl1oap hl1oap 53518080 2009-03-08 10:37 system.img
> -rw-------  1 hl1oap hl1oap     2112 2009-03-08 10:37 userdata.img

> ls -l data
> Total 0

hi,

I downloaded the binaries posted by you and could get the android up
on beagleboard.
thanks for making it so simple..

now i wanted to run simple C program on the command prompt, i used
arm-none-linux-gnueabi-gcc toolchain.
But i could run the .out only with static linking .
With dyanmic linking, it give out the error "./a.out: not found".

Could you help me on how to use dynamic linking and still be able to
run it on command prompt.

Regards,
Sonal

sonal wrote:
> hi,
>
> I downloaded the binaries posted by you and could get the android up
> on beagleboard.
> thanks for making it so simple..
>
> now i wanted to run simple C program on the command prompt, i used
> arm-none-linux-gnueabi-gcc toolchain.
> But i could run the .out only with static linking .
> With dyanmic linking, it give out the error "./a.out: not found".

the android system comes with it's own libc and linker, if you do not
use the android toolchain then you also need to provide your own linker
and libc.

Regards,

--
Rupesh Gujare
http://embinux.com

On Apr 27, 6:43 am, Rupesh Gujare <rupesh.guj...@embinux.com> wrote:
> Hi,
>   You can sync android-beagle build with all patches.
> I have updated instructions, please check:-
>
> http://labs.embinux.org/index.php/Android_Porting_Guide_to_Beagle_Board
>
> Regards,
>
> --