I recently switched from elseed to ncid an I'm seeing that after a day or so the gui on the Tivo starts acting a little stangely.
Normally, when you start on the Now Playing List and click right, the text clears away and the show description, etc. scrolls over from the right.
When it gets in the "bad state", when you click right, the show description, etc. displays immediately, then another copy scrolls over it from the right.
I've tried to reproduce it by calling out2osd at various times manually, but can't seem to do so.
Also, the blue selection bar that goes off to the left edge of the screen sometimes leaves an extra copy of itself along the left edge.
Some screen refreshing code seems to be getting messed up.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does this happen after a call comes in? TiVoCID pipes its output to out2osd, so I would expect the problem to show up when you manually call out2osd. It is possible that it is a memory problem. Try a reboot and see if that solves it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The HD Tivo is running 3.1.5f.
I recently switched from elseed to ncid an I'm seeing that after a day or so the gui on the Tivo starts acting a little stangely.
Normally, when you start on the Now Playing List and click right, the text clears away and the show description, etc. scrolls over from the right.
When it gets in the "bad state", when you click right, the show description, etc. displays immediately, then another copy scrolls over it from the right.
I've tried to reproduce it by calling out2osd at various times manually, but can't seem to do so.
Also, the blue selection bar that goes off to the left edge of the screen sometimes leaves an extra copy of itself along the left edge.
Some screen refreshing code seems to be getting messed up.
Does this happen after a call comes in? TiVoCID pipes its output to out2osd, so I would expect the problem to show up when you manually call out2osd. It is possible that it is a memory problem. Try a reboot and see if that solves it.