Through trial and error I discovered that making the app crash on purpose solves the problem - this results in an identical behaviour to the user as calling the sendExitEvent method. (which returns the user to the Smart Hub instead of exiting completely). becomes slower after starting again) when using the command ndReturnEvent() The exit is realized by executing the JS command var widgetAPI = new () This behavior happens on all devices (TV and Blu-Ray Player devices with Smart TV Platform). The measured JS execution times are only slightly slower, but the HTML elements are rendered much slower to the screen. Normally the app is performing well, but after exiting the app becomes very slow, by a factor of six. We have developed a Samsung Smart TV app for the 2011 & 2012 platforms.
0 kommentar(er)
