The thread on my blog post is getting a little unmanageable. How about we discuss test results here instead...
I'll also post release notes as new builds are out. The device must support 'USB host mode' (most devices running android 3.1 or later are fine). You'll need a 'OTG' adapter such as this
Please post feedback here or on the github issues site - the google play comments are not really useful yet.
Hi ya'll. Please move further discussion of this app to a newly created group:
Feel free to make new approprately titled discussion threads.
Future app releases will be announced only there.
That is what YOU collect. You have no control over what Flurry collects. They offer targeted advertising, so it is very likely that their library collects much more.
Flurry uses the device's IMEI and that is per definition a personally identifiable information. Especially the IMEI tracking makes Flurry so dangerous for privacy because Flurry does not only collect data through their library - it all starts with Flurry knowing every Flurry-using-app on my device, which itself already makes a very interesting set of data for advertisers, because it tells all my interests.
Actually - I don't give Flurry permission to see the IMEI (you can verify this by looking at the andropilot permissions in settings or the market). You'll see there is no access to "get identity of this phone" (I forget the exact name).
Flurry _will_ track unique users via IMEI if given such access, but Andropilot doesn't allow that. Does this address your concern? The anonymized reporting we use is really useful, because it gives good information on how the app is used and typically I fix a couple of auto reported bugs a week - bugs the user never even knows occurred.
I could also add a checkbox to allow flurry, but as we use it it doesn't seem to violate any privacy I'm aware of.
Here's the permission I specifically don't request:
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
I just read up on the ID thing. If it can't get the IMEI, Flurry seems to read Secure.Android_ID which is as unique as the IMEI and as much makes the user identifiable, especially through the market. As far as I could find, no special permission is needed to read that but I'm a bit short on time to research.
Just to make it clear - I'm not proposing that YOU are spying. I am critically looking at the usage of Flurry, because as a provider of targeted advertising they have a raised interest in collecting data about users.
No problem. I can add a checkbox to allow the user to disable flurry. Cool? Though at best the only data they can get from andropilot is a unique ID which is not linked to any sort of user name or account.
I'd also accept a pull-request with change to any of the other instrumentation libraries.
That sounds like a good solution :).
ok - no problem - will do.
How do I prefetch map files? Or do I require a internet connection out in the field?
This being asked, my proposed offline mapsforge inclusion would be a solution. Any news on this Kevin?
I looked into it a bit and I think this one will be a while (in addition to switching to mapsforge I'd also need to make a UI to predownload map tiles)
alas - prefecting kinda works in google maps but isn't guaranteed. I normally just tether my tablet to my phone via wifi and use the phone's internet to get out.