Hey, Mike. I want to start by saying that I love the concept behind this app. I really appreciate that it focuses on security and making the most out of Android's native WiFi functionaliy. I'm using Cyanogenmod 13.0/Android 6.0.1, and I'm curious if the Background WiFi scanning works for this version. Just in case, I detailed the issue below.

-Background WiFi Scan: I really prefer the rationale behind this option because I want my wifi to connect based on BSSID, not SSID. This section is check-marked, but greyed out. It says "background scanning is turned off," and gives some instructions to activate it. But, in my Advanced WiFi settings, I only have the "Keep wifi on during sleep" never/charging/always option, and since none of those options seem to un-grey that option in SWM, I can only assume that I'm unable to use this feature in Android 6.0. Am I doing something wrong?

Thanks for making this app!

One more beta, R83. This fixes the notification saying SWM is disabled when wifi is just off, and actually implements aggressive Wi-Fi checking.

If this runs smoothly it'll likely be the next release; with the fixed up timer code it should be much less "weird".

New beta posted on google play!

This fixes a bunch of small random bugs, maybe addresses the problem in N where it turns on and stays on, and adds some new features:

- Ignore open networks. Open networks suck. Turn this on and SWM won't learn from them. This lets SWM coexist with open cable networks and with the google auto-VPN, if you use that.

- Use background Wi-Fi scanning. It's really hard to turn this off and have a reasonable system anymore, so it's not worth throwing an alert for. The devices I've tested don't send probe packets in background scan, and just do passive beacon collection, so there's no real disclosure risk. Since we have to have it on, we might as well use it - in background scan mode, SWM will remember the BSSID of APs you connect to and us that to determine when to turn on Wi-Fi.

For anyone who thought the tower-level mapping covered too wide a physical area, bgscan mode is for you - it won't activate wi-fi until you're literally in range of your specific AP.

The trade-off is that bgscan won't activate until Android decides to perform a scan. This is fairly regular, and appears to always happen when the device is turned on, so in my tests while it may be slightly slower to turn on Wi-Fi, it gets the job done fine. Hopefully it works the same for others in test.

Seems like on DP5 there's some spurious turn-on of Wi-Fi where it thinks you've used it somewhere nearby, but haven't.

I'm still trying to narrow it down, though, unfortunately.

It seems like things still work with the new N preview release, but I'll keep testing. Over all the differences from m to n seem less than the change from l to m. 

R76 beta processing in the play store.

Does a more aggressive permissions check to make sure that we didn't lose permissions in the background (before an alarm fires, for instance), and fixes a UI loop if the permissions management system has decided we have to show the user an explanation for permissions.

Both of these are android 6 only issues.

I'm contemplating integrating the 'nearby' API to allow using Eddystone beacons as triggers for where you use wifi, instead of towers.

Of course, figuring out the UI would be the killer part of it, and making it make sense from that regard, but it might solve some problems for people who:

a) want higher precision than cell towers
b) are willing to buy a beacon

and I suppose

c) don't want to use GPS

I'm still hesitant to roll the gps geofencing in since it would take a lot more power, and is a lot less reliable once wifi is turned off and background scanning isn't available. Ha.

Feature Request: I often take a bus that provides wifi. As a result, I would like to disable wifi manager while I am moving. However, I often forget to turn it back on. So, the request is, add a feature where I can disable wifi management for a set period of time. For me, an hour would be appropriate but I assume a settable amount would be a better feature.

Thanks for a great app! 

Is this the best place to make feature requests? 

Did anyone else here have problems with Android 6.0?
I have a nexus 5 and it keeps crashing; I have been sending the feedback report with every crash but m starting to think m the only one with the issue. 
Wait while more posts are being loaded