howardagoldberg 13 Posted September 3, 2019 Share Posted September 3, 2019 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 Link to comment Share on other sites More sharing options...
MikeO3 1 Posted September 4, 2019 Share Posted September 4, 2019 This does not work for me. Location permission is enabled for eset. Link to comment Share on other sites More sharing options...
howardagoldberg 13 Posted September 4, 2019 Author Share Posted September 4, 2019 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! Link to comment Share on other sites More sharing options...
MikeO3 1 Posted September 4, 2019 Share Posted September 4, 2019 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. howardagoldberg 1 Link to comment Share on other sites More sharing options...
somewheretodisappear 1 Posted October 16, 2019 Share Posted October 16, 2019 I was having the same issue on a Pixel 2 after the Android 10 update. Permissions were set to Always. Disconnect/reconnect to home WiFi fixed the error. Thanx. howardagoldberg 1 Link to comment Share on other sites More sharing options...
Walt 1 Posted October 19, 2019 Share Posted October 19, 2019 Thanks! I had the same issue with a Pixel XL after upgrading to Android 10. Giving ESET Location always permission, and toggling wi-fi off and on cleared it up. howardagoldberg 1 Link to comment Share on other sites More sharing options...
howardagoldberg 13 Posted October 20, 2019 Author Share Posted October 20, 2019 (edited) @Marcos @Peter Randziak Late last week, ESET Mobile Security for Android was updated on my device to version 5.2.18.0. With the update, this issue has returned with somewhat different symptoms, but it is easily reproducible: 1) While on my home network, no 'warnings' from ESET. 2) If I leave my home, keep WiFi on (but not connected, obviously), phone automatically switches to LTE, no issues. 3) RETURN home. Phone reconnects to home WiFi network. Now, ESET throws a warning that I am connected to an insecure network and I should disconnect. 4) Toggle WiFi off. Toggle WiFi on, issue 'resolves.' But obviously, it's a bit of an annoyance to have to toggle WiFi off and on again on my home network that is fully secured. Clearly, this is a bug. I am running the latest version of Android 10 (with both the system and 'play' October security patches) on a Pixel 3 running on Verizon wireless. Location setting for the app is to allow location access at all times. Please advise. Thank you! Edited October 20, 2019 by howardagoldberg Link to comment Share on other sites More sharing options...
howardagoldberg 13 Posted October 23, 2019 Author Share Posted October 23, 2019 On 10/20/2019 at 1:51 PM, howardagoldberg said: @Marcos @Peter Randziak Late last week, ESET Mobile Security for Android was updated on my device to version 5.2.18.0. With the update, this issue has returned with somewhat different symptoms, but it is easily reproducible: 1) While on my home network, no 'warnings' from ESET. 2) If I leave my home, keep WiFi on (but not connected, obviously), phone automatically switches to LTE, no issues. 3) RETURN home. Phone reconnects to home WiFi network. Now, ESET throws a warning that I am connected to an insecure network and I should disconnect. 4) Toggle WiFi off. Toggle WiFi on, issue 'resolves.' But obviously, it's a bit of an annoyance to have to toggle WiFi off and on again on my home network that is fully secured. Clearly, this is a bug. I am running the latest version of Android 10 (with both the system and 'play' October security patches) on a Pixel 3 running on Verizon wireless. Location setting for the app is to allow location access at all times. Please advise. Thank you! @Marcos @Peter Randziak ... ^^^ any thoughts? I just left my house to run an errand. When I returned, and the phone reconnected to WiFi, ESET is throwing up the 'insecure network' notification. This is def a bug ... Link to comment Share on other sites More sharing options...
howardagoldberg 13 Posted October 25, 2019 Author Share Posted October 25, 2019 On 10/23/2019 at 12:42 PM, howardagoldberg said: @Marcos @Peter Randziak ... ^^^ any thoughts? I just left my house to run an errand. When I returned, and the phone reconnected to WiFi, ESET is throwing up the 'insecure network' notification. This is def a bug ... On 10/20/2019 at 1:51 PM, howardagoldberg said: @Marcos @Peter Randziak Late last week, ESET Mobile Security for Android was updated on my device to version 5.2.18.0. With the update, this issue has returned with somewhat different symptoms, but it is easily reproducible: 1) While on my home network, no 'warnings' from ESET. 2) If I leave my home, keep WiFi on (but not connected, obviously), phone automatically switches to LTE, no issues. 3) RETURN home. Phone reconnects to home WiFi network. Now, ESET throws a warning that I am connected to an insecure network and I should disconnect. 4) Toggle WiFi off. Toggle WiFi on, issue 'resolves.' But obviously, it's a bit of an annoyance to have to toggle WiFi off and on again on my home network that is fully secured. Clearly, this is a bug. I am running the latest version of Android 10 (with both the system and 'play' October security patches) on a Pixel 3 running on Verizon wireless. Location setting for the app is to allow location access at all times. Please advise. Thank you! ^^^ This is still an issue. Any updates @Marcos? Link to comment Share on other sites More sharing options...
MikeO3 1 Posted October 25, 2019 Share Posted October 25, 2019 Still a problem for me. I disabled eset wifi network checking. Link to comment Share on other sites More sharing options...
Most Valued Members peteyt 359 Posted October 29, 2019 Most Valued Members Share Posted October 29, 2019 On 10/25/2019 at 9:49 PM, howardagoldberg said: ^^^ This is still an issue. Any updates @Marcos? You might find opening a ticket will get a better result as mods don't always read everything on here. Link to comment Share on other sites More sharing options...
howardagoldberg 13 Posted November 20, 2019 Author Share Posted November 20, 2019 @Marcos @Peter Randziak This is still an issue after today's update to 5.2.31.0. Please advise. Thanks! Link to comment Share on other sites More sharing options...
ESET Moderators Peter Randziak 944 Posted December 11, 2019 ESET Moderators Share Posted December 11, 2019 Hello @howardagoldberg, I noticed similar behavior during Connected home scan. The issue (feature) is caused by the Android permissions i.e. if an application wants to know the SSID of a WIFI, the permissions to read location had to be granted and the Location services enabled... Peter Link to comment Share on other sites More sharing options...
howardagoldberg 13 Posted December 11, 2019 Author Share Posted December 11, 2019 (edited) 11 minutes ago, Peter Randziak said: Hello @howardagoldberg, I noticed similar behavior during Connected home scan. The issue (feature) is caused by the Android permissions i.e. if an application wants to know the SSID of a WIFI, the permissions to read location had to be granted and the Location services enabled... Peter Correct. But I gave ESET full location permissions, and the issue persists. Giving location permissions actually solved the issue right after the release of Android 10, but a more recent update to the ESET app reintroduced the issue - even if ESET has location permissions granted. (Currently my app is at version 5.2.42.0-0) Edited December 11, 2019 by howardagoldberg Link to comment Share on other sites More sharing options...
Recommended Posts