This content has been marked as final. Show 1 reply
replied by myself...
After checking w/ the box manufacturer, we have some findings.
The marquee program is always switching among the stages of 'sleeping' and 'awake'. The 'sleeping' stage might be sometimes extended due to STB is unable to finish its sleeping in time (due to cpu time competition). STB with MHP middleware is an embedded system that usually equips only with minimum computation power, (cost and some other design consideration). Thus the programmer should not expect it is a powerful computation environment and being able to response every single request in time(or as it behaves on emulators running on a pc). We are now doing work-around to adjust the program presentation so that the 'jitter' could be hardly 'seen' by the users.