Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Websites not loading properly after Android 12 update

  • 8 replies
  • 2 have this problem
  • 1 view
  • Last reply by Vel

more options

Recently my Google pixel phone got the Android 12 update. Since then I'm having issues with Firefox loading websites like Walmart, Sams club, Lowes. It seems to be serving the desktop versions and it is hard to navigate. The toggle switch for "Desktop Site" is off, so not sure why it is showing the desktop site. The attached images show how Walmart site shows in Chrome and Firefox. My firefox version is 94.1.2. If anyone has any suggestions, please let me know.

Recently my Google pixel phone got the Android 12 update. Since then I'm having issues with Firefox loading websites like Walmart, Sams club, Lowes. It seems to be serving the desktop versions and it is hard to navigate. The toggle switch for "Desktop Site" is off, so not sure why it is showing the desktop site. The attached images show how Walmart site shows in Chrome and Firefox. My firefox version is 94.1.2. If anyone has any suggestions, please let me know.
Attached screenshots

Chosen solution

The issue is resolved, now on Firefox 95.1.0.

Read this answer in context 👍 0

All Replies (8)

more options

Here is the Chrome screenshot for comparison

more options

Hi

Which add-ons are you using?

What level of enhanced tracking protection are you using?

more options

Thanks for your reply Seburo! I have no add-ons. I have the "Standard" option selected for enhanced tracking protection.

more options

Hi

Are you using any kind of additional security or VPN app on your device?

Modified by Paul

more options

No additional security or VPN on my phone. I tried uninstall and re install Firefox. Hasn't helped.

more options

Which Pixel device do you have?

more options

Pixel 3a XL

more options

Chosen Solution

The issue is resolved, now on Firefox 95.1.0.