Yes, that is actually what I am doing. Using chrome without acceleration and edge for anything that needs it.
Surface Pro X, Issues with Google Maps
I am using:
Device name *******
Processor Microsoft SQ1 @ 3.0 GHz 3.00 GHz
Installed RAM 8.00 GB (7.54 GB usable)
System type 64-bit operating system, ARM-based processor
Pen and touch Pen and touch support with 10 touch points
Recently, after an update, when using Google maps, the names of the locations disappear.
Initially the maps shows all the detail
But few seconds later when everything is loaded, the town names disappear:
I thought this was a Chrome issue, thus cleared the cache etc. but this not fixed the issue.
I then tried different browsers MS Edge and Firefox. They all have the same issue.
I contacted Google and provided the above info, but they believe this is o/s issue and suggested I contact MS.
Is anyone able suggest how I can fixed this problem?
EDIT: Removed personally identifiable information (PII) from post.
Surface | Surface Pro | Install and update
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
82 answers
Sort by: Newest
-
Anonymous
2023-09-20T17:11:24+00:00 -
Anonymous
2023-09-20T16:56:50+00:00 Turning hardware acceleration off on chrome resolves the problem with google maps. However, that will cause other issues. If you use backgrounds on conference calls, they won't work without hardware acceleration turned on. So, you need to do without, or switch the setting back and forth.
Just a thought and suggestion for the interim until this issue has an actual fix:
- pick one browser to be the google maps browser and turn off (and leave off) the hardware acceleration (I confirmed this solution also works for Edge, and I'd assume it should any other Chromium browser as well - Opera, Vivaldi, Brave, etc, or straight up Chromium itself).
-Leave it on for the rest of the installed browsers, and use those browsers for everything except google maps.
That's what I would do, and some of you may already be doing this. I've seen this kind of issue with other web apps in the past at my place of employment, with turning off hardware acceleration in chrome being the fix, at least for the short term. It's annoying, but having other browsers available for everything else eases the pain a bit.
-
Anonymous
2023-09-20T16:11:20+00:00 Turning hardware acceleration off on chrome resolves the problem with google maps. However, that will cause other issues. If you use backgrounds on conference calls, they won't work without hardware acceleration turned on. So, you need to do without, or switch the setting back and forth.
-
Anonymous
2023-09-20T16:11:01+00:00 Turning hardware acceleration off on chrome resolves the problem with google maps. However, that will cause other issues. If you use backgrounds on conference calls, they won't work without hardware acceleration turned on. So, you need to do without, or switch the setting back and forth.
-
Anonymous
2023-09-20T15:29:21+00:00 I still have a hard time believing Google that this is solely Microsoft's fault, if it's their fault at all. It's Google's app after all; I'd bug the heck out of them. Seems ultimately they're the ones that should be fixing it. Of course, they still haven't bothered to release a native ARM version of Chrome (windows or linux) except for ChromeOS.
But what's curious is the issue doesn't seem to happen when running Firefox via Ubuntu WSL (windows subsystem for linux) on my Surface Pro X (more specifically "Mozilla Firefox Snap for Ubuntu"). Not sure if any of you would want to dive into the linux world, but it is an option now that gui apps running in WSL is possible.