I am using a T95Z S912 box as a headless CoreELEC TVHeadend server in my attic and I plan on using the AML-VNC addon for remote maintenance when needed but I am having an unusual resolution problems.
Is it possible that the VNC addon is starting too early before the correct resolutions are being set?
If so is there a way to add a delay to addon start?
I have tried it with no disp_cap, I get a similar problem only at a much reduced resolution in both pre and post sending the sigterm to aml-vnc See post below, no disp_cap actually results with a blackscreen when booting headless.
I have also tried it with the full variety of resolution entries in disp_cap reported by my TV downstairs and the same as above happens.
So far the best (but broken) result is as I have described above (disp_cap with 1080p60hz but having to forse restart aml-vc).
I am defo on the latest aml-vnc addon (I even forced an update to be sure) and situation is the same.
I removed my disp_cap file (still booting headless for now as I am not home to connect to TV) and I now only get a black screen on VNC both before and after restarting the aml-vnc service.
Obviously I will restore my prev disp_cap file as the situation was better!
As is possible to add a wait command to the start of aml-vnc to see if delaying the start gets the correct resolution? If so where do I add it to test?