Vehicle machine screen picture display fault detection method, device, equipment and medium

Abstract

The invention relates to the technical field of vehicle machine screen detection, in particular to a vehicle machine screen picture display fault detection method and device, equipment and a medium. The detection script adopts a C-layer interface to interact with a native service of the in-vehicle infotainment system so as to synthesize a picture for display through the native service; if the detection script is successfully loaded, triggering the detection script to run in the vehicle machine; and drawing a set color on the screen by executing an instruction corresponding to the prompt information serial number provided by the detection script, if the display color does not accord with the expectation, judging that the screen hardware has a fault, and if the detection script is executed completely and the screen picture is normal, judging that a software end code defect exists. Therefore, the whole detection process is automatically executed through the script, a tester is quickly helped to locate whether the vehicle machine screen picture fault is caused by software or hardware, the troubleshooting time is greatly shortened, and the working efficiency is improved.

Description

Technical Field

[0001] This application relates to the technical field of in-vehicle infotainment (IVI) screen detection, and particularly to a method, device, equipment and medium for detecting display faults of IVI screen images. Background Art

[0002] During the functional testing of IVI, it is quite common for faults such as screen distortion and uneven color to occur on the IVI screen. Currently, once such screen faults occur, it is often difficult for testers to quickly determine whether it is a software problem or a hardware problem of the IVI. Since the source of the fault cannot be determined, testers usually do not easily disrupt the fault phenomenon, but need to preserve the scene and notify relevant software and hardware personnel to analyze the cause together on-site. This processing method involves multiple communications and cross-departmental exchanges, which not only consumes a large amount of time and labor costs, but also has extremely low efficiency, seriously affecting the progress of IVI research and development. For example, in multiple IVI test projects, the test cycle is extended and the R & D cost is increased due to waiting for on-site analysis of the fault by all parties. Summary of the Invention

[0003] To overcome the deficiencies in the prior art, this application provides a method, device, equipment and medium for detecting display faults of IVI screen images, which can quickly and accurately detect the cause of the IVI screen image fault and automatically determine whether it is a software problem or a hardware problem.

[0004] In a first aspect, this application provides a method for detecting display faults of IVI screen images, the method including the following steps:

[0005] Execute a pre-written detection script; the detection script interacts with the native service of the IVI system through the C-layer interface to synthesize a displayable image through the native service;

[0006] If the detection script fails to load and the screen image is black, it is determined that the IVI program has not started properly; if the detection script loads successfully, trigger the detection script to run inside the IVI;

[0007] Execute the instruction corresponding to the prompt message number provided by the detection script to draw a set color on the screen. If the displayed color does not match the expectation, it is determined that there is a screen hardware fault: if the detection script execution is completed and the screen image is normal, it is determined that there is a software-side code defect.

[0008] In a possible implementation, if the detection script fails to load and the screen image is black, check whether the data cable connected to the IVI is normal. If it is normal, it is determined that the IVI program has not started properly.

[0009] In a possible implementation, the instructions corresponding to the prompt message serial numbers provided by the detection script include at least one of drawing red, green, blue, white, black, grayscale, horizontal grayscale multi-color, random color, custom input color, horizontal color bar multi-color, vertical color bar multi-color, and vertical grayscale multi-color.

[0010] In a possible implementation, by executing the instructions corresponding to the prompt message serial numbers provided by the detection script to draw a set color on the screen, if the displayed color does not match the expectation, it is determined that there is a hardware failure of the screen, including the following steps:

[0011] Sequentially execute the corresponding instructions according to the prompt message serial numbers provided by the detection script to draw a set color on the screen;

[0012] If the color corresponding to any instruction does not match the color displayed on the screen, it is determined that there is a hardware failure of the screen.

[0013] In a possible implementation, by executing the instructions corresponding to the prompt message serial numbers provided by the detection script to draw a set color on the screen, if the displayed color does not match the expectation, it is determined that there is a hardware failure of the screen, and the following steps are further included:

[0014] Execute the grayscale instruction option in the detection script. If the displayed color matches the expectation, determine whether there are hardware failures such as color difference or light leakage on the screen.

