webosbrew
when no internet while switching on TV and later connect to internet - youtube app does not open
YTAF Version
0.4.1
webOS Version
No response
Firmware Version
No response
OTAID
No response
SoC
No response
Model
No response
Description
I am using homebrew youtube and works good. I find a issue in that when the tv switch ON, and not connected to internet due to router not switched on. And when i switch on router and tv connects, when i open youtube app. it wont open or grey screen will be there. I have to kill it. the method i use is open kodi play some video addon and exit kodi. Then if i again open youtube it will open and ask to select my login or kids or guest. Thereafter it will continue to work.
I am able to repeat this error if i switch on TV without router hotspot. This issue persist in earlier versions too.
Priority
Annoying, but I can live with it.
To be fair, this is probably not really an issue with YTAF at all and I doubt it can be coded around as a fix. The problem is far more likely caused by the priority the software operating the SmartTV's OS chooses when connecting to a network which you will have zero chance of getting fixed by the TV manufacturer. Most TV OS will assume there is an always-on network available and will try to connect to it as a priority as soon as a power-on request is received. If it can't find the last network it successfully connected to, then it will start looking for others it can see and testing whether any of the encryption passwords it knows and has stored works. This all takes time. If the TV is cable connected (as it should be since a TV is not by definition a portable device), then there is no encryption necessary, and this all happens very quickly - almost instantly. If the TV connects by wi-fi, then there is encryption required and this takes much longer. If you, for whatever reason, regularly switch off the router providing that wi-fi signal, then this doesn't happen at all or it takes a very long time. If the TV fails to find a working network it can use in a time period the coder author deemed reasonable to wait for a usable signal, then the TV will generally give up, until a pre-determined amount of time has passed, before it tries looking again.
By switching off your router (or letting your router go into a power saving mode), you are forcing your TV to give up connecting to a network it can't find and hence anything looking to use that network, like youtube, will probably fail to load or at least become very unpredictable in its response.
The solution is to fix the non-permanent network connectivity you have. If the router has a power saving mode switched on by default, then disable it. If you are for some strange reason deliberately switching off your router when not actively using it, then stop doing that. If connecting the TV via some other cable method such as Cat-5e or EoP adapter for a non-invasive/non-destructive method rather than wifi is available, then do that. Any form of cable connection is far more reliable, secure and faster than wifi.
just a suggestion, if user opens the app, kill and load again if it is running in background. will this method solve?? bacically i am doing like that only, open kodi, play addons (jio tv), exit kodi. Then if i open YT it is getting loaded and YT works.
@vkkindia: Yes, if it fails to start, kill the running background process (WebAppMgr) and try starting it again. Works every time for me.
Just to add some info from my experience on my two LG TVs (10 & 4 years old) with the same version of YTAF installed on both.
On my webOS 3.4 TV, if YTAF cannot find the network, a page is displayed informing you of this with three options: retry, go to network settings or exit app.
The webOS 6.5 (C1) TV is the one on which YTAF hangs if the network was not connected at the time of the TV starting up, despite the network being clearly connected well before YTAF is started.
On a few occasions a similar "no network connection" page has been displayed as per webOS 3.4, but this is the rare exception and usually if the TV has been running for a while before starting YTAF. No idea why this is hit-or-miss on webOS 6.5.
All stock apps display the no network connection page if there is no connectivity.
Unfortunately YTAF is the only non-stock app I have that must have internet connectivity in order to work, so I am unable to confirm if this is the same for other jail apps that must connect to the internet to work.
I am wondering, does YTAF try to make a background connection as soon as webOS start-up has finished in order to create a cache for faster loading??
Just a thought.
This happens often to mine, as I limit internet access on different devices from the router for our family.
At times, someone will try to open this YouTube app on my unrooted TV (OLED55C4PUA) while the internet is off. When it fails, I'll restore the internet, but the app becomes unselectable from the app list. When you click on it, it won't even make the "click" animation. It's just inert, does nothing, and the problem will persist after a restart (waiting one minute while off).
Per @febman123 , I looked for a way to kill the running background process (WebAppMgr), but I couldn't find any kind of process manager, so I assume that's only possible on a rooted TV.
The only solution I've found is to uninstall and reinstall the app, which is a pain in the rear.
If it helps, this was also a problem on the previous TV firmware, not just after the most recent update.
I am doing one method to kill yt. I have kodi installed, just open and click one addon u have installed, browse that addon like play one link or so . Then exit kodi. Then try to reopen yt, it will open. Or else switch off the tv, then with internet router on, switch on the tv. It will come, no need to uninstall and install yt. These Two workways works for me.
On Thu, 9 Oct, 2025, 9:10 pm beefamato, @.***> wrote:
beefamato left a comment (webosbrew/youtube-webos#326) https://github.com/webosbrew/youtube-webos/issues/326#issuecomment-3386220668
This happens often to mine, as I limit internet access on different devices from the router for our family.
At times, someone will try to open this YouTube app on my unrooted TV (OLED55C4PUA) while the internet is off. When it fails, I'll restore the internet, but the app becomes unselectable from the app list. When you click on it, it won't even make the "click" animation. It's just inert, does nothing, and the problem will persist after a restart (waiting one minute while off).
Per @febman123 https://github.com/febman123 , I looked for a way to kill the running background process (WebAppMgr), but I couldn't find any kind of process manager, so I assume that's only possible on a rooted TV.
The only solution I've found is to uninstall and reinstall the app, which is a pain in the rear.
If it helps, this was also a problem on the previous TV firmware, not just after the most recent update.
— Reply to this email directly, view it on GitHub https://github.com/webosbrew/youtube-webos/issues/326#issuecomment-3386220668, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJUF4WZCE25BMKNEKIUGMSD3WZ6VBAVCNFSM6AAAAACDEKNTUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOBWGIZDANRWHA . You are receiving this because you were mentioned.Message ID: @.***>
Thanks for the suggestion. I couldn't figure out the kodi app. I installed it from Homebrew and installed a few addons, but I'm not sure which one I should use that works to reset YouTube's. After restoring the internet access and then opening Kodi and clicking around on some addons, it still leaves YouTube unresponsive.
Same with restarting, however I discovered YouTube will respond again if I leave the TV off for like 30 minutes and try again with restored internet. So weird.
U need to play some content, so that u are using as much mem as possible, that will inturn kill, flush the app from memory. So when we open YouTube it will start to load.
On Mon, 13 Oct, 2025, 8:05 pm beefamato, @.***> wrote:
beefamato left a comment (webosbrew/youtube-webos#326) https://github.com/webosbrew/youtube-webos/issues/326#issuecomment-3397792352
Thanks for the suggestion. I couldn't figure out the kodi app. I installed it from Homebrew and installed a few addons, but I'm not sure which one I should use that works to reset YouTube's. After restoring the internet access and then opening Kodi and clicking around on some addons, it still leaves YouTube unresponsive.
Same with restarting, however I discovered YouTube will respond again if I leave the TV off for like 30 minutes and try again with restored internet. So weird.
— Reply to this email directly, view it on GitHub https://github.com/webosbrew/youtube-webos/issues/326#issuecomment-3397792352, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJUF4W3XB45PZZLPWRNXZET3XO2EDAVCNFSM6AAAAACDEKNTUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJXG44TEMZVGI . You are receiving this because you were mentioned.Message ID: @.***>
Per @febman123 , I looked for a way to kill the running background process (WebAppMgr), but I couldn't find any kind of process manager, so I assume that's only possible on a rooted TV.
You can kill the running YTAF process on a dev mode TV by connecting using webOS dev manager installed on Windows/Linux/Mac.
As you are using developer mode on your TV:
Install webOS Dev Manager from https://github.com/webosbrew/dev-manager-desktop
Once you have set it up to connect to your TV, it will display a list of your installed Hombrew apps as per this screenshot of mine:
To set it up to connect to your TV:
First, confirm your TV's IP address (depends on the TV's age/model, but usually under Settings, Network, or from your router).
Then in dev manager, click on the "cog" icon at the bottom and select Devices to add a new device (TV):
Select "Use Developer Mode":
Go through the check list and confirm you have everything ready to continue. If you know you do, you can click "Skip" to continue.
In the next section, give your TV whatever name you want (or leave the default "tv" as-is), input your TV's IP address in the address section and enter your dev mode passphrase and click "Finish":
If you have done everything correctly you should be able to restart webOS dev manager and connect to your TV - it will display a list of your installed Homebrew apps (in your case at least Homebrew and YTAF).
So, to kill (stop) the YTAF process, click on the third icon down (terminal):
then type: pkill -9 WebAppMgr NOTE: type exactly as shown here as it is case-sensitive, and press Enter:
This will kill (stop) the YTAF process and you should be able to start it again as per normal.
Hope this helps.
Thanks for the suggestion! Unfortunately, I'm not rooted, but I might consider rooting if I can't figure this problem out.
Thanks for the suggestion! Unfortunately, I'm not rooted, but I might consider rooting if I can't figure this problem out.
Sorry, my mistake! It's been so long since my TVs were using dev mode that I forgot about its limitations.
Some more info from my observations that may help you (and the YTAF devs???) and any others similarly affected....
After powering on both of my rooted LG TVs, YTAF automatically starts up in the background soon after the OS has loaded and its process appears in the running processes list.
On my webOS 6.5.0 C1 OLED, which is the one that is affected by this "no Internet at TV power-on" issue, I guess during the YTAF background process start-up it checks for an established Internet connection.
It appears to try once only and if an Internet connection is not detected it just sits there, running in the background in a kind of zombie state. YTAF will try to start if you click on its icon, but it will fail and after a while you are returned back to the Home screen. Nothing happens on subsequent attempts to start it unless its process (WebAppMgr) is manually killed or the TV is restarted.
However on my webOS 3.4.0 TV, if I try to start YTAF at any time and there is no Internet connection available, a "Check Network Connection" page is immediately displayed, providing the options to Retry, Go to Network Settings or Exit the app. At any time when an Internet connection is re-established, YTAF will start. It does not have to detect an Internet connection when the YTAF background process is started soon after the TV is switched on.
I guess there is something going on in YTAF on 6.5.0 why the "Check Network Connection" page is not displayed by default and why YTAF does not continually check for and use a subsequently available Internet connection.
FYI, I found in webOS 6.5.0 and YTAF it is possible to get the "Check Network Connection" page to appear under the following circumstance:
Switch on the TV when the Internet connection is available and wait for webOS start-up to complete (and therefore YTAF to start up in the background and detect the Internet connection). Disconnect the Internet - for testing I switch off my TV's Wi-Fi connection in Network Settings. Start YTAF. After less than a second, the "Check Network Connection" page appears with Error Code: -106, and the options: RETRY, NETWORK SETTINGS, EXIT APP. If I then re-enable Wi-Fi and click on "Retry", or click on "Exit app", re-enable Wi-Fi and use the icon as per normal, YTAF will start. So it seems that in webOS 6.5.0 as long as YTAF detects an Internet connection shortly after TV power on it will then behave in exactly the same way as it does on webOS 3.4.0.
Both of my TVs are running the same, default version of YTAF (0.4.1), installed via dev manager.
Again, all supposition on my part, based on my testing and observations on my two LG TVs, which only became an issue because I am currently using my mobile phone and its Wi-Fi hotspot for Internet connectivity until my proper broadband is up and running again.