search

yucemahmut / android-on-freerunner

Automatically exported from code.google.com/p/android-on-freerunner
0 stars 0 forks source link

WiFi connects to AP, but no data communication #96

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. New Week 53 Cupcake
2. Connect to open WiFi network with or without fixed ip/DHCP
3. Run mail or web browser, and even though connection icon is shown, no 
data communication happens.

What is the expected output? What do you see instead?
Data connection, but getting error of "web page not available" (Browser) 
and "unable to open connection to the server" (EMail)

What version of the product are you using? On what operating system?
Week 53 Cupcake build on GT02v6

Please provide any additional information below.
GPRS works, but WiFi not.  Thus I know what to expect.  Wifi icon appears, 
but no data is transmitted.

Original issue reported on code.google.com by v4mpyr8...@gmail.com on 31 Dec 2009 at 11:06

GoogleCodeExporter commented 9 years ago 
PS. Not even using local IPs for LAN machines resolve in the browser.

Original comment by v4mpyr8...@gmail.com on 31 Dec 2009 at 11:09

GoogleCodeExporter commented 9 years ago

Original comment by larlin...@gmail.com on 16 Jan 2010 at 9:54

GoogleCodeExporter commented 9 years ago 
Interesting issue here:  If GPRS stays connected (indicator in system tray/title
bar), Wifi works.  But more times than not, the GPRS gets dropped once the WiFi 
gets
enabled.

Solutions?

Original comment by v4mpyr8...@gmail.com on 11 Mar 2010 at 6:46

GoogleCodeExporter commented 9 years ago 
Can you add your logcat and logcat -b radio?

Original comment by niels.he...@gmail.com on 11 Mar 2010 at 10:45

GoogleCodeExporter commented 9 years ago 
* Using fixed IP.  Tried it with DHCP as well, no joy.
* AP is open with only MAC ADDR security.
* WiFi worked under SHR & Hackable:1, so hardware is fine.
* In this case, GPRS was down before doing the logs.

#logcat

D/dalvikvm(  900): GC freed 1081 objects / 46568 bytes in 128ms
W/WifiHW  (  862): wifi.module_name: 
/sys/bus/platform/drivers/s3c2440-sdi/s3c2440-sdi
W/WifiHW  (  862): wifi_load_driver module_name = 
/sys/bus/platform/drivers/s3c2440-sdi/s3c2440-sdi
W/WifiHW  (  862): wifi.module_name: 
/sys/bus/platform/drivers/s3c2440-sdi/s3c2440-sdi
E/WifiHW  (  862): Unable to open connection to supplicant on "eth0": No such 
file or directory
E/WifiHW  (  862): Supplicant not running, cannot connect
V/WifiStateTracker(  862): Connection to supplicant established, state=SCANNING
V/WifiMonitor(  862): Event [Trying to associate with 00:13:46:27:75:26 
(SSID='StarshipSystems' freq=2412 MHz)]
V/WifiMonitor(  862): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=3]
V/WifiStateTracker(  862): Changing supplicant state: SCANNING ==> ASSOCIATING
V/WifiMonitor(  862): Event [CTRL-EVENT-STATE-CHANGE id=0 state=4]
V/WifiMonitor(  862): Event [Associated with 00:13:46:27:75:26]
V/WifiMonitor(  862): Event [CTRL-EVENT-STATE-CHANGE id=0 state=7]
V/WifiMonitor(  862): Event [CTRL-EVENT-CONNECTED - Connection to 
00:13:46:27:75:26 completed (auth) [id=0 id_str=]]
V/WifiStateTracker(  862): Changing supplicant state: ASSOCIATING ==> ASSOCIATED
V/WifiStateTracker(  862): Changing supplicant state: ASSOCIATED ==> COMPLETED
V/WifiStateTracker(  862): New network state is CONNECTED
V/WifiStateTracker(  862): Static IP configuration succeeded
V/WifiStateTracker(  862): IP configuration: ipaddr 192.168.0.36 gateway 
192.168.0.1 netmask 255.255.255.0 dns1 
192.168.0.1 dns2 0.0.0.0 DHCP server 0.0.0.0 lease 0 seconds
E/NetworkStateTracker(  862): Can't set tcp buffer 
sizes:java.io.FileNotFoundException: 
/sys/kernel/ipv4/tcp_rmem_min
D/WifiWatchdogService(  862): (android.server.ServerThread) StarshipSystems 
(00:13:46:27:75:26) does not require the 
watchdog
I/ActivityManager(  862): Stopping service: 
com.android.providers.downloads/.DownloadService
D/dalvikvm(  956): GC freed 307 objects / 17400 bytes in 102ms
D/dalvikvm( 1098): GC freed 10208 objects / 524016 bytes in 117ms

