[SOLVED] WIMAXIT Raspberry Pi 7" Touch Screen

[xibalba]

hi!

I am currently using the WIMAXIT Raspberry Pi 4 Touchscreen, model 7 m728, on a Raspberry Pi 3B+.
Despite following the configuration instructions in the manual and setting up the necessary parameters in the config file, the device remains on the login screen upon booting the Raspberry Pi. I have tried various troubleshooting steps but have not been able to resolve the issue.

Could you please provide any suggestions or additional steps I might take to successfully get past the login screen? 
its like its waiting authentication input. moode on the browser works great


thank you in advice

[DRONE7]

hi!

I am currently using the WIMAXIT Raspberry Pi 4 Touchscreen, model 7 m728, on a Raspberry Pi 3B+.
Despite following the configuration instructions in the manual and setting up the necessary parameters in the config file, the device remains on the login screen upon booting the Raspberry Pi. I have tried various troubleshooting steps but have not been able to resolve the issue.

Could you please provide any suggestions or additional steps I might take to successfully get past the login screen? 
its like its waiting authentication input. moode on the browser works great


thank you in advice

Not at my Pi currently but have you gone to the system tab and activated the options for local screen ?

[xibalba]

hi!

I am currently using the WIMAXIT Raspberry Pi 4 Touchscreen, model 7 m728, on a Raspberry Pi 3B+.
Despite following the configuration instructions in the manual and setting up the necessary parameters in the config file, the device remains on the login screen upon booting the Raspberry Pi. I have tried various troubleshooting steps but have not been able to resolve the issue.

Could you please provide any suggestions or additional steps I might take to successfully get past the login screen? 
its like its waiting authentication input. moode on the browser works great


thank you in advice

Not at my Pi currently but have you gone to the system tab and activated the options for local screen ?

yes

[TheOldPresbyope]

From their marketing material, this display appears to use an HDMI interface. I have limited experience using such displays with moOde players but the ones I have tried "just work".

I have a 3.5-in LCD HDMI display screen, for example, that mounts like a HAT on a Pi, using the GPIO pins to get its 5v power and a little HDMI-HDMI jumper plug that looks just one pictured in the WINMAXIT kit of parts. On a Pi 3B with moOde 9.0.1 unmodified in any way except to enable local display this screen works fine. (I decided the image is too small to be truly useful in this application but that's another story.)

Maybe it's time for you to explain in detail what you've done to configure your player.

What did you mean, for example, by "Despite following the configuration instructions in the manual and setting up the necessary parameters in the config file"

What's the system info output from moOde? (See other posts in the forum for how to capture this.)

Regards,
Kent

[xibalba]

Maybe it's time for you to explain in detail what you've done to configure your player.

What did you mean, for example, by "Despite following the configuration instructions in the manual and setting up the necessary parameters in the config file"

Specifically, I have added the following settings to the /boot/firmware/config.txt file as instructed on the manual:

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

I have tried various troubleshooting steps but have not been able to resolve the issue like adding this parameters:
dtoverlay=vc4-fkms-v3d
or
dtoverlay=ads7846

on Peripherals > Display its on

20240610 064747 worker: -- Peripherals
20240610 064747 worker: --
20240610 064750 worker: Local display: on
20240610 064750 worker: On-screen kbd: off
20240610 064750 worker: HDMI 4K 60Hz: off
20240610 064750 worker: Rotary encoder: off
20240610 064750 worker: USB volume knob: off
20240610 064750 worker: LCD updater: off


moode was flashed with Raspberry Pi Imager followed the setup guide, i dont have any other issue with that in fact
im using a dac hat upon the raspberry pins

let me know if i can post some other things more specific

[TheOldPresbyope]

@xibalba 

It is certainly possible the default settings in config.txt don't suit every possible HDMI display but since I don't have the same device you have I have no way of testing various solutions.

Have you tried the safe setting described in the Raspberry Pi OS documentation? (https://www.raspberrypi.com/documentatio...#hdmi_safe) Since the hdmi_safe=1 setting is described as a legacy parameter, it may or may not still work in Bookworm, but you could try the equivalent set of values listed in that description.

Other than that, I can only suggest you post your question instead on the Raspberry Pi Forum, where there's more likely to be other WIMAXIT owners, and/or to WIMAXIT themselves.

Good luck.

Regards,
Kent

[xibalba]

@xibalba 

It is certainly possible the default settings in config.txt don't suit every possible HDMI display but since I don't have the same device you have I have no way of testing various solutions.

Have you tried the safe setting described in the Raspberry Pi OS documentation? (https://www.raspberrypi.com/documentatio...#hdmi_safe) Since the hdmi_safe=1 setting is described as a legacy parameter, it may or may not still work in Bookworm, but you could try the equivalent set of values listed in that description.

Other than that, I can only suggest you post your question instead on the Raspberry Pi Forum, where there's more likely to be other WIMAXIT owners, and/or to WIMAXIT themselves.

Good luck.

Regards,
Kent

i have done that and they responded as follows:
The Raspberry Pi OS Bookworm Lite system itself may not come with a desktop control  system. In other words, you connect the HDMI signal to any other regular model HDMI monitor, it will be stuck in the software login interface too.

there is maybe a next steps to resolve this issue?

[Nutul]

The Raspberry Pi OS Bookworm Lite system itself may not come with a desktop control  system. In other words, you connect the HDMI signal to any other regular model HDMI monitor, it will be stuck in the software login interface too.

The problem is not the lack of a "desktop control system", as all moOde releases work without one.
Here the problem is that Chrome is not starting...

[xibalba]

The Raspberry Pi OS Bookworm Lite system itself may not come with a desktop control  system. In other words, you connect the HDMI signal to any other regular model HDMI monitor, it will be stuck in the software login interface too.

The problem is not the lack of a "desktop control system", as all moOde releases work without one.
Here the problem is that Chrome is not starting...

how i can start it or trying to troubleshoot?

[xibalba]

i read on the latest version 9.0.5 this:
- Add HDMI-CEC support to Local Display feature

anyone think can works now?

thank you

no its another thing, my bad