Presently, we search for a home wifi in order to act in client mode. After some timeout of non-finding, we revert to acting as an AP beacon.
For some OSes that's great - they connect to SOTAcat and retain their external internet access for calls to figure spots, etc.
On Android, this bi-network situation is somehow precluded. A work-around, though, is to broadcast a hotspot from the phone, and have the SOTAcat connect to that.
That is very convenient, but perhaps not most convenient for debugging (or even data-usage fees), where preferential access to home network might be best.
Here I propose two SSID/password combinations to be searched in order, and specified in a way that is user-describable and saved across sessions in NVRAM.\
Presently, we search for a home wifi in order to act in client mode. After some timeout of non-finding, we revert to acting as an AP beacon.
For some OSes that's great - they connect to SOTAcat and retain their external internet access for calls to figure spots, etc. On Android, this bi-network situation is somehow precluded. A work-around, though, is to broadcast a hotspot from the phone, and have the SOTAcat connect to that.
That is very convenient, but perhaps not most convenient for debugging (or even data-usage fees), where preferential access to home network might be best.
Here I propose two SSID/password combinations to be searched in order, and specified in a way that is user-describable and saved across sessions in NVRAM.\
Comment?