-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Pixel Phones won't load Web UI or Android 14 Issue #3456
Comments
Please connect your phone to your PC, open browser's developer tools and monitor what's happening in network tab and console log. |
192.168.90.5.zip |
|
Thank you. It seems "onLoad()" does not get executed when it should. Possibly due to delay. EDIT: Can you use some other phone/tablet or PC? |
If you can compile yourself, please try compiling |
Okay I will try and give that a shot. Will need to do some research on compiling |
I'm having the same issue on a Samsung S23 Ultra with Android version 13. |
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. :( |
Fire up developer tools for Android browser and check for possible error messages. |
Drive-by comment: 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. |
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. |
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
The text was updated successfully, but these errors were encountered: