Android port for beagle(OMAP3530)- Code Released

[Rupesh Gujare]

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).

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

[Rupesh Gujare]

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.
>
> 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

[Syed Mohammed, Khasim]

This is really great effort and thanks a lot for releasing the sources.

Regards,
Khasim

[padmarao edapalapati]

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

[Rupesh Gujare]

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,

-- 
Rupesh Gujare
http://embinux.com

[rainman747]

Thank you for all your sweaty-efforts.
it will be much appreciated if you upload downloadable-image stuff
for newbi.

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).
>

> 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

[John (USP)]

Make sure mkimage is in your path and then do this

 

make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage

 

Regards,

[Tamer S. Mohamed]

mkimage is in the tools folder of the uboot git.

 

git clone git://www.sakoman.net/git/u-boot-omap3.git

cd u-boot-omap3

git checkout --track -b omap3-dev origin/omap3-dev

 

copied from

http://elinux.org/BeagleBoard#U-Boot

 

 

---

[Rupesh Gujare]

Hi all,
   You can download binaries (kernel uImage and Android RFS) from following link:-
http://www.embinux.com/download_beagle.php

Regards,

-- 
Rupesh Gujare
http://embinux.com

[padmarao edapalapati]

Thanks for u r help

 i got the uImage

 

Regards

rao

[padmarao edapalapati]

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

On Thu, Dec 18, 2008 at 7:02 PM, Rupesh Gujare <rupesh...@embinux.com> wrote:

[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]

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

[Shivdas]

Hi Padmarao,

You have followed right steps. But could you please
verify using multimeter, is GND and pin4 is really shorted?
also make sure to select USB host mode while "make menuconfig".

Regards,
Shivdas Gujare


On Dec 21, 10:10 am, "padmarao edapalapati" <padmara...@gmail.com>
wrote:

> 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

> <rupesh.guj...@embinux.com>wrote:

>
> > 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
>

> > On Thu, Dec 18, 2008 at 7:02 PM, Rupesh Gujare <rupesh.guj...@embinux.com>wrote:
>
> >> 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,
>
> >> --

> >> Rupesh Gujarehttp://embinux.com

> >>> >> You can refer to -http://dkc1.digikey.com/us/mkt/beagleboard.html

[haife...@gmail.com]

Thanks a lot! But I cannot compile alsa_sound, which reports a lot of
errors.

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).
>

> 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

[hha...@gmail.com]

I had the same problem using the Android Cupcake branch. I just
didn't add the audio support, and it builds and runs mostly fine. The
only issues I'm seeing are the Soft Keyboard introduced in Cupcake
crashing (although it did come up on the screen one time.) Also,
since I'm using the dual-partition SD card for the uImage and Android
Filesystem, I cannot use the SD card for Android storage. I wanted to
try downloading some apps, but they require the SD card to be
available. I tried using a USB Memory Stick for the Android
filesystem, and it works; however, when using it in conjunction with
my USB Ethernet Adapter (AirLink 101) the simultaneous use of Ethernet
and USB Memory stick cause the kernel to crash. I saw a bug was filed
on this on the Issue Tracker:

http://code.google.com/p/beagleboard/issues/detail?id=31&can=1

Unfortunately, there is no root-cause found for it, and it looks like
there is no plan to fix this problem. Using a USB 1.1 hub as a
workaround is not a great solution since 1.1 hubs are difficult to
find these days, and slow down the performance.

I also tried using using MTD partitions to store the Android
Filesystem, but Android's "flash_image" utility fails, and directly
mounting the MTD partition and writing to it seems unstable (kernel
crashes frequently.) I will try the latest version of Angstrom and
see if the MTD partitions work there.

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.

It will be nice when the Rev C boards with working EHCI controller are
available. Then it will be possible to use the EHCI controller for
USB devices, and use the OTG port for USB Gadget and Android Debug
Bridge (ADB.)

The BeagleBoard will make a nice Android set-top box if some of these
issues can be resolved.

-Howard

On Dec 31 2008, 2:39 pm, "haifeng....@gmail.com"

[Søren Steen Christensen]

Hi Howard,

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

[Jason Kridner]

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.

[Howard M Harte]

Thanks for the info. At this point, I'm more concerned with reliable
USB and getting the MTD partitions working.

I'd also like to get the second UART and SD interface on the expansion
connector working. I have a 1.8v SD device, so it should just be a
matter of wiring it up, and software.

