Maybe you should provide an alternative "driver" based on a service like geonames.org. Their address database is free to use (with content attribution). Only downside is that they have a daily usage limit which must not be exceeded unless you pay for some premium access.
However, if that problem just occurs with a fraction of your users you could run that workaround only on their particular devices. You could let the user decide which driver to use (native one or geonames). On Friday, February 1, 2013 11:15:56 AM UTC-6, Franklin wrote: > > This problem still bugs the hell out of me. I have written an obscure > workaround that doesn't work 100% of the time, and it really bugs the hell > out of my users (I have about 500,000 active users) as well. -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
