POI alert STOP button doesn't stop the POI alerts

Thanks for the quick clarification. Strange because I've never seen this button before. I do have "notify till stopped". I only have one (quick) point/ one folder being monitored so was confused why STOP button didn't stop the notifications.

You are welcome.

You may simply simulate POI alert feature with disabled GPS in Locus to test it's behavior.

I do notice if I tap STOP then move away from the point, then back towards the point, the notification is re-triggered. How much distance hysteresis is there? Maybe that was what I observed?

Related question then, what if the POI alert is enabled, then I add a point into a monitored folder (say quick point), then I move (simulate) position towards towards point. It appears a notification is not triggered. Only if the point exists before the POI alert is started does the notification occur. If there were minimal cost (processing/ battery) to having POI alerts permanently enabled I should be able to add/ delete points anytime into a monitored folder and have the notification occur/ stop. For me, no need to start/ terminate.

And is there any reason the POI alerts screen has two X's:

Moving out of defined range from point and return back into the range definitely trigger alarm again!

POI Alert keeps internal list of possible targets and refresh it when needed. Anyway I have to say that used system is really really old and definitely needs improvements. It also have some holes, like these "quick points". I've fixed it, so next time new "quick point" should be automatically added to "possible point for POI alert alarm".

I always saw huge potential in this feature, but I see needs for an improvements to make it perfectly usable.

Issue with double-x fixed too, thanks!

OK, great result. You didn't comment on the CPU load for permanent POI alert? I see no reason to disable POI alerts. I simply add/ delete or hide quick points as I am riding for when I want an alert. My use case - navigating along track, find nearest upcoming shop, add quickpoint, get alert, delete point. Beautiful.

Ah CPU load ... I'm checking code and seems that troubles may comes in case of huge number of points. Anyway during enabled GPS & lower number of points, this should be quite fast and efficient. In case you notice increased battery usage, let me know and push me little ... I see space for improvements here.

Excellent. I generally hide most points (although while away I did have 2000

camp ground points visible for route planning) but my use-case is to only

have max. 1 visible point in monitored POI alert folder.

Do you mean huge number of user defined basic points across all folders or huge number of points in monitored POI alert folder(s)? It may be a while before I can test battery usage as winter here now. It needs quite long ride (>5h) before change in battery % is meaningful.

Ah no no, only important are monitored folders. POI alert has internal list of points that check and for which compute distances after every change of your position. In this list are anyway only visible points from monitored folders.