[SOLVED] WIMAXIT Raspberry Pi 7" Touch Screen

[xibalba]

Are there version differences?

Here is whats on r905

Code:

pi@moode9test:~ $ dpkg -l | grep chromium
hi  chromium-browser                     126.0.6478.164-rpt1                    arm64        Chromium web browser, open-source version of Chrome
hi  chromium-browser-l10n                126.0.6478.164-rpt1                    all          chromium-browser language packages
hi  chromium-codecs-ffmpeg-extra         126.0.6478.164-rpt1                    arm64        Extra ffmpeg codecs for the Chromium Browser

yes
my versions on Raspberry Pi 3B+:

hi  chromium-browser                     124.0.6367.73-rpt1                     arm64        Chromium web browser, open-source version of Chrome
hi  chromium-browser-l10n                124.0.6367.73-rpt1                     all          chromium-browser language packages
hi  chromium-codecs-ffmpeg-extra         124.0.6367.73-rpt1                     arm64        Extra ffmpeg codecs for the Chromium Browser

What version of moode?

Release 9.0.5 2024-07-24

RPiOS: 12.5 Bookworm 64-bit | Linux: 6.6.31 64-bit                                                                                                                                                                  

Model: Pi-3B+ 1GB

Is this a fresh 905 image or an earlier version in-place upgraded to 905?

earlier version in-place upgraded to 905 

i think from 9.0.0 when for the version upgrade we must rebuild the SDcard i think for the new version

[Tim Curtis]

I should probably add chromium to the list of packages that are included in the in-place update.

[xibalba]

I should probably add chromium to the list of packages that are included in the in-place update.

ok

Canceled hold on chromium-browser.                                                                                                                                                                                  
Canceled hold on chromium-browser-l10n.                                                                                                                                                                              
Canceled hold on chromium-codecs-ffmpeg-extra.

now
hi chromium-browser 126.0.6478.164-rpt1 arm64 Chromium web browser, open-source version of Chrome
hi chromium-browser-l10n 126.0.6478.164-rpt1 all chromium-browser language packages
hi chromium-codecs-ffmpeg-extra 126.0.6478.164-rpt1 arm64 Extra ffmpeg codecs for the Chromium Browser

i will let know you if i encounter another issue

[Tim Curtis]

I ended up purchasing the 10" version of the the display and after some testing with a Pi4 it turns out that no config.txt entries are needed but the method for automatically determining the correct screen size needs to use kmsprint instead of fbset.

/home/pi/.xinitrc

Code:

# Capture screen size
#SCREENSIZE="$(fbset -s | awk '$1 == "geometry" { print $2","$3 }')"
SCREENSIZE="$(kmsprint | awk '$1 == "FB" { print $3 }' | awk -F"x" '{print $1","$2}')"

The correct KMS screen size for this display is 1600x900

Code:

pi@moode9test:~ $ kmsprint | awk '$1 == "FB" { print $3 }' | awk -F"x" '{print $1","$2}'
1600,900

Another finding was that the Pi3B+ doesn't work well with this display. There are a lot of screen glitches and all kinds of issues with popup keyboard and modals. 

With a Pi4 the display was glitch free, touch was fast and accurate and no issues with the popup keyboard or modals. I assume it will be same with Pi5. I don't have a spare 5 ATM but will get more of them at some point.

I'll prolly update the xinitrc script to use kmsprint for upcoming 9.0.6 release.

[xibalba]

I ended up purchasing the 10" version of the the display and after some testing with a Pi4 it turns out that no config.txt entries are needed but the method for automatically determining the correct screen size needs to use kmsprint instead of fbset.

/home/pi/.xinitrc

Code:

# Capture screen size
#SCREENSIZE="$(fbset -s | awk '$1 == "geometry" { print $2","$3 }')"
SCREENSIZE="$(kmsprint | awk '$1 == "FB" { print $3 }' | awk -F"x" '{print $1","$2}')"

The correct KMS screen size for this display is 1600x900

Code:

pi@moode9test:~ $ kmsprint | awk '$1 == "FB" { print $3 }' | awk -F"x" '{print $1","$2}'
1600,900

Another finding was that the Pi3B+ doesn't work well with this display. There are a lot of screen glitches and all kinds of issues with popup keyboard and modals. 

With a Pi4 the display was glitch free, touch was fast and accurate and no issues with the popup keyboard or modals. I assume it will be same with Pi5. I don't have a spare 5 ATM but will get more of them at some point.

I'll prolly update the xinitrc script to use kmsprint for upcoming 9.0.6 release.

nice!

Yes, I encountered and confirm some issues with graphic glitches on the Pi 3B+ in the power-off/reboot menu.

I will use my spare Raspberry Pi 4, but I need to find another compatible DAC. I'm not sure which one to get. i got the miniboss dac

i got this output btw with that command
kmsprint | awk '$1 == "FB" { print $3 }' | awk -F"x" '{print $1","$2}'
1024,600

with the chromium-browser update to Version 126 i dont get anymore the error code 11

[Tim Curtis]

OK, good :-)

[xibalba]

Another finding was that the Pi3B+ doesn't work well with this display. There are a lot of screen glitches and all kinds of issues with popup keyboard and modals. 

Hi Tim, just a quick update for you. After upgrading to version 9.1.0, I haven't experienced any more graphical glitches on the interface with the model you mentioned.

[Tim Curtis]

Cool :-)

[xibalba]

Cool :-)

After the update with the introduction of Log2RAM, the screen has become less responsive, and Chrome often hangs ;_;

[Tim Curtis]

What model Pi?
HDMI or DSI display?