But the app needed us to go to an Android device’s settings, not a Fire device’s settings. But the second an app requires something a bit more, lets say proprietary, we get a situation like this: the app seems to run, up to a point, where it suddenly just abandons us in the system settings because that’s where the app told it go to do something. Since Fire’s OS was based on a version of Android, compatibility has always been matter of “it just happens to do enough of the right things to either run, or not crash.” There’s enough similarity between the two to get quite a bit of use out of Play Store apps on a Fire device, especially if we’re talking Google Apps since their folder names, structures, and etc would be very similar if not outright identical. The fact that you successfully installed the Google Play Store and other Google Apps is frustratingly just more evidence that this is the situation. Fire’s OS has something similar to what Duo is looking for, hence the permissions loop and why it doesn’t just outright crash, but the similarities stop at that folder level and the actual setting or command it needs is nowhere to be found, so it just leaves you there. And this is most likely by design, in the sense that the app is trying to access some function or setting that doesn’t exist in the OS. If it’s a permissions issue, or anything related to how it interacts with the device’s OS, then I think you’re out of luck here.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |