chris lowe
Assigned
Reported
Comments
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!
@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.
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!
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.
#[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!
@[Mojang] Tomas Alaeus - glad to hear the battle is ongoing!
@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!
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?
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.
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
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?
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!
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.
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.
I have tried both online and offline on my Moto Xoom on Android 4.4.4. Still broken on 0.16.2.
0.16.10 still broken on Moto Xoom running Android 4.4.4
0.16.10 still broken on Moto Xoom running Android 4.4.4
0.16.10 still broken on Moto Xoom running Android 4.4.4
0.16.10 still broken on Moto Xoom running Android 4.4.4
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!