I´m just going to chip in with one thing, just in case;
I am still under the impression that libcec is exactly the same as in Raspbmc.
The reason I say this is that popcornmix´s libcec version went into his Kodi backport branch even before Kodi 14.0 release and as I have built Helix for Raspbmc for a long time I can say that you cannot even build his backport branch without his libcec version.
It HAS to be the same version, otherwise the wrong libcec is being shipped for Raspbmc but at the same time the Kodi version for Raspbmc is being built with the “correct” version.
I don´t think that this is the case.
Edit: That said, you cannot just switch the lib versions as Kodi depends on them (Popcornmix´s backport branch has patches that depends on his version of libcec both when building and after).
Unless there are different dependencies between newclock4 and the backport branch (newclock4 has more libcec patches)???
Have you actually tested this on raspbmc though or are you just assuming this is the case ?
Have you manually set the time forwards on raspbmc then triggered an ntp sync to cause the time to jump back while you are using cec ?
As miappa has pointed out, libcec should be nearly identical if not identical between raspbmc and osmc - there shouldn’t be any significant differences between the two that would cause one to be vulnerable and the other not.
Until proven conclusively otherwise I am going to assume that the raspbmc version of libcec is just as vulnerable to time shifts and that it just doesn’t exhibit under raspbmc because there aren’t two ntp clients fighting to control the time with one connecting to your dodgy ntp server.
As I said earlier, we will see if we can disable the built in ntp client in connman for the next build.
About ntp - I wrote ealier that it is not ntp dependent issue. If I manually change time via date -s it triggers the “lost connection” too.
Please read my post regarding my testing procedure and test it yourself. It is completely harmless and you can test it on both osmc and raspbmc - I know I did
This is the Raspbmc library: You should be able to drop it in over /usr/lib/libcec.so.2.0.1 as follows:
systemctl stop mediacenter
wget http://download.raspbmc.com/downloads/bin/lib/libcec.so.2.0.1 -O /usr/lib/libcec.so.2.0.1```
My other comment was that ConnMan is likely getting time from DHCP time servers and 'fighting' with NTP. I will disable time updates in ConnMan for next release.
Unfortunately the same issue occurs (connection to cec lost after time shift backwards). So it is not the libcec.so. Any other thought about the root cause of the problem?
Maybe firmware, or some other dependant libraries?
I mean, this is not critical right now. After addressing the timing issues cec will probably work ok. It is just something that shouldn’t behave like that and I believe the decision is up to you, whenever or not you what to fix it.
I’d categorize this bug as moderate/high because it is not disrupting anything (when the time is correct) but just because nobody can find the root cause.
Hey, sorry for not being to help a bit more.
My issue never repeated while I was looking at the tcp dumps running. It worked for a long time, but the next day it wasn’t working anymore, so it’s hard to pinpoint exactly when it fails.
Anyway, hoping the next release will fix it.
Unrelated: Do updates like this come in when updating the system via the UI or do I have to reflash?