Comment 8 for bug 579466

I spent some time making some fixes to osmdroid for this issue, and although I wouldn't go so far as to say it's fixed, I haven't had this error for quite a long time. Maybe that doesn't directly help you, but I'm just hinting that if you look at the code then there's a good chance you're on a good track. You could also just try using the new jar version of osmdroid directly.

This comment relates to the stack trace in the description. I don't know anything about the things mentioned in the comments.