Is it possible to set resolution to 1366 x 768?

@Pelican I will check to verify that the values for that mode are correct.

Thank you!

@cdu13a thanks for the explanation.

Then I still can’t understand why in Kodi I don’t see 1280x1024 mode native for the display?
It seems advertised by the display:

CoreELEC:~ # edid-decode /sys/devices/virtual/amhdmitx/amhdmitx0/rawedid
EDID version: 1.3
Manufacturer: BNQ Model 7904 Serial Number 21573
Made in week 7 of 2008
Digital display
Maximum image size: 38 cm x 30 cm
Gamma: 2.20
DPMS levels: Off
RGB color display
Default (sRGB) color space is primary color space
First detailed timing is preferred timing
Display x,y Chromaticity:
  Red:   0.6474, 0.3398
  Green: 0.2880, 0.6054
  Blue:  0.1445, 0.0683
  White: 0.3134, 0.3291
Established timings supported:
  720x400@70Hz 9:5 HorFreq: 31469 Hz Clock: 28.320 MHz
  640x480@60Hz 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz
  640x480@75Hz 4:3 HorFreq: 37500 Hz Clock: 31.500 MHz
  800x600@60Hz 4:3 HorFreq: 37900 Hz Clock: 40.000 MHz
  800x600@75Hz 4:3 HorFreq: 46900 Hz Clock: 49.500 MHz
  832x624@75Hz 4:3 HorFreq: 49726 Hz Clock: 57.284 MHz
  1024x768@60Hz 4:3 HorFreq: 48400 Hz Clock: 65.000 MHz
  1024x768@75Hz 4:3 HorFreq: 60000 Hz Clock: 78.750 MHz
  1280x1024@75Hz 5:4 HorFreq: 80000 Hz Clock: 135.000 MHz
  1152x870@75Hz 192:145 HorFreq: 67500 Hz Clock: 108.000 MHz
Standard timings supported:
  1152x720@60Hz 16:10
  1280x800@60Hz 16:10
  1280x960@60Hz 4:3 HorFreq: 60000 Hz Clock: 108.000 MHz
Detailed mode: Clock 108.000 MHz, 376 mm x 301 mm
               1280 1328 1440 1688 hborder 0
               1024 1025 1028 1066 vborder 0
               +hsync +vsync 
               VertFreq: 60 Hz, HorFreq: 63981 Hz
Serial number: V2815356SL0
Monitor ranges (GTF): 55-76Hz V, 31-83kHz H, max dotclock 140MHz
Monitor name: BenQ E900
Checksum: 0x55 (valid)

CoreELEC:~ # cat /sys/devices/virtual/amhdmitx/amhdmitx0/edid
Rx Manufacturer Name: BNQ
Rx Product Code: 7904
Rx Serial Number: 00005445
Rx Product Name: BenQ
Manufacture Week: 7
Manufacture Year: 2008
Physical size(cm): 38 x 30
EDID Version: 1.3
EDID block number: 0x0
blk0 chksum: 0x55
Source Physical Address[a.b.c.d]: 0.0.0.0
YCC support 0x00, VIC (native 3):
ColorDeepSupport 0x00 10/12/16/Y444 0/0/0/0
3 4 5 16 
Audio {format, channel, freq, cce}
Speaker Allocation: 0x00
Vendor: 0x0 ( DVI device)
MaxTMDSClock1 140 MHz
SCDC: 0
RR_Cap: 0
LTE_340M_Scramble: 0

checkvalue: 0x00000000

CoreELEC:~ # cat /sys/devices/virtual/amhdmitx/amhdmitx0/edid_parsing
ok

CoreELEC:~ # cat /sys/devices/virtual/amhdmitx/amhdmitx0/disp_cap
480p60hz*
720p60hz
1080i60hz
1080p60hz

CoreELEC:~ # cat /sys/devices/virtual/amhdmitx/amhdmitx0/disp_cap_3d 
3D support lists:

480p60hz 
576p50hz 
720p60hz 
1080i60hz 
1080p60hz 
720p50hz 
1080i50hz 
1080p30hz 
1080p50hz 
1080p25hz 
1080p24hz 
640x480p60hz 
800x480p60hz 
800x600p60hz 
852x480p60hz 
854x480p60hz 
1024x600p60hz 
1024x768p60hz 
1152x864p75hz 
1280x600p60hz 
1280x768p60hz 
1280x800p60hz 
1280x960p60hz 
1280x1024p60hz 
1360x768p60hz 
1366x768p60hz 
1400x1050p60hz 
1440x900p60hz 
1600x900p60hz 
1600x1200p60hz 
1680x1050p60hz 
1920x1200p60hz 
2160x1200p90hz 
2560x1080p60hz 
2560x1440p60hz 
2560x1600p60hz 
3440x1440p60hz

Adding 2560x1440p60hz resolution to disp_add file and switching to it results in following glitch

Basically the same result as posted above by Pelican. But I remember that this trick used to work just couple of versions back and must have regressed somehow.

@cdu13a can you please have a look at this?

I think it stopped working around the time we had a major kernel change a few versions back.

Can you log in via ssh and run dispinfo and post it’s output here.

I unfortunately don’t have a display that can do that resolution, or a way of emulating it. But I may be able to sort something out. I’m however getting ready to move so I’m not sure how quickly I can do this.

http://ix.io/2yJs

Thanks. Let me know if you need more info.

Update: here’s a result of running get-edid -b 6 | parse-edid while this monitor is connected to PC.

