Izzy

@Primokorn Yes. And yes, as the Android version will also be taken from the `build.prop` it will reflect the version actually used on your device – and not be fixed...

Then it might be the app really is incompatible with your device. Maybe check with the dev, something might have changed in the app's definition. If the dev tells you...

@mar-v-in certainly cannot hurt if _microG_ ships its own tool for that. As for _DummyDroid,_ the [sources are available at Github](https://github.com/onyxbits/dummydroid). It reads all data from the `build.prop` you offer...

Are you using the latest version of BlankStore (v0.7.5 currently)?

@tecufanujacu Ah, OK – that's a different case then. A (pastebin'd or attached) `logcat` might prove helpful then. As I wrote, I'm using the _DummyDroid_ generated ID without any issues....

Raccoon is what I'm using as well meanwhile. Still there's one remaining issue neither Raccoon nor Blankstore can solve: if such an app wants to verify its license, it will...

If you read the description on the [FakeStore page](https://github.com/microg/android_packages_apps_FakeStore), you will note the difference: > An **_empty package**_ that **_mocks the existence of the Google Play Store**_ to the Play...

To be honest, @breversa, I didn't check deeper into _FakeStore._ I'm still using _BlankStore_, so I saw no need to install the other (but there certainly is one if you...

> (The only missing thing is a date, to quickly check the relevancy level in the future) Check the end of the page. It's either one date (article created), or...

@mar-v-in especially with F-Droid, signatures will never match (and thus, without something "ignoring signatures" like an appropriate Xposed module), updates from another source would fail anyway. How about an option...