Database Users

Tasker

I had high hopes (very high!) that I could get tasker to run on the ouya, unfortunately I have not had any luck as of yet.
Maps was installed, as was a few files that needed to be manually installed in /system, but unfortunately neither seemed to work.
Has anybody had any luck? Please let me know if you did, I had big plans for this little system and tasker was a key piece to it.
Thanks.

Well, apparently I'm batting 1000 tonight on threads.
A reboot allowed instillation of the tasker trial version.
It looks like everything works, or as much as you would expect for the ouya. I did two test tasks. First was just a screen popup, which obviously worked great. The other was a reboot to test root access, and this also worked perfect (say hello to automated weekly reboots!).
Now, to see if autoremote can be made to work, and then on to autovoice or utter! and the inherently difficult prospect that will be.

Snoman002 said:
Well, apparently I'm batting 1000 tonight on threads.
A reboot allowed instillation of the tasker trial version.
It looks like everything works, or as much as you would expect for the ouya. I did two test tasks. First was just a screen popup, which obviously worked great. The other was a reboot to test root access, and this also worked perfect (say hello to automated weekly reboots!).
Now, to see if autoremote can be made to work, and then on to autovoice or utter! and the inherently difficult prospect that will be.
Click to expand...
Click to collapse
Please periodically update this thread with your progress? Curious to follow suit, though don't have the time to help in the investigations

A few issues with tasker itself, such as I can't download from Google play, it won't recognize my original order #, i can't find 'my' .apk, basically can't get my purchased version working and am stuck on the 7 day trial version. As for functionality it works great.
Current main task is to start XBMC if Autoremote received a certain message, as well as sending a message when xbmc is open and a different one when it closes.
On my tablet when I fire up the Yatse app, Tasker checks to see if XBMC is running, if not it displays a popup asking if I want to start xbmc. If I say yes it sends a command through autoremote which is what triggers tasker to start xbmc.

