WLED icon indicating copy to clipboard operation
WLED copied to clipboard

Google Pixel Phones won't load Web UI or Android 14 Issue

Open nsaneadmin opened this issue 1 year ago • 12 comments

What happened?

Since I update to version 14 the WLED Native app and chrome android browser gets stuck on Loading Web UI. I've reflashed back to 13 and everything will work again on my phone, but once I flash back to 14 the web UI gets stuck again. I have no issues loading it on other phones and PC in my home just my Pixel Phones. It could also be an issue with Android 14 the other devices I have used are on android 13 and lower.

If I open a browser with IP.com/settings every works fine from my phone also it just won't load the main UI.

To Reproduce Bug

Use and Google Pixel 8 or 6 with Android 14

Expected Behavior

I expect the web UI to load, but it just sticks at loading.

Install Method

Binary from WLED.me

What version of WLED?

Installed version: WLED 0.14.0 (ESP32-D0WDQ5 build 2310130)

Which microcontroller/board are you seeing the problem on?

ESP32

Relevant log/trace output

No response

Anything else?

Please let me know if you need any screenshots or any other information.

Code of Conduct

  • [X] I agree to follow this project's Code of Conduct

nsaneadmin avatar Oct 18 '23 04:10 nsaneadmin

Please connect your phone to your PC, open browser's developer tools and monitor what's happening in network tab and console log. Without his information we cannot determine where the problem lies.

blazoncek avatar Oct 18 '23 05:10 blazoncek

192.168.90.5.zip attached is a har file

nsaneadmin avatar Oct 18 '23 05:10 nsaneadmin

Please connect your phone to your PC, open browser's developer tools and monitor what's happening in network tab and console log. Without his information we cannot determine where the problem lies.

image

nsaneadmin avatar Oct 18 '23 05:10 nsaneadmin

192.168.90.5.zip attached is a har file

image

nsaneadmin avatar Oct 18 '23 05:10 nsaneadmin

Thank you. It seems "onLoad()" does not get executed when it should. Possibly due to delay. Please tap on the settings cog and then back. Or try refreshing several times.

EDIT: Can you use some other phone/tablet or PC?

blazoncek avatar Oct 18 '23 05:10 blazoncek

Thank you. It seems "onLoad()" does not get executed when it should. Possibly due to delay. Please tap on the settings cog and then back. Or try refreshing several times.

After hitting refreshing for a few minutes it finally loaded! Screenshot_20231017-233856

nsaneadmin avatar Oct 18 '23 05:10 nsaneadmin

If you can compile yourself, please try compiling 0_15 branch where I tried to implement request throttling to prevent ESP8266 being drained of resources. It may help in this particular case.

blazoncek avatar Oct 18 '23 05:10 blazoncek

Okay I will try and give that a shot. Will need to do some research on compiling

nsaneadmin avatar Oct 18 '23 05:10 nsaneadmin

I'm having the same issue on a Samsung S23 Ultra with Android version 13.

browsean avatar Oct 18 '23 14:10 browsean

If you can compile yourself, please try compiling 0_15 branch where I tried to implement request throttling to prevent ESP8266 being drained of resources. It may help in this particular case.

I've compiled the esp32dev for version 0.15.0-a0 and still seem to run into the same issue.

If I use any other PC or Android phone I don't seem to have the issue. :(

nsaneadmin avatar Oct 20 '23 01:10 nsaneadmin

Fire up developer tools for Android browser and check for possible error messages.

blazoncek avatar Dec 14 '23 06:12 blazoncek

Drive-by comment: I've used a self-compiled WLED on -S3 from source somewhere between 0.14.1b3 and 0.14.1 on my Pixel 5a rather heavily and it's seemed flawless.

Since I'm just reading issues in bulk, @blazoncek blazoncek's comment above about the browsers just more aggressively hammering the connection and stressing out AsyncTCP, it seems possible that https://github.com/Aircoookie/WLED/pull/3726/files will make the problem better or worse (hepful, I know...) as it largely replaces the dead and less-than-robust net handlers with an actively maintained module that claims to hold up better under stress.

On the third hand, it looks like one of the posters (not OP) is using the 8266 and PsychicHTTP, like much of the modern world, has just run out of gas on 8266 so it might be better at handling stress, but you may be the first person to ever try it on 8266. Since code generally doesn't get smaller over time as robustness is added, it may just move around a breaking point.

So it's possible that something in trunk has already fixed this - my Pixel is fine with very late 0.14 betas. If you still have problems, it may be worth following up on #3726 and see if it makes things better or worse and then participating in that code review/discussion at #3724.

robertlipe avatar Jan 29 '24 09:01 robertlipe

Hey! This issue has been open for quite some time without any new comments now. It will be closed automatically in a week if no further activity occurs. Thank you for using WLED! ✨

github-actions[bot] avatar May 28 '24 12:05 github-actions[bot]