I don’t know what issue you are talking about. I think you are mixing issues now. One issue after another. Now poweroff your device not suspend. Then power it on. Once it is in kodi send it to suspend. After it woken up ssh to your box and input:
Just for info, I tried the 2 builds, and the problem of exit from standby is identical.
It works randomly, around 1 time out of 2. Sometimes it works 3 times in a row. Then after nothing 3 times in a row. It’s very strange. I continue tomorrow. Good evening.
So i have been able to create a (fairly) consistent crash with the current latest build on my N2, it can be triggered by chapter skipping of a 2160p bluray remux, strangely fast fwd seems fine but chapter skipping (not always but fairly consistently) causes kodi to crash and restart. I have included a lnk to the crashlog, if you need a full debug log as well then let me know.
I’ve had debugging on but haven’t seen the issue since yesterday.
Weird because it did it 3 times in 20 mins.
Can’t get it to happen at all now that I’m trying to capture it
This seems to completely address the decoding issue in all h264 bluray rips in my collection. Thanks.
As a bonus, it also seems to fix the really annoying audio glitches on pass-through to an AVR that afflicted both h264 and h265 encodings. Double thanks.
I have observed that my SMB based sources often take several minutes to become accessible after the system is rebooted. During that time they are available to other devices continuously.
This was observed on the 22 April nightly, the 23 April Nightly and the pixelation fix version. The following log was captured with the pixelation fix version:
The actual delay to availability seems to vary, but during the unavailable time no videos on the SMB shares are inaccessible.
In this case the film Atomic Blonde was tried about two minutes apart. The first time I was told that the film was no longer present in the collection, the second it played normally.
Btw, tested versions that I have saved and last that works OK for me is 1555398703. First version on which it happened rare was 1555226781 and on 1555851841 it happens more often…
Edit: is it enough to copy kernel and system on 1555851841, or is the update process needed?