SamyGO

Hello all,

I have realisied that when ntpclient is started, the SmartHub does not allow anymore the log-in (it has something to do with the time and date update and it is not ntpclient related).

Just by chance, I discovered that when a SW update is launched (from web or from antenna does not matter), SmartHub is closed and when you reopened it works perfectly even if ntpclient is running.
The obvious conclusion is that ntpclient date shall be set at TV start-up before that Smarthub is started.

Is it possible to block SmartHub automatic start-up at TV boot ?

Thanks for the help.

miazza

Update: if you launch smarthub during TV boot, it takes some time but it boot after ntpclient. maybe if we run ntpclient as first item after run.sh it will solve the issue.

Do someone know how to kill Smarthub ? What is the process name ?

Killing "WidgetEngine" process kills smarthub, but I don't know how to reopen it without rebooting TV (it is exeDSP child process)

Thanks.. I thought it was possible to kill it and to invoce it only when needed by pushing the relevant button on remote.

zoelechat wrote:Killing "WidgetEngine" process kills smarthub, but I don't know how to reopen it without rebooting TV (it is exeDSP child process)

Code: Select all

kill $(pidof WidgetEngine)

Hei zoelechat, you are a great men.

I tied the your command just for fun and this is magic: When lounching this the Smartshb is killed and restarted automatically with the right time and login is allowed and all functions are working.

Still to be extensivly tested but it seems I have solved my issues with ntpclient .