Retested on Android 3.1 on Motorola Xoom - OK
Acer A500 Android 3.2 - TimeOut Error after 5-10 seconds. No matter how
Socket was configured.
Is it a bug in Mono?
Or Acer Drivers?
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/SocketError-TimedOut-tp5022774p5028605
Using 1.9.2, I either Deploy my app to Kindle Fire, or deploy via Debug. App
downloads fine and functions, but on the Kindle Fire home screen my app
shows up with a generic KF dark gray squares on light gray background.
http://mono-for-android.1047100.n5.nabble.com/file/n5028644/Test_Default_Icon
After 10,000 different tries, now it magically decides to work!!!
--
View this message in context:
http://mono-for-android.1047100.n5.nabble.com/VS-2010-Deploy-to-Kindle-Fire-Cannot-Get-App-Icon-Just-Default-Icon-tp5028644p5028669.html
Sent from the Mono for Android mailing list archive at Nabble
Hi,
Hmm, something is still not right. Are there any types which cannot be
serialized for Android?
Currently, I have this
[Serializable()]
public class common
{
public int p, a, w, pa;
public double bodyWeight, tempBody, tempSurround;
public double[,] correcti
On Nov 27, 2011, at 4:34 PM, Axel Busch wrote:
> Hi Jon. I don't remember how high the count went. If you think it's valuable
> at this time, I can run the code on a few different devices and android
> versions.
I would suggest just waiting for the next release, and retrying your fuller
tests.
