Custom KML - This Community Map could not be displayed....

by raster » Tue, 25 Jan 2011 02:51:15 GMT

Sponsored Links
 I'm new to Android Dev but have been looking at the tutorials/
examples. One was hooking up google maps to the AVD. It was a small
tutorial and google maps come up fine. I then added the few lines to
link in a custom KML file. My AVD target is Google APIs Platform=2.1
API Level=7.
When I link the google example KML file like so...
Uri uri1 = Uri.parse("geo:0,0?q= 
It all runs fine and the KMl loads.
But when I copy this same KML_Samples.kml onto a local server in our
domain, I get the "This Community Map could not be displayed because
it contains errors.".
I've looked on the web and others have had this issue but there are no
resolutions I can find. The local domain server I'm putting it on is
Server 2003 with IIS running. I put the KML_Samples.kml in the same
virtual directory which serves up another KML for a Google Earth app
we have. I can hit this KML file on our local server through a browser
(http://IPAddress/kml_files/KML_Samples.kml) and it opens fine. It
just fails when being link through google maps on the AVD.
Is there something else I need to do to make it work on the local



Other Threads

1. Why does booting time reduce from 2 min to 1 min after just adding a printk(..) invoking?

This sounds like something I've seen on other devices.

Try the kernel 'quiet' option.  See

The kernel printk buffer (known internally as the "log buffer") is
filled will messages throughout the execution of the kernel.
However, these messages can not be printed out to the serial
port until the kernel initializes the serial console.  When
the serial console is ready, all the messages that were previously
saved in the buffer are displayed at once.  From then on, each
message that is "printk-ed" to the buffer is both saved in the
buffer, and also immediately displayed on the console.

This explains why 1) you see no messages for a little while
before the console is initialized 2) why there is a long delay
when the console is initialized, and the previoulsy buffered
messages are drained out to the serial port (which is usually slow).
BTW  - what speed is your serial port?  On most systems, draining
the queued messages to the serial console takes less than a half

You can avoid this delay by turning off the message output to console
during booting.  By using the 'quiet' option on the kernel command
line, the messages are saved in the log buffer, but not displayed.
They can be retrieved later using the 'dmesg' command on the target
(or 'adb dmesg' on the host).  If you have printk times turned on,
you can see a timestamp on each message, which will allow you to see
when each message was printk-ed.

On some ARM systems, the kernel has the capability to print directly to the
serial port (NOT going through the log buffer).  These messages come
out on the serial console immediately when they are output by the code,
not later after buffering.

Set CONFIG_DEBUG_LL and add calls to printascii, printch and printhex.
Google CONFIG_DEBUG_LL for more information, and look at uses of
it in the kernel source tree.

I hope this helps.
 -- Tim

Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Network Entertainment


2. Apk LWP ikan koi

As subject,
Ada yang bisa japriin saya apk anipet koi livewallpaper ?
Thanks sebelumnya


"Indonesian Android Community [id-android]" 

3. Finish an activity not started from the service

4. Get a permisssion to a known source

5. java.lang.NoClassDefFoundError:

6. Area map / Area plan

7. app not working ,need help