Socrates Amadeus Thomas
- socksmusicalcat
- socksmusicalcat
- Europe/Stockholm
- Yes
- No
MCPE-1249On the TF300 model, specifically, entry of text into signs causes the game to hang and then crash. This could possibly have to do with the virtual keyboard as I do not use a dock or Bluetooth keyboard. When Minecraft is started again and the world is re-opened, a blank sign is in spot where I placed it before the crash. I have sent a bug report via Android 4.0's built-in bug-reporting system, but I thought I would mention it here as well.
On the TF300 model, specifically Android 4.0.3, entry of text into signs causes the game to hang and then crash. This could possibly have to do with the virtual keyboard as I do not use a dock or Bluetooth keyboard. When Minecraft is started again and the world is re-opened, a blank sign is in spot where I placed it before the crash. I have sent a bug report via Android 4.0's built-in bug-reporting system, but I thought I would mention it here as well.
On the TF300 model, specifically Android version 4.0.3, entry of text into signs causes the game to hang and then crash. This could possibly have to do with the virtual keyboard as I do not use a dock or Bluetooth keyboard. When Minecraft is started again and the world is re-opened, a blank sign is in spot where I placed it before the crash. I have sent a bug report via Android 4.0's built-in bug-reporting system, but I thought I would mention it here as well.
On the TF300T model, specifically Android version 4.0.3 (stock ROM), entry of text into signs causes the game to hang and then crash. This could possibly have to do with the virtual keyboard as I do not use a dock or Bluetooth keyboard. When Minecraft is started again and the world is re-opened, a blank sign is in spot where I placed it before the crash. I have sent a bug report via Android 4.0's built-in bug-reporting system, but I thought I would mention it here as well.
On the TF300T model, specifically Android version 4.0.3 (stock ROM), entry of text into signs causes the game to hang and then crash. This could possibly have to do with the virtual keyboard as I do not use a dock or Bluetooth keyboard. When Minecraft is started again and the world is re-opened, a blank sign is in spot where I placed it before the crash. I have sent a bug report via Android 4.0's built-in bug-reporting system, but I thought I would mention it here as well.
UPDATE: I have upgraded the firmware to 4.1.1 (still ASUS stock ROM), and signs no longer cause the game to crash. From the comments, I have determined that this is an error specific to Android 4.0.3/.4's virtual keyboard. I was able to update and circumvent this bug, but others may not be so fortunate. Therefore, this issue should not be closed until the problem is fixed for Android 4.0, as I am sure that many devices have not been updated to Jelly Bean.
On the TF300T model, specifically Android version 4.0.3 (stock ROM), entry of text into signs causes the game to hang and then crash. This could possibly have to do with the
virtual keyboard as I do not use a dock or Bluetoothkeyboard. When Minecraft is started again and the world is re-opened, a blank sign is in spot where I placed it before the crash. I have sent a bug report via Android 4.0's built-in bug-reporting system, but I thought I would mention it here as well.UPDATE: I have upgraded the firmware to 4.1.1 (still ASUS stock ROM), and signs no longer cause the game to crash. From the comments, I have determined that this is an error specific to Android 4.0.3/.4's virtual keyboard. I was able to update and circumvent this bug, but others may not be so fortunate. Therefore, this issue should not be closed until the problem is fixed for Android 4.0, as I am sure that many devices have not been updated to Jelly Bean.
On the TF300T model, specifically Android version 4.0.3 (stock ROM), entry of text into signs causes the game to hang and then crash. This could possibly have to do with the way the OS handles keyboard input. When Minecraft is started again and the world is re-opened, a blank sign is in spot where I placed it before the crash. I have sent a bug report via Android 4.0's built-in bug-reporting system, but I thought I would mention it here as well.
UPDATE: I have upgraded the firmware to 4.1.1 (still ASUS stock ROM), and signs no longer cause the game to crash. From the comments, I have determined that this is an error specific to Android 4.0.3/.4's virtual keyboard. I was able to update and circumvent this bug, but others may not be so fortunate. Therefore, this issue should not be closed until the problem is fixed for Android 4.0, as I am sure that many devices have not been updated to Jelly Bean.
This makes the situation a bit more complex, considering that your devices have completely different hardware, that leads me to believe it is some sort of incompatibility with the virtual keyboard. Jonathan, have you upgraded your phone to ICS?
Firmware upgrade (to Android 4.1.1) fixed it for me, but I doubt Jelly Bean is available for everybody else. This is probably an ICS-only issue. My bug report has been updated to reflect this information.
See https://mojang.atlassian.net/browse/MCPE-1249
I have determined that this is probably due an issue with the virtual keyboard for Android 4.0. Upgrade your firmware to Android 4.1 or 4.2 if possible.
Duplicates MCPE-1249. I have determined that this is most likely an Android 4.0 virtual keyboard bug. Update your device if possible, and please search to see if your issue has already been mentioned elsewhere next time.
I figured this would be a problem for many older devices that just barely made the cut for ICS. I guess I should consider myself lucky that ASUS decided to support my device.