On Dec 8, 2011, at 5:40 AM, tsukrov wrote:
>> Or are you testing on different devices with different Android versions,
> and it only fails on the Acer A500 running Android v3.2?
>
> Yup. My co-worker allegedly could not reproduce the bug on Xoom with 3.1.
> It's easy to reproduce by me.
We have
> Or are you testing on different devices with different Android versions,
and it only fails on the Acer A500 running Android v3.2?
Yup. My co-worker allegedly could not reproduce the bug on Xoom with 3.1.
It's easy to reproduce by me.
Same WLAN network, same build.
Need to investigate further
On Nov 25, 2011, at 8:23 AM, tsukrov wrote:
> I'm receiving often a *SocketError.TimedOut* from *ReceiveAsync* in a
> multi-threaded Mono App on Android 3.2.
> Android 2.1 & Android 2.3 works fine.
In re-reading this, I'm not sure I understand. Are you saying that when you
build against TargetFra
Thanks for the answer.
Nope, it's not a HTTP-connection. It's a custom socket connection.
It's something like that (pseudo code):
{...
socket.Completed += OnRecv;
socket.ReceiveAsync();
..}
void OnRecv(args)
{
if(args.SocketError != NoError)
{
HandleData();
socket.ReceiveAs
On Nov 28, 2011, at 6:41 AM, tsukrov wrote:
> 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?
I would suggest that you try the same URL within Browser, and see how that
works. If it's an https URL, it could
On Nov 25, 2011, at 8:23 AM, tsukrov wrote:
> I'm receiving often a *SocketError.TimedOut* from *ReceiveAsync* in a
> multi-threaded Mono App on Android 3.2.
> Android 2.1 & Android 2.3 works fine.
Have you tried opening the same URL from Browser? Does it load in Browser as
well?
I'm not aware o
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
Hi!
I'm receiving often a *SocketError.TimedOut* from *ReceiveAsync* in a
multi-threaded Mono App on Android 3.2.
Android 2.1 & Android 2.3 works fine.
I link armeabi-7va.
Can it be something connected to runtime multi-threading issues?
--
View this message in context:
http://mono-for-android
