How to change screen resolution of Raspberry Pi [closed] - raspberry-pi

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago.
Improve this question
I am using 7" TFT LCD Display with the Raspberry pi, can anyone tell how i can change the screen resolution of Raspberry Pi and what should be the resolution for the 7" TFT LCD Display.

Just run the following simple command on Raspberry Pi 3 running Raspbian Jessie.
run terminal and type
sudo raspi-config
Go to: >Advanced Option > Resolution >
just set your resolution compatible fit with your screen.
then
reboot
If you didn't found the menu on configuration, please update your raspberry pi software configuration tool (raspi-config).
That's all TQ.

I made the following changes in the /boot/config.txt file, to support my 7" TFT LCD.
Uncomment "disable_overscan=1"
overscan_left=24
overscan_right=24
Overscan_top=10
Overscan_bottom=24
Framebuffer_width=480
Framebuffer_height=320
Sdtv_mode=2
Sdtv_aspect=2
I used this video as a guide.

If you are like me using a TFT that is connected via SPI (e. g. PiTFT 2.8" 320x240) driven by FBTFT in combination with fbcp to utilise hardware accelerated video decoding (using omxplayer) like it is descriped here. You should add the following into the /boot/config.txt to force the output to HDMI and set the resolution to 320x240:
hdmi_force_hotplug=1
hdmi_cvt=320 240 60 1 0 0 0
hdmi_group=2
hdmi_mode=87

As other comments here pointed out, you'll need to uncomment disable_overscan=1
in /boot/config.txt
if you are using NOOBS (this is what im using), you'll find in the end of the file a set of default settings that has disable_overscan=0 attribute. you'll need to change its value to 1, and re-boot.

You can change the display resolution graphically (without using Terminal) on Raspbian GNU/Linux 8 (jessie) using following window.
Application Menu > Preferences > Raspberry Pi Configuration > System > Set Resolution.
Click to view screenshots

Default Rpi resolution is : 1366x768 if i'm not mistaken.
You can change it though.
You will find all the information about it in this link.
http://elinux.org/RPiconfig
Search "hdmi mode" on that page.
Hope it helps.

TV Sony Bravia KLV-32T550A
Below mention config works greatly
You should add the following into the /boot/config.txt to force the output to HDMI and set the
resolution 82 1920x1080 60Hz 1080p
hdmi_ignore_edid=0xa5000080
hdmi_force_hotplug=1
hdmi_boost=7
hdmi_group=2
hdmi_mode=82
hdmi_drive=1

After uncommenting
disable_overscan=1
follow my lead. In the link, http://elinux.org/RPiconfig when you search for Video options, you'll also get hdmi_group and hdmi_mode. For, hdmi_group choose 1 if you're using you TV as an video output or choose 2 for monitors. Then in hdmi_mode, you can select the resolution you want from the list.
I chose :-
hdmi_group=2
hdmi_mode=23
And it worked.

This works for me
hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_cvt 800 480 60 6 0 0 0
max_usb_current=1

Related

No GPS on Raspberry Pi LineageOS 18.1

UPDATED See edit!
I have installed LineageOS 18.1 for Raspberry Pi 4 (which is an awesome piece of software) and everything seems to be working correctly.
With the exception of GPS. I have an A9G connected to the Pi. It is connected to the first Pi's UART and I can see the data coming on ttyAMA0.
:/ # microcom -s 9600 /dev/ttyAMA0
$GNGGA,092800.998,4955.7547,N,00900.2330,E,0,0,,102.0,M,48.0,M,,*5E
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$BDGSA,A,1,,,,,,,,,,,,,,,*0F
$GPGSV,1,1,00*79
$BDGSV,1,1,00*68
$GNRMC,092800.998,V,4955.7547,N,00900.2330,E,0.000,0.00,211021,,,N*55
$GNVTG,0.00,T,,M,0.000,N,0.000,K,N*2C
$GNGGA,092801.998,4955.7547,N,00900.2330,E,0,0,,102.0,M,48.0,M,,*5F
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$BDGSA,A,1,,,,,,,,,,,,,,,*0F
$GPGSV,1,1,00*79
$BDGSV,1,1,00*68
$GNRMC,092801.998,V,4955.7547,N,00900.2330,E,0.000,0.00,211021,,,N*54
$GNVTG,0.00,T,,M,0.000,N,0.000,K,N*2C
$GNGGA,092802.998,4955.7547,N,00900.2330,E,0,0,,102.0,M,48.0,M,,*5C
I changed the GPS receiver to use ttyAMA0 in /vendor/build.prop
# GPS ro.kernel.android.gps=ttyAMA0
I also trying with adding
ro.kernel.android.gpsttybaud = 9600
or
ro.kernel.android.gps.speed = 9600
But not a single App can receive GPS data.
I have the feeling I am missing something very simple but essential.
Any help very appreciated
EDIT
Ok, I am a step further. The first problem was apparently, what a bummer, a permission issue.
I adjusted it in the file: /vendor/ueventd.rc
From:
/dev/ttyAMA0 0660 bluetooth bluetooth
To:
/dev/ttyAMA0 0660 system radio
Now it seems that the data is being received and correctly interpreted. But when I open a GPS testing App, the signal is flickering. It almost like if something else is reading from ttyACM0.
Is it possible?
just to clarify what I mean with "flickering", please take a look at https://cloud.sobi.pro/f/68f0398aea1549918376/
I also had the same flickering issue. I can see it in a map program or with physics toolbox where I can see the GPS LAT LONG. It flickers between the "real" position and 0.00000 for the LAT and LONG.
I am using LineageOS17.1 on a Raspberry Pi 4
my Ultimate GPS USB is from Adafruit and is on /dev/ttyUSB0
I tried updating build.prop in both /vendor and /system with the
ro.kernel.android.gps.speed = 9600
and
ro.kernel.android.gps = ttyUSB0
The solution that I eventually used was to remove the r0.kernel... from both build.prop and use the app GPS Connector
https://play.google.com/store/apps/details?id=de.pilablu.gpsconnector&hl=en_US&gl=US
Enable in developer options under "select mock location app" you can select the GPS Connector.
You can have the GPS Connector app start at boot.
If you find a more elegant solution than using an app, please reply.

Cannot Use Raspberry Pi Camera v1/2 with Gumstix Pi Compute Dev Board

Referencing this item:
https://store.gumstix.com/gumstix-pi-compute-dev-board.html
I cannot use the official Pi camera(s) using either the official Raspberry Pi "Buster" disk image or the Pi disk image provided by Gumstix:
Disk image referenced here--> https://store.gumstix.com/raspberry-pi-cm-fast-flash.html
Note: The Gumstix Pi image would "hang" on the rainbow colored splash screen during boot, using the image above. I am using the "fast flash" board to write the images, and have been able to repeatedly (successfully) install the standard Raspbian OS. FYI I have been using Balena Etcher, and it has worked with my other boards.
Also, I followed the official instructions to add camera support in an attempt to understand what I am doing wrong. vcgencmd initially reported no support or detection in raspbian. I was able to add camera support using the blobs mentioned here (I compliled manually and also used the precompiled variant):
https://www.raspberrypi.org/documentation/hardware/computemodule/cmio-camera.md
Final result:
vcgencmd get_camera : supported=1 detected=0
Lastly, yes the camera is enabled, and I have tested the cam/cable on other systems with no issues. I suspect the pin GPIO settings may be to blame, but based on the information in front of me (for this board) I should not be expecting to manually adjust those params. Thanks for any insight….hopefully this is an I-D-10-T error.
First off I should appologize, the page you referenced about getting the disk image is very out of date. We will work to update it soon.
My guess of why it's not booting is likely a hardware imcompatibilty, are you using a Raspberry Pi CM3+?
Give this image a try
https://gumstix-raspbian.s3.amazonaws.com/2019-12-29/raspberrypi-cm3/rpi-4.19.y/2019-09-26-raspbian-buster-lite.img.xz
That's a recently compiled Buster image that has some extra drivers added in to support Geppetto modules. The default Buster image should also work.
To properly support any of our boards, it's best to download the board support package for that particular design. In your case, you're using the Gumstix Pi Compute Dev Board, which can be found
https://geppetto.gumstix.com/#!/design/1045/
Please go to that page and click on the "AutoBSP" button on the top. That will prompt you to download a zip file that will contain some instructions and files needed to configure the Raspberry Pi.
Please let me know if you have any trouble.
Thanks,
Andrew

Interfacing the 1366x768 HDMI display on raspberry pi

I have HDMI display which has corrupted EDID checksum and its working with other ARM board with work around.
The same display I am using on Rpi3 & rpi zero boards and got the below output image.
https://drive.google.com/file/d/13h7srCBQk_LqK2OXenCvuwivFZBHoO_9/view
Seems its using correct 1366x768 resolution but color is not correct, what could be the problem ?
And this is my config.txt file.
https://drive.google.com/file/d/1ydf13vYktgfleqCeXJb2SZX6PsErL1dq/view
Here is the link where I discussed the issue. BTW, this HDMI diplay works with Windows & Linux PC without any issues.
https://www.toradex.com/community/questions/19407/change-hdmi-lcd-resolution-in-toradex-imx6-board.html
Patches:
https://share.toradex.com/lg644qhtqv1jnk9?direct
https://share.toradex.com/pyzdaan5ozk9v4k?direct
How the EDID is handled in rpi hdmi driver if any corrupted or incorrect EDID data present ?
Thanks for the support & help.
The below forum link solved the problem. Hope it would help someone.
https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=205958&p=1277210#p1277210

3.5 LCD does not start on my Rasberry pi-2 Model B windows 10

I am using a Raspberry Pi 2 Model B. I also have a 3.5 inch Touch Display LCD for Raspberry Pi. I am running the Raspberry Pi with the attached Touch screen, but it only shows a white screen. It is connected via the GPIO port. I have installed Windows 10 IOT OS.
1) How can it connect to Raspberry Pi?
2) Why is it only White(Blank) Screen showing?
Usually, the 3.5 Inch LCD Display Modules require special drivers that do not come standard with the Raspbian OS. They either come packed with the Module itself (Usually for Raspbian) or are downloadable from the web. I'm not aware of any drivers for Windows 10, but with a datasheet you may be able to configure it for yourself (This may serve as a starting point for that kind of project if that's what you really want to do.)
To answer your two questions:
(1) The Display connects to the Raspberry by via the GPIO Port. You have already done this.
(2) The screen is white because this is the default state of the module when it is plugged in and not utilised.
Hope this helps!
I had the same problem! I solved it last night. Here is the answer on my post: How do you get a waveshare 3.5 inch touch LCD to work with Raspbian Jessie?. Hope this helps!

