Related
I'm running stock unrooted. Before the update I was able to select which frequency I wanted to scan for under the Wifi Advanced menu...either 2.4 or 5.0 ghz. My Netgear router is dual band and I had selected 5.0 so I could connect to the N signal instead of the G signal, which is on 2.4 ghz.
Well, after the update today, I checked the Wifi Advanced menu and I can't select frequencies anymore. Furthermore, I'm stuck on 5.0 ghz and can't connect to my G signal either, only the N.
Does anyone else on LG8 stock have this issue? I searched the other settings to see if they moved it somewhere else but it's nowhere to be found.
"Any hep would be hot."
Sent from my SPH-L710 using xda premium
I notice the same thing. I'm not rooted but if you are I think that some of the developers (freeza) I just don't know if it's just going to be in zip form to flash it or if we have to flash the whole Rom again. What I did is flash back to stock and change this settings to Auto and then flash back LG8 manually. Here is the directions that I follow:
http://forums.androidcentral.com/sprint-galaxy-s-iii/195095-unroot-return-stock.html#post2017547
I hope this help
it is gone and was by design, no worries, it is automatic and behind the scenes and isn't really a battery drainer by any means.
Naddict said:
it is gone and was by design, no worries, it is automatic and behind the scenes and isn't really a battery drainer by any means.
Click to expand...
Click to collapse
It is not by design. It has to be a mistake. I am stuck in 5.0 ghz and cannot connect to any WiFi broadcasting at 2.4 ghz. McDonalds and Starbucks are not available to me because. This menu is on page 54 of the manual. It doesn't make sense to take this option away, especially if I want to connect to the N instead of G.
I just got off the phone with Tech Support and they hadn't heard of this before. They said to take it into a Sprint store to be looked at. I'll give an update later.
dennistpm said:
It is not by design. It has to be a mistake. I am stuck in 5.0 ghz and cannot connect to any WiFi broadcasting at 2.4 ghz. McDonalds and Starbucks are not available to me because. This menu is on page 54 of the manual. It doesn't make sense to take this option away, especially if I want to connect to the N instead of G.
I just got off the phone with Tech Support and they hadn't heard of this before. They said to take it into a Sprint store to be looked at. I'll give an update later.
Click to expand...
Click to collapse
Yes, I too notice that if you flash while in 5Ghz Mode from whatever to LG8, your stuck on 5GHz mode. So you will have to find an LG8 rom like freegs3 and flash the mod for the wifi frequency selection, or go back to lg2 or lf9 and do the same and then upgrade.
So i went into the repair center and they only said it's a known issue. Their only fix was to do a master reset, which I had no interest in doing. I guess I'm going to have to root and flash a Rom.
Does anyone have a fix that doesn't involve rooting?
Sent from my SPH-L710 using xda premium
Hey There,
I've just installed this fine ROM today, and it seems great,
but for some reason, the wifi reception is BAD now.
It works fine if I seat near my router, but if I move 3 meters away
it looses the connection ... and says the reception is POOR.
Any1 else has this problem?
Which version of CM10 did you flash, if it's anything older than beta 1 try flashing Beta 1 ? if you still have problems after Beta1
Try flashing a different kernel and see if that resolves your problem. (if i can spare you some time, try faux123's kernel)
http://forum.xda-developers.com/showthread.php?t=1647993
And then if you still have problems.
Try running the Viper ROM 2.6.0 with the Butter hacks runs very smooth.
http://forum.xda-developers.com/showthread.php?t=1745176
Thanks for the quick replay
I flashed the "[08-09] [ROM] CyanogenMod 10 - Endeavor Unleashed" rom.
I don't think this is the same cm10 everyone's using.
and I don't really understand, doesn't the Kernal comes with the rom?
Can I change it without changing a rom ?
alexx_za said:
Which version of CM10 did you flash, if it's anything older than beta 1 try flashing Beta 1 ? if you still have problems after Beta1
Try flashing a different kernel and see if that resolves your problem. (if i can spare you some time, try faux123's kernel)
http://forum.xda-developers.com/showthread.php?t=1647993
And then if you still have problems.
Try running the Viper ROM 2.6.0 with the Butter hacks runs very smooth.
http://forum.xda-developers.com/showthread.php?t=1745176
Click to expand...
Click to collapse
I notice the same problem a few days ago (I think is since I have install CM10). I have switched on OrDrost since 2 days, I tried the Faux kernel and finally I just revert to full stock rom and my wifi signal haven't change :/
// Edit : after more search, it's a hardware fault :
XDA news
XDA thread
Thesalan said:
// Edit : after more search, it's a hardware fault :
XDA news
XDA thread
Click to expand...
Click to collapse
But on the stock rom WIFI was ok.
Update: Ok I did the "Squeeze" test. Wifi is great whn I squeeze
So it is a hardware problem?? How it only started after I put CM10?
Have you reinstalled the stock rom since you have the problem?
I don't know if CM10 is the cause, or it's a coincidence..
there's an UNOFFICIAL release at the moment which may fix some issues, though I've not noticed anything and I've had every release since A10 installed, so it could be a hardware issue.
I'm on the newest build of cm10 and my WiFi network is fine. I can from leedroid and so far just the same. I do have a tiny bit of earphone cable between my back and hard case which gives me my full bar due to the hardware fault.
Couldnt be bothered sending it back. So this works. Bit did recorded it with HTC so they know I have the fault.
Sent from my HTC One X using xda app-developers app
Thesalan said:
Have you reinstalled the stock rom since you have the problem?
Click to expand...
Click to collapse
Not yet, I really hate the stock rom.
tgcp, Where can I get this rom?
(Although it really seems like an hardware problem,
I heard the latest stock update helps a little so there
might be a software solution)
Rodbouy said:
I'm on the newest build of cm10 and my WiFi network is fine. I can from leedroid and so far just the same. I do have a tiny bit of earphone cable between my back and hard case which gives me my full bar due to the hardware fault.
Couldnt be bothered sending it back. So this works. Bit did recorded it with HTC so they know I have the fault.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
But if you use Cm10 without that little earphone cable, the wifi won't work good?
BTW, what does htc support ask to fix the problem? Do they care you rooted and unlocked the device?
The cable is about 3mm in lengh and as i have a hard case, its enough to compress the connection inside the phone where the fault is.
Htc would of course fix it, but whats the point if the phone is working and its not noticeable.
I would have had to relock bootloader and go back on stock rom.
Sent from my HTC One X using xda app-developers app
Rodbouy said:
The cable is about 3mm in lengh and as i have a hard case, its enough to compress the connection inside the phone where the fault is.
Htc would of course fix it, but whats the point if the phone is working and its not noticeable.
I would have had to relock bootloader and go back on stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
but it is noticeable!
I can't move more then 2 meters from my router or it disconnects.
Does your wifi issue not that bad? (without the cable's help)
With out my fix the signal is a joke. 1 bar when 3 feet away. Wasnt usable.
Sent from my HTC One X using xda app-developers app
Rodbouy said:
I would have had to relock bootloader and go back on stock rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Problem is I can't get back to stock! from what I understand the Stock RUU for my phone wasn't released ...
Do you think HTC will be "understanding" and fix the wifi issue even with a custom rom?
(they'll know anyway that I opened bootloader)
Try flash the Rom with the stock kernel, that will surely solve the WiFi problem.
Sent from my HTC Desire C using xda premium
Did you not do a backup before installing custom rom. Im positive that even if you relock the bootloader they can see that if they went in to recovery. But unlikely. So if you flash stock rom and re lock bootloader, remove root you should be fine
Sent from my HTC One X using xda app-developers app
Hi, try using tbaldens CM10. It can be found under HTC ONE X ORIGINAL ANDROID DEVELOPMENT. I found this to be the best CM10
I have been chasing this problem ever since installing CM10 on my Evo 4g LTE. I was getting 4 times the wifi distance on the stock rom. I go about 30 ft. outside the office and wifi drops. Also, what is the most annoying... I stream over our LAN, and when the screen is off, it turns wifi off after a few minutes. (and yes, the check box is checked to keep wifi alive). I've also tried all of the wifi fix apps and none work. If I leave the screen on and stream........ it is good anywhere from 1/2 hour to an hour, then it will just stop. This kills my battery of course. The problem 1st occured when I first bought my OEM 4g lte, but there was an option in the advanced menu "best wifi performance", after checking that, it worked great, then I switched to CM10 and I now have the wifi issue, and there is no option for "best wifi performance". I've tried a couple other jellybean roms and they have the issue as well. This is driving me nuts. I hope someone finds a solution. I don't think the average person would find this as a problem, but when I stream over the net and move all about the shop, it is unacceptable.
I faced the same issue but not on any other ROM. It was specifically with Cyanogenmod 10. I was upset because it gave me the best results but the wifi result was really poor.
However, since I work with wireless networks often, I decided to explore Cyanogenmod's wifi settings. I noticed that if you go in the Advanced Wifi functions (which you can find in the Wifi options menu) you will notice that there is an option called "Wi-Fi Region Code".
Apparently, this option allows you to select the frequency bands your device can operate and is subject to the different world regions. It is quite possible that your Access Point follows the regulatory body of your country and you should know which frequency bands they allow the AP to operate. Due to this it may be just that the Cyanogenmod, by default, put you in a different regulatory domain and limits your frequency band to a subset offered by the AP. Hence, this effectively limits your wifi reach even if you are sitting right next to the AP.
I chose "Japan" since I remembered that their regulatory domain allowed for quite a large subset of frequencies that are allowed on the WIFI spectrum. This immediately increased my received signal strength and I did not have any problem since.
I suggest you play with this, it is likely that your android device will start functioning correctly. However, if you are facing this limited frequency issue on more than one device and that too running different operating systems and different wifi hardware...chances are that your wifi router is malfunctioning. In that case, replacement or repair of the Access point is the best alternative.
Good luck. I hope this solves your problem.
rectorfury said:
I faced the same issue but not on any other ROM. It was specifically with Cyanogenmod 10. I was upset because it gave me the best results but the wifi result was really poor.
However, since I work with wireless networks often, I decided to explore Cyanogenmod's wifi settings. I noticed that if you go in the Advanced Wifi functions (which you can find in the Wifi options menu) you will notice that there is an option called "Wi-Fi Region Code".
Apparently, this option allows you to select the frequency bands your device can operate and is subject to the different world regions. It is quite possible that your Access Point follows the regulatory body of your country and you should know which frequency bands they allow the AP to operate. Due to this it may be just that the Cyanogenmod, by default, put you in a different regulatory domain and limits your frequency band to a subset offered by the AP. Hence, this effectively limits your wifi reach even if you are sitting right next to the AP.
I chose "Japan" since I remembered that their regulatory domain allowed for quite a large subset of frequencies that are allowed on the WIFI spectrum. This immediately increased my received signal strength and I did not have any problem since.
I suggest you play with this, it is likely that your android device will start functioning correctly. However, if you are facing this limited frequency issue on more than one device and that too running different operating systems and different wifi hardware...chances are that your wifi router is malfunctioning. In that case, replacement or repair of the Access point is the best alternative.
Good luck. I hope this solves your problem.
Click to expand...
Click to collapse
I've tried changing my Region Code, but for some reason it keeps defaulting back to Europe... Any ideas? I've tried changing it numerous times, same result.
So I have tried to trace my issue to it's roots and after a lot of investigation I decided to make this thread.
The issue:
When connecting to home wifi network I get "Authentication error occurred" even though it's the good password.
It first occurred on stock 4.1.1 ROM with stock Kernel even before rooting. What's more interesting is that I've successfully used the same wifi network for around a month. Other devices connect just fine, no settings on the router changed when this started happening. Didn't fiddle with any settings on the phone neither. I can connect to free wifi APs just fine.
What I've tried:
Dialing *#0011# and from service mode disabling wifi power saving feature.
Using all possible encryption combinations on the router (Open - no password, WEP, WPA-PSK AES and/or TKIP, WPA2-PSK AES and/or TKIP or both WPA and WPA2 at the same time), switching channels, disabling 802.11n mode.
Using some modded wpa_supplicant files from this thread.
Using a bad password just to get a different error.
Downloading some other wifi connectors from the Play Store including Wifi Connection Manager which claims to "Fix device Wi-Fi problems." by cleaning the stored wifi config files and maybe something more.
Flashed Omega v10 ROM with Perseus kernel.
All these things and basically any combinations of them worked to no avail. And the only thing that helped was being very close to the router. That way I manage to connect but moving a couple of meters away, like to a nearby room, and it starts giving the same error even though the network strength is still full at that point.
My thoughts:
I saw a similar issue at a couple of places including a similar thread last active dec 23rd, Android issues on code.google.com and androidforums, but no solutions found there worked. Also comparing how my old original Note and an even older LG P500 perform, the wifi signal is obviously weaker on the Note 2. My area is not heavy on wifi networks, so my guess is there's something wrong with wifi drivers or configuration. Sooooo.... What can I do to remedy this issue and also is there any way to beef up my wifi in the process?
OrangGeeGee said:
So I have tried to trace my issue to it's roots and after a lot of investigation I decided to make this thread.
The issue:
When connecting to home wifi network I get "Authentication error occurred" even though it's the good password.
It first occurred on stock 4.1.1 ROM with stock Kernel even before rooting. What's more interesting is that I've successfully used the same wifi network for around a month. Other devices connect just fine, no settings on the router changed when this started happening. Didn't fiddle with any settings on the phone neither. I can connect to free wifi APs just fine.
What I've tried:
Dialing *#0011# and from service mode disabling wifi power saving feature.
Using all possible encryption combinations on the router (Open - no password, WEP, WPA-PSK AES and/or TKIP, WPA2-PSK AES and/or TKIP or both WPA and WPA2 at the same time), switching channels, disabling 802.11n mode.
Using some modded wpa_supplicant files from this thread.
Using a bad password just to get a different error.
Downloading some other wifi connectors from the Play Store including Wifi Connection Manager which claims to "Fix device Wi-Fi problems." by cleaning the stored wifi config files and maybe something more.
Flashed Omega v10 ROM with Perseus kernel.
All these things and basically any combinations of them worked to no avail. And the only thing that helped was being very close to the router. That way I manage to connect but moving a couple of meters away, like to a nearby room, and it starts giving the same error even though the network strength is still full at that point.
My thoughts:
I saw a similar issue at a couple of places including a similar thread last active dec 23rd, Android issues on code.google.com and androidforums, but no solutions found there worked. Also comparing how my old original Note and an even older LG P500 perform, the wifi signal is obviously weaker on the Note 2. My area is not heavy on wifi networks, so my guess is there's something wrong with wifi drivers or configuration. Sooooo.... What can I do to remedy this issue and also is there any way to beef up my wifi in the process?
Click to expand...
Click to collapse
I had somewhat the same issue. Autentication error.Even though WIfi worked properly on my Galaxy y.
From v9, I flashed v6 Omega and then everything was working fine. So go ahead and flash Omega v6.
And after that did you go back to a Jelly Bean ROM?
Edit: at first I figured omega v6 wasn't JB, but then I checked... For the peace on my mind I'll try flashing Omega v6 later today.
OrangGeeGee said:
And after that did you go back to a Jelly Bean ROM?
Click to expand...
Click to collapse
When I went to v6, all was working well. But when v10 was released,i flashed it,hopiing that the wifi issue is not there but alas same result.
Before flashing,I made a backup of my wifi folder found in root folder /etc/wifi .
After flashing v10, and overwriting the wifi folder with the one that i had backed up, the issue was solved even on 4.1.2 for me.
Worth a try mate.
Do report back.
zeeshanonlyme said:
When I went to v6, all was working well. But when v10 was released,i flashed it,hopiing that the wifi issue is not there but alas same result.
Before flashing,I made a backup of my wifi folder found in root folder /etc/wifi .
After flashing v10, and overwriting the wifi folder with the one that i had backed up, the issue was solved even on 4.1.2 for me.
Worth a try mate.
Do report back.
Click to expand...
Click to collapse
Sounds very interesting. Will report Dunno if an upcoming exam is more important than solving this issue now
OrangGeeGee said:
Sounds very interesting. Will report Dunno if an upcoming exam is more important than solving this issue now
Click to expand...
Click to collapse
The curiosity will hamper your exam!
Is it today?
Well there's 24 hours left, but work and catch-up for half a year is no small feat
To follow up, did flashing Omega v6 work?
i'm really keen to know as I am having the problem currently.
Authentication Problem Wifi - solved for me
Hi folks - I had the same issue with my Galaxy Note I717 (it's the AT&T Note 1) that I got yesterday. I have no problem with my T959 Vibrant to connect to my router at all. But the Note always gave me the authentication problem. So I took it with me to work today and no problems at all to connect to Wifi over there - everything just worked fine.
Back at home - same issue. So I was thinking about to reset my router when I saw this button on it's side and I remembered that I had read something in the settings of my phone.
So that's what I did: When choosing the network on the phone I went to advanced settings. WPS - here I choose Push Button. After that I pushed the button on my router and voila everything worked as supposed.
After switching Wifi off and back on there was no authentication problem anymore. So to confirm the whole thing I let the phone forget the connection and I had the same authentication problem. After choosing WPS "push button" and pushing the button on the router everything worked again.
I don't know - maybe it's just basics for a lot of guys here, but I was glad to figure that out by myself and maybe it helps someone else.
In the case that it might be important - my Note runs stock ICS 4.0.4, stock kernel. is rooted and unlocked. The Vibrant runs ICS Passion V13.1 and Kernel Kiss Yum Yum Good #2. The router is a D-Link DIR 655 Wireless N
Following up the thread:
No, flashing omega v6 didn't work for me.
What I found out is actually 5 GHz band routers work just fine (for example at my university) and all the 2.4 GHz ones give the same error if I'm not close enough to them (something like 5 meters with straight visibility and 2 meters behind closed doors with my home router Comtrend WAP 5813n).
I have called Samsung's Warranty Center to ask for assistance and since we don't have official Samsung service centers in Lithuania, they told me partnered service centers might just return the phone to me as it is and so they would call me when they found out more about this issue (that was almost 2 weeks ago). Will call them again tomorrow and will post any updates if the story develops.
EDIT: After talking to them they apologized for taking so long and assured me I was not forgotten and the issue was forwarded to UK because they have no records/info about it here in Lithuania. Strange thing is I still have my phone, they didn't even wanna check it out.
Note 2 wireless issues
Lads I tried EVERYTHING to get connection working after it dropped on me after a month. Done everything I have read on every forum. EVERYTHING. All other Samsung devices work fine except this note 2! One other odd thing I discovered. It connects fine to any modem or roster fine then when try again on each it won't. You tell me guys? I had it with this issue. Help before I chuck it in Port Phillip Bay!
Hello Jumbo,
i had the same problem and read a lot threads about this error message.
For me it looks like not all who get this error have the same problem.
Some wrote that they fixed it by
- exchanging the wifi folder with the one from 4.1.1..
- flashed a different kernel
- downgraded to 4.1.2
- changed wifi energy saving stuff
- messed around with their routers
and so on..
I also did all this stuff but with no success..
In my case I figured out that
- the same problem exist on 3 different routers (so it couldn't be a router issue)
- the wifi speed (when I sometimes got connected) kept falling from 65MBit down to 5MBit
and by having a wifi connection, I couldn't reach any webpage.
- then I recognised, that I only had a working connection, when I was close
to my router, like 1 or 2 meters without anything between us. In this case
I had no problems with authentication and to surf on the web.
I decided to send my Note2 in for a repair, and guess what... They changed my
Mainboard and since then, everything is back to work..
How long did it take for the repair? I can't imagine being without my phone for an extended period....
I know, it's an addiction, but I'm ok with that..
Steve
I have an identical issue with my S3 GT-I9300
For a totally reliable wifi connection, I've had to site the cradle for the phone on top of my router!
Am out of warranty, so if anyone finds a fix for this that does not involve a mainboard change...
(My first post on this site- I just wish it had been a fix rather than a query)
fuzzer said:
How long did it take for the repair? I can't imagine being without my phone for an extended period....
I know, it's an addiction, but I'm ok with that..
Steve
Click to expand...
Click to collapse
Sorry for the late answer.
My repair took 1 week...
shipped it to w-support on Monday and got it back Saturday.
I was really happy with w-support here in Germany.
I've reset my device to stock and so far it's been sitting @ warranty center for a week, no answer about the roots of the problem yet..
May have found a solution
Hi,
I had the similar problem. With me it started happening after I changed to a Zyxel modem. After some investigation I noticed that in the Zyxel the default gateway is set at 192.168.1.254 whereas most other brands use 192.168.1.1.
Have an inkling that Android doesn't play nice with non-192.168.1.1 gateways.
So changed this in the router settings.
To be sure I also allocated fixed IP on the LAN to my devices and made sure that in the advanced settings of my WiFi network on the Android device I made sure the primary and secondary DNS addresses matched those that the router uses.
Oh.. And to top it all off I fixed the broadcast channel of the router to channel 11 (Probably best you use an app like WiFi Analyser from the Play Store to find the channel that works best for you)
This seems to have solved it for me for now. (I know, not a very scientific method, but got fed up with trying to isolate the culprit)
BTW. Am running (1) Galaxy Note on latest stock ROM (rooted though) (2) Galaxy Tab 2 7" (stock JB ROM - non rooted).
Hope this helps..
Sounds so strange that gateways and channels did it for you. I've tried to change channels on my router with no results. Also I have tried way too many routers before I decided router settings were not a problem. I guess we may have different kind of hardware/software faults resulting in same error message.
OrangGeeGee said:
Sounds so strange that gateways and channels did it for you. I've tried to change channels on my router with no results. Also I have tried way too many routers before I decided router settings were not a problem. I guess we may have different kind of hardware/software faults resulting in same error message.
Click to expand...
Click to collapse
I know. It is weird.
Mind you only a few hours have passed since my changes. I'll keep an eye on it if it reverts to it's old state.
Ok.
Had the same issue again this morning, but oddly enough, once it connects, it stays connected. Also when the phone is put to sleep.
Sent from my GT-N7000 using xda app-developers app
hi friends this is my first post in GS3 world. We live in a rural area and are dependent on good WIFI service - I do tech work so the WIFI in the hacienda is very robust. All our other many devices love the WIFI rig: 2 ipad mins, one Galaxy Note 1, another older Galaxy, two laptops, one HTPC, etc. Only the new-to-me GS3 has issues with it. The visual indicator on the handset seems to not give an accurate picture, so we keep going into settings and seeing what is reported there... "Strong" signal is usually what displays, but in use, sending messages, making wifi calls, whatever, the results are pretty bad. We're using the stock messaging [google] app and stock T-Mobile WIFI calling app.
I want to say that web browsing is a little better, but can't really give details.
ROM etc:
android 4.1.2
baseband T999UVDMD5
Kernel 3.0.31-1128078
build JZ054K.T999UVDMD5
searching around the web I see a lot of the same complaints but really lousy diagnosis and lousier fixes [turn off 'data'; reboot the handset; call T-mobile... that sort of 'fix']
What is the scoop? Is there an internal WIFI antenna connection inside that needs to be checked?
Is there some elusive patch from Samsung?
Is the rig Channel-sensitive? [some older handsets only liked channel 11, or others only channel 6, etc.]
pls point me to the definitive thread if there is one...
thanks in advance
I'm not sure of any threads with much information on this. I don't recall seeing very many WiFi issues at all with the S3.
Are you rooted? Custom ROM?
If so you may want to try some of the other modems/baseband. Link in my Sig.
Otherwise, maybe try Odin flashing the UVDLJC or LJA firmware.
You say it's new to you, so I'm assuming you got it used. Do you know who you bought it from and did they report any problems?
How does it perform on other WiFi networks?
Sent from my SGH-T999L using xda premium
DocHoliday77 said:
I'm not sure of any threads with much information on this. I don't recall seeing very many WiFi issues at all with the S3.
Are you rooted? Custom ROM?
If so you may want to try some of the other modems/baseband. Link in my Sig.
Otherwise, maybe try Odin flashing the UVDLJC or LJA firmware.
You say it's new to you, so I'm assuming you got it used. Do you know who you bought it from and did they report any problems?
How does it perform on other WiFi networks?
Sent from my SGH-T999L using xda premium
Click to expand...
Click to collapse
Yep, flash stock or root66 firmware of choice. We will go from there.
Aerowinder said:
Yep, flash stock or root66 firmware of choice. We will go from there.
Click to expand...
Click to collapse
its all stock now.
are you saying to go ahead and nuke, reinstall stock ROM?
I don't have the option of going down Root66 - we are utterly dependent on WIFI Calling.
Is there a way to stop scanning selectively? that is, when I am on my own AP, there's no point in constantly scanning - there are other very weak wifi AP's in the vicinity and I"m wondering if somehow that causes an issue? my Note 1 is rock-solid. I don't recall a single drop with it in the 6 months I've had it. Most disconcerting is when WIFI calling drops - I've been using T-mobile devices for years and only once did I have one for which WIFI calling would disconnect, restart, and reappear like this. It will drop out, then refind its WIFI connection, then you get the "WIFI is Ready" all over again, just like you do when Rebooting the phone.
cognus said:
its all stock now.
are you saying to go ahead and nuke, reinstall stock ROM?
I don't have the option of going down Root66 - we are utterly dependent on WIFI Calling.
Is there a way to stop scanning selectively? that is, when I am on my own AP, there's no point in constantly scanning - there are other very weak wifi AP's in the vicinity and I"m wondering if somehow that causes an issue? my Note 1 is rock-solid. I don't recall a single drop with it in the 6 months I've had it. Most disconcerting is when WIFI calling drops - I've been using T-mobile devices for years and only once did I have one for which WIFI calling would disconnect, restart, and reappear like this. It will drop out, then refind its WIFI connection, then you get the "WIFI is Ready" all over again, just like you do when Rebooting the phone.
Click to expand...
Click to collapse
Yes, nuke everything. That's the only way we can rule out modified/mismatched firmware as a cause.
root66 is stock firmware with root injected into the system image. So wifi calling will still be there. It's just whether or not you want root.
Also wipe data/factory reset. If using stock recovery, this WILL wipe your internal SD. Backup your user apps with TiBu/RTB, and your internal SD card. Do not backup system apps.
You can adjust scanning frequency with build.prop modifications, but I personally use Tasker to control when it's on and off.
ahh. my fault.
ok, we'll get on it tonight and report back when squeaky clean.
Aerowinder said:
Yes, nuke everything. That's the only way we can rule out modified/mismatched firmware as a cause.
root66 is stock firmware with root injected into the system image. So wifi calling will still be there. It's just whether or not you want root.
Also wipe data/factory reset. If using stock recovery, this WILL wipe your internal SD. Backup your user apps with TiBu/RTB, and your internal SD card. Do not backup system apps.
You can adjust scanning frequency with build.prop modifications, but I personally use Tasker to control when it's on and off.
Click to expand...
Click to collapse
please; need a little guidance
Friends, I successfully nuked the GS3, flashed with Root66, got everything working really well but the WIFI issues resurfaced.
Does the GS3 just have a really weak radio?
Compared to even the most humble Galaxy S4G [old and tired], its WIFI performance is not impressive.
Compared to my personal Galaxy Note 1 running more/less stock ICS, its awful ... annoying, unreliable, glitch.
WHY?
My suspicion is that it has trouble switching/credentialing/authenticating from one physical router/AP to another. In our wifi lan setup we have a common AP composed of 2 routers of different chipsets/mftr. Works dandy on ipads, iphones, windows 8, windows 8.1, my Note 1, older/retired/sold androids, etc. The Galaxy S3 is pretty much alone at having trouble when the physical signal of one gets weak and the second one is available - it seems to fumble the ball. Thus, you try to make/receive/talk wifi Call, and get random drops, retries, reload of the WIFI Calling APP.
is there a fix?
Set static channel?
Set static IP [instead of DHCP/select] ?
Grab inSSIDer from the play store, it'll show you if you are on the best wifi channel for your network.
Try turning off some of your other devices wifi connections. May be that the router isn't handling them all at once very well.
Do you have anything that operates on the Wireless-G standard? If so shut it down. Itll only severely degrade the entire networks performance.
You need to be rooted for this, but try the LJC and LJA modems, others too if your up for it.
Does it exhibit the same problems on other wifi networks?
Sent from my SGH-T999 using xda premium
Thank you for helping!
OK - Let me ask a question [it is rooted - root66 per above, busybox, SU, etc]:
I've used InSSIDer before and moved channels here and there and what I noticed is that the way inSSIDer deals with signal data display, whatever channel you pick, it will show one of the other channels as being "better". switch to that channel, and it will show some other channels to be better, etc round and round we go. maybe I'm not using it right...
as to G-only devices I'll give that a shot - I think one of my windows units may be all G. easy fix.
To me it seems clear: the places where the GS3 goes ambiguous and fails to maintain a connection is where the two AP signals [again, one AP,one login, one authentication type, but 2 physical] are pretty evenly matched, per how WIFI Analyzer displays the data. If I shut off the tertiary router, it will just drop signal when you move a tad too far away which is what one would expect, but the GS3's "reach" is the worst of the lot. I'm hoping somebody has figured out how to get hold of that radio and boost the signal.
I don't have a feel for how it does otherwise - we are dependent on WIFI calling at home/office - when out and about its the usual drill... sit in the right spot at the restaurant and you're good.
Those modems you suggest: do they support T-mo WIFI calling APP ?
DocHoliday77 said:
Grab inSSIDer from the play store, it'll show you if you are on the best wifi channel for your network.
Try turning off some of your other devices wifi connections. May be that the router isn't handling them all at once very well.
Do you have anything that operates on the Wireless-G standard? If so shut it down. Itll only severely degrade the entire networks performance.
You need to be rooted for this, but try the LJC and LJA modems, others too if your up for it.
Does it exhibit the same problems on other wifi networks?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
cognus said:
Thank you for helping!
OK - Let me ask a question [it is rooted - root66 per above, busybox, SU, etc]:
I've used InSSIDer before and moved channels here and there and what I noticed is that the way inSSIDer deals with signal data display, whatever channel you pick, it will show one of the other channels as being "better". switch to that channel, and it will show some other channels to be better, etc round and round we go. maybe I'm not using it right...
as to G-only devices I'll give that a shot - I think one of my windows units may be all G. easy fix.
To me it seems clear: the places where the GS3 goes ambiguous and fails to maintain a connection is where the two AP signals [again, one AP,one login, one authentication type, but 2 physical] are pretty evenly matched, per how WIFI Analyzer displays the data. If I shut off the tertiary router, it will just drop signal when you move a tad too far away which is what one would expect, but the GS3's "reach" is the worst of the lot. I'm hoping somebody has figured out how to get hold of that radio and boost the signal.
I don't have a feel for how it does otherwise - we are dependent on WIFI calling at home/office - when out and about its the usual drill... sit in the right spot at the restaurant and you're good.
Those modems you suggest: do they support T-mo WIFI calling APP ?
Click to expand...
Click to collapse
As or inssider, or any similar app, I don't go by what it says is the best channel. I simply look for the channel that has the fewest networks overlapping it. It probably tells you a different one us best each time because its taking into account that there is now another network on the previously recommended channel, yours.
If you have a single G device on an N network, it'll slow the entire network down to wireless-g speeds. So yeah, shut down that machine and ill bet you see improvements across the board. (You may need to reboot the network and other devices)
If you have one router and one AP but both with the same ssid and pw that may be causing your problems. With this type setup there's no way to really be sure which you're connected to. You may connect when close to one, but when you move away from it and closer to the second, it won't connect to the closer/stronger one automatically. Even if you turn it off then on again, it may still connect to the first if the signal is strong enough, even though there may be a stronger one available.
Try having it connect to the ap using different credentials and then you should have greater control over which you're using at a given time.
Allthe modems should function properly with everything they are supposed to, so yes they'll all work for wifi calling. I was looking into a way to adjust the Tx power for wifi a long time ago. Ill see if I can find what I was doing and try again. If you use a 3rd party router firmware (dd-wrt or tomato), you can adjust Tx power on the router itself if I remember correctly.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
If you have a single G device on an N network, it'll slow the entire network down to wireless-g speeds. So yeah, shut down that machine and ill bet you see improvements across the board. (You may need to reboot the network and other devices)
If you have one router and one AP but both with the same ssid and pw that may be causing your problems. With this type setup there's no way to really be sure which you're connected to. You may connect when close to one, but when you move away from it and closer to the second, it won't connect to the closer/stronger one automatically. Even if you turn it off then on again, it may still connect to the first if the signal is strong enough, even though there may be a stronger one available.
Click to expand...
Click to collapse
in reverse order:
- as to to the wifi device power/range I was speaking of the phone/handset, not the router. But since you mentioned: I have not found an N or beyond router that has GOOD open source; open-wrt, dd-wrt, tomato et al - if you really read carefully what the feedback is, a lot of them suffer bad speed degradation. the old wrt54gl's would run full-tilt G speeds, over a wide range, and last for many years, but I have not found the equivalent in any other device running or capable of running one of the good [or formerly good] open-source codebase
- Are you sure about that client-bridging common-ssid/pw/encryption? the whole point of such firmware is to make the transition seamless and it is for every device except the GS3: two ipad's, one Galaxy S4G [999v], one Galaxy note T879 [debloated stock ics], two HP workstations, three laptops - gateway, thinkpad, hp Envy - not one of those devices gags when switching router signals. only the GS3. with the other devices, you literally forget that you've got multiple routers
The GS3 code has multiple network notifications also that the other two Galaxy's do not: it interrupts your blasted work to INFORM you that you're signal is dropping [how dumb is that?] - then it informs you that you've been disconnected, and informs you that you're "not registered on the network", then it informs you that it is logging in again, then it informs you that WIFI Calling App is ready for use as though it was the first time you used it.
- I will give the modems a whirl. I'll stash a full nandroid and try them out - If any of you happen to have a link to the 'how to' steps pls pass on as it will save me a lot of careful reading.
oh, and I was wrong about G-device; i replaced that one with an N device. Frankly, G speed is way fast enough. my internet connection is only 20Mbps so if I had the old WRT rigs back and up/running it would be PLENTY fast. Mixing B with G... now that was a real problem - there you were talking about effectively 1 to 5 Mbps
cognus said:
in reverse order:
- as to to the wifi device power/range I was speaking of the phone/handset, not the router. But since you mentioned: I have not found an N or beyond router that has GOOD open source; open-wrt, dd-wrt, tomato et al - if you really read carefully what the feedback is, a lot of them suffer bad speed degradation. the old wrt54gl's would run full-tilt G speeds, over a wide range, and last for many years, but I have not found the equivalent in any other device running or capable of running one of the good [or formerly good] open-source codebase
- Are you sure about that client-bridging common-ssid/pw/encryption? the whole point of such firmware is to make the transition seamless and it is for every device except the GS3: two ipad's, one Galaxy S4G [999v], one Galaxy note T879 [debloated stock ics], two HP workstations, three laptops - gateway, thinkpad, hp Envy - not one of those devices gags when switching router signals. only the GS3. with the other devices, you literally forget that you've got multiple routers
The GS3 code has multiple network notifications also that the other two Galaxy's do not: it interrupts your blasted work to INFORM you that you're signal is dropping [how dumb is that?] - then it informs you that you've been disconnected, and informs you that you're "not registered on the network", then it informs you that it is logging in again, then it informs you that WIFI Calling App is ready for use as though it was the first time you used it.
- I will give the modems a whirl. I'll stash a full nandroid and try them out - If any of you happen to have a link to the 'how to' steps pls pass on as it will save me a lot of careful reading.
oh, and I was wrong about G-device; i replaced that one with an N device. Frankly, G speed is way fast enough. my internet connection is only 20Mbps so if I had the old WRT rigs back and up/running it would be PLENTY fast. Mixing B with G... now that was a real problem - there you were talking about effectively 1 to 5 Mbps
Click to expand...
Click to collapse
I havent used any 3rd party firmwares for my networks in a long time. I was assuming that for the Wireless-N routers, they would have come a long way and solved a lot of their issues by now. My mistake.
I am sure about the router/ap setup. (Is your second set up as an Access Point or Repeater? Either way the same issues can still present themselves) I refer you to the following website for information on this and a little bit to back up my claim. It may be worded better or easier to understand than me, but either way its good info.
http://www.smallnetbuilder.com/wire...w-to-add-an-access-point-to-a-wireless-router
Step 3 is where this is touched on.
I have to be honest that I am skeptical that your other devices are transitioning over to the AP. (im guessing they are ALWAYS connecting to the AP) Unless their radios are actually much weaker than the GS3's. In fact, what I suspect at this point is that your GS3 is trying to connect directly to your router all the time, while your other devices are connecting to one or the other, all of the time. This is one of the draw backs to using the same SSID, it is difficult to tell which you are actually connecting to.
Read over that linked page. Let me know what you think.
Will do. thanks for that.
if your theory is right, on any one of the frequent auto-disconnect cycles, you're saying that the GS3 will connect to which? the stronger one? any idea how the firmware is setup to pick a winner?
Also, webbing around for answers [there are a LOT of threads on this issue as it turns out], there's a good deal of discussion about 5ghz vs 2.4ghz bands, and that samsung/t-mo have changed how the firmware handles transitions [or connect/disconnect] to one or the other. i.e. https://support.t-mobile.com/thread/37707?start=0&tstart=0
I can set my routers to one or the other if that would help - Any ideas if one is preferable?
Ever heard of GS3 being "channel sensitive"? I have not. Early WIFI/WIFI-Calling capable models from several mftrs were quite channel-nitpicky.
I could easily check that transition [seamless dropping of one, connecting to another] if there was a way to verify the MAC of the connected ap. know of such? I can't find much in the way of advanced settings but I have not a guide to the keyboard/manual settings methods for this build 4.1.2.
read the article but see no discussion of your point.
pick the right link?
the setup I'm using is simple wireless bridging - no physical medium between the twain. subordinate router has the mac address, encryption type, ssid, credentials and channel setting of the boss. reboot and done.
pretty much the same type of bridging as with DD-WRT [though it has a lot more options... more confusing]
I really think that the GS3 modems aren't that good, especially when it comes to wifi calling. My family and I haven been having some bad signal problems as of late so we've been relying on wifi calling to make calls. I had a lot of dropped calls in the past but I knew that had a lot to do with the old modem/router setup I was using. I would lose internet connection not matter what I was on. The internet would just drop and then reconnect, very frustrating if you were on a call or playing Xbox live. so last week I hooked up a new Comcast modem with wifi. The drops stopped but I still have to literally be standing right next to the modem if I wanted to make sure I didn't lose a call. If I walked into the kitchen, which is 15ft away, I'd get the little beep that warns that I'm about to lose the wifi signal. I know my signal that's coming from the router is good because all my devices, including the phone says so. Hell, the kids across the street asked if they could have the password because their internet was shut off and my signal is strong over there.
I don't have anything technical to support what I say, just experience but that experience tells me that Tmobile's wifi calling doesn't work that well unless your within 3 ft of the router.
cognus said:
Will do. thanks for that.
if your theory is right, on any one of the frequent auto-disconnect cycles, you're saying that the GS3 will connect to which? the stronger one? any idea how the firmware is setup to pick a winner?
Also, webbing around for answers [there are a LOT of threads on this issue as it turns out], there's a good deal of discussion about 5ghz vs 2.4ghz bands, and that samsung/t-mo have changed how the firmware handles transitions [or connect/disconnect] to one or the other. i.e. https://support.t-mobile.com/thread/37707?start=0&tstart=0
I can set my routers to one or the other if that would help - Any ideas if one is preferable?
Ever heard of GS3 being "channel sensitive"? I have not. Early WIFI/WIFI-Calling capable models from several mftrs were quite channel-nitpicky.
I could easily check that transition [seamless dropping of one, connecting to another] if there was a way to verify the MAC of the connected ap. know of such? I can't find much in the way of advanced settings but I have not a guide to the keyboard/manual settings methods for this build 4.1.2.
Click to expand...
Click to collapse
Accorfong to my research it'll try to always connect to the first one it connected to. Even if the signal is stronger on another. That's the main point I was linking to that article for.
As for which band to choose, 2.4 is usually best. 5.0 is faster, but with a shorter range and more susceptible to interference.
tmob removed the option as you can manually select which you prefer. There is an apl I include with all my roms though that'll give this option back. Let me know if you want the link, though I doubt it'll help ypur particular problem.
cognus said:
read the article but see no discussion of your point.
pick the right link?
the setup I'm using is simple wireless bridging - no physical medium between the twain. subordinate router has the mac address, encryption type, ssid, credentials and channel setting of the boss. reboot and done.
pretty much the same type of bridging as with DD-WRT [though it has a lot more options... more confusing]
Click to expand...
Click to collapse
Ok, so its more of a repeater setup. The routers are not connected to each other via Ethernet or powerline?
Step 3 of that article is what I wanted you to read. Its on the 2nd page. (Though I do suggest reading the whole of both pages)
nataku199 said:
I really think that the GS3 modems aren't that good, especially when it comes to wifi calling. My family and I haven been having some bad signal problems as of late so we've been relying on wifi calling to make calls. I had a lot of dropped calls in the past but I knew that had a lot to do with the old modem/router setup I was using. I would lose internet connection not matter what I was on. The internet would just drop and then reconnect, very frustrating if you were on a call or playing Xbox live. so last week I hooked up a new Comcast modem with wifi. The drops stopped but I still have to literally be standing right next to the modem if I wanted to make sure I didn't lose a call. If I walked into the kitchen, which is 15ft away, I'd get the little beep that warns that I'm about to lose the wifi signal. I know my signal that's coming from the router is good because all my devices, including the phone says so. Hell, the kids across the street asked if they could have the password because their internet was shut off and my signal is strong over there.
I don't have anything technical to support what I say, just experience but that experience tells me that Tmobile's wifi calling doesn't work that well unless your within 3 ft of the router.
Click to expand...
Click to collapse
Make sure you don't have a bottleneck somewhere on your network. (Such as a misconfigured router, a docsis 1.0 cable modem, etc.) Or as I stated before, if you have a wireless g device active on your network, it'll force the whole network to degrade to wireless g speeds. Also use inssider to check if you are on the best channel. And check for any points of interference. (Microwaves, cordless phones, power hungry appliances, etc)
If your cell signal went south recently, it may be due to the work tmobile has been doing. What worked best before, may not anymore. Try out the many other available modems to see if it improves.
Sent from my SGH-T999 using xda premium
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
Thos is a copy/paste of the text I was referring to.
(Starting under step 3)
But most wireless clients are very "sticky" and tend to stay associated to the first AP they encounter,*even when APs with stronger signals are available. So I recommend setting a*different SSID*for the AP, so that you can manually control connection.The other advantage of setting a different SSID for the AP is that you'll be able to see both the AP and your main wireless router if you're using the Wireless Zero Configuration utility that is built into Windows. Even in Vista, Microsoft has stubbornly chosen to not show multiple wireless networks that use the same Network Name / SSID.
4) Set the AP channel
One large network practice that you*do*want to follow is to set the AP to a different channel than the main wireless router. In the U.S. you should use only the non-overlapping channels*1, 6 and 11. So if your main wireless router is set to channel 6, set the AP to either 1 or 11.You should probably do a quick site-survey first (see this HowTo), to make sure that you aren't setting the AP channel to one used by a neighbor's network. If you can't find a completely clear channel, choose the*weakest*neighboring network and set the AP to its channel.
Sent from my SGH-T999 using xda premium
I'll look into it.
Thanx
Since I've updated to Android 4.3 on my Galaxy Nexus (Maguro), I've noticed an issue with the WiFi. Sometimes, when entering the range of a known WiFi network, my device doesn't automatically connect, as if it doesn't know I'm in range or hasn't scanned for the WiFi networks nearby. This issue has been reported on the official Google Bugs tracker here. -->
https://code.google.com/p/android/issues/detail?id=58230
If you have this issue, please visit this link and star/report it so that Google will know. For now, I've found a few ways to resolve the problem, and wanted to share them.
Solution 1: When I go into Settings < Wi-Fi to view the WiFi networks, I notice that at first it shows the network I'm trying to connect to as "Not in range," but then it immediately connects to it.
Solution 2: I also found that turning WiFi off completely, and then back on again allows my device to see the network and connect.
Both solution 1 and 2 are manual fixes. While both are easy to do, they require you to actually take action to reconnect to your network. This can cause you to miss notifications, etc. if you aren't aware of what's going on. I didn't like that too much, so I made a simple Tasker profile to help.
Solution 3: This requires a little bit of knowledge about Tasker, but I'll try to explain it well enough that anyone can get the profile setup and working.
First we will create a Task called "Wifi fix." This task will have 2 simple actions.
Disconnect Wifi
Reconnect Wifi
Now we need to create a profile to trigger the task. I'll name it "Wifi Fix Profile."
This is going to have 3 context triggers that all have to be met before it will execute our Wifi fix task, all are state contexts.
First we will use Wifi State Connected, with the Invert Checkbox checked
Then, Variable value "%WIFI" matches "on". Both "%WIFI" and "on" are case sensitive, so be careful.
Lastly, Display State "ON". This one is optional. I added it because I don't want wifi constantly disconnecting/reconnecting while my phone is asleep if I'm not near a network. So instead, the profile can only trigger while I'm actually using the phone.
After that, all you need to do is go into Profile Settings (by long pressing the profile name) and set a cooldown. I use 5 minutes, you can use anything (or nothing) you want.
Basically, what this profile does is when your wifi is on but not connected to a network, then it forces a scan for wireless networks by disconnecting, then reconnecting wifi. Simple, and it works.
Theory:
Now that we have a workaround, back to the problem. Based on the solutions listed, namely solution number 1, I believe that the problem lies with how often/ when WiFi networks are scanned for. This could be due to the new WiFi Setting Google added in 4.3, "Scanning always available". It has been reported that disabling this does not fix the issue, but I haven't tried it myself. I also tried changing the wifi scan interval in build.prop, but that didn't seem to make a difference.
Hope this helps some of you!
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Sent from my Nexus 7 using xda app-developers app
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
geckocavemen said:
I had problems with Wi-Fi on 4.2 so I just got in the habit of expecting Wi-Fi to be a little wonky and haven't paid much attention to it on 4.3. Have you noticed the same issue on custom roms as well? I'm running slim bean is why I ask.
Click to expand...
Click to collapse
Yes, I do have the issue on both custom and the stock factory image. I am also currently on Slim Bean Beta 1 (it's my favorite), but I also had the issue on Cataclysm.
NCguy said:
Can someone please verify for me, so I know its not just me, that network speed tests using speedtest.net are erratic and performance is horrible when bluetooth is on and connected. My theory is also that it continually gets worse over time to the point that your wifi begins to actually stutter and stall.
Click to expand...
Click to collapse
I would test this for you, but I don't have a bluetooth device to connect to. Sorry, maybe someone else can test this?
http://forum.xda-developers.com/showthread.php?t=2380403
Sendt fra min Nexus 7 med Tapatalk2
What I really wanto to know if this issue is posted in the official google bugs tracker
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
stevensoaj said:
Well, I haven't done it because I don't know how, but I would be glad to if someone could point me in the right direction.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Expose your case here:
https://code.google.com/p/android/issues/list
Then come here and recruite some people to star your posted issue, the more stars the more atention Google puts on the issue. If you do it, add 1 star from me for sure.
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Big ZD said:
Can it truly be verified as a bug if it's not stock 4.3? Not trolling...just asking.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
FlickFlack said:
I think so. Have a look at the link I posted. There are different ROMs and devices used. Mostly stock ROMs.
Click to expand...
Click to collapse
I stand corrected. My apologies for not reading more thoroughly.
Sent from my Galaxy Nexus using xda app-developers app
FlickFlack said:
I also have this problem with my GNex running CM10.2 nightly 0708. It is a real shame that google introduces a new bug in 4.3.
Android 4.2 suffers from a similar bug and they never fixed it and promised to fix this in 4.3 and now we encounter a new one :crying:
The 4.3 problem is already tracked here https://code.google.com/p/android/issues/detail?id=58230 I think.
Will test your tasker profile and report if it works. From your description it sounds like a good workaround for this bug.
Click to expand...
Click to collapse
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
I promised to give feedback for testing the tasker profile. After 3 days I am sure that the tasker profile described in OP is working fine.
For me it is a good workaround. But I am still hoping that google will fix the problem, because for normal users this must be a real annoying bug.
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
memnoc said:
I'm not experiencing any dropping issue..I'm curious about one thing anyway, all of the guys are experiencing dropping issues are actually running latest bootloader and latest radio? did you change RIL? latest means from 4.3 jrr update, and RIL well, you tell me..
Click to expand...
Click to collapse
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
stevensoaj said:
OP edited with link to Official Google Bug tracker, thanks for finding this!
I also changed up the tasker profile to disable wifi and then enable it again instead of just disconnecting and reconnecting. Seems to work better.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Scratch that. A little more testing and I'm back to the initial, disconnect then reconnect wifi net. What do you guys think?
stevensoaj said:
It's not a "dropping" issue, but rather a reconnecting issue. When entering range of a known, configured WiFi network, our devices don't connect to the network automatically.
As far as being on the latest, bootloader, radio, and RIL, yes, I am. I flashed the factory image way before flashing any 4.3 custom firmware, and I had the issue there, as well as on the custom firmware.
Click to expand...
Click to collapse
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
memnoc said:
Well, I believe we have a radio/ril issue here.. I saw this happening multiple times during years.. Update to new fw, new radio, new ril, poor/problematic connection...sure the problem here is a bit weird but, is well known that a certain radio module doesn't work in the same way in every part of the planet, same goes for its interface libraries..I honestly don't know why you and many others flash a factory image when a new Fw pops up..if it's a matter of having the latest stuff, OK, but if someone claims it is mandatory then it's absolutely pointless and 100% wrong..the hour before 4.3 appeared on Goole platform I extracted the system image and booted a working ROM.. That's it..I will never ever flash a factory image unless it is a matter of sending my device to the manufacturer for repairing...so I currently have old radio, old ril, old bootloader, new 4.3 roms, and I don't have the issue...of course it is just a theory, and could be 100% unrelated but it is worth trying another radio, possibly with its ril but this last thing doesn't really matter on a nexus device...bootloader afaik it is not related with radio module so i wouldn't change it but the point is that the radio gives different performance according to the zone where it is used..edit: I just flashed latest radio, all is fine..this could be both a proof of my theory is wrong or right...I would try If I were you.
Inviato dal mio Galaxy Nexus usando Tapatalk 4
Click to expand...
Click to collapse
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
stevensoaj said:
I'm going to try a different radio now because I'm curious, but I wasn't aware that the radio had ANYTHING to do with wifi. I thought the radio was only the mobile radio. Was I mistaken?
Click to expand...
Click to collapse
yes, you was, my friend; radio has everything to do with gsm/umts, wifi/bluetooth connections...it is exactly what a radio module does in the phone, to be precise, radio.img is that piece of software that virtually connect the radio chipset hardware with the basic software..the RIL (radio interface layer) instead, is what connect the software previously mentioned with the actual OS (the rom), but I read somewhere it is not so important in aosp roms, while it very important in other OS, propietary ones, like HTC (that has a specific RIL different from the asop one)...
You probably know it as "baseband", which is how google used to define it..in samsung environment is a.k.a as "modem" , whatever you call it, we are talking about the same thing, I keep calling it "radio" because of the old froyo times we learned to call this way, since changing the baseband it's just changing the radio.img..now, be very careful, flashing this kind of stuff may brick your device IF something goes wrong in the flashing process..however, I flashed tons of radios, and I've never experienced any hard brick..here on maguro we have the opportunity to fash it from recovery which is what I suggest you to do, so you'll avoid any issue whatsoever, and remeber, it may not be related to your problem but, as I stated before, radio module controls all the wireless signals, included network/provider frequencies, their range, and their geo-location, as well as bluetooth, and anything communicate wirelessly into your phone, it's worth to give it a shot in my opinion..here some extra info for you:
RIL info
http://www.netmite.com/android/mydroid/development/pdk/docs/telephony.html
radio module info
http://android.stackexchange.com/questions/70/what-is-radio-firmware
http://forum.xda-developers.com/showthread.php?t=1462360
http://forum.xda-developers.com/showthread.php?t=1930844