#logcat -b radio

D/RILJ    (  900): [0139]> SIGNAL_STRENGTH
D/RIL     (  858): onRequest: SIGNAL_STRENGTH
D/AT      (  858): MUX[primary]: AT> AT+CSQ
D/AT      (  858): MUX[primary]: AT< +CSQ: 29,0 
D/AT      (  858): MUX[primary]: AT< OK
D/RILJ    (  900): [0139]< SIGNAL_STRENGTH {29, 0}
D/GSM     (  900): setDataEnabled(true) isEnabled=true
D/RILJ    (  900): [0140]> SIGNAL_STRENGTH
D/RIL     (  858): onRequest: SIGNAL_STRENGTH
D/AT      (  858): MUX[primary]: AT> AT+CSQ
D/AT      (  858): MUX[primary]: AT< +CSQ: 29,0 
D/AT      (  858): MUX[primary]: AT< OK
D/RILJ    (  900): [0140]< SIGNAL_STRENGTH {29, 0}

# ./ifconfig eth0
eth0: ip 192.168.0.36 mask 255.255.255.0 flags [up broadcast running multicast]

TIA

Original comment by v4mpyr8...@gmail.com on 11 Mar 2010 at 8:49

GoogleCodeExporter commented 9 years ago 
PS.  Running RC1 since it came out.

Original comment by v4mpyr8...@gmail.com on 11 Mar 2010 at 8:50

GoogleCodeExporter commented 9 years ago 
Observation: I just tried a weird thing: while connected to my PC, I did a 
ifconfig 
usb0 down and Android became much less confused when it came to the WiFi.  So, 
the 
problem as routing all along.

Now the question: is there a way to switch usb0 on and off from the phone 
itself?  
I've installed Better Terminal (because the built in terminal does not want to 
accept 
the return key), but it runs without root rights.  So can't do it there...

Thx

Original comment by v4mpyr8...@gmail.com on 11 Mar 2010 at 9:27

GoogleCodeExporter commented 9 years ago 
Could anyone please add simple 'for dummies' steps to workaround this issue?  
Also according to issue 55 (terminal could not be used).

Thank you.

Original comment by bambas.jan@gmail.com on 25 Apr 2011 at 12:00

GoogleCodeExporter commented 9 years ago 
So how could that workaround for dummies look like?

Original comment by niels.he...@gmail.com on 26 Apr 2011 at 2:05

GoogleCodeExporter commented 9 years ago 
I've changed /init.gta02.rc file using adb push over USB.  Line

service usb-ether /system/bin/ifconfig usb0 192.168.0.202 

changed to

service usb-ether /system/bin/ifconfig usb0 192.168.100.202

After reboot of the device I'm not able to connect it any more (from Win7, 
properly configured RNDIS interface with address 192.168.100.200/24).  First 
ping result is Destination host unreachable and then all others Request timed 
out.  Routing tables seems to be correct (auto-configured by Win).

WiFi in Android still doesn't work.

Restarted both Android and Windows machine.

The installed default terminal doesn't allow me to look at the usb0 setting 
with ifconfig to check the change has worked or not because of either:
- cannot press enter in the terminal line (worked around by forcing quit of 
Android Soft Keyboard)
- with the other keyboard allowing enter key I cannot type numbers (this is so 
funny :))
- even I could type 'ifconfig usb0' and confirm that command I suspect 
privileges of the terminal are not su, so no luck anyway

Is there any official way to change the usb0 address to do not conflict with so 
widely used 192.168.0/24 network?

Thanks for reply.

Original comment by bambas.jan@gmail.com on 20 Oct 2011 at 9:55

GoogleCodeExporter commented 9 years ago 
Changing my NAT to a network different from 192.168.0/24 (in my case 192.168.5) 
solved the problem with WiFi.

I believe changing the usb0 network setting to a network different from 
192.168.0/24 is the solution to this bug.

Original comment by bambas.jan@gmail.com on 21 Oct 2011 at 1:08