Emulate an IP Camera [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 1 year ago.
Improve this question
I am using software (DVR) that is meant to talk directly to an IP camera. I am trying to pass a h264 stream directly into it, but it does not work if I just throw a stream onto it.
Can you recommend any "spoofing" software to emulate an IP camera? For the sake of argument, we can say that the camera we want to emulate is Axis P3301.
Given that a lot of software out there can talk to IP cameras, is there a way to use something like vlc/ffmpeg to look like its an IP camera ?
Thanks.
Axis IP cameras provide video through RTSP. Any RTSP server can be used to spoof the video aspect of an IP camera.
Examples:
Streaming with VLC
Open VLC
Select Media > Stream
Select source media, then click "Stream"
Click "next" to confirm the source
Under "New Destination" select "RTSP"
Deselect "Activate Transcoding" (make sure your source is h264/aac)
Click Add.
Select port and path to mimick the camera. Port is usually 554 but path varies by camera model.
Click Stream
Now you can connect with your DVR software.
Note that Axis cameras also have APIs to pant/tilt/zoom and set options like resolution and bitrate. You won't be able to emulate that.
Another good option is the Axis SDK that's available as part of their Application Development Partner program. The SDK includes software that will mimic an Axis camera perfectly. To join you fill out some paperwork and talk to a representative, but there's no cost and if you're working with Axis there are a ton of benefits.
http://www.axis.com/partner/adp_program/index.htm
If you want to fully emulate an Axis camera, there is a free software provided by Axis which allows you to do it with all the functionalities. It is mandatory to have that camera just one time to create the virtual camera template.
Axis Virtual Camera Download