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
Make sure mkimage is in your path and then do this
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- uImage
Regards,
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
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.
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 ?
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
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).
Hey Rupesh, I grab the beagle.android-2.6.27 branch for the kernel, and it appears the omap3_beagle_android_defconfig file is a diff file. Did you check in the right file?
mount -t vfat /dev/mmcblk0p1 /sdcardthen i get
$setprop EXTERNAL_STORAGE_STATE mounted
$am broadcast -a android.intent.action.MEDIA_MOUNTED --ez read-only false -d file:///sdcard
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.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?
Cheers, Jay P.S. The changes to the build instruction look good:) On Jan 14, 11:04 pm, Rupesh Gujare <rupesh.guj...@embinux.com> wrote:Jay, JayBird wrote:
Have you synced you Android build with latest code. Patches mentioned in wiki are working with latest code drop. There have been quiet few changes related to sound in HAL. Also we are working on 2.6.27 kernel branch, as all development is moved to it and we expect all code base to work with 2.6.27 branch. I will look at rest of your suggestions soon. Regards, -- Rupesh Gujarehttp://embinux.com
Hi, all: When doing the porting Android port for beagle, some problem happens like below: step1: successully Getting Android build from http://source.android.com/download, problem met: a lots time lost to communication with the downloading website. solution is just repeating repo sync. After downloading, make succesully. step2: Apply tls & gl wrapper patch given below to Android build No problem with applying the patch for gl wrapper but problem met with applying the patch for tls and it gives error info: tls.h file not available. just skip. This is not solved. Does anybody know how to fix this? Thanks a lot. step 3 do ALSA Support. do substep 1-7 good. in substep 8: Compile build, when make, it gives lots of error info, don't know how to fix? Anybody can help me? The error info is pasted below Thank you very much in advance. Frank build/core/main.mk:180: implicitly installing apns-conf_sdk.xml target arm C++: libaudio <= hardware/alsa_sound/AudioHardwareInterface.cpp In file included from hardware/alsa_sound/AudioHardwareInterface.cpp:27: hardware/alsa_sound/AudioHardwareStub.h:24:40: error: hardware/AudioHardwareBase.h: No such file or directory In file included from hardware/alsa_sound/AudioHardwareInterface.cpp:27: hardware/alsa_sound/AudioHardwareStub.h:30: error: expected class-name before '{' token hardware/alsa_sound/AudioHardwareStub.h:40: error: expected ',' or '...' before '<' token hardware/alsa_sound/AudioHardwareStub.h:40: error: ISO C++ forbids declaration of 'Vector' with no type hardware/alsa_sound/AudioHardwareStub.h: In member function 'virtual int android::AudioStreamOutStub::format() const': hardware/alsa_sound/AudioHardwareStub.h:36: error: 'AudioSystem' has not been declared hardware/alsa_sound/AudioHardwareStub.h: At global scope: hardware/alsa_sound/AudioHardwareStub.h:43: error: expected class-name before '{' token hardware/alsa_sound/AudioHardwareStub.h:52: error: expected ',' or '...' before '<' token hardware/alsa_sound/AudioHardwareStub.h:52: error: ISO C++ forbids declaration of 'Vector' with no type hardware/alsa_sound/AudioHardwareStub.h: In member function 'virtual int android::AudioStreamInStub::format() const': hardware/alsa_sound/AudioHardwareStub.h:49: error: 'AudioSystem' has not been declared hardware/alsa_sound/AudioHardwareStub.h: At global scope: hardware/alsa_sound/AudioHardwareStub.h:57: error: expected class-name before '{' token hardware/alsa_sound/AudioHardwareStub.h:74: error: ISO C++ forbids declaration of 'AudioStreamOut' with no type hardware/alsa_sound/AudioHardwareStub.h:74: error: 'AudioStreamOut' declared as a 'virtual' field hardware/alsa_sound/AudioHardwareStub.h:74: error: expected ';' before '*' token hardware/alsa_sound/AudioHardwareStub.h:80: error: ISO C++ forbids declaration of 'AudioStreamIn' with no type hardware/alsa_sound/AudioHardwareStub.h:80: error: 'AudioStreamIn' declared as a 'virtual' field hardware/alsa_sound/AudioHardwareStub.h:80: error: expected ';' before '*' token hardware/alsa_sound/AudioHardwareStub.h:88: error: expected ',' or '...' before '<' token hardware/alsa_sound/AudioHardwareStub.h:88: error: ISO C++ forbids declaration of 'Vector' with no type hardware/alsa_sound/AudioHardwareStub.h:92: error: expected ',' or '...' before '<' token hardware/alsa_sound/AudioHardwareStub.h:92: error: ISO C++ forbids declaration of 'Vector' with no type In file included from hardware/alsa_sound/AudioHardwareInterface.cpp:28: hardware/alsa_sound/AudioHardwareALSA.h:116: error: 'Mutex' does not name a type hardware/alsa_sound/AudioHardwareALSA.h:130: error: expected class-name before ',' token hardware/alsa_sound/AudioHardwareALSA.h:163: error: expected ',' or '...' before '<' token hardware/alsa_sound/AudioHardwareALSA.h:163: error: ISO C++ forbids declaration of 'Vector' with no type hardware/alsa_sound/AudioHardwareALSA.h:179: error: expected class-name before ',' token hardware/alsa_sound/AudioHardwareALSA.h:213: error: expected ',' or '...' before '<' token hardware/alsa_sound/AudioHardwareALSA.h:213: error: ISO C++ forbids declaration of 'Vector' with no type hardware/alsa_sound/AudioHardwareALSA.h:228: error: expected class-name before '{' token hardware/alsa_sound/AudioHardwareALSA.h:260: error: ISO C++ forbids declaration of 'AudioStreamOut' with no type hardware/alsa_sound/AudioHardwareALSA.h:260: error: 'AudioStreamOut' declared as a 'virtual' field hardware/alsa_sound/AudioHardwareALSA.h:260: error: expected ';' before '*' token hardware/alsa_sound/AudioHardwareALSA.h:267: error: ISO C++ forbids declaration of 'AudioStreamIn' with no type hardware/alsa_sound/AudioHardwareALSA.h:267: error: 'AudioStreamIn' declared as a 'virtual' field hardware/alsa_sound/AudioHardwareALSA.h:267: error: expected ';' before '*' token hardware/alsa_sound/AudioHardwareALSA.h:282: error: expected ',' or '...' before '<' token hardware/alsa_sound/AudioHardwareALSA.h:282: error: ISO C++ forbids declaration of 'Vector' with no type hardware/alsa_sound/AudioHardwareALSA.h:292: error: 'Mutex' does not name a type hardware/alsa_sound/AudioHardwareInterface.cpp:88: error: expected constructor, destructor, or type conversion before '*' token hardware/alsa_sound/AudioHardwareInterface.cpp:236: error: expected `}' at end of input make: *** [out/target/product/generic/obj/SHARED_LIBRARIES/libaudio_intermediates/AudioHardwareInterface.o] Error 1 |
--- On Tue, 1/20/09, frank zhu <fzhu...@yahoo.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
console=ttyS2,115200n8 noinitrd root=/dev/mmcblk0p2 video=omapfb:mode: 1024x768@50 init=/init rootfstype=ext3 rw rootdelay=1 nohz=off
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.)
How can I fix this problem to show Android main screen on my LCD? (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. Check here: http://git.mansr.com/?p=linux-omap;a=commitdiff;h=80fe5350fcb8feeae2db01b0173c39077b656ecf The source code on embinux git seems not add this function? Hope this will help you. Sincerely, Ken
-- Rupesh Gujare http://embinux.com
On 1月15日, 上午5時23分, Howard M Harte <hhar...@gmail.com> wrote:
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.