I have just recently purchased a Samsung Galaxy Note 4. I love this phone and didn't have any problems until now. My phone will not connect to any WiFi and it will either say "Saved and Secured" or "Disabled." Either way, it won't connect. I've looked on some different websites and some suggested to reboot my phone. But, I don't know if they are a safe website so I didn't do that. Please help me.
No harm in rebooting, give it a shot.
Related
I have gone through three Verizon Samsung Galaxy Tab 10.1's in the past two days (since the Verizon release).
PLEASE NOTE: this only pertains to Verizon devices while trying to access Google pages using your device's DATA PLAN.
EVERYTHING works fine when you are connected via WiFi.
The first time I opened the browser, it tried to auto-log me into the default Verizon/tablet Google webpage. It never got there. I tried to access other pages in Google until I tired myself out. I tried installing Dolphin, Firefox, etc and still no go. I then tried connecting to WiFi and was able to access Google, so I figured this was probably a 4G issue. So I decided to call Verizon as I was somewhat sad about my new toy. Verizon had no notes or information at the time except for wiping my device a few times. Nothing worked. I was advised to return it, as it was deemed defective by Verizon's Tech Support.
I brought my device in and swapped it out. This one did the exact same thing. I tried logging onto Yahoo and it worked though. I showed the Verizon staff inside the store (because they had been fiddling with it for over an hour) and they were very happy to see that I found a way to make it work. I then tried accessing other sites and it also worked. About 10 minutes later, the staff had checked their Tech Notes on their Intranet or whatever they use, and a note popped up about a very large number of other customers reporting this problem.
Verizon said that they had a server issue and that was why this was not visible in their "notes" earlier. They said they are working on the problem and should have a way to fix the problem very shortly. One of the Techs their said I would be lucky if it happened in the next update. So we will see what happens.
Again this is only affecting a small portion of the Verizon Tab 10.1 4g LTE users at this time. And only when you are connected to CDMA or 4G. If you are having these issues with Google while on CDMA 4G (your data connection), just use your WiFi and everything should work just fine.
Don't cry. It will all be okay.
PS: I would like to apologize in advance if this post is not in the proper section. I am sorry.
-h3lls
Droid X-Droid X2
Xoom-Galaxy Tab 7-Galaxy Tab 10.1
Verizon Wireless
thanks for the info. BTW do you have Gtab wifi other than verizon Gtab. If yes any difference in functionality?
tabing said:
thanks for the info. BTW do you have Gtab wifi other than verizon Gtab. If yes any difference in functionality?
Click to expand...
Click to collapse
I personally do not have a Galaxy Tab (WiFi Only) for either the 7 or 10.1.
But my ex-wife has the WiFi Only version and she says that there is not as many processes running in the background on her WiFi Only Tab (compared to mine). I would have to guess that this has to do with the Provider, but I could be totally wrong.
-h3lls
Droid X-Droid X2
Xoom-Galaxy Tab 7-Galaxy Tab 10.1
Verizon Wireless
I have the same issue...
I wanted to chime in on this post to let you know what I've found out and to also give you a background on the experiments I've conducted both locally and with the Verizon techs.
I purchased the new Samsung 10.1 4G LTE tablet 2 days ago and have the same issue where I can't access google.com or anything related to the google domain via a browser when connected to the cellular network. Over wi-fi it works fine, but not over the 3g network.
That being said, I called Verizon tech support (no one had been aware of any issues with the tablets), and explained what was happening. I was escalated to a very good tech who walked me through several tests. In addition, I had two people in my office that had other tablets (a Verizon Xoom and an iPad2). This setup the perfect test bed.
Here's what we found out:
1. My Samsung 10.1 4G LTE can connect to google.com via wi-fi (both via a router and cellular hotspot).
2. My Samsung 10.1 4G LTE cannot connect to google.com via the cellular connection.
3. We did a factory restore on the tablet but that had no effect.
4. I turned on the Samsung 10.1 hotspot and had the other tablets try to connect to google.com using my cellular connection to see if it was something on their server blocking the domain. Both their tablets connected successfully.
5. I downloaded both Firefox and Dolphin browsers to see if it was in the default browser. Both didn't load google.com.
6. Tested all the google apps on the Samsung and all worked via wi-fi and cellular connection.
The only thing I couldn't try was to load google.com inside a 4g network. I live in South Texas and the closest 4g network is 2 hours away.
So...
I was told to take back the device to where I purchased it and exchange it to see if it was the device. It took about an hour to see the local tech, so in the meantime, I though I would try the display tablets in the store to see if the problem existed with those.
All the Samsung 10.1 4G LTE devices didn't load google.com over the cellular network.
I felt like I had reached the limit of what could be done, but I still was interested to see if it would work in a 4g network.
So...
I had one of the techs call another Verizon store in San Antonio (a 4G environment) to have them load google.com.
IT WORKED!!!
My conclusion is that there is an issue with the tablet's software that is preventing google.com from loading via a 3g cellular connection. This explains why some people can get it to work (4g network) while others can't (3g network).
The tech went ahead and exchanged my device for a new one (which by the way, still didn't load google.com as expected) so he could send it back to Verizon and start the process of getting this rather embarrassing situation fixed...hopefully.
The ironic thing is, this only affects loading google.com and no other website. Being a google supported device, I would expect this to be resolved quickly.
I hope this has been helpful.
UPDATE: My 10.1 is working FLAWLESSLY now.
Thanks for the chime in. As I had said, the Tab worked fine with Google when connected to wifi, just not when connected to the Verizon network. That was the whole issue. The software issue seems to be a part of the issue, BUT I HAVE LEARNED THAT THE 4G LTE SIM CARDS MAY WELL ALSO BE A HUGE ISSUE (ALSO HOW THEY WERE INSTALLED).
The way the SIM card is installed could have been an issue, but there also could have been an issue with certain "batches" of 4G LTE cards that Verizon was given. To be perfectly honest, the first tablet I had that had this problem, I returned immediately and asked them to just replace my device and give me the card to take home so I could install it myself (I had been the only customer that day [opening day] to pickup a 10.1 and nobody there really knew how to set them up. They know the type of work I do and had no issue with it. I followed directions exactly as described, and still had the same issue.
It really disturbed me though when I had brought my first 10.1 back and they spent an hour into closing trying to figure out what was wrong (all 5 employees). The man who installed the card in the first place really wasn't even that sure if he had done it correctly. I don't think everyone was really too up-to-date on how to get these Tabs up and running with the LTE out of the box.
Verizon later told me that problems with the SIM cards themselves could be corrected without having to manually service the device.
Who knows.... All I know is that the issue is no longer a problem for me. If anyone is still having problems in this area, please try and give me any details you can besides what has already been said. This way I can forward the information to my colleagues at Verizon and Motorola and update them further.
PS: I had also just learned that if you lived in an area where 4G was not available, but was suppose to be in the very near future, you could have also had some "issues" with your 10.1. Nothing too specific, but there could be a handful of odd issues concerning new and upcoming 4G locations. That's about all I can really say.
-h3lls
Droid X-Droid X2
Xoom-Galaxy Tab 7-Galaxy Tab 10.1
Verizon Wireless
Sent from my DROID X2 using Tapatalk
Chiming in here. I've had the same issue with not being able access Google sites while on CDMA (LTE coming in November locally) since I purchased the GTab 10.1 LTE a week and a half ago. I have read posts on several forums with others having the same issue. After seeing this post today I tried once more using CDMA and it works. I have not made any changes or messed with the SIM card on my Gtab. Verizon must have done something on their end.
Whenever I am somewhere with a new network, my Tab is slow to recognize it. Sometimes the network will show up in the list of available networks for a brief moment, and then disappear before I can establish a connection. Other times I can connect by manually adding the SSID. Sent Sometimes turning the wifi off and then back on, or rebooting the Tab, works, but not always.
Most recently, I was in a place for almost an hour before it recognized the local network, even manually adding the SSID didn't help. The weird thing is, once it saw this network, it also saw several others in the neighborhood that previously were not shown on the list of available networks.
Once you I finally establish a connection, reconnecting to that network usually works without a problem.
Any thoughts?
Sent from my GT-P7510 using xda app-developers app
Try a factory reset or if you are in any custom rom, try reflashing other rom.
Factoryreset willerase all your data so watch out.
Tried a factory reset... Didn't fix it. Here's the strangest thing: if I bring another network into the picture, all of a sudden it recognizes all the nearby networks. For example, right now I am in a place with 5 or 6 networks. Couldn't see any of them, until I fired up my cell phone's teather app, at which point it recognized not only the cell phone teather network but all of the others as well. It's almost as if it needs a new network to come along and wake it up. Other times though, it is my cell phone teather network that it won't see!
Sent from my GT-P7510 using xda app-developers app
you need to mention if you have stock or non-stock, rooted or not, etc.
my best guess is that you are rooted and running a non-stock ROM. in this case, you should try another kernel. the wifi modules are the ones causing most of the problem, whatever the device. make sure you flash the proper wifi modules after the kernel!
otherwise... I would suggest to root. I heard all kind of crazy stories about our beloved Tab, so... don't fear trying different solutions until you get the one working for you.
okty2k said:
you need to mention if you have stock or non-stock, rooted or not, etc.
Click to expand...
Click to collapse
Stock, not rooted. That's what makes this so frustrating - I haven't messed with anything, and it still doesn't work right! I'm running the most current Samsung android distribution for the Tab 10.1.
I've been avoiding rooting the Tab because one of the apps I use does a root check and won't run on a rooted device, but I think there is a workaround to that so rooting is definitely a possibility.
Rooting the device won't be sufficient in itself to solve this problem - I'd need to root and then install a different kernel, right? Or are there wifi modules I can install on top of the stock kernel (once I root the device)?
Any ideas on why this is happening and how I might fix it, short of rooting and installing a non-stock version of Android? My temporary fix is that I fire up FoxFi on my cell phone, and once the Tab sees the FoxFi network, it all of a sudden "sees" the other networks as well. But I've had several situations where I have my tablet but not my cell phone, and in those instances I can't get the Tab to recognize the new networks, even if I reboot the Tab or try messing around with the various networking settings. Note that a factory reset didn't fix this either.
Never mind - broke down and installed CM10.1.
I was having a similar issue on stock. I rooted and have since installed a few roms. I am a Much bigger fan of my tab now. I used infamous for a while and am now on the paranoid android 3.50 build which is awesome!
CM10.1 solved the shy network problem for me... And my tab is much more reliable now too.
Sent from my HTCONE using xda app-developers app
I tried searching this fourm, online, and no results after countless hours.
This is my problem. At work there is one big open network with a lot of extenders everywhere. When I got my new phone phone from BB when I broke my screen I tried to connect to it and it says " Connecting...." for a few seconds then automatically goes to "Saved".
I tried the obvious, forgetting network, rebooting phone, restoring to factory, updating firmware, nothing has worked so far. It always goes from connecting to saved. Every other device has worked flawlessly besides this phone
My last few phones have had no problem connecting. I do not have the authority to reboot the whole system, change frequently, add a pw, basically I'm only allowed to connect.
Wondering if anyone has experienced this problem, and might have any ideas or solutions. This is the only network that has ever gave me a problem.
Thanks for taking your time to read and help!
Sent from my SAMSUNG-SGH-I337 using XDA mobile
Has anyone else ever experienced this problem?
fals3illusion said:
I tried searching this fourm, online, and no results after countless hours.
This is my problem. At work there is one big open network with a lot of extenders everywhere. When I got my new phone phone from BB when I broke my screen I tried to connect to it and it says " Connecting...." for a few seconds then automatically goes to "Saved".
I tried the obvious, forgetting network, rebooting phone, restoring to factory, updating firmware, nothing has worked so far. It always goes from connecting to saved. Every other device has worked flawlessly besides this phone
My last few phones have had no problem connecting. I do not have the authority to reboot the whole system, change frequently, add a pw, basically I'm only allowed to connect.
Wondering if anyone has experienced this problem, and might have any ideas or solutions. This is the only network that has ever gave me a problem.
Thanks for taking your time to read and help!
Sent from my SAMSUNG-SGH-I337 using XDA mobile
Click to expand...
Click to collapse
if i'm not wrong you need to reflash stock rom because your kernel is broken i get this problem with a galaxy s2 after that all working great
mugensiz said:
if i'm not wrong you need to reflash stock rom because your kernel is broken i get this problem with a galaxy s2 after that all working great
Click to expand...
Click to collapse
Funny thing... I just got a brand new galaxy note 3 and it does the same thing... Making me think something with this Wifi setup and the galaxy family phones are not getting along. I'll try and see if I can talk to the Web tech and see if he can tweet something to get it to work.
Sent from my SM-N900V using XDA Free mobile app
Hi,
Please excuse my naivety, am relatively new.
I just got my Galaxy S6 Edge Plus and am having a problem with accessing my wifi at work. I find the wifi network and can connect with no problems, except it should come up with an icon asking me to verify myself. I then would add my email address and away I go.
Except, since having this new phone, I can't seem to get access to the verify page. I thought I would be able to access a web page (using Chrome, built in browser AND Dolphin) and forcing the page to come up, but nothing.
Am I missing something at all?
My old phone and my tablet both work as expected. I also tested someone elses phone today, next to my own, and that worked exactly as expected.
Please help!!
Anyone?? Any ideas?
Am at my wits end. Doesn't help that my normal internet signal is a crappy ole E!
I've had my S7 Edge (Verizon, Android 6.0.1, stock Samsung) for, a week, and have been trying to connect to my school's wi-fi with zero success. My attempt is met with:
"Authentication error. Credentials not valid. Incorrect password."
Settings
Security:
802.1xEAP
EAP method:
PEAP
Phase 2 authentication:
MSCHAPV2
Identity:
<my school username, which I have verified with my laptop, and school computers)
Anonymous identity
<none>
Password
<my password, which I have verified on laptop and school computers)
The phone is able to connect to my home Wi-Fi without issue.
I have been able to connect to the school's wifi with my S4 and my laptop with no problem.
I've rebooted the phone, "forgotten" the network several times (with rebooting before attempting to access again).
I've forgotten the network, shut off wifi, shut off the phone, drove to lunch, come back, restarted the phone, turned on wifi, sacrificed a goat (just kidding, NSA), and tried to reconnect, to no avail.
I've check with my IT dept, and they were unable to help. They are, for obvious reasons, unwilling to reboot the router to try that.
With stock Samsung, I'm unable to change wi-fi freq (or, at least, I haven't been able to figure out where to do that).
I've searched online for fixes, and searched through the forum, and haven't found anything I haven't already tried, or are unable to try (ie, router reboot).
I'm completely at a loss here. I'd really prefer not to use my data when there's a perfectly good wi-fi network available...
Any of you smart folk have an idea?
similar issue
I too am facing the same issue. With bit of research it looks like a bug in android 6.0.1 which was patched in later revisions of 6.0.1 which samsung have't updated.
https://code.google.com/p/android/issues/detail?id=188867
http://forum.xda-developers.com/nexus-6/help/broken-wifi-peap-android-m-marshmallow-t3221066
Apparently, there is a simple workaround if we have root, But we are stuck at this point.
I guess this problem could be solved only if Samsung updates the software with merges from newer versions of android or if we get root.
Anyways, post here if anybody finds a solution to this.
I may as well add a "Me too" to this one and a bit of more information.
For me, I have a Galaxy Note 4 for AT&T and it is stock and up-to-date, still connecting to the work WiFi (802.1x EAP -> PEAP username & password) with zero issues.
My Galaxy Note 4 with Verizon (work phone) WAS working until it got updated to 5.01 and then it broke the WiFi to 802.1x, just sits there and says connecting.
Phone (Verizon) got two more updates since then but nothing fixed it.
So, I had them upgrade my phone to the Galaxy S7 (not Edge) and lo and behold, STILL broken! And in the past three days, there has been two OTA updates to the phone, but neither one fixed the issue.
So, I would like to know if it is just Verizon, holding back the patches, or maybe I am lucky because I can still use my personal phone (AT&T) on the company WiFi?
If this is going to be a long drawn out battle to get Verizon to fix it, I think I have just enough clout to get my work phone moved to AT&T as I should not have to use my personal phone for work, even if it is not costing anything (WiFi).
Can anyone confirm the S7 for AT&T works ?
How about the Note 5 on Verizon? (probably not).
Waiting with everyone else. . .