Can you post some screenshots of what your creative inventory looks like after this has happened?
@unknown please do not post comments simply asking someone to look at your issue. First, this doesn't do anything (no one gets notice). Second, there are many many many issues being managed with different priority, so it will take an unknown amount of time for a moderator to get to your issue.
Sorry, I cannot reproduce this issue. Can you please provide more details in your bug report to help us reproduce it in a new survival world?
On my Samsung Galaxy S6 (SM-G920W8) Android 7.0 security patch level July 1, 2017 running build 1.2.022 in a new survival world using the Pocket UI, GUI scale medium, I can tap an item from inventory, tap an empty hotbar slot and the item is placed in that slot as expected.
Hi. This works as intended because your device does not have sufficiently high specs. Per the changelog for 1.2.0.22 "Jungle leaves are now transparent on higher-end devices when Fancy Leaves are enabled".
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.
Can anyone confirm this bug is still present in 0.16.2?
Does this happen with any diamond sword or one in particular in your world?
Can you reproduce this crash in a new creative flat world? If yes, please describe how you've built the "library" surrounding the enchantment table and exactly what steps you take to place a diamond sword and cause the crash.
Confirmed on Samsung Galaxy S4 SGH-I337M Android 5.0.1, MCPE 1.0.0.7: new creative flat single player world, using tp command to move to these coordinates, I built portals and observed as follows:
254,6,0 (stretched pixels in N/S direction)
0,6,254 (stretched pixels in E/W direction)
0,254,0 (fine).
Interesting to note the stretch direction changed!
I picked 254 distance because that's the most we can go in the z direction.
I forgot that this bug might not affect Android 6, oops. I'll retest on an Android 5 device and report back... As requested, I'll test changing x and z independently too.
I tried to test this using a new creative flat world with cheats enabled. I teleported to these four locations and built end portals at each: 0,5,0 then 300,5,300 then 1000,5,1000 and finally 40000,5,40000 and at all locations the portals all looked fine and the same... Tested MCPE 1.0.0.7 on Samsung Galaxy S6 SM-G920W8 Android 6.0.1
On the first portal, I was too close to it when it opened and I traveled to the end, had to convert personal game mode to survival, kill myself and convert back to creative to get back and continue the test.
The format changed so the packs must be revised to work with 0.16, even if those packs worked with a 0.15 beta build.
Agree, I confirm they do generate in 0.16.0. Perhaps they don't generate in the same places in 0.16.0 as in the beta builds.
To see one in 0.16.0 try seed 984344053 coords 243 63 - 420
Please post the seeds that you used. At the moment, I cannot generate a new world in 0.16.0 and find an ocean monument.
I have tested these two seeds that had ocean monuments when testing beta builds:
Seeds with ocean temples right near spawn in 0.15.90.8:
One Ocean Monument near spawn -1436927780
Two Ocean Monuments near spawn -1528394888
As above, the custom resource packs need to be updated to match the new structure in 0.16.0.
This is a known issue that the devs are working on. Thanks. Here's hoping we don't have hundreds of duplicates to resolve between now and fix...
Tested on Samsung Galaxy S6 (SM-G920W8), Android 6.0.1 MCPE 0.15.90.8 in a new creative/survival infinite world using villager spawn eggs and in a village of a new survival world (seed 228529541). I tested against different villagers (brown, white, purple, but no babies). In all cases, crouching by a villager showed the open button, but I could not cause clicking it to crash the game. I did not test using split controls.
Not too late. We (volunteer moderators) don't control when bug fixes go into new updates. I hope Stronghold generation is fixed in the next public release too.
Well, back on June 8, 2015 (when that comment was posted) Magma Cubes weren't splitting when killed. This feature wasn't added until 0.12.1 build 1. see http://minecraft.gamepedia.com/Magma_Cube#History
Now (versions 0.15.90.8 or 0.15.10) this should be working fine. If it is not, please create a new ticket.
Confirmed using Samsung Galaxy S6 (SM-G920W8), Android 6.0.1 as wifi direct host and Samsung Galaxy S4 Active, Android 5.0.1 as wifi direct guest, both on 0.15.90.8 with other network connections disabled.
@unknown Does this problem happen on your device everytime and even if you start a new world? I could not reproduce at first, but have now experienced this once (I tapped an item in inventory, it selected. Then I tapped anempty hotbar slot and it became selected too (I expected the item to move to that slot, it did not) So I tapped the selected slot again and the item moved. It is not yet clear to me what is causing this bug to start happening, if you could investigate when it starts happening (presuming it doesn't happen all the time in every world you play) and post back, that would be helpful.