SecureW2: Android 10 and 11 Connectivity Issues

Are you having issues using your SecureW2 Android Application to connect Android 10/11 device to your organization’s Wi-Fi?

Don’t worry! You’re not alone.

Due to recent changes made to the Android 30 Software Development Kit (SDK), there are a few ways the SecureW2 Android App interacts with the Android Operating System (OS) that have caused a lot of people to have trouble connecting to their Wi-Fi network.

So if you need help connecting your Android device to your Wi-Fi network, read this article and we will help you get your device back on the network!

Why Won’t my SecureW2 App Connect to Wi-Fi?

The recent changes Google made to the Android SDK now prompts users to “Allow suggested Wi-Fi networks?” or “Connect to Wi-Fi networks?” (see image below). If you don’t press Allow on this prompt, the SecureW2 App can’t connect your device to the Wi-Fi network!

While Google has promised to fix this in Q1 of 2021, they haven’t specified if this fix will be an update for Android 10 or 11, or just something that’s fixed in Android 12. Making the situation worse, Android 10 devices experience delays waiting for the notification to pop-up, which is confirmed as another bug by Google.

However, after rigorous testing and feedback from the field, we’ve summarized the best ways you can get around this issue and get your Android connected today!

Re-Connecting Your Android Device

If you denied the system notification to “Allow suggested Wi-Fi networks?” there are a couple ways to get your device connected to the Wi-Fi network. The fastest and easiest way to connect your device to the network is to remove the SecureW2 Android App and reinstall it.

Reinstalling the SecureW2 App

  1. First remove the Wi-Fi network you were attempting to connect to
    1. From the main menu, select Settings.
    2. In the Settings screen, select Wi-Fi settings from the Wireless and Network section
    3. Select the secure Wi-Fi network your organization uses. Some real-world examples include:
      1. eduroam
      2. Columbia U Secure
      3. UNA WiFi
    4. Click Forget 
  2. Uninstall the SecureW2 JoinNow App from your Android Device
  3. Connect your device to your organization’s Onboarding Wi-Fi SSID
    1. Onboarding SSIDs are the Wi-Fi networks dedicated to setting up devices for the secure Wi-Fi network. Some real-world examples include:
      1. University of Washington
      2. UNC-Setup SSID
      3. WiFi@OSU
      4. Columbia University
      5. UNA Start Here
  4. If you are not redirected to your organization’s SecureW2 Landing Page automatically, navigate to it by using your preferred search engine and searching for your organization’s name + Wi-Fi and you should be able to find the SecureW2 Landing Page on your organization’s Wi-Fi IT page.
  5. The landing page should automatically detect your device is an Android device and present you with some instructions.
    1. Follow Step 1 and click Download which will navigate you to the Google Play Store where you can re-install the SecureW2 Application
    2. Once the app is installed, return back to your browser and click the “JoinNow” button.
  6. Once the application opens, enter in your username and password provided by your Organization.

IMPORTANT: This next section highlights how the SecureW2 Android Application works around the nuances of the Android Operating System that commonly prevents devices from properly connecting to the Wi-Fi network. Do not proceed further with the SecureW2 Android Application before reading the next section!

Configuring the Mandatory Android System Settings

  1. Once you’ve entered in your credentials, you may be prompted to enter in a device description if your organization requires it. If you are not prompted, that is ok.
  2. Next, you will see a window that says Enrolling… which will be followed by Connecting…

This is where you will need to follow instructions carefully, so please pay close attention!

  1. In this Connecting… window in the App (shown below), you will see a set of instructions guiding you how to forget the Onboarding/Setup Wi-FI network you are/were using to download the SecureW2 App. If you’re not sure which network is your “Onboarding” network, here are some real-world examples of them:
    1. University of Washington
    2. UNC-Setup SSID
    3. WiFi@OSU
    4. Columbia University
    5. UNA Start Here

  1. Once you’ve forgotten/removed your Onboarding Wi-Fi Network, go back to the SecureW2 App.
  2. The app will now trigger an Android System notification asking you to Allow suggested Wi-Fi networks? or Connect to Wi-Fi networks? (some examples shown below) Select “Allow”, “Yes” or whatever confirmation option is shown to you (it varies per version of Android you have).

IMPORTANT: It is incredibly important that you do not decline, or ignore this Android System Notification. With recent changes made by Google, declining and dismissing this notification will prevent the SecureW2 Application from being able to configure your device to the Wi-Fi network!

Help! I Don’t See the ‘Connect to Wi-Fi Networks?’ Prompt!

One bug that we’ve seen recently is that Android 10 device either don’t receive this prompt, or receive this prompt after a really long delay (sometimes over 4-5 minutes!) This is a confirmed bug by Google, and it will require Android 10 users to manually connect to their organization’s secure Wi-Fi network manually. To do this:

  1. Navigate to your Wi-Fi Settings
  2. Select the secure Wi-Fi network your organization uses. Some real-world examples include:
    1. eduroam
    2. Columbia U Secure
    3. UNA WiFi
  3. If prompted, select your Certificate that was generated by the SecureW2 Android Application

Note: When connecting to the secure Wi-Fi network, the Android System Notification “Connect to Wi-Fi Networks?” may prompt. If so, do not decline or dismiss this or you will be forced to reconfigure your device!

Parting Notes

If you’ve followed the instructions shown above, the SecureW2 Android Application should be able to configure your device without any issues.

It is unfortunate that these changes were made by Google, but with promises to change this in Q1 of 2021, this issue will likely go away in the near future.

If you’re still having issues with your Android Application, please reach out to your Organization’s IT team for further assistance.