oceanclub 10 Posted January 15 Posted January 15 Has anyone noticed the app being perceptibly slower recently? I'm running it on both a Samsung S20 FE, and a Lenovo Tab P11 Pro, connecting via WiFi to a Windows server on the same network. I have ports forwarded on my router in case. The app takes 10 seconds to start up. Then if I click into something to play, I get a black screen up to 10 seconds, sometimes longer.
Luke 39008 Posted January 15 Posted January 15 Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!
oceanclub 10 Posted January 15 Author Posted January 15 HI Luke, it's not the media playback speed that is the issue, but the speed of the actual GUI. For example, from the home page, I just tried My Media > Music, and got a black screen which stayed black even after 30 seconds. (Returning to the home screen, clicking around and then going back fixed it.) Is it a caching issue maybe?
Luke 39008 Posted January 15 Posted January 15 Hi, please attach the emby server log from when the problem occurred:; How to Report a Problem Thanks.
oceanclub 10 Posted January 15 Author Posted January 15 Here you go: 2025-01-15 22:56:33.631 Info App: Udp message sent to [::ffff:192.168.0.130]:45305 2025-01-15 22:56:33.632 Info App: Udp message sent to [::ffff:192.168.0.130]:45305 2025-01-15 22:56:37.135 Info Server: http/1.1 POST http://192.168.0.52:8096/emby/Sync/data. Source Ip: emby_remote_ip, UserAgent: okhttp/4.11.0 2025-01-15 22:56:37.137 Info Server: http/1.1 Response 200 to emby_remote_ip. Time: 2ms. POST http://192.168.0.52:8096/emby/Sync/data 2025-01-15 22:56:43.023 Info Server: http/1.1 POST http://192.168.0.52:8096/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby for Android&X-Emby-Device-Name=SM-G780G&X-Emby-Device-Id=4293bd03dd749d56&X-Emby-Client-Version=3.4.20&X-Emby-Token=x_secret1_x&X-Emby-Language=en-ie&reqformat=json. Source Ip: emby_remote_ip, UserAgent: Mozilla/5.0 (Linux; Android 13; SM-G780G Build/TP1A.220624.014; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/131.0.6778.260 Mobile Safari/537.36 2025-01-15 22:56:45.173 Info Server: http/1.1 Response 204 to emby_remote_ip. Time: 2150ms. POST http://192.168.0.52:8096/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby for Android&X-Emby-Device-Name=SM-G780G&X-Emby-Device-Id=4293bd03dd749d56&X-Emby-Client-Version=3.4.20&X-Emby-Token=x_secret1_x&X-Emby-Language=en-ie&reqformat=json 2025-01-15 22:56:46.823 Info App: Sqlite: 284 - automatic index on LastWatchedEpisodes(SeriesPresentationUniqueKey) 2025-01-15 22:56:52.707 Info Server: http/1.1 Response 500 to 127.0.0.1. Time: 3ms. GET http://localhost:8096/web/modules/themes/dark/theme.json?v=4.8.10.0 2025-01-15 22:56:52.787 Info Server: http/1.1 POST http://localhost:8096/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=77727f14-f681-4b39-be4d-649716f78bfe&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret3_x&X-Emby-Language=en-gb&reqformat=json. Source Ip: 127.0.0.1, UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0 2025-01-15 22:56:52.788 Info Server: http/1.1 Response 204 to 127.0.0.1. Time: 1ms. POST http://localhost:8096/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=77727f14-f681-4b39-be4d-649716f78bfe&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret3_x&X-Emby-Language=en-gb&reqformat=json 2025-01-15 22:57:07.423 Info Server: http/1.1 POST http://localhost:8096/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=77727f14-f681-4b39-be4d-649716f78bfe&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret3_x&X-Emby-Language=en-gb&reqformat=json. Source Ip: 127.0.0.1, UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0 2025-01-15 22:57:07.424 Info Server: http/1.1 Response 204 to 127.0.0.1. Time: 1ms. POST http://localhost:8096/emby/Sessions/Capabilities/Full?X-Emby-Client=Emby Web&X-Emby-Device-Name=Firefox Windows&X-Emby-Device-Id=77727f14-f681-4b39-be4d-649716f78bfe&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=x_secret3_x&X-Emby-Language=en-gb&reqformat=json
Luke 39008 Posted January 16 Posted January 16 Hi there, please attach the complete emby server log file. thanks.
oceanclub 10 Posted January 21 Author Posted January 21 Sorry about delay, here you go. embyserver.txt hardware_detection-63873057157.txt
oceanclub 10 Posted January 28 Author Posted January 28 Was wondering if any news on this? I don't think it's a LAN problem or particular to a device as (a) the problem shows up on Emby Connect as well, (b) if I say use VLC to stream a video from my PC to my phone, there's no delay or lag there, and (c) both my Samsung phone and Lenovo tab show the same issues. Regards, Paul
Luke 39008 Posted February 3 Posted February 3 Hi, I don't see anything obvious yet. Are you still having an issue with this?
Solution oceanclub 10 Posted February 4 Author Solution Posted February 4 (edited) Hi @Luke, I was in the process of writing a reply and as I did, I did some troubleshooting and fixed it! It's very edge case. The summary: I had two entries in my router's port forwarding for port 8096 - the default port number for LAN access. One was added manually by me; one was automatically added by UPnP. Even though _both_ were to the same internal IP address for my server, when I deleted the manual one, everything suddenly worked. Troubleshooting: My server is running on Windows (still on 7!), and I access it primarily via an XBox One X, both on Ethernet. That works absolutely fine. From my phone, rather than using the Android app, I browsed to the "In-Home (LAN) access" URL for my server. It obviously connects, as I see the Emby logo, but that's all that happens. There's no progress beyond the logo. However, when from my phone, I turned off my wifi so only connecting via mobile data, and accessed the "Remote (WAN) access" URL, that works fine, no slowdown. So I checked checked various settings: * On my router, I can see the correct ports are forwarded * On my firewall, I can see embyserver.exe is enabled for both TCP and UDP. But then as described above, I saw I had two rules for 8096. One manual and one automatic. Even though both did the same thing, when I deleted the manual one - hey presto. I checked both the "In-Home (LAN) access" URL on my phone, and the Android app, and both work fine now. Edited February 4 by oceanclub 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now