Dom Cote
- Domc
- domc
- Europe/Stockholm
- Yes
- No
Minecraft will not let me connect to Realms of any kind if I try to use the built-in LTE 4G cellular modem on my always connected Snapdragon PCs. It only says "You must be connected to WiFi to play with your friends". I can't find a setting in Minecraft to override or enable this. Minecraft plays wonderfully otherwise. Every other app uses LTE 4G cellular with out problems. To me, Minecraft blocking cellular connections seems almost intentional, but it is so annoying and weird that it looks plain broken to me - so I'm filing this as a bug.
btw. playing in Realms via cellular tethered WiFi hotspot works fine. But is annoying, because 1) I need to enable it, 2) I have to share bandwidth with my cell-phone's services and 3) it increases latency 4) it rapidly drains my phone's battery.
Change requests in descending priority:
- Don't check for cellular. Just play. Assume we know what we're doing.
- Check whether cellular is set to "metered". If yes, ask user to change or warn and ask whether to play anyways.
- Add a toggle to game settings to let me play on cellular.
In this day and age of huge or unlimited data plans and cellular connectivity becoming more common on Windows PCs too, please let us use it to play Minecraft wherever and whenever we like.
Since late last week, Minecraft crashes on start and is impossible to play.
Can't explain what caused it. One evening, I was playing, the next day it had stopped working. It doesn't look as if any updates came through that night.
After first install/app reset, the app closes silently right after connecting to my Microsoft account.
Repeating it later, it silently closes during the loading splash screen.
Reproduction is easy: Get a Snapdragon device (Surface Pro X) and try it. 100% reproducible.
And yes, I tried the usual:
- un-install + re-install --> no fix
- reset app --> no fix
- check for updates --> no fix
Render Distance limited to 5, 6 or 7 on mainstream+premium ARM Snapdragons.Super
The new update changed my render distances to unacceptably low values. On my ARM Snapdragons, I am unable to override the render distance anymore, ruining my gameplay. I simply can't see far enough anymore. Details:
On my Celeron N4020, Minecraft sets the RD default to 10. It is impossible to play Minecraft on that device period, even with the lowest graphics settings possible. Oddly, Minecraft lets me push RD up to 30
on this device, which lets me count seconds per frame...
My SQ1 Snapdragon (Surface Pro X) is quite powerful and I used to play Minecraft with an RD of 24
and still got a very decent gaming experience, even when serving to other players.
Even my SD850 worked well between 14 and 18.The new update locks render distance to either 5, 6 or 7 on my Snapdragons. I BET that's an artifact of android / ARM versions, targeted at low power Android phones and tablets. Even if it isn't, this can only be considered a bug, since something won't let me override the RD setting on my Snapdragons, whereas on the crap*iest Intel I can find I can override with no issues.
Please let me freely choose my render distance on my Snapdragons, just like on every other Windows platform.
Steps to repro: Get a Windows on Snapdragon device and try it. 100% consistently reproducible and also 100% not sensible.
Thanks°
The new update changed my render distances to unacceptably low values. On my ARM Snapdragons, I am unable to override the render distance anymore, ruining my gameplay. I simply can't see far enough anymore. Details:
On my Celeron N4020, Minecraft sets the RD default to 10. It is impossible to play Minecraft on that device period, even with the lowest graphics settings possible. Oddly, Minecraft lets me push RD up to 30
on this device, which lets me count seconds per frame...
My SQ1 Snapdragon (Surface Pro X) is quite powerful and I used to play Minecraft with an RD of 24
and still got a very decent gaming experience, even when serving to other players.
Even my Snapdragon 850 worked well between 14 and 18.The new update locks render distance to either 5, 6 or 7 on my Snapdragons. I BET that's an artifact of android / ARM versions, targeted at low power Android phones and tablets. Even if it isn't, this can only be considered a bug, since something won't let me override the RD setting on my Snapdragons, whereas on the crap*iest Intel I can find I can override with no issues.
Please let me freely choose my render distance on my Snapdragons, just like on every other Windows platform.
Steps to repro: Get a Windows on Snapdragon device and try it. 100% consistently reproducible and also 100% not sensible.
Thanks°