This is read-edid version 3.0.2. Prepare for some fun.
Attempting to use i2c interface
Only trying 6 as per your request.
256-byte EDID successfully retrieved from i2c bus 6
Looks like i2c was successful. Have a good day.
Checksum Correct

Section "Monitor"
        Identifier "PHL 245E1"
        ModelName "PHL 245E1"
        VendorName "PHL"
        # Monitor Manufactured week 26 of 2019
        # EDID version 1.4
        # Digital Display
        DisplaySize 530 300
        Gamma 2.20
        Option "DPMS" "true"
        Horizsync 114-114
        VertRefresh 48-75
        # Maximum pixel clock is 300MHz
        #Not giving standard mode: 1920x1080, 60Hz
        #Not giving standard mode: 1680x1050, 60Hz
        #Not giving standard mode: 1440x900, 60Hz
        #Not giving standard mode: 1280x1024, 60Hz
        #Not giving standard mode: 1280x960, 60Hz
        #Not giving standard mode: 1280x720, 60Hz

        #Extension block found. Parsing...
        Modeline        "Mode 13" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync 
        Modeline        "Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync +vsync 
        Modeline        "Mode 1" 296.00 2560 2568 2600 2666 1440 1443 1448 1481 +hsync -vsync 
        Modeline        "Mode 2" 25.200 640 656 752 800 480 490 492 525 -hsync -vsync
        Modeline        "Mode 3" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
        Modeline        "Mode 4" 74.250 1920 2008 2052 2200 1080 1082 1087 1125 +hsync +vsync interlace
        Modeline        "Mode 5" 74.250 1920 2448 2492 2640 1080 1082 1089 1125 +hsync +vsync interlace
        Modeline        "Mode 6" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync
        Modeline        "Mode 7" 74.250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
        Modeline        "Mode 8" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync
        Modeline        "Mode 9" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
        Modeline        "Mode 10" 27.027 720 736 798 858 480 489 495 525 -hsync -vsync
        Modeline        "Mode 11" 27.000 720 732 796 864 576 581 586 625 -hsync -vsync
        Modeline        "Mode 12" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
        Modeline        "Mode 14" 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync 
        Modeline        "Mode 15" 27.00 720 736 798 858 480 489 495 525 -hsync -vsync 
        Modeline        "Mode 16" 27.00 720 732 796 864 576 581 586 625 -hsync -vsync 
        Option "PreferredMode" "Mode 13"
EndSection

I just bought a new s905x3 based box to replace our aging s905x box so I can migrate to ng. On our old box 1366x768 output works fine. On this new one when I change to 1366x768 my TV says not support. Did something change with the new kernel to make this no longer work? Is there some way I could possibly troubleshoot this?

edit: my dispinfo http://ix.io/2QCa

Experiencing the same issue as @quickfast

Tyring to use 1366x768 resolution on the Panasonic TV, screen stays black.
Device: Orbsmart S97pro (S905x4)
Running Coreelec amlogic-ne 20

dispinfo here

Did this only work in earlier releases?

@quickfast @Orbsmartie I get something on Vertex when I limit display colour depth to 8bit.
But I am not sure if this is correct. With 12 or 10 bits I get only a black screen.

1 Like

Hi @Portisch ,
thank you for the recommendation, tried it, unfortunately same result, screen stays black and then defaults back to 1280 * 720.
Any other idea, any kind of log i could provide?

Just use 1080p?
It’s even higher than 1366*768

Would love to, however the TV (Panasonic TX-32FSW504) only supports HD Ready (1366 x 768 Pixel). :frowning:

Your disp_cap tells something else

1366 x 768 is the pixel format of your display panel, but your TV can handle 1920 x 1080 input format, and should as all “HD Ready” TVs, simply convert this to native display size of 1366 x 768

I also have such “HD Ready” TV in cellar somewhere and use 720p or 1080i, what’s the problem?

Hi,
sorry for getting back only now, TV room was in quarantine :slight_smile:

I am able to switch to 1920 x 1080 as well, however this does not really solve the problem. Same as with 1280 * 720 the kodi screen is somewhat skewed, e.g. top right time/clock is cut, same as for the starting letters of the left hand side menu.

Would 1366 x 768 fix this as being the correct resolution? If so, would you have an idea how to get there?

No, 720p would be the correct resolution. It works on my HD ready TV. It’s 16:9, same as 1080i or 1080p.

The 1366*768 is a Vesa resolution, so mainly for PC, not as TV resolution.

You might try another HDMI port because some do overscan or native resolution handling.

Looks to me that you have “Overscan” turned on on your TV. Every TV has a possibility to turn overscan off, so that all pixels are shown on display panel. Overscan is in my opinion unnecessary, as it was used in old analog TV days to get garbled picture edges out of view. Now days we all want all pixels displayed :smile:

@Sholander , @Portisch , yes, the Overscan was the issue, turned it off and now it fits exactly as it should, thanks a lot for the help!

1 Like

I have few TV’s like that, and also ran them on 1366 etc., VESA/DMT modes. Reason for this is, that this native resolution looks really better than FullHD CEA (well at least I have picture there) on these TV’s. And I dont mean overscan issue… Its like, I dont know, the density is too high/wrong/sharp, even if I always tried to smooth/blend it via TV Picture settings, it cant beat native HD Ready picture.

Usually, I dont have 23.976 on DMT mode, which is possible on CEA mode, but for some cases, where BR is not used, like TV streaming 50/60 fps etc., those VESA modes are gift from heaven for some particular TV’s…