# T95 s1 issue with display

**URL:** <https://emuelec.discourse.group/t/t95-s1-issue-with-display/2059>\
**Category:** Amlogic Devices\
**Created:** [July 21, 2023, 9:18pm UTC](https://emuelec.discourse.group/t/t95-s1-issue-with-display/2059 "2023-07-21T21:18:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![compusat22](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@compusat22](https://emuelec.discourse.group/u/compusat22)\
**Post date:** [July 21, 2023, 9:18pm UTC](https://emuelec.discourse.group/t/t95-s1-issue-with-display/2059/1 "2023-07-21T21:18:06Z")

</div>

![IMG_20230721_214257](https://global.discourse-cdn.com/free1/uploads/emuelec/original/1X/619575c83028f4f76ecbc0005782b5b7f1a3760c.jpeg)  
Anyone know why this is happening,  
New install on a t95 s1, s905w 2g,  
When it was first booted with latest ng build, it doesn’t display anything but boots up and is available on ssh, when resolution is put in config.ini it displays the emulec boot screen perfectly but black on emulationstation.  
When resolution put into emulec.conf it shows a garbled display with 4 overlaping screens.

On same bo latest coreelec build same issue when installed first installed (all black) but when resolution is placed in boot, it displays a similar corrupt coreelec boot screen but Kodi displays perfectly.  
Batocera runs perfectly but can’t sort analogue audio on it.

---

<div class="post-metadata">

**Author:** ![Langerz82](https://avatars.discourse-cdn.com/v4/letter/l/bc79bd/32.png) [@Langerz82](https://emuelec.discourse.group/u/Langerz82)\
**Post date:** [July 22, 2023, 10:02am UTC](https://emuelec.discourse.group/t/t95-s1-issue-with-display/2059/2 "2023-07-22T10:02:56Z")

</div>

s905w have a locked frame buffer resolution of 1080p that cannot be changed in the latest version.

If you want to change resolution you have to apply this PR:

> <https://github.com/EmuELEC/EmuELEC/pull/1208>
>
> This patch enables the user to set the framebuffer values different from the out…put resolution. CVBS is a classic example of using a different internal resolution, however others might benefit from being able to output in whatever there external display shows and have a lower or higher framebuffer resolution. It would also be an advantage for 2D games to use lower resolutions and perform faster, as well as some 3D emulation depending on the type.
> 
> I will make frame buffer resolutions and bordering configurable in ES in the near future, I have some code but it's outdated with this script and possibly causing some memory allocation issues which I need to fix.
> 
> For now to change the framebuffer resolution from standard (matched to resolution) to custom the user needs to enter into emuelec.conf for example with 720p60hz:
> \`\`\`
> ee\_es.framebuffer.720p60hz=640 480
> ee\_emu.framebuffer.720p60hz=640 480
> \`\`\`
> ee\_es stands for the fb resolution in emulationstation.
> ee\_emu stands for when the user enters an emulator.
> 720p60hz is an example display mode we are changing it for.
> 640 480 is telling the setres script to set the fb 640px width, 480px height.
> 
> This patch also allows setting black borders to the framebuffer by giving the x1,y1,x2,y2 location of the pixels to shift the display to. Please note the following is the pixel locations NOT the x,y width, and height, that would be calculated as so:
> \`\`\`
> x1 = x\_pos
> y1 = y\_pos
> x2 = x1+width-1
> y2 = y1+height-1
> \`\`\`
> So for a 10 pixel border around a 640x480 frame it would be:
> width = 640-20 (double 10 pixels)
> height = 480-20 (double 10 pixels)
> 
> \`\`\`
> ee\_emu.framebuffer\_border.720p60hz=10 10 629 469
> \`\`\`
> Note - Old Amlogic (s905M, s905W) devices have a locked framebuffer so you can change display mode, but cannot change it's 1920 1080 internal buffer.
> 
> edit:
> This PR is designed to work with ES PR: 
> https://github.com/EmuELEC/emuelec-emulationstation/pull/78

And recompile a build. But bear in mind internally its still 1080p.

---

<div class="post-metadata">

**Author:** ![compusat22](https://avatars.discourse-cdn.com/v4/letter/c/9f8e36/32.png) [@compusat22](https://emuelec.discourse.group/u/compusat22)\
**Post date:** [July 22, 2023, 11:37am UTC](https://emuelec.discourse.group/t/t95-s1-issue-with-display/2059/3 "2023-07-22T11:37:23Z")

</div>

Thanks for the info, but how is it I have another s905w (x96 mini) running 4.6 ng without an issue, is it to do with the monitor it’s connected to?

Also how do I easily put a pull request into a build, last time I manually edited the scripts before building as it was only 2 lines but this seems a lot more complex.

Again Thanks for info and solution, was looking at emuelec GitHub and the work you have done especially with regards resolution and setres has been outstanding, (maybe you would be a good candidate to fork this and manage it as it as it seems to be dead or at least on life support ATM not to knock the excellent work that the current owner has put in to get it this far)

---

<div class="post-metadata">

**Author:** ![Langerz82](https://avatars.discourse-cdn.com/v4/letter/l/bc79bd/32.png) [@Langerz82](https://emuelec.discourse.group/u/Langerz82)\
**Post date:** [July 22, 2023, 11:51am UTC](https://emuelec.discourse.group/t/t95-s1-issue-with-display/2059/4 "2023-07-22T11:51:02Z")

</div>

Not sure why your other one works fine, but yeah s905w cant change resolution easily with EE I think 4.5 (correction) onwards.

If you know how to build, here is the latest version that should have those changes in it.

> **[GitHub - Langerz82/EmuELEC at dev\_4.6.1-TEST](https://github.com/Langerz82/EmuELEC/tree/dev_4.6.1-TEST)**
>
> dev\_4.6.1-TEST

Remember to switch to the branch after a clone with:

```auto
git checkout dev_4.6.1-TEST

```

edit:  
Also here is a really long thread discussing the issue lol:

> <https://github.com/EmuELEC/EmuELEC/issues/900>
>
> My S905w (tx3 mini) worked fine with 720p resolution until yesterday, when I did… a clean install to 4.5 version. I just can't change the resolution to 720p without glitches.
> Thanks.
