Minecraft PE not starting (Blackscreen)

I've updated my ASK 913 SP to Android 4.1.2. The problem still exists.

More info about the ASK 913 SP: Based on Allwinner A13, ARM Cortex A8 CPU, Mali 400 GPU, Allwinner CedarX VPU.

Using MCPE 0.12.1 Build 5 and continues happening to me.

There was an exception before MCPE hangs. The message from logcat is:

W/System.err( 2561): java.io.FileNotFoundException: images/mob/sheep_0.tga
W/System.err( 2561): at android.content.res.AssetManager.openAsset(Native Method)
W/System.err( 2561): at android.content.res.AssetManager.open(AssetManager.java:337)
W/System.err( 2561): at android.content.res.AssetManager.open(AssetManager.java:311)
W/System.err( 2561): at com.mojang.minecraftpe.MainActivity.getFileDataBytes(MainActivity.java:430)
W/System.err( 2561): at dalvik.system.NativeStart.run(Native Method)
W/System.err( 2561): at dalvik.system.NativeStart.run(Native Method)
W/System.err( 2561): getImageData: Could not open image images/fireball.png

Version 0.12.1 fixed this for me.

Using the latest 0.12.1 hangs. Previous version (prior to yesterday's release (9/9/2015) worked fine.

Symptoms: Starts, switches to black screen and progresses no further. Have to use <Home> button to break out and Task Manager shows excessive CPU usages ( > 50%)

Model: Samsung S II
Android version: 4.0.4

I just download the new update of Minecraft PE, and finally fixed this bug. Thanks Mojang!

The latest version (v0.12.1) from Google Play fixed the problem. Thanks!

Sean Moenkhoff - Did you ever get this resolved? I am having the same problem on 0.12.1. Please email me at [email protected].

MCPE 0.12.1 will not load, screen just goes black. I have to click the home screen several times to get out. I've tried uninstalling and reinstalling to no avail. Please help!

Android 4.0.4
Samsung Galaxy Tab 10.1

Does this bug still appear in 0.12.2? If so please respond.

For me on my Samsung SII - yes, it still starts with a black screen, high CPU and never progresses further. My last communication with Sheri is still still experiences the issue as well.

Yes, still occurring on Samsung Galaxy Tab 10.1 running Android 4.0.4. Not resolved.

Sometimes MCPE starts with a black screen and didn't load.

Device Samsung Galaxy Note3 SM-N9005
Android 5.0
MCPE 0.13.0

Hi,

I get black screen every time I open latest version (0.13.0). Tried uninstall, restart, re-opening the app, nothing works:

Motorola Xoom
Android 4.0.4

Thanks

OK, so I have now upgraded my Xoom to Android 4.4.4 and still getting the same issue. The logcat shows a tonne of Java.FileNotFoundException errors.

Please acknowledge ASAP as to when this will be resolved.

Please can we have an update to this issue. There has been no moderator activity since 22 October.

We're having a hard time reproducing, but I will definitely bump the priority.

Nick, does it feel like the device is sluggish/slow when this happens? Try switching to/from the game with the home/multitask buttons and see if it reacts fast or not.

Switching to/from MCPE and home screen does seem sluggish, although when at the home screen it's fine.

That could mean that the game is stuck in an infinite loop. Thanks.

An update would be nice. How is the investigation going? Thanks.

I have the same issue where I just get a black screen when trying to open minecraft on Motorola Xoom. Here are the details of the issue:

Device:  Xoom
OS Version:  Android 4.04
Minecraft APK version:  0.13.1
Please see [logcat main|https://bugs.mojang.com/secure/attachment/108929/colton_minecraft1.txt] and [system logs|https://bugs.mojang.com/secure/attachment/108928/colton_minecraft_system1.txt] attached.  The symptom is the the device immediately goes to an all black screen when launching minecraft and stays there for several minutes.  The logs show the device is stuck in an infinite loop trying to open a file that does not exist.  Here is a snippet from the logcat logs.

h3.logcat main
{quote}
I/ActivityManager(  275): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=com.mojang.minecraftpe cmp=com.mojang.minecraftpe/.MainActivity bnds=[144,52][240,148]} from pid 594
I/ActivityManager(  275): Start proc com.mojang.minecraftpe for activity com.mojang.minecraftpe/.MainActivity: pid=4275 uid=10053 gids={3003, 1015}
D/dalvikvm(  275): GC_CONCURRENT freed 1579K, 37% free 13763K/21511K, paused 3ms+9ms
D/OpenGLRenderer(  594): Flushing caches (mode 1)
D/OpenGLRenderer(  594): Flushing caches (mode 0)
D/dalvikvm( 4275): GC_CONCURRENT freed 162K, 4% free 6812K/7047K, paused 3ms+3ms
D/dalvikvm( 4275): Trying to load lib /data/data/com.mojang.minecraftpe/lib/libgnustl_shared.so 0x410a9d30
D/dalvikvm( 4275): Added shared lib /data/data/com.mojang.minecraftpe/lib/libgnustl_shared.so 0x410a9d30
D/dalvikvm( 4275): No JNI_OnLoad found in /data/data/com.mojang.minecraftpe/lib/libgnustl_shared.so 0x410a9d30, skipping init
D/dalvikvm( 4275): Trying to load lib /data/data/com.mojang.minecraftpe/lib/libfmod.so 0x410a9d30
D/dalvikvm( 4275): Added shared lib /data/data/com.mojang.minecraftpe/lib/libfmod.so 0x410a9d30
D/dalvikvm( 4275): Trying to load lib /data/data/com.mojang.minecraftpe/lib/libminecraftpe.so 0x410a9d30
D/dalvikvm( 4275): Added shared lib /data/data/com.mojang.minecraftpe/lib/libminecraftpe.so 0x410a9d30
I/dalvikvm( 4275): Could not find method android.media.AudioManager.getProperty, referenced from method org.fmod.FMOD.getOutputBlockSize
W/dalvikvm( 4275): VFY: unable to resolve virtual method 78: Landroid/media/AudioManager;.getProperty (Ljava/lang/String;)Ljava/lang/String;
D/dalvikvm( 4275): VFY: replacing opcode 0x6e at 0x0016
I/dalvikvm( 4275): Could not find method android.media.AudioManager.getProperty, referenced from method org.fmod.FMOD.getOutputSampleRate
W/dalvikvm( 4275): VFY: unable to resolve virtual method 78: Landroid/media/AudioManager;.getProperty (Ljava/lang/String;)Ljava/lang/String;
D/dalvikvm( 4275): VFY: replacing opcode 0x6e at 0x0016
I/System.out( 4275): getwidth: 1280
I/System.out( 4275): getheight: 752
I/dalvikvm( 4275): Failed resolving Lcom/mojang/minecraftpe/input/JellyBeanDeviceManager; interface 37 'Landroid/hardware/input/InputManager$InputDeviceListener;'
W/dalvikvm( 4275): Link of class 'Lcom/mojang/minecraftpe/input/JellyBeanDeviceManager;' failed
E/dalvikvm( 4275): Could not find class 'com.mojang.minecraftpe.input.JellyBeanDeviceManager', referenced from method com.mojang.minecraftpe.input.InputDeviceManager.create
W/dalvikvm( 4275): VFY: unable to resolve new-instance 269 (Lcom/mojang/minecraftpe/input/JellyBeanDeviceManager;) in Lcom/mojang/minecraftpe/input/InputDeviceManager;
D/dalvikvm( 4275): VFY: replacing opcode 0x22 at 0x0006
I/dalvikvm( 4275): Failed resolving Lcom/mojang/minecraftpe/input/JellyBeanDeviceManager; interface 37 'Landroid/hardware/input/InputManager$InputDeviceListener;'
W/dalvikvm( 4275): Link of class 'Lcom/mojang/minecraftpe/input/JellyBeanDeviceManager;' failed
D/dalvikvm( 4275): DexOpt: unable to opt direct call 0x0477 at 0x08 in Lcom/mojang/minecraftpe/input/InputDeviceManager;.create
W/MCPE    ( 4275): INPUT Noop register device manager
D/libEGL  ( 4275): loaded /system/lib/egl/libGLES_android.so
I/ActivityManager(  275): Displayed com.mojang.minecraftpe/.MainActivity: +468ms
D/libEGL  ( 4275): loaded /system/lib/egl/libEGL_tegra.so
D/libEGL  ( 4275): loaded /system/lib/egl/libGLESv1_CM_tegra.so
D/libEGL  ( 4275): loaded /system/lib/egl/libGLESv2_tegra.so
W/MinecraftPE( 4275): INITINIT!
I/fmod    ( 4275): AudioDevice::init : Min buffer size: 8916 bytes
I/fmod    ( 4275): AudioDevice::init : Actual buffer size: 8916 bytes
D/Finsky  ( 2393): [179] InAppBillingUtils.pickAccount: com.mojang.minecraftpe: Account determined from installer data - [XLjYeNqpKvaqB1PqQ4taBDHbYAI]
D/Finsky  ( 2393): [178] InAppBillingUtils.pickAccount: com.mojang.minecraftpe: Account determined from installer data - [XLjYeNqpKvaqB1PqQ4taBDHbYAI]
I/GooglePlayStore( 4275): onIabSetupFinished: 0, Setup successful. (response: 0:OK)
W/System.err( 4275): Cannot find file 
W/System.err( 4275): java.io.FileNotFoundException: 
W/System.err( 4275): 	at android.content.res.AssetManager.openAsset(Native Method)
W/System.err( 4275): 	at android.content.res.AssetManager.open(AssetManager.java:315)
W/System.err( 4275): 	at android.content.res.AssetManager.open(AssetManager.java:289)
W/System.err( 4275): 	at com.mojang.minecraftpe.MainActivity.getFileDataBytes(MainActivity.java:433)
W/System.err( 4275): 	at dalvik.system.NativeStart.run(Native Method)
W/System.err( 4275): 	at dalvik.system.NativeStart.run(Native Method)
W/System.err( 4275): Cannot find file 
W/System.err( 4275): java.io.FileNotFoundException: 
W/System.err( 4275): 	at android.content.res.AssetManager.openAsset(Native Method)
W/System.err( 4275): 	at android.content.res.AssetManager.open(AssetManager.java:315)
W/System.err( 4275): 	at android.content.res.AssetManager.open(AssetManager.java:289)
W/System.err( 4275): 	at com.mojang.minecraftpe.MainActivity.getFileDataBytes(MainActivity.java:433)
W/System.err( 4275): 	at dalvik.system.NativeStart.run(Native Method)
W/System.err( 4275): 	at dalvik.system.NativeStart.run(Native Method)
W/System.err( 4275): Cannot find file 
{quote}
\\
\\
h3.logcat system
{quote}
D/dalvikvm( 4365): Trying to load lib /data/data/com.mojang.minecraftpe/lib/libgnustl_shared.so 0x410aaac0
D/dalvikvm( 4365): Added shared lib /data/data/com.mojang.minecraftpe/lib/libgnustl_shared.so 0x410aaac0
D/dalvikvm( 4365): No JNI_OnLoad found in /data/data/com.mojang.minecraftpe/lib/libgnustl_shared.so 0x410aaac0, skipping init
D/dalvikvm( 4365): Trying to load lib /data/data/com.mojang.minecraftpe/lib/libfmod.so 0x410aaac0
D/dalvikvm( 4365): Added shared lib /data/data/com.mojang.minecraftpe/lib/libfmod.so 0x410aaac0
D/dalvikvm( 4365): Trying to load lib /data/data/com.mojang.minecraftpe/lib/libminecraftpe.so 0x410aaac0
D/dalvikvm( 4365): Added shared lib /data/data/com.mojang.minecraftpe/lib/libminecraftpe.so 0x410aaac0
I/dalvikvm( 4365): Could not find method android.media.AudioManager.getProperty, referenced from method org.fmod.FMOD.getOutputBlockSize
I/System.out( 4365): getwidth: 1280
I/System.out( 4365): getheight: 752
W/dalvikvm( 4365): VFY: unable to resolve virtual method 78: Landroid/media/AudioManager;.getProperty (Ljava/lang/String;)Ljava/lang/String;
D/dalvikvm( 4365): VFY: replacing opcode 0x6e at 0x0016
I/dalvikvm( 4365): Could not find method android.media.AudioManager.getProperty, referenced from method org.fmod.FMOD.getOutputSampleRate
W/dalvikvm( 4365): VFY: unable to resolve virtual method 78: Landroid/media/AudioManager;.getProperty (Ljava/lang/String;)Ljava/lang/String;
D/dalvikvm( 4365): VFY: replacing opcode 0x6e at 0x0016
I/dalvikvm( 4365): Failed resolving Lcom/mojang/minecraftpe/input/JellyBeanDeviceManager; interface 37 'Landroid/hardware/input/InputManager$InputDeviceListener;'
W/dalvikvm( 4365): Link of class 'Lcom/mojang/minecraftpe/input/JellyBeanDeviceManager;' failed
E/dalvikvm( 4365): Could not find class 'com.mojang.minecraftpe.input.JellyBeanDeviceManager', referenced from method com.mojang.minecraftpe.input.InputDeviceManager.create
W/dalvikvm( 4365): VFY: unable to resolve new-instance 269 (Lcom/mojang/minecraftpe/input/JellyBeanDeviceManager;) in Lcom/mojang/minecraftpe/input/InputDeviceManager;
D/dalvikvm( 4365): VFY: replacing opcode 0x22 at 0x0006
I/dalvikvm( 4365): Failed resolving Lcom/mojang/minecraftpe/input/JellyBeanDeviceManager; interface 37 'Landroid/hardware/input/InputManager$InputDeviceListener;'
W/dalvikvm( 4365): Link of class 'Lcom/mojang/minecraftpe/input/JellyBeanDeviceManager;' failed
D/dalvikvm( 4365): DexOpt: unable to opt direct call 0x0477 at 0x08 in Lcom/mojang/minecraftpe/input/InputDeviceManager;.create
W/MCPE    ( 4365): INPUT Noop register device manager
D/libEGL  ( 4365): loaded /system/lib/egl/libGLES_android.so
I/ActivityManager(  275): Displayed com.mojang.minecraftpe/.MainActivity: +438ms
D/libEGL  ( 4365): loaded /system/lib/egl/libEGL_tegra.so
D/libEGL  ( 4365): loaded /system/lib/egl/libGLESv1_CM_tegra.so
D/libEGL  ( 4365): loaded /system/lib/egl/libGLESv2_tegra.so
W/MinecraftPE( 4365): INITINIT!
I/fmod    ( 4365): AudioDevice::init : Min buffer size: 8916 bytes
I/fmod    ( 4365): AudioDevice::init : Actual buffer size: 8916 bytes
D/Finsky  ( 2393): [178] InAppBillingUtils.pickAccount: com.mojang.minecraftpe: Account determined from installer data - [XLjYeNqpKvaqB1PqQ4taBDHbYAI]
D/Finsky  ( 2393): [179] InAppBillingUtils.pickAccount: com.mojang.minecraftpe: Account determined from installer data - [XLjYeNqpKvaqB1PqQ4taBDHbYAI]
I/GooglePlayStore( 4365): onIabSetupFinished: 0, Setup successful. (response: 0:OK)
W/System.err( 4365): Cannot find file 
W/System.err( 4365): java.io.FileNotFoundException: 
W/System.err( 4365): 	at android.content.res.AssetManager.openAsset(Native Method)
W/System.err( 4365): 	at android.content.res.AssetManager.open(AssetManager.java:315)
W/System.err( 4365): 	at android.content.res.AssetManager.open(AssetManager.java:289)
W/System.err( 4365): 	at com.mojang.minecraftpe.MainActivity.getFileDataBytes(MainActivity.java:433)
W/System.err( 4365): 	at dalvik.system.NativeStart.run(Native Method)
W/System.err( 4365): 	at dalvik.system.NativeStart.run(Native Method)
W/System.err( 4365): Cannot find file 
W/System.err( 4365): java.io.FileNotFoundException: 
W/System.err( 4365): 	at android.content.res.AssetManager.openAsset(Native Method)
W/System.err( 4365): 	at android.content.res.AssetManager.open(AssetManager.java:315)
W/System.err( 4365): 	at android.content.res.AssetManager.open(AssetManager.java:289)
W/System.err( 4365): 	at com.mojang.minecraftpe.MainActivity.getFileDataBytes(MainActivity.java:433)
W/System.err( 4365): 	at dalvik.system.NativeStart.run(Native Method)
W/System.err( 4365): 	at dalvik.system.NativeStart.run(Native Method)
W/System.err( 4365): Cannot find file 
{quote}

MY LAST COMMENT ,I WILL NOT DUPLICATE AGAIN!
samsung galaxy ace plus ,GT-S7500, Android 2.3.6
always force close when open,minecraft logo not available, PLS FIX IT THANK.
Device type: Samsung Galaxy Ace plus GT-S7500/ AND/ SGH-I727
always force close when open,minecraft logo not available
What I expected to happen was...:
when i open minecraft app 0.13.1 it will start minecraft home,but 0.14.0 Beta 1,2,3 also now black screen
What actually happened was...:
when i open minecraft app it will start with phone vibrate,screen black
Steps to Reproduce:
1. apps list the icon of minecraft is not available
2. after that i tap and open minecraft pe
3.then my phone vibrate,screen black
4.then i saw SORRY! the apps minecraft .................is stopped

Does this bug still appear in 0.14.0? If so please respond.

Sorry I cannot test, since I don't own that device.

My Samsung SII still gets a Blackscreen.

Hi I am also getting a black screen when attempting to launch Minecraft Pocket edition on Motorola MZ604 Android version 4.0.4, running Minecraft Pocket Edition v 0.14.1

Just reproduced this on Motorola Xoom, running Android 4.1.2. MCPE version 0.14.1. I successfully installed the same version on a Sony SGPT12 (my tablet – my son's is the Xoom) with no issues. The Xoom just shows an endless black screen upon launching the game. Uninstalled and reinstalled with no luck. Son is quite disappointed, but I'll need to refund this until the bug is fixed.

The summary will not be changed.

LG G-Pad 7 happens the same, but it opens after some seconds

My son managed to boot our old Samsung SII phone (Android 4.0.4) into Safe Mode accidentally and Minecraft version 0.14.3 appears to no longer get the Blackscreen on startup. Not sure if this helps anyone or if anyone else can confirm or had this same success.

Just updated to 0.15.1.2 and mcpe will not load. Black screen and then android error.
Samsung Gt-p5210
Android 4.4.2
Was working fine before update.

Device: Galaxy Tab 10.0
System: Android 4.0.4
Version: 0.15.0

With recent update, having the same problem...black screen then back to home screen (will not launch).

0.15.1.2 android same thing here

Samsung sm-t530nu

Android 5.0.2

Same issue. when tapping the MCPE icon, screen goes blank for a few seconds then back to the tablet home screen. No menu, no errors, just black screen. Only happened recently when updating to 15.0 and/or 15.1.

Sony tablet S
Android version 4.0.3 (release5a)
System is up to date.

Same problem here, My niece updated Minecraft from 0.14 to 0.15 . When trying to open it, she gets black screen for a few seconds then back to the tablet home screen.

Samsung GT-P5210
Android 4.4.2

And also, it was working perfect before. I hope you find a solution ASAP 😞

clearing the com.mojang folder from the tablet resolved it on the tablet it was occuring on.

Same problem click on Minecraft PE screen goes black & then back to home page. Worked fine before .15 update.

Acer 500

Mike W's Fixed worked on my daughters Samsung galexy tab 4, but before deleting EVERYTHING out of the folder i copied the minecraft worlds folder to my PC. Then i deleted the folder in its entirety. launched Minecraft and it launched just like it is intended to with no worlds. Closed the app again. Then i then copied the worlds into the new worlds folder on the tablet. Re-opened the app and all her worlds were able to be opened. Thank you Mike you are a life saver.

Version 0.15.1.2

Same black screen on attempt to start after updating to 0.15.1. Goes black for about 15-20 seconds then returns to home screen. Have tried reboot, delete and reload of MCPE. Also removed MCPE, saved copy of worlds directory, removed MCPE directories (as some have suggested to attempt to fix problem), then reinstalled MCPE and attempted to start. Same black screen result and MCPE directories have not been recreated. Worked fine on 0.14.3. System is Samsung GT-P7510 with Android 4.0.4.

Thanks Thomas, a better ticket for you to discuss this on is MCPE-15986. Please read the comments there, comment with your particulars, try the solutions proposed and let us know (on that ticket) what happens.

Thanks for the redirection. I guess that this black screen startup issue number is only for pre 0.15 versions? Since several comments here were about problems after installing 0.15 I thought this might be the right place but I will comment over on 15986.

Dears, I've tried deleting all other mods & third party programs. Also deleted com.mojang folder entirely. Restart the Tablet, then installed 0.15.0 and tried 0.15.1 , disabled WiFi and try to open it, and guess what? I didn't work!! enable WiFi again, Not working again. The exact blackscreen.
Device Information:
Samsung Galaxy Tab 3
Model #: GT-P5210
Android: 4.2.2
Any other suggestions?

Dear Mojäng support,

My son have same problem, black screen after starting and after ~20s thrown back. He is running
MCPE 0.15.2.1
on a
Samsung GT-P7310 with
Android 4.04

hello

my daugther have the same problem
minecraft start and still with black screen after a few second the apk shut down
it s on a samsung galaxy tab 1 and started with the last upgrade

thank you for your help

I have the same problem on my Samsung Tab 8.9 (The device that my son place on)
https://en.wikipedia.org/wiki/Samsung_Galaxy_Tab_8.9
GT-P7310, with android 4.0.4
the problem started for me with the 0.15.0 version and I have tried to clear memory/cache/re-install and the problem is the same. On all other devices that I have it works well.
If there is a way to help to solve the problem let me know and I can send logs and other things to help.

SAMSUNG GALAXY ACE PLUS(android 2.3.6) FORCE CLOSE AT THE VERSION 0.15.3.PLS FIX THE BUGS

Hello

I have the same Problem with the black screen since Version 0.15.0 until to actual Version 0.15.3.2 on an Sony Tablet S with Android 4.0.3…

Same issue here. Updating to MCPE Version 0.15.3.2 did not fix the black screen problem.
Try to launch app, screen goes black except for my soft keys/notification bar at the bottom of the screen, stays black for about 35 seconds, then returns to whatever screen I attempted to launch from (home screen or Play Store)

Device: Samsung Galaxy Tab 10.1
Model number: GT-P7510
Android version: 4.0.4 (Ice Cream Sandwich)

Running COMPLETELY STOCK MCPE. Have 0 texture packs and 0 mods. Pure Vanilla MCPE here.

Please tell us a fix is on the way, or at least make older versions that worked available. I have 2 very upset children that spent their allowances on this game and haven't been able to play for about a month now. Play Store reviews for this device echo my same complaints time and time again. Multiple emails to Mojang have gone unanswered! I don't think the answer should be that I have to go out and buy a newer tablet for hundreds of dollars.

Also not working on Motorola Xoom Wifi (MZ604) running Android 4.4.4. None of the 0.15.x versions have worked. No extra mod/textures installed. Tried uninstalling and reinstalling MCPE, clearing cache, dalvik cache. Nothing has worked. Haven't tried the network turn-off yet, but will tonight.

Another upgrade 15.6 and still not fixed. Little bit annoyed that I have paid for this app and other add ons and my son still can not even open Minecraft PE. Any clues on a time scale as its been going on for weeks now??????

0.15.6 still broken on Moto Xoom.

0.15.6 still broken for me as well. System is Samsung GT-P7510 with Android 4.0.4.

0.15.6 still broken for me too. Blackscreen for a few seconds, than return to previous screen.
Acer Iconia A200 Android 4.0.3
Boring and annoying. Why did I pay for this crap?
Does anyone from Mojang take notice of all these reports here? Does anybody from Mojang try to fix this problem?

Same here. Did not fix Sony Tablet S, Android 4.0.3

We also have Sony S tablets (both now not accessing MCPE) - Android version 4.0.3.
Ever since the update introducing realms, whenever we try to open MCPE it hangs on a black screen for a few seconds then goes back to the home screen.
We have not been able to open it for over 3 months now and my children are getting rather upset.
I am too scared to update the iPad in case it stops working also!!
The last version to work on the Sony S tablets was v0.14.3.... every update since that version has resulted in the black screen/not opening problem.
I have installed every update so far, and tried all the suggestions on various threads, but nothing is yet to work. Latest update installed this morning on the Sony S tablet was v0.15.6.

Mine is a RCA device same issue

Come on Mojang. This has been an issue for many since 0.15.0. Seemingly common characteristics are folks running Android 4.x.x. People are willing to send logs and help troubleshoot. Unfortunately it looks like the 0.16.x beta versions still do not run for many. We have bought this app 3 times in our family - 2 of the tablets will not run it.
On my daughter's Motorola Xoom running 4.4.4, the first anomaly to note in the logs shows issues accessing an unavailable shared library xperiaplaycertified and then numerous errors associated with /data/app-lib/com.mojang.minecraftpe-1/libminecraftpe.so

Hi all,

if you are now running one of the 0.16 beta testing testing builds, please comment on MCPE-16647 instead of this ticket. If you are running 0.15.7 or earlier, please try the following and comment back if it did not resolve your problems:

Temporary Solution 1: rename the resource_packs folder (if it exists, it is inside of games/com.mojang) and try to start MCPE.

Temporary Solution 2 (clean reinstall):

1. back up your com.mojang/MinecraftWorlds folder (to backup your worlds)

2. uninstall MCPE

3. delete the com.mojang folder

4. reinstall MCPE

5. start MCPE, and if it runs, you can restore your MinecraftWorlds folder.

I am also looking into FMOD, an audio library used by MCPE which may be out of date (or causing problems) on MCPE on older Android versions.

Tried the two solutions just proposed (again) back in early July on 0.15.1 and commented here that they didn't work. I can't try the solutions again since the directory has been gone for two months now as it doesn't get created on MCPE install or startup. I have posted a few traces on MCPE-14125 since I was directed to comment there rather than here but the problem description here still seems to me to be a better match. Still running 0.15.7 on Samsung GT-P7510 with Android 4.0.4.

Thanks @unknown, I haven't received much assistance keeping the crash tickets straight, but when I get logs I forward them to the devs. Am I reading your comment above correctly:

1. Installing MCPE 0.15.7 succeeds on your Samsung ST-P7510 Android 4.04 but that doesn't create the resource_packs folder.

2. Running MCPE crashes (giving you crash1.txt and crash2.txt as examples) and also does not create the resource_packs folder.

3. MCPE has not run on your device since _____ update?

rplatham wrote: Thanks Thomas Towle, I haven't received much assistance keeping the crash tickets straight, but when I get logs I forward them to the devs. Am I reading your comment above correctly:
1. Installing MCPE 0.15.7 succeeds on your Samsung ST-P7510 Android 4.04 but that doesn't create the resource_packs folder.
2/ Running MCPE crashes (giving you crash1.txt and crash2.txt as examples) and also does not create the resource_packs folder.
3. MCPE has not run on your device since _____ update?

1. Correct, install succeeds but doesn't create any resource_packs folder.
2. Running MCPE just causes a black screen for some seconds and does not create the resource_packs folder. It does not however generate any crash?.txt messages. (This is why I say that the problem descriptions on MCPE-8332 or on MCPE-15986 are a better match for my problem than the description associated with MCPE-14125 where I was sent after starting on this issue).
3. MCPE has not run on my device since the automatic update to 0.15.1 from 0.14.3 where it was working fine.

I have tried both 1 and 2.
Nothing worked. I did not get any folders under 'games' in step 2.
I am currently running 0.15.8
Need any more help let me know. I am located in Stockholm. I guess you are too. I can provide with non working samsung pad for trial.

Stil a problem in 0.15.9
what do you need to solve this? Is anyone looking into this?
What can I do to help? I am a sw developer my selfe and understand the problem of solving an issue without good solid log.

Also still no fix for me in 0.15.9. This is the ninth release since you broke it with 0.15.1 three months ago. I know it has been requested before but how about making some 0.14 release available so I can at least go back to using the app I paid for.

0.15.9 still broken on Moto Xoom.

Moto Xoom 0.15.9 crash log

Same here on my Moto Xoom, Android 4.0.4, MCPE 0.15.10. Click on icon, black screen for a few seconds, and then close. I know it's not the right place, but for some reason the exactly same thing happens with XBOX app. I thought it could be related as version 0.15 brings in the Realms.

I can confirm 0.15.10 is still broken on Moto Xoom - however, mine is running Android 4.4.4.

This has happened to me to and I find it really anoing, I just want to play the game I payed for.

It is still broken on my android device, yes.

I have just fixed this issue with MCPE 0.15.10. running on Android 5.1. (Hudl 2)
I installed ES Explorer to investigate file differences between my broken version and a vanilla install. To fix my broken version I added the word 'Minecraft' (without quotes) to the previously empty file : /games/com.mojang/minecraftpe/resource_packs.txt and it worked perfectly.

same here. paid but can not play. do they come out a solution yet?

Same issue on Android Alcatel tablet model T10, Android version 4.0.4 , kernel version 3.0.8+, MCPE version 0.15.10.0
I have checked all issues, and all redirected to this MCPE-8332
Black screen only when opening, after minutes of black screen, and attempt to return to home screen - get message "minecraft - pocket edition is not responding. Would you like to close it? wait/report/OK"
Game continues to be running in background, as in Settings/Apps/Running game systems and processes running com.mojang.minecraftpe
Only started since updated MCPE to latest version. was working previously.
tried other suggestions eg going to settings, backup/reset, ensure autorestore is disabled, uninstall and re-install - no good
Explorer> rename resource_packs folder in games/com.mojang, restart, and/or reinstall - no good
Explorer > games/com.mojang. delete file, reinstall - no good
delete cache, internal data. reinstall - no good
Only have 2 games on tablet, so plenty of storage and RAM

Phone: LG-P700, Android 4.0.3, MCPE version 0.16.0.5

The game ran without issues before the 0.16.0 update. Now it crashes within seconds after startup.

0.16.0.5 still broken on Moto Xoom running Android 4.4.4 - i have had the same issue since 0.15.0.

MCPE 0.14.3 was working fine on both of my Android devices. When I updated to 0.15.0, it broke on one of my devices, but not the other. This has remained true with each update through 0.16.0 on two Android devices:

Samsung Galaxy S5, Qualcomm Snapdragon 801 quad-core processor (ARM), Android OS version 5.0, Minecraft PE version 0.16.0, never any 3rd party mods etc. – RUNS
.
Dell Venue 7 3740, Intel Atom z3460 dual-core processor (x86), Android OS version 4.4.4, Minecraft PE version 0.16.0, never any 3rd party mods etc. – STILL CRASHES (upon launching app, immediately crashes "Unfortunately, Minecraft - Pocket Edition has stopped."). Last working version: 0.14.3

So frustrating! What can we do to help identify the problem? It hasn't worked for almost FIVE MONTHS now... C'mon guys!

Still broken in my Motorola Xoom running Android 4.4.4. What's more frustrating is that we get absolutely no feedback from Mojang.

The lack of communication from Mojang is very annoying.

At their request, I have provided crash logs a few times. I am not going to bother again because Mojang doesn't even acknowledge receipt of the logs or whether they are even useful or not. Some feedback would be nice.

We do read the comments here and all the logs. Sadly we have trouble reproducing the issue, and in this case the crash logs doesn't reveal what the real cause is. At this point there are probably even multiple causes for this issue. Every now and then we push a fix for a blackscreen issue, but it's incredibly hard to know if it's the one that causes this or not...

The game just crashes without ever showing the crash report screen.

@tomas alaeus
If you are located in Stockholm I could provide with a non working device. That might solve one issue

Phone: LG-P700, Android 4.0.3
Updated MCPE to 0.16.1.0 and it works fine again.

I stil have the same issue with 0.16.1
Black screen and then it just stops without any crash report.

Most of the current black screen issues started with the 15.0 update affecting most android 4.0 systems. Seems that would be a good starting point for a fix. The problem started with the incorporation of MCPE to the Windows 10 platform and the addition of Realms. Also the requirement for an internet connection to play the game may also be an issue. I think earlier versions could be played off line. My Sony Tablet still don't work. Android version 4.0.3

@tomas alaeus - thanks for a bit of insight - it's good to get some feedback even if a successful fix hasn't yet arrived.

0.16.1 still broken on Moto Xoom running Android 4.4.4

I'm trying to summarize which devices/OS versions we still have problems with, after we did the 16.1 memory fixes (we lowered memory usage, and some 512mb devices started working again).

There have been recent reports about the following devices:
1. Dell Venue 7 3740, Intel Atom z3460 dual-core processor (x86), 512mb ram, Android OS version 4.4.4. Maybe 16.1 fixed this one?
2. Android Alcatel tablet model T10, 1gb, vivante gc800 gpu, Android version 4.0.4
3. Motorola Xoom, tegra 2, 1gb ram, Android 4.4.4
4. Motorola Xoom, tegra 2, 1gb ram, Android 4.0.3
5. Sony Tablet, tegra 2, 1gb ram, Android version 4.0.3

There are many older reports, but I don't know if the issue still occur. Are there other devices that also suffer from this, as of 16.1 or newer? Please also specify if you are offline or online when playing (I don't think we require online connections, but it may still affect stability for some devices).

We haven't been able to repro on our own devices, so maybe they have something else in common? The only common factor is that it is Android 4.x.x versions. We will keep looking for this, though.

I have tried both online and offline on my Moto Xoom on Android 4.4.4. Still broken on 0.16.2.

Still doesn't work on 0.16.2.2 either online or offline. System is Samsung GT-P7510 with Android 4.0.4.

Thank you, Soren, for summarizing. The Dell Venue 7 is decidedly not fixed yet, so it should stay on the list.

My Samsung S2 acts interesting now. Let summarize below:
Android: 4.0.4
Mode: Online/Offline (both)
Last Working Version: 0.14.3
Broken Versions: 0.15 - 0.16.1
Current Version: 0.16.2

After updating to 0.16.2 from the Google Playstore, it has started all but 2 times (so far). These times the screen was black for a while but dropped me back to the Android screen from which the Minecraft icon was touched. I touched it again and it loaded following the times listed below.

It loads with the device held in landscape or portrait oriented position.

In either orientation, touching the Minecraft icon it takes approximately 1 minute, 12-25 seconds with purely a black screen but finally loads. It plays and generates worlds just fine.

Clicking the Exit on the Exit Minecraft Diaglog box does not seem to stop the game from running, just merely drops the device back to the screen in which Minecraft was loaded from. Task Manager still shows it running even after several minutes. A force kill is required to actually stop the app from running.

Thank you for that detailed report. Sean, your occasional crash on startup could easily be something different than the consistent crash. If it crashes on launch but a subsequent launch succeeds, it could easily be timing related. Maybe the device is busy doing other things, and it slows down the launch enough for the OS to think the app failed to launch. It would make sense why that happens on slower devices.
The exit dialog bug is a different issue.

Soren, you said, "The exit dialog bug is a different issue." I am not sure what the "exit dialog bug" relates to. The description of the problem associated with MCPE-8332 says "There is just a Blackscreen. There is no way that it starts. Tried to reopen app and just lock/unlock device. Note:The app does not crash, its just a Blackscreen"

So according to this problem description, there is no exit dialog. Just to let you know, my failure report is of the Blackscreen type.

Thomas, that note was in response to Sean's comment - he mentioned an issue with the exit dialog, and I just said I think that part is unrelated

We're believing that this issue is sometimes caused by a very long startup time. For those that experience this (blackscreen when starting, no crash), try to let the device run for at least an hour and see what happens.

For my problem Moto Xoom, I have tried running Minecraft immediately after a reboot, after the tablet has been on for hours, and after the tablet has been on for days. The length of time it has been on has made no difference for this issue unfortunately.

Huawei ascend Android 4.3 eternal black screen on startup issue started happening in 0.17/1.0 build 3 tried rremoving all files relating to resource/behavior packs going to try removing other files as this has helped with some previous startup failure issues if anything works I will post a comment if It doesn't work for me that doesn't mean it won't work on other devices as such fixes aren't always universal with this game

@chris lowe, thank you for trying- we actually think you may have to launch the app and then wait for a long time, up to an hour. We started using a function that took a really long time on Android 4.x, but apparently only on some devices. We have a large pool of different android devices that we circle through, but none were affected. We have ordered a Motorola Xoom to add to this pool now, though, as that seem to be the most common offender.
@j parker: We don't have that device, but I think we have that one fixed in next release. As Tomas said, "crash on startup" can be many different things. Sometimes multiple compounding errors are affecting the machines, so it's hard to say for sure who's issues are fixed by each version 😞

I wish it was as simple as just waiting a long time. I either get the black screen then kicked to homescreen or blackscreen followed by this app has stopped, do you want to report message.

So, the app crashes before I get the opportunity to wait.

I still have the same problem on my Samsung Tab 8.9 https://en.wikipedia.org/wiki/Samsung_Galaxy_Tab_8.9
GT-P7310, with android 4.0.4
the problem started for me with the 0.15.0 version and I have tried to clear memory/cache/re-install and the problem is the same.
If there is a way to help to solve the problem let me know and I can send logs and other things to help.
I have check memory consumption and it does not increase that much when launching the app. After a while it just stops.

I think you misunderstood my comment the issue I'm having is the eternal black screen not a crash you were probably confused by me comparing this to the 0.16 crash on startup but the comparison was only to suggest that the first thing to try with any startup related issue is to remove the com.mojang folder

@j parker and @chris lowe: yeah, the eternal black screen is what I think we may have fixed. The crash is the one I'm not sure about.
@Peter: logcat output may help.

Can confirm on v1.0 b3

Thank you for the helpful comments and information given.

Just a reminder:

Please make sure that comments are related to reported bug and written respectfully towards other players and development team. Offtopic, arguments and insults will be removed and author will be banned.

This is how the issue performs in my Moto Xoom 4.0.4: https://youtu.be/41v39v05Dng

Started affecting my Pantech P8010 (ARM 7, v71 running Android 4.1.2) as of 1.0.0.0 build 3.

I'm having the same problem as of 1.0 b3. I'm on a Motorola droid turbo running Android 5.1.

I have the same problem in 1.0.0.0 (Build 3) the game only starts after 3 or 4 minutes and in addition to get the game started I had to keep the notification bar open until the black screen comes out if I did not stop for so long Waiting for the game to open.And my device that I play is in Lg L70

EnderDragon, I didn't let mine go long enough. This time I let it sit and it did finally load the game after a full minute.

The 1.0.0.0 beta has a very long start time. On my tab(Shield K1), it takes about 5-10sec.

For my device (Samsung Galaxy Tab 3V aka SM T116 NU, with stock android 4.4.4 kitkat OS), the startup time is about 5 minutes, sometimes longer and starts in 7 minutes. It sometimes shows "not responding" while still in blackscreen sometimes especially when I tap the touchscreen to keep the display on while MCPE is loading. It only started loading this long since I updated to the 1.0.0.0 beta for me.

Just to answer your reports. We have found the major cause for this increase in startup time, and it's fixed in the next release/beta release. But I don't think it will fix the issue for everyone unfortunately...

Hi Tomas, did you guys have a chance to look at the Moto Xoom issue? Soren Hannibal mentioned earlier that you ordered a unit of it for testing.

We got the Moto Xoom, still waiting on the charger to arrive 😞

I have an original Moto Xoom WiFi (MZ-604), it's currently rooted and on android 4.1.2. and MCPE just exits on launch back to home screen. I gave up on it running MCPE back in 0.15.x I think having tried all the suggested fixes but I am happy to test any builds and supply whatever debug info might help to diag this on the xoom.

Ok, so we reproduced the issue on the Motorola Xoom, and I have investigated this thoroughly for the last 2 days. Unfortunately I have some bad news. The problem is caused by the fact that a small number of chipsets used for Android devices (like the Nvidia Tegra 2) does not include the Neon extension. About 6 months ago we made a number of major architectural changes that means we rely on Neon for a number of things – including making the game run faster, to compensate for the performance cost of all the added features.

While we will investigate further if we can fix this, it’s a very large task to take on, and it’s would risk destabilizing the game for everyone else. I think it would take at least 3 months from now to have a verified, fully tested fix. I’m not sure if it is even possible for us to fix it at all, but I will be trying.

Thanks for the update Soren. I'm glad to hear that the issue has been identified. An alternative to fixing the Neon extension issues would be to roll-back these devices to Minecraft 0.14.x. While we wouldn't get all the newer features, we would at least be able to play local solo games and you would save the time necessary to do a development fix!

Hey Chris, thank you for the suggestion. Unfortunately, there's no way for us to segment the non-Neon devices from other android devices in the stores, so if we did a rollback it would affect every Android player. And I don't know of any way to make older builds optionally available. I'll keep thinking about this problem, maybe an idea will pop up.

Hi @Soren, should we consider filling for a refund then? Google Support says we're supposed to contact the developers and they are "responsible for deciding if you are eligible for a refund." - https://support.google.com/googleplay/answer/2479637?hl=en

I've updated the ticket description so this information about Neon is easy to find. For those experiencing a Blackscreen crash at startup of MCPE, please check to see if your device supports Neon. As in @unknown's comments above, MCPE on Android devices requires a processor that supports Neon and will crash to a blackscreen if your processor does not support Neon.

You can check if your device supports Neon by installing a system checking tool and looking at the supported features for your processor. I recommend SysCheck by Christopher Moeller because it is free, simple and because you can see if your processor supports Neon on the very first page, just like in this screenshot (ugly red circling added for emphasis).

If you are still getting a Blackscreen crash at start up of MCPE and you have confirmed that your device supports Neon, then please create a new ticket and mention that you've already checked for Neon support. We really hope this is the only reason for a blackscreen crash at start up, but if there are more bugs, we'd like to figure them out and squash them too.

I'm about to buy a new phone for my girl with a MediaTek MT6750 SoC, but could not find any information about its Neon support. Can you help me please with checking this specific SoC? Does it have Neon support? Any idea how can I check the support before purchasing? Thanks!

As far as I can tell from this page, it should support NEON. http://system-on-a-chip.specout.com/compare/1070-1217/Media-Tek-MT6752-vs-MediaTek-MT6750

Lee, thank you for finding this great website!
Although it states that only MT6752 supports Neon, but NOT MT6750. 😞
http://system-on-a-chip.specout.com/l/1217/MediaTek-MT6750
http://system-on-a-chip.specout.com/l/1070/Media-Tek-MT6752

my device samsung galaxy ace plus gts7500 also support neon but still getting a Blackscreen crash at start up of MCPE

I finally bought a Meizu m3s phone (3GB/32GB version http://www.gsmarena.com/meizu_m3s-8148.php )
which has MediaTek-MT6750 chipset WITHOUT Neon support according to this page:
http://system-on-a-chip.specout.com/l/1217/MediaTek-MT6750
SURPRISE: It still runs MineCraft flawlessly!

MediaTek MT6750 uses the Cortex A53 ARM architecture, which always supports NEON. See https://en.wikipedia.org/wiki/List_of_ARM_microarchitectures
Almost all Cortex-A architectures have NEON support, and the only exceptions are A5 and A9, where NEON is optional.

@Leandro: I don't know the answer to that question - I'm only part of the programming team, this seems like a community question.

@Soren: Thanks for the clarification!

Hey guys! I got the black screen bug on mcpe 1.0.0 and it is not from the neon because my device supports neon I need help, thank you.

Not sure if anyone is still following this thread. There has been a related issue - Google Play Services has recently introduced Neon related code which has hobbled at least all Tegra2 (i.e., non-neon) devices. In chatting with Google support, I have suggested that they figure out some sort of developer flag that could be used to identify Neon vs Non-Neon devices, which is a Play store app flag that @Soren Hannibal claims does not currently exist. Such a flag could be useful to Mojang to potentially roll non-neon devices back to Minecraft 0.14.x when Neon wasn't required. While recognizing that those older versions of Minecraft may not be compatible with the new versions, it would at least be playable locally on the non-neon device.

@Soren Hannibal - if such a flag existed at Google, would Mojang consider rolling us back to an older version? My daughter really misses Minecraft on her Moto Xoom tablet.

Also - Soren - you mentioned you were continuing to assess options for non-Neon devices (over the next few months). Realistically do think newer Minecraft versions will ever support non-Neon devices or should we give up hope?

Other Tegra2 devices (I don't know if it's complete) which are probably impacted by this same Minecraft issue.

Acer Iconia Tab A100
Acer Iconia Tab A101
Acer Iconia Tab A200
Acer Iconia Tab A500
Acer Iconia Tab A501
Advent Vega
Asus Eee Pad Slider SL101
Asus Eee Pad Transformer TF101
Dell Streak 10 Pro
Dell Streak 7
Dell Streak 7 Wi-Fi
eLocity A7
Exper EasyPad P10AN
LGE Optimus 2d SU660 star_450-05
LGE Optimus 2X SU990
LGE Optimus EX SU880
LGE Optimus Pad V900
LGE Optimus Q2 LU6500
LGE Revolution
MALATA SMB-A1011
Micromax A85
Motorola ATRIX
Motorola Droid Bionic XT865
Motorola Droid X2
Motorola MOTO MT870
Motorola MOTO XT882
Motorola Photon 4G MB855
Motorola Xoom MZ505
Motorola Xoom MZ600
Motorola Xoom MZ601
Motorola Xoom MZ604
Mouse LuvPad AD100
Olivetti OliPad 100
ONKYO TA117
Point of View Mobii 10.1
Samsung Captivate Glide i927
Samsung Galaxy R I9103
Samsung Galaxy Tab 10.1 ( ALL MODELS!)
Samsung Galaxy Tab 8.9 ( ALL MODELS!)
Sony Tablet P
Sony Tablet S
T-Mobile G-Slate
T-Mobile G2x
TORADEX Colibri T20
Toshiba FOlio AC100
Toshiba Thrive
Velocity Micro Cruz Tablet L510
ViewSonic G Tablet
WooW Digital The One
ZTE Grand X V970

hi @chris lowe
thank you for your explications
i'm afraid, as an ultimative non-expert i don't understand what this means for me as an owner of a asus a200 (non-neon). you mention a "Neon related code which has hobbled at least all Tegra2". can i install this code and fix the minecraft-problem which still exists for months and months without creepy and completely disappointing mojang working on it?
thanks for support

Nope there is nothing you can do - it is something the developers need to fix.

It is the Neon code that Minecraft v 0.15.x and newer introduced, plus the neon code that Google introduced in their most recent version of Google PLay Services that has caused issues with at least some non-neon devices. So far no fixes have been found for Minecraft and the only fix for Google Play Services has been to revert from the most recent version 10.2.98 back to 10.0.84. This Google Play Services fix is only temporary as it eventually auto-updates to 10.2.98.

Are you experiencing numerous "Google Play Services has stopped" errors since Feb 9 when the latest Google Play Services was rolled out? These errors have effectively hobbled my Moto Xoom when any Google app such as GMaill, Maps or Hangouts runs.

Ah, thanks for explanation. So this was only a very short moment of hope ;-(
Luckily no "Google Play Services has stopped" errors. Until now at least... From now on I will be scared about it.
So perhaps other game-starting problems are also due to this "Neon"-problem, for example no more "Crossy Road" and no more "Talking Ben" - both games formerly being loved by my son.

Interesting that you're not getting Google Play Services errors. I have seen folks with Acer (not ASUS) Iconia A200 devices reporting the errors in the Google support forums.

Do you have an Asus S200 or an Acer A200?

@chris lowe, thanks for reporting to Google. If a google store option for uploading non-neon binaries existed, I imagine we could upload an older build, but I can't guarantee it - I'm not really involved with the submission process and don't know what issues we can get into by uploading a second build.

We're still investigating, and have not given up. In fact, our non-neon device is currently in shipping to another dev to investigate further. However, it's a tough issue, and I can't say for sure if it will get fixed. It's one of those things that sound like it should be easy to flip a switch somewhere, but it just isn't 😞

@Soren Hannibal - thanks for filling us in on current status! It will be interesting to see if Google resolves the NEON issue they introduced with Google Play Services. I understand developers like Mojang perhaps not going back to support non-Neon devices - but you'd hope at least that Google wouldn't brick the OS of otherwise still mostly useful older non-Neon devices!

there is documentation how to write code using NEON for android and how to check whether device supports it
https://developer.android.com/ndk/guides/cpu-arm-neon.html

I've seen that page. Unfortunately it doesn't really help. I'm currently battling our build system/compilers to get them to build the game without NEON instructions. Depending on how the game performs after that there will be some different routes that we can take.

@[Mojang] Tomas Alaeus - glad to hear the battle is ongoing!

Yay, it starts now. There were some other issues with shaders (which might fix the startup issue for others that have NEON devices) that I had to fix as well. I need to tweak it, clean it up and measure the performance hit as well.

Details: It's actually not just NEON instructions that make the Xoom (Tegra 2) different from others. It's also that it doesn't support VFPv3 which is another optional instruction set available on ARMv7 processors. For the Android target which Google calls "armeabi-v7a" they only require Thumb2 and VFPv3-D16 (not VFPv3). Disabling NEON was therefore not enough, we also need to turn it down to VFPv3-D16.

In short: I think I have successfully built the game with only VFPv3-D16 (instead of VFPv3 and NEON) and it does seem to work on the Xoom that we have here. It also doesn't seem to affect performance negatively in any measurable way. Yay \o/.

#[Mojang] Tomas Alaeus - thanks for the update and the technical explanation - it's exciting to hear Minecraft may come back to Tegra2 devices like my daughter's Xoom! Fortunately Google has also seemingly fixed the recent Google Play Services issues which temporarily bricked all Tegra2 devices. The effort you (and presumably others at Mojang) have put into this issue is much appreciated!

I most definitely agree, @chris lowe. There's still goodness in the world 🙂 Thank you for all the effort, @Tomas Alaeus.

PSA: This bug fix will most likely not make it into 1.0.5, unfortunately. @unknown has run into some shader problems that he needs to refix, so this bug will probably not be fixed until either the next minor update (1.0.6, if another minor update comes before 1.1) or the next major update (1.1). Sorry for any disappointment. 😞 At least the bugfix is actively being worked on, and is getting very close to being done now! 🙂

Ok, I think I managed to solve the issue now. I don't know why the device had problems compiling the shader code, what caused it or which part of the shader compilation that failed (Motorola building the device, Nvidia building the chipset, X for making the compiler, Khronos group for defining GLSL). But I do know that if I have to continue investigate this issue then I will lose brain cells.

Thanks Mojang-ites - we appreciate the effort to support our oldie, but still goodie devices! We wouldn't want anyone to lose brain cells either.

I can confirm 1.0.5 still crashes on Asus TF101 so the fix is not included as [MCPE Mod] SuperGeniusZeb mentioned above. Looking forward to next version and thanks a lot for the effort. I do not plan to retire my TF101 any time soon so I really appreciate it.

We just released 1.0.6, and we think this should fix it. Please give it a try and post back what you see. We're not going to resolve the bug until we hear that the problem has gone away, because I don't want us to jinx it 🙂

I am having the some problem but it iwi1.0.6

With not iwi

Can you explain what you see? which device? which android version? which build?

Tried 1.0.6, and am unfortunately still getting the same error. 😞

Dell Venue 7 3740, Intel Atom z3460 dual-core processor (x86), Android OS version 4.4.4, NO NEON SUPPORT
Minecraft PE version 1.0.6, never any 3rd party mods etc. Last working version: 0.14.3
Upon launching app, hangs in black screen for maybe 10 sec. then crashes with message "Unfortunately, Minecraft - Pocket Edition has stopped."

Let me know if there's anything I can do to help. We'll get this bug yet!

Wow! Great job, unexpected! Minecraft working again on my Acer Iconia A200 (Android 4.0.3) after many months of blackscreens. Thank you, guys, my son will be happy!
Unfortunately we lost all our worlds. I find them in the folder games/com.mojang/minecraftWorlds but not, when starting the game. Perhaps there will be a solution?
Thanks so far!

@FrankK, so I don't think you have lost the worlds. In 1.0.5, we moved worlds to a different location to follow Android best practices. But you can hopefully access the old files by going to Settings->profile->File Storage Location, and set to “application”. Hopefully that works, but at least you can still run the game.

@Matthew Greer, the error you see is not neon-related, because Neon is an ARM only. And with the Neon issue, it crashes in a second. What you see is possibly a timeout - I believe Android shuts down any app that is unresponsive for more than 10 seconds. If so, it could be because our code just takes too long before it gets going - it's hard to know. Some things that may help is to try to restart your device, to try starting 2/3 times in a row, or disabling wifi.

Woot woot! SUCCESS on my daughter's Moto Xoom running a custom android 4.4.4 ROM! Thanks VERY much Mojang folks for resolving the issue! My daughter is very happy!

Just installed 1.0.6 and it has fixed the problem on my Samsung GT-P7510 with Android 4.0.4. Black screen on startup problem started on my system with the update to 0.15.1 back in June of last year. It has been a long time coming but better late than never. Since I was originally prompted to move my problem report to MCPE-14125 I will also comment on that issue. Thanks for the update.

@Soren Hannibal: Thanks for reply and help. Unfortunately this doesn't work. Perhaps I have to copy the files to another folder or to rename the folder?
Yes, you are right: At least it runs after 10 months of darkness 😉

It works! Asus TF101 (Tegra2),Android 4.4
Thank you 🙂

Yay! I'll give it a try tonight! Thank you, Mojang!

OFFTOPIC: @chris lowe, how did you work around that annoying issue with Google Play Services? I'm still having issues with many apps, including Youtube.

@unknown: Well, if Android force closes the app because it doesn't respond within 10 seconds, then it is our fault for not making it respond fast enough. There is no reason why the app shouldn't respond in time, thus it's a valid bug that we definitely can fix.

Yeah, agree.

@Leandro Dimitrio - you need to install a beta version of Google Play Services (for the Xoom it is version 10.5.48 (032-150087156) - you can download it from apkmirror. There's additional info @ https://forum.xda-developers.com/motorola-xoom/help/motorola-xoom-10-1-wifi-mz604-crashing-t3554786

@FrankK - I think you actually need to change the file storage location to "external". I played around a bit with locations last night as my daughter created a new world in the "application" storage location, but couldn't see any of her older worlds. I found the new world "application" location, but I think you need to be rooted to navigate to it. I moved this new world to the same location where you have yours stored and switched the storage location to "external" and now I can see both the new world and the older ones.

For some reason, though, when I tried to move the older "external" worlds to the "application" location, they wouldn't load - only the newly created world would load - hence why I settled on the "external" location.

Hopefully Google has figured out a Play store flag that allows developers to now identify non-NEON devices and either fork development for continued support or freeze updates when NEON code is introduced into their apps!

WOW!
1.0.6 Is working now on my UK Moto Xoom WiFi (MZ-604).
Excellent job!

@chris lowe, that worked perfectly well! Thank you bud.

Mojang dev team, working beautifully in my good 'ol Moto Xoom, stock rom 😃 Thanks again for all the good effort!

Wow also! I can confirm that while my Samsung SII (Model SPH-D710) started loading MCPE at version 0.16.2 again but took approximately 1 minute and 20 seconds to load the screen. Now, with version 1.0.6 that start time is down to 47 seconds.

Good Job!

It works for me as well. Great work

As non-NEON devices now seems to be starting again, we'll be resolving this bug.

If your device crashes on start-up, please see MCPE-14125.

Ok, here we are again.
Minecraft no more working since latest updates (actual version 1.1.2) on my ACER Iconia A200 (non-neon).
Long loading time (black screen), then start interface. Crash to home-screen when creating a new world or when opening a saved one, no warning, no message.
How FRUSTRATING!

I updated my Moto Xoom yesterday - the latest version of Minecraft is still working for me, granted it took a while to load. I chalk up the slowness to the age of the device as everything generally runs slow on the Xoom these days!

Recently update mcpe and now it will not open. Screen goes black and will not open. Have mcpe 1.1.3.52,. Have confirmed that my Verizon Ellipsis 8 does support Neon and has ARMv7. Will not open. Please help!

@unknown - Have you tried a full uninstall/reinstall (including deleting the com.mojang folder)?

Back up anything you don't want to lose first, such as your worlds.

I just bought MCPE 1.1.4 today. Black screen. Samsung Galaxy Tab 2 7.0
Wiped to factory reset, re-installed MCPE, still black screen.
NEON supported, added the SysCheck.
My son paid for this, and is so sad that he cannot play it. I have read all comments in this string. I do not know what else I can do, any suggestions?

I'm having the same problem on my Amazon Fire tablet. MCPE worked for a few weeks and now I'm getting the black screen when I click on the app and it just takes me back to my home screen.

I still havê same problem and neon is OK