I started a new lag thread because the issue I'm seeing is limited to the transport buttons while viewing a previously recorded program so I would assume it has nothing to do with speed of loading the guide data for slice pull-out which seems to be the focus of the other "Lag" thread.
I'll start by saying that I'm seeing this issue on cheap, no-name, generic Android 6.0.1 boxes which I realize are not officially supported/approved and are certainly underpowered compared to the typical front-end hardware being used by most of you.
However, these low-powered boxes have provided instantaneous responsiveness to the skip-fwd, and skip-back buttons for years. I can't imagine how the addition of a little eye-candy to the UI has resulted in transport lag going from zero to 2-3 seconds per button-push, sometimes even so long that the "app has stopped responding message" pops up and I have to hit "wait" in order to get the desired result.
Can anything be done to cleanup the code and address this delay?
Discussion of the new user interface for the HDHomeRun app.
1 post • Page 1 of 1