Hi All, Can anyone please clarify my doubts?
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 <koansin....@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 > > > > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