[0015] In a possible implementation, the software-side code defects include at least one of App vendor exception, software-side surfacetexture exception, and software-side GPU drawing exception.

[0016] In a possible implementation, the native service is SurfaceFlinger.

[0017] In a second aspect, the present application provides a vehicle-mounted screen display failure detection device, and the device includes:

[0018] An execution module for executing a pre-written detection script; the detection script uses a C-layer interface to interact with the native service of the vehicle-mounted system to synthesize a displayable picture through the native service;

[0019] A loading module for determining that the vehicle-mounted program fails to start normally if the detection script fails to load and the screen picture is black; if the detection script is successfully loaded, trigger the detection script to run in the vehicle-mounted device;

[0020] A judgment module is configured to execute an instruction corresponding to the prompt message serial number provided by the detection script, draw a set color on the screen, and determine a screen hardware failure if the displayed color does not match the expectation. If the detection script is executed and the screen image is normal, it is determined that there is a software-side code defect.

[0021] In a third aspect, the present application provides an electronic device, including: a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device runs, the processor communicates with the memory through the bus. When the machine-readable instructions are executed by the processor, the steps of the vehicle-mounted screen image display fault detection method according to any one of the first aspects are executed.

[0022] In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is run by a processor, the steps of the vehicle-mounted screen image display fault detection method according to any one of the first aspects are executed.

[0023] A vehicle-mounted screen image display fault detection method, device, equipment, and medium provided in this embodiment execute a pre-written detection script. The detection script uses a C-layer interface to interact with the native service of the vehicle-mounted system to synthesize a screen for display through the native service. If the detection script fails to load successfully and the screen image is black, it is determined that the vehicle-mounted program fails to start normally. If the detection script loads successfully, the detection script is triggered to run in the vehicle-mounted device. By executing an instruction corresponding to the prompt message serial number provided by the detection script, a set color is drawn on the screen. If the displayed color does not match the expectation, it is determined that there is a screen hardware failure. If the detection script is executed and the screen image is normal, it is determined that there is a software-side code defect. Thus, the entire detection process is automatically executed through the script, quickly helping testers locate whether the vehicle-mounted screen image fault is caused by software or hardware, greatly shortening the fault troubleshooting time and improving work efficiency. Description of the Drawings

[0024] To more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings required for the embodiments. It should be understood that the following drawings only show some embodiments of the present invention, and thus should not be regarded as limiting the scope. For those of ordinary skill in the art, other related drawings can be obtained based on these drawings without creative efforts.

[0025] Figure 1 Shows a flowchart of the vehicle-mounted screen image display fault detection method according to an embodiment of the present application;

[0026] Figure 2Shows the schematic diagram of the instruction corresponding to the prompt message serial number provided by the detection script in an embodiment of the present application;

[0027] Figure 3 Shows the schematic diagram of the screen when executing the detection script in an embodiment of the present application;

[0028] Figure 4 Shows the schematic structural diagram of the vehicle-mounted screen display fault detection device in an embodiment of the present application;

[0029] Figure 5 Shows the structural block diagram of the electronic device in an embodiment of the present application. Detailed implementation manners

[0030] To make the objectives, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. It should be understood that the accompanying drawings in the present application are only for the purposes of illustration and description, and are not used to limit the protection scope of the present application. In addition, it should be understood that the schematic drawings are not drawn to actual scale. The flowcharts used in the present application show the operations implemented according to some embodiments of the present application. It should be understood that the operations in the flowchart may not be implemented in sequence, and steps without logical context relationships may be reversed or implemented simultaneously. In addition, those skilled in the art may add one or more other operations to the flowchart or remove one or more operations from the flowchart under the guidance of the content of the present application.

[0031] In addition, the described embodiments are only some embodiments of the present application, rather than all embodiments. The components of the embodiments of the present application described and illustrated in the accompanying drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application claimed, but only represents the selected embodiments of the present application. All other embodiments obtained by those skilled in the art based on the embodiments of the present application without creative efforts fall within the protection scope of the present application.

[0032] It should be noted that the term "including" will be used in the embodiments of the present application to indicate the existence of the features stated hereinafter, but does not exclude the addition of other features.

