not exactly
i experience this same problem on my slow 3G (Megafon) connection too,
but don't have this on WIFI or wire network.

but! if i connect my laptop to internet via my phone (winmobile 6.5)
3g connection, it works perfect. a bit slow, but none of content i see
on laptop is corrupt.
i haven't really tried to connect laptop via android phone though.

so it's definitely not a problem with internet provider. and basically
this all sounds fantastic. tcp has error correction and it shouldn't
corrupt data by any means. but what i see is what i see.. it's
strange, but it is happening

On 16 фев, 12:13, Kostya Vasilyev <kmans...@gmail.com> wrote:
> Alex,
>
> Ok, let's see if I understand it:
>
> - Your clients are having this problem with data corruption;
>
> - You are not having this problem, the code works just fine every time.
>
> Right? If so, let me go on:
>
> - Your clients use some kind of "slow WiFi" and experience data
> corruption between the phone and the server;
>
> - You have logged what you send, and the data you send is correct.
>
> If those are the facts, then
>
> - It's a problem with your client's network.
>
> Wikipedia says there is only one internet (and mobile) provider in
> Andorra, perhaps your clients could drive a few miles into France or
> Spain, find a McDonalds with free WiFi, and test your application there?
>
> -- Kostya
>
> 16.02.2011 11:56, alex c пишет:
>
>
>
> > yeah. i tried it with WIFI and via tethering through usb to my laptop
> > pppoe connection. and it works. fine.
> > but the problem is that my clients use quite slow wifi connection in
> > Andorra and they have this same issue and images they upload though
> > app get almost 100% corrupt.
>
> > as for htc hd2 - yeah, you are correct. it's 3rd party firmware, but
> > at least it is something real and not an emulator (which, in fact,
> > works perfect via pppoe connection).
> > my cilents are using samsung galaxy tab (as i mentioned in the first
> > post) with android 2.2 and having same issue. this is why i started to
> > investigate it and finished up with this post.
>
> > as for mime type headers - i was just experimenting with it, thinkign
> > that maybe it was due to incorrect mime type before i switched to
> > base64 and had these stange results. btw, 2 times i got an extremely
> > strange result: i found  pieces of some crap texts in the base64 post
> > (at apache's end). and it seems like with this big MTU value the
> > device (or some router on the path) messes tcp packets from different
> > sections.
>
> > i was thinking about wrong MTU path discovery implementation in froyo,
> > or something like this...
>
> > On 16 фев, 00:36, Kostya Vasilyev<kmans...@gmail.com>  wrote:
> >> Alex,
>
> >> I don't think you need to call addHeader with the content type here.
>
> >> Other than that, have you tried testing with different network
> >> connectivity options? (mobile with different networks, WiFi though
> >> different routers).
>
> >> Finally, you mentioned an HTC HD2 - that's a Windows Mobile phone, are
> >> you testing your code with a custom Android build made for that phone?
> >> If that's the case and you didn't mean the Desire HD, try a device that
> >> has vendor-supplied Android firmware.
>
> >> -- Kostya
>
> >> 14.02.2011 10:25, alex c пишет:
>
> >>>                     HttpPost post = new HttpPost(uri);
> >>>                     post.addHeader(entity.getContentType());
> >>>                     post.setEntity(entity);
> >>>                     HttpResponse resp = mHttpClient.execute(post);
> >> --
> >> Kostya Vasilyev --http://kmansoft.wordpress.com
>
> --
> Kostya Vasilyev --http://kmansoft.wordpress.com

-- 
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

Reply via email to