1) Android SDK & Sources : What we get from google
contains a built Emulator along with ramdisk, data & system imgs.
It is an ARM Emulator (QEMU) which emulates a ARM processor architecture.
2) Android Sources : When we get android sources, run . ./envsetup.sh
& lunch 1, It gives the Emulated ARM Environment (QEMU).
3) A generic x86 PC: This is the build which will make Android to work
on X86 architectures like Asus ePC, Normal Desktop etc. We have the
live script to make it and run.
4) QEMU x86 version: Is this the QEMU emulated environment of Android
running on X86? What are the steps to make it work? choosecombo steps?
Is my understanding right?
Thanks,
Ram.On Fri, Dec 26, 2008 at 9:59 PM, freedom <koans...@gmail.com> wrote:
for the first case, most likely your USB hard drive is not /dev/block/
sdb, to use it to install Android on your system, kill the /system/bin/
installer process and run '/system/bin/installer -p /dev/block/
WHAT_YOUR_HARDDRIVE_IS2' (e.g., my USB stick is sdd, I use /dev/block/
sdd2)
for the second case, I think what you guessed is right. To be sure of
it, if you got ethernet, 'adb logcat' could help you. To build
required modules, you may wanna read 'vendor/asus/eee_701/modules/
module.versions', check out android-2.6.25 kernel, and start from
'vendor/asus/eee_701/kernel.config'.
On Dec 26, 8:58 pm, Stargatto <carl.ro...@virgilio.it> wrote:
> Ok, after some work I get installer.img from android sources.
>
> I'm trying to use it on 1) QEMU x86 version 2) a generic x86 PC (not
> Asus eee).
>
> In the first case linux kernel loads, but the installer stops trying
> to lauch init script
> (I guess there are some scripts to modify to permit android to work
> properly on
> an emulated environment). In particular, I obtain something like
> init: Unable to open persistent property directory /data/property
> errno:2
> installer : waiting for device: /dev/block/sdb2
>
> The secondo case in more interesting. I've used make-live script to
> copy installer.img
> on an USB hard drive. Android kernel and init scripts start without
> problems.
>
> The problem is that after the first loading I obtain a "black screen",
> but with ALT+F1
> I can use the sh prompt. I think that the black screen appears because
> I haven't an
> Intel 915 video card on the pc...but I'm not really sure.
>
> Any tips or suggestion?
>
> On 25 Dic, 15:55, "gowtham gowda" <gowth...@gmail.com> wrote:
>
> >http://code.google.com/p/android/issues/detail?id=1598
>
>
Thanks Lee for the detailed instructions. Do you know if this build
works in Virtual Environment(like VMWare or VirtualBox?).
What changes do I need to make if I need to run this in virtual
environment?
Also, Do you know if the vanilla cupcake branch will work for the
virtual environment? Or do I need to pull in the Asus tree?
Thanks
On Dec 23, 7:11 am, "Lim,GeunSik" <lee...@gmail.com> wrote:
> HOWTO Build Android-X86 Full Source
> ====================================
> Last Modified on 23-Dec-2008 23:10
>
> I Summarized how to build android full source for x86 target.
>
> 0. My development environments
> - OS : Ubuntu 8.10 Distribution ( 2.6.27-4-generic )
> - CPU: Intel(R) Core(TM)2 Duo CPU T5750 @ 2.00GHz ( Samsung SENS
> R60 Laptop )
> - RAM: Samsung DDR Ram
> - Target: Eee PC (ASUS)
>
> 1. Query of Linux distribution information
> - At first, Prepare ASUS Eee 701 Lattop or Samsung nettop (NC01).
> And then, confirm system information on your linux distribution
> like belows.
>
> $ uname -a
> Linux invain-laptop 2.6.27-4-generic #1 SMP Wed Sep 24 01:30:51 UTC
> 2008 i686 GNU/Linux
>
> $ gcc --version
> gcc (Ubuntu 4.3.2-1ubuntu10) 4.3.2
> Copyright (C) 2008 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There
> is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
>
> 2. repo init and Sync
> - You have to download android full source for x86 architecture like
> ASUS Eee PC 701.
> - Eee pc dev tree is "git://android.git.kernel.org/platform/vendor/
> asus/eee_701.git".
> $ cd ~
> $ mkdir bin_x86 && cd bin_x86
> $ mkdir mydroid && cd mydroid
> $ repo init -u git://android.git.kernel.org/platform/manifest.git -b
> cupcake
> $ repo sync
> $ vi ./.repo/local_manifest.xml
> <manifest>
> <project name="platform/vendor/asus/eee_701" path="vendor/asus/
> eee_701"/>
> </manifest>
>
> $ repo sync
> ... A new repo command ( 1.8) is available.
> ... You should upgrade soon:
>
> cp /home/invain/bin_x86/mydroid/.repo/repo/repo /home/invain/bin/
> repo
>
> Initializing project platform/vendor/asus/eee_701 ...
> remote: Counting objects: 33, done.
> remote: Compressing objects: 100% (31/31), done.
> remote: Total 33 (delta 2), reused 33 (delta 2)
> Unpacking objects: 100% (33/33), done.
> From git://android.git.kernel.org/platform/vendor/asus/eee_701
> * [new branch] cupcake -> korg/cupcake
> * [new branch] master -> korg/master
>
> 3. Building x86 android full source
> $ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make -
> j2 installer_img
>
> build/core/product_config.mk:207: WARNING: adding test OTA key
> ============================================
> TARGET_PRODUCT=eee_701
> TARGET_BUILD_VARIANT=eng
> TARGET_SIMULATOR=
> TARGET_BUILD_TYPE=release
> TARGET_ARCH=x86
> HOST_ARCH=x86
> HOST_OS=linux
> HOST_BUILD_TYPE=release
> BUILD_ID=
> ============================================
> build/core/main.mk:178: implicitly installing apns-conf_sdk.xml
> ............... Below Omission ...................
>
> * Toouble Shooting
>
> $ vi external/srec/tools/thirdparty/OpenFst/fst/lib/../../fst/lib/
> vector-fst.h
> $ vi external/srec/tools/thirdparty/OpenFst/fst/lib/symbol-table.cpp
> $ vi frameworks/base/tools/aidl/aidl.cpp --> #include <stdlib.h>,
> #include <string.h>
> and so on......
>
> $ vi
> $ ls -lh out/target/product/eee_701/
> total 753M
> -rw-r--r-- 1 oedev oedev 2.5M 2008-12-20 21:23 boot.img
> -rw-r--r-- 1 oedev oedev 57 2008-12-20 22:15 clean_steps.mk
> drwxr-xr-x 4 oedev oedev 4.0K 2008-12-20 21:32 data
> drwxr-xr-x 2 oedev oedev 4.0K 2008-12-20 19:54 grub
> drwxr-xr-x 4 oedev oedev 4.0K 2008-12-20 22:36 installer
> -rw-r--r-- 1 oedev oedev 388M 2008-12-20 22:38 installer.img
> -rw-r--r-- 1 oedev oedev 1.9M 2008-12-20 18:45 kernel
> drwxr-xr-x 12 oedev oedev 4.0K 2008-12-20 22:33 obj
> -rw-r--r-- 1 oedev oedev 592K 2008-12-20 21:10 ramdisk.img
> drwxr-xr-x 9 oedev oedev 4.0K 2008-12-20 21:09 root
> drwxr-xr-x 4 oedev oedev 4.0K 2008-12-20 19:55 symbols
> drwxr-xr-x 12 oedev oedev 4.0K 2008-12-20 21:29 system
> -rw-r--r-- 1 oedev oedev 355M 2008-12-20 22:34 system.img
> -rw-r--r-- 1 oedev oedev 5.0M 2008-12-20 21:32 userdata.img
>
> $ file out/target/product/eee_701/installer.img
> out/target/product/eee_701/installer.img: x86 boot sector;
> GRand Unified Bootloader, stage1 version 0x3; partition 2:
> ID=0x83, starthead 0, startsector 10926, 783672 sectors, code offset
> 0x48
>
> $ file out/target/product/eee_701/system.img
> out/target/product/eee_701/system.img: Linux rev 0.0 ext2 filesystem
> data
>
> $ file out/target/product/eee_701/userdata.img
> out/target/product/eee_701/userdata.img: Linux rev 0.0 ext2 filesystem
> data
>
> $ sudo mount -o loop boot.img /mnt
> total 2.5M
> -rw-r--r-- 1 oedev oedev 77 2008-12-20 21:23 cmdline
> -rw-r--r-- 1 oedev oedev 1.9M 2008-12-20 21:23 kernel
> -rw-r--r-- 1 oedev oedev 592K 2008-12-20 21:23 ramdisk
>
> $ cat /mnt/cmndline
> console=tty0 console=ttyS1,115200n8 console=tty0
> androidboot.hardware=eee_701
>
> $ cp /mnt/ramdisk /tmp/ramdisk.gz
> $ cd /tmp
> $ gunzip ramdisk.gz
> $ cpio -iv < ramdisk
> sys
> init.goldfish.rc
> system
> data
> init.rc
> proc
> init
> default.prop
> sbin
> sbin/adbd
> init.eee_701.rc
> lib
> lib/modules
> lib/modules/i915.ko
> lib/modules/font.ko
> lib/modules/drm.ko
> lib/modules/cfbcopyarea.ko
> lib/modules/cfbimgblt.ko
> lib/modules/bitblit.ko
> lib/modules/cfbfillrect.ko
> lib/modules/softcursor.ko
> lib/modules/fbcon.ko
> lib/modules/atl2.ko
> dev
> 2955 blocks
>
> $ file /tmp/init
> /tmp/init: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
> statically linked, not stripped
>
> 4. Make USB Stick Installer
> $ dd if=out/target/product/eee_701/installer.img of=/dev/<usbstick of
> your choice>
>
> 5. Now. Enjoy X86 Android Platform!
>
> End of Line.
Problems?
1) at high resolutions android doesn't work very well (using vga=794)
2) low screen refresh rates (obvious, is a framebuffer...)
3) no mouse support
4) buggy keyboard support
5) no network support
6) dialer function doesn't work.. ;-)
--
Yang, Chen
Yes. It also had pre-cupcake source. It works now. Thanks, Chen! I
will now follow the make output and see what I have got.
I now get the following error: could not locate libstdc++. Any pointers?
# TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make
installer_img
build/core/product_config.mk:207: WARNING: adding test OTA key
============================================
TARGET_PRODUCT=eee_701
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_ARCH=x86
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=
============================================
build/core/main.mk:178: implicitly installing apns-conf_sdk.xml
host Executable: genext2fs
(out/host/linux-x86/obj/EXECUTABLES/genext2fs_intermediates/genext2fs)
/home/developer/mydroid/prebuilt/linux-x86/toolchain/i686-unknown-linux-gnu-4.2.1/bin/../lib/gcc/i686-unknown-linux-gnu/4.2.1/../../../../i686-unknown-linux-gnu/bin/ld:
cannot find -lstdc++
collect2: ld returned 1 exit status
make: *** [out/host/linux-x86/obj/EXECUTABLES/genext2fs_intermediates/genext2fs]
Error 1
I now get the following error: could not locate libstdc++. Any pointers?
# TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make
installer_img
build/core/product_config.mk:207: WARNING: adding test OTA key
============================================
TARGET_PRODUCT=eee_701
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=
TARGET_BUILD_TYPE=release
TARGET_ARCH=x86
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=
============================================
build/core/main.mk:178: implicitly installing apns-conf_sdk.xml
Check the link below- it should do:
http://source.android.com/download#TOC-Installing-Repo
Avtar
I have the same problem, and have already tried the solutions.
Using the first solution, I got the following message
make: *** No rule to make target `droid'. Stop.
and Second solution, I remove -j2 from command but got the same error
message as before.
out/host/linux-x86/bin/genext2fs: out/target/product/eee_701/data ismake: *** [out/target/product/eee_701/userdata.img] Error 1
neither a file nor a directory
Is there anyone has ideas??
The kernel and i915 driver should be ok. I used EeePC1000H which is also 945 but they use same driver source.I think your kernel config should still have problem. The black screen is because your graphics modules (drm.ko and i915.ko) are not loaded correctly. You must missed sth in kernel config. You can "alt+F1" to switch to console to check dmesg what's the missed module. A better way is to enable adbd and login to check the error. But you need to rebuild the atl ethernet driver to get network work.Best Rgd
Thanks in advance
Giridhar