[0033] In view of the technical problems proposed in the background art, the present application provides a vehicle-mounted screen display fault detection method, device, equipment and medium, which can quickly and accurately detect the cause of the vehicle-mounted screen fault and automatically determine whether it is a software problem or a hardware problem.

[0034] In one embodiment, refer to the accompanying specification Figure 1, a method for detecting faults in the display of the in-vehicle infotainment (IVI) screen provided by this application, the method comprising the following steps:

[0035] S1. Execute a pre-written detection script; the detection script uses the C-layer interface to interact with the native services of the IVI system to synthesize a displayable image through the native services;

[0036] S2. If the detection script fails to load and the screen image is black, it is determined that the IVI program has not started properly; if the detection script loads successfully, trigger the detection script to run within the IVI;

[0037] S3. By executing the instructions corresponding to the prompt message numbers provided by the detection script, draw a set color on the screen. If the displayed color does not match the expected color, it is determined that there is a hardware fault with the screen. If the detection script has been executed and the screen image is normal, it is determined that there is a defect in the software-side code.

[0038] Specifically, in step S1, the native service surfaceflinger of the IVI Android system is used to synthesize the image. The detection script uses the C-layer interface to apply for a canvas from it, directly modifies the pixel values of the canvas, and then submits it to the native service surfaceflinger for display. Among them, the C-layer interface is selected because it has high efficiency and the ability to directly access underlying resources, enabling more accurate and rapid operation of the canvas. The detection script applies for a canvas for drawing from the native service surfaceflinger and directly modifies the pixel values of the canvas without relying on any graphics library. This operation method avoids the compatibility issues and performance losses that may be brought by the graphics library, ensuring that the modification of the canvas can be more directly and accurately reflected in the final display effect. After the modification is completed, the canvas is submitted to the native service surfaceflinger, and the native service surfaceflinger is responsible for passing the modified image to the driver, which is finally displayed on the IVI hardware screen. In this way, a stable and reliable image generation mechanism is provided for subsequent fault judgment based on the display results.

[0039] In step S2, at the start of the detection, the tester only needs to click to execute a pre-written detection script. After the detection script is started, it will first perform a loading operation, and the loading process involves reading and initializing various resources and configuration information required by the detection script. If the loading is successful, the detection script will automatically send a specific command, which can trigger the detection script in the in-vehicle unit to start running. During the running of the detection script, it will collect and output relevant information for each step of the detection in real time. This information covers various states, parameters, and operation results during the detection process. For example, when detecting the running state of the in-vehicle unit, it will output the execution situation of the relevant programs started by the in-vehicle unit, the status information of the connection with the computer, etc.; when performing the detection of the screen color drawing, it will output the execution result of the drawing instruction, the comparison information between the expected color and the actual displayed color, etc. By observing and analyzing these output information, the tester can judge the specific problems of the abnormal display of the in-vehicle unit screen.

[0040] Among them, in the initial stage of the fault detection, it is necessary to judge whether the in-vehicle unit is in a normal running state. This step is judged by running the detection script. An important sign of the normal running of the in-vehicle unit is that the program in the soc (System on a Chip) runs normally. If the in-vehicle unit fails to start at all, the program in the soc cannot run normally, and in this case, the screen of the in-vehicle unit is likely to be black. When running the script, if the running fails, it is necessary to further investigate the cause. First, check the data cable connection between the computer and the in-vehicle unit. If the data cable connection is normal and the possibility of the script not running due to the connection problem is excluded, then it can be determined that the in-vehicle unit program has not started normally. This judgment process is based on a deep understanding of the startup principle of the in-vehicle unit and the running mechanism of the detection script, and can quickly locate the problem of abnormal screen display caused by the in-vehicle unit not starting normally.

