Related
I have searched this and other forums and have not seen either this problem or an answer to it. Per AT&T's suggestion, I just upgraded to the new AT&T rom version that adds PTT and seems to have big problems. My current issue is that when I first boot up and connect via GPRS/3G all works well. When I get to a wifi area and switch to wifi, again all works well. However when I leave the wifi area (or just turn off wifi) I can't get any data via GPRS/3G. The balloon comes up saying it is connecting. The little "G" and bidirectional arrows in the top left indicate it is connected. However in the browser, it just continues to grind away with "Locating" in the bottom right corner until it finally times out and puts up a screen that says that the "page cannot be displayed because the connection was lost". I open the connection manager and press and hold the "Data Connection" icon until that goes off and try again, same problem. The only way I can get GPRS/3G data connection to actually work again is to reboot. Any ideas what is going on or how this can be fixed? Forgot to add that this is an HTC 8525. Thanks.
From your description I wasn't able determine whether AT&T's suggestion was aimed at remedying the issue, or if it's something that came about with the update.
Assuming the latter, you may want to try a hard reset first and run it for a bit before loading any other apps. Failing that, reflash the ROM. I had a lot of trouble with my radio when my 8525 was new, but it mysteriously cleared up after a few radio flashes.
Thanks but still a problem
Thanks for your thoughts here. I hard reset and reflashed.
Yes the firmware is the latest one that AT&T has suggested that everyone who had the older Cingular phones upgrade to. It provides the AT&T logo, the "push to talk" feature, and some other junk. I have contacted AT&T about this and their response was to send me a new phone that they claimed had the old firmware, since they have been getting a lot of complaints about the new firmware. It didn't have the old firmware and also it's SIM card reader appears to be broken. I called HTC and they said that they too have had lots of complaints about the new firmware quirks but had nothing to offer to solve them. Anyway, the old firmware had no problem switching between wifi and CGRS so I don't think it is in the hardware. On the other hand I'm surprised that nobody else is encountering the problem from the upgrade.
I'm having the same prob. Purchase three of these phones and the other users have little technical expertise. First I set up a sync with my office PC. Then loaded the ROM update. I run MAC's @ home had difficulty connecting to my home wifi. Finally determined that the 8525 would not accept the 13 key ASCII wep password. Needed to use the HEX. So I connected. Went to work and had problems syncing with my PC. Active sync had to rediscover the device. Now I'm back home and can't connect again. My Device ID changed names upon "resyncing" and I updated the Airport Base Station with my new name. I've spent a lot of time on this issue.. Maybe I need to send em back for an iPhone!
Well I found a solution to it
This is a great forum - though somewhat hard to search through thoroughly. Anyway the solution for me was to go back to ROM 1.34. Found how to do that through flashing from the micro card at http://forum.xda-developers.com/showthread.php?t=311704&highlight=cingular+8525+rom+version and getting the production ROM version at http://wiki.xda-developers.com/index.php?pagename=Hermes_Upgrades. Back to normal - everything works fine. Just for a trial, I also downloaded ROM V2.1.1 and it works find also - but sure seems a bit large - ends up with 42.9M of storage free vs V1.34 that has 50.25. Think I'll try the the memory expansion process at http://forum.xda-developers.com/showthread.php?t=298327&highlight=want+more+storage. That seems to at least provide a more than 9 megabyte smaller MBH file but I don't know what that translates to in memory usage yet.
Suspect there is a way to fix this problem but I haven't seen anything in the forums on it.
After flashing CM6.1 I got the notorious wifi connectivity issue that numerous people have been reporting around the web. The issue is the following:
1: Wifi discovers neighbor's AP but no longer home AP.
2: Wifi problem randomly fixes itself, but sometime comes back and home AP can't be found again.
Many random solutions on the web include removing all stored AP's on the phone, resetting the router, rebooting and power cycling the phone numerous times, etc. Most people report that wifi miraculously start working again after the above but there is no consistency to exactly why and what works.
I tried all of the above with no luck, and even flashed three different roms with different kernels, did wipes, formatted everything inculding boot partition etc.
Here is the ACTUAL problem:
Different regions use different wifi channels. North America uses the first 11, most of the world uses 13, and Japan uses all 14. After flashing CM6.1 it changed the regulatory domain on the phone to only scan the first 11 channels meaning my European router broadcasting on 13 wouldn't show up. This setting seems to be persistent and doesn't change just because a new rom is flashed.
The reason people report the problem to be randomly fixed after a few days (and sometimes coming back days later) is because most routers automatically select which channel to broadcast on and therefore might end up within the first 11 at occasion. If it changes to something higher after that however, the problem is back.
Solution:
Open Settings, Wireless & network settings, Wi-Fi settings. Press "Menu" and select Advanced. Press regulatory domain and change to 14 channels.
To learn more about this and understand which channels are used in which countries, look here: http://en.wikipedia.org/wiki/List_of_WLAN_channels#2.4.C2.A0GHz_.28802.11b.2Fg.2Fn.29
Thanks man, even I still met an issue which was wifi disconnect frequently (usually after 12 seconds or less, it's re-scanning AP and trying to re-connect again) when I was trying to share my broadband internet from laptop to my legend.
BUT, after I update my wlan driver (now using 8.0.0.238 for my Atheros AR5XXX), the issue seems gone.
I found that by updating wlan driver to the very latest driver (for mine is 9.2.0.xxx) is not a guarantee to resolve this problem.
Now, by combining your suggestion and an "appropriate" driver version for my wlan, it work flawlessly until now
PS: driver version which will work varies from devices to devices. Do trial and error if you must
edit: well, not 100% gone, but much better . the connection is far more stable
Could be a problem for some but not all the issues with WiFi. I knew about this and even posted one or two times this check for the number of channels in different other topics as a possible solution. Still there are times when the connection to the "home" AP is done very late after entering in range or switching on the WiFi and the signal is changing from none to full and back frequently, for the same relative position to the router (I'm standing in the same place). Also even if the signal is full or good, the Legend seems not to have Internet connection that is, the weather updates or XDA applications or browser could not connect. This is still happening even if the selection for the number of channels is correct. And also this is not happening with a stock ROM, I made some comparisons between my Legend and one of my friends that has stock ROM. He is having full signal and excellent browsing experience while I have random disconnects or drops in signal level. My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause. As it is with some other HTC proprietary developments (like Flash implementation or FM radio), could be that HTC spent some more development time in eliminating bugs and making a better driver.
Of course, this will not stop me use CM ROMS, it is a little bit frustrating, but the other things in CM ROM's makes the difference for me.
Rapier said:
My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause
Click to expand...
Click to collapse
I think you're right. Yesterday, I tried my friend's phone (which has a stock ROM), using the same AP and there was no dropped signal or disconnected in wifi. I also tried using other android phone brand (5 series from samsung) which also has a stock ROM and there was no problem at all. Drivers is the culprit
Work
Thanks u very much.worked on my milestone
Thanks. Actually worked.
Rapier said:
Could be a problem for some but not all the issues with WiFi. I knew about this and even posted one or two times this check for the number of channels in different other topics as a possible solution. Still there are times when the connection to the "home" AP is done very late after entering in range or switching on the WiFi and the signal is changing from none to full and back frequently, for the same relative position to the router (I'm standing in the same place). Also even if the signal is full or good, the Legend seems not to have Internet connection that is, the weather updates or XDA applications or browser could not connect. This is still happening even if the selection for the number of channels is correct. And also this is not happening with a stock ROM, I made some comparisons between my Legend and one of my friends that has stock ROM. He is having full signal and excellent browsing experience while I have random disconnects or drops in signal level. My thought is that the difference between drivers made by HTC and the ones in CM ROM is the cause. As it is with some other HTC proprietary developments (like Flash implementation or FM radio), could be that HTC spent some more development time in eliminating bugs and making a better driver.
Of course, this will not stop me use CM ROMS, it is a little bit frustrating, but the other things in CM ROM's makes the difference for me.
Click to expand...
Click to collapse
Hello Rapier,
I have installed the CyanogenMod 6.1.1 (stable) on my HTC Desire (GSM / France) with latest radio image (32.49.00.32U_5.11.05.27) and taken some time to configure it. Now, everything seems to run well ... excepted the WiFi (and perhaps also the GSM). My problem is exactlw what you have described:
- on stock ROMs, the WiFi signal is stable and quite strong
- on Cyanogen ROM 6.1.1, the WiFi signal fluctuates, the connection is unstable and gets lost.
I like CyanogenMod ROMs very much. The WiFi issue is the only thing that I was not able to correct. You were speaking about WiFi drivers: would it be possible to extract the WiFi drivers from the latest HTC Desire stock ROM and copy them into the CyanogenMod installation?
My impression is that the CyanogenROM is scanning for networks in the background, even if a stable and strong WiFi network has been found and is currently connected. Perhaps there is a possibility to disable this scanning?
To finish, I have also the impression (I know, this is not very scientific ... but perhaps it could help to determinate where the issue comes from) that the GSM network is also fluctuating. I use WiFi Analyzer (available on the Android market) and when I plot a graph, without moving the phone or even without moving myself, the plot oscillates between -80dBm and -30dBm (I swear that there is nobody playing with the on/off button of my ZyXEL router ).
@sz1a: Thank you very much for your post: this helped me to discover these "hidden" settings, but my configuration is manual on the ZyXEL and everything was fine. Perhaps you should switch the thread to "unsolved".
I'n not a developer, only an ethusiast with a Legend. Also I'm not a Linux expert so I can only guess and experiment...threfore I cannot tell if porting HTC proprietary drivers is possible. I'd say not...if it was, we would have it by now. The main reason I think, is that those drivers are not open source, so nobody can port them since the sources are not available. I'm sure that if it was possible, they'll have been included in CM
Sent from my Legend using XDA App
pleaaaase help, im running CM 6.1 RC 1
wifi was working fine untill yesterday, i tried to connect to my friends router but couldnt.. i tried putting it in manually too.. then i couldnt connect to any router infact my phone wont even pick up any even my home one.. i tried switching to 14 channs like this said but no luck
any help please
Hello,
If you don't want the boring details of how I discovered the problem feel free to skip the next couple of paragraphs and go straight to the technical details.
I got my first Android phone (Motorola Defy) a couple of weeks ago and at first I was only using it with wifi because my data plan wasn't activated yet. While playing with it a little I realised that I saw a lot less ads than my boyfriend on his 6 month old Defy. I thougt it was weird but, well, seeing less ads is not a big problem.
Then when I got my data plan I saw that when I wasn't home I saw a lot more ads, so I began to suspect it had to do with how my phone was connected to the internet : wifi or 3G.
Next I wanted to try out Astrid and when I tried to log in using my Google account it failed repeatedly. Until I disabled wifi and it logged in fine using 3G.
Then I installed RTÉ DocOnOne to listen to documentaries while falling asleep. When wifi is enabled, it cannot start up because it can't connect (network timeout). Over 3G, no problem.
At first I thought it was my router blocking ports or something but it happens with different wifi APs and more importantly my boyfriend's phone, connected to the same access point, loads everything without a problem.
Let's sum up:
Some apps can't access the network using wifi but work fine when using 3G.
It happens regardless of the wifi AP (tried 4 different ones with different routers) and another phone using the same app connected to the same wifi AP can access the network just fine.
If I initiate the connection using 3G then switch to wifi (typically I launch the app with 3G, switch wifi on without closing the app), it still works after that (RTE DocOnOne has no pb streaming the documentaries once it has launched)
My phone is a Motorola Defy, French retail ROM, not rooted, no motoblur account (skipped the configuration), Froyo 2.2.2 (already on the phone when I got it), system version (if that means anything to you) Version.34.164.3.MB525.Retail.en.FR, kernel 2.6.32.9-g050ccf2, build 3.4.2-164
I can't give as much details about my boyfriend's phone (that doesn't have the problem) because he's not here right now but I can tell you that it is a Motorola Defy too, French retail (I think) ROM, Froyo updated from preinstalled Eclair (using the official Motorola update), not rooted, with a motoblur account
I have no idea if that's relevant or not, but my phone has the "google maps 5.7.0 crashes on Defy" issue (18446 in the android issue tracker) and my boyfriend's phone hasn't.
Has anyone encountered this issue before ? I couldn't find anything on this forum or with a google search.
Is there any tool I can use to try and find the cause of the problem ?
Thank you for reading all this, sorry if my message was long but I wanted to give as much detail as possible to help the nice people who may find what is wrong with my phone
I didn't read all..
but if your phone don't have problems then check this:
1. go to settings
2. Select "Location & security settings"
3. enable this "Use wireless networks" Location determined by WiFi and/or mobile networks
4. test does it work...
Hello manumanfred,
I did what you suggested (actually it was already checked) and the problem is still there (tried unchecking it too).
I am not sure why you suggested it, was that related to some phones having wifi problems in some countries ? I read a thread about that when I was researching my problem but it is different. In my case, wifi works most of the time, but some requests always time out.
Thanks for trying
Anyone else has an idea of something I could try ?
Anne-Laure said:
Hello manumanfred,
I did what you suggested (actually it was already checked) and the problem is still there (tried unchecking it too).
I am not sure why you suggested it, was that related to some phones having wifi problems in some countries ? I read a thread about that when I was researching my problem but it is different. In my case, wifi works most of the time, but some requests always time out.
Thanks for trying
Anyone else has an idea of something I could try ?
Click to expand...
Click to collapse
Hello, did you solve the issue?
Hi everyone,
First I'd like to thank those fearless tinkerers that produced (and explained the how-to) the Froyo upgrades for the Huawei s7-104.
I actually bought the device only AFTER downloading the Indonesian upgrade (that was-and still is-the extension of my faith in you).
The process worked like a charm and I successfully checked and confirmed that the new version matched the claimed upgrade.
I later managed to root the device and now even enjoy a longer battery life thanks to CPU Master set on "on demand".
The only problems I encountered were:
- Sometimes the screen orientation gets stuck in horizontal or vertical and the device needs to be rebooted to unlock the orientation. This is minor and doesn't bother me that much.
-I have lost 3G connectivity and neither the carrier nor a mobile lab has managed to get a shred of data into the device with anything but WiFi.
The Network pane says that it's connected and should receive data.
The APN settings should now be reviewed and corrected since I brought the device to the carrier's office and, after their failure to fix the problem, to the lab (they told me they did anyway).
The SIM was then taken out and connected into another device. It received data merrily, proving satisfactorily (at least to the C.Y.A. carrier) that they could not help me further.
Everything else works beautifully, phone, WiFi, GPS, everything...
Any idea? I live in Mexico and the carrier is Movistar.
Thank you in advance.
Thimage
screen orientation quick fix
can't comment on the 3G problem din really face it
you can try flashing to another rom
Zmey Mod from Belarus! would be a good choice
for screen orientation just install shake n rotate from the market
it's just a quick fix which can settle the problem
Thanks for the shake'n rotate tip! I'll try it!
Never heard of the zmey mod from Belarus. Is it in english or in local lenguage? I'll try to find it anyway.
Anybody out there who's actually had the same network connectivity problem that I've had? Can't be the only one right?
Thanks again,
Thimage
Connectivity recovered
I finally recovered connectivity by looking for the right APN on the web and I found it here:
decibel-elektrobeat.blogspot.com/2011/04/3g-de-movistar-configurado-en-xperia.html
The reason why it didn't work before is because for some reason it is not enough to correct the APN after flashing the Rom. You have to delete it and create a new one.
It works fine now.
Thanks. T
This thread is about the 3 types of known wifi-roaming bugs, how to differentiate these and fix at least one of them with a little hack.
Documentation of the bug avioded by this workaround on Google: Click Here
BIG NEWS!! As mentioned by a spanish user above there are newer firmwares, that are correcting the wifi-roaming bug, that was fixed by this fix.
Confirmed by an german OTA-Update. So try upgrading your firmware to fix the bug.
But : Keep in mind that an OTA-Update, official from Samsung wont install on a modified system. This includes also our modified wpa-supplicant. So if you want to use a newer firmware you have to restore the old wpa-supplicant: View attachment wpa_supplicant.zip(From The newest Firmware in Germany[OTA-Eplus, JZO54K.I9300XXELL4)
General facts to know about buggy Wifi-Roaming on Android Devices:
Bugs types that are existing
1.The phone never tries to roam by, unless it completely loses signal. Then it connects to the strongest AP. This is the typical Galaxy S2 bug.
2.The phone never tries to roam, and on top of that tries to reconnect to the specific AP that it knows, even if it is right next to a better one while connecting. This has been observed on some Nexus devices, but is apparently fixed on the Galaxy Nexus running CM10.
3.The phone tries to roam as it can see a better AP, but drops the connection and reconnects to the stronger AP shortly after. That's the typical Galaxy S3 and Galaxy Nexus bug, which is fixed by the hack described in this thread.
Only Bug 3 in this list is fixed by this hack. It will not help for the other two bugs!
To determine which bug you are observing, try this:
- Pick two access points that are within range of each other, we will call them AP1 and AP2.
- Locate the phone close to AP1, turn on wifi, and connect to the network. You should get full signal strength.
- Start listening to a web radio stream using e.g. TuneIn Radio (available on Play Store), configure the buffer size to the minimum possible.
- Slowly walk towards AP2, watching the signal strength indicator.
- If you reach AP2 and the phone still shows a low signal strength (at most one bar) after 10-20 seconds:
You are observing a different bug which is not avoided by this workaround.
- Turn off wifi and turn it back on again.
- If the phone now connects to AP2 and shows a high signal strength, you are observing the Galaxy S2 bug --> Bug 1 in the list
- If the phone still connects to AP1 and shows a low signal strength, you are observing the Nexus bug --> Bug 2 in the list
- If the connection drops before getting close enough to AP2, the access points are too far away from each other. -->Retry with a different set of access points.
- If the signal strength seems to increase while getting closer to AP2, but then the wifi icon disappears briefly and comes back after a few seconds, and the web radio stream drops, you are observing the Galaxy S3 bug, and this workaround will help you. --> Bug 3 in the list
- If the signal strength increases while getting closer to AP2, the wifi icon doesn't disappear, and the web radio stream doesn't drop, everything is working normally --> no bug:
-You might have a device that just doesn't have a wifi bug. Apparently such devices indeed exist.
-You might have a Galaxy S3 or Galaxy Nexus, but you were lucky. Try walking back to AP1 and check if it drops the connection this time.
-You might have already applied the workaround above, or a different fix for the same bug. (However there doesn't seem to be one yet.)
______________________________________________________________________________________________________________________
Now as you know which bug your device has you maybe have noticed that your device has bug type 3, here is the hack to fix it:
IMPORTANT: IM NOT RESPONSIBLE FOR NOT WORKING DEVICES AFTER THIS PROCEDURE. INSTALL AT YOUR OWN RISK!! THIS MOD IS EXPERIMENTAL!!
THIS MOD ONLY IS CONFIRMED WORKING FOR THE SAMSUNG GALAXY i9300 AND THE SAMSUNG GALAXY NEXUS i9250
For the installation procedure i give here root rights are needed. It also is recommended to make a CWM-Backup before. If you are unsure about root rights or dont know how to use a Custom Recovery feel free to ask before you do anything.
Installation Instructions for the Standalone-file(no Custom-Recovery needed):
1. Download View attachment Standalone-file.zip and unzip
2. Search for your original "wpa_supplicant"-file in \system\bin.
You can use any Explorer that offers root-acess but be sure you set the permissions to rwx r-x r-x if you use another file explorer as i mentioned. It is needed for the file to have the permission to be executed
(f.e. Root Browser Lite)
3. Copy your original "wpa_supplicant"-file to any location you will remember in case anything goes wrong.
4. Delete the original "wpa_supplicant"-file from the folder
5. Paste the modified "wpa_supplicant"-file downloaded from here in \system\bin. Make sure the file still is named "wpa_supplicant"
6. Reboot your device
Installation Instructions for CWM Flashable-file(CWM-Recovery needed):
1. Download View attachment 1549825
2. Copy the downloaded file to your sdcard.
3. Search for your original "wpa_supplicant"-file in \system\bin.
You can use any Explorer that offers root-acess but be sure you set the permissions to rwx r-x r-x if you use another file explorer as i mentioned. It is needed for the file to have the permission to be executed
(f.e. Root Browser Lite)
4. Copy your original "wpa_supplicant"-file to any location you will remember in case anything goes wrong.
5. Reboot to recovery and flash the downloaded file.
6. Reboot your device.
Your device should now roam correctly from one AP to another.
Please leave your feedback here in the thread and hit the thanks-button if it fixed your problem. ENJOY
FOR ADDITIONAL INFO: Click Here
______________________________________________________________________________________________________________________
Special Thanks to:
- TheSeven, who created this hack
- querty12, who created the flashable CWM-file
- Gabeloooooo, who was the first to give me feedback about this
I hope this leads to a fix. GS3 is garbage when there is more than 1 AP, makes VOIP useless.
Yeah thats the Main Problem with this.
Also Streaming apps, spotify and so on suffer from this issue
I will add the modified wpa_supplicant to replace with the old on soon
felixchris said:
Yeah thats the Main Problem with this.
Also Streaming apps, spotify and so on suffer from this issue
I will add the modified wpa_supplicant to replace with the old on soon
Click to expand...
Click to collapse
Technically speaking, will someone be able to make this fix available for stock sammy roms as well?
Gabeloooooo said:
Technically speaking, will someone be able to make this fix available for stock sammy roms as well?
Click to expand...
Click to collapse
Actually this fix was tested on Stock Rom and Cyanogenmod It works on official Stock Roms as well Just have to be rooted
Tried it, breaks wifi. Can't enable wifi anymore. (i9300 stock 4.1.1)
And oddly enough, restoring the old file back to system\bin doesnt fix it. Will do a couple of tests than will restore from nandroid.
Ok, the reason it didn't work is permissions. Copying using ES explorer did not give the execute permission. Now both files allow me to enable wifi. Will report back on AP roaming after using for a while.
Thanks for your feedback Gabeloooooo
Can you please, after finishing your tests, tell me which permissions you did to set ? as i can mentione it in the instructions
i only tested with root browser...
Used this: rwx r-x r-x
thx will add it to the instructions
Things seem MUCH better with this fix. It is no longer constantly disconnecting. MAJOR IMPROVEMENT!!
I haven't tested groove ip yet, too many bad experiences in the past, but will try it this week to see how it fares.
So maybe if you like the world you could drag it out to the SGS3 - World as i am normally focused on the SGSL- Forums But thanks gor the feedback
Sent from my GT-I9003 using xda app-developers app
Will this work on the LG Nexus 4?
It has a Murata SS2908001 802.11 a/b/g/n Wi‐Fi and Bluetooth module according to ifixit.
Will this work on the LG Nexus 4?
It has a Murata SS2908001 802.11 a/b/g/n Wi‐Fi and Bluetooth module according to ifixit.
Click to expand...
Click to collapse
First of all: Has the Nexus 4 really this bug?
if yes, there is a chance that it will work as the problem comes from google code itself, so basically every device can have that problem if they dont do anything against.
But this fix isnt a real fix, it an provisoric hack, that solves the problem
So for now its only confirmed working on Samsung SGS 3 and Samsung GN. I recommend just install it according to the instructions and you see if it changes anything. If not revert back
Is it safe to apply to latest 4.1.2 sammy rom, or do they never change the wpa applicant file?
Is it safe to apply to latest 4.1.2 sammy rom, or do they never change the wpa applicant file?
Click to expand...
Click to collapse
It was tested on this Version and till now they never changed it
I was pointed to this thread from SGS2 forum... http://forum.xda-developers.com/showpost.php?p=35143039&postcount=41
Now I read, that this is only for SGS3...
Is there any possibility that this will work on SGS2? :fingers-crossed:
felixchris said:
First of all: Has the Nexus 4 really this bug?
if yes, there is a chance that it will work as the problem comes from google code itself, so basically every device can have that problem if they dont do anything against.
But this fix isnt a real fix, it an provisoric hack, that solves the problem
So for now its only confirmed working on Samsung SGS 3 and Samsung GN. I recommend just install it according to the instructions and you see if it changes anything. If not revert back
Click to expand...
Click to collapse
Hello, brand new to Android and the forum and I was referred here by a thread on code.google.com. The id=22575 (I can't post a direct link).
I can confirm I have the bug on a Nexus 4 with Android 4.2.1.
My home network has 2 different APs with the same SSID and same security. There is a "primary" AP and a wireless repeater, both running DD-WRT. My Nexus 4 will only connect to the primary AP. Even if I forget the network and attempt to connect to the repeater standing inches away from it, the Nexus 4 still associates with the primary AP.
Thank you!
Jard16 said:
Hello, brand new to Android and the forum and I was referred here by a thread on code.google.com. The id=22575 (I can't post a direct link).
I can confirm I have the bug on a Nexus 4 with Android 4.2.1.
My home network has 2 different APs with the same SSID and same security. There is a "primary" AP and a wireless repeater, both running DD-WRT. My Nexus 4 will only connect to the primary AP. Even if I forget the network and attempt to connect to the repeater standing inches away from it, the Nexus 4 still associates with the primary AP.
Thank you!
Click to expand...
Click to collapse
did this fix work on your Nexus 4?
drewski_1 said:
did this fix work on your Nexus 4?
Click to expand...
Click to collapse
I will have to try it some time next week when I learn enough to actually apply it. Again, this is my first Android phone so this is all very new to me.
My workaround was to install another AP using a different SSID and use the app 'Best WiFi' to force switch when the signal drops too low. I just got the phone yesterday.
SGS2 and Nexus4
I was pointed to this thread from SGS2 forum... http://forum.xda-developers.com/show...9&postcount=41
Now I read, that this is only for SGS3...
Is there any possibility that this will work on SGS2?
Click to expand...
Click to collapse
The SGS2 also had problems with WifiRoaming, but they were different as far as i know. This fix shouldnt work for the Galaxy S2.
Quote:
Originally Posted by drewski_1 View Post
did this fix work on your Nexus 4?
I will have to try it some time next week when I learn enough to actually apply it. Again, this is my first Android phone so this is all very new to me.
My workaround was to install another AP using a different SSID and use the app 'Best WiFi' to force switch when the signal drops too low. I just got the phone yesterday.
Click to expand...
Click to collapse
I dont know of what kind the bug of the Nexus 4 is. So i dont know if it will fix anything. As posted above you can just install it and see if it changes anything Be sure to follow the instructions and BACKUP!!