Yeah seems my collegue has blocked some devices to avoid bad reviews.
We also have some api level defined Android 4.03 or higher.
I’ll get in touch with him tomorrow.
Sorry, I confused things here. I was not able to install on a Galaxy S1 (Android 2.3.6) but was able to install it on my S3. (I said to you S4 on the email, but it was on a S3).
Just wondering on this - is there a difference between the “official” S3 phones and the unofficial knockoffs? Has anyone managed to track this down to a particular phone with a particular CPU/GPU?
David
Sorry about the delay, but we have heard back from users since trying the “READ” permission fix. It does not fix our issue. Latest request for a refund is from a user on an S3. Any other ideas as to what this could be?
Hi Martijn,
Just curious, could you reproduce this via samsung’s remote test lab? If so, on what device/setup?
Frustrating that this issue does not seem to be getting any closer to a solution.
Thanks,
David
@playthisstudio.
It still happens, but dont waste your energy, I have been reporting this bug since more than one year and half ago.
I have reported it like 3 times.
Just wondering on this - is there a difference between the “official” S3 phones and the unofficial knockoffs? Has anyone managed to track this down to a particular phone with a particular CPU/GPU?
David