One more comment, we at Microsoft are launching an entire new fleet of Snapdragon 850 and 7c based education devices worldwide. I somehow suspect they'll have the same issue with MCEE, correct? I'd ask to get this bug's status changed from "postponed" back to "open" and actually expedite it. There will be literally zillions of panicked support requests from educators pouring in otherwise... thanks!
Some additional information:
Minecraft only seems to crash when I try to connect to my xbox account. When I don't connect to xbox after reinstalling/resetting, Minecraft starts and runs just fine.
It looks like the xbox account/connection is triggering the crash, although I'm not sure it's the root cause.
Other games run fine when signed in to xbox.
@James, Minecraft stopped working on ARM64 a few weeks ago. Looks like xbox accounts trigger the crash. When you reinstall/reset the app and DON'T log in to xbox, it runs fine.
There is another bug open here:
MCPE-97724Minecraft stopped working on Surface Pro X (and other Snapdragons, too?) - Jira (mojang.com) Feel free to vote for that bug, too!@goldenHelmet All Snapdragon Chipsets that support Windows (835, 850, 7c, 8cx, SQ1) have DX12 capable GPUs. So while this ticket is indeed about Surface Pro X, it impacts ALL current and coming Snapdragon devices.
I'm betting this is happening because MC is one of the few native ARM apps for Windows. It runs in native ARM32 code because it was designed as a Universal Windows Platform UWP app that could run on Snapdragon-based Lumia smartphones. However, since Windows Mobile and Lumia are dead, supporting ARM32 code probably doesn't make much sense anymore and Mojang doesn't see a business case for porting to ARM64. Am I right?
Sadly, that ARM32 code is the reason why MC runs so awesomely well on all the Snapdragons I've tested. Even the 835 drives a FHD panel at high GPU setting without breaking a sweat.
btw. I tried MC Education Edition on my SQ1, and it runs as an emulated x86 app. But the performance is truly awful compared to the ARM32 native version. It's one of the few emulated apps that suffer noticeably (like Teams).
At IGNITE, Microsoft announced "App Assure" for ARM64 devices. Microsoft now guarantees 100% app compatibility on ARM64 and will help customers make their apps run on ARM free of charge. Perhaps Mojang could reach out? 😉
App Assure now assists with Windows 10 on ARM64 PCs - Microsoft Tech Community
Umm, please wait before anyone closes this. Give it a week or two.
Again, please give it a week or two. 😉
Anyone seen this yet? 👍

Awesome team! Just got the 1.16.100 update and I can play again. 👍 Thanks for fixing this. 😃
Strange tho: I only get a small subset of graphics options vs. previously. For example: I can't switch on Anti-Aliasing and the rendering distance is either only 5 or 6. This restricts my visibility noticeably. I used to have these all maxed out and still got excellent performance on my Snapdragons. But I'll open a separate bug for this.
Hey team - just got 1.16.20002.0 and my Rendering Distance is back! 👍 I can finally see in to the distance again. 😊 still not getting anti-aliasing, but i can live with that. Thanks for fixing this!
Same for me - MC only lets me pick 5, 6 or 7 render distance on my Windows Snapdragons. I used to play with RD set to 24 on my Surface Pro X (SQ1) and 18 on my Snapdragon 850.
But on my puny little Celeron N4020, MC defaults to render distance 10, and lets me override to 30!? Minecraft is unplayable on this device on any setting. But the Surface Pro X cranks out a really decent experience, even while serving other players. Makes no sense at all to limit on powerful devices, but not to on better calculators...
Please let me override the suggested/default RD.
I also saw that comment in a email, but can't see it here now for some reason.
In any case: I just installed MC on a CELERON N3710 (Braswell!).
The default setting on this stone age heap of junk is 10 chunks and 4x Anti-Aliasing. 🤪
Fun fact: at 10 chunks and 1x AA, the performance isn't even that bad - it's playable.
But my Pro X (SQ1) is limited to 7? Which has a GPU that is 10x more powerful than the 3710?
Heck, even my mid-range Snapdragon 850 Windows PC has 4-5x the GPU power of the 3710...
So if the limitations are intentional, they make NO sense at all.
To me, it looks like someone at Mojang simply programmed a check for "mobile" processors in the broadest sense and slammed a hard limit on them that users can't override.
Trying to enforce a good gaming experience this way WILL FAIL.
Dear Mojang, the solution is simple, go ahead and set defaults you think make sense, but let us change them in ways we want - just like any other decent game out there lets folks tweak graphics settings for every person's own best experience.
Thanks!
Hi Justyna, thanks for asking. Here is a screenshot when I try to install from the store. This error has been around for at least 2 months now - when I tried to re-install on my Surface Pro X (SQ1). Initially, I thought it might be a glitch, so I ignored it until I had time to try again. Which is now.
A video isn't really going to show much more tbh.
As you can see, the "install" button is enabled. I have both an active Game Pass Ultimate Subscription (connected to the MS account the store is signed in to) and I also purchased MC long before I got XBGPU.
When I click the install button, nothing happens for a few seconds, then the Store throws this message:
When I try to install the launcher manually from minecraft.net/download, I get this error:

This is new btw - up to last week, I'd also just get an unspecific error.
Switching to the store only causes the first error, so fixes nothing.
I'm happy to provide a trace, if you can tell me how I can do that for you.
Dom