Hi friends
Searched the forum and tried the proposed solutions but nothing helped.
I'm trying connect to addhoc wifi on my desire HD os=2.2
I replaced the wpa_supplicant file with one of those that exists on the forum and
indeed now i see adhoc networks but the connection is not stable - it goes like connecting -> obtaining ip address -> connected -> disconnected
and so on in loop ... i verified that the ip is static and i even put gateway+mask+dns.
when trying to ping the target it even sometimes succeeds!
Tried with several different adhoc targets and tried both wpa_supplicant for ver 0.5 & ver 0.6
Please does someone can help ?
thanks
ezchip said:
Hi friends
Searched the forum and tried the proposed solutions but nothing helped.
I'm trying connect to addhoc wifi on my desire HD os=2.2
I replaced the wpa_supplicant file with one of those that exists on the forum and
indeed now i see adhoc networks but the connection is not stable - it goes like connecting -> obtaining ip address -> connected -> disconnected
and so on in loop ... i verified that the ip is static and i even put gateway+mask+dns.
when trying to ping the target it even sometimes succeeds!
Tried with several different adhoc targets and tried both wpa_supplicant for ver 0.5 & ver 0.6
Please does someone can help ?
thanks
Click to expand...
Click to collapse
My phone is samsung galaxy GT - I 5503. I do too and obtainging IP address...
This question not yet solved
I have the same issue with my sgs2. I get no connection ever, only a constant "Obtaining IP address.."
I'd suggest resetting your router and forgetting the network and trying to reconnect. Also a static IP might work but as for finding any of your provider's info, that's up to you. Unfortunately, XDA doesn't even recognize my network (Sasktel) so I am having a very tough time with this!
most probably firewall problem , i had same problem with hotspot doing exactly as you discribe.
it can also happen by some custom Roms and don't happen with others ( firewall disabled ) .
Also lot of sense Roms have an issue with that exact wifi problem , not like AOSP Roms ,i don't know why
I only had this problem with a network called; 'eduroam', my schools' network. I solved it by recotting & changing the network security TLS/TTLS/EAP or somethinf like that.
hi guys,
does somebody have the slightest clue, why my GN cannot reach mtalk.google.com when i'm connected via WIFI after a few hours? every other host is accessible without any troubles over the same connection.
reconnecting to the accesspoint doesn't help, using a different one doesn't help. 3G connection works.
when i try to ping mtalk.google.com the host ip address is resolved correctly, but i only get dozens of
From 192.168.1.33 icmp_seq=xx Destination Host Unreachable
...
adb logcat shows
W/GTalkService( 365): -- caused by: java.net.ConnectException: failed to connect to mtalk.google.com/173.194.70.188 (port 5228): connect failed: EHOSTUNREACH (No route
to host)
ifconfig down/up doesn't help
the only thing that helps is a shutdown and restart. for a few hours ...
this drives me crazy!! anybody?
kind regards,
bernie
There is no wifi on gederom or any CM9 rom.I turn on and off wifi and still it doesn't work. I have an Intellinet router.
Thanks for any replies.
You should probably try changing your router's channel. I've heard that channel 13 is bad news ... and I think that was for a cm9 rom. Anyway, it's definitely worth a shot.
Are you wiping cache/dalvik before flashing new roms? If you're going from one developers rom to another developer, you should do a factory reset, then wipe, then install rom. If all you're doing to flashing roms from the same developer, then a cache/dalvik wipe is all you need to do. Hope that helps!
Wipe that kindle clean. Are you using fios? I've heard of a few people having issues with them.
I notice I can't see one particular Linksys wireless router at one of my job sites, but since we have two wireless routers it doesn't really affect me. No idea why...but maybe there is something someone else knows that can help understand the issue?
I still have no wifi and I wiped my kindle fire clean too. I changed the wifi channel from 11 to 4 but still it doesn't work.The connection shows up and when I enter the password the signal strength goes down.It says Authenticating and then it says saved and doesn't connect.
Any Help please.
Daniel120201 said:
I still have no wifi and I wiped my kindle fire clean too. I changed the wifi channel from 11 to 4 but still it doesn't work.The connection shows up and when I enter the password the signal strength goes down.It says Authenticating and then it says saved and doesn't connect.
Any Help please.
Click to expand...
Click to collapse
Try changing from dhcp to static.
Daniel120201 said:
I still have no wifi and I wiped my kindle fire clean too. I changed the wifi channel from 11 to 4 but still it doesn't work.The connection shows up and when I enter the password the signal strength goes down.It says Authenticating and then it says saved and doesn't connect.
Any Help please.
Click to expand...
Click to collapse
Can you go someplace where there is another router? Like I said, I notice there is one particular flavor of Linksys router that my Fire can't see on this ROM, yet at home I have a different model Linksys and there is no problem. Check it out on another router to see if it's just some weird compatibility issue.
Daniel120201 said:
I still have no wifi and I wiped my kindle fire clean too. I changed the wifi channel from 11 to 4 but still it doesn't work.The connection shows up and when I enter the password the signal strength goes down.It says Authenticating and then it says saved and doesn't connect.
Any Help please.
Click to expand...
Click to collapse
Check the router and see if QOS is enabled. If so try turning it off.
I don't have any other routers in my house. With static I still get the same result.
Any way thanks for all the replies.
Sent from my Kindle Fire using Tapatalk
IF FOR SOME REASON WIFI DOESN'T WORK ON THE FIRST BOOTUP DO THE FOLLOWING:
This is what hashcode say's
Enter Terminal Emulator
Type: su
Type: fix-mac.sh
Exit Terminal Emulator
Reboot
Daniel120201 said:
I don't have any other routers in my house. With static I still get the same result.
Any way thanks for all the replies.
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Daniel120201 said:
I don't have any other routers in my house. With static I still get the same result.
Click to expand...
Click to collapse
Is there a reason you can't go to a coffee shop, library, or any number of other hotspots with your Fire? I mean if you have a medical issue that keeps you bedridden, I understand, but if not, there are usually routers everywhere you can try connecting to.
Please try connecting to your wifi and then pastebin the output from the following and PM me the links:
Adb shell "dmesg" > dmesg.txt
Adb logcat > logcat.txt
Thanks
Sent from my DROID4 using Tapatalk 2
The fix-mac.sh fix still doesn't work and I found something with build.prop and settings.db and with some locale things while I was with channel 11 and still it didn't work.
Thanks for the replies.
Daniel120201: I looked at your pastebin logs and here are some notes:
The key lines in your logs are:
logcat: 7551.D/wpa_supplicant( 1040): EAPOL: Supplicant port status: Unauthorized
dmesg: 3949.<7>[ 538.654174] wlan0: disassociated from 00:0e:e8:d5:c5:d1 (Reason: 15)
When I looked up "Reason 15" as a disassociation error, I find:
Reason code 15: 4-Way Handshake timeout.
When I looked up how 4-Way Handshake works:
http://en.wikipedia.org/wiki/IEEE_802.11i-2004
On that page it references CCMP protocol for WPA2 and IPSEC:
http://en.wikipedia.org/wiki/CCMP
And on that page it mentions this:
CCMP is an enhanced data cryptographic encapsulation mechanism designed for data confidentiality and based upon the Counter Mode with CBC-MAC (CCM) of the AES standard
I double-checked the kernel config and low and behold:
#
# Authenticated Encryption with Associated Data
#
# CONFIG_CRYPTO_CCM is not set
I think this can be solved via a kernel config change. Later today, I will create a new kernel only .zip file with this change and I'd like for you to test it.
This also may solve IPSEC issues as well.
Here is a link to the new kernel w/ CCMP support added [Kernel #12 06/08]:
http://bit.ly/KPbDVm
md5sum: e7476ff785b2dfbdb062e1cc036c14ac
Thanks for the kernel Hashcode.It's Works.
You're quite welcome. I think there were a few others who were in the same boat.
Updated kernel Still same problem for me
Hashcode said:
You're quite welcome. I think there were a few others who were in the same boat.
Click to expand...
Click to collapse
I am still experiencing this error after kernel update. Too bad this is a very good rom otherwise.:crying:
Under phone settings I keep getting ping ipaddr - fail, ping hostname - pass, HTTP client - pass. I still have internet and all seems to be working fine. I had a random MMS not send which led me to check my settings. Not sure why it keeps saying unreachable. The thing I've recently done was flash miui. I wiped then went back to mmuzzy's 4.2.2 ROM, I have the newest radio available. Anyone else experience this?
Unreachable could be your wifi router causing the problem. Try reboot the Router and see if it corrects itself.
Even if it occurs while I'm on mobile data?
dancingtortoise said:
Even if it occurs while I'm on mobile data?
Click to expand...
Click to collapse
I am having the same issue.
Ping IpAddr: Fail IP addr not reachable
Ping Hostname(www.google.com): Fail: Host unreachable
HTTP client testass
Data seems to be working otherwise.
any one can solve this??
It's fairly evident by the number of "wifi problem" threads posted all over xda that there seems to be a huge wifi problem with Android 4.0+. I've seen multiple reports of problems and several reports of methods for fixing user-specific scenarios. In my attempts to better understand what is going on at a system level and in hopes of finding a better solution, I've tried just about all methods I've come across to solve this issue. The only "fix" that works for me is turning off WIFI Power Save Mode via *#0011#. The problem with that fix is it does not work on AOSP ROMs! Hence, I'm trying to find another solution or another method of disabling WiFi Power Save Mode within AOSP ROMs.
Background Information/Description of problem: Turn on wifi and list of available networks will appear. Regardless of being able to connect to a network or not, after 8-10 seconds, the device will scan again, it will time out and the list of available networks will disappear and any connection will be lost. Available networks cannot be seen again until wifi is successfully toggled off and back on again (note - the device seems very picky about actually turning wifi off; it wants to keep it on for some reason - this could be an issue with the multiple reporting of the wifi state in various settings).
Known "Fixes": Some people seem to have luck with certain "fix methods" where others do not.
For most people having this issue or a similar issue, disabling WiFi Power Save Mode in the Service Menu seems to allow the phone to stay connected to networks. This is also true given that the user's wireless router is configured correctly. I've seen reports of several different router models being notorious for issues with Samsung phones, most notably the D-Link DIR-655. I have the DIR-655 and I've configured it to talk nice with my phone when WiFi Power Save Mode is turned off. (I have a new router being shipped to me this week to eliminate this factor altogether)
Some have performed a factory reset with successful wifi connectivity afterwards.
Some have re/flashed a radio and had success. I would like to try reflashing a radio via recovery but we currently do no have one posted on the forum - can someone help me out here?
Some have luck by manually setting the IP address on the router and/or phone.
For the sake of being able to flash an AOSP ROM and have working wifi, I'd like to try and find what's causing this issue and try to find a solution/workaround. I've been troubleshooting and trial-and-erroring most of the weekend.
My research so far:
While looking for the specific setting being toggled via the Service Menu (*#0011#), I found that the WIFI Power Save Mode setting is referenced in /system/app/serviceModeApp_RIL/res/values/strings.xml as
Code:
<string name="powersavemode">WIFI Power Save Mode</string>
which is referenced in /system/app/serviceModeApp_RIL/res/values/public.xml as
Code:
<public type="string" name="powersavemode" id="0x7f06006b" />
That's as far as I've gotten on that road - I haven't found the "0x7f06006b" constant referenced anywhere else yet - maybe someone else knows a quicker way to search for it?
I've attempted to modify settings in wpa_supplicant.conf found in /system/etc/wifi/ and /data/misc/wifi/ with no luck.
I've attempted to use bcm4335 drivers found on other variants of the S4 but I didn't get very far - some implementations are different!
I've gathered several Logcat files for reference:
WiFi Toggle On & Connect
WiFi Connects & Disconnects
CM10.1 WiFi Toggle On Only
Various lines that stand out to me:
Code:
E/wpa_supplicant( 3911): wpa_driver_nl80211_driver_cmd: failed to issue privatecommands
E/wpa_supplicant( 3934): Line 6: unknown global field 'okc=1'.
E/wpa_supplicant( 3934): Line 6: Invalid configuration line 'okc=1'.
I/wpa_supplicant( 3934): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 3934): Could not set interface wlan0 flags (UP): Operation not permitted
E/wpa_supplicant( 3934): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 3934): wlan0: Failed to initialize driver interface
E/wpa_supplicant( 6961): Can't open default ap file
E/wpa_supplicant( 6961): Failed to open config file '/mnt/shell/emulated/0/cred.conf', error: No such file or directory
E/WifiHW ( 721): can't find ctrl_interface=
E/WifiHW ( 721): ctrl_interface != /data/misc/wifi/sockets
E/WifiHW ( 721): wifi_wpa_ctrl_cleanup is skiped.
E/WifiHW ( 721): Unable to open connection to supplicant on "/data/misc/wifi/sockets/p2p0": Connection refused
I'm no expert, but those lines seem to indicate some sort of underlying permissions and/or read/write issues? Some of the files those logs reference to as not existing actually do exist on the device. I saw in one thread where someone mentioned bad partitions? In that same thread someone mentioned flashing the radio/modem to correct their issue and it worked; this is why I want to try reflashing the radio on my phone.
Another thing I want to try is using Odin to reset the entire phone back to official stock, overwriting everything including the modem but we don't have an official tar for this yet.
What I would like to see from other T-Mobile S4 users:
Logcats of someone on stock who does not have wifi issues turning WiFi on from an off state and leaving it for at least 15 seconds. I'd like one where the device does not connect to a network and one where it does connect to a network.
Logcats of someone on CM10.1 doing the same mentioned above.
Someone who knows more about Android than I do to interpret these logcats and provide guidance
I can confirm that the service menu option to disable wifi Does work. Since I did the procedure wifi has been flawless.
im using a verizon dsl modem w router built in, jusy fyi.
Same here with the service code. Tmo s4 btw
Sent from my SGH-M919 using xda app-developers app