7inch raspberry pi touch screen with aosp 13 size problem
-
wrote on 29 Jul 2024, 11:28 last edited by Sakhana99
I’m working on a project using a Raspberry Pi 4 with a custom Android 13 ROM and the official 7" Raspberry Pi touchscreen.
The touchscreen display is zoomed in, causing part of the display to be cut off and not fit the screen properly. The resolution settings do not seem to address this issue.
here is my config.txt file:kernel=Image.gz arm_64bit=1 dtparam=audio=on # The functional overlay dtoverlay=vc4-fkms-v3d-pi4-overlay,cma-256 # Touchscreen and backlight overlays dtoverlay=rpi-ft5406-overlay dtoverlay=rpi-backlight-overlay #dtoverlay=vc4-kms-dsi-7inch-overlay,sizex=800,sizey=480 # Additional settings #dtoverlay=dwc2,dr_mode=peripheral initramfs ramdisk.img followkernel enable_uart=1 disable_overscan=1 #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 display_rotate=0 # Enable the DSI display ignore_lcd=0 display_default_lcd=1 # Display settings framebuffer_width=800 framebuffer_height=480 gpu_mem=256 hdmi_group=2 hdmi_mode=87 hdmi_cvt=800 480 60 6 0 0 0 dtparam=spi=on
NB: both vc4-kms-v3d-pi4-overlay (white screen) and vc4-kms-dsi-7inch-overlay ( correct dtbo file generation problem or blocked in splash screen step) did not work for me that's why i am working with vc4-fkms-v3d-pi4-overlay,cma-256 overlay .
NB:the home screen you are seeing is a qt quick interface
also tried with wm size command but it did not solve the problem
-
Hi,
I am not sure if I understand this correctly. When a touch screen is zoomed in, parts of the desktop will be off-screen. That's kind of natural behavior, just like zooming into a phone.
What is the expected behavior? -
I’m working on a project using a Raspberry Pi 4 with a custom Android 13 ROM and the official 7" Raspberry Pi touchscreen.
The touchscreen display is zoomed in, causing part of the display to be cut off and not fit the screen properly. The resolution settings do not seem to address this issue.
here is my config.txt file:kernel=Image.gz arm_64bit=1 dtparam=audio=on # The functional overlay dtoverlay=vc4-fkms-v3d-pi4-overlay,cma-256 # Touchscreen and backlight overlays dtoverlay=rpi-ft5406-overlay dtoverlay=rpi-backlight-overlay #dtoverlay=vc4-kms-dsi-7inch-overlay,sizex=800,sizey=480 # Additional settings #dtoverlay=dwc2,dr_mode=peripheral initramfs ramdisk.img followkernel enable_uart=1 disable_overscan=1 #overscan_left=16 #overscan_right=16 #overscan_top=16 #overscan_bottom=16 display_rotate=0 # Enable the DSI display ignore_lcd=0 display_default_lcd=1 # Display settings framebuffer_width=800 framebuffer_height=480 gpu_mem=256 hdmi_group=2 hdmi_mode=87 hdmi_cvt=800 480 60 6 0 0 0 dtparam=spi=on
NB: both vc4-kms-v3d-pi4-overlay (white screen) and vc4-kms-dsi-7inch-overlay ( correct dtbo file generation problem or blocked in splash screen step) did not work for me that's why i am working with vc4-fkms-v3d-pi4-overlay,cma-256 overlay .
NB:the home screen you are seeing is a qt quick interface
also tried with wm size command but it did not solve the problem
wrote on 29 Jul 2024, 12:00 last edited by Pl45m4@Sakhana99 said in 7inch raspberry pi touch screen with aosp 13 size problem:
The touchscreen display is zoomed in, causing part of the display to be cut off and not fit the screen properly
So you want your Qt Quick "overlay" to be independent from the rest of the underlaying display content?!
The kmh gauge should be fixed size and position? -
wrote on 29 Jul 2024, 12:01 last edited by Sakhana99
i did not zoom in i mean the display is bigger than the screen itself when it boots it already boots bigger than the touch screen i am looking for a way to resize it so it fits
-
i did not zoom in i mean the display is bigger than the screen itself when it boots it already boots bigger than the touch screen i am looking for a way to resize it so it fits
wrote on 29 Jul 2024, 12:03 last edited by Pl45m4@Sakhana99 said in 7inch raspberry pi touch screen with aosp 13 size problem:
i am looking for a way to resize it so it fits
QML issue?
https://forum.qt.io/topic/86294/creating-a-window-fit-for-the-all-space-of-the-screen
?
-
wrote on 29 Jul 2024, 12:16 last edited by
no it's an OS or the overlay itself issue not qml or qt thing
-
Looks a bit like the android screen drivers don't support the screen.
Have you tried booting with embedded linux, to see if the eglfs drivers get it correctly?
If they don't, it could be a hardware defect. Nothing surprises me anymore with these embedded systems.... -
wrote on 29 Jul 2024, 13:20 last edited by
yes i tried with embedded linux and it worked well
i am pretty sure that i added all the necessary drivers -
I don’t have the very same screen and I don’t use Android on the Pi4. Does the screen work with a non Qt application?
-
wrote on 30 Jul 2024, 11:08 last edited by
the problem is not with qt sir it's with the resolution of the OS itself
-
wrote on 30 Jul 2024, 11:40 last edited by
@Sakhana99 said in 7inch raspberry pi touch screen with aosp 13 size problem:
the problem is not with qt sir it's with the resolution of the OS itself
Why post this in a Qt forum, when you know it's an issue of your device?
Maybe we hardware guys here who know what's going on, but most people can't help you with this. -
wrote on 31 Jul 2024, 08:53 last edited by
it's not a device issue but a qt with android issue and maybe some of you have worked with android
-
wrote on 31 Jul 2024, 10:46 last edited by
@Sakhana99 said in 7inch raspberry pi touch screen with aosp 13 size problem:
the problem is not with qt sir it's with the resolution of the OS itself
but then
@Sakhana99 said in 7inch raspberry pi touch screen with aosp 13 size problem:
it's not a device issue but a qt with android issue
so which one is it?
-
yes i tried with embedded linux and it worked well
i am pretty sure that i added all the necessary drivers@Sakhana99 said in 7inch raspberry pi touch screen with aosp 13 size problem:
yes i tried with embedded linux and it worked well
If that means that the screen zooms correctly, it’s not a hardware issue.
It’s probably a hardware compatibility issue with the Android low level driver.
That’s not Qt related, it’s Android related.
1/14