[0041] In step S3, when it is determined that the in-vehicle unit has started normally, it is necessary to detect the screen hardware. The detection script provides a series of prompt information numbers, and the tester can input corresponding instructions according to these numbers. In one embodiment, see the attached Figure 2 to the specification. The instructions cover 1 - 12 options, corresponding to red, green, blue, white, black, grayscale, multi-color grayscale - horizontal graph, random color, custom input color (hexadecimal number), multi-color color bar - horizontal graph, multi-color color bar - vertical graph, multi-color grayscale - vertical graph respectively. The detection script uses the native service surfaceflinger to draw images. This method does not rely on the gallery gpu and app layers for rendering, but directly operates on the underlying display resources to ensure that the drawn colors accurately reflect the display capabilities of the screen hardware. When the tester inputs an instruction, the detection script will draw a specific color on the screen according to the instruction requirements. See the attached Figure 3If the color finally displayed on the screen is inconsistent with the expected color, whether it is color deviation, the appearance of noise, or abnormal display in some areas, it can be determined that there is a fault in the screen hardware. This detection method is based on the research of the screen display principle and the Android system image rendering mechanism, and can accurately detect problems in the screen hardware.

[0042] In addition, to more comprehensively detect the display quality of the screen, it is necessary to detect the color gamut, color difference, and light leakage of the screen. A grayscale instruction option is set in the detection script. When this option is executed, the script uses the native service surfaceflinger to draw the grayscale color gamut and outputs it to the screen side. For example, when running the script and entering the serial number 5, the screen should theoretically display a completely black screen. At this time, place the in-vehicle computer in an area with relatively dim ambient light, which can avoid interference from external light on the detection results and more clearly observe the display situation of the screen. If the screen does not display a completely black screen, there are white light spots or uneven colors, etc., it can be judged that there are light leakage or color difference problems with the screen. Through the detection and observation of the grayscale color gamut, various problems that may occur when the screen displays gray tones can be effectively discovered, further improving the detection of the screen hardware.

[0043] Furthermore, after completing various detections of the in-vehicle computer's operating state and screen hardware, if the detection script has finished executing and the screen displays a completely normal image, that is, it shows all the expected colors without any faults such as screen distortion or uneven colors, then it can be inferred that the problem lies in the software side. There may be various code defects in the software side that cause abnormal screen display, including App vendor exceptions, which means that there are exceptions in the layer of the UI of the application layer app, which may cause errors in the screen layout or display elements; surfacetexture exceptions in the software side, which will affect the texture processing and display effect of the screen; GPU drawing exceptions in the software side, which may cause deviations or errors in graphic drawing. Through the comprehensive judgment of the execution results of the detection script and the screen display situation, the problem in the software side can be accurately locked, providing a strong basis for subsequent software repair.

[0044] It can be seen that a method for detecting faults in the in-vehicle computer screen display provided by this application, the entire detection process is automatically executed by the script. The tester only needs to click to execute the script without complex operations, which reduces the technical threshold of detection and improves the detection efficiency. It can quickly help the tester locate whether the fault of the in-vehicle computer screen display is caused by software or hardware, enabling the tester to promptly contact the corresponding module personnel for processing, greatly shortening the fault troubleshooting time and improving the work efficiency. And by accurately positioning the cause of the fault, developers do not need to spend a lot of time on fault troubleshooting, but can focus their energy on problem repair, effectively reducing the workload of developers and accelerating the in-vehicle computer R & D process.

[0045] Based on the same inventive concept, an on-vehicle infotainment (IVI) screen display fault detection device is further provided in an embodiment of the present application. Since the principle of the device in the embodiment of the present application for solving problems is similar to that of the above-mentioned on-vehicle infotainment (IVI) screen display fault detection method in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be described again.

[0046] As shown in the Figure 4 accompanying drawings, an on-vehicle infotainment (IVI) screen display fault detection device provided in an embodiment of the present application includes:

[0047] An execution module 401, configured to execute a pre-written detection script; the detection script interacts with the native service of the IVI system through a C-layer interface to synthesize a displayable screen through the native service;

[0048] A loading module 402, configured to determine that the IVI program fails to start normally if the detection script fails to load and the screen is black; if the detection script is successfully loaded, trigger the detection script to run in the IVI;

[0049] A judgment module 403, configured to draw a set color on the screen by executing an instruction corresponding to a prompt message serial number provided by the detection script. If the displayed color does not match the expectation, it is determined that there is a screen hardware fault: if the detection script is executed and the screen is normal, it is determined that there is a software-side code defect.

[0050] In one embodiment, if the detection script fails to load and the screen is black, the loading module 402 detects whether the data cable connected to the IVI is normal. If it is normal, it is determined that the IVI program fails to start normally.

