Finally asking for help!

[Hillbilly]

So I have just recently got into the Raspberry pi addiction with a Pi 4 4gb . I am really enjoying the technical side of it and the retro side. Right now I have everything running and have installed the Raspberry Pi official OS on one card and RetroPi on another to keep things simple while I am trying to get everything figured out. The few issues I have are with my sound and my display. I have tried every tutorial to try to fix it before I asked for help. I believe that is the best way to learn for myself in particular. Do and fail if needed but now its time to ask for help.

I have this display http://www.lcdwiki.com/Main_Page attached and had issues with the pi recognizing it up I adjusted the config.txt file. The issue I have is the display leaves a 1/2" border around the left and right edges and a 1/4" border around the top and bottom edges. I have adjusted overscan, removed hashmarks, adjusted the pasted code from the LCD manufactures website, adjusted screen resolutions and all to no avail. I have pasted the config.txt file so maybe someone can tell me what is wrong with it. This is now back to its original form once the display started working for me. No matter what I adjust, there seems to be absolutely no effect on the screen.

As for sound, it is stuck on 0. Cannot adjust it at all though I do have sound coming from the jack through a small speaker in games. Absolutely refuses to connect via bluetooth. Always tells me Error Failed: Protocol not available. I am trying to get a mp3 to play during the retropi menu screen but without my volume turned up, I'm not sure I can hear it to see whether I have done it correctly or not.

Any and All help is appreciated. Let me know if there is anything else that I can provide to help solve this issue.

uncomment if you get no picture on HDMI for a default "safe" mode

hdmi_safe=1

uncomment this if your display has a black border of unused pixels visible

and your display can output without overscan

#disable_overscan=1

uncomment the following to adjust overscan. Use positive numbers if console

goes off screen, and negative if there is too much border

#overscan_left=16
#overscan_right=16
#overscan_top=10
#overscan_bottom=10

uncomment to force a console size. By default it will be display's size minus

overscan.

#framebuffer_width=1280
#framebuffer_height=720

uncomment if hdmi display is not detected and composite is being output

hdmi_force_hotplug=1

uncomment to force a specific HDMI mode (this will force VGA)

#hdmi_group=1
#hdmi_mode=1

uncomment to force a HDMI mode rather than DVI. This can make audio work in

DMT (computer monitor) modes

#hdmi_drive=2

uncomment to increase signal to HDMI, if you have interference, blanking, or

no display

config_hdmi_boost=9

uncomment for composite PAL

#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

Uncomment some or all of these to enable the optional hardware interfaces

#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

Uncomment this to enable infrared communication.

#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

Additional overlays and parameters are documented /boot/overlays/README

Enable audio (loads snd_bcm2835)

dtparam=audio=on

[pi4]

Enable DRM VC4 V3D driver on top of the dispmanx display stack

dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
overscan_scale=1

max_usb_current = 1
hdmi_force_hotplug = 1
config_hdmi_boost = 7
hdmi_group = 2
hdmi_mode = 1
hdmi_mode = 87
hdmi_drive = 1
display_rotate = 0
hdmi_cvt 1024 600 60 6 0 0 0

[i2ed3ye]

@Hillbilly The page you have linked for your display is their whole lineup so I'm not sure which one you have, but judging by your config it should be an easy fix. I have a similar display that they give me almost identical settings with.

The main issue is that you've been given a bunch of text to copy and paste without any explanation from the supplier. To top it off, what they've given you is erroneous and based on an old config. This is a great resource for figuring things out and checking whether your /boot/config.txt settings are valid and have the proper syntax: https://www.raspberrypi.org/documentation/configuration/config-txt/README.md . If you bought it off a place like Amazon, there's a good chance someone has posted the correct options in their review.

Long story short though, you should replace the last section that was added after overscan_scale=1 with:
hdmi_group = 2
hdmi_mode = 87
hdmi_cvt=1024 600 60 6 0 0 0
hdmi_drive = 2

This will properly set the resolution to the display if it indeed the correct resolution by putting the equal signs next to cvt and actually setting the option. group 2, mode 87 lets you set a custom CVT that is 1024x600 resolution @ 60 Hz with a 15:9 (6) aspect ratio and no margins (0), progressive (0), and normal blanking (0) described in https://www.raspberrypi.org/documentation/configuration/config-txt/video.md . I also find it good practice to put each option where they make sense only once so it's less confusing and doesn't cause frustration when you're changing one and then further down the same option is overriding your changes so I would recommend moving them back up into the config.txt to replace the others.

To remove the black bars, you can uncomment (remove the hashmark) from disable_overscan=1. You also more than likely won't need config_hdmi_boost=9 so you can probably comment that out.

Not super versed in audio troubleshooting. If sound is working in games, I would've thought it'd also be working in EmulationStation. Hopefully the previous mention of setting hdmi_drive to 2 will fix that. It's not making little clicks when you move around in the menus? Does changing it around from Auto, Headphones, and HDMI have any difference on whether you can change the volume? You might try using a keyboard to see if that helps or updating RetroPie through Setup.

Imagine you've tried all the Bluetooth options while getting Protocol not available? If you're trying to connect to speakers or headphones you'll probably have to follow a tutorial to add that functionality. I don't know if things have changed with the Pi 4, but I remember being rather frustrated when I finally got it to work and just started over with a new RetroPie image without it.

I hope at least the part explaining the config.txt options has been helpful to you.