Norton Android 13 no longer autoconnects

[MRNIGELGWILLIS]

Note: Please do not post Personally Identifiable Information like email address, personal phone number, physical home address, product key etc.

Issue abstract:

Detailed description: I have finally twigged that my Android 360 for mobile Version 26.9 can no longer tell that my home wifi is secure and will no longer auto disconnect when i get home. Nor will it connect when i go to my local coffee shop even though it is not secure.

Can anyone tell me please if these problems well known and being sorted?

Any feedback welcome.

Product & version number:

OS details:

What is the error message you are seeing?

If you have any supporting screenshots, please add them:

[bjm]

@MRNIGELGWILLIS

Android 360 for mobile Version 26.9 can no longer tell that my home wifi is secure and will no longer auto disconnect when i get home. Nor will it connect when i go to my local coffee shop even though it is not secure.

Can anyone tell me please if these problems well known and being sorted?

Hello @MRNIGELGWILLIS
and you’ve restarted device?
and you’ve reinstalled Norton 360 – granting all permissions?

Do you happen to use Android Auto (especially wireless Android Auto)? Asking because it can create unusual Wi-Fi/VPN behavior on some Android devices and may affect how Norton detects trusted vs untrusted Wi-Fi networks.

• Android battery optimization/background restrictions can interfere with Norton VPN staying active. Norton itself mentions excluding the app from battery optimization.
• Some Android users reported the “Automatic” VPN protocol causing connection logic problems, while manually selecting WireGuard/OpenVPN improved stability.
• Trusted Networks handling seems inconsistent for some users after updates.

Typical troubleshooting steps being suggested by experienced forum members include:

• Verify Auto Connect is enabled
• Re-check Trusted Networks entries
• Disable Android battery optimization for Norton 360
• Try changing VPN protocol from “Automatic” to WireGuard/OpenVPN
• Remove/re-add trusted Wi-Fi networks
• Reinstall Norton 360 mobile
• Ensure no second VPN app is installed simultaneously

There appears to be complaints around Norton Android VPN auto-connect/trusted network behavior after newer app updates, but there is not much evidence of Norton publicly acknowledging a widespread known bug yet. Some of the forum discussions suggest behavior changes rather than outright failure.

The OP’s symptoms specifically point to:

• Trusted Wi-Fi recognition failing
• Auto-connect logic not triggering properly
• VPN not disconnecting on trusted home Wi-Fi

There are scattered reports of Norton Android VPN auto-connect/trusted-network issues on newer builds, but it’s unclear whether this is a confirmed widespread bug, an Android networking change, or a device-specific regression.

An Android 13 device in mid-2026 is likely:

• an older phone/tablet,
• a lower-end model with shorter support lifecycle,
• or a device no longer receiving major Android or vendor networking updates.

That matters because VPN auto-connect and “trusted Wi-Fi” detection rely heavily on:

• Android network APIs,
• background service permissions,
• battery management behavior,
• Wi-Fi state reporting,
• and vendor customizations (Samsung, Xiaomi, Motorola, etc.).

So the issue may not be purely “Norton broke it.”

A reasonable interpretation is:

Norton v26.9 may now depend on behaviors or permissions that are less reliable on older Android 13 devices, especially if the device manufacturer stopped optimization/security updates.

In other words:

• the app updated,
• Android stayed old,
• and the interaction changed.

That would also explain why there are not huge waves of identical reports:

• newer Android 14/15 devices may behave correctly,
• while certain Android 13 devices regress quietly after app updates.

Android 13 on an older/no-longer-supported device could absolutely be part of the equation here, especially with VPN auto-connect and trusted Wi-Fi detection. Recent Norton app builds may simply not behave as reliably on older Android networking stacks.

AI sourced content may make mistakes

[MRNIGELGWILLIS]

Thank you for all the feedback bjm - as usual. I will meditate on what you have said first of all.

[globus5000]

det er en generel fejl på alle enheder de ser på den nu senior teamet

[MRNIGELGWILLIS]

At least today when i went for a coffee it auto-connected and when i got home it disconnected. Cant wait for it to be solved though.

[peterweb]

Assuming your home network is properly secured with a strong password, that is how the VPN Auto Connect is supposed to work. Turn on when unsecured network is detected, and turn off for a secure network, such as your home network.

[MRNIGELGWILLIS]

Hello.

I added that as a courtesy. Before that my app was failing to auto connect when I went into place with an unsecured network on not turn off when I got home.

[peterweb]

So were you just reporting that things are fixed? I just wondered because you said " Cant wait for it to be solved though." What needs to be solved?

[MRNIGELGWILLIS]

I am not sure if it is fixed or even what broken was . Tomorrow wj j I switch on mh phone and visit Tesco I should see the same behaviour. Then we will see!