OK... so it looks like when the app is initializing (on my device) it can't find the libraries for the FMOD platform-independant audio libraries.
What's a quick and easy way for me to get these libraries installed back onto this device that I could perhaps invoke from Google Play Store?
Which folder should the fmodex.jar file be residing in... in order for the app to be able to see it and load it in on startup?
Inspecting logs during startup attempt of MCPE the following lines caught my eye:
D/dalvikvm( 2201): Added shared lib /data/data/com.mojang.minecraftpe/lib/libgnustl_shared.so
D/dalvikvm( 2201): No JNI_OnLoad found in /data/data/com.mojang.minecraftpe/lib/libgnustl_shared.so ... skipping init
D/MCPE ( 2201): OVRfmod library not found
D/MCPE ( 2201): OVRPlatform library not found
D/dalvikvm( 2201): Trying to load lib /data/data/com/mojang.minecraftpe/lib/libfmod.so
D/dalvikvm( 2201): Added shared lib... <the same one>
D/dalvikvm ( 2201): Trying to load lib /data/data/com.mojang.minecraftpe/lib/libminecraftpe.so
F/libc ( 2201): Fatal signal 4 (SIGILL) at <such and such address> (code=1)
.
.
.
then a bunch of I/DEBUG messages for process id (82) which are about pid 2201
.
.
then..
V/NvAudioALSA (86): Closing ALSA device!, curDev 0x2, curMode 0
I/BootReceiver (143): Copying /data/tombstones/tombstone_03 to DropBox (SYSTEM_TOMBSTONE)
Could this be some kind of scenario where a different version of a common shared library becomes installed into the Andriod device by another vendors software and messes isht up? Much like "DLL-Hell" in Windows?
Why is it telling me OVRfmod library not found? and OVRplatform library not found?
Could it be that needed components are not being deployed into your installer app?
I doubt it's an issue of RAM. He can run Clumsy Ninja and it's file size is like twice as big as MCPE. Monster Dash by HalfBrick is also greater in size. Plus, when I went thru his device I went to town and yanked everything that didn't look like any of the apps I know he uses with any regularity. Indeed there were multiple MCPE add-on mod apps though. As I said before, I specifically went thru and yanked any and all of those.
But... if there is the possibility that the uninstalls leave behind files that might affect this issue... that was why I asked if the support staff would be so kind as to post up a doc showing which folders to look for and wipe-clean, I'd be more than happy to do so. If requested, I'd even document any findings in them, if they felt it might help ID whats the cause.
"Do it for the kids man, do it for the kids!". Support staff... please understand this issue is depriving all these kids of one of their favorite past-times.
Big thanks to Nat Thomas for noting which was last version to work. Hopefully then can look at their Build/Revision history and get an idea for what new coding changes might be throwing this off. Another user talked about it seems to be since the introduction of the Realms feature related to ?XBOX Live?
Mods: When will there be any newer additional "steps you can try" being provided by MOJANG support posted to this bug thread number???
This is getting ridiculous the amount of wait time being left "in-limbo" without any communications as to whether or not any of your staff is even looking into this issue, first of all... and then... possible documents/notes posted to this thread annotating detailed steps the tech-savvy among us can try to correct the issue.
For starters... you could post instructions for how to go about ensuring that you've checked for and eradicated all possible places and file locations where 3rd party texture packs may be located in the file system?
In response to this issue... I also setup my kids tablet so that it is associated with its own Google Play account based off his very own email address, in order to further isolate his tablet from my Visa accounts.
As such, I just now had to buy this App again for his device. Which I did, no big whoop.
But 0.15.6 is now installed... and as far as I can tell by going thru every app in the Apps manager... I've uninstalled (before re-purchasing) any and everything that even remotely resemble something Minecraft-related that was not actually Minecraft PE itself. And STILL... no go.
You invoke... there's some number of full seconds where screen is black... then Boop! right back out to home screen. No msgs of any kind.
At the very least can you post-up instructions for us non-root'd users for how to go about inspecting whichever event logs are in the OS for this?
I don't happen to develop in Android OS (yet). But I'll betcha money I can spot something that looks off in a log. Been using computers since C-64. Been coding since '92.
Just give me some direction here.
-G
What Thomas Towle said on 01/Aug/16 @11:42pm
Kindly please ask the techs in the future... when such a case occurs that you all would like to opt to follow the case with an earlier item number... that you'd be so kind as to let the rest of us stressfully waiting for resolution to the issue know that we now need to hop over to another train and camp out there instead.
Thank you sir.
Please forgive me... but can somebody please explain to me why this issue got marked as Resolved?
What EXACTLY was tested for and was resolved? (Just marking an item as Resolved without notes like that... especially in a customer-facing position... Really??)
... and in what version number did it get resolved in? (C'mon man, this is Developer/QA 101 stuff here!)
As of the date of this comment (8-2-2016) The currently listed version is 0.15.4 and that version does not seem to correct this problem that, at least these poor folks here, are having.
(BTW, Here are the specs for all the devices mentioned so far. Found on GMSArena.com, URL's provided for your convenience)
Samsung Galaxy Tab 3 P5210 --> (http://www.gsmarena.com/samsung_galaxy_tab_3_10_1_p5210-5478.php)
Samsung Galaxy GT-P7310 --> (http://www.gsmarena.com/samsung_galaxy_tab_8_9_p7310-3893.php)
LG LEON --> (http://www.gsmarena.com/lg_leon-7053.php)
Samsung Galaxy Ace Plus --> (http://www.gsmarena.com/samsung_galaxy_ace_plus_s7500-4397.php)
Sony Tablet S --> (http://www.gsmarena.com/sony_tablet_s-4137.php)
Motorola Xoom Wifi (MZ604) --> (http://www.gsmarena.com/motorola_xoom_mz604-3833.php)
Samsung GT-P7510 --> (http://www.gsmarena.com/samsung_galaxy_tab_10_1_p7510-3894.php)
Asus Transformer TF101 --> (http://www.gsmarena.com/asus_transformer_tf101-3936.php)
Acer Iconia A500 --> (http://www.gsmarena.com/acer_iconia_tab_a500-3907.php)
My Samsung Galaxy Tab 2 10.1 that it does work on?
(http://www.gsmarena.com/samsung_galaxy_tab_10_1_p7510-3894.php)
Several of us were instructed to begin watching this opened issue... and that our reports were duplicates... SO... as good little users that's what we did.
Closing this case.. as Resolved.. (With No Notes?) Even AFTER the same folks that have reported it to you have also explicitly told you that your latest release which is posted up on the Play store (0.15.4) did NOT resolve it for them?
Kinda not cool, no?
Just so we, as users, are being thorough here.. Perhaps you can ask around with your tech's and see if any of them has made a document that describes how to go about thoroughly ensuring that you've removed any and all mods which could affect MCPE? I very thoroughly went thru my Boys Acer and uninstalled quite a bit of stuff off that darn thing. Before doing so I backed-up the worlds he constructed to a different location on the External SD. Uninstalled anything that looked like it could be related to MCPE (and even a bunch of other games not related, just to re-gain room)... did a shutdoon/restart...re-installed MCPE (0.15.4)... before even bothering to put back the files for his level he built, tried running it... nogo... like everybody else is saying... few split-seconds of blackscreen... then BOOP!... back to OS. No error msgs. No nothing.
Thank you sir. I've added a watch to the other issue number.
Pardon the interruption. By virtue of me opening this item ticket here, when whomever eventually addresses this issue closes this item number as Resolved.... does your system automatically send me an email to my registered address... explaining it's been resolved, and in what version number and approx when that version number will be available for DL in the Google Play store?
Hmmph... I included both OS version and kernel build number in one of those original fields you fill out when posting your bug report.
Anyway.. lemme see... (boots up the device)...
Android version 4.0.3
Kernel version 2.6.39.4+
I think you hit the nail on the head with this one.
Sure enough... in this message forum thread... I read Acer Iconia A500. (Among MANY others)
Since this message thread seemed to have a very definitive list of models which do not support NEON I figured I'd post the link to it here so that OTHER concerned parents such as myself who'd like to get their kid back up and being able to enjoy the game will now have a point of reference for knowing which models they can AVOID.
https://forum.unity3d.com/threads/failure-to-initialize-your-hardware-does-not-support-this-application-sorry.311613/