Related
My buddy's HTC Eris cannot connect to our work WIFI.
His Phone: Gingerbread 1.6RC1
Our network: Hidden SSID WPA2+TKIP+AES
Before you ask, yes, I've entered in the SSID and Password manually.
I've tried Hidden SSID enabler, I've tried setting the IP to static... no dice. No one seems to have a solution or a reason why this happens. The best advice they give is to unhide the SSID. While I agree, I can't, because this is a work WiFi network. Not my router, not my policy.
Does anyone know if there's a radio update for the WiFi or a way to get it working? I thought the custom rom would fix it, but it doesn't. The LG Swift and Moto Droid both connect, no problems.
I've helped others with issues like this for the Eris and usually turning off TKIP solves the problem. For some reason, TKIP causes issues, and though you'd think that having AES as well would fix that, it may be that the Eris tries to use the "easy" method of TKIP and then fails.
That said, TKIP and WPA2 means that it is not exactly following the standard - I think that WPA2 is supposed to use CCMP/AES only. (It's actually a sort-of misnomer to say TKIP vs. AES - TKIP is to CCMP as RC4 is to AES. Or, in other words, TKIP uses RC4 as a cypher, while CCMP use AES.)
Anyway, the other possible issue is that the Eris is b/g only - if that router is a or n only, the Eris will not work.
It seems rather silly these days to be using SSIP hiding with WPA2 - anybody who wants to break in will get around SSID hiding easily, but will only get around WPA2 through brute-force cracking, and WPA2 will keep casual drive-by people out anyway - but, as you say, it's not your router. I'm not sure if you'll have any luck getting the folks who run it to change it to CCMP/AES only if you can't get them to unhide the SSID.
What doogald told you is spot on.
The only thing that I can add to what he said is that - unfortunately - it is quite typical with WiFi to run into interop problems when mixing gear from different vendors. That's not supposed to happen - but it in fact it happens all the time.
I ran into a case where Eris successfully negotiated an association with a older WiFi router (with AES+TKIP+WPA2), got an IP via DHCP from the AP.... and then was completely unable to communicate via IP - not even a ping. This particular problem was solved by updating the router firmware to a newer version.
I have beacons supressed on my WiFi router (although I completely agree with doogald that it provides NO extra security, despite popular misconceptions to the contrary), and sometimes my WiFi connection does not come up straight away - sometimes using the WiFi Scanner app (by farproc) seems to do something to kickstart the association/authentication. (The other thing you might give a try is this - if the PSK is a series of hex characters, check to see that it is not a simple matter of the case of the a-f characters being wrong. iirc, WPA2 uses string values rather than hex, so case sensitivity can pop up from time to time if network admins had a past history of using hex strings for WEP)
Usually, fixing a problem like this is a matter of trial and error; you try and eliminate or change one behavior at a time until something changes. (e.g. the B/G/N multi-mode behaviors, or turning beacons back on.) Generally, because there are more knobs to turn on the WiFi router, that's the place to start.
If you are in a position where the WiFi router can not be touched - well, you might be SOL, as there's precious little you can easily tweak on the Eris**
bftb0
**PS I suppose that it is possible that if we are talking about a rooted phone, you could dig in to configuration options for the "wpa_supplicant" process on the Eris - "wpa_supplicant" is based off of open source code, so perhaps a configuration file could - if nothing else - encourage it to be a little more verbose so you can detect what the error is.
bftb0 said:
I have beacons supressed on my WiFi router (although I completely agree with doogald that it provides NO extra security, despite popular misconceptions to the contrary), and sometimes my WiFi connection does not come up straight away - sometimes using the WiFi Scanner app (by farproc) seems to do something to kickstart the association/authentication.
Click to expand...
Click to collapse
I hate to go a little off-topic, but this happens to me with Froyo and GB ROMs (not with the Eclair ROMs), and I am not hiding the SSID. I actually think it has more to do with the kernel (Conap's CFS or BFS vs. Zanfur) than it does the Android version, though I could be wrong about that.
Anyway, here is what I noticed: in 2.2 or 2.3, if I turn on the WiFi radio using a widget, or just a setting toggle in an app like Quick Settings, it takes about 5-10 minutes before it finally connects to the access point. However, if I follow the settings->wireless & networks and then check WiFi to enable it, it will make the connection in a matter of seconds - every time; it's 100% repeatable. With a 2.1 ROM running Zanfur, no matter how I turn on WiFi, it reconnects every time within seconds.
I've tried looking at logs but I haven't seen anything obvious to suggest that there is some issue.
This is just a question for you two or anyone else who knows. Has there ever been a reported problem with anyone's Eris WIFI when using JIT? I'm just grasping at straws here.
Also, thanks doogald for the information regarding TKIP and AES. I don't recall if I ever researched this stuff before, but if I had, evidently it hadn't sunk in. I'm sure I could've found the information if it was actually important enough for me to, but I have often wondered about some of the "options" available in setting up wireless networks.
doogald said:
I hate to go a little off-topic, but this happens to me with Froyo and GB ROMs (not with the Eclair ROMs), and I am not hiding the SSID. I actually think it has more to do with the kernel (Conap's CFS or BFS vs. Zanfur) than it does the Android version, though I could be wrong about that.
Anyway, here is what I noticed: in 2.2 or 2.3, if I turn on the WiFi radio using a widget, or just a setting toggle in an app like Quick Settings, it takes about 5-10 minutes before it finally connects to the access point. However, if I follow the settings->wireless & networks and then check WiFi to enable it, it will make the connection in a matter of seconds - every time; it's 100% repeatable. With a 2.1 ROM running Zanfur, no matter how I turn on WiFi, it reconnects every time within seconds.
I've tried looking at logs but I haven't seen anything obvious to suggest that there is some issue.
Click to expand...
Click to collapse
In case you don't already know this, a long time ago I learned that differen't widgets ways of toggling things like 3G and WIFI may differ slightly, and some widgets methods may cause problems or delays where other widgets with different methods may work without any trouble. I use the EasySwitch app myself, I actually paid for it. I would suggest at least trying the trial version and see if that helps any.
roirraW "edor" ehT said:
Also, thanks doogald for the information regarding TKIP and AES. I don't recall if I ever researched this stuff before, but if I had, evidently it hadn't sunk in. I'm sure I could've found the information if it was actually important enough for me to, but I have often wondered about some of the "options" available in setting up wireless networks.
Click to expand...
Click to collapse
You're very welcome.
roirraW "edor" ehT said:
In case you don't already know this, a long time ago I learned that differen't widgets ways of toggling things like 3G and WIFI may differ slightly, and some widgets methods may cause problems or delays where other widgets with different methods may work without any trouble. I use the EasySwitch app myself, I actually paid for it. I would suggest at least trying the trial version and see if that helps any.
Click to expand...
Click to collapse
Thanks for the suggestion, and I will try it just to see. I do know that the Cyanogen notification bar widget, plus the Android standard Power Control Widget, has this issue with all of the Froyo and GB ROMs that I have tried, and I think I even had this issue when I installed Conap's BFS or CFS on xtrROM as well. Again, it doesn't happen with the Zanfur kernel in a standard 2.1 Eris ROM that you'll find here.
What I like about Quick Settings (https://market.android.com/details?id=com.bwx.bequick&feature=search_result) allows you to tap the WiFi wording (not where it has an on/off toggle button, but anywhere else on that line) it will bring you to settings->Wireless & Networks directly. Nice little app.
roirraW "edor" ehT said:
This is just a question for you two or anyone else who knows. Has there ever been a reported problem with anyone's Eris WIFI when using JIT? I'm just grasping at straws here.
Click to expand...
Click to collapse
Sorry, I forgot about this with my last post.
I tend to doubt that JIT would have anything to do with WiFi issue. If I am not mistaken, the JIT that we are talking about is just in time compiling for the Dalvik virtual machine, and I am fairly certain that WiFi operations are handled by Linux on the phone, not by Dalvik. Perhaps I am wrong about that, though.
That said, I ran GSB for a day or so before I realized that JIT was turned off by default, and it had that same issue with delayed connection. It's actually one of the first things I test with a new ROM...
And I am also pretty sure that I have seen issues with people whose router was set to TKIP (it's usually WPA rather than WPA2, where TKIP is more likely than WPA2) with stock Eris (and the Hero, I might add), which, of course, is not JIT.
roirraW "edor" ehT said:
I use the EasySwitch app myself, I actually paid for it. I would suggest at least trying the trial version and see if that helps any.
Click to expand...
Click to collapse
doogald said:
Thanks for the suggestion, and I will try it just to see.
Click to expand...
Click to collapse
As it turns out, EasySwitch Trial is set to run up to 2.2 only. It doesn't show up in the market on 2.3, and it wasn't until I went to market.android.com that I learned that it's not compatible with my GB device.
I will try it the next time I go back to Froyo, though.
doogald said:
You're very welcome.
Thanks for the suggestion, and I will try it just to see. I do know that the Cyanogen notification bar widget, plus the Android standard Power Control Widget, has this issue with all of the Froyo and GB ROMs that I have tried, and I think I even had this issue when I installed Conap's BFS or CFS on xtrROM as well. Again, it doesn't happen with the Zanfur kernel in a standard 2.1 Eris ROM that you'll find here.
What I like about Quick Settings (https://market.android.com/details?id=com.bwx.bequick&feature=search_result) allows you to tap the WiFi wording (not where it has an on/off toggle button, but anywhere else on that line) it will bring you to settings->Wireless & Networks directly. Nice little app.
Click to expand...
Click to collapse
Oh yeah, I remember Quick Settings. I used to use that a lot for the first few months I had my Eris (I had rooted immediately), before I went to EasySwitch.
doogald said:
Sorry, I forgot about this with my last post.
I tend to doubt that JIT would have anything to do with WiFi issue. If I am not mistaken, the JIT that we are talking about is just in time compiling for the Dalvik virtual machine, and I am fairly certain that WiFi operations are handled by Linux on the phone, not by Dalvik. Perhaps I am wrong about that, though.
That said, I ran GSB for a day or so before I realized that JIT was turned off by default, and it had that same issue with delayed connection. It's actually one of the first things I test with a new ROM...
And I am also pretty sure that I have seen issues with people whose router was set to TKIP (it's usually WPA rather than WPA2, where TKIP is more likely than WPA2) with stock Eris (and the Hero, I might add), which, of course, is not JIT.
Click to expand...
Click to collapse
I see. Thanks for your informed opinion!
doogald said:
As it turns out, EasySwitch Trial is set to run up to 2.2 only. It doesn't show up in the market on 2.3, and it wasn't until I went to market.android.com that I learned that it's not compatible with my GB device.
I will try it the next time I go back to Froyo, though.
Click to expand...
Click to collapse
Ah! Well, that is a bummer. Although, actually, I wasn't using EasySwitch under CM6 since it had the notification bar widgets. Does CM7 have those yet? That would probably be a deal breaker for me until I could at least use one of those under GB, which I haven't tried yet.
roirraW "edor" ehT said:
Ah! Well, that is a bummer. Although, actually, I wasn't using EasySwitch under CM6 since it had the notification bar widgets. Does CM7 have those yet? That would probably be a deal breaker for me until I could at least use one of those under GB, which I haven't tried yet.
Click to expand...
Click to collapse
Yep, CM7 sure does have those.
doogald said:
Yep, CM7 sure does have those.
Click to expand...
Click to collapse
Oh, good. I'm not positive if I'll try a CM7 build until a final release or not, anyway. Thanks for the info.
Hey all!
Just started this thread to explain something about SOD and phone SHUT DOWNS by itself.
I was NEVER BEFORE have these problems, like SOD or SHUT DOWN phone by itself, till now. I sure that it was related to one WIFI program, what I downloaded yesterday(Unlock With Wifi). Today I activated the app and I have phone SHUT DOWN by itself, like 3 times in hour. If I disabled the app, I solved the problem(for now I already UNINSTALLED that app).
Now I sure, that our SOD and S.DOWN problem not hardware problem, but SOFTWARE related problem.
I want to say you all, who have SOD or S.D...., look what app you have installed(what can use wifi) or in phone settings and try several times to configure your wifi(one of most: dont but your wifi to sleep, when screen is OFF), untill you solve you problem.
If you too know some examples, from you experience, then share with us here!
THX for reading!
Hope it will HELP someone.
CHEERS!
I'll try if turning off wifi will help. It should if this is wifi related problem.
JiiJii said:
I'll try if turning off wifi will help. It should if this is wifi related problem.
Click to expand...
Click to collapse
Hey!
Like I sayed, just try different things with WIFI settings. I think turning OFF wifi, will solve the problem, until you turning it back(when you have the problems). We will see, dose it solve the problem, if you turn OFF WIFI.
CHEERS!
You got the nail on spot. I was also in the same impression with SOD. Till now I'm not able to Figure out the app which cause this. But yes this is software issue rather than hardware. I also read else where that the SOD cause because of the lower voltage supplied to processor during sleep with which its not able to get itself up from sleep. Not sure...
I have a app that turns the wifi off when I lock the screen (dont remember which one of my apps!) so I havent experience it for awhile.
Sleep as an droid has a feature that shuts down the sleep tracker at a certain procentage (I chose 20%), instead of shutting the sleep tracker down, it shuts down the whole phone. Both of the times that i got SOD my phone had 20% left of its battery, so it was pretty obvious what caused it.
Sleep bot tracker is a great app if you forget to shut down your wi-fi before going to bed. Make it a habit to track your sleeping time, in the same time ull make it a habit to turn you wifi off. It has a built in function that shuts off the wifi when u start tracking your sleeping time. This app does not bring you and SOD.
What, but the general advise to sod had always been to check wifi always on...
XDA ♥
consegregate said:
What, but the general advise to sod had always been to check wifi always on...
XDA ♥
Click to expand...
Click to collapse
The topic been active in other threads so that's why the OP is taking this up I believe.
casiocas said:
Hey all!
Just started this thread to explain something about SOD and phone SHUT DOWNS by itself.
I was NEVER BEFORE have these problems, like SOD or SHUT DOWN phone by itself, till now. I sure that it was related to one WIFI program, what I downloaded yesterday(Unlock With Wifi). Today I activated the app and I have phone SHUT DOWN by itself, like 3 times in hour. If I disabled the app, I solved the problem(for now I already UNINSTALLED that app).
Now I sure, that our SOD and S.DOWN problem not hardware problem, but SOFTWARE related problem.
I want to say you all, who have SOD or S.D...., look what app you have installed(what can use wifi) or in phone settings and try several times to configure your wifi(one of most: dont but your wifi to sleep, when screen is OFF), untill you solve you problem.
If you too know some examples, from you experience, then share with us here!
THX for reading!
Hope it will HELP someone.
CHEERS!
Click to expand...
Click to collapse
I noticed that this problem is only for those who are using the older firmwares including XXKPH or the ROMs whose base are 2.3.4 KPH.
Haven't encountered this problem in the Samsung July 2011 release of 2.3.3 (KPN). But I guess, this is a good post for those who are still experiencing this.
For now, I'm just happy with KPN (that's why I'm not as active before here in the forums).
Before I flashed to 2.3.4 KPH, my Wifi worked flawlessly.
Now my Wifi reception is extremely limited (I have to be in direct line of sight to the router within 2 meters to be able to get a stable connection)
and
I get those dreaded SoDs (sleep of deaths).
My question:
Is it possible to flash only the modem file of 2.3.3 to try whether that works?
If yes, will my current system be wiped if I only flash the modem file?
kiudee said:
Before I flashed to 2.3.4 KPH, my Wifi worked flawlessly.
Now my Wifi reception is extremely limited (I have to be in direct line of sight to the router within 2 meters to be able to get a stable connection)
and
I get those dreaded SoDs (sleep of deaths).
My question:
Is it possible to flash only the modem file of 2.3.3 to try whether that works?
If yes, will my current system be wiped if I only flash the modem file?
Click to expand...
Click to collapse
If you don't use the video chat in Google Talk, then why not just flash 2.3.3 KPN?
The only new feature in 2.3.4 is the video chat in Google talk. Most bug fixes are now in the July 2011 release of 2.3.3 KPN.
Yes, I'm contemplating to do that.
But as I've spent a bit over a weeks time to set my system up, I would like to know if it's possible to just flash the modem without touching the already working system.
edit: I see KPN is a single file flash, so I won't be able to flash only the modem. Ok, backup and downgrade it is.
I've only experienced SOD once... But I always have wifi off. Just on when I'm going to use it. Afterwards I turn it off and good bye SOD issue
Sent from my GT-S5830B using XDA App
kiudee said:
Yes, I'm contemplating to do that.
But as I've spent a bit over a weeks time to set my system up, I would like to know if it's possible to just flash the modem without touching the already working system.
edit: I see KPN is a single file flash, so I won't be able to flash only the modem. Ok, backup and downgrade it is.
Click to expand...
Click to collapse
Hey!
Dont know exactly, but I think that you can restore your system settings and other system things, with TITANIUM BACKUP. Backup the ALL SYSTEM DATA in batch menu. Go to TITANIUM BACKUP>Menu>batch. Pick: backup all system data and RUN THE BATCH. After that, flash you ROM(what ever you want) and try to restore all system settings from TITANIUM B.. Ofcourse, what ever happens, I suggesting you do NANDROID BACKUP from CWM recovery, before you start anything. If nothing works(or **** happens), you can RESTORE ALL FROM NANDROID BACKUP.
CHEERS!
Update: I flashed 2.3.3 KPN and did a factory reset.
The SOD problems are gone now,
but
the bad wifi reception still remains. (Connection to router only works within an extremely close range)
If I cannot find a fix for this problem I might try out a froyo firmware.
Did anybody have a similar problem? Would really appreciate some hints.
kiudee said:
Update: I flashed 2.3.3 KPN and did a factory reset.
The SOD problems are gone now,
but
the bad wifi reception still remains. (Connection to router only works within an extremely close range)
If I cannot find a fix for this problem I might try out a froyo firmware.
Did anybody have a similar problem? Would really appreciate some hints.
Click to expand...
Click to collapse
Hey!
I think its not ROM-s problem. Try look your Router settings and phone settings. I think something is not right in PHONE or ROUTER settings. Not seen this kinde of problem YET, with ANY ROM. Try to look.
One question: dose you not DROP you phone or similar? I seen little problems can happen, even nothing SERIOUS was done(like speaker, wifi and other HARDWARE problems).
CHEERS!
kiudee said:
Update: I flashed 2.3.3 KPN and did a factory reset.
The SOD problems are gone now,
but
the bad wifi reception still remains. (Connection to router only works within an extremely close range)
If I cannot find a fix for this problem I might try out a froyo firmware.
Did anybody have a similar problem? Would really appreciate some hints.
Click to expand...
Click to collapse
Froyo will not help i think. I had all the mentioned problems in Froyo aswell. That's why i flashed to KPH and now KPN for eventually.
From my 3 days experience with Froyo i never experienced SOD.
I don have any sod problems.
BUT,sometimes my phone vibrates 3 times n then goes to Samsung bootlogo,den homescreen comes up n mediascanner starts.. (I ges this is called soft resetting)
Any solutions to get rid of this???
M in stock froyo rom..
Any help ll b appreciated...
Thanks
Sent from my GT-S5830 using Tapatalk
i had SOD with bluetooth turned on((((((((((((((((((((((((((
apps i downloaded are:
whatsapp
twitter
Facebook
im+ pro
dolphin browser
barcode reader
go launcher ex
my phone was rooted and running on 2.3.4 KPH. i had 3 SODs today but i never have any sods when i am at home. i have no idea which one(s) cause SOD.
today i flashed with coderom v2 (formatted sd and wiped internal memory and cache) i will see if sods keep on coming. if they do happen, then i am going to try KPN
I've been having issues with wifi on my tab. I visit a friends house and it won't pick up the wifi. My phone picks it up fine, laptops pick it up ect. I stand AT the router and still it doesn't pick it up.
I thought it was a 1 off but it started happening at work too. The only differenceis that is WAS working fine at work, now won't pick it up. And now I have the same issue at my parents.
Does anyone else have this issue? Does anyone know a fix?
Cheers
Try wifi sleep policy and play with the options. Mine was set to "Never" and I was having random problems. Now set to "when screen turns off", and I never lose connection, screen on or off... On the other hand your problem may be different.
/reviveThread
Can't be sleep policy as it picks up other wireless networks fine.
I was just living with this issue until it lost my Home Wifi! Now thats gone I have to turn Hotspot on my phone, which I shouldn't have to do.
I thought it might be a problem with the ROM, so I've tried Task's GalaxyTask v5.0 and I still have the same issue. Might try flashing Stock and seeing if I get the same issue.
This is doing my head in now!
I flashed 3.2 Stock (rooted) and it picked up the missing Wifi connections. The rom is full of hebrew with silly boot and shutdown animations though. Tried flashing several custom 3.2 ROMS other than that and same issue as before.
Also, added connection manually and stood next to the Wifi antenna at work. Still got nothing. WTH is going on?
I read somewhere that Galaxy tab is not able to connect to some channels of wifi.
I believe it was not working with channels above 11
Try changing the channel and check
Thanks for the reply.
My home network is on channel 3. Plus it doesn't really explain how it can work 1 sec then totally disapear forever. Also doesn't explain how it works with the stock hebrew ROM but not with any others I've tried.
Just trying to find the wireless details for work now so I can change the channel anyway.
Then go with the Hebrew Rom and select English as language
Sent from my GT-P7510
ansonantonym said:
Then go with the Hebrew Rom and select English as language
Sent from my GT-P7510
Click to expand...
Click to collapse
I'd rather have no Wifi than see that nasty looking shutdown animation.
Anyway, problem seems to be semi resolved now.
Changed my wireless from channel 2 to 12, still didn't show. Back to 2, still didn't show. Changed it to 10 and it magically appeared.
Not sure what the work one is on. Still waiting for access.
Hi there!
So, I have a little problem with my second phone. The problem now is that I can't find any WiFi networks when I search for one. I have always had connection here home, and it works fine on my XS.
I don't want to restore or flash anything because the reason I need WiFi is to back up the bookmarks I got on the Dolphin Browser that is installed on the phone.
I also want to say that I don't have any SIM-card in the phone because I'm using that one in my XS, but that should not affect WiFi as far as I know.
I'm running Android 2.3.3 and baseband 2.1.71.
So what could the problem be?
Thanks in advance!
What rom have you installed, if so, do you have the right kernel and wifi modules? any details of what you have installed?
Are other pc's or mobiles at home able to perform a search for wifi networks and see the SSID of the router?
Upps.. sorry for leak of info.
I'm running stock ROM. Yeah, I have the right kernel and WiFi modules. The phone have worked well before.
Yes. This phone is the only one who can't find any WiFi networks. It sucks! Never had this issue before.
I am having the same issue. Just started the other day. My phone will not find a wifi network unless it is sitting next to the router. If I am over 5 feet away it just says searching and not in range.
Any thoughts?
Okay, just stood 1 meter from the router, still it didn't find any wifi connections!
This sucks!
When you go to wifi settings and activate it, does the tick apply to the box(enabled) or does not do anything?
It doesn't sound nice. if you are sure that you are running Sony ericsson original software (no custom roms, kernel and else) then try to do a factory reset from the menu, if it doesn't do anything then use SEUS and reinstall the software.
This will prove that this is either or not a hardware fault. It is the best way to check. If it still doesn't work after SEUS reinstall, then it is definitely a fault. If it fixes it then congrats..
If it's a custom rom from here then forget seus and flash the rom again.
Screenshots are welcome if you have..(wifi settings, system info..)
Good luck
The tick apply to the box yes.
Okay, so I connected it to my PC and ran Update Service and did a fresh reinstall of the software. Still the same problem. Can't find any WiFi connections
Well you already know the answer..
Yeah I do.. Think I'm going back to the store with it and get it fixed. Also have some reboots problem that may be related to this..
Thanks for answer.
If you only need your bookmarks just put sim from XS in X10 and turn on and backup info and replace sim in XS.
EDIT: do you have unlocked bootloader? If yes u can try relocking it.
http://forum.xda-developers.com/showthread.php?t=1259617
Sent from my X10S using XDA
dehmducks said:
I am having the same issue. Just started the other day. My phone will not find a wifi network unless it is sitting next to the router. If I am over 5 feet away it just says searching and not in range.
Any thoughts?
Click to expand...
Click to collapse
hello mister, I have a same issue with you.
my LWW cannot find a network althought I was sitting in front of the router and it says not in range.
but sometimes it can works well, but it often cannot work
still searching for the solutions
Think its the wifi antenna thats failing.
First I couldnt find any WiFi networks. I had it off for a few weeks (got my Xperia S xD) and when I tried it, it worked well.
So its not easy to find the solution for this.. It sounds like a hardware issue
Sry m8.
Sent from my LT26i using xda premium
hi
I am using Sony T3 D5103
I have a problem with my wifi its turning on but coudnot dtect any hotspots kindly help me in this thanking you in advance
Hi Guys,
i have a problem.
Since a couple of days, the wifi connection on my i9100 does not work anymore. I tried multiple roms but to no avail.
The thing is that the wifi connection is established, but nothing works.
I tried different roms, router resets (but the problem occurs on any wifi connection).
Any ideas?
theBIGone said:
Hi Guys,
i have a problem.
Since a couple of days, the wifi connection on my i9100 does not work anymore. I tried multiple roms but to no avail.
The thing is that the wifi connection is established, but nothing works.
I tried different roms, router resets (but the problem occurs on any wifi connection).
Any ideas?
Click to expand...
Click to collapse
may be its a problem with your device karnel version. try to use stoke karnel, i had this problem once. then i flashed stock karnel using odin. then solved
Thanks for the reply, i tried it and i am now running stock. BUT the problem still persists.
This could not be a hardware problem could it? since the wifi is connected?
theBIGone said:
Thanks for the reply, i tried it and i am now running stock. BUT the problem still persists.
This could not be a hardware problem could it? since the wifi is connected?
Click to expand...
Click to collapse
Ive had this happen to both my my Note 2 and my SGS2 LTE before that. With the Note 2, No matter what rom/stock firmware i flashed it never got better and I ended up selling it at a loss, but the SGS2 was made better when I flashed to stock then reflashed a Cm 4.2.2 rom. Maybe try that?
butthurtlocker said:
Ive had this happen to both my my Note 2 and my SGS2 LTE before that. With the Note 2, No matter what rom/stock firmware i flashed it never got better and I ended up selling it at a loss, but the SGS2 was made better when I flashed to stock then reflashed a Cm 4.2.2 rom. Maybe try that?
Click to expand...
Click to collapse
I just tried it with an CM 4.4.2 rom, that did not fix the problem. i will try to flash a 4.2.2 rom next.
Any ideas?
Given what you've already tried, flash the 3 part firmware from Hopper8's 'Odin troubleshooting' thread stickied in the General section. If you can get WiFi working on that, then reflash a more recent stock rom. If it's still working, then reflash whatever custom rom.
Might not work, but worth a shot given the 3 part will wipe your phone & might get rid of anything funky that might be causing this (don't forget to back stuff up before you flash it).
That it happens with every WiFi network you try to use is a worry though, and probably points either to something really simple we're all missing here, or a hardware issue.
MistahBungle said:
Given what you've already tried, flash the 3 part firmware from Hopper8's 'Odin troubleshooting' thread stickied in the General section. If you can get WiFi working on that, then reflash a more recent stock rom. If it's still working, then reflash whatever custom rom.
Might not work, but worth a shot given the 3 part will wipe your phone & might get rid of anything funky that might be causing this (don't forget to back stuff up before you flash it).
That it happens with every WiFi network you try to use is a worry though, and probably points either to something really simple we're all missing here, or a hardware issue.
Click to expand...
Click to collapse
I will try that when i get back from work. But i've been thinking, how is it possible that it is a hardware issue? i mean the phone still connects, something hardware related can not be partially broke right?
You'd think not (that it wouldn't be a hardware issue), but you've tried pretty much everything you can on the soft/firmware side, and it obviously isn't something on the WiFi network side unless all the WiFi networks you've tried & failed to get data flow to/from have this problem.
One thought I did have since my last post...I can't remember whether it's possible to do this on the S2 (it is on the S3/S4) as it's been months since I've even looked at mine; if you delete a WiFi connection in settings, then when you re-add it, are you able to choose between DHCP & static for IP address (might be in advanced settings if you check the box) ? If you're able to do this, choose a static IP address (I use 192.168.1.168 on my S4) rather than DHCP & see how that goes.
If that's not possible or it doesn't work, then try flashing the 3 part. Make sure you test once you've flashed it without restoring anything or installing any apps first to rule in/out something on the app side of things causing the problem.
THe 3part Odin flash did also not work. Is there a last resort solution, or is this it. Should I accept that my phone is broken
theBIGone said:
THe 3part Odin flash did also not work. Is there a last resort solution, or is this it. Should I accept that my phone is broken
Click to expand...
Click to collapse
pheraps there is a problem with your modem version. Try to flash an other modem using recovery.
isnt that what i did in the 3 step flash from hopper8?
No, it's not. There's a big difference between flashing a 3 part rom & just simply flashing a modem. However...
It won't work anyway because WiFi has nothing to do with the modem (WiFi drivers are in the kernel).
Did you try what I suggested with removing the connection in phone WiFi settings & re-adding it with a static IP (presuming this is even possible on the S2) ?
If you did & it didn't work, or it isn't possible after all, take it to a service centre or local mobile repair shop.
or just buy a new phone as i did. I will keep you posted if the static ip worked.
MistahBungle said:
No, it's not. There's a big difference between flashing a 3 part rom & just simply flashing a modem. However...
It won't work anyway because WiFi has nothing to do with the modem (WiFi drivers are in the kernel).
Did you try what I suggested with removing the connection in phone WiFi settings & re-adding it with a static IP (presuming this is even possible on the S2) ?
If you did & it didn't work, or it isn't possible after all, take it to a service centre or local mobile repair shop.
Click to expand...
Click to collapse
Holy &^#(*^ that worked! a static IP worked. How is that possible?!
The short answer ? Magic
The long/non-tech answer; the connection between the phone/router is basically dropped & constantly re-established over & over & over (we're talking about once a second or less; basically looping like that) which means you've never got a stable connection long enough to get any data flow with a DHCP allocated IP.
There's threads on here somewhere that explain it better/explain 'the why' if you're interested enough to search for them; sorry, I don't have bookmarks handy & it's 5.30am here so I'm going to bed.
Important thing is, problem solved
MistahBungle said:
The short answer ? Magic
The long/non-tech answer; the connection between the phone/router is basically dropped & constantly re-established over & over & over (we're talking about once a second or less; basically looping like that) which means you've never got a stable connection long enough to get any data flow with a DHCP allocated IP.
There's threads on here somewhere that explain it better/explain 'the why' if you're interested enough to search for them; sorry, I don't have bookmarks handy & it's 5.30am here so I'm going to bed.
Important thing is, problem solved
Click to expand...
Click to collapse
100% thanks, i've looked around on the forum and see now that you've helped multiple people solve this problem. That is great.
[FIX]
For the people that read this thread, fix the problem by applying a static IP for their WIFI and think "but what about all the public accespoints that do not allow static IPs?? Will i never be able to use them anymore?"
Don't worry
The problem is not so much the fact that the phone suddenly needs a static IP on certain WIFI accespoints, but that it needs an assigned DNS. Through some "magical" "unexplainable" reason some of our phones suddenly go broke in a weird way that everything works, but no DNS is assigned on specific WIFI spots (mostly WPA2 protected).
Solution:
Set a fixed DNS for all WIFI connections
Google Play has multiple apps that will apply a fixed DNS.
[edit] after this debacle i bought a second hand i9300. The first couple of days, it worked perfectly but soon it started to display similar behaviour as my i9100. That is when i started to look for other possible solutions for the problem. I soon found out that the Ip adress that was handed out by my router was off. it was 192.168.2.xxx instead of 192.168.1.xxx as is setup in my router settings. That is why entering a static IP solved the problem for my i9300. After restoring my router to factory settings everything is normal. My router is a Tp-link wr740N with DDWRT flashed on it. Maybe this information will also help other users
Good job digging up the DNS info, hopefully this helps people in future/they don't spend days pulling their hair out trying to fix this issue