This is great functionality but is possible to make it faster? When I download map for quite a few points which are distant from each other, it looks like it's downloading e.g. 200,000 tiles. I understand that it works the way it makes rectangle around all points and then checks which tiles in this rectangle are close enough to any of these points. But it runs only about 100-500 tiles/sec on my Nexus S. So when this rectangle is made of 200,000 tiles, it works for ~15 minutes even if there are only 100 tiles to download.
Are you able to change this behavior to make it work faster?
In the past I made simple app for WinMobile 6 which did this: it converted GPS coords to tiles' coords, added & substracted 1 somehow and I had 9 tiles around every point. It was pretty fast even though it was slow .NET app on slow WM device written by someone who's not very good programmer. :-)
But I don't know if there are any disadvantages or complications to use this way in Locus...