Samsung Galaxy Note II Can’t Connect To WiFi


The Galaxy Note II was one of Samsung’s most stable devices, however, some owners are still troubled with some problems. One of our readers emailed us asking why her phone cannot connect to any WiFi network. While the email message didn’t exactly describe the problem, I will try to cover the possible reasons why this problem happens.

The email:

Good day All

I bought my Gallexy Note II in March 2013. I cannot connect to Wi-Fi, even when I am at a zone where it is much stronger. Can you please advise me on what to do. I have an app that needs to be updated through Wi-Fi but I cannot update it because of the current problem I am coming accross

Kind Regards


Step 1. Make sure WiFi is turned on.

I know it sounds stupid but it’s a necessary step to be able to resolve this problem. From the Home screen, tap and drag the notification bar down. Tap the WiFi icon once or twice so that its color would turn neon green, which means it’s on.

Step 2: Scan for available networks.

After turning on the WiFi, go to Settings => WiFi. As long as you’re within range, you should see available networks on your screen. Tap the network you want to connect to, enter credentials and try to browse the web.

These two steps alone are what you need to be able to connect to any WiFi network. If errors popup during the process, heed to what the device is telling you. But the possible or most common problems you can encounter are the following:

Authentication Error – it means that the credentials you entered like the password are incorrect. Of course, you need to know the correct ones to be able to connect to the network.

Random Disconnection – it’s either the modem / router or the phone itself is causing the problem. If it’s with the network, a simple power-cycle could solve the problem. However, if the disconnection happens when the phone sleeps, the ‘Keep WiFi On During Sleep’ option should be set to ‘Always’ under the Advanced WiFi settings.

Can’t Detect Network – this one’s a bit complicated but knowing that the device we’re talking about in this post is a Samsung Galaxy, there is a possibility that the network the user wants to connect is an ad hoc connection; all Galaxy devices don’t support this kind of connection. Naturally so, the Note 2 cannot detect any signal transmitted using this type of connection.

Device Refuses To Connect – if you’ve done all the possible troubleshooting procedures but the phone still refuses to connect, it could be a hardware problem. Have an appointment with an authorized technician to have the phone checked.

As a workaround, try to use the mobile data if you badly need an internet connection.

Having problems with your phone?

Tell us about them by emailing us at mailbag@thedroidguy.com. Make sure to include as much details as possible so that we could understand the problem well and find the best solutions for you. If you can share a screenshot or two, that would be better.

We may not be able to respond to every email we receive but rest assured we do read them… yes, all of them even if some do look like spams.


Leave a Reply
  1. same thing is happening to my samsung note 2. it was all working well then one day it started to fail connecting. it can’t even detect the wifi connection it used to log. i am wondering what happened. i didnt drop my phone nor wet it. why it suddenly stopped working? help please

  2. It has nothing to do with how much the phone costs. Resetting the access point resolved this 90% of the time. No help in a cafe if they won’t oblige, but at home, this is the answer

  3. I wonder why the author, Harold Hisona makes every problem out to be the manufacturer’s issue, even on something that is most likely an “operator error” – Hes starts this article with the line: “The Galaxy Note II was one of Samsung’s most stable devices, however, some owners are still troubled with some problems.” – Even the title of this places blame at Samsungs doorstep. Ridiculous.

    XDA Developers has several forums that discussed this: There appears to be a problem with new versions of Android and old routers. Many people have reported the “obtaining IP address” loop problem. It has NOTHING to do with Samsung,

    Also, Harold forgot another good troubleshooting method: If a password changes or is entered incorrectly for a secured access point, you need to long press on that item and choose “forget network” then scan for it again and put the correct password in.

  4. Or… Just go to Settings, WiFi. Select “Menu”, then “advanced”, finally select “Keep WiFi on during Sleep” – this is the same as your steps, but is a menu option.

  5. Im having the same issue with my device, i was able to connect then but since im always on the go, i always use my mobile network.. just last month i tried connecting to wifi, my phone can detect the signal but it always says obtaining ip address… i tried to connecting to other wifi,but its still the same, signal is really good and it keeps saying “obtaining ip address”…i have entered the correct password, restarted my phone couple of times but its still the same. my kids dont have a problem connecting to our wifi and they use a cheaper phone

  6. You can try this:

    Go to your phone screen. Now type: *#0011#

    The phone will now go in “Service Mode”

    Now hit the menu button (left hardware button)

    Now go to WiFi menu and you see a button WiFi power save mode

    This button is Enabled now hit this button to disable the WiFi power save mode

    Press back button to exit Service mode.

    This action will boost your range of your WiFi antenne from your phone.

    Note: Battery will drain faster.
    To disable the setting just reboot your phone or repeat above steps.
    Use at own risk.

  7. l faced the problem few months back and it didn’t have to do with ad hoc network. It just refuses to connect, authentication error kept popping up. What I did was installed a patch I found through Google. Very sorry for I do not remember the link. You do need a rooted phone. However for some reason this problem sorted itself out after I updated the device to 4.1.2. Maybe it was one of those minor update that did not play nice? Back then it always worked fine with the default Android built. Was so till I installed a minor software up paste. I mean I did hard reset and even re-installed the OS.

Leave a Reply

Your email address will not be published. Required fields are marked *