[0051] In one embodiment, the instructions corresponding to the prompt message serial numbers provided by the detection script include at least one of drawing red, green, blue, white, black, gray scale, horizontal gray scale multi-color, random color, custom input color, horizontal color bar multi-color, vertical color bar multi-color, and vertical gray scale multi-color.

[0052] In one embodiment, the judgment module 403 draws a set color on the screen by executing an instruction corresponding to a prompt message serial number provided by the detection script. If the displayed color does not match the expectation, it is determined that there is a screen hardware fault, including: sequentially executing the corresponding instructions according to the prompt message serial numbers provided by the detection script, and drawing a set color on the screen; if the color corresponding to any instruction does not match the screen display color, it is determined that there is a screen hardware fault.

[0053] In one embodiment, the determination module 403 executes the instruction corresponding to the prompt message serial number provided by the detection script, draws a set color on the screen, and if the displayed color does not match the expectation, determines that there is a hardware failure of the screen. It further includes: executing the grayscale instruction option in the detection script, and if the displayed color matches the expectation, determining whether there are hardware failures such as color difference or light leakage on the screen.

[0054] In one embodiment, the software - side code defects include at least one of App vendor exception, software - side surfacetexture exception, and software - side GPU drawing exception.

[0055] In one embodiment, the native service is SurfaceFlinger.

[0056] A vehicle - mounted screen display fault detection device provided by the present application executes a pre - written detection script through an execution module; the detection script uses a C - layer interface to interact with the native service of the vehicle - mounted system to synthesize a screen for display through the native service; through a loading module, if the detection script fails to load and the screen display is black, it is determined that the vehicle - mounted program fails to start normally; if the detection script is successfully loaded, the detection script is triggered to run in the vehicle - mounted device; through a judgment module, by executing the instruction corresponding to the prompt message serial number provided by the detection script, a set color is drawn on the screen, and if the displayed color does not match the expectation, it is determined that there is a hardware failure of the screen: if the detection script is executed and the screen display is normal, it is determined that there are software - side code defects. Thus, the entire detection process is automatically executed through the script, quickly helping testers locate whether the vehicle - mounted screen display fault is caused by software or hardware, greatly shortening the fault troubleshooting time and improving work efficiency.

[0057] Based on the same inventive concept of the present invention, the specification appendix Figure 5 As shown, the structure of an electronic device 500 provided by an embodiment of the present application, the electronic device 500 includes: at least one processor 501, at least one network interface 504 or other user interfaces 503, a memory 505, and at least one communication bus 502. The communication bus 502 is used to implement connection communication between these components. The electronic device 500 optionally includes a user interface 503, including a display (such as a touch screen, LCD, CRT, holographic imaging, or projector, etc.), a keyboard, or a pointing device (such as a mouse, trackball, touchpad, or touch screen, etc.).

[0058] The memory 505 may include a read - only memory and a random - access memory, and provide instructions and data to the processor 501. A part of the memory 505 may also include a non - volatile random - access memory (NVRAM).

[0059] In some embodiments, the memory 505 stores the following elements, executable modules, or data structures, or subsets thereof, or extended sets thereof:

[0060] The operating system 5051, which includes various system programs for implementing various basic services and processing hardware-based tasks;

[0061] The application program module 5052, which includes various application programs, such as a launcher, a MediaPlayer, a Browser, etc., for implementing various application services.

[0062] In the embodiments of the present application, by invoking the programs or instructions stored in the memory 505, the processor 501 is used to execute the steps in a method for detecting faults in the display of a vehicle-mounted screen, and can quickly and accurately detect the cause of the fault in the vehicle-mounted screen display, and automatically determine whether it is a software problem or a hardware problem.

[0063] The present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is run by a processor, it executes the steps in the method for detecting faults in the display of a vehicle-mounted screen.

[0064] Specifically, the storage medium can be a general storage medium, such as a removable disk, a hard disk, etc. When the computer program on the storage medium is run, it can execute the above-mentioned method for detecting faults in the display of a vehicle-mounted screen.

