[android-porting] Re: x86 svn repository is ready

2009-05-21 Thread liuhy
good news! thanks On 5/21/09, fredchen wrote: > > Thanks for your reply. By the way, can you teach me how to download > 2.6.29 kernel? Thanks. > > On 5月21日, 下午1時46分, Yi Sun wrote: >> 05-18-2009 I have just tested out the kernel 2.6.29. It seems that it >> works fine with x86 platform. Just do f

[android-porting] Re: Everyone in google IO gets a free phone --Ha ha ha ha..... -eom

2009-05-27 Thread liuhy
eom? what is it? On Thu, May 28, 2009 at 1:49 AM, Yi Sun wrote: > > > > > > > --~--~-~--~~~---~--~~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~--~~~~--~~--~--

[android-porting] Re: Freeze while booting

2009-05-31 Thread liuhy
check if dirtory "data/dalvik-cache/" exist? On Sun, May 31, 2009 at 11:04 PM, Anonymous Anonymous < firewallbr...@googlemail.com> wrote: > Hi All , Can anyone give me some idea on the below scenario please ! > > > W/vold( 1026): _mmc_event++ > > W/vold( 1026): media_lookup_by_path++ >

[android-porting] Re: HW acceleration of OpenGL on Android x86

2009-06-09 Thread liuhy
a good news. 3x 2009/6/9 Chia-I Wu > > Hi all, > > We (0xlab.org) have successfully accelerated opengl on android x86 using > mesa i915 dri driver. The work is more a proof-of-concept, but it does > show that it is possible to re-use the hard work of mesa/intel guys in > android. For more de

[android-porting] Re: HW acceleration of OpenGL on Android x86

2009-06-09 Thread liuhy
can your branch run on vmware? or only on eeepc ? 3x 2009/6/9 liuhy > a good news. > 3x > > > > 2009/6/9 Chia-I Wu > > >> Hi all, >> >> We (0xlab.org) have successfully accelerated opengl on android x86 using >> mesa i915 dri driver. The work

[android-porting] Re: Is 768MB RAM sufficient to install and build Android ?

2009-06-12 Thread liuhy
in my environment , build android need 1G ram at least. 2009/6/12 Ishita Sharan > > > It would be great if someone could let me know whether 768MB of RAM is > sufficient to install and build Android source code . (With 32 bits > Ubuntu Linux) > > Thanks > Ishita > > > > --~--~-~--~~

[android-porting] Re: Announcement: [New project] Build and run only Dalvik

2009-07-15 Thread liuhy
hi avtar can i join? I also run servel example in dalvik on x86 2009/7/15 Avtar Singh > > > Great Job Avtar ! Canonical had recently shown android apps running on > > ubuntu. > Thanks! > > > Quite interested in having this working on ARM along with other linux > > applications. > > Are yo

[android-porting] Re: Hi

2009-07-16 Thread liuhy
ok. very good idea . thanks a lot .i see the project and then tell you 2009/7/16 Avtar Singh > > Hi Liuhy, > > I have created the project at http://code.google.com/p/dvk. Please see > if it is useful to you and let me know what user role should I create > for you. > >

[android-porting] Re: Hi

2009-07-16 Thread liuhy
. now ,i read the dalvik source code . i think if it possible put dalvik to j2ee . ( google app engine may use dalvik .) what do you think 2009/7/16 liuhy > ok. very good idea . thanks a lot .i see the project and then tell you > > 2009/7/16 Avtar Singh > > >> Hi Liuhy, >

[android-porting] Re: Hi

2009-07-17 Thread liuhy
>> i success build some java test on dvk . for example , transform dom4j.jar >> to dex jar ,and use it to parse xml string . hehe Have you completed the testing..? If yes (!) you can add it to the dvkpatch/samples for reference of others. I will setup the SVN trunk with the code and provide you ac

[android-porting] Dalvik in J2EE : running tomcat on dalvik

2009-08-06 Thread liuhy
hi everybody . I successful running tomcat on dalvik vm recently. Maybe the first new to do this . I think , dalvik can be used in J2EE realm . In app server, you can run dalvik just as other vms like sunjava , jrocket , ibmvm .What is you opinion? Let's discuss it . --~--~-~--~---

[android-porting] Re: Dalvik in J2EE : running tomcat on dalvik

2009-08-07 Thread liuhy
bionic 。 maybe on tomcat , we can run other interesting things 。 Flex app 。 I just finish a demo . after finish porting totally , I wish to opensource it . 2009/8/7 Avtar Singh > > Good work, Liuhy! > > Have you been able to run on a desktop with glibc? or bionic? > > On T

[android-porting] Re: Howto build Android full source for X86 Architecture like EeePC(ASUS)

2009-02-08 Thread liuhy
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 something ? On 2008年12月28日, 下午4时40分, "Chen Yang" wrote: > At hand, i only have VMware works

[android-porting] Re: Howto build Android full source for X86 Architecture like EeePC(ASUS)

2009-02-09 Thread liuhy
have posted the steps to build the installed image file directly here: > >> http://groups.google.com/group/android-porting/msg/2dedc5fe7ad58ed3 > >> After that you can use the steps to create the vmdk to use with VMWare. > :) > >> See whether it solves the issue. >

[android-porting] Re: Howto build Android full source for X86 Architecture like EeePC(ASUS)

2009-02-15 Thread liuhy
Hi , chen Thanks for your help. I followed your steps bellow. 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 pr

[android-porting] Re: eee_701

2009-03-03 Thread liuhy
can you give more details? On Tue, Mar 3, 2009 at 9:26 AM, Luca Belluccini wrote: > > I'm testing Android on a eee_701 and VMWare appliance. > Both are giving me android.process.acore has stopped ... error. > Any hint? > > > --~--~-~--~~~---~--~~ unsubscribe: andr

[android-porting] Re: Dalvik Porting Guide

2009-05-15 Thread liuhy
up , very good! On Fri, May 15, 2009 at 1:41 AM, fadden wrote: > > The first cut at a new "Dalvik Porting Guide" is available. This may > be of interest to anyone who wants to move beyond libffi and the > "portable" interpreter on a non-ARM, non-x86 platform. > > It's now in the source tree as