SDK 1.5 - "Emulator Control" don 麓t send GPS location

by Ricardo » Wed, 29 Apr 2009 08:47:49 GMT

Sponsored Links
 Hi all,

I installed de SDK 1.5 with the ADT 0.9 plugin, but I cant send the
GPS location using the Emulator Control view as before..

But using telnet and the "geo fix" command it works.

Any idea ?

Anybody could get the Emulator Control view work with the new sdk/
plugin ?

thank you


Other Threads

1. How to force system built my own library earlier

I would like to add my own shared library in Android opencore
protocol, but I got some error messages when making whole system.
After checking the following directory: out/target/product/generic/obj/
SHARED_LIBRARIES/libxxx_intermediates, I found out there was no, even it's already added in prelinkmap. I am not sure the
reason but guess that might be because my library wasn't built yet
when system needed it to make opencore library. So, does any one can
give me suggestion to solve this problem? like how to modify the make
file to force system built my library earlier than opencore?


2. android JFFS2 based rootfs problem


I am trying to run Android SDK on ARM RealView board based virtual
platform having Cortex-9 processor.
The board has two nor flash (flash0 and flash1) of 64M each.
Taken android-2.6.32 version kernel, I,  configured, modify, built and
booted it on the platform.

The flash has been partitioned (using MTD subsystem) like this:
armflash.0 -> First 2M for android Kernel and next 2 MB for busybox
based cramfs image
armflash.1 -> Full 64 MB for android root (JFFS2) image

Current situation is that I am able to boot android kernel and log it
into cramfs image.
Now after that I mount the android root on tmpfs using the following command

mount -t jffs2 /dev/mtdblock2  /tmpfs/android

The command executes successfully, but when I run "ls /tmpfs/android",
system seems to go into infinite loop and the prompt never comes back.

(Other Details) I prepared the android rootfs as follows :

using cpio, I unzip the ramdisk.img image that comes with Android 2.1
platform. Downloaded pre-built system.tar.gz and data.tar.gz from, untar them
into the rootfs directory.
and then running the command

mkfs.jffs2  -n  -s 128 -r _install -o root_jffs2.img

where _install is my android rootfs directory and root_jffs2.img is
the output image. The size of root_jffs2.img is around 48MB.

Other observations are:

When I keep the the partition size of android rootfs on armflash.1 to
be 32 MB the ls commands succeeds. But due to obvious reasons when I
run "chroot /tmpfs/android /int", I got segmentation fault.

I don't understand why the ls commands works (for the same image) when
the partition size is equal to 32 MB but not when partition size is
64MB and what should I do to correctly mount the android rootfs.

Any help in this regard will be highly appreciated.


CircuitSutra Technologies
Software Partner to Semiconductors


3. Kernel Panic

4. Tanya : Pengguna Motorolla Droid. Anda memakai Rom apa saat ini ?

5. IP infringements on the Market

6. Error when adding gdata jar library to Android

7. Support ECIES encryption?