There are plenty of wifi issue not turning on under this forum, a lot of them were resolved by turning on and off, reload rom etc. But I narrowed down to some question possibly hardware related and need some clarification on settings.
I am playing with a old HP touchpad (I know it has it's own forum) and wifi was working on a older android mod. After a certain time left the machine, I dug it out recently to use it and wifi is "suck at the turning on phase". Android will also goes into a boot loop after 30 sec after boots.
So I went to recovery and looking at the hardware address , numbers and settings and discover few things.
The adaptor name is not the typical eth0, it's call dummy0. Also there is something call "lo" Link encap:Local Loopback under the hardware.
Here are the numbers:
dummy0 Link encap:Ethernet HWaddr DAlB0:37:5E:9F:93
BROADCASTS NOARP MTU:1500 METRIC:1
(follow by a bunch of 0s on RX packets etc etc)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 METRIC:1
(follow by a bunch of 0s on RX packets etc etc)
Now looking at this information, the dummy0 should be the wifi adapter information right? What is broadcast NOARP means?
I have tried to turn on the dummy0 device and it will show UP Broadcast, also turning on ARP (I read somewhere this should be default) and after booting back into android, these settings will revert back to the information above.
Can anyone shine a light on if this is the right place poking at the wifi adapter setting or it's some type of hardware failure causing the wifi not turning on?
The Wi-Fi settings are stored in Android's settings.db located at
/data/data/com.android.providers.settings/databases.
Note that you cannot access it unless you have root.
The SSIDs and passwords of the Wi-Fi networks are stored to
/data/misc/wifi/wpa_supplicant.conf
HTH
Related
I'm using a Samsung Fascinate with AOKP Milestone 5 by Stephen.k.spear.
My second device is an Asus Transformer TF-101 running Megatron CM9 based ROM by ricardopvz.
I use WiFi Tether for Root that is no longer beta and available on the market so I have the newest version. My WiFi tether set up options that are pertinent to this post are as follows:
1. Change Device Profile
a. Samsung Galaxy Nexus (CDMA/LTE)
2. Change Setup Method
a. Netd (master)
3. Change LAN
a. 192.168.1.0/24
4. Routing Fix
a. Routing fix is NOT enabled
5. Default DNS settings
I have no issues tethering, it works very well, very fast. I can ping by hostname from each device while tethered. I have set both device name entries in the host file.
My issue while tethering: When I run netstat on the Transformer, I can see that wlan0 is listening on port 139(NetBIOS) and 445(SMB). However, when I netstat on the Fascinate, it is NOT listening to either of these ports. I use the Samba app available from the market and have configured all the appropriate settings for both devices.
Using the ip route command, I can see that both devices show appropriate routing on 192.168.1.x to the appropriate adapter (wlan0).
Why won't the Fascinate listen for the two ports when the adapter (wlan0) appears to be working fine, routing is good, pinging by NetBIOS name from the hosts file, and Samba is broadcasting NetBIOS and SMB?
My purpose for this post and the questions is to be able to perform wireless syncing between the two devices and a computer for various directories like Pictures and Documents. I want all three devices to be the same. If I go home and connect to WiFi the IP addresses will change and I will constantly have to adjust settings. I'm looking for a seamless option because I use tether almost as much as I use home WiFi.
I figured it out. WiFi Tether app creates a rule with iptables called wireless-tether. It's regenerated each time the app starts by using the tether.edify file in the app's data directory. If you edit the firewall rule it will default back after the app starts again. I have emailed the dev to see if they can allow some user options so the traffic can pass internally such as netbios and samba.
The default linux rules allow all traffic which is why netstat on the tablet passes netbios and smb. The tablet is connecting wirelessly with no changes to iptables.
Also, standard home wifi on the phone would also pass the traffic because no additional rules to the iptables are being made.
Hi, guys, here's my problem.
My Galaxy S2 using my own WiFi is unable to retrieve some content from web. This content is:
apps icons in Android Market,
Picasa images,
Accuweather forecasts
and some others.
Other devices using the same WiFi has no problems with it. S2 switched to other ISP than my WiFI also has no problems with it.
While trying to narrow possible causes I've picked an example image, which is problematic to my S2+WiFI combination:
https://lh3.ggpht.com/NpoJbnyQbI1kEIlrWhP_t7lj9lN519RkPB3mxQS2z6pTFjh01R3ISeyYnj4AccBSsQ=w788 (an icon of an app from Adroid Maret, remove space from url).
It won't open on my phone using WiFi, so I checked host availability. I've run on my phone following command:
Code:
[email protected]:/ $ ping lh3.ggpht.com
ping: unknown host lh3.ggpht.com
But on my PC using the very same WiFi:
Code:
C:\Users\Grzegorz>ping lh3.ggpht.com
Badanie photos-ugc.l.google.com [173.194.70.132] z 32 bajtami danych:
Odpowiedź z 173.194.70.132: bajtów=32 czas=27ms TTL=47
Odpowiedź z 173.194.70.132: bajtów=32 czas=25ms TTL=47
I'm stuck, what should I do now?
Have you any ad blockers or DNS stuff running ???
jje
Nope, it's clean Android 4.0.3.
Echo request for lh3.ggpht.com on your phone does not work. On your PC you get a response from 173.194.70.132. Just to make sure your problem is related to DNS (and not to some lower service): did you try to ping the IP address 173.194.70.132 from your phone? Do you get a response?
Yes, the host is reachable from phone using IP dot address, only name resolving does not work.
Ok, looks definitely like some DNS problem. As you already confirmed that your hosts file is fine the only thing I can imagine is your phone using some 'wrong' DNS server for address lookup.
To make (almost) sure you use a set of different DNS servers you could disconnect your phone from the wifi and enable a 3G data connection. Make absolutely sure you are not connected to your wifi. Now again run 'ping lh3.ggpht.com'; do you get a response?
Yes, that is the case.
Another weird thing is that phone on 3G resolves lh3.ggpht.com as 173.194.35.139, while PC on WiFi as 209.85.148.132. My 'hosts' file contains only localhost reference.
When I switch to WiFi while pinging that host, pings keep successful, unless I restart terminal session — after that I get 'unknown host' message.
Is there DNS configuration in Android somewhere?
OK, it seems I fixed it.
My WiFi works in a bigger subnet and hides all connected WiFi devices as as single computer.
I've installed on my Phone app called Set DNS from former Android Market, which allowed me to change both primary and secondary DNS. Initally both addresses were pointing to WiFi router itself which seems to work fine for my PC. I've changed it to DNSes of that bigger subnet I'm connected to. And it did the trick. Hopefully it won't mess settings for other WiFis I use to connect.
Thanks for showing me right direction!
I mean this is stupid... you can have IPv6 APN and everything, but on WIFI you cant get IPv6 address... I have dualstack LAN at home, every client should get local IPv4 address and public IPv6. But for some silly reason Google decided to not include this in to ICS, but since there is support for UMTS IPv6 APNs it should WORK technically... This works flawlessly on iPhone4S and other clients (read computers) that supports IPv6 on my LAN...
From what I can see, ICS manages to configure a IPv6 global address on its wlan0 interface via autoconfiguration.
Looking at results from tcpdump and other command line tools, there seem to be two other problems:
1) Even though there is a router on the LAN sending router advertisements and the device configures its address, it does not seem to install or use the the default gateway. I am able to ping the phone via IPv6 on the same local /64 global, and its link local, and am able to ping those devices back from the device (ping6 via busybox). I cannot however ping past the local IPv6 global network.
2) None of the web browsers on the phone I have tried seem to be doing AAAA lookups. Confirmed tcpdump, even when trying to resolve names that only have AAAA records, the request only ever goes out for an A record and never a AAAA.
I was able to run a web server on the same local /64 the phone was configured on, and was able to browse to it by its IPv6 address directly through the browser. So it does work, just missing the default route and AAAA DNS functionality it seems.
As an FYI this was tested on a rooted Galaxy S3 SGH-I747M running 4.0.4. I'm assuming the IPv6 functionality wouldn't be any different between this and the SII, but maybe I'm wrong.
themikea said:
1) Even though there is a router on the LAN sending router advertisements and the device configures its address, it does not seem to install or use the the default gateway. I am able to ping the phone via IPv6 on the same local /64 global, and its link local, and am able to ping those devices back from the device (ping6 via busybox). I cannot however ping past the local IPv6 global network.
Click to expand...
Click to collapse
I have a Galaxy S3 SPH-L710 running Android 4.0.4, and I had the same problem with it not configuring the default IPv6 route. There is a sysctl variable that controls whether the Linux kernel automatically adds the default route advertised in the IPv6 Router Advertisement messages, and it defaults to 0 (off) on the phone. Look at /proc/sys/net/ipv6/conf/default/accept_ra_defrtr.
themikea said:
2) None of the web browsers on the phone I have tried seem to be doing AAAA lookups. Confirmed tcpdump, even when trying to resolve names that only have AAAA records, the request only ever goes out for an A record and never a AAAA.
Click to expand...
Click to collapse
When I set accept_ra_defrtr to 1 and cycled my Wi-Fi connection, it came back up and added the default IPv6 route. Now test-ipv6.com on my phone gives me a 10/10 on both IPv4 and IPv6, meaning the DNS resolver is asking for AAAA records too and even preferring them when a host has both A and AAAA, which is the recommended and desired behavior. Loading comcast6.net on my phone shows my IP address as an IPv6 address.
Trouble is, setting sysctl variables in /proc/sys will not survive through a reboot, and there is no /etc/sysctl.conf on Android, so I don't know where to stash this setting so it gets applied on every boot. There is no file anywhere in /system that contains "accept_ra_defrtr" except for the vpnclient.ko kernel module, and that's not loaded, so I'd guess the kernel has been modified to disable IPv6 default routes by default.
Any idea if there's an Android equivalent of inittab or sysctl.conf or how might I go about setting that sysctl variable automatically on boot?
whitslack said:
I have a Galaxy S3 SPH-L710 running Android 4.0.4, and I had the same problem with it not configuring the default IPv6 route. There is a sysctl variable that controls whether the Linux kernel automatically adds the default route advertised in the IPv6 Router Advertisement messages, and it defaults to 0 (off) on the phone. Look at /proc/sys/net/ipv6/conf/default/accept_ra_defrtr.
When I set accept_ra_defrtr to 1 and cycled my Wi-Fi connection, it came back up and added the default IPv6 route. Now test-ipv6.com on my phone gives me a 10/10 on both IPv4 and IPv6, meaning the DNS resolver is asking for AAAA records too and even preferring them when a host has both A and AAAA, which is the recommended and desired behavior. Loading comcast6.net on my phone shows my IP address as an IPv6 address.
Trouble is, setting sysctl variables in /proc/sys will not survive through a reboot, and there is no /etc/sysctl.conf on Android, so I don't know where to stash this setting so it gets applied on every boot. There is no file anywhere in /system that contains "accept_ra_defrtr" except for the vpnclient.ko kernel module, and that's not loaded, so I'd guess the kernel has been modified to disable IPv6 default routes by default.
Any idea if there's an Android equivalent of inittab or sysctl.conf or how might I go about setting that sysctl variable automatically on boot?
Click to expand...
Click to collapse
bro look at your /system/etc/init.d. if it exists, you can add a new script as
#!/system/bin/sh
echo 1>/sys/XXXXXXX
in init.d and name it 89enipv6 or sth.
if it don't work, check your /system/bin/sysinit. if it doesn't exist, google and copy one.
Does anyone know how I can disable IPV6 on my S3 ?
ahoslc said:
Does anyone know how I can disable IPV6 on my S3 ?
Click to expand...
Click to collapse
Why do you want to disable IPv6? It's new better version of IP protocol and should be used whenever it possible.
runapp said:
bro look at your /system/etc/init.d. if it exists, you can add a new script as
#!/system/bin/sh
echo 1>/sys/XXXXXXX
in init.d and name it 89enipv6 or sth.
if it don't work, check your /system/bin/sysinit. if it doesn't exist, google and copy one.
Click to expand...
Click to collapse
In my case of 4.1.3 the value of 0 rewrited in /proc/sys/net/ipv6/conf/wlan0/accept_ra_deftrt on every wifi interface restart, even independently on "all"/"default" values.
Rooted Thunderbolt - Connect to wifi quit working
I recently purchased a used rooted Thunderbolt. So far I've only used it on wifi networks and had no issues. Yesterday, when I try to turn the wifi on it never turns on and at some point it ultimately says error. I did some looking around and found that turning the wireless router off and then back on can often take care of this. I did this and it resolved the problem.
I'm having the same issue today only this time turning the router on and off doesn't solve the problem.
Here is some info about my phone:
Android Version
4.0.4
HTC Sense Verion
3.6
Software Number
NusenseROM_ReBorN_5.2_040813
Kernel Version
3.0.16-g65bd5ca
[email protected] #1
PREEMPT
Baseband Version
2.03.00.0201r.0.02.02-1211r
PRI Version
1.41_002.1.64_002
PRL Version
00000
ERI Version
5
I once had the same issue with a Droid Incredible, however, after a few days it started working again without me doing anything (intentionally) to resolve the problem.h
Does anyone have any suggestions?
The receiver might be going out but you could try flashing a different kernel or rom. Someone else just posted that their receiver went out.
Sent from my ADR6400L using Tapatalk 2
That's not real encouraging.
I think I'll install OSMonitor tomorrow and see if it gives any clues what is going on.
I found some suggestions at techrepublic.com blog titled "smartphones/troubleshoot-wi-fi-connections-on-your-android-phone/" [I'm new to this forum so I can't post a link or Figure B]"
There are a couple suggestions about changes in the wireless/advance settings. One is to select Proxy and make sure the phone is not set up for a proxy. The post is a few years old and I don't see this option on my phone. The other is to set a static IP Address which again I don't see as an option:
"6. Tap Advanced (Figure B).
7. Tap the Proxy setting and make sure your Android device is not set up for a Proxy. (Unless the Wi-Fi network you are on requires a Proxy, this setting will get in the way of your device's access to the Internet.) If you tap on Proxy and see an IP address or domain, delete it.
Figure B
Most likely the Proxy and Port settings will not be set, but it's always good to check if you're having frequent issues with Wi-Fi.
Static IP address
Another troubleshooting approach is to give your Android device a static IP address. This could reveal if the router you are trying to connect to is having issues with handing out DHCP addresses, or if your device is getting a bad address. To configure a static IP, tap Use Static IP and then fill in the settings (IP Address, Gateway, Netmask, DNS).
The only issue with setting up a static IP is that address will apply to all wireless networks, so only use this for troubleshooting if you just connect to one Wi-Fi network."
Any idea how (or if) I can do this?
wifi won't start - more info
I hope somebody is still tuned to this thread.
I have a rooted HTC Thunderbolt. It is running NuSenseROM_ReBorN_5.2_040813. I am having the same problem with the wifi not turning on.
I've run: logcat > /sdcard/logcat.txt and I've attached the log file.
If I run: ifconfig wlan0, I get:
wlan0: No such device
Anyone have any suggestions?
Hi,
i'm developing a realtime audio streaming client for Android that reproduces audio frames from network.
The server samples, encodes and sends audio over UDP broadcast datagrams, and all works well... until client's screen is turned on!
When screen is turned off(i.e. device goes to sleep) problems begin. I can divide them into two categories (apparently the discriminating factors are ROM/Silicon vendor):
No audio at all: behaviour found mainly on Qualcomm/Samsung devices. The WLAN drivers filters bcast datagrams when device is in sleep mode. The filter can be turned off from WCNSS_qcom_cfg.ini.
This fix apparently solves the problem on Qualcomm-based phones. I have a Marvell-based Samsung device with the same behaviour, but I've not investigated yet.
Stuttering audio: Happened on MTK-based phones. Apparently devices drop parts of UDP broadcast datagrams in sleep mode. Problem can be "solved" running a thread that keeps interface awake by sending dummy UDP datagrams every 100ms, but i don't like this solution.
Is there anybody who knows a way to tweak WLAN drivers on MTK/Marvell/OtherVendors phones to remove power-saving filters and allow broadcast activities in sleep mode(something like WCNSS_qcom_cfg.ini for Qualcomms) ?
UPDATE: Galaxy Xcover 3 (SM-G389F) has an Exynos 3475 and uses bcmdhd wifi driver, that uses dhd_pkt_filter_enable param to enable/disalbe filter.
Unfortunately it's defined with permission 0 (so it can't be accessed from sysfs) and I haven't found a way to pass the parameter to the kernel at boot time.
Recompiled the kernel with permission set to 0644 and it works (can be triggered from /sys/module/dhd/parameters/dhd_pkt_filter_enable).