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!
MCPE 0.16.2 on two devices:
Samsung Galaxy S5, Qualcomm Snapdragon 801 quad-core processor (ARM), SUPPORTS NEON, 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), DOES NOT SUPPORT NEON, 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, when I mentioned in July that I suspected it had to do with processor architecture, I might have been in the right ballpark. On a similar bug report β MCPE-8332 Minecraft PE not starting (blackscreen) β the problem seems to be caused by some chipsets that do not include the NEON extension. Could this be what's causing these devices to be unable to run MCPE 0.15.x and up? Pertinent comments from MCPE-8332 are quoted below.
"MCPE-8332 Soren Hannibal said:
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.
[MCPE Mod] rplatham said:
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 Soren Hannibal'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."
Thank you, Soren, for summarizing. The Dell Venue 7 is decidedly not fixed yet, so it should stay on the list.
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!
Updated to 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 (I'll save my complaints about 0.16.0 for a more appropriate forum).
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!
Updated to 0.15.9 on two android devices:
Samsung Galaxy S5, Qualcomm Snapdragon 801 quad-core processor (ARM), Android OS version 5.0, Minecraft PE version 0.15.9, never any 3rd party mods etc. β WORKS FINE
Dell Venue 7 3740, Intel Atom z3460 dual-core processor (x86), Android OS version 4.4.4, Minecraft PE version 0.15.9, never any 3rd party mods etc. β STILL CRASHES (upon launching app, immediately crashes "Unfortunately, Minecraft - Pocket Edition has stopped.")
This has been a major problem since JUNE. What's being done to make it right? How long are we going to have to wait to have a usable version of this software we paid for? It's really frustrating.
Updated to 0.15.6 on two Android devices
Samsung Galaxy S5, Qualcomm Snapdragon 801 quad-core processor (ARM), Android OS version 5.0, Minecraft PE version 0.15.6 β WORKS FINE
Dell Venue 7 3740, Intel Atom z3460 dual-core processor (x86), Android OS version 4.4.4, Minecraft PE version 0.15.6 β STILL CRASHES (upon launching app, immediately crashes "Unfortunately, Minecraft - Pocket Edition has stopped.")
Updated to 0.15.4 on two Android devices
Samsung Galaxy S5, Qualcomm Snapdragon 801 quad-core processor (ARM), Android OS version 5.0, Minecraft PE version 0.15.4 β WORKS FINE
Dell Venue 7 3740, Intel Atom z3460 dual-core processor (x86), Android OS version 4.4.4, Minecraft PE version 0.15.4 β STILL CRASHES (upon launching app, immediately crashes "Unfortunately, Minecraft - Pocket Edition has stopped.")
Updated to 0.15.2 on two android devices this morning:
Samsung Galaxy S5, Qualcomm Snapdragon 801 quad-core processor (ARM), Android OS version 5.0, Minecraft PE version 0.15.2 β WORKS FINE
Dell Venue 7 3740, Intel Atom z3460 dual-core processor (x86), Android OS version 4.4.4, Minecraft PE version 0.15.2 β STILL CRASHES (upon launching app, immediately crashes "Unfortunately, Minecraft - Pocket Edition has stopped.")
No 3rd Party Mods. No 3rd Party Texture Packs. Crashes when connected or disconnected to any network.
Dell Venue 7 3740, Intel Atom z3460 dual-core processor (x86), Android OS version 4.4.4, Minecraft PE version 0.15.1.2
Just an idea. I was thinking of Android devices, not Win10, since the 0.15 updates have worked well on my phone's Snapdragon ARM, but never on my tablet's Intel x86...
I also have had this problem on my Dell tablet since the 0.15.0 update. I suspect it has something to do with the tablet's processor architecture being x86, not ARM, but why this update broke it when 0.14.x was running just fine, I dunno. Is there any way to roll back to 0.14?
Version 1.0.7.0 (Amazon App Store)
Samsung Galaxy S5, Qualcomm Snapdragon 801 quad-core processor (ARM), SUPPORTS NEON, Android OS version 5.0, Minecraft PE version 1.0.7.0, never any 3rd party mods etc. β RUNS
Dell Venue 7 3740, Intel Atom z3460 dual-core processor (x86), DOES NOT SUPPORT NEON, Android OS version 4.4.4, Minecraft PE version 1.0.7.0, never any 3rd party mods etc. β STILL CRASHES (app crashes within 2 seconds of launching "Unfortunately, Minecraft - Pocket Edition has stopped."). Last working version: 0.14.3
I'm glad to see the latest updates are now working for some devices without NEON support. Unfortunately, mine still crashes. Happy to provide any info I can to help solve this (almost year-old) problem.