HAM seems to treat them as required. I don't use fapman, so have no idea how that handles it.

Looks like 1.19 doesn't cause it to happen any more. I tried it on the way to work today and it loaded just fine...

Yes, I'm following at least two, but the main one appears to be here.

[/QUOTE]
I like the third option (and think it will help). I also would like to propose the following: Trigger on not just the current point, but the point after it. This way, even if it's still focused on a point behind us, once we pass the next point it will auto-fix itself.

I dislike using one of the buttons for a fix for this though. I would think adding a widget/button to the lower right stack of route buttons would work well for this. (eg "Jump to next point" or "skip this point") It would also allow one to jump to a turn 3 or 4 ahead to trigger on too, and make "robo-phone" quiet during a sequence of turns one already knows well.

I like those options, and highly vote for a restore route on restart. Especially now that there's a top-level button for "clear current route".


Now for the bug list:

So over the holiday, I took modRana on a trip with me, about 800 miles round trip. I found a couple small bugs on the way, three of which were real problems:

1> Despite spending lots of time downloading tiles, when I was in an area that I know downloaded, local tiles were not used. If I turned off (or lost) GSM, I got the "download failed" tiles. And if I switched my data plan setting to "only vital info" I got a grey background. I even had wifi for one stop in the trip, and downloaded tiles for a 20k radius. It said it got all the tiles (and my free space dropped by 200M), but on starting it up and driving, I got the same thing. I have sqlite turned on, and the database files seem to be ok / intact and about the right size. Any ideas?

2> After some points I started getting an odd "blinking" when going over 50MPH. It seemed to happen when I was in an area where I only had GSM2.0 (not EDGE or 3G). The screen would draw, but then would go blank (no title bar or map or anything). The GPS would fall behind during this, and the whole device would become non-responsive. After I'd slowed (under 30mph) or stopped for a short time, it would return to normal.

3> The text in the box seemed to change size randomly, more based on how long the text was. In may cases it was so tiny as to be illegible unless looked VERY closely at the device. Thankfully I didn't have to rely on it much, since the voice announcements are now happening more frequently and with more fore-warning.

Of course, I was driving and didn't turn on debugging, so I have no logs for any of this. :P And I updated to 1.19 just before the trip, so it's the current version.

One more thing to check out: Not sure if modRana is hitting a processing wall (though it seems it may be). This may be something to check out to see if modRana could benefit from it. It compiles python code in to platform specific executable code, and can really speed things up. At least one other app on the N900 is using it.


Overall, this trip modRana really did a great job. Minus the tile cache issue, everything went well, and the announcments worked like a charm. (I love the warning a couple miles out btw, much better.)