I’m using this projector that has a native resolution of 1366 x 768
It does work with 1280 x 720, but some pixels are bigger than others so it looks weird.
Is it possible to force CoreELEC into using the resolution of 1366 x 768?
It doesn’t show on the list in the system settings, so there is obviously not an easy way.
I use CoreELEC 8.95.2 and my hardware is a TV box based on Amlogic S905
I’m currently working on adding support for more resolutions to the kernel.
Next round of test builds I will make an s905 image and post it for you to try.
OK, thanks. Looking forward to it.
So here is a build for you to try.
A few notes first.
I have tested that this build supports the 1366x768 resolution on my monitor. However 1366x768 is an oddball resolution that is occasionally problematic to support.
If your projector / monitor does not correctly advertise it’s capabilities through EDID you may still not be able to pick the resolution you want in kodi.
However to get around that you can create a file with a list of resolutions for kodi to choose from.
.kodi/userdata/disp_cap
In your case you can use the following. (It’s a good idea to have a few known working resolutions such as 720p/1080p in the the list in addition to the one you want to try.)
720p60hz
1080p60hz
1366x768p60hz
You will need to reboot or at least restart kodi for it to read the list. Since kodi only checks for display info at startup.
Thank you.
I tried your build and it seems to be working just fine - I can choose different resolutions.
Although it is like you said; I did not have 1366x768 on the list (I did however had 1024x768), but after I added it to disp_cap, it showed on the list in the display settings.
However, with this new build I seem to be having the same problems as I experienced with 8.95.3.
Whenever I try to play HD movie from a windows network, it keeps re-buffering every minute or so…
I did not know how to fix it back then, just downgraded to 8.95.2.
But maybe now it is worth to look into the solution, as this new resolution setting is really what I need.
Anyway, thanks again and I confirm it working.
Hello,
I realized the same for my smaller TV. Rpi detects and offers correct resolution (in case Philips, Rpi detect he should be able to show 1366x768, but only with 50/60Hz), so I believe its not just incorrectly advertise EDID 
I believe, when checked by tvservice, 1080ones was under CEA, and native one (where pictore looks better, because no Kodi upscaling) under DMT. Maybe CE detects only CEA mode?
cat /sys/devices/virtual/amhdmitx/amhdmitx0/edid
Rx Brand Name: PHL
Rx Product Name: PHILIPS
Manufacture Week: 12
Manufacture Year: 2017
Physical size(cm): 64 x 36
EDID Version: 1.3
EDID block number: 0x1
blk0 chksum: 0xbf
Source Physical Address[a.b.c.d]: 1.0.0.0
YCC support 0x03, VIC (native 255):
ColorDeepSupport 0xb8 10/12/16/Y444 1/1/0/1
19 4 31 16 33 34 32 20 5 17 2 21 6 1
Audio {format, channel, freq, cce}
{1, 1, 0x07, 0x03}
{2, 5, 0x07, 0x00}
{7, 5, 0x07, 0x00}
{10, 7, 0x07, 0x00}
Speaker Allocation: 0x01
Vendor: 0xc03
MaxTMDSClock1 225 MHz
SCDC: 0
RR_Cap: 0
LTE_340M_Scramble: 0
DeepColor
checkvalue: 0xbf700000
.
cat /sys/class/amhdmitx/amhdmitx0/disp_cap
720p60hz
1080i60hz
1080p60hz
720p50hz
1080i50hz
1080p30hz
1080p50hz
1080p25hz
1080p24hz
I tried edit ./kodi/userdata/disp_cap, add this:
1366x768p60hz
1366x768p50hz
1366x768i60hz
1366x768i50hz
to the already existing values. In kodi shows only 1366x768p, when choosing it, No Signal 
Tv is Phillips 32PHS4032-12
Hi jimmy,
The kernel that CoreELEC uses does not currently support VESA and other non standard video modes.
If the kernel either can’t support a video mode or the TV is not clear about the modes it supports the user will not be offered the video mode to use. Trying to force an unsupported video mode will not work.
Thank you for explanation, adamg also mentions the same thing, but in private message, so its good to let others know. Hopefully it will be some day? To support also not Full HD / not BIG TVs nativelly, the way as they was made 
Are the non-standard resolutions supposed to work already, in the 9.0.1 release?
Because I still get black screen when switching to 1366 x 768.
It’s a shame.
Hi @cdu13a,
many thanks for your testbuilds, I have installed one, edited the disp_cap and voila, 1366*768 started working on my old TV, now I have a nice and sharp image.
Although I’d like to ask if there is any possibility to get the current version 9.0.3 compiled with extended resolution support (in my case S905 architecture). Or is there any guide how to compile myself? I’m sure I could follow the compile article, but how to make changes in the kernel to add resolution support?
Many thanks
Mike
+1 here (not 9.0.3 logically, but include to the stable branch would be nice). I remember no luck with custom disp_cap with stable version. Would be great to support quite a much 26-32’’ avaible on the market, which are in my experience very often 1366.
The 1920x1080 is usually possible on those, but image is a bit too much sharp, which could be softened by sharpness on TV, but still, native res. looks (tested on Rpi) better on them, although they usually doesnt support 23.976/24 fps on that resolution (often they are able to do so when switch to 1080p by force).
An answer would be really appreciated 
Thanks
Mike
Sorry for the delay, I likely got distracted and forgot to respond.
1366x768 is currently not possible with the s905/s912 devices on CoreELEC.
However I’m planning on revisiting my work on supporting more resolutions on the older devices, soon.
Tonights( 20191002) nightly build will have support for 1366x768p60hz on the amlogic builds for the s912/s905 variants.
To use create a /storage/.kodi/userdata/disp_add file and add 1366x768p60hz to it.
Hi @cdu13a,
I have just tested this on the latest nightly (20191019) and it works like a charm.
Does this mean that the resolution support will get into the next stable release? That would be fantastic.
Many thanks
Mike
@myso glad that worked for you.
Yes the extra resolution support will be in the next stable release once that happens. I can’t say when that will be since there is still a few things that need to be fixed up before the next stable release happens.
Can you please reffer commit(s) for that? Out of curiousity… Is it just this? (refer.)
Wondering, if modeline "1366x768p60hz" within bootargs did the same job without any modification or is there somthing under hood…
I tried to add 2560x1440p60Hz to here on my VIM3 Pro: /storage/.kodi/userdata/disp_add
but it freezed my monitor.
Then I tried to add 2560x1440p50Hz and got this:
@cdu13a Thanks, you made my day!
I was able to add 1280x1024 for S905x:
Is that disp_add documented somewhere?
LE has disp_cap, does it work here? What is the difference?
@bam disp_add does just what it says. It adds any modes listed in it to kodi’s known list of video modes. disp_cap overwrites kodi’s list of known video modes.
Use of disp_add is preffered over the use of disp_cap, since it doesn’t block use of modes advertised by the display. Which tends to drastically cut down the support questions that seem to oddly pop up 4 months after a user sets disp_cap, and has forgotten they set it and are now trying to figure out why they can’t set X resolution on their shinny new display they just bought. 
About | FAQ | Terms of Service | Privacy Policy | Legal Notice
