Expanded App section with comprehensive guide #91
Conversation
Zaarrg
left a comment
Zaarrg
left a comment
There was a problem hiding this comment.
Amazing work on this PR! I’ve left some comments with suggestions to help clarify a few sections, and I also noticed a couple of details that weren’t entirely correct—so I’ve explained the correct information in my comments as well. Once these are addressed, I think this will be good to go!
| 1. **Try F5 first** - Refreshes the page and fixes many display issues | ||
| 2. **Try Ctrl+F5** - Clears cache and fixes persistent problems (including volume slider) | ||
| 3. **Restart the app** - Close completely via Task Manager and restart | ||
| 4. **Reboot PC** - Fixes sleep-related streaming server issues |
There was a problem hiding this comment.
Reboot wont really help with anything. If pc goes to sleep the Stremio Service (Server.js) is closed. Meaning restarting the app is enough as this starts the Stremio Service again.
| > **⏳ Note:** A default stremio-settings.ini can be found [here](https://github.com/Zaarrg/stremio-desktop-v5/blob/webview-windows/utils/stremio/stremio-settings.ini) | ||
| - ❌ **App Errors & Troubleshooting** |
There was a problem hiding this comment.
Lets use a level 2 heading this way it can be directly linked to: ## ❌ App Errors & Troubleshooting
|
|
||
| - 📱 **"Device suddenly not support stream" Error** | ||
| - **Immediate fix:** Restart the application completely | ||
| - **Root cause:** Occurs after computer sleep/hibernate |
There was a problem hiding this comment.
Root cause is the Stremio Service (server.js) not starting. In Stremio under settings > Streaming the url for the server is shown (localhost:11470). Meaning either the server did not start at all, so a app restart can help.
Or a server was already running on port 11470 e.g. someone has stremio 4 running as well. Meaning closing any other stremio app running then restarting the app will fix it.
One other root cause might be the server starting too late. This means the app starts trys to connect to the streaming url specified in settings but its not running yet. This then can be fixed by clicking on the Reload button in the settings so it trys to connect again.
(Sleep/hibernate seems to close the server or the connection that is why the sleep causes the not support msg)
| - **If offline:** Use Task Manager to close all Stremio processes, then restart | ||
|
|
||
| - 🌐 **Web UI Connection Issues** | ||
| - **Cannot reach Web UI:** Verify you can access the web interface hosted [here](https://zaarrg.github.io/stremio-web-shell-fixes/) |
| - Close other applications | ||
| - Reduce ``ThumbFastHeight`` setting or set to ``0`` | ||
| - Update graphics drivers | ||
| - **Stuttering/Buffering:** |
There was a problem hiding this comment.
Also might be worth adding to check the hoster or url a user is trying to play. Most of the time buffering is caused by the hoster e.g. real debrid/torrentio. I also saw cases in which the isp was throttling the connection. Meaning even tho the hoster was fine users still got buffering as the isp detected the streaming.
| - 🚀 **App Won't Start / Instantly Closes** | ||
| - **Check error logs:** ``portable_config\errors-{date}.txt`` for specific error messages | ||
| - **WebView2 Issues:** |
There was a problem hiding this comment.
Also might be worth adding as troubleshoot step to use the portable version of the app. As the portable version comes with webview2. As there is the case users with custom windows iso like tinyOS or some kinda of optimized windows version have webview fully disabled as the edge browser is almost always stripped away. Meaning even installing it via the installer wont help as other components are fully missing from the os. So the only working way is the portable version in such cases.
Maybe could be also added under the Advanced Troubleshooting section.
2 participants
This PR addresses issue #84 by expanding the existing "App Errors" section with comprehensive troubleshooting information. The expanded section includes detailed solutions for black screen issues, fixes for "device not support stream" errors after sleep mode, WebView2 GPU acceleration troubleshooting, volume control issues, and advanced troubleshooting procedures. All solutions are based on real user issues and incorporate maintainer-provided fixes while following the existing documentation style.