Android Field Triangulate has historically stored events (collections of readings comprising a triangulation) in memory. The intention was to create a few readings (in a relatively limited timeframe) and create a triangulation. Job done, triangulation shared. In actuality this isn’t how things always work, and wasn’t always sufficiently reliable.
Despite attempts to save these readings to instance state, in memory storage could lead to lost data … say if the application is unloaded (e.g. by a battery saver killing applications.) Lost data is never good, and this was never the intention.
Note: The reason for network connectivity at first setup is because the persistent store utilized is a cloud synchronized database. In theory (given a named account) this could be used to synchronize events (readings and triangulations) between devices. Please contact me if that seems of interest.
BTW: If/when asked for location permissions, Android Field Triangulate doesn’t need more than “Allow only while using the app”.