Things are going nowhere fast regarding the "Service is not running" issue - previous theories of it being mux specific or signal level being too high have now gone out of the window. Latest theory is that it is related to timers in some way, and this could involve the recording library also since the two are linked. I'm still in the process of trying to prove this theory as the problem for me tends not to show up when I'm trying to reproduce it. It may seem random, but usually there is a solid reason behind these things even if the symptoms appear random.
As such, any help from anybody running v4.6 or v4.8 who can consistently reproduce the "Service is not running" problem could prove critical.
As such, any help from anybody running v4.6 or v4.8 who can consistently reproduce the "Service is not running" problem could prove critical.




. Unfortunately it is broken in v5.2, so presumably that bug came along with the TRD changes.