Has anyone used the SD interface on the expansion connector?

The BeagleBoard is really a neat little board.

-Howard


On Jan 6, 2009, at 5:08 PM, Jason Kridner <jkri...@beagleboard.org>
wrote:

[Andrew Diller]

Hello:

Just put this on a BB- should I expect USB Ethernet to work? Or do I
have to build in support and build my own kernel? I'm using the pre-
build version that you have kindly supplied. I'm using a linksys USB
Ethernet dongle.

I read that Android doesn't know about USB, so how is working on the
BB ?

-andy

On Dec 18 2008, 1:24 am, Rupesh Gujare <rupesh.guj...@embinux.com>
wrote:

[Rupesh Gujare]

Hi,

  

Hello:

Just put this on a BB- should I expect USB Ethernet to work? Or do I
have to build in support and build my own kernel? I'm using the pre-
build version that you have kindly supplied. I'm using a linksys USB
Ethernet dongle.

  

You are welcome to integrate it with BB. Please post your efforts and progress.
 Indeed USB ethernet work in our prebuild version. We have tested it. You don't need to build support in your kernel.

I read that Android doesn't know about USB, so how is working on the
BB ?

  

Your information is incorrect. Android have full support for USB

Regards,

-- 
Rupesh Gujare
http://embinux.com

[Rupesh Gujare]

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.

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

You can browse kernel source at:-
http://labs.embinux.org/git/

We have tested input device (keyboard,mouse), network and sound(*.mp3)
with this release, all is working fine.

I will like to thanks Sean for sharing a patch that fixed ALSA issue.

[Rupesh Gujare]

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

Regards,

[JayBird]

Hi Rupesh,

I was just looking over the "Android Porting Guide to Beagle Board"
and I think there my be a couple of typo errors

1. In the "Ownership" section, the command

$ chmod -R 666 /data /system

will override the permission you set in the previous step

$chmod -R 777 /system/use/keychar


Did you mean to reverse those two steps?


2. I think there is a space missing in the TLS Patch:

Should the line "/* get the TLS */" be " /* get the TLS */"?

Thanks for the all the hard work put into creating this document.

Cheers,
Jay

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.
>

> http://labs.embinux.org/wiki/index.php/Android_Porting_Guide_to_Beagl...
>
> You can browse kernel source at:-http://labs.embinux.org/git/

[Rupesh Gujare]

Jay,
   Thanks for pointing out, We have updated wiki page.

Regards,

-- 
Rupesh Gujare
http://embinux.com

 

[JustinLove]

Rupesh Gujare wrote:
> 2. Fixed broken ALSA sound for Android build.

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

[Howard M Harte]

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

[hha...@gmail.com]

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.

Actually the git failure is as follows:
$ git remote update
Updating labs.embinux
fatal: The remote end hung up unexpectedly
fetch labs.embinux: command returned error: 128

-Howard

>
> 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, 2009, at 10:13 AM, Rupesh Gujare <rupesh.guj...@embinux.com>  

> >>> Rupesh Gujarehttp://embinux.com- Hide quoted text -
>
> - Show quoted text -

[Shivdas Gujare]

On Thu, Jan 8, 2009 at 3:09 AM, Andrew Diller <dil...@gmail.com> wrote:
>
> Hello:
>
> Just put this on a BB- should I expect USB Ethernet to work? Or do I
> have to build in support and build my own kernel? I'm using the pre-
> build version that you have kindly supplied. I'm using a linksys USB
> Ethernet dongle.

No, your USB Ethernet adapter will not work with demo image, we have
tested it with
"Davicom DM9601 based USB Ethernet adapter", hence you needs to build
your own image with linksys driver support.

>
> I read that Android doesn't know about USB, so how is working on the
> BB ?

I believe, Android doesn't needs to know about USB if your kernel
and platform has support for USB.

Regards,
Shivdas Gujare

[Howard M Harte]

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

[Rupesh Gujare]

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,

-- 
Rupesh Gujare
http://embinux.com

[JayBird]

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"!
***


Did I miss a "git" step or something?


--- Jay

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,
>
> --

> Rupesh Gujarehttp://embinux.com

>
> 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
>

> >>>>>> Rupesh Gujarehttp://embinux.com-Hide quoted text -

[JayBird]

Hi Rupesh,

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

> > >>>>>> Rupesh Gujarehttp://embinux.com-Hidequoted text -