Multiplayer mode, does not find server -- Android 4.1.2 devices
This is MCPE 0.5.0 running on Android 4.1.2 (Jelly Bean)
(verified with MCPE 0.4.0 same problem exists, not a regression in 0.5.0)
Also verified Android 4.1.2 with direct WiFi connection between devices, has the same problem. The tablets we have don't have 3G and cannot set up hotspot connection.
Went back to Android 4.0.4 verified with MCPE 0.4.0 and MCPE 0.5.0 same issue does NOT happen. Flashed ICS 4.0.4 on the tablets, MCPE can connect immediately. Flashed back Android 4.1.2 on the devices, devices don't find each other.
In all cases all servers are set to visible.
Other Android 4.1 UDP related comments with no solutions, here: http://stackoverflow.com/questions/12904703/udp-packets-seems-to-be-blocked-by-android-4-1
Let me know if it's possible to trace the failure if it really is a UDP issue.
Created Issue:
Multiplayer not finds server -- Android 4.1.2 devices
This is MCPE 0.5.0 running on Android 4.1.2 (Jelly Bean)
(verified with MCPE 0.4.0 same problem exists)
Also verified that on Android 4.1.2 with direct wifi connection between devices, has the same problem.
Android 4.0.4 does not have same issue. Flashed ICS 4.0.4 on the tablets, MCPE can connect immediately. Flashed back 4.1.2, devices don't find each other.
In all cases all servers are set to visible.Problem might be related to this: http://code.google.com/p/android-rcs-ims-stack/issues/detail?id=72#c12
Other Android 4.1 UDP related comments with no solutions, here: http://stackoverflow.com/questions/12904703/udp-packets-seems-to-be-blocked-by-android-4-1Let me know if it's possible to trace the failure if it really is a UDP issue.
Multiplayer not findsserver -- Android 4.1.2 devicesMultiplayer mode, does not find server -- Android 4.1.2 devices
This is MCPE 0.5.0 running on Android 4.1.2 (Jelly Bean)
(verified with MCPE 0.4.0 same problem exists)
Also verified that on Android 4.1.2 with direct wifi connection between devices, has the same problem.Android 4.0.4does not have same issue. Flashed ICS 4.0.4 on the tablets, MCPE can connect immediately. Flashed back4.1.2, devices don't find each other.
In all cases all servers are set to visible.Problem might be related to this: http://code.google.com/p/android-rcs-ims-stack/issues/detail?id=72#c12
Other Android 4.1 UDP related comments with no solutions, here: http://stackoverflow.com/questions/12904703/udp-packets-seems-to-be-blocked-by-android-4-1Let me know if it's possible to trace the failure if it really is a UDP issue.
This is MCPE 0.5.0 running on Android 4.1.2 (Jelly Bean)
(verified with MCPE 0.4.0 same problem exists, not a regression in 0.5.0)
Also verified Android 4.1.2 with direct WiFi connection between devices, has the same problem. The tablets we have don't have 3G and cannot set up hotspot connection.Went back to Android 4.0.4 verified with MCPE 0.4.0 and MCPE 0.5.0 same issue does NOT happen. Flashed ICS 4.0.4 on the tablets, MCPE can connect immediately. Flashed back Android 4.1.2 on the devices, devices don't find each other.
In all cases all servers are set to visible.Problem might be related to this: http://code.google.com/p/android-rcs-ims-stack/issues/detail?id=72#c12
Other Android 4.1 UDP related comments with no solutions, here: http://stackoverflow.com/questions/12904703/udp-packets-seems-to-be-blocked-by-android-4-1Let me know if it's possible to trace the failure if it really is a UDP issue.
This is MCPE 0.5.0 running on Android 4.1.2 (Jelly Bean)
(verified with MCPE 0.4.0 same problem exists, not a regression in 0.5.0)
Also verified Android 4.1.2 with direct WiFi connection between devices, has the same problem. The tablets we have don't have 3G and cannot set up hotspot connection.Went back to Android 4.0.4 verified with MCPE 0.4.0 and MCPE 0.5.0 same issue does NOT happen. Flashed ICS 4.0.4 on the tablets, MCPE can connect immediately. Flashed back Android 4.1.2 on the devices, devices don't find each other.
In all cases all servers are set to visible.Problem might be related to this: http://code.google.com/p/android-rcs-ims-stack/issues/detail?id=72#c12
Other Android 4.1 UDP related comments with no solutions, here: http://stackoverflow.com/questions/12904703/udp-packets-seems-to-be-blocked-by-android-4-1Let me know if it's possible to trace the failure if it really is a UDP issue.
is duplicated by
Hum, so it doesn't work to either host or join games with these combos? I'm running 4.1.2 myself (although a custom rom) and I have not had any issues. It's not clear form you post but does this only happen when the 4.1.2-device is hosting the wifi as well?
Johan, no, I could not get multiplayer to work with 5.1.2. I have tried several 5.1+ custom roms, I had the same issue with all. Going back to 4.0.4 solved the problem. When hosted the WiFi on the 5.1.2 ROM (that's what I referred to as direct connection as that's what I think they call it in the settings in Android), the same happens, no connection can be made.
Is there a way to dump some sort of a trace from MCPE to see what's going on while scanning for devices that can help figure out what's happening?
Tomy, I assume nothing shows up in logcat?
Good idea, I have not checked the logs yet. I will reflash 4.1.2 on the devices today because they are on 4.0.4 right now, and try it out and let you know.
Is this still a concern in the current Minecraft version? If so, please update the affected versions in order to best aid Mojang ensuring bugs are still valid in the latest releases/pre-releases.
Can only use first item as building tool through LAN world over Wifi. It is okay for the owner to build with all item boxes, but not the person who joins.
Cleaning up all the old issues - please reply if this affects 0.9.3.
In build 3,It always says:"You must be connected to WiFi to join your friends" even though I'm the one hosting the Local WiFi Hotspot and the same thing happens to my siblings even though they are connected to my Local WiFi Hotspot! Please fix this,multiplayer is very important to minecraft
We can't join in each other's worlds no matter what we try
@James or Am I? Please create a new ticket so we can deal with your bug separately.