termux-location times out, returns nothing

If I run termux-location two times in a row, the first one will work and give me a json object and the second time it will time out after roughly thirty seconds and return an empty string. This happens for both gps and network providers. I haven't tried the third. I am running Termux on a Samsung S8+.

I am going to cache the response and use a timestamp to give the response of termux-location if it is going to be called more than once in fifteen minutes, but is that a safe enough pause? Can I go lower?

As for a more permanent fix, could we please have some more information as to how and when to use this? There wasn't a man page for it, and that seemed pretty odd.

Start by reproducing the consecutive termux-location calls with GPS and network providers, confirming the second call times out and returns an empty string. Trace the termux-location entry point and related Android request handling, then review available documentation. Done means repeated calls behave predictably and the command's usage and timing limitations are documented.