Thanks for getting back, also Hannah replied soon after I posted with the same message. Hopefully you can host the current version file on your website at some point.

I will also get back to Google as they aren't being consistent if waht you say is correct. I have another tablet without built in GPS and Play Store makes Skydemon available to that device.

I suspect there is not a resolution to this issue for you. There is no setting that we set to tell Play Store which devices SkyDemon will run on. There is no such thing as installers for Android apps. All there is, is a list of permissions we have to ask for including the GPS permission otherwise SkyDemon wouldn't be able to receive location data (which is obviously critical). I suspect that the Play Store sees this permission and decides that devices which don't have GPS shouldn't be shown apps that require GPS permissions. It's an imperfect system and not one we're able to do anything about.

I have sympathy with the idea of also hosting the latest version on our website, that might be something we can implement later this year. If it helps, the forthcoming 3.1 release will barely have changed between the current beta and release. That's the nature of a beta system.

I already did give Google's response to Hannah, who said I needed to contact Google as it was my problem.

"According to our records, the app you're referring to is not compatible with your device because your device is missing a GPS feature and so it won't be advertised to you in Google Play.

App compatibility is determined by individual app developers, not by Google Play, so I'm afraid I can't help further - I can't change the requirements this developer has set for their app.

That being said, I'd recommend contacting the app developer directly to see if they plan to expand compatibility in the future or if they have other options for your device. "

As the Beta direct download works fine there would appear to be no reason for the "GPS feature" Google say is the issue.

Hope this helps.

If the settings can't be changed how about having a permanent download page in the Customer area of SkyDemon?

We require no more permissions than are absolutely necessary:

Internet
WriteExternalStorage
AccessFineLocation
AccessCoarseLocation
AccessNetworkState

To my knowledge, it is these and only these which the Play Store uses to determine whether an app is compatible with your device. I am happy to be corrected with a specific setting that I'm not aware of, but you really will need to be specific. Perhaps you could share your response from Google with us?

This Beta works fine on a HiSense Sero8. Just one cosmetic bug, when you stop naviagting  and return to route planning screen the virtual radar section below the chart is just black.

Please do keep the geo-referencing feature - and put some pressure on AFE to bring their plates up to date!

An annoyance, which your support people seem to have stopped replying to me about despite me checking with Google as requested and proving it is a developer issue, is that the Play Store installer settings include a GPS feature that my tablet doesn't have so Google shows it as non compatible with my device. Clearly it isn't a required feature as the Beta works on the tablet with an external GPS receiver and mock locations enbled. Hopefuilly when 3.1 is released this will be resolved.

Shame, but thanks for the info. 

Ah. That's a prototype from back when we investigated the possibility of georeferencing IFR plates. Enjoy them while you can, but we currently have no plans to georeference IFR approach plates which would be a HUGE amount of work for us to do when only a tiny percentage of our subscribers would benefit.

The answer to your question, I believe, is that IFR plates are not candidates for automatic loading.

If I try to display the georeferenced plate for LOWZ on my PC it takes ages to download and then several minutes to render even on a PC. I think it may be a very complex or faulty PDF file that is taking a VERY long time to render on Android devices. Just tried it on Android (Nexus 7) and can replicate what Herbert is seeing.



I have IFR approach plates enabled and in addition to the above I have available two georeferenced IFR approach plates for Cambridge (ILS/DME/NBD RWY 23 and RNAV(GNSS) RWY 23). This is fantastic having georeferenced IFR plates.  I was just wondering how SkyDemon chooses which plate to auto-display on approach when there is more than one?

Edit: Gloucestershire and Carlisle also have georeferenced IAPs

Herbert, it sounds like plate rendering simply isn't working on your device. Unfortunately there isn't an easy way for us to determine what is wrong, though we will add some debugging/reporting functionality to the final version of 3.1 to help us diagnose.
Simon, there are only two georeferenced plates for Cambridge and they're both airfield diagrams. IFR plates are not georeferenced.

When approaching an airfield (e.g. EGSC Cambridge) how is the auto-displayed approach plate chosen when there are several available such as different runways and approach types?