[android-developers] DropBox
Hi Guys, I am integrate my android app with drop-box...What i need is i am get the share file/folder link now i want to know how to share that link with my friends? -- *Regards* *Arun* -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] BLE support in Android
Hi, Which is the first Android version with BLE support? In particular, Does Samsung galaxy s2 support BLE? Thanks in advance. Guillermo -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Application crashes on Formatted Android Phone
Hello Guys, I am facing awkward problem. Android Mobile Users who has formatted their handsets are not able to run my application. In rest of Android Mobiles the application is running just fine. Can anyone enlighten me what could be the possible reason and how can i over come such a problem. Thanks Regards, Krishna V. Mahadik -- -- . \\\/// . /\ . | \\ // | . ( | (.) (.) |) --o00o--(_)--o00o- Yesterday is not ours to recover, but tomorrow is ours to win or to lose. ---ooo0--- . ( ) 0ooo .\ ( ( ) . \_) ) / .(_/ -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Google seems unresponsive to reports about two adware developers I found
I am now more concerned about Electric Plasma HDhttps://play.google.com/store/apps/details?id=com.lzc.live.wallpaper.electrichl=en. It is not named identically to my app, but it is the same sort of adware/malware as the Electric Plasma Live Wallpaper knockoff and it has achieved more downloads (+50,000, compared to +10,000.) Does anyone know a way that I can contact someone at Google directly about this? -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Android 4.4 Encryption Code Not Backwards Compatible
What does key.getAlgorithm() return on 4.4 and previous versions? PBEWithSHA256And256BitAES-CBC-BC on both. What does ecipher.getProvider().getName() return on 4.4 and previous versions? BC on both (bouncy castle I guess) Note that Using Cipher.getInstance() without specifying explicitly the algorithm, mode and padding is a recipe for disaster. I thought mode was CBC, padding BC (whatever that is). I was under major time pressure when I implemented encryption :-) AlgorithmParameterSpec paramSpec = new IvParameterSpec( initVector ); Where does initVector come frome and how was it generated? An array of 8 random bytes, fixed. As is the salt. Most importantly, what encryption algorithm are you trying to use? AES. AES's block size is 16 bytes (128 bits) so there is no way it can work 8 byte (56 bit) IVs. Right, that matches with on old devices the cipher reporting the block size as 16 also. However, it's worked since 2010 on a huge variety of devices, which leads us to the conclusion that the previous implementation was doing something to adapt to the too-short IV instead of complaining, right ? So I need to find out what that something is. I'll start with filling the IV up to 16 bytes with 0s or 1s though :-) Pent -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Google seems unresponsive to reports about two adware developers I found
Michael, I suggest you just move on. You've reported those apps. There's nothing more to do. If Google eventually sees fit to remove them, then fine. If it takes them five years, that's just the way it is. -John Coryat On Tuesday, November 26, 2013 8:43:23 AM UTC-6, Michael Palmer wrote: I am now more concerned about Electric Plasma HDhttps://play.google.com/store/apps/details?id=com.lzc.live.wallpaper.electrichl=en. It is not named identically to my app, but it is the same sort of adware/malware as the Electric Plasma Live Wallpaper knockoff and it has achieved more downloads (+50,000, compared to +10,000.) Does anyone know a way that I can contact someone at Google directly about this? -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Android 4.4 Encryption Code Not Backwards Compatible
I forgot: if I pad initVector up to 16 bytes, and using the code I posted in the first post, I get this from the cipher init() call: java.security.InvalidKeyException: invalid parameter passed to AES init - com.android.org.bouncycastle.crypto.params.ParametersWithIV So it seems that PBEWITHSHA-256AND256BITAES-CBC-BC in the BC provider is not usable at all now ?! Or something else has also changed to make my code no longer valid. Pent -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Google banned AdSense account, and will not pay money earned with Paid App
Hi everybody, I have a app published for more then one year, Lumiè, for photo enchantments. So, early in Android, payments were sent to AdSense, before they migrated to Google Checkouts. Thing is, I had more then $4.000,00 in Google AdSense, but never was able to receive the money. Last month, I discovered I have to validate my account with a PIN number, but I never received the PIN number, because my account didn't reach $10. Seems insane right? I had 4000, but they didn't sent me the PIN because of $10.. Anyway, to be able to receive, I installed Google AdSense in my wife blog, hosted by Google Blogger. The process was automated, so I didn't have to do anything, just enable. Problem is, yesterday, I received a mail from Google, saying my AdSense account is banned for invalid clicks. But the thing is, the blog never was able to generate more then $5 dollars, so I'm really confused why they did that. After appealing, they rejected my appeal, and according to the AdSense FAQ, I won't be able to receive my money! So I'm really disappointed with Google, because I only used their services, and now they seem to rob me *$4.000,00* dollars!!! That's a lot of money, and I need that to live. *Anything I can do?* *Besides never, ever, developing for Google again?* -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Android 4.4 Encryption Code Not Backwards Compatible
On Wed, Nov 27, 2013 at 1:10 AM, Pent supp...@apps.dinglisch.net wrote: I forgot: if I pad initVector up to 16 bytes, and using the code I posted in the first post, I get this from the cipher init() call: java.security.InvalidKeyException: invalid parameter passed to AES init - com.android.org.bouncycastle.crypto.params.ParametersWithIV The reason it worked before is that it was probably falling back to using the IV included with the key (Cf. the class name). PBE algorithms can derive both the key and the IV from the password. So it seems that PBEWITHSHA-256AND256BITAES-CBC-BC in the BC provider is not usable at all now ?! Convert your key to a 'plain' key with something like this and is should work SecretKey sk1 = new SecretKeySpec(sk.getEncoded(), AES); Then pass sk1 to Cipher. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Android 4.4 Encryption Code Not Backwards Compatible
The reason it worked before is that it was probably falling back to using the IV included with the key (Cf. the class name). PBE algorithms can derive both the key and the IV from the password. Bingo! Changing the IV on an older device doesn't affect decryption :-) Convert your key to a 'plain' key with something like this and is should work SecretKey sk1 = new SecretKeySpec(sk.getEncoded(), AES); Yep, that fixes that error, but now the decryption fails (doFinal). I'm way out of my depth here, but does it make sense to use getIV() on the cipher on the old device and then set that as the IV on the new one ? Pent -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Android 4.4 Encryption Code Not Backwards Compatible
. no, because it's different for each passphrase. So the problem is that I'm specifying an IV at all now, so it's not doing it's internal derivation from the password ? Pent -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: Android 4.4 Encryption Code Not Backwards Compatible
Yep, that's it, if I pass a null parameter spec it can decode the old files on 4.4. Can't thank you enough for your help! Pent -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Android 4.4 Encryption Code Not Backwards Compatible
On Wed, Nov 27, 2013 at 2:53 AM, Pent supp...@apps.dinglisch.net wrote: Yep, that's it, if I pass a null parameter spec it can decode the old files on 4.4. Or just use the Cipher.init() version that takes only two parameters: ecipher.init( Cipher.ENCRYPT_MODE, key) -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [android-developers] Re: Android 4.4 Encryption Code Not Backwards Compatible
Or just use the Cipher.init() version that takes only two parameters: ecipher.init( Cipher.ENCRYPT_MODE, key) This experience has taught me to specify all possible parameters when dealing with encryption :-) Pent -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Problem signing up for Google Play for Education
My application was reviewed for Google Play for Education and had issues that needed to be addressed. I was instructed to visit developer.android.com/edu and sign uphttps://services.google.com/fb/forms/playedu but I get Internal Server Error 500 on every attempt to sign up. Has anyone else had these problems? - Cliff Davies -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: How to direct adb commands to specified device?
It seems -s works only with real devices' serial numbers (and emulator generated names, AFAIK), not with IP addresses. El miércoles, 28 de septiembre de 2011 09:32:23 UTC-3, Vasyl Boyko escribió: Hello. How to direct adb commands to specified device? I have two devices: adb devices List of devices attached 172.24.226.35: device MT-ndQmBAnwoVyC3ikKVCNc5yqC device I'm tried: adb -s MT-ndQmBAnwoVyC3ikKVCNc5yqC forward tcp:8080 tcp:8080 everything ok, but when adb -s 172.24.226.35: forward tcp:8080 tcp:8080 error: unknown host service or adb -s 172.24.226.35 forward tcp:8080 tcp:8080 error: device not found What's wrong? -- 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 unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] How do I validate an android.net.http.SslCertificate with an X509TrustManager?
Cross-Posted on Stackoverflow: http://stackoverflow.com/q/20228800/9636
Android's WebViewClient calls onReceivedSslError when it encounters an
untrusted cert. However, the SslError object I receive in that call doesn't
have any way public way to get to the underlying X509Certificate to
validate it against an existing TrustStoreManager. Looking at the source, I
can access the X509Certificate's encoded bytes thusly:
public void onReceivedSslError(WebView view, SslErrorHandler handler,
SslError error) {
Bundle bundle = SslCertificate.saveState(error.getCertificate());
X509Certificate x509Certificate;
byte[] bytes = bundle.getByteArray(x509-certificate);
if (bytes == null) {
x509Certificate = null;
} else {
try {
CertificateFactory certFactory =
CertificateFactory.getInstance(X.509);
Certificate cert = certFactory.generateCertificate(new
ByteArrayInputStream(bytes));
x509Certificate = (X509Certificate) cert;
} catch (CertificateException e) {
x509Certificate = null;
}
}
// Now I have an X509Certificate I can pass to an X509TrustManager for
validation.}
Obviously, this is private API and is fragile, though I assume it is fairly
reliable since they can't change the bundle format. Is there a better way?
In the source, I see that SslCertificate has the X509Certificate as a
member variable. Could you just make that public with a getter?
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[android-developers] Re: How do I validate an android.net.http.SslCertificate with an X509TrustManager?
Added a feature
request:
https://code.google.com/p/android/issues/detail?id=62883thanks=62883ts=1385503421
On Tuesday, November 26, 2013 3:59:41 PM UTC-6, Heath Borders wrote:
Cross-Posted on Stackoverflow: http://stackoverflow.com/q/20228800/9636
Android's WebViewClient calls onReceivedSslError when it encounters an
untrusted cert. However, the SslError object I receive in that call doesn't
have any way public way to get to the underlying X509Certificate to
validate it against an existing TrustStoreManager. Looking at the source, I
can access the X509Certificate's encoded bytes thusly:
public void onReceivedSslError(WebView view, SslErrorHandler handler,
SslError error) {
Bundle bundle = SslCertificate.saveState(error.getCertificate());
X509Certificate x509Certificate;
byte[] bytes = bundle.getByteArray(x509-certificate);
if (bytes == null) {
x509Certificate = null;
} else {
try {
CertificateFactory certFactory =
CertificateFactory.getInstance(X.509);
Certificate cert = certFactory.generateCertificate(new
ByteArrayInputStream(bytes));
x509Certificate = (X509Certificate) cert;
} catch (CertificateException e) {
x509Certificate = null;
}
}
// Now I have an X509Certificate I can pass to an X509TrustManager for
validation.}
Obviously, this is private API and is fragile, though I assume it is
fairly reliable since they can't change the bundle format. Is there a
better way?
In the source, I see that SslCertificate has the X509Certificate as a
member variable. Could you just make that public with a getter?
--
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 unsubscribe from this group and stop receiving emails from it, send an email
to android-developers+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
