Still affecting the newest version: 1.1.3
Still not fixed in 1.1.1... I saw a YouTube video that showed an Android device using it, but they connected while they were in the game. On a kindle, you cannot do that because it puts the game in the background whenever you want to mess around with Bluetooth (which includes connecting to the controller) so it can't recognize it. I'll suggest a better way to handle the game knowing if a controller is connected or not: check when the game is started. Seemed obvious enough to me. Actually, I would think that that would've been how you did it in the first place.
https://youtu.be/KyYBGfb8aHA
This is a video I made to show the bug. Maybe it could help?
If this is necessary to know, Fire OS 4.4.5.2
Confirmed for 1.10.2
Also affects slabs.
Last screen shot was fixed I believe, but still. How did that happen.
Affects 0.14.0 b5
No, it has been fixed.
It seems to be fixed in 0.13.1 for Amazon Kindle Fire HD.
I think I figured out what happened. So I tested it with my friend by having him put his device on airplane mode. I stood in the portal and had him put airplane mode on, I stood in the portal and had him turn airplane mode off and got out and back in the portal, and I lost half health. I think the longer you stand in the portal when the host or you have lost Wi-Fi the more damage you take. It might be suffocation damage, either from the obsidian, or it is thinking the portal is a full block.
Fixed (I'm on 0.12.3, but I think it was fixed in 12.2)
I will test, but I am on 0.12.3 Ok so, if I did it right, it has been fixed. 😺
I don't know. But I think it might have been fixed. It rarely happened. I'm almost positive it was when the host lost wifi and gained it back, hence why I had said that it didn't teleport me the first time. I deleted it because I thought it wasn't important. I will reply once I try something. Sorry for taking forever to reply. Didn't see the email somehow.
Yes, it has been in the game since the full release of 0.11.0 if that helps.
No, it does not. It has been fixed. 😊
Oh my gosh. Hahahaha. I just realised that I put 10/9 instead of 9/10. Huge fail lol. fixed it
That's what I basically said. It thinks the button is not there, so when you tap and hold the button, it basically thinks your just tapping and holding the screen like the button is not there, which what I previously mentioned, is the only way to get in a minecart. Tapping a holding the screen does the alternate action (getting in a minecart instead of punching it, shearing seep instead of punching it, ect.)
I got a screenshot, and it turns out, it's flickering green!
This bug is still in the full release of 0.12.1
I think it is something to do with Fire OS's inability to multitask. When you have an app open, it freezes all other apps, but keeps them open. Minecraft might not recognize the controller due to the bluetooth device handler being frozen. I know that the kindle definitely has background tasks, but only with important apps, such as the system, or keyboard. Furthermore, I have tried to turn off the controller and turning it back on again, to see if it would connect, and allow Minecraft to recognize it. It wouldn't connect, most likely because the bluetooth device handler is frozen.
(I will mention, I have no idea if bluetooth has a device handler, but that seems like the only way a bluetooth device wouldn't be able to unconnect and reconnect, but is still usable).