OK, a few things I have found.
Originally I could not download Tasker through the Play Store as the Ouya showed up as 'incompatible', however after a Play Store crash that removed it from my system, and subsequent reinstall, I can now download it from Google Play. I don't know why this was, but when I first did the play store mod I didn't have busybox installed, I did for the reinstall. I don't need the play version however as I was able to get the 'Trial' version validated, which is good as the direct download has added functionality (that I will never use). To validate the trial version you need to find the 15 digit order number (not the 16 digit Google provides in the email). This is best accomplished by using the 'Contact Crafty Apps' link in the email, and then finding Tasker, the 15 digit order number should then be visible. This only works if you bought Tasker before March 2013 though, otherwise you will need the Play store version (thanks Google :/)
To get Tasker to run you need to be Rooted and move two Google files to the proper location on the Ouya. Tasker will not run without the Google maps framework and oddly enough installing Google maps doesn't install the full framework. You can get these files by flashing the gapps package with CWM, or just install the two files themselves. To get the files unzip the gapps package, I think in the 'framework' folder. You need to move com.Google.android.maps.XML to /system/etc/permissions, and move com.Google.android.maps.jar to /system/framework. This WILL require you to remount /system as writeable. ES File Explorer worked for me (download an old version, 3.0.4 maybe, as the newest Play store version crashes), it was the only free root access file manager to work for me. Remount /system back to the way it was. BTW, I did all of this without adb, it was all done on the system itself with some help from dropbox (unzipped on my nexus, it was easier).
Tasker itself works great and I currently have it sending messages through autoremote to update variables on my other devices, this triggers a popup that asks if I want to start XBMC when I start my XBMC remote app (only if XBMC isn't running). If I select yes then it sends an Autoremote message that triggers a Tasker profile that starts XBMC. I also have Utter! setup to trigger the 'Start XBMC' Auto remote message on my Nexus
My next two tasks will be for an automatic nightly reboot, and a task that sends the Ouya into sleep mode when I start my alarm clock app on my nexus. I'm still trying to think of good ideas to implement. I hope to get a microphone working to use voice commands directly on the Ouya, and my dream is for an IR blaster to work so the Ouya could turn on my TV with voice commands (old TV)

Snoman002 said:
OK, a few things I have found.
Click to expand...
Click to collapse
Wow! I really commend you for your perseverance and willingness to share your experience and findings...people don't realize how much this helps others.

Scenes Working
Hey Snoman002,
I have my Ouya rooted and found a Tasker that can be used to mount and unmount NFS mounts. I have the two google maps files installed and have version 4.2 of Tasker installed. When i try to open the scene or even create a new one Tasker closes and goes back to the Make Menu. Have you seen a similar thing with the version you have been using ?
Thanks
Techhhead33

Techhead33 said:
Hey Snoman002,
I have my Ouya rooted and found a Tasker that can be used to mount and unmount NFS mounts. I have the two google maps files installed and have version 4.2 of Tasker installed. When i try to open the scene or even create a new one Tasker closes and goes back to the Make Menu. Have you seen a similar thing with the version you have been using ?
Thanks
Techhhead33
Click to expand...
Click to collapse
Sadly, other than getting it running initially I have done nothing more with Tasked on my ouya.
Your trying to make a scene in tasked? Scenes are really only for overlays and custom menus (drastic oversimplification I know). I fail to see the need for the complication of a scene just for mounting and unmounting. Perhaps you could change the tasker task to a simple popup menu (which now that I think about it may be a scene...). Popups worked for me, but that's all I can say about it.
Sorry, I'm not here much anymore as my ouya just runs xbmc now. I will try and check in more often.

Nova Widgets Still Possible (without ADB)?

Platform: Fire HD 8 (6th edition)
OS: 5.4.0.1
Willing to rollback?: Yes (it has broken some email functionality)
Launcher: Nova paid
I have activity launcher installed, as well as launcherhijack v3.
I have set the home screen button in accessibility, and have Nova enabled as the home. I have Nova enabled as the launcher, but have not deleted the fire launcher, as I would prefer not to.
The issue I'm having is that I can't seem to use widgets. I have read up on adb use for the fire, but Windows doesn't want to play nicely, and I don't currently have a linux machine available (yes, I could VM one, or setup a bootable USB, but I'm looking for a solution that would work with what I have currently in place).
Issue: Any time I go to place a widget on a Nova launcher screen, it brings up the list per normal, but when I go to place the widget, I get bounced back to the Kindle settings UI, and am unable to sort out a workaround.
Any suggestions would be appreciated, particularly if they don't require ADB, as so far Windows does not want to allow me to update the ADB drivers (it shows them as current stock drivers and functioning, as well as stating that the ones from google are a no-go).
Sadly, pushed the update when I did not expect it, so all of this was done after update rolled out. Play store was isntalled prior, and settings are for allowing debugging and developer settings, so at least I got the play store on prior to the update (which apparently some people are having issues with). For me, the store is working well, as is sideloading, which is why I'm thinking there must be a reliable solution to get widgets functioning in Nova without needing to ADB command it on.
Thank you,
--bb

No, you definitely need a working adb, it's your gate to all Fire HD hacks and improvements. If you can't - stay with Amazon bits and don't ask questions like this here.
Thanks to @DragonFire1024, we have a pretty nice hack to enable widgets on any launcher; it's very easy to apply and use. But PLEASE don't complain about prerequisites, if you can't get adb working on Windows, it's better to stay off all hacks and actually this site. Just enjoy your Amazon Fire HD (it's pretty cool even with OEM software installed).

Agreed! There is no need to be rude to those who are just learning. I appreciate those like Dragon who gives help to others without making them feel like idiots. With the help of this forum, I have gotten everything but gmail working! And that weird go to black screen and back to lock screen when I swipe application off the screen. An sure it will get fixed.

The widget script might work in a terminal emulator. Jack Pals on the play store is by far the best. Just search for terminal emulator for Android, place the script in the internal storage and try running it in the emulator. I honestly don't know if that will work though as all the hacks I do are usually with ADB.

DragonFire1024 said:
The widget script might work in a terminal emulator. Jack Pals on the play store is by far the best. Just search for terminal emulator for Android, place the script in the internal storage and try running it in the emulator. I honestly don't know if that will work though as all the hacks I do are usually with ADB.
Click to expand...
Click to collapse
Thank you! I will give that a try.

Let's try to keep the comments directly related to Q&A for this device.
Getting snarky with other users and starting a back and forth argument is off-topic, and usually rude (both violations of the rules).
So, please; keep the Off-topic back and forth off the thread. If you are offended by, or feel another user's comment violates the rules, simply REPORT the comment and do not engage the other user further. No need to add MORE clutter.
Thanks for your cooperation.

sensboston said:
No, you definitely need a working adb, it's your gate to all Fire HD hacks and improvements. If you can't - stay with Amazon bits and don't ask questions like this here.
Thanks to @DragonFire1024, we have a pretty nice hack to enable widgets on any launcher; it's very easy to apply and use. But PLEASE don't complain about prerequisites, if you can't get adb working on Windows, it's better to stay off all hacks and actually this site. Just enjoy your Amazon Fire HD (it's pretty cool even with OEM software installed).
Click to expand...
Click to collapse
Can you please explain to me how I can update the ADB? I'm not familiar with how to do this at all.

https://www.xda-developers.com/install-adb-windows-macos-linux/

Yeah, but...
bladebarrier said:
https://www.xda-developers.com/install-adb-windows-macos-linux/
Click to expand...
Click to collapse
This is where I started, but I have been unable to find a way to find anything mentioning ADB (much less enable it) on our Fire HD 8 (7th Generation).
I have been looking through multiple guides for the past 20 minutes, but the newest firmware seems to have hidden or disabled the ability on the actual device. I am logged into the tablet on the main account, but even under "Device Administrators" it says "No available device administrators".
Did Amazon manage to lock these down to be nothing but a pimp for Amazon (as was their intended goal)?
Edit: Fire OS 5.6.1.0

Did Amazon manage to lock these down to be nothing but a pimp for Amazon (as was their intended goal)?
Yes, they did. It's the razor and blades business model. Such as one item is sold at a low price (or given away for free) in order to increase sales of a complementary goods.
When you go into the Setting then into Device Options, is Developer Options at the bottom of the list? If it isn't I think you need to tap the Serial Number 7 times, then it should appear and that is where you can enable ADB.
The dedication of the members of the xda forums are the only reason why a lot of devices such as these manage to reach their potential. I'm pretty new here (joined in February) but I never seen any member give up on a device. What most see as frustration, including myself, a lot of the members here not only see a challenge but an opportunity.

caldersm44 said:
Agreed! There is no need to be rude to those who are just learning. I appreciate those like Dragon who gives help to others without making them feel like idiots. With the help of this forum, I have gotten everything but gmail working! And that weird go to black screen and back to lock screen when I swipe application off the screen. An sure it will get fixed.
Click to expand...
Click to collapse
For now without a rooted device the kick to the lock screen cannot be fixed. That is an unfortunate event which is a result of disabling fire launcher without root. Gmail is give or take. Sometimes it works and sometimes it doesn't. If I really had to take a guess I would say Google and Amazon are fighting between each other to get Gmail to work or stop working. It seems when enough users complain Gmail stops working within a few minutes it works again in a couple days later Amazon stops it. I would go back to an old version of Gmail, take your pick and keep trying different versions from there. If he older versions don't work that I'm at a loss at the moment. I do not currently use Gmail on my Amazon tablets. Only because I get too much mail lol. however with that having been said I have never had a problem with Gmail on any of my Amazon tablets with or without root.

dondraper23 said:
Did Amazon manage to lock these down to be nothing but a pimp for Amazon (as was their intended goal)?
Yes, they did. It's the razor and blades business model. Such as one item is sold at a low price (or given away for free) in order to increase sales of a complementary goods.
When you go into the Setting then into Device Options, is Developer Options at the bottom of the list? If it isn't I think you need to tap the Serial Number 7 times, then it should appear and that is where you can enable ADB.
The dedication of the members of the xda forums are the only reason why a lot of devices such as these manage to reach their potential. I'm pretty new here (joined in February) but I never seen any member give up on a device. What most see as frustration, including myself, a lot of the members here not only see a challenge but an opportunity.
Click to expand...
Click to collapse
Thanks for the reminder of how to enable Developer Options - it has been a while since I had to do that. ADB is now enabled!
Thanks to everyone in the xda-developers community!

AnotherNameFFS said:
Thanks for the reminder of how to enable Developer Options - it has been a while since I had to do that. ADB is now enabled!
Thanks to everyone in the xda-developers community!
Click to expand...
Click to collapse
Glad you got it enabled! It's one of those steps that is easy to forget

Why are you saying that he should get off the site. Thats rude

NO ROOT REQUIRED: Completely disable and enable your lock screen

Many of us don't have root and many of us also uninstalled may system apps, including Fire Launcher. That left us with some annoyances. One major annoyance was being kicked to the lock screen whenever we swiped away apps from the recent apps menu. Some people saw annoying flashes. Well this isn't quite a fix, but it pretty much takes care of the problem. You can now remove your lock screen completely and replace it at will and you do NOT need root access.
***WARNING: Touching any other settings on your tablet during this guide can cause a brick!!!***
1. Download and install Settings Database Editor.
2. Plug your tablet into your PC and open an ADB window. Enter the following:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Step number 2 MUST be done in order for this to work.
3. Open Settings Database Editor and tap on the 'secure' tab at the top.
4. These settings are in alphabetical order. Scroll until you see:
Code:
"lockscreen_disabled" "0"
5. Change the 0 to a 1. DO NOT CHANGE ANYTHING ELSE
6. Close Settings Database Editor
Now turn off your screen. Now turn it back on. You are welcome! I have a few more tricks coming. Watch for some later!
IF THE ABOVE DOESN'T WORK, TO DISABLE LOCK SCREEN:
Code:
adb shell settings put secure lockscreen_disabled 1
ENABLE LOCK SCREEN:
Code:
adb shell settings put secure lockscreen_disabled 0

Both methods don´t work on my Fire HD10 2017.

tommes-d said:
Both methods don´t work on my Fire HD10 2017.
Click to expand...
Click to collapse
It worked almost instantly for me. Maybe wait a bit? Did you reboot? It won't work on every device. Doesn't work on my Galaxy S7.

Not working for me too (Fire HD 8 2016). Also, you've made a mistake: original setting name is "lockscreen.disabled" (dot, not an underscore).

sensboston said:
Not working for me too (Fire HD 8 2016). Also, you've made a mistake: original setting name is "lockscreen.disabled" (dot, not an underscore).
Click to expand...
Click to collapse
Disappointing. Today I got a good one though. I can't wait to get home and post a thread.

I know this isn't the correct forum for this but I tried this on a Fire 7 (2017) and it also does not seem to work.

is there an updated way to do this?
is there an updated way to do this?
edit: kindle fire 8 7th gen, confirmed not working.

Doesn't work on my Fire HD8. But while browsing through Settings Database Editor I have found something useful.
In the "Global Table" tab there's a setting called LOCKSCREEN_AD_ENABLED. Change the value from 1 to 0, save. Turn off screen, turn it on again --> ads are gone!
At least for a while...

Seems to be working on KFAUWI (Fire 7 7th Gen) on 5.4.0.0.
EDIT: Maybe it doesn't work with 5.4.0.1 and later?
It would be useful for those reporting success/failure to include not just device model, but fw version as well.
EDIT1: After some time playing around the system I have found out that by default it actually does not work, but if Global Table->"device_provisioned" = 0 then lock screen gets disabled, but serial number gets greyed out and developer options get disabled, while adb remains functional.
On 5.6.0.0 even change to "device_provisioned" did not disable the lock screen.

gabosius said:
Seems to be working on KFAUWI (Fire 7 7th Gen) on 5.4.0.0.
EDIT: Maybe it doesn't work with 5.4.0.1 and later?
It would be useful for those reporting success/failure to include not just device model, but fw version as well.
Click to expand...
Click to collapse
There are settings in the "private" class that override some of these lower ones, usually in favor their using their own software. I think most device stock settings are hidden for the purpose of favoring their own software. Though with Amazon, I scratch my head. Why spend the large amount of money, to install a high tech, customizable GPS system on devices, only to spend more money carelessly blocking your Access?
Sent from my Samsung Galaxy S4 using XDA Labs

DragonFire1024 said:
There are settings in the "private" class that override some of these lower ones, usually in favor their using their own software. I think most device stock settings are hidden for the purpose of favoring their own software. Though with Amazon, I scratch my head. Why spend the large amount of money, to install a high tech, customizable GPS system on devices, only to spend more money carelessly blocking your Access?
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
That's fairly simple, the same goes for one of the iPhones (don't recall which gen exactly) which had two different models of radio chips, one of which did support LTE, but Apple decided to disable LTE support for that gen of the phone altogether.
Now more on the topic, checked the specs of all 7th gen tablets, indeed none of them seem to support GPS officially (for some reason I thought that HD8/HD10 might have it), but if they have the hw, it could be for testing purposes to test proprietary GPS related sw on development devices before introducing it in the next gen? Or simply they decided to drop it somewhere along the way but left the hardware (as we still have Serial/UART on some production devices nowadays, which are used only for debugging in the development stage).
On the other hand, where did you get the info that it actually has GPS related hardware? Because while exploring my device settings I only found a hint on A-GPS support (which is not proven).

gabosius said:
That's fairly simple, the same goes for one of the iPhones (don't recall which gen exactly) which had two different models of radio chips, one of which did support LTE, but Apple decided to disable LTE support for that gen of the phone altogether.
Now more on the topic, checked the specs of all 7th gen tablets, indeed none of them seem to support GPS officially (for some reason I thought that HD8/HD10 might have it), but if they have the hw, it could be for testing purposes to test proprietary GPS related sw on development devices before introducing it in the next gen? Or simply they decided to drop it somewhere along the way but left the hardware (as we still have Serial/UART on some production devices nowadays, which are used only for debugging in the development stage).
On the other hand, where did you get the info that it actually has GPS related hardware? Because while exploring my device settings I only found a hint on A-GPS support (which is not proven).
Click to expand...
Click to collapse
Add a few .xml configuration files to start and there is configuration settings in the framework. Look for an app on the tablet with HERE in all caps in the title. That's the APK module making it possible. And yes I figured out a way to modify framework settings

DragonFire1024 said:
Add a few .xml configuration files to start and there is configuration settings in the framework. Look for an app on the tablet with HERE in all caps in the title. That's the APK module making it possible. And yes I figured out a way to modify framework settings
Click to expand...
Click to collapse
I see, just checked MT8127 specs, and indeed there seems to be integrated support for GPS with GLONASS, that may be something interesting to play with.
EDIT: HD8/HD10 even have broader support of GPS related technologies according to their SoC specs.
Yeah, I was following root progress thread, even tried Blueborne exploit (the one published by Armis labs on github) on KFAUWI without much success as there is no access to /proc/<pid>/maps. And framework-res.apk mod looks promising only for devices having root, as getting required permissions outside /system is rather problematic.
Yet I was surprised that WRITE_SECURE_SETTINGS can be assigned outside /system. As I was poking around com.amazon.dcp.permission.DISPLAY_DEBUG_UI for quite some time.

gabosius said:
Yet I was surprised that WRITE_SECURE_SETTINGS can be assigned outside /system. As I was poking around com.amazon.dcp.permission.DISPLAY_DEBUG_UI for quite some time.
Click to expand...
Click to collapse
Do you have any idea if you can grant something like Activity Launcher the DISPLAY_DEBUG_UI permission? Some of the activities gave me errors when I tried to open them, saying they require com.amazon.dcp.permission.DISPLAY_DEBUG_UI.
The thing is, this appears to be a custom permission added by Amazon, not available in the official Android documentation.
Would Activity Launcher even be capable of launching certain "hidden" activities with this permission granted? Presumably you would grant permission over ADB the same way as WRITE_SECURE_SETTINGS?
Any ideas would be great.

lakitu47 said:
Do you have any idea if you can grant something like Activity Launcher the DISPLAY_DEBUG_UI permission? Some of the activities gave me errors when I tried to open them, saying they require com.amazon.dcp.permission.DISPLAY_DEBUG_UI.
The thing is, this appears to be a custom permission added by Amazon, not available in the official Android documentation.
Would Activity Launcher even be capable of launching certain "hidden" activities with this permission granted? Presumably you would grant permission over ADB the same way as WRITE_SECURE_SETTINGS?
Any ideas would be great.
Click to expand...
Click to collapse
Tried granting it to other apps and it resulted in "com.amazon.dcp.permission.DISPLAY_DEBUG_UI is not a changeable type" the command I used was pm grant com.amazon.dcp com.amazon.dcp.permission.DISPLAY_DEBUG_UI so yes, the syntax is the same with custom amazon permissions. Also execution of dumpsys package com.amazon.dcp shows that app already has DISPLAY_DEBUG_UI permission.
My guess is that it requires root, as even when I am launching activity from adb shell (not in context of activity manager) I get the same error that it requires the permission, and the same goes for some other hidden amazon applications.
EDIT: you can get list of device permissions by executing "pm list permissions" without quotes from adb shell, there are at least a few interesting ones.

lakitu47 said:
Do you have any idea if you can grant something like Activity Launcher the DISPLAY_DEBUG_UI permission? Some of the activities gave me errors when I tried to open them, saying they require com.amazon.dcp.permission.DISPLAY_DEBUG_UI.
The thing is, this appears to be a custom permission added by Amazon, not available in the official Android documentation.
Would Activity Launcher even be capable of launching certain "hidden" activities with this permission granted? Presumably you would grant permission over ADB the same way as WRITE_SECURE_SETTINGS?
Any ideas would be great.
Click to expand...
Click to collapse
That's a great question and one that hasn't been asked before. I can tell you I've been able to, in some apps, modify the manifest permissions. For example, I can use an app to edit the manifest of Jack Pals terminal emulator to add the secure settings permission and have it successfully install etc. I never thought of doing the same with activity launcher and if successful, seeing what happens. This could be very interesting. If you give me a few copies of some of the manifests permissions, I can see if a recompile and install will hold.

DragonFire1024 said:
That's a great question and one that hasn't been asked before. I can tell you I've been able to, in some apps, modify the manifest permissions. For example, I can use an app to edit the manifest of Jack Pals terminal emulator to add the secure settings permission and have it successfully install etc. I never thought of doing the same with activity launcher and if successful, seeing what happens. This could be very interesting. If you give me a few copies of some of the manifests permissions, I can see if a recompile and install will hold.
Click to expand...
Click to collapse
I attached a text document with ALL of the permissions listed by "pm list permissions" since it was too long to put here.

lakitu47 said:
I attached a text document with ALL of the permissions listed by "pm list permissions" since it was too long to put here.
Click to expand...
Click to collapse
Give me a few hours to see if I can modify the app. If I can, I'll upload a. APK
Sent from my Samsung Galaxy S4 using XDA Labs

DragonFire1024 said:
Give me a few hours to see if I can modify the app. If I can, I'll upload a. APK
Sent from my Samsung Galaxy S4 using XDA Labs
Click to expand...
Click to collapse
Questionable whether anything would change, as I don't see where activity launcher would need write secure settings permission.
On the other hand I did some digging on the "not a changeable permission type" message, and this provides some answer on what it might be expecting in order to activate?/assign the permission.

gabosius said:
Questionable whether anything would change, as I don't see where activity launcher would need write secure settings permission.
On the other hand I did some digging on the "not a changeable permission type" message, and this provides some answer on what it might be expecting in order to activate?/assign the permission.
Click to expand...
Click to collapse
Interesting. So each permission has a certain "protection" level?

Ideas to enable multi-user support

At my job, I have been tasked with finding a cheap way to replace some paper forms with a digital equivalent. I have a Fire HD 10 7th gen, and since they inexpensive, they seemed like a good fit to accomplish this. I'm in the final stages of this prototype - if all goes well we would order a bunch to distribute to employees.
Using tutorials and guides from this forum (thanks!), I have rooted the tablet and stripped out the amazon bloatware, replaced the launcher, and now have a fairly bare bones tablet. Basically we only need email, calendar and something to open spreadsheets.
I am now trying to figure out a way to set up multiple users on each tablet. Amazon replaced the native user accounts with their own version for 'households'. You can have two 'adult' profiles and 4 'child' profiles and must be linked to an amazon account. The adult accounts function exactly like regular android user profiles, so the underlying features are there, I just need to remove the two adult limit, and be able to add them without having to set up an amazon account.
What I have tried:
1. Adding profiles while offline, still get prompted to log into amazon.
2. Tried to edit the build.prop file and included these lines
fw.max_users=3
fw.show_multiuserui=1
This did not seem to have an effect
3. Via an adb shell, I tried
adb shell pm create-user TEST
This produces the error:
Error: Unable to perform this action on production builds
4. I thought this might be a root issue, so I installed adb insecure. The command above still failed.
Is there anything else I should try? Is it possible to restore the original user manager from stock android? Is there a 3rd party user manager that I could use? More drastically, can change the build from production to something else, so that the create-user instruction is available? Obviously, the amazon user manager is able to trigger the creation of a new profile, so it must be using some other mechanism to accomplish the same thing.
Any help would be greatly appreciated!

You must be modify the framwork-res.apk

[Q] Fire HD8 (2018) w/ Play Store - app recognises it isn't Google, won't run.

The tablet is owned by someone else and they want to use one app called Landscape Magazine. On the Nexus 7 it runs fine but the battery just went on it and I'm having issues sourcing a replacement battery in the UK so that's where the HD8 comes in. I thought I could just put the Play Store on (plus framework etc) and it would be ok for them. It downloads the app fine, all others work fine but when I try to launch this one app it says it only works on Android tablets. I don't know why they'd code it that way but it is what it is.
Can anyone tell me if there's some way to get an app to run if it's throwing up an error like this?

Dyonas said:
The tablet is owned by someone else and they want to use one app called Landscape Magazine. On the Nexus 7 it runs fine but the battery just went on it and I'm having issues sourcing a replacement battery in the UK so that's where the HD8 comes in. I thought I could just put the Play Store on (plus framework etc) and it would be ok for them. It downloads the app fine, all others work fine but when I try to launch this one app it says it only works on Android tablets. I don't know why they'd code it that way but it is what it is.
Can anyone tell me if there's some way to get an app to run if it's throwing up an error like this?
Click to expand...
Click to collapse
Not easily. It would take experimentation to determine which device or rom characteristic(s) are trigging the behavior followed by additional fiddling to entice the app to run. Tethering that Nexus 7 to a slim power bank may be the best solution.

NEED ROOTED.
/system/build.prop
ro.product.brand = Amazon
ro.product.manufacturer = Amazon
Change to 'Google' or etc.
I think amazon is banned by the app.

The exact error message is "This app is only suitable for the Android platform."
Didn't see the pictures attached by @erono. If you root the tablet (or may be possible in temp root shell) and change the keys he mentioned, the app works after reboot.

Thanks all for replying, especially erono who seems to have found the solution. I'll see what I can do with it because my understanding is that there is still no major Android build for the 2018 HD8. I have a starting point if nothing else and that's more than I had before!

Dyonas said:
Thanks all for replying, especially erono who seems to have found the solution. I'll see what I can do with it because my understanding is that there is still no major Android build for the 2018 HD8. I have a starting point if nothing else and that's more than I had before!
Click to expand...
Click to collapse
You could always root it and just edit BuildProp (excellent guide by bibikalka) . As far as other ways, I'm not knowledgeable enough to know any alternatives. Maybe without root, you might be able to pull BuildProp from the elevated shell and push it back after changing the lines. I'm sure there would be some permissions changes required. Hopefully someone with a bit more experience pops in and can guide you if rooting isn't an option.

nujak said:
You could always root it and just edit BuildProp (excellent guide by bibikalka) . As far as other ways, I'm not knowledgeable enough to know any alternatives. Maybe without root, you might be able to pull BuildProp from the elevated shell and push it back after changing the lines. I'm sure there would be some permissions changes required. Hopefully someone with a bit more experience pops in and can guide you if rooting isn't an option.
Click to expand...
Click to collapse
No need to modify build.prop nor will any notable gains be realized by doing so. Simply follow the guides as written.

Davey126 said:
No need to modify build.prop nor will any notable gains be realized by doing so. Simply follow the guides as written.
Click to expand...
Click to collapse
Yeah, sorry I meant in specific context to having that particular app work on the HD 8 2018. Thanks to @erono (and testing it myself) Lanscape Magazine works with changing brand and manufacturer values in the BuildProp. I know it's possible and easy to do with root. I'm just not knowledgeable enough to know any other methods.

Method without root:
Use 'App Cloner (pro version)' create an cloned app.
You can modify MANUFACTURER and BRAND in 'Developer options -> Build props'.
App was modified, you can't update in Google Play Store or purchase any paid content.
This is not a good way.