Valkyrie: Valkyrie apk for Kindle Fire 10 HD 2017?

[dalembraun]

Any chance the android apk might be made compatible with Kindle Fire 10 HDs? I can sideload it onto my Kindle Fire 10 HD 2017 (2nd Gen), and it launches. It shows the Unity splash screen, then gets to the first menu (choose which game you want to use), but none of the items are active because Valkyrie can't find the install directory. Since this tablet allows the use of both SD card storage and internal storage, I've tried having Mansions of Madness installed on the SD card and on the internal storage, but neither install method helps. MoM launches just fine; Valkyrie also launches, but cannot find install files.

[dalembraun]

if this helps, it appears that the MoM install area might be in /sdcard/Android/data/com.fantasyflightgames.mom (/sdcard being the internal storage area of the tablet, which is a redirect from /storage/sdcard0), and /storage/sdcard1/Android/data/com.fantasyflightgames.mom for the plugin SD Card.

[NPBruce]

Valkyrie is looking for a file ending in ".com.fantasyflightgames.mom.obb" which is located in \

However I am not sure if the Kindle version even uses obb files as these are a play store thing. Do you have any obb files on your device? If not are there any single large (hundreds of MB) files you have associated with an FFG app?

[redwolf2]

https://developer.amazon.com/de/docs/app-submission/understanding-submission.html

Binary blobs (.obb) are not supported by the Amazon Appstore, so it is up to the developer to install external resources in the proper path after downloading them at runtime, and to submit an APK compiled without .obb files.

As suggested by bruce. The amazon app store is probably using a single apk file or maybe there is an alternative way of sideloading the data with the amazon store deployed apps.

You can uninstall the Amazon store version of Mansions Of Madness. Download and install Google Play and download the official Mansion Of Madness app from there. That should also work. Maybe the Amazon and Goolge Play versions can both be installed next to each other, if you have concerns about already purchased dlc.

https://www.youtube.com/watch?v=XrPRv3DHZJI
https://www.howtogeek.com/232726/how-to-install-the-google-play-store-on-your-amazon-fire-tablet/

You may also be lucky with just downloading and placing the obb in the right folder:

Try this: https://www.apk4fun.com/apk-obb/181219/

Let us know what worked out for you.

[dalembraun]

I installed the obb in the folder per the apk4fun.com info, and now I have the import content option. That's further than I've gotten before! And I believe it's successful in importing in the content, since I can now download the scenarios. I'll experiment with it a bit further, but I think y'all are amazing! Thanks so much!

[redwolf2]

I added a guide here: https://github.com/NPBruce/valkyrie/wiki#fire-os

[dalembraun]

Had a chance to play with my Fire. Works great with the above info (copying obb to correct location). I think that some of the issues I had with certain MoM Scenarios are probably related to the scenarios themselves. Things like some buttons having long menu names, or empty buttons/text windows, or flipping between english and french. It could also be due to not actually playing the scenarios, but just clicking through all the explores, searches, etc., just to see if it'd crash.

I also tried the option of having MoM installed on my SD Card by using the Fire Storage option to move the App to the SD card, and it still ran with the obb on the internal storage.

From what I've seen, you provided the solution! I'm willing to call this closed.

[NPBruce]

If any developers want to find a better solution for FireOS, I am open to pull requests.

[dalembraun]

Thanks again for the fast response. I plan on hosting three MoM games at a local convention and I wanted to highlight the user-made scenarios.

Sent from my iPhone

On Apr 3, 2018, at 4:31 PM, NPBruce [e-mail] wrote:

If any developers want to find a better solution for FireOS, I am open to pull requests.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

[NPBruce]

By mindful that the mobile version is not a final release. People have reported less issues with 1.7.0b than 1.7.0c, something to consider.