Hi Andy,
After setting the dx path I am getting the below error
[r...@localhost tests]# ./run-test 001
/home/myandroid/dalvik/tests/001-nop: running...
/home/myandroid/dalvik/tests/001-nop: succeeded!
[r...@localhost tests]# ./run-test 002
/home/myandroid/dalvik/tests/002-sleep: running...
Hi all
Embinux and TI are jointly conducting a seminar on Android on BeagleBoard
on 25-July-2009.
For details and registration, please visit,
http://www.embinux.com/beagle_embinux.html
or
http://www.pacemarketingsolutions.com/promos/texas/beagle/beagle.html
Thanks,
Embinux Team
Hi, all
many people downloaded livedroid alpha iso file.
I am afraid that I may have given all of you disappointment.
I prepared a slightly better thing hastily.
livedroid update alpha2.
* CD remaster ready
* add mouse patch
* add 32bit color patch
* fixed GRUB menu title
* fixed ISO
Hi, I'm interested in your livedroid project, but I cannot very understand
your introductions.
What do you mean by saying based on Debian lenny? Have you port the
android base system to the kernel based on Debian?
At last, thanks for your great job!
On Tue, Jul 7, 2009 at 5:44 PM, kinneko
Hi,
I am trying to build android for eee 701 with the following host
system configurations:
architecture: x86_64
OS: Ubuntu 9.04
gcc version: 4.3.3
I downloaded the source files and initiated build with this command:
sudo TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true
make -j2
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 vaishali.kara...@gmail.comwrote:
Hi,
I am trying to build android for eee 701 with the following host
system configurations:
On Jul 7, 10:41 am, Chen Yang sunsety...@gmail.com wrote:
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.
We don't see a
On Jul 6, 11:05 pm, Sivan sivaprasa...@gmail.com wrote:
+error: device not found
By default, the tests are run on the emulator or an attached device.
Do you have these? If so, what does adb devices show?
--~--~-~--~~~---~--~~
unsubscribe:
Fadden:
Thanks.
I don't have it at present.
Is there some good approach for generating the native stack trace? It seems
in my case, it just aborts and restarts the zygote again and again.
From what I have observed, it dumped some weird value as reference, the
value doesn't belong to any dalvik
It does not give me a trace at all. The dalvik only reports a process exit
by sig 11.
On Tue, Jul 7, 2009 at 11:06 AM, Chen Yang sunsety...@gmail.com wrote:
Fadden:
Thanks.
I don't have it at present.
Is there some good approach for generating the native stack trace? It seems
in my case,
There seem to be two problems under discussion in this thread. One is
a native stack trace and the other is the keystore problem Fadden
mentions, in a non-public merge. Both go away with the rollback. I
don't think anyone at Google has a good handle on what the native
problem is; I don't think
On Tue, Jul 7, 2009 at 12:20 PM, barry bha...@gmail.com wrote:
There seem to be two problems under discussion in this thread. One is
a native stack trace and the other is the keystore problem Fadden
mentions, in a non-public merge. Both go away with the rollback. I
don't think anyone at
Hi All,
I am running in to out of memory while using 800x480 resolution. While
the same code runs fine for 320x480 resolution. In heap memory alloc
after some time i get NO_MEMORY and this exception. Does this bigger
resoltion need more of heap memory.
In logcat i am getting following messages.
Hi,
Thank you for your interest in my project !
After starting as a minimal Debian system,
livedroid execute chroot to the environment of Android.
I merged the configuration of Android to kernel configuration of Debian.
If you intercept boot process of livedroid, you can use debian system.
Of
The issue should be caused by too many surface exist at one time,you
can dump service info to check it.Then you can check if so much
surface is really needed,if yes I guess you should increase it.
On 7月8日, 上午7时20分, ysadhu sadhu.yog...@gmail.com wrote:
Hi All,
I am Getting out of Memory for
FYI--I just made a gdbserver for Android on X86. It is in
http://patch-hosting-for-android-x86-support.googlecode.com/files/gdbserver
On Tue, Jul 7, 2009 at 3:19 PM, Yi Sun beyo...@gmail.com wrote:
On Tue, Jul 7, 2009 at 12:20 PM, barry bha...@gmail.com wrote:
There seem to be two problems
Thanks tony, this was my first suspicion, as its working after
increasing memory.
But i couldn't get any info of tracking surfaces held at one point of
time.
On Jul 7, 6:56 pm, tony e13...@gmail.com wrote:
The issue should be caused by too many surface exist at one time,you
can dump service
Hi,
I can build an executable which uses shared libraries using android
tool chain but unable to build a static one. When I use -static switch
it complains saying
.../../arm-eabi/bin/ld: cannot find -lc
collect2: ld returned 1 exit status
--~--~-~--~~~---~--~~
18 matches
Mail list logo