[0065] In the embodiments provided by the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical function division, and there can be other division methods in actual implementation. For another example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some communication interfaces. The indirect couplings or communication connections of devices or units can be electrical, mechanical or other forms.

[0066] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they can be located in one place, or they can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0067] In addition, each functional unit in the embodiments provided in the present application may be integrated into one processing unit, may exist physically alone for each unit, or two or more units may be integrated into one unit.

[0068] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), magnetic disks, or optical discs.

[0069] Finally, it should be noted that the above embodiments are only specific implementation manners of the present application, used to illustrate the technical solutions of the present application, rather than limiting it. The protection scope of the present application is not limited thereto. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: any person skilled in the art within the technical scope disclosed in the present application can still modify the technical solutions recorded in the foregoing embodiments, or can easily think of changes, or perform equivalent replacements on some of the technical features; and these modifications, changes, or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application. All should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for detecting a vehicle computer screen display fault, characterized in that: The method comprises the following steps: Execute a pre-written detection script; the detection script uses a C-layer interface to interact with the native service of the vehicle system to synthesize a screen for display through the native service; If the detection script is not loaded successfully and the screen is black, it is determined that the vehicle computer program is not started normally; if the detection script is loaded successfully, the detection script is triggered to run in the vehicle computer; By executing the instructions corresponding to the prompt information serial number provided by the detection script, the set color is drawn on the screen. If the displayed color does not match the expected color, it is determined that the screen hardware is faulty. If the detection script is executed and the screen image is normal, it is determined that there is a software code defect.

2. According to claim 1, a vehicle computer screen display fault detection method is characterized in that: in, If the detection script is not loaded successfully and the screen is black, check whether the data cable connected to the vehicle computer is normal. If normal, it is determined that the vehicle computer program is not started normally.

3. According to claim 2, a vehicle computer screen display fault detection method is characterized in that: in, The instructions corresponding to the prompt information serial number provided by the detection script include drawing at least one of red, green, blue, white, black, grayscale, horizontal grayscale multi-color, random color, custom input color, horizontal color bar multi-color, vertical color bar multi-color, and vertical grayscale multi-color.

4. According to claim 3, a vehicle computer screen display fault detection method is characterized in that: The method of executing the instruction corresponding to the prompt information serial number provided by the detection script to draw the set color on the screen, and if the displayed color does not match the expected color, determining that the screen hardware is faulty, includes the following steps: Execute corresponding instructions one by one according to the prompt information sequence number provided by the detection script, and draw the set color on the screen; If the color corresponding to any instruction is inconsistent with the screen display color, it is determined that the screen hardware is faulty.

5. A vehicle computer screen display fault detection method according to claim 4, characterized in that: The method further includes the following steps: drawing a set color on the screen by executing the instruction corresponding to the prompt information serial number provided by the detection script, and determining that the screen hardware fails if the displayed color does not match the expected color; Execute the grayscale command option in the detection script. If the displayed color is consistent with expectations, determine whether the screen has a hardware failure such as color difference or light leakage.

6. A vehicle computer screen display fault detection method according to claim 5, characterized in that: The software-side code defect includes at least one of an App vendor exception, a software-side surfacetexture exception, and a software-side GPU drawing exception.

7. A vehicle computer screen display fault detection method according to claim 6, characterized in that: The native service is SurfaceFlinger.

8. A vehicle computer screen display fault detection device, characterized in that: include: An execution module, used to execute a pre-written detection script; the detection script uses a C-layer interface to interact with a native service of the vehicle system to synthesize a screen for display through the native service; A loading module, used to determine that the vehicle computer program is not started normally if the detection script is not loaded successfully and the screen is black; if the detection script is loaded successfully, trigger the detection script to run in the vehicle computer; The judgment module is used to draw the set color on the screen by executing the instructions corresponding to the prompt information serial number provided by the detection script. If the displayed color does not match the expected color, it is determined that the screen hardware is faulty; if the detection script is executed and the screen image is normal, it is determined that there is a software code defect.

9. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and when the machine-readable instructions are executed by the processor, the steps of the vehicle screen display fault detection method as described in any one of claims 1 to 7 are performed.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the vehicle screen display fault detection method as claimed in any one of claims 1 to 7 are executed.

Images