Cannot connect to Google Maps since yesterday from ADP1

by Adrien Guichard » Sun, 01 Feb 2009 08:11:03 GMT


Sponsored Links
 since yesterday, gmap refuse to function on my ADP1. Everything else
seems to work ok. I do kill "Maps" process using Task Manager, but
this action does not change anything. I am using official RC30
version.

The only manipulation I have done yesterday is to clear Browser data,
because I was running out of space (Browser data was taken over 16MB).

Is anybody facing this issue?

--~--~---------~--~----~------------~-------~--~----~



Cannot connect to Google Maps since yesterday from ADP1

by Dave Sparks » Sun, 01 Feb 2009 12:04:43 GMT


 There was a problem that was fixed at 11:30AM PST Saturday. Let us
know if you are still experiencing problems.



--~--~---------~--~----~------------~-------~--~----~


Sponsored Links


Other Threads

1. Device unique ID, other than getDeviceId()?

I need a unique ID for each phone, just enough to distinguish it from 
any other Android phone. In theory, TelephonyManager#getDeviceId() would 
be fine, except that it requires READ_PHONE_DATA as a permission, and 
that seems overkill.

The catch is that I need this ID to be cross-application; two 
applications on the same device need to get the same ID.

So, two questions:

1. Is there some other API in Android-land that returns a unique value 
for each phone, that I just haven't found yet? One that does not require 
any special permission to access? I even considered a MAC address, but 
Android doesn't offer NetworkInterface#getHardwareAddress(), unfortunately.

2. If the answer to #1 is "no, silly", is there a spot (that I just 
haven't found yet) where I could tuck a world-readable UUID that could 
serve this purpose? It doesn't seem like there's any good 
cross-application storage spot outside of the SD card, and I can't count 
on all devices having one.

Thanks in advance!

-- 
Mark Murphy (a Commons Guy)
http://commonsware.com
_The Busy Coder's Guide to Android Development_ Version 1.3 Published!

--~--~---------~--~----~------------~-------~--~----~

2. AliasActivity: Two Questions

The AliasActivity looks interesting, as a way to redirect a user to
another activity/intent under a different name.  I can see this being
used to put a launcher icon to a document/url. But I don't see any
examples of it, or documentation of the XML to configure it.  (From
the docs: "To use this activity, you should include in the manifest
for the associated component an entry named "android.app.alias". It is
a reference to an XML resource describing an intent that launches the
real application. ")

Does anyone have any pointers?




Secondly, I think I want to make a something that acts similar to the
AliasActivity as my app's entry point, but redirects to the most
recently used activity.  Calling startActivity() followed by finish()
still invokes the activity after returning from the child activity
(its still on the activity stack, despite the finish() call), leading
to a loop that re-enters the child.  What should I be doing instead?
(I.e., What does AliasActivity do?)




Anxiously awaiting the sources so I can answer these types of
questions on my own.


Anm
--~--~---------~--~----~------------~-------~--~----~

3. Limited XML Support

4. What happens to the Intent internally after startActivity ??? (especially to Google-Developers)

5. MapView API Key??

6. get_tasks permission

7. Playing XMF files with MediaPlayer