No - unfortunately I haven’t received enough logs to chase this down.
I don’t want to delay the October update so will release that shortly and look at this when I have a better idea of the problem.
I mean the last test build has certainly improved it for me, with longer periods between occurrences than on the standard September release - but it’s far from perfect.
Will the “standard” October update have these test build changes worked into it so those affected can at least go onto that rather than stick to this test USB build (or have to downgrade to a release prior to the September update, which I haven’t got round to doing yet)?
It seems im still having a problem… But i think it occurs when some one uses a different source in the tv and then powers off the tv still in that source… When i power back on and switch to the vero i need to reboot it to get cec working.
I’ll try and get some more logs this weekend.
I’d like to go back to the last update that was working perfectly (so, just before the September release).
I know I can download the 2022.03-1 release and reinstall but is it possible to ensure I get all the OS updates right up to just before the September release but not go onto the September version (or beyond)?
There were no stable updates released between March and September.
Fair enough - but what about OS-level updates? I suppose I could remove/comment-out the osmc repo from /etc/apt/sources.list which would ensure I get any Debian updates?
EDIT: I’ve re-imaged on 2022-03 and done exactly this (commented out the osmc repo) - all seems to be working.
I hope others can help provide logs to find a resolution to this bug - I would love to help more but unfortunately I just can’t keep it in this state due to it breaking the whole AV setup from time to time whenever it occurs and I’m not always there to manually intervene by restarting the Vero, leaving family without the use of the TV/AVR. It’s the fact it interferes with the AVR audio output and other devices connected to the AVR/TV that is the most frustrating…
1 Like
Thanks for raising and trying Rod.
My setup is a Vero4k with just an earc LG soundbar setup l, firestick4k, and LG GX Oled TV. Suffers the same hdmi problem, first key is LG remote stops working with Vero4k and then sound from LG soundbar goes. Reboot of Vero4k fixes it for a bit.
Well as is typical i havn’t managed to reproduce the problem… I need to see what it is my daughter does to the blimen TV in the evenings and then maybe it’ll make sense lol
I couldn’t find any particular pattern to be honest personally - it does it randomly - most times for sure would be noticed after a period of the TV/AVR/other devices being in standby, but certainly not always…it might not happen for a day or two (or even longer) but then it could also do it multiple times a day even with a service restart or reboot in between each occurrence.
Any update on an official release? I just lost my native remote and of course got hit by this bug so my logitech does not work on it now with CEC when it worked fine before the Sept update.
I’m hoping to do a release soon.
All we’ve done is restore CEC to its pre-update behaviour.
3 Likes
After almost 3 weeks of using problem free with [kernel-osmc] Vero 4K: fix CEC connectivity issues when bus is busy ] patch, today the HDMI ports got messed up again and soundbar disappeared . After turning the vero 4k+ off and on all is back to normal.
Sadly it still misbehaves on the build you did with cec set to as it was before the update.
Could it be something deeper in the Linux code or some other dependency?
Unfortunately I don’t have any further suggestions at this time.
I’ll release the update and see how people find things.
Sam
are you releasing it today?
Tom
No – I’m tentatively scheduling for Sunday, 30th.
This was my problem, it took down the whole system when connected to my LG TV. I re-imaged back to 2022-03 and have not had a single issue since. I was coming back here just to see if it had been resolved… seems to be quite an issue!
Me too. Been back on 2022-03 for a while now and it’s been solid.
Hi, How do you go back to 2022-03?
Is this fix still planned to go out today?