angeloh / chrometophone

Automatically exported from code.google.com/p/chrometophone
0 stars 0 forks source link

WiFi not working, 3G is okay. #15

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
using wifi cannot receive the urls.

But 3G does.

Please fix.

Thanks for the great app.

Original issue reported on code.google.com by tangts...@gmail.com on 23 May 2010 at 1:18

GoogleCodeExporter commented 9 years ago
Working fine for me over WiFi.

Original comment by arant...@gmail.com on 23 May 2010 at 10:53

GoogleCodeExporter commented 9 years ago
Perhaps the WiFi you were connected to doesn't allow traffic through on the 
port being 
used by Chrome to Phone? I just tested this connected to a WiFi hotspot that 
doesn't 
allow much other than port 80, 443 and 53 and it didn't work. When I 
reconnected to the 
cellular network I received all the links I had sent.

Original comment by daniel.c...@gmail.com on 24 May 2010 at 1:29

GoogleCodeExporter commented 9 years ago
The message subsystem requires a TCP connection to be made with the device, 
which is being blocked by your 
WiFi firewall. 

Original comment by burke.da...@gmail.com on 24 May 2010 at 10:51

GoogleCodeExporter commented 9 years ago
Hmm, how about a pull-mode fallback that the android side can use?

Original comment by nils.me...@gmail.com on 2 Jun 2010 at 1:35

GoogleCodeExporter commented 9 years ago
If we can't make a TCP connection from device to ours servers - what could the 
pull-
mode use ? 
C2DM uses the same path with gmail/contacts sync, talk, market - all will 
probably 
fail if the firewall is blocking it. 

Original comment by costin on 2 Jun 2010 at 2:39