Can only connect through wifi

[GoogleCodeExporter]

What steps will reproduce the problem?
1.connect to wifi (app works)
2.connect to mobile network (stops working)
3.reconnect to wifi (app works again)

What is the expected output? What do you see instead?
I expect to be able to manage my cruncher while on mobile network but I can 
only do that when connected to wifi.

What version of the product are you using?
v6.10.17.beta

What is the vendor/model of the device? What is the Android version?
Motorola Droid android 2.2 froyo

Please provide any additional information below.
I apologize if this is just a setting I wrong but I think I checked everything.

Original issue reported on code.google.com by cehler...@gmail.com on 7 Dec 2010 at 6:57

[GoogleCodeExporter]

Thank you for reporting this issue. 

Can you please provide more clarification? Which one of the following 
situations are you in?

Scenario A:
AndroBOINC is NOT connected to BOINC client. WiFi is turned OFF, MobileData 
(e.g. GPRS) is turned ON. AndroBOINC is started, connect to BOINC client is 
initated, but AndroBOINC cannot connect to BOINC client...

Scenario B:
Phone is using WiFi network (e.g. in your home), MobileData is also enabled 
(but not used because WiFi is used). AndroBOINC is started, connection to BOINC 
client is initiated and successful. Then the mobile phone detaches from WiFi 
(e.g. you walk from your home) and uses MobileData instead. Or alternatively, 
you turn off WiFi manually. The connection to BOINC client drops as the WiFi 
becomes unavailable...

Original comment by pavol.michalec@gmail.com on 7 Dec 2010 at 7:26

• Changed state: Queried

[GoogleCodeExporter]

I'm pretty sure its both scenarios. Androboinc can connect to my cruncher
when my phone is on wifi but not when I switch to mobile network.

Sent from my Droid.

MobileData

is

enabled

Original comment by cehler...@gmail.com on 7 Dec 2010 at 7:33

[GoogleCodeExporter]

Most probably you have some connectivity issues from your phone towards your 
BOINC client. This could be:
- Maybe your mobile provider does not transfer traffic to BOINC TCP-port (31416 
by default). Maybe it limits transfer only to ports 80 (http), 443 (https) and 
other commonly-used ports...
- Firewall/NAT on your home router can prevent access from internet to your 
BOINC client (and when you use your home WiFi, you are inside your home 
network). In such case also WiFi from other site than your home (e.g. from 
public WiFi hotspot) will not work.
- Your home network is not accessible from internet, because your ISP does not 
give you public IP-address, but you are behind ISP's NAT (this technique is 
more and more used by ISPs because of limited number of available IPv4 
addresses).
- Your BOINC-client can be set to accept only addresses specified in file 
remote_hosts.cfg (which is the default setting). The option 
--allow_remote_gui_rpc must be used as described in 
[http://code.google.com/p/androboinc/wiki/HowToSetup#4._Make_BOINC_client_access
ible_via_network Wiki page]

Generally, the AndroBOINC can use MobileData connection. In fact, this is the 
primary benefit of AndroBOINC, to control your BOINC when you are outdoor 
without computer access, only with mobile data network.

Now you should check the settings of your BOINC client and your router first. 
Then you can try to access your BOINC client from internet (e.g. from home of 
your friend). If it is all OK, then you should diagnose your MobileData 
connectivity. For example, if you have notebook computer and can use WiFi 
tethering of your Android phone (so you connect your notebook to internet via 
the same MobileData service as AndroBOINC uses), you can diagnose the 
connectivity, e.g via telnet access to the BOINC port, or by running original 
BOINC Manager on your notebook... 

So your issue at the moment does not seem to be AndroBOINC problem. 
Nevertheless, some small improvements can be done:
- Wiki can be updated to describe possible problems and related 
checks/solutions.
- AndroBOINC can be more descriptive about connection failure (now it only 
silently fails if there is timeout at connect), so user can have better 
understanding about the situation and possibly also hints.

So I'm re-classifying this issue from Defect to Enhancement and I plan to make 
improvements.

After you investigate the reasons and find solution, feel free to post your 
findings here, so other users could also benefit from your experience.

Original comment by pavol.michalec@gmail.com on 7 Dec 2010 at 8:39

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Wow very informative! As I have a chance to play around with it some more
I'll update the issue on your site. Keep up the good work!

Sent from my Droid.

your

http://code.google.com/p/androboinc/wiki/HowToSetup#4._Make_BOINC_client_accessi
ble_via_network

can

your

Original comment by cehler...@gmail.com on 7 Dec 2010 at 1:29

[GoogleCodeExporter]

No more comments during last 2 months - closing the issue

Original comment by pavol.michalec@gmail.com on 11 Feb 2011 at 1:44

• Changed state: Done