Re: [android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
Hi mendhak, did you solve this problem? Were you able to get the MD5 Certificate Fingerprint of your app programmatically? Any directions on how to achieve this please? -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
Hi Dude, follow this link .. it will work http://blogspot.fluidnewmedia.com/2009/04/displaying-google-maps-in-the-android-emulator/ On Wed, Jun 8, 2011 at 6:37 PM, Dom dominicmarm...@gmail.com wrote: Hi mendhak, did you solve this problem? Were you able to get the MD5 Certificate Fingerprint of your app programmatically? Any directions on how to achieve this please? -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
Actually, I (and mendhak's original post) would like to get the MD5 fingerprint via CODE or PROGRAMMATICALLY. Getting it via the keytool is well documented in tonnes of places across the web. I would like to implement an architecture similar to google maps api. The way google maps authorizes requests for each map tile is by the requesting app to send up its apiKey from the xml layout and also send up the fingerprint of the app that is using the maps. What I can't figure out is how does the app using the maps send its fingerprint? (code example please) This seems to be a big mystery of the google maps api because I've scoured the internet and found nothing. Thanks for your reply! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
On Wed, Jun 8, 2011 at 10:54 PM, Dom dominicmarm...@gmail.com wrote: Actually, I (and mendhak's original post) would like to get the MD5 fingerprint via CODE or PROGRAMMATICALLY. Getting it via the keytool is well documented in tonnes of places across the web. Simply use the MessageDigest class to calculate the hash. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
3 Sent from my Verizon Wireless Phone -Original message- From: Nikolay Elenkov nikolay.elen...@gmail.com To: android-developers@googlegroups.com Sent: Wed, Jun 8, 2011 11:46:52 GMT-03:00 Subject: Re: [android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code? On Wed, Jun 8, 2011 at 10:54 PM, Dom dominicmarm...@gmail.com wrote: Actually, I (and mendhak's original post) would like to get the MD5 fingerprint via CODE or PROGRAMMATICALLY. Getting it via the keytool is well documented in tonnes of places across the web. Simply use the MessageDigest class to calculate the hash. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
On Thu, Jun 9, 2011 at 12:21 AM, Dom dominicmarm...@gmail.com wrote:
Got it, thanks! Here's the snippet of code:
Signature[] sigs =
getBaseContext().getPackageManager().getPackageInfo(getPackageName(),
PackageManager.GET_SIGNATURES).signatures;
for(Signature sig : sigs)
{
byte[] hexBytes = sig.toByteArray();
MessageDigest digest = MessageDigest.getInstance(MD5);
byte[] md5digest = new byte[0];
if(digest != null)
{
You can skip the null check, getInstance() will throw an exception if
the specified algorithm cannot be found. Also, AFAIK, there is
only one Signature (actually certificate), so you just get sigs[0]
and skip the for loop.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
Got it, thanks! Here's the snippet of code:
Signature[] sigs =
getBaseContext().getPackageManager().getPackageInfo(getPackageName(),
PackageManager.GET_SIGNATURES).signatures;
for(Signature sig : sigs)
{
byte[] hexBytes = sig.toByteArray();
MessageDigest digest = MessageDigest.getInstance(MD5);
byte[] md5digest = new byte[0];
if(digest != null)
{
md5digest = digest.digest(hexBytes);
StringBuilder sb = new StringBuilder();
for(int i = 0; i b.length; ++i)
{
sb.append((Integer.toHexString((b[i] 0xFF) |
0x100)).substring(1, 3));
}
String fingerprintMD5 = sb.toString();
}
}
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
Re: [android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
Ok, cool, thanks! -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
[android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
I'm curious as to whether these are always the same, or generated for us and unique to each SDK install, but I'm not going to look just now. It definitely varies - I use several boxes for development (my older laptop retired to mother in law house ;) ) and I have to uninstall apps compiled with debug keys before I can start them from other box. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using remove me as the subject.
Re: [android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
On Sun, Apr 11, 2010 at 6:08 AM, ko5tik kpriblo...@yahoo.com wrote: It definitely varies - I use several boxes for development (my older laptop retired to mother in law house ;) ) and I have to uninstall apps compiled with debug keys before I can start them from other box. I believe that the debug key is based on the relative path from your project to the folder where you installed the Android SDK. I used to have this same problem of having to uninstall my app when switching machines until I moved the SDK to within my project's root, such that the relative path from the project was the same on both machines. After that I no longer have to uninstall and reinstall when switching machines and the debug Maps API key generated for both is the same. - TreKing - Chicago transit tracking app for Android-powered devices http://sites.google.com/site/rezmobileapps/treking -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using remove me as the subject.
[android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
Hi, thanks for responding. I had a look, and yes, the bytes were the same as the 979 character string (hex) - they contained the certificate itself. I should post it here anyways, since it is the debug certificate in this case. Well, here it is: -- 308201e53082014ea00302010202044baf98bc300d06092a864886f70d01010505003037310b30090603550406130255533110300e060355040a1307416e64726f6964311630140603550403130d416e64726f6964204465627567301e170d3130303332383137353832305a170d3131303332383137353832305a3037310b30090603550406130255533110300e060355040a1307416e64726f6964311630140603550403130d416e64726f696420446562756730819f300d06092a864886f70d010101050003818d0030818902818100c571d5da04aacec883134f20a27b9fe73a7fab49a31443885d4ddd979fa61084bb54110d597857cd1c80429ccb3d8dacef702e5c006856399ddd5b61630b59c6632dc5af8698a5fe4dd5795b93bc41814adf92bb81867bbf69f9f051325862651dae28f9483fdded978e5d4497da365f8cf9cbeb50dd67ab114be08587347fad0203010001300d06092a864886f70d010105050003818100af92d2bf20aaebe83761bb73d4e3cd240b2e96f23d43d4cbc33db5d8e1090dbd5fbb43ae45924dbda6f961b2f06b00304c39ed68c382134a507101a9eaa23f480cac7563aa54fb507bdf9433a2f5e015a9a23dbb6de1a0a7c8f2f8f6a2ee522faaff4c73767b22581572e55c40726f2c41b21b31cd309d5bed9b4a568cdf2665 -- If you run it through a tool like this: http://home2.paulschou.net/tools/xlate/ You'll see gibberish interspersed with words like Android and Debug. That definitely looks like the certificate to me, not that I'm a certificate expert. I'm still wondering how the maps API does it. If it's something that they're keeping secret, fair enough I guess, would've been nice. But still an interesting problem. On Apr 6, 12:10 am, Bob Kerns r...@acm.org wrote: Actually, the package manager would be able to check using the API. The only thing that was at question was whether the byte sequence included anything beyond the certificate or not. We know the API doesn't. Actually, what I'd like to know is whether it includes the certificate, or just the public key from the certificate! You've effectively answered the first question, at least for now. But since the API doesn't say -- you can't really depend on the bytes anyway. All you can really do with them is the comparison. The issues around being able to keep secrets within an application are pretty deep. Let's just say it's never been made practical and robust. On Apr 5, 11:20 am, ko5tik kpriblo...@yahoo.com wrote: On Apr 5, 6:09 pm, Bob Kerns r...@acm.org wrote: Hashcode would not be secure. That is, you can construct an alternate app+signature that would produce the same hash code. That may be good enough for you, but I would discourage such a technique. However, you could construct a secure SHA-1 hash of the value! The problem is, that every other application can also read this signature and produce hash out of it... Unfortunately, the contract given for PackageManager does not even guarantee that you'd get the same 979-character string consistently, even for the same version of the same application. I'd be quite surprised if you didn't. A more relevant question is if you get the same value for two different versions of your app. If they include the hash portion of the signature, and its encrypted counterpart, then the answer is no. I checked - it was the same. Otherwise market app/installer would be unable to check whether you are upgrading existing application. or user, yes, but application, no. Nothing in a .apk can be regarded as secret. ... It would be cool feature request for android. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using remove me as the subject.
[android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
OK, converting to base64 (using your link), formatting it as a certificate file, and using openssl to parse the result, we get to see the actual content: Certificate: Data: Version: 3 (0x2) Serial Number: 1269799100 (0x4baf98bc) Signature Algorithm: sha1WithRSAEncryption Issuer: C=US, O=Android, CN=Android Debug Validity Not Before: Mar 28 17:58:20 2010 GMT Not After : Mar 28 17:58:20 2011 GMT Subject: C=US, O=Android, CN=Android Debug Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public Key: (1024 bit) Modulus (1024 bit): 00:c5:71:d5:da:04:aa:ce:c8:83:13:4f:20:a2:7b: 9f:e7:3a:7f:ab:49:a3:14:43:88:5d:4d:dd:97:9f: a6:10:84:bb:54:11:0d:59:78:57:cd:1c:80:42:9c: cb:3d:8d:ac:ef:70:2e:5c:00:68:56:39:9d:dd:5b: 61:63:0b:59:c6:63:2d:c5:af:86:98:a5:fe:4d:d5: 79:5b:93:bc:41:81:4a:df:92:bb:81:86:7b:bf:69: f9:f0:51:32:58:62:65:1d:ae:28:f9:48:3f:dd:ed: 97:8e:5d:44:97:da:36:5f:8c:f9:cb:eb:50:dd:67: ab:11:4b:e0:85:87:34:7f:ad Exponent: 65537 (0x10001) Signature Algorithm: sha1WithRSAEncryption af:92:d2:bf:20:aa:eb:e8:37:61:bb:73:d4:e3:cd:24:0b:2e: 96:f2:3d:43:d4:cb:c3:3d:b5:d8:e1:09:0d:bd:5f:bb:43:ae: 45:92:4d:bd:a6:f9:61:b2:f0:6b:00:30:4c:39:ed:68:c3:82: 13:4a:50:71:01:a9:ea:a2:3f:48:0c:ac:75:63:aa:54:fb:50: 7b:df:94:33:a2:f5:e0:15:a9:a2:3d:bb:6d:e1:a0:a7:c8:f2: f8:f6:a2:ee:52:2f:aa:ff:4c:73:76:7b:22:58:15:72:e5:5c: 40:72:6f:2c:41:b2:1b:31:cd:30:9d:5b:ed:9b:4a:56:8c:df: 26:65 I'm curious as to whether these are always the same, or generated for us and unique to each SDK install, but I'm not going to look just now. The other interesting thing to know would be whether the comparison compares the entire value, or just the public key. On Apr 10, 12:49 am, mendhak mend...@gmail.com wrote: Hi, thanks for responding. I had a look, and yes, the bytes were the same as the 979 character string (hex) - they contained the certificate itself. I should post it here anyways, since it is the debug certificate in this case. Well, here it is: -- 308201e53082014ea00302010202044baf98bc300d06092a864886f70d01010505003037310 b30090603550406130255533110300e060355040a1307416e64726f69643116301406035504 03130d416e64726f6964204465627567301e170d3130303332383137353832305a170d31313 03332383137353832305a3037310b30090603550406130255533110300e060355040a130741 6e64726f6964311630140603550403130d416e64726f696420446562756730819f300d06092 a864886f70d010101050003818d0030818902818100c571d5da04aacec883134f20a27b9fe7 3a7fab49a31443885d4ddd979fa61084bb54110d597857cd1c80429ccb3d8dacef702e5c006 856399ddd5b61630b59c6632dc5af8698a5fe4dd5795b93bc41814adf92bb81867bbf69f9f0 51325862651dae28f9483fdded978e5d4497da365f8cf9cbeb50dd67ab114be08587347fad0 203010001300d06092a864886f70d010105050003818100af92d2bf20aaebe83761bb73d4e3 cd240b2e96f23d43d4cbc33db5d8e1090dbd5fbb43ae45924dbda6f961b2f06b00304c39ed6 8c382134a507101a9eaa23f480cac7563aa54fb507bdf9433a2f5e015a9a23dbb6de1a0a7c8 f2f8f6a2ee522faaff4c73767b22581572e55c40726f2c41b21b31cd309d5bed9b4a568cdf2 665 -- If you run it through a tool like this:http://home2.paulschou.net/tools/xlate/ You'll see gibberish interspersed with words like Android and Debug. That definitely looks like the certificate to me, not that I'm a certificate expert. I'm still wondering how the maps API does it. If it's something that they're keeping secret, fair enough I guess, would've been nice. But still an interesting problem. On Apr 6, 12:10 am, Bob Kerns r...@acm.org wrote: Actually, the package manager would be able to check using the API. The only thing that was at question was whether the byte sequence included anything beyond the certificate or not. We know the API doesn't. Actually, what I'd like to know is whether it includes the certificate, or just the public key from the certificate! You've effectively answered the first question, at least for now. But since the API doesn't say -- you can't really depend on the bytes anyway. All you can really do with them is the comparison. The issues around being able to keep secrets within an application are pretty deep. Let's just say it's never been made practical and robust. On Apr 5, 11:20 am, ko5tik kpriblo...@yahoo.com wrote: On Apr 5, 6:09 pm, Bob Kerns r...@acm.org wrote: Hashcode would not be secure. That is, you can construct an alternate app+signature that would produce the same hash code. That may be good enough for you, but I would discourage such a technique. However, you could construct a secure SHA-1 hash of the value! The problem is,
[android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
Still struggling with this. Based on what you said, I tried playing with this: Signature[] sigs = getBaseContext().getPackageManager().getPackageInfo(com.whatever.blahpackage, 64).signatures; (64 = GET_SIGNATURE) I then had a look at sigs[0].toCharsString() which produced a 979 character long string! Is hashCode() of any use here? I ignored it for now. I also had a look at toByteArray(), by converting it to a String. The result was a string that contained some readable ASCII characters and some gobbledygook characters like 0� �0� N� I'm wondering if toCharsString is what we're actually looking for, but that's a huge amount of text to be sending along with the request! Would hashCode do? On Mar 31, 2:46 pm, ko5tik kpriblo...@yahoo.com wrote: I'm also gnawing on the same problem. At the moment I'm investigating following path: Context - Package Manager - Package info (for name, with signatures ) - Signatures -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using remove me as the subject.
[android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
Well, first, there's likely to be no MD5 hash involved at all. DSA with SHA-1 would be the default signature type now, I believe. Hashcode would not be secure. That is, you can construct an alternate app+signature that would produce the same hash code. That may be good enough for you, but I would discourage such a technique. However, you could construct a secure SHA-1 hash of the value! The documentation for android.content.pm.Signature states that it is opaque. That means -- you're not supposed to know or try to figure out what's in it. I imagine the 979 characters include the hex or base 64 encoding of the signing certificate. I am not sure if it actually contains the signature! The purpose appears to be to compare WHO signed it, not the actual individual signature. Everywhere the PackageManager documentation refers to a signature, it is talking about seeing if two packages have the same signature. That would imply it is ignoring the hash, if it is even present in the datastructure. (It could ignore the hash after verifying the application). We could find out by comparing the Signature for two apps that have been signed with the same key. Unfortunately, the contract given for PackageManager does not even guarantee that you'd get the same 979-character string consistently, even for the same version of the same application. I'd be quite surprised if you didn't. A more relevant question is if you get the same value for two different versions of your app. If they include the hash portion of the signature, and its encrypted counterpart, then the answer is no. I wish the semantics were better documented here. However, you can include whatever you want in your manifest in metadata. Why not just put your key there? Even if you are seeking to tie it to your specific app, there's nothing that would prevent an intruder from computing the same values with your app and then using them from his app. There IS no secure way to guarantee that a request comes from a specific application. A particular uncompromised device or user, yes, but application, no. Nothing in a .apk can be regarded as secret. On Apr 5, 5:33 am, mendhak mend...@gmail.com wrote: Still struggling with this. Based on what you said, I tried playing with this: Signature[] sigs = getBaseContext().getPackageManager().getPackageInfo(com.whatever.blahpacka ge, 64).signatures; (64 = GET_SIGNATURE) I then had a look at sigs[0].toCharsString() which produced a 979 character long string! Is hashCode() of any use here? I ignored it for now. I also had a look at toByteArray(), by converting it to a String. The result was a string that contained some readable ASCII characters and some gobbledygook characters like 0 0 N I'm wondering if toCharsString is what we're actually looking for, but that's a huge amount of text to be sending along with the request! Would hashCode do? On Mar 31, 2:46 pm, ko5tik kpriblo...@yahoo.com wrote: I'm also gnawing on the same problem. At the moment I'm investigating following path: Context - Package Manager - Package info (for name, with signatures ) - Signatures -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using remove me as the subject.
[android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
On Apr 5, 6:09 pm, Bob Kerns r...@acm.org wrote: Hashcode would not be secure. That is, you can construct an alternate app+signature that would produce the same hash code. That may be good enough for you, but I would discourage such a technique. However, you could construct a secure SHA-1 hash of the value! The problem is, that every other application can also read this signature and produce hash out of it... Unfortunately, the contract given for PackageManager does not even guarantee that you'd get the same 979-character string consistently, even for the same version of the same application. I'd be quite surprised if you didn't. A more relevant question is if you get the same value for two different versions of your app. If they include the hash portion of the signature, and its encrypted counterpart, then the answer is no. I checked - it was the same. Otherwise market app/installer would be unable to check whether you are upgrading existing application. or user, yes, but application, no. Nothing in a .apk can be regarded as secret. ... It would be cool feature request for android. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using remove me as the subject.
[android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
Actually, the package manager would be able to check using the API. The only thing that was at question was whether the byte sequence included anything beyond the certificate or not. We know the API doesn't. Actually, what I'd like to know is whether it includes the certificate, or just the public key from the certificate! You've effectively answered the first question, at least for now. But since the API doesn't say -- you can't really depend on the bytes anyway. All you can really do with them is the comparison. The issues around being able to keep secrets within an application are pretty deep. Let's just say it's never been made practical and robust. On Apr 5, 11:20 am, ko5tik kpriblo...@yahoo.com wrote: On Apr 5, 6:09 pm, Bob Kerns r...@acm.org wrote: Hashcode would not be secure. That is, you can construct an alternate app+signature that would produce the same hash code. That may be good enough for you, but I would discourage such a technique. However, you could construct a secure SHA-1 hash of the value! The problem is, that every other application can also read this signature and produce hash out of it... Unfortunately, the contract given for PackageManager does not even guarantee that you'd get the same 979-character string consistently, even for the same version of the same application. I'd be quite surprised if you didn't. A more relevant question is if you get the same value for two different versions of your app. If they include the hash portion of the signature, and its encrypted counterpart, then the answer is no. I checked - it was the same. Otherwise market app/installer would be unable to check whether you are upgrading existing application. or user, yes, but application, no. Nothing in a .apk can be regarded as secret. ... It would be cool feature request for android. -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using remove me as the subject.
[android-developers] Re: How do I get the MD5 fingerprint of my application certificate through code?
I'm also gnawing on the same problem. At the moment I'm investigating following path: Context - Package Manager - Package info (for name, with signatures ) - Signatures -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using remove me as the subject.
