DEVICE = Acer Iconia Tab A500.
Son had been happily enjoying your app. The app is set to Auto-Update in Google Play. He goes into Google Play the other day, Auto-Update kicks-off. Update seems to run to completion as per norm. Afterward invoking app goes to Blackscreen for a brief bit, then bops back out to OS.
Steps tried:
Uinstalled all possible extraneous Minecraft-related apps he had installed on the device. There were a handful. Then did uninstall and re-install of currently avail. version on Google Play. 0.15.3 reinstall seems to go without a hitch. Same issue invoke...blackscreen for a moment, then back to OS.
Uninstalled again. Tried copying his saved word maps to an external SD... then completely deleted the \com.mojang folder under \games folder. Which only had 3 txt's in it anyway. One was like a UserID value, another held something like data Re: last server he'd joined, then the 3rd had a lot of what I'll assume are a buncha command-line vars for settings within the engine of the game system.
With the \com.mojang folder completely deleted.. I goto Google Play and do install again. Seems to run to completion fine. Again, invoke, blacksreen, bops right back out to OS.
Did the latest update change the OS version requirements or something?
I even tried turning off the Dolby mobile Sound settings. no change. put settings back.
Internal storage show as 12.71GB Available showing at 7.05GB
All these attempts were done with power connected to charger, just in case.
Linked issues
duplicates 1
Comments 18
What android version are you on?
What android version are you on?
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+
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+
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+
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?
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?
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?
Hi @unknown sorry, but our system doesn't quite work that way. Depending on your profile in this bug tracker, you may get an email when someone comments on a ticket you submitted. For MCPE this bug tracker is not directly connected to the MCPE developers, so the volunteer moderators resolve bugs based on already existing tickets (i.e resolved duplicate, so follow the other ticket) or based on identification that the bug is no longer in the game. Here is a ticket where many Android 4.0.3 users are having this same problem: MCPE-15986. At the moment we are unaware of a solution.
Hi @unknown sorry, but our system doesn't quite work that way. Depending on your profile in this bug tracker, you may get an email when someone comments on a ticket you submitted. For MCPE this bug tracker is not directly connected to the MCPE developers, so the volunteer moderators resolve bugs based on already existing tickets (i.e resolved duplicate, so follow the other ticket) or based on identification that the bug is no longer in the game. Here is a ticket where many Android 4.0.3 users are having this same problem: MCPE-15986. At the moment we are unaware of a solution.
Hi @unknown sorry, but our system doesn't quite work that way. Depending on your profile in this bug tracker, you may get an email when someone comments on a ticket you submitted. For MCPE this bug tracker is not directly connected to the MCPE developers, so the volunteer moderators resolve bugs based on already existing tickets (i.e resolved duplicate, so follow the other ticket) or based on identification that the bug is no longer in the game. Here is a ticket where many Android 4.0.3 users are having this same problem: MCPE-15986. At the moment we are unaware of a solution.
Since the issue is the same, I've resolved this ticket as a duplicate of MCPE-15986. Please put further comments on that ticket, and clikc "Watch this issue" to get emails when there are further comments.
Since the issue is the same, I've resolved this ticket as a duplicate of MCPE-15986. Please put further comments on that ticket, and clikc "Watch this issue" to get emails when there are further comments.
Since the issue is the same, I've resolved this ticket as a duplicate of MCPE-15986. Please put further comments on that ticket, and clikc "Watch this issue" to get emails when there are further comments.
Thank you sir. I've added a watch to the other issue number.
Thank you sir. I've added a watch to the other issue number.
Thank you sir. I've added a watch to the other issue number.
What android version are you on?