I’ve just started properly testing the 4.9 USB image and have hit a green screen.
For me this was in a HDR HEVC rip of Aquaman which I never had problems with on 3.14 kernel. The green screen occurred as I was skipping though the file.
After hitting the green screen I found that every video I attempted to play thereafter would not play and instead showed a green screen until I rebooted
After a reboot I was able to easily reproduce…I play Aquaman again and hit a remote button which I have mapped to the action: Seek(250) a few times in succession and bam…green screen.
I can’t, sorry, next time.
It was fixed by reboot or me exiting to console to clear the arp cache and back from there to the gui a few times. I will when it happens again.
I reread, you mean a debug log when it works? I can do that when I get back home.
I am very happy with this test version. Have been using it for some time now and don’t have any major issues. Great 3D performance also. Yesterday I have watched Avatar in 3D and this release still has some glitches, but this is a known issue and I can live with it this way. I think it is almost ready for release to stable?
I did, while the vero was unplugged. It required me to add the source in the tv again but was still showing low res and no cec. When i did the same before the updated version it went hd and cec for a while but a day or so later it was back to low res etc. I always leave the vero on and just put the tv to sleep
I have found a further issue. When playing TS recordings from tvheadend, or even just playing the raw TS file directly I find that the screen flashes black for a couple of seconds a time during playback. It seems to always be at the same points in the file.
If I boot back to the 3.14 kernel then the same file plays flawlessly.
Should I break this out into support then?
More info:
[bluetooth]# info 1C:12:B0:A8:50:C2
Device 1C:12:B0:A8:50:C2
Name: AR
Alias: AR
Appearance: 0x0180
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
Modalias: usb:v0171p0413d0000
[bluetooth]# connect 1C:12:B0:A8:50:C2
Attempting to connect to 1C:12:B0:A8:50:C2
[CHG] Device 1C:12:B0:A8:50:C2 Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 1C:12:B0:A8:50:C2 Connected: no
Sorry that cat thing was not obvious to me, you know all the cat videos on the Internet
Will try to search for the exact cat command when it happens next time.
Does this mean the above two logs are not useful?