Jump to content
howardagoldberg

Android 10: Interesting Issue with Location, Permissions, and WiFi identification

Recommended Posts

I just upgraded my Pixel 3 (Verizon Wireless) from Android 9 to Android 10 on my secured home network.

Interesting issue encountered: After the update, ESET Mobile Security flagged my home network as an 'insecure public WiFi hotspot,' and recommended that I disconnect!

Reason? ESET had not been given location permissions and therefore could not resolve the SSID of the network (even though I was connected to the WiFi).

Giving ESET location permissions resolved the issue, no muss - no fuss.

So, just as a heads up: If network aware apps aren't working correctly (security apps, WiFi/Network scanning apps, apps that sync over WiFi such as DejaOffice) after updating to Android 10, make sure you give those apps location permissions.

As an aside, hopefully ESET folks will test this themselves, and roll out an update to account for this change in Android 10 so less savvy users do not become concerned that they are suddenly connecting to a non-secure public network from their home! ūüėȬ†

@Marcos

Share this post


Link to post
Share on other sites

This does not work for me. Location permission is enabled for eset.

Share this post


Link to post
Share on other sites
47 minutes ago, MikeO3 said:

This does not work for me. Location permission is enabled for eset.

Thoughts:

1) Is the permission for location set to 'always' or 'just when app is in use?' It needs to be set for always.

2) Are you certain that the WiFi network you are on is actually secure (WPA2 or better)?

3) After setting the location permission for ESET, toggle your WiFi off, let the phone connect to LTE, then turn the WiFi back on. I had to toggle the WiFi in order for ESET to 're-scan' the network I was connected  to.

Hope that helps!

Share this post


Link to post
Share on other sites
2 hours ago, howardagoldberg said:

Thoughts:

1) Is the permission for location set to 'always' or 'just when app is in use?' It needs to be set for always.

Yes, Always...

2) Are you certain that the WiFi network you are on is actually secure (WPA2 or better)?

Yes, it is my home network.

3) After setting the location permission for ESET, toggle your WiFi off, let the phone connect to LTE, then turn the WiFi back on. I had to toggle the WiFi in order for ESET to 're-scan' the network I was connected  to.

This worked and appears to have solved the problem. i ran an audit and now the error is no longer reported.

Hope that helps!

Thanks for you help and quick response.

1. Yes, it is Always.

2. Yes, WPA2 personal (this is my home network WiFi)

3. Disconnect & reconnect WiFi worked.

 

Thank you for your suggestions as it appears to be resolved now after an scan and reviewing the audit summary.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...