Languages

Menu
Sites
Language
[CRITICAL] App freeze after tv turn off and on

Hello,

we have a critical problem with our webapp on Samsung Tizen 2015 and 2016.

If we have the app up & running and then we turn off and turn on the tv, when we reopen the application it is in the same previous situation (the multitasking feature is managed using the listener on the event visibilitychange ).

The problem is that, since this moment, all the animations done by the library "VelocityJS" don't work anymore and all menus are overlapped. If we use the CSS animation no problem is detected.

Instead, if we switch to an other application while the our one is opened (so the same event visibilityChange is called), and then we come back to our one, no problem is detected using "VelocityJS".

So, there is a problem bound to "VelocityJS" only after switching off and on the TVs.

 

Can you give us support please? It's a critical problem.

Edited by: ss ndcdev on 25 Jan, 2017

Responses

2 Replies
Armaan-Ul- Islam

From your findings I guess the Power on/off event does not trigger ‘onVisibilityChange()’ event. What comes in my mind is you may try writing an event handler for pressing power on/off button on remote. In that case you have to register ‘Power’ key, add ‘tv.inputdevice’ privilege and write ‘document.addEventListener()’ function. You may get some hint from these documents:

http://developer.samsung.com/tv/develop/tutorials/user-input/key-code-table

http://developer.samsung.com/tv/develop/tutorials/user-input/remote-controller

You may also look in the http://developer.samsung.com/tv for details.

ss ndcdev

Hello,

I added an overlaylog in the app attaching it to the event "visibilityChange".

It prints "HIDE" when document.hidden is true or "RESTORE" if it is false.

I saw that "HIDE" and "RESTORE" are printed both when you change application while the app is opened using multitasking (for example, I open Netflix and then I come back on our app which is in the same previous situation) or when I turn off and on the tv and then I reopen our app (which is in the same previous situation).