I can further confirm this for testing in the new release 1.21.1 and the snapshot phase of 1.21.2 Bundles of Bravery.
Here is the resource pack updated for 1.21.1:
[[1.21.1] Classic Minecraft_zip|https://www.mediafire.com/file/n0rdxbf4b9kga0d/%25C2%25A7f%255B1.21.1%255D_%25C2%25A7r%25C2%25A7aClassic_%25C2%25A7r%25C2%25A77%25C2%25A7lMinecr%25C2%25A7r%25C2%25A7a%25C2%25A7la%25C2%25A7r%25C2%25A77%25C2%25A7lft.zip/file]
I can confirm this bug for Minecraft: Playstation 4 Edition 1.20.62.
I hope this bug gets fixed soon, even though Bedrock Edition prioritizes permformance, it is not suitable for the beacon to be "performant". This issue had to have been resolved by now as many people are still coming back to this page to report the bug over and over again. Also, hardware is a lot stronger these days and there is no reason for this bug to still exist.
Updated the resource pack to version Minecraft 1.20.4:
[[1.20.4] Classic Minecraft_zip|https://www.mediafire.com/file/gvjw2uka44a952k/%25C2%25A7f%255B1.20.4%255D_%25C2%25A7r%25C2%25A7aClassic_%25C2%25A7r%25C2%25A77%25C2%25A7lMinecr%25C2%25A7r%25C2%25A7a%25C2%25A7la%25C2%25A7r%25C2%25A77%25C2%25A7lft.zip/file]
I can confirm this issue for Minecraft Pocket Edition 1.20.51.
I am using a Samsung Galaxy S23 Ultra with the Snapdragon 8 Gen2 inside.
But in this version, I am experiencing freezes, stutters, and large lag spikes. It leaves the game in a not that playable state.
Architechture of my phone + GPU + CPU
UPDATE:
This now even applies to cherry blossom wooden doors.
I can confirm this issue for version MCPE 1.19.73.
But the problem is different for me. The Switch Pro Controller doesn't get recognized by Minecraft as an input device. Rather more Minecraft recognized the Pro Controller as an Xbox-Like input that mixes with some empty buttons that show up. Because it shows RB and LB instead of ZL and ZR and the arrow buttons infinitely scroll through lists when pressed once instead of just scrolling once. All other buttons work fine.
(Device: Galaxy S21 FE)
(works normally through the android interface)
I am just going to update the ticket with the version and not keep confirming them but yes, confirmed for Minecraft 1.19.3 Release Candidate 1.
I can confirm this bug for 1.19.3 pre-release 3.
Correction for nether and bamboo wooden doors:
(These doors do use the wooden door sound, just quieter).
Grab any nether or bamboo wooden door
place them down
interact with them slowly
listen to the subtle sound of the wooden door that is played
you will find that only 3-4 are used*
*Weirdly under certain circumstances the game uses 4 sounds from the list of wooden door sounds or only 3. This behavior can be replicated by using a resource pack with set sounds (my attached one). While the game only uses 3 for the wooden doors (I'll refer to them as the classic overworld doors), the game uses 4 for the quieter sound of the nether and bamboo doors. If a texture pack is applied then it may use 5 but still not all of them.
Here is a clip (posted on YouTube) for the observed results on bamboo, classic overworld and nether doors: 1.19.3 pre-release 3 test with all wooden doors
Comparison how it should work (trusty version 1.12): 1.12 wooden door test to prove how it should work
I would like to, but the limit for attaching files is 10,00mb. I can not attach the resource pack that way.
But here is a Media Fire link to it: Classic Minecraft
(It is a private resource pack I compiled off of other packs).
UPDATE:
The Link above no longer works. Here are the two updated packs that I use.
The death screen in the current release version of Minecraft Pocket Edition 1.18.30.04 is tilting the screen and zooming in correctly.
However the damage animation isn't played while dying as demonstrated in this video below.
On the left you see a simulation, with a glitch that I managed to pull off (with correctly timing fatal poison and fall damage together into the death) of the death screen what it should look like (also what it looks like on Java Edition) and on the right you see the normal death screen on McPE Version 1.18.30.04.
Video here: GoogleDrive_MinecraftDeathScreenSimulation
Here is a more detailed version. Watch closely to what happens. Deathscreen bug + examples
I can confirm this for the latest full release 1.17.11.
Video Link (Google Drive): Nether portal.mp4
The issue still persists. I have done further testing. I will provide a video if I can get a proper one with decent quality.
As of now I can't get a lag free video ready. So I am really sorry for showing no evidence but in further testing I have investigated that the bug does still sometimes happen. It backfires the fireball but also sometimes it goes through the player, explodes before taking off into the other direction or explodes without doing any damage.
Umm, ok but this is just one ticket
I want to mention another bug with the water bucket. It is pretty much the same concept as this persons report.
Basically, if you place a water bucket while falling, to save yourself from fall damage, then for some reason. It always happens to me the water bucket deploys it's water and then instantly picks it up again.
How is this possible can someone explain?
I will test it out and make a new clip of it.
Then I will post it on my YouTube Channel.
This is now the 2nd time I add a comment to this. I fixed the issue that my video could not be watched on YouTube. So I uploaded it to Google Drive instead.
Zombie villager breaks iron door(Google Drive Upload).mp4
I hope this issue gets fixed soon. I can't revive villagers when they always escape.
Guys I found a bug where, in 1.14.0 the latest official update, zombies including zombie villagers could break iron doors. I made a video on it. I hope you can watch it. I recorded it on Android, where I played with a Ps4 controller. YouTube Video link:
I hope you are able to watch it.
So just to clarify things, this bug doesn't seem to occur in the latest version anymore, therefore it should be fixed. I tried it and it does seem to happen anymore.
So for the time being I would mark this as fixed until someone finds it maybe on a different platform but the PC.
In my old video (which is attached and set to unlisted, so it should be accessible) it was happening for an older version. Why this bug is marked as open still, is unclear to me.