I have had my new Galaxy Note 3 for about 3 weeks now, and have had an issue with certain apps not connecting to the internet over wifi. All of the google apps (youtube, play store, hangouts, gmail, etc) are not able to connect to the internet over any wifi hotspot, or if they do, they're painfully slow.
I have changed MTU settings on my home router, DNS settings, wifi auto switch is off on the phone.
Here's the kicker. If I enable airplane mode first, then turn wifi on, everything works great. I suspect this to somehow be related to the SIM card? Really should have nothing to do with wifi, but who knows...
I should add that I've owned a couple other android phones that have had this issue, but it seemed to have just "worked itself out" after a day or so. (Droid 4, Stratosphere II)
Have you tried a 30/30/30 hard reset on the router yet?
Does a laptop connected via Wi-Fi also have similar issues?
Sent from my SM-N900V using XDA Premium 4 mobile app
I have hard reset and factory reset the router a few times, even went so far as to buy a brand new router and use it. No difference.
I get 26/8 speeds on two different laptops, and one desktop, all with ping times down to about 18ms (as shown on speedtest.net)
spoke with a helpful rep at verizon today, who supposedly called samsung regarding this fix while I was on hold. My replacement should be here tomorrow. This issue is exactly the same as when older android phones would not connect to google (signal indicators would be white instead of blue). It seems like something to do with ssl traffic.
Anyhow, will post back after i've played with the replacement for a bit.
syntheticexctasy said:
I have hard reset and factory reset the router a few times, even went so far as to buy a brand new router and use it. No difference.
I get 26/8 speeds on two different laptops, and one desktop, all with ping times down to about 18ms (as shown on speedtest.net)
Click to expand...
Click to collapse
syntheticexctasy said:
spoke with a helpful rep at verizon today, who supposedly called samsung regarding this fix while I was on hold. My replacement should be here tomorrow. This issue is exactly the same as when older android phones would not connect to google (signal indicators would be white instead of blue). It seems like something to do with ssl traffic.
Anyhow, will post back after i've played with the replacement for a bit.
Click to expand...
Click to collapse
The next most common thing that it would be is the channel that your router is set to. You want to use a frequency that has little interference and there is an app called WiFi Analyzer to help figure it out for your surroundings.
The reason that the laptops might work ok is because the channel can be set within Windows and are most likely set to a different random number between 1-11 than your phone is.
I have found open channels and used those, which made no difference. I believe this may be a google issue as evidenced here (granted these guys are talking about the nexus 5, the issue is very much the same)
https://productforums.google.com/forum/#!topic/nexus/SN03aclu7B8[1-25-false]
I received my replacement today, no dice. I also bought a new router today, no dice. I've tried every channel 1-12, no dice.
The only thing that works is to enable airplane mode, then turn wifi on. I then see full speeds on play store, youtube, gmail, and hangouts. Interestingly enough, the facebook app is affected by this, as well as all push notifications.
It should be noted that the replacement note 3 exhibits the exact same behavior. This leads me to believe there is a modem issue causing the phone to switch back and forth between LTE and wifi, or something along those lines (if the cell radio is off, wifi works great)
syntheticexctasy said:
I received my replacement today, no dice. I also bought a new router today, no dice. I've tried every channel 1-12, no dice.
Click to expand...
Click to collapse
syntheticexctasy said:
The only thing that works is to enable airplane mode, then turn wifi on. I then see full speeds on play store, youtube, gmail, and hangouts. Interestingly enough, the facebook app is affected by this, as well as all push notifications.
It should be noted that the replacement note 3 exhibits the exact same behavior. This leads me to believe there is a modem issue causing the phone to switch back and forth between LTE and wifi, or something along those lines (if the cell radio is off, wifi works great)
Click to expand...
Click to collapse
That is truly odd. I suppose it could be believable that an ISP throttled traffic to specific blocks (net neutrality anyone?), but I don't know why that would cause an interface change on the handset.
There are some apps which are network interface aware - e.g. as an example carriers will use split DNS and inbound IP firewalling so only people on their own network can resolve the IPs of MMS (APN) servers or *send* data to them. That prevents them from being DDOS'ed and I suppose other attacks from anything but their own network - which they have well instrumented. But that means that the MMS apps can not use whatever IP interface happens to be up - either for DNS service or for IP routing - so they need to be able to bring up a specific IP interface, use DNS that is bound through that interface, and route through that interface as well.
I was going through the apps on my phone the other night with a package browser (Package Explorer (Ribo), btw) and I was stunned at how many apps have "CHANGE_NETWORK_STATE" privileges.
What I'm wondering is if you have an app installed that has gone nuts and is toggling on/off your cell I/F. Something like that would be consistent with your observations.
Is there anything relevant happening in your device logcat when this is going on?
.
bftb0 said:
That is truly odd. I suppose it could be believable that an ISP throttled traffic to specific blocks (net neutrality anyone?), but I don't know why that would cause an interface change on the handset.
There are some apps which are network interface aware - e.g. as an example carriers will use split DNS and inbound IP firewalling so only people on their own network can resolve the IPs of MMS (APN) servers or *send* data to them. That prevents them from being DDOS'ed and I suppose other attacks from anything but their own network - which they have well instrumented. But that means that the MMS apps can not use whatever IP interface happens to be up - either for DNS service or for IP routing - so they need to be able to bring up a specific IP interface, use DNS that is bound through that interface, and route through that interface as well.
I was going through the apps on my phone the other night with a package browser (Package Explorer (Ribo), btw) and I was stunned at how many apps have "CHANGE_NETWORK_STATE" privileges.
What I'm wondering is if you have an app installed that has gone nuts and is toggling on/off your cell I/F. Something like that would be consistent with your observations.
Is there anything relevant happening in your device logcat when this is going on?
.
Click to expand...
Click to collapse
There are no apps installed other than the stock verizon/samsung apps. I have reset to factory in preparation for sending this unit back to vz, however it appears i'll be keeping it since the replacement didn't work any better.
Nothing interesting from logcat. Just a lot of IRListener messages, and DalvikVM occasionally clearing ram.
I can see why you would be pulling your hair out.
And the fact that you observe the same behavior with two different units (completely different hardware) and two different routers means one of two things:
- the problem is the handset/software
- the problem is not the handset/software.
Not trying to be funny there. What I mean by the above is that for you to pull two devices out of Samsung's production line at random (unless you happened to get two devices from a single batch of defective units), then the problem couldn't possibly be a low-probability defect thing: either it happens on a very large fraction of all N3 handsets, or the problem actually has nothing to do with the handset at all.
e.g. suppose Sammy shipped handsets where 1 out of 100 had the problem you observe. For you to end up with two of them in a row, the odds of that happening would be 1 in 10,000. If affected half of all handsets, then your odds would be more reasonable - 1 out of 4.
But it sure seems like if it affected half of all owners... or even 10% of all owners, people would be piling in in droves to complain.
I haven't noticed it on my N3, but I have other devices so I'm not sure how much I have used it for e.g. Youtube streaming. I do leave both WiFi and the cell on, and haven't noticed what is happening to you, but I am on MJ7 instead of MJE, and my WiFi is older (802.11g), so maybe if it is a bug it that wouldn't even show up with my setup even if it were the N3's fault.
(BTW, that offers a suggestion - because the N3 is so new it has 802.11ac capabilities - and I suppose your new router does too - if you turn off some capabilities, does the problem disappear? For instance turn off 802.11ac or 802.11n or 5Ghz band usage on the router, does that change anything?)
The other alternatives? Some kind of burst RF noise in your local environment? You earlier said
are not able to connect to the internet over any wifi hotspot, or if they do, they're painfully slow.
Click to expand...
Click to collapse
were the "any wifi hotspot" APs that were all relatively close to a single location, or were they widely dispersed (miles apart)? If they were miles apart, then the problem isn't ISM-band interference. Even if it were, interference from non 802.11 devices (bluetooth devices, baby monitors, microwaves, some wireless cameras, etc) isn't going to show up using a scanning app. Relatively sophisticated equipment would be needed to make that determination. Or a search and destroy mission.
I will say that I had a similar problem a few weeks back (using completely different gear) - I was tethering to a different Android phone (USB tether), and Web browsing on the client device (N7 tab) was fine except the Google Play store app - data would only come dribbling out of it. I couldn't even complete a single app listing, much less begin an app download. At the time I just chalked it up to a temporary problem with Google's Play store. But now it makes me wonder if it isn't something more subtle - as you noted, Google servers seem to be a commonality you are observing. Maybe some ridiculous bug involving Google's single credential efforts?
Well, now I'm rambling and I really haven't given you a suggestion. Maybe something I said will jog you in a different direction and you'll figure it out. If it really is something generic to the current Note 3, it seems like Google would want to know about it. I wonder if it is even possible to get telephone support from Google - they don't really have a reputation as being a consumer-oriented business.
good luck
.
Thank you for all of your help. I am sort of an amateur RF "enthusiast" myself. This happens in more than one location, literally every wifi location i've connected to.
I do believe on past handsets a new sim card sorted this out for some reason, however the vz rep that I spoke with activated a new one that I had gotten with the note 3, but not activated at the time, since my droid 4's sim card was "current enough".
I am lead to believe that this is a modem firmware issue, due to the fact that when the cell radio is off (doesn't matter if mobile data is on or off) the wifi works great. I am running MJE, and would be willing to try and downgrade to the previous radio to see if it makes a difference, but I don't know if that's even possible without causing some damage.
edit: I just realized that the replacement phone is running MJ7...so not sure it would matter.
Resolved
Ok guys, I figured this out, sort of.
I went into an angry router swapping/resetting frenzy when I figured out that the replacement acted the same.
My original setup consisted of: (I have a lot of wired devices in my house)
Comcast Gateway (set up as a normal cable modem, wifi/firewall/dhcp disabled) ----> Linksys WRT54G w/ DD-WRT (wifi off, using for firewall/routing) -----> Zonet N router (no dhcp, using as a switch, wifi off) --------> Linksys BEFW11S4 (used as a switch) ------> Netgear WNR1000V2 (used as a switch and second wifi access point occasionally)
During this frenzy, I eliminated the Zonet unit, and the BEFW11s4. My network now looks like this:
Comcast Gateway ----> Netgear WNR1000V2 (router/firewall/dhcp/wifi access point) -----> WRT54G (as a switch)
This seems to have solved my problem. I noticed while troubleshooting that if I disconnected the segment between the Zonet and the BEFW11S4, my phone would work perfectly fine. I believe that taking the BEFW11S4 out of the picture solved my problem, even though my data was not riding on that segment of the network.
Still, I am perplexed as to why the airplane mode trick fixed the issue.
LOL. I have a pile of Cisco routers if you want to buy them - and I'll throw in some token ring gear and another BEFW11S4 for free.
But seriously - you did the right thing by (experimentally) simplifying; the more complex an environment is, the more opportunities there are for bug expression.
Glad everything worked out - and I await your PM inquiring about my Cisco pile
I never wanted to upgrade from my WRT54G V1! What an awesome, rock solid router! However, need faster wireless speeds nowadays.
I was trying to keep that as my firewall, since the dd-wrt firewall is so much more robust than that of the netgear, also the netgear does not support nat loopback (something I really would like to have)
[Q] Does the Nexus Player support "login" WiFi networks (such as those at a hotel(?
One of the biggest disappointments I had with Chromecast was that it was impossible to set the unit up in a hotel. Since many hotels have WiFi that require you to log in, you couldn't set up your Chromecast on these networks.
Is this the case with the Nexus Player?
Not really sure, but I have a trick you can try with your Chromecast. Not sure if it will work, but we used to do it back when I was in college because the University network required a username/password login (which sucked if you wanted your XBOX on the network).
Figure out the MAC address of your Chromecast. Go to your laptop or PC, and spoof the mac address of your NIC (or wifi) to match the chromecast. You can usually do this through the device manager in Windows by going to the Properties for your NIC. After that, use your brower to sign in. Go back to Chromecast and see if it worked.
Usually they tie the authentication to your NIC's MAC address...so the theory is that as long as you authenticate the mac address somehow, then any device with that mac address will work. Things might have changed over the past 6 or 7 years though when we used to do that.
IBNobody said:
One of the biggest disappointments I had with Chromecast was that it was impossible to set the unit up in a hotel. Since many hotels have WiFi that require you to log in, you couldn't set up your Chromecast on these networks.
Is this the case with the Nexus Player?
Click to expand...
Click to collapse
Another option if you are a frequent traveler is a portable travel router like the D-Link DIR-510L. This tiny router easily fits in your briefcase yet can turn any wifi network into your own personal wifi hotspot. Basically it connects to a hotel wifi and through your phone, tablet or pc you can log in with your hotel credentials. It then creates a separate wifi network for your own use, one that you control for all your devices (including your chromecast) without having to pay the hotel more for multiple device connections, etc. It even has a built in battery to either run without power or to charge your devices and, with its 3 usb ports, can share a USB drive full of media with all your wireless devices. I know I sound like a commercial here, but I simply couldn't live without this tiny little beauty on the road.
Hi folks,
I have two Nexus players at home. When I first got the initial one, I had it setup on my 2.4G network (network connectivity was very strong so it did not matter). Recently, I upgraded my router that supports 802.11AC (2400mbps). Since the router was further out and since AC provides a better streaming experience, I added the 5G network as well. It turned out that it was still connecting to my 2.4G network (based purely on signal strength, I assume, which is absurd). So I had it "forget" the 2.4G connection. The next day, I had my replacement for the Nexus player (had a issue with the remote but they sent me the whole thing anyway) and bought a second Nexus player. I logged in with the same account that I had used and surprisingly both of them were logging onto my 2.4G network without even asking. It left me puzzled. I tried "forgetting" the network and it did not work. I tried intentionally giving a "bad" password and that did not work either (i.e. the second option at least kind of worked for one full day where it did not connect to the 2.4G connection). I have since done a factory reset with two options. A) re-login with the same account and B) login with a different account. Not too surprisingly, option (A) allows me to "connect" to the 2.4G connection whereas (B) does not.
I have since tried to figure out where this password is saved and I cannot seem to find it. The only logical way for me to NOT connect is to turn off the 2.4G connection (which is not possible because some of my devices still do not support 5G) or rename the connection (logistical issue but can be done). My concern is "WHERE IS MY PASSWORD SAVED AND WHY AM I NOT ABLE TO DELETE IT AS I WOULD ON ANOTHER DEVICE"
I called Nexus support (they are practically useless unless you are requesting a replacement) and I got the following (no I am not kidding, these were literally the things that they told me):
1. "The Nexus player has no GUI". I refuted this claim and explained that the device was fully self-sustained in that it did not require a phone to be its alibi and that a network can be "forgotten"
2. "The Nexus player has no firmware". I again respectfully refuted this claim as well but it was getting a little hilarious because I really thought she said "no GUI" to imply something else. To this, the rep said (and in a very authoritative tone), GIVE ME THE ADDRESS OF THE FIRMWARE. I explained that all firmware does not have to have an IP address (I work at a company that makes hardware and specifically work on the DSP which has no direct access or IP address except via a host processor). I then asked "Can you do a software update on the device" and she responded "I don't know" and then went on to say the following
3. "THE NEXUS PLAYER HAS NO OS!". SHE LITERALLY SAID THAT.
At no point in time was she did even accept that the password was saved "somewhere" in the cloud and was attached to my google account that I had no access to which I believe is very creepy (because now I do not know what other information is "stored"). Then she said "let me send you to speak to the manufacturer because we have nothing to do with this device" or something to that effect!
I am curious if anyone of you can try this out and tell me if the player continues to connect to a network that you ask to be forgotten. I am curious also what you think about the issue.
Saving WiFi passwords to your Google account is a standard feature of Google's Backup & Restore, if you have this enabled. The option to disable this doesn't seem to be exposed by the Android TV UI, though.
And that support conversation was hilarious
ghtop said:
Saving WiFi passwords to your Google account is a standard feature of Google's Backup & Restore, if you have this enabled. The option to disable this doesn't seem to be exposed by the Android TV UI, though.
And that support conversation was hilarious
Click to expand...
Click to collapse
That is precisely my point as well. When information that pertains to me is stored, I need to have the option (within reason) of being able to delete it. When such an option is being provided on their Android devices, they only have 2 options on the Nexus player. Save it on the device and a factory reset removes it OR allow the option to delete such info. Not doing either seems like a violation IMO.
I've been looking for a way to solve this exact problem.
I have a 5ghz SSID and a 2.4ghz SSID and I want my nexus player to ALWAYS use the 5ghz, but because I have the same Google account synced to all my Android devices I can never "forget" the 2.4ghz SSID on my nexus player, it always gets restored. To make matters worse, the nexus player prefers the 2.4ghz connection because the signal tends to be stronger.
The only solution I've seen is to dump and disable android backup on every android device I own (2x Nexus Player, 2x Tablets, 3 Phones) to prevent it from syncing both network connections, but it doesn't appear to be possible to JUST remove wifi networks from being synced.
Intersting to read that. Do you at least have a reliable connection when using the 5GHz? (meaning a stable connection over a full week, without connection drops?)
By the way: If *anybody* could shed some light on whether the Marshmallow preview finally enables us to use DFS channels on the Nexus Player, then this would be great. I cannot really flash the preview as it would wipe the player and I'd need hours to set up all my apps again from scratch... and since I know that some people have been testing this, I prefer to ask. Apparently got new neighbors last week who are now polluting the lower 5GHz band which used to be perfectly free... so I wanna switch to the DFS channel frequencies, however the Nexus Player can only connect to the lowest four 5GHz currently, which are the non-DFS ones (all my laptops and even a friend's Samsung tablet from 2013 support the 5GHz DFS channels though)
The Marshmallow changelog contains the following commit: https://android.googlesource.com/platform/frameworks/opt/net/wifi/+/dfc7d48
Has anyone been able to check if this has any effect on the Nexus Player with the latest firmware?
Edit: besides this there's also: https://android.googlesource.com/platform/frameworks/opt/net/wifi/+/6f59b02
For the two people caring: The Nexus Player supports DFS channels and can successfully connect to those after the Marshmallow update.
Mine got the update without me noticing it at all and when I realized it had received the update, I wanted to check the wi-fi and saw it was already connected to my 5GHz wi-fi (which is on one of the upper DFS channels).
Hi guys,
I have recently bought a Shield TV Pro and as much as the excitement was at the beginning, as much disappointed I am now. And that's because I have a few issues that from my research was fixed long time ago. But alas, it seems like I still have them and I was wondering if is this a case of returning the problem or waiting a little bit more for some fixes.
On short: Netflix cannot play anything. I can browse and do whatever I want but it cannot play. I get the message that the show cannot be played at the moment and to try a different one. But is the same for all. The message has a tiny code: AIP-703. On a little bit of google-ling I found that it might be a connection problem, or a vpn problem, but I don't have any vpn on my router, the internet connection is ok (also from the app internal testing) , and I also tried on another network, plus my phone as a Hot Spot for the shield. Same result. Netflix on my Chromecast works just fine, so somehow I exclude the network, although I keep hoping that it is a router problem, another reason to replace that and keep the Shield
And another big problem is that I cannot cast to the device. I can see the device on my phone (Samsung Galaxy s5 mini), but I cannot connect to cast from any of the apps that I have (including youtube and netflix). Casting to my Chromecast 2 works just fine.
What I did:
- Full factory reset (yeah, I know, waited for more that 2 hours for this one)
- tried to play with the device and apps not updated and with them updated
- sign out, clear app cache sign back in, sign out of all devices in Netflix account settings
- I even created another Netflix account to see if that was the problem
- router rebut
- tried again and again to see if the issues are gone for more than a week now. 2 days ago I also saw a netflix update and I thought that this is it, the fix, but still, the problem is still there.
So, any other ideas that I should try? Or should I give it back? If yes, should I try another one or I will get on the same results?
Thank you.