JP

I started migrating an Android project from the old Google Maps API to
v2. Or an attempt at that, rather.
A few issues with the brand new documentation aside*), there seems to
be a substantial mismatch in the architecture, and as a result, the
vast amount of API calls and classes are not available any more?
(Somebody correct me if I am wrong). After switching the Java imports
to com.google.android.gms.maps.*, I am missing MapActivity, GeoPoint,
RecticleDrawMode and Overlay. Sure there are more. Right now a
migration to v2 seems like a pretty hopeless undertaking for anything
but the most trivial projects. Or am I completely missing the boat
here?

*)
1. Eclipse: File -> Import -> Existing... does not work: As should be
the case for release, there are no Eclipse project files in the Google
Play Services SDK, so I used New -> Project -> Android Project from
Existing Code
2. Eclipse: Reference to google-play-services_lib as a library project
results in a red cross in the referencing project properties and class
references from the project source into com.google.android.gms do not
resolve. Workaround: Include google-play-services.jar as a JAR file
reference
3. A web search for "com.google.android.gms.maps" on Google finds a
link ( https://developers.google.com/commerce/wallet/sdk/android/
reference/com/google/android/gms/maps/package-summary) but no content
there

Read more »

After not having touched it since July, I've updated one of my apps in
Google Play the other day and noticed that it was filtered out from a bunch
of devices I use for testing. There are no new features that would require
any new permissions, and the target-sdk remains at 11. (min-sdk level 3)

Turns out that Google Play in its infinite wisdom added permission requests
that aren't required for the app, at least not for the devices I've tested
it on over the years. BTW, this becomes obvious only after expanding the
version in the APK panel of the old publisher console, because only the old
console interface posts a warning about the new permission set.

With that, not only do I lose a substantial amount of reach. Even worse
perhaps, many users that already have the app installed based on the
original permissions, now fall off the upgrade path, I suppose. I'm not
going to rewrite the whole thing and go through the exercise trying to
figure out which Android SDK calls trigger user permissions adds by Google
Play. What a mess.

Anybody know a solution?

BTW, using the old interface, reactivating the July version results in the
following "error": "New APK version is lower than previous APK version."
(Well duh) and I can't delete any new upload, old interface or new. So I
can't even switch back to any of the old versions.

Read more »

I can't seem to find the Nexus 10 ADB drivers, assuming they are out
there.
- I have the SDK USB Drivers at Rev 7. (SDK Manager reports this as
the latest)
- I've installed the latest version of Kies
And yes I've enabled USB debugging on the device, but no luck.

Anybody know if the ADB drivers are out and where they are?

Read more »