OK, I'll add 1km option, maybe also 2km ? I checked if it's possible to use sub kilometer values but an implementation detail currently prevents this. Concerning the 1 tile corridor, I'll have to check the source, its been a while since I wrote that part of the code
Yeah, it is quite confusing. This is because it is quite time consuming to check which tiles are available and which need to be downloaded. ModRana currently just lists the maximal number of tiles that would be needed, thats why there is the ~ before the number I changed the size estimation function for the next version so that it removes tiles that are available, so it should show the number o actually needed tiles after the tile estimation job finishes.
There is setting in options that disables the automatic tile download...but I'll have to check if it's actually working/implemented
The activation should be much easier when widgets finally become clickable, etc. Regarding the tracklog selection, what about a longclick near the track + "do you want to select track XY"popup ?
The next version will have a logging feature (basically stdout piped to a textfile in MyDocs). This may help to find the root cause of the lockups. BTW any guesses why such hard lockup can even happen ? IMO there is a hardware watchdog that is checking multiple device parameters and should prevent this or just restart the device...
There is definitely room for improvements in power-saving. I was thinking about skipping the drawing loop if I can detect that the screen is off (it currently redraws even when the screen is blanked - as do many other apps IMO). As drawing and module state updates are two separate loops, logging etc. should still run normally.
I could also add less pretty but more power efficient optional drawing methods (like not redrawing the map while it's being dragged, moving the map just once a while (like in mappero), etc.).