have you specified the vga=788 in the cmdline? The vesafb can only be
started when booting up.
--
Chen
On Wed, May 20, 2009 at 2:13 PM, Alex wrote:
>
> I have installed android x86 eee_701 in VirtualBox successfuly.
> But the steps seem too repeated when I try to replace a kernel or
> system im
Cool!
have you applied the Jackie's alarm related patch in the kernel?
--
Chen
On Thu, May 21, 2009 at 7:55 AM, Yi Sun wrote:
>
> BTW-- I have confirmed that 2.6.29 kernel works with Android on x86. I
> can boot up Android without any problem even I did not test any devices
> yet.
> Chih-wei has
The mouse cursor works! Thanks to Yi for your great work! :)
I also observed the same as Chih-wei, if there are some dialog appears,
the mouse cursor responds very slowly. To have a try, you can just try in
the home screen, long press the mouse and then one dialog will pop up, then
you can try
emu command.
> qemu -kernel bzImage -initrd rootfs.cpio.gz -hda system.img -dhdb
> userdata.img -append "console=tty0 console=ttyS1,115200n8 console=tty0
> androidboot.hardware=eee_701 vga=788"
>
> On May 21, 9:54 am, Chen Yang wrote:
> > have you specified the vga=
sitory? Please let me know. Many thanks for the help
> >
> > On 5月21日, 上午10時09分, Chen Yang wrote:
> >
> >
> >
> > > Cool!
> > > have you applied the Jackie's alarm related patch in the kernel?
> > > --
> > > Chen
> >
>
sing apt-get?
> http://qemu-forum.ipi.fi/viewtopic.php?f=10&t=3913
>
>
> On May 21, 10:41 am, Chen Yang wrote:
> > AFAIK, qemu doesn't support the vga= option with append,
> > You may need to patch the qemu for that option:
> http://lists.gnu.org/archive/html/qemu-
n value seems correct, need to
> dig more when have time.
>
>
> 2009/5/20 Chen Yang
>
>The mouse cursor works! Thanks to Yi for your great work! :)
>> I also observed the same as Chih-wei, if there are some dialog appears,
>> the mouse cursor responds very slow
; try it out.
> Yi
> On Thu, 2009-05-21 at 12:24 +0800, Chen Yang wrote:
> > My guess is the surface transaction related handling caused the
> > recomputation of the whole screen. I have observed with the diaglo on,
> > system_server used lots of cpu time.
> > So w
How about trying "adb push"? It needs the network being configured properly,
you may need to compile the kernel supports the virtual ethernet card that
virtualbox emulates.
--
Chen
2009/6/15 GrainWang
>
> HI Sammy:
>Thanks! Is there any way to add files in virtuabox after the
> system bootin
: command not found"? do I still need something tools and where's
> the link? Thanks!
>
> On 6月15日, 上午10时27分, Chen Yang wrote:
> > How about trying "adb push"? It needs the network being configured
> properly,
> > you may need to compile the kernel suppor
search" to search in the website, the network
> connection is ok. Does adb need some aditional configations? Is there
> any guide exist for this? Also, when selecting "gallery", there is
> always "No media found", even when I insert a mini sd card and a usb
>
est clips in the /sdcard path, the
> "gallery" still prompt "No media found", does you know the reason? And
> how can I do to make the clips availble in the virtual box?Thanks!
>
> On 6月15日, 下午3时32分, Chen Yang wrote:
> > Oh, the ethernet card driv
> network adapter. do i need to recompile the kernel to enable the e1000
> driver? Thanks!
> On 6月15日, 下午6时36分, Chen Yang wrote:
> > You may need to set the state to tell the system:
> > try:
> > #setprop EXTERNAL_STORAGE_STATE mounted
> > Then see whether it work
ChenYang:
> Can you kindly tell me the detailed path in make menuconfig for
> choosing "CONFIG_PCNET32" or e1000 driver, I enabled everything in
> "network support" and "Devices drivers"->"Network device support", but
> I can't find the
I have raised the question about 5 months ago:
http://groups.google.com/group/android-porting/browse_thread/thread/f34d9ff618f8fc50/5dcd265cd2b7e126?pli=1
While no response.
Only google can do the that porting.
--
Chen
On Tue, Jun 16, 2009 at 1:33 PM, Yi Sun wrote:
>
> what does you mean about "g
did you forget to copy the kernel again? :-)
> >
> >
> >
> > On Tue, 2009-06-16 at 14:20 +0800, Chen Yang wrote:
> > > I have not met this kind of problem. I have successfully used the
> > > pcnet-pci card, also well as the e1000 desktop card with original
&g
i Sun wrote:
> >
> >
> >
> > > Grain,
> > > Let's us know if it works for you or not. If it is solve your problem,
> I
> > > will make this thread into a wiki page.
> > > Yi
> >
> > > On Tue, 2009-06-1
In short, no. I think lots of android on x86 have the data partition as
ext2, it works correctly.
--
Chen
On Mon, Jun 22, 2009 at 9:04 PM, thomasbl wrote:
>
>
>
> On Jun 19, 7:14 pm, Chen Yang wrote:
> > It looks like that you haven't mounted the /data with proper partit
it looks like that the installer is waiting for the second partition on the
usb drive.
You can check the paritions via looks into:
/dev/block/
try to list the nodes under that directory.
if you have the installer.img dd-ed on your usb drive, it should have 2
paritions. Don't know the detail of your
at of these is
> causing an issue?
>
>
>
> On Jun 29, 6:23 pm, Chen Yang wrote:
> > it looks like that the installer is waiting for the second partition on
> the
> > usb drive.
> > You can check the paritions via looks into:
> > /dev/block/
> > try to lis
syncing and rebuilding the installer from scratch just to
> make sure I haven't broken something.
>
> Thanks again for any further suggestions!
>
>
>
> On Jun 29, 9:23 pm, Chen Yang wrote:
> > No, it doesn't care about the target hdd's parition as the
t now
> with a clean build it works fine. It seems for HDD models of the
> eeePC you may have to change the IDE mode in BIOS from Enhanced to
> Compatibility.
>
> Thanks for your help guys, it's been a great learning experience!
>
> Bruce
>
>
>
> On Jul 1, 1
just curious to know: is the arm version working correctly?
>From what i have observed on x86, the introduced code by that patch brought
none reference stuff as reference, which caused the runtime segmentation
fault.
On Tue, Jul 7, 2009 at 2:34 AM, Yi Sun wrote:
> All,
> If you have a tree that i
you can follow the patch posted there:
http://code.google.com/p/patch-hosting-for-android-x86-support/
--
Chen
On Tue, Jul 7, 2009 at 12:46 AM, androidfan wrote:
>
> Hi,
> I am trying to build android for eee 701 with the following host
> system configurations:
> architecture: x86_64
> OS: Ubun
to any dalvik heap.
one case I remembered:
IS_CLASS_FLAG_SET(clazz, CLASS_ISARRAY) in scanObject: caused segfault
Any plan to introduce the precise GC soon? Thanks.
--
Chen
On Wed, Jul 8, 2009 at 1:49 AM, fadden wrote:
>
> On Jul 7, 10:41 am, Chen Yang wrote:
> > just curious to
Cool!
Any explanation on why it doesn't show on ARM platform?
--
Chen
On Thu, Jul 9, 2009 at 1:26 AM, fadden wrote:
>
> bhayes has posted an explanation of the problem in the change (https://
> review.source.android.com/#change,10482).
>
> In short, it can cause live objects to be collected.
>
>
u4 newBit = CLASS_BIT_FROM_OFFSET(f->byteOffset);
+clazz->refOffsets |= newBit;
+f++;
}
-f++;
-}
+ }
}
if (dvmCheckException(self)) {
On Fri, Jul 10, 2009 at 5:41 AM, fadden wrote:
>
> On Jul 9, 1:13 am, Chen Yang
Cool. would you like to provide some more detail about the issue? Thanks.
--
Chen
On 7/30/09, Chih-Wei wrote:
>
>
> The android-x86 build broken due to upstream changes (donut merged) is
> fixed.
> Now you can get a workable tree and enjoy Donut on x86.
>
> You may try to repo sync. But the chang
helps.
--
Chen
On Thu, Jul 30, 2009 at 3:10 PM, Chen Yang wrote:
> Cool. would you like to provide some more detail about the issue? Thanks.
> --
> Chen
>
>
> On 7/30/09, Chih-Wei wrote:
>>
>>
>> The android-x86 build broken due to upstream changes (donut mer
AM, Yi Sun wrote:
> Have you run the image? There should be more issues, the 10482 was not
> fixed yet (not sure about today's status), the init.rc has new entries need
> to add
> Yi
>
>
> On Sun, Aug 2, 2009 at 3:21 AM, Chen Yang wrote:
>
>> Just finishe
try Yi Sun and Chih-wei's work on android-x86:
http://code.google.com/p/android-x86/
They have done some great work for android on x86.
--
Chen
On Mon, Aug 3, 2009 at 7:54 PM, vishal bhoj wrote:
> Hello Everyone,
>
> I saw the livedroid image for x86 machine at
> http://groups.google.com/group/l
ild/core/main.mk:458: *** No TARGET_CPU_ABI defined by board
>> config: . Stop.
>>
>> Is this related?
>>
>> Thanks.
>>
>> P
>>
>>
>> On Aug 2, 6:12 pm, Yi Sun wrote:
>> > Chihwei backed out both from android-x86
>> &g
> > > > > Android 1.5 r3 into my eeepc, I am not able to do it with the .iso
> > > > > provided on the above link.
> >
> > > > > I downloaded eeepc-v0.9.iso, when I choose to install it return a
> > > > > message saying that installati
I have used android on x86 system with HT.
--
Chen
On Fri, Jan 9, 2009 at 1:21 AM, Simon Braunschmidt <
simon.braunschm...@gmail.com> wrote:
>
> Hi
>
> I am currently researching possibilities to run android on SMP. Would
> there be any blocking points that immediately come to your mind?
>
> Sin
You may be able to reference my post in this thread for the fix:
http://groups.google.com/group/android-porting/browse_thread/thread/b87d6c96a16af57d/a0461561a68c6e24#a0461561a68c6e24
On Tue, Aug 11, 2009 at 11:49 PM, Sergej Pupykin wrote:
>
> logcat log contains:
>
> I/PackageManager( 1448): N
I guess it is a permission problem:
According to the source:
mArchiveSourcePath = sourceFile.getPath();
if (!sourceFile.isFile()) {
Log.w(TAG, "Skipping dir: " + mArchiveSourcePath);
mParseError = PackageManager.INSTALL_PARSE_FAILED_NOT_APK;
return nul
Have you put the vmdk file together with the installer.img and be sure that
the installer.img can be accessed by current user. I cannot see obvious
problem in your steps in creating the vmdk. Hope it helps.
--
Chen
On Wed, Sep 30, 2009 at 3:15 PM, Rakesh Kumar wrote:
> Hi,
> Please tell me t
Cool! Would you like to share some insights on what makes the preloading and
scan so efficient on Nexus One? Fast CPU + fast flash? Which one is more
important? Or both?
Thanks.
--
Chen
On Tue, May 11, 2010 at 6:31 AM, Dianne Hackborn wrote:
> There is no trivial way to reduce either of those. T
Dianne:
Thanks a lot! Very helpful.
--
Chen
On Sat, May 15, 2010 at 3:02 AM, Dianne Hackborn wrote:
> On Wed, May 12, 2010 at 7:40 AM, Chen Yang wrote:
>
>> Cool! Would you like to share some insights on what makes the preloading
>> and scan so efficient on Nexus One? Fas
It would also be interesting to look at the log dumped by logcat with a
fresh rebooted nexus one. Would someone share here? Thanks.
--
Chen
On Sat, May 15, 2010 at 3:15 AM, Tim Bird wrote:
> On 05/14/2010 12:02 PM, Dianne Hackborn wrote:
> > On Wed, May 12, 2010 at 7:40 AM,
hi All:
Is there any known good approach to disable the trace-jit for installed
application on non-rooted phone?
I read the document in dalvik direcotory, it states that via setting
property of dalvik.vm.execution-mode can achieve the goal. But it doesn't
seem to work.
Also read the document that
have you specified the vesa mode support with vga=785 or so?
the console looks like in generic text mode.
--
Chen
On Sat, Aug 21, 2010 at 9:49 AM, Mitchell Lee wrote:
> Hello.
>
> I hope you give me some advice for me.. thank you for your time in advance.
>
> I'm using generic cupcake source cod
This thread may give some hints:
http://groups.google.com/group/android-porting/msg/64eb5a0158e6b815?dmode=source
The system server is parsing some vars to to values, while in your init.rc,
it hasn't specified it.
You can check ActivityManagerService.java:1303 for more information.
--
Chen
On Sun
i remembered that init.rc would invoke some script under /system/etc/
add a line under that:
netcfg eth0 dhcp
you may also assign eth0 with ifconfig in that script.
if you are referring to 169.xx like private ip, you can specify similar ip
on your host side to get communicatation with your target.
Forgot to add one better soultion by using Chris's script make-live:
http://code.google.com/p/android/issues/detail?id=1598
--
Chen
On Dec 24, 11:12 pm, Sunset wrote:
> The ramdisk may void the rootwait option, thus it won't solve the
> issue.
>
> Several approaches can be used to solve the
For use on qemu or generic PC, you may need to compile the kernel with VESA
Frame buffer support and specify the VESA mode when boot: vga=788 (800x600,
that may be a good resolution, 785 for 640x480, 791 for 1024x768). You can
add it in grub's menu.lst
For disk file with qemu, it may be possible to
I have managed to run it under both Vmware and Virtualbox. You need to
compile the kernel with proper driver: vesafb, ethernet, scsci or ide, etc.
You may be able to use the dd image of the make-live created usb key.
--
Chen
On Sat, Dec 27, 2008 at 2:58 AM, Andriod Developer wrote:
>
> Thanks Lee
t with my
description. Thanks.
--
Chen
On Sat, Dec 27, 2008 at 5:57 PM, Andriod Developer wrote:
>
> Hi Chen, could u pls list the steps to do this(i.e. running the image
> in virtualbox)?
> thanks
> Sri
>
> On Dec 26, 5:43 pm, "Chen Yang" wrote:
> > I have
, to replace the the hd0 with hd1, then it will start the installation
process correctly. You will also need the same rebooting and re-configure
the 0 sysloader, and 3 lines configuration to accomplish the installation.
Hope it helps!
--
Chen
On Sun, Dec 28, 2008 at 4:40 PM, Chen Yang wrote:
>
0 release and it complains about .vmdk file
> when i try to add it. Somebody has opened a bug for virtualbox for the
> same issue.
> What release are you using?
>
> On Dec 28, 8:12 am, "Chen Yang" wrote:
> > I just repeated the process on VirtualBox, mostly the same
lHWVersion = "4"
> ddb.geometry.cylinders = "49"
> ddb.geometry.heads = "255"
> ddb.geometry.sectors = "63"
> ddb.adapterType = "ide"
> ddb.toolsVersion = "0"
>
>
> I am choosing the existing virtual hard disk
on exisiting and selecting the .vmdk file(this is only 1k file
> though). When i select the file, virtualbox complains about failing to
> open the file and says it has invalid signature.
>
> Not sure if i am doing any wrong in this step..
>
> Please help!
>
>
>
>
>
&
hi Avtar:
Is this directory also used for pre-cupcake source? It seems that the
compilation issue was caused by the stale directory "recovery" under your
android source root directory. You may remove it to see whether it works or
not. Hope it helps!
--
Chen
On Sat, Jan 3, 2009 at 2:27 PM, Avtar
you have one typo in your command, missed the last 'g':
it should be
"TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true
CC=gcc-4.2 CXX=g++-4.2 make -j2 installer_img"
On Tue, Jan 6, 2009 at 9:24 AM, drew wrote:
>
> Hi, I'm running Ubuntu 8.04 with java-6-sun and tried to compile the
Some additions to build the kernel for VMWare/VirtualBox:
Hope it helps:
$cd mydroid
$cp vendor/asus/eee_701/kernel.config kernel/.config
$cd kernel
$make menuconfig
Select the device drivers:
For network card:
network device support ->
Ethernet (10 or 100Mbit) --->
[*] EISA, VLB,
installer.img to install in vmware/virtualbox again.
Hope it helps!
--
Chen
On Sat, Jan 10, 2009 at 12:21 PM, gowtham gowda wrote:
>
> After "make menuconfig"
> should we just save .config file or should we run "make" to compile a
> new kernel.
>
> Thanks,
>
&g
ke menuconfig.
>
> Thanks,
> gowthsm
>
> On Jan 9, 11:44 pm, "Chen Yang" wrote:
>> Sorry, I forgot to put the required information to that step:
>>
>> After that, you should save the .config
>> $make bzImage
>> Then copy the kernel to vendor/asus/eee_7
get past this.
>
> Thanks once again.
>
> Gowtham
>
>
> On Jan 10, 12:20 am, "Chen Yang" wrote:
>> For modules, you may need to put under
>> vendor/asus/eee_701/modules directory.
>> You can add the insmod in init.rc
>> or in the ini
Jan 10, 2009 at 1:35 PM, gowtham gowda wrote:
>
> works,
>
> thank you very much.
>
> Gowtham
>
> On Jan 10, 12:31 am, "Chen Yang" wrote:
>> how about:
>> $make bzImage
>>
>> --
>> Chen
>>
>> On Sat, Jan 10, 20
ild. And the "menu makeconfig" is compiling the new 2.6.27 kernel,
> so the driver modules are mismatching Do you know how to build drivers
> for kernel 2.6.27?
>
> Thanks,
> Gowtham
>
> On Jan 10, 12:37 am, "Chen Yang" wrote:
>> I remembered that pmem m
One potential start is to try to use eeepc's branch and together with
Chris's make-live script:
http://code.google.com/p/android/issues/detail?id=1598
You can reference this thread for build the installer_img:
http://groups.google.com/group/android-porting/t/66862bdb52dac936
and then you may
Can you check whether eth0 exist or not by issuing: netcfg?
If it exisits, you can try:
#netcfg eth0 dhcp
Hope it helps!
--
Chen
On Mon, Jan 12, 2009 at 9:10 PM, Wing wrote:
>
> I can run the live-USB image on my EeePC, but the Ethernet seem not
> work. Is there anyone has make it work?
>
> Th
0049"
>
> I also use dmesg to check, it seem there is no drivers for the
> etherent devices.
>
> Thanks anyway.
>
>
> Chen Yang wrote:
>> Can you check whether eth0 exist or not by issuing: netcfg?
>> If it exisits, you can try:
>> #netcfg eth0 d
Hi Samuel:
It seems that you need to modify the menu.lst to reflect the
correct root device, in your case:
root(hd0,0) -> change to (hd0,2)
kernel /boot/vmlinuz-2.6.27-android root=/dev/sda1 init=/init rw
selinux=0 vga=788 quiet -> change the rppt=/dev/sda1-> /dev/sdb3
iles in
> the directory of "grub", right?
>
>
> As of now, I can't yet boot up android from external mobile hard
> disk!! Most likely, I should review from the starting the entire
> processes of enabling android by virtue of the external mobile hard
> disk with usb
network with kvm/qemu, you may need to compile
the rtl8139 driver.
If you want to use ext3, please apply "tune2fs -j your.img".
Enjoy!
--
Chen
On Sun, Jan 11, 2009 at 11:36 AM, Chen Yang wrote:
> It looks like that you are missing the vga=788 option, you can
> reference my post:
hen you can build it.
Hope it helps!
--
Chen
On Wed, Jan 14, 2009 at 11:50 AM, gowtham gowda wrote:
>
> another question for the expert dhen
>
> How can we add busybox to this build?
>
> Thanks,
> Gowtham
>
> On Jan 10, 10:36 pm, "Chen Yang" wrote:
>>
W95 FAT32
> (LBA)
> /dev/sdb3 *5101972937182442+ 83 Linux
>
> Furthermore, what root-causes and which phase will cause that error
> information, "error loading operating system"?
>
> Finally, I really expect that I can start up android fr
Hi Mathias:
Just interested to know, what's the relationship between surfaceflinger
and pixelflinger?
Meanwhile, is there some document on sufraceflinger and pixelflinger?
Thanks.
--
Chen
On Sat, Jan 17, 2009 at 5:58 AM, Mathias Agopian wrote:
>
> On Fri, Jan 16, 2009 at 8:18 AM, F H wr
$ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make
installer_img -j2
...
build/core/main.mk:180: implicitly installing apns-conf_sdk.xml
target thumb C: init <= system/core/init/builtins.c
target thumb C: init <= system/core/init/init.c
8010+49000]
> <6>[ 51.677764] SurfaceFlinger[2055]: segfault at 38 ip 80110cf9 sp
> 9e18200c error 4 in libc.so[8010+49000]
> <6>[ 57.058660] SurfaceFlinger[2074]: segfault at 38 ip 80110cf9 sp
> b5cde00c error 4 in libc.so[8010+49000]
> <6>[ 61.437928] Surfac
try to build it again without the -j 2 option:
$TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true make
installer_img
See whether it helps or not.
--
Chen
On Wed, Jan 21, 2009 at 1:12 PM, poppa wrote:
>
> After following the directions, I have these error messages.
>
>
> -
t; when i am configuring the kernel. Where should i look for
> surfacefliner?
>
> Thanks for the reply
>
> Gowtham
>
> On Jan 19, 10:52 pm, "Chen Yang" wrote:
> > Your libc.so is causing segmentation fault.
> > You can firstly locate the routine at 0x10cf9 o
e bzImage to vendor/asus/
> eee_701/kernel and used the $ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701
> DISABLE_DEXPREOPT=true make -j2 installer_img to build the
> installer.img.
>
> Do i need to just compile as target_product=x86? and not use the asus
> files?
>
> Thanks,
&g
/data/mnt
if not, you need to resize that partition using resize2fs.
--
Chen
On 1/21/09, Chen Yang wrote:
>
> Would you like to provide related dmesg info? You can just print the lines
> leading with vesafb.
> --
> Chen
> On Wed, Jan 21, 2009 at 9:19 PM, gowtham gowda w
I found that gears is missing for android on IA, visiting gears.google.com,
it says:
Your browser is not currently supported. Please check the list of supported
browsers below.
While for the emulator provided by google, it shows: Gear is installed.
Current version:0.5.2.0
When will the gears.so f
Just fyi, i have successfully compiled the sample application for x86
target and run successfully with some similar modifications. :)
--
Chen
On Fri, Jan 23, 2009 at 3:29 AM, kozak wrote:
>
> Hi all,
> I am trying to compile and execute the simple hello world native app
> from the NDK (many com
It looks that your configuration in grub is incorrect.
You can modify it according to the reported sdb:
/boot/grub/menu.lst:
kernel /boot/kernel root=/dev/sdb2 rootdelay=6 rw ...
Or use the make-live script to build the usb book disk again, by
selecting 1 or default when promting "How many disks a
hi Zia:
It's not in the kernel, it's in the busybox. You can download the
BusyBox source and config it using make menuconfig.
--
Chen
On Wed, Feb 4, 2009 at 8:46 AM, Zia wrote:
>
> I'm looking to run BusyBox on Andoird x86 port (on VMware for now).
> Looking through the group, I noticed this
M, liuhy wrote:
>
> Dear Chen
>
> I meat "no sda6" problem.
>
> print this error
> "E/diskutils(1752):Could not open '/dev/block/sda6' for read/write
> (errno = 2)"
>
> I follow you flow , reboot vm ,but the same error.
> Did I miss do somethi
Are you trying to install android to the usb disk itself?
I remembered that the target is specified as /dev/block/sda in the
installer.img. So you are using the sda as both the source and the
destination at the same time, which seems to problematic.
If you want to build live usb, you can use Chris
AFAIK, the -p specifies the source of the parition where installation
related files locate.
Installation destination is specified in the /system/etc/disk_layout.conf
the path section, by default:
device {
path /dev/block/sda
...
}
Thus it installs to /dev/block/sda
Then in your case, you
be too old :)
> Do you kown where is "sda6" setting ? In which config file?
>
> I will try you suggestion
> 3x
>
> On Mon, Feb 9, 2009 at 12:48 AM, Chen Yang wrote:
>>
>> hi, I don't know whether the modification to sda has been already
>>
which config file?
>
> I will try you suggestion
> 3x
>
> On Mon, Feb 9, 2009 at 12:48 AM, Chen Yang wrote:
>>
>> hi, I don't know whether the modification to sda has been already
>> flushed to the virtual disk of VMWare. The safe way seems to issue the
>> command
In short, it applies the dexopt optimizations for those framework
library(/system/framework) and built-in applications(/system/app) with
the specific build of the system.
You can reference mydroid/build/tools/dexpreopt for information on
what it has done.
At present, the script only supports arm t
DJ:
You can reference the information from the thread:
http://groups.google.com/group/android-porting/t/66862bdb52dac936
Hope it helps!
--
Chen
On Thu, Feb 12, 2009 at 9:25 PM, dhananjay wrote:
>
> Hi All,
> I want to build android on my linux x86 core 2 duo m/c.
> (ubuntoo) .
>
Sam:
You can reference the thread on eeepc, i have one post regarding
build the kernel for VMWare.
http://groups.google.com/group/android-porting/msg/b9ffcb185b758b92
http://groups.google.com/group/android-porting/msg/4e5a2a4498e2513f
To build the drivers in the kernel, if you select built-in
; I succeed running android in qemu , but failed running in vmware.
> In my vmware, androidboot run well until the cmdline output "eth0 :
> link up " , and then stop boot.
> After that , I can just input cmdline in it.
>
> Do you meet this problem , how to slove it
Yes. You can follow the discussion on compilation for VMWare target to
build Android for a common PC.
--
Chen
On Thu, Feb 19, 2009 at 9:42 PM, MacknZ wrote:
>
> Is it possible to run android on a common PC (x86) ?
>
> On 1月10日, 下午9时11分, "Lim,GeunSik" wrote:
>> Hi, all
>>
>> How to use
You may be able to reference these posts:
Create the installed image directly from the source:
http://groups.google.com/group/android-porting/msg/2dedc5fe7ad58ed3?pli=1
Installation in VMWare:
http://groups.google.com/group/android-porting/msg/fe85782f1bc3ad2f
Installation in VirtualBox:
http://gr
Would you like to provide more information on what the problem is?
Are you using the system installed by using the usb installer? Or
using a live usb?
When you met with the problem, have you removed the usb stick?
--
Chen
On Sat, Feb 21, 2009 at 8:04 PM, Toni.g wrote:
>
> mhh i not sure but I t
How about the result using the installer.img directly as mentioned in the post:
http://groups.google.com/group/android-porting/msg/fe85782f1bc3ad2f
--
Chen
On Sun, Feb 22, 2009 at 8:56 PM, MacknZ wrote:
>
> I started installer.vdi in virtualbox, it just print "Grub Loading
> stage2" and stopped
oh, you are using the installer.img to boot with normal boot, that is
impossible. Since the installer.img only contains 2 partitions. it
doesn't have the (hd0,2) partition as the installed system. You can
reference my post in this thread for the information on building the
image that can be used d
\
drm.ko \
i915.ko
..
Add you modules in that list.
Hope it helps!
--
Chen
On Thu, Mar 5, 2009 at 6:19 PM, ehung1...@gmail.com wrote:
>
> Hi chen Yang
> I still have a question about adding modules to compile the kernel
> when we select the option in make menuconfig.
>
would you like to tell the problem in mounting?
--
Chen
On Fri, Mar 6, 2009 at 8:48 AM, Iuri Fiedoruk wrote:
>
> Was anyone able to use the SD Card from inside Android on a eee 701?
> I'm running a live-usb of android got the .img from
> http://virtuallyshocking.com/2008/12/20/building-android-f
look like, how your Android.mk?
>
> Dani
>
> On Feb 4, 7:36 pm, AndyM wrote:
>> when you build busy box there is an option to build statically. That
>> may be your best bet to get it running on x86.
>>
>> On Feb 4, 1:02 pm, Zia wrote:
>>
>> > Than
hi Brian:
You are using the installer.img which is used to work as a USB
installer for eeepc, after it installs, it can start the gui
correctly.
--
Chen
On Sun, Mar 22, 2009 at 11:53 PM, Brian wrote:
>
> I am getting the same error message when I ran the android x86 eeepc
> in vmware.
> init
You may need to set the adb target:
under linux:
export ADBHOST=your_vmware_target_ip
under windows:
set ADBHOST=your_vmware_target_ip
then try to start the adb server. if you have already started the
server, you need to kill it firstly by: adb kill-server
If you are using NAT network in VMwar
gt; [time] init : cannot find '/system/bin/mountd', disabling 'mountd'
> sh : can't access tty: job control turned off
> [time] warning: 'app_process' uses 32-bit capabilities (legacy support
> in use)
>
> How can I fix it? It's hard to pinpoint
ed on VESA VGA and Framebuffer Console support when I
> compiled bzImage.
>
> dmesg output keeps printing out the following.
> <6> [timestamp] SurfaceFlinger[2956]: segfault at 38 ip 80111049 sp
> b5b56fec error 4 in libc.so [80100000+4b000]
>
> Thanks for your help.
> Brian
&
1 - 100 of 140 matches
Mail list logo
