Screen log acquisition method and device, equipment and storage medium

Abstract

The invention relates to the technical field of intelligent cabins, in particular to a screen log acquisition method, device and equipment and a storage medium, and the method comprises the steps: responding to a screen log acquisition demand of external storage equipment accessed to a vehicle-mounted terminal system when the external storage equipment accessed to the vehicle-mounted terminal system is identified; reading a pre-defined configuration description file in an external storage device; according to the configuration of the configuration description file, collecting and exporting corresponding screen log data, and generating a screen log file; the screen log file is copied to the external storage device, and a screen log export prompt is displayed, so that the situation that log export is affected due to the fact that the external storage device is pulled up in the waiting process of a user is avoided. According to the scheme, the effective log when the screen is abnormal can be obtained in time, the problem analysis and positioning period is shortened, and therefore the working efficiency of a research and development team is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of intelligent cockpit, and particularly relates to a screen log acquisition method and device, equipment and a storage medium. BACKGROUND

[0002] With the rapid development of Internet technology, intelligent cockpit has ushered in an era of rapid development. In the process of continuous iteration of intelligent cockpit software, logs, as an important part of recording system module working state and abnormal information, play a crucial role in analyzing the root cause of problems, solving abnormal problems and improving user experience for developers. However, in the existing technology, there are mainly two ways to obtain logs: one is to obtain logs through a U disk, and the user needs to perform a series of operations on the vehicle machine to export the logs to the U disk; the other is to directly pull the logs through a remote interface. However, these two ways have obvious deficiencies when the screen is abnormal. When the screen is abnormal, such as screen flickering, black screen and the like, the user cannot operate the screen, and thus cannot trigger the log export function, resulting in that the logs cannot be imported into the U disk.

[0003] In addition, since the screen logs are not recorded in real time into the system logs, remote acquisition of logs often lacks some key information, which cannot provide effective log support for problem analysis. This brings great difficulty to developers in problem analysis and positioning, prolongs the problem solving cycle, and also increases the cost of manpower and material resources for test personnel to reproduce the problem phenomenon. SUMMARY

[0004] In order to solve the above problems, the present application provides a screen log acquisition method, device, equipment and storage medium, which can quickly and effectively acquire screen abnormal log when the screen is abnormal, thereby shortening the problem analysis and positioning cycle and improving work efficiency.

[0005] To achieve the above purpose, the present application adopts the following technical solutions:

[0006] In a first aspect, the present application provides a screen log acquisition method, which comprises:

[0007] When an external storage device accessing the vehicle machine system is identified, a screen log acquisition requirement of the external storage device accessing the vehicle machine system is responded to;

[0008] A pre-defined configuration description file in the external storage device is read;

[0009] According to the configuration of the configuration description file, corresponding screen log data is collected and exported, and a screen log file is generated;

[0010] The screen log file is copied to the external storage device, and a screen log export prompt is displayed.

[0011] Optionally, the response to the requirement of the head unit system for accessing the screen log of the external storage device further comprises:

[0012] When an abnormality of the central control screen is monitored, the factory mode is started based on the requirement of the head unit system for accessing the screen log of the external storage device.

[0013] In the factory mode, the screen log acquisition command is sent to the screen driver based on the received requirement for accessing the screen log through the Android middleware and the QNX middleware.

[0014] Optionally, the predefinition of the configuration description file comprises:

[0015] A plurality of functions of different service applications of the head unit system are acquired to generate a function list.

[0016] The operation content corresponding to different functions in the function list is described to obtain a description file; a configuration area is located in the description file, the screen log type and the log level parameter corresponding to the log operation type identifier are sequentially set in the configuration area, and the log path for exporting the screen log file is defined to generate the configuration description file.

[0017] The log level parameter comprises a debug level, an information level, a warning level and an error level of the screen log.

[0018] The screen log type comprises an operating system screen log, a hardware device screen log, a user operation log, a display content log, a fault diagnosis log and a security audit log.

[0019] Optionally, the description of the operation content corresponding to different functions in the function list to obtain the description file comprises:

[0020] A log operation type identifier is added to the description file in a self-defined text format to represent the operation to be performed by the description file.

[0021] An operation switch is set for the description file, and the operation of the description file is set to be performed or not performed by switching the operation switch to an open mode or a closed mode, and a state identifier representing that the operation switch is in the open mode or the closed mode is added; if the value of the state identifier is ON, the operation switch is in the open mode; if the value of the state identifier is OFF, the operation switch is in the closed mode.

[0022] When the operation switch is switched to the open mode, the operation of the description file is performed; when the operation switch is switched to the closed mode, the operation of the description file is not performed.

[0023] Optionally, the screen log file is generated by collecting and exporting the corresponding screen log according to the configuration of the configuration description file.

[0024] According to the screen log type and log level parameters in the configuration description file, screen-related log data is collected; the collected screen-related log data is packaged and summarized with the car machine system log to generate a screen log file.

[0025] Optionally, the collecting of the screen-related log data according to the screen log type and log level parameters in the configuration description file comprises:

[0026] The log operation type identifier in the configuration description file is read to identify the operation performed by the configuration description file;

[0027] According to the screen log type and log level parameters of the configuration description file under the current operation, the log content required to be included in the exported log and the log level output by the car machine are determined;

[0028]

[0029] According to the log content required to be included in the exported log and the log level output by the car machine, screen-related log information is collected,

[0030] Screen log data matching the requirements of the configuration description file in the car machine system is obtained.

[0031] Optionally, the copying of the screen log file to the external storage device and the display of the screen log export prompt comprise: according to the pre-defined log path in the configuration description file, the exported screen log file is copied to a directory accessed by the external storage device;

[0032] Real-time reception of progress signals in the log collection and file copying process, display of log collection progress and screen log file copying progress on the central control screen; after the screen log file is copied to the external storage device, the log export result is prompted on the central control screen.

[0033] In a second aspect, the present application provides a screen log acquisition device, which comprises:

[0034] The identification module is configured to, when an external storage device accessing the car machine system is identified, respond to the screen log acquisition requirement of the external storage device accessing the car machine system;

[0035] The reading module is configured to read a pre-defined configuration description file in the external storage device;

[0036] The screen log generation module is configured to collect and export corresponding screen log data according to the configuration of the configuration description file, and generate a screen log file;

[0037] ​The display module is configured to copy the screen log file to the external storage device and display a screen log export prompt.

[0038] In a third aspect, the present application provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0039] When an external storage device accessing the car machine system is identified, a screen log acquisition requirement of the external storage device accessing the car machine system is responded to;

[0040] A pre-defined configuration description file in the external storage device is read;

[0041] According to the configuration of the configuration description file, corresponding screen log data is collected and exported to generate a screen log file;

[0042] The screen log file is copied to the external storage device, and a screen log export prompt is displayed.

[0043] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the following steps:

[0044] When an external storage device accessing the car machine system is identified, a screen log acquisition requirement of the external storage device accessing the car machine system is responded to;

[0045] A pre-defined configuration description file in the external storage device is read;

[0046] According to the configuration of the configuration description file, corresponding screen log data is collected and exported to generate a screen log file;

[0047] The screen log file is copied to the external storage device, and a screen log export prompt is displayed.

[0048] Compared with the closest prior art, the present application has the beneficial effects of:

[0049] The screen log acquisition method, device, equipment and storage medium provided by the present application solve the problem that the existing external storage device cannot be used to acquire effective screen logs when the screen is abnormal. Through the present application, the user can insert the external storage device when the screen is abnormal, without the need for other operations, and can import the effective logs of the screen abnormality into the external storage device, thereby providing effective log support for developers and avoiding the situation that the fault problem cannot be analyzed due to the lack of logs.

[0050] The technical solution of the present application avoids the waste of manpower and material resources caused by the repeated reproduction of the problem by the test personnel, improves the work efficiency of the research and development team, and saves the cost.

[0051] The technical solution of the present application is simple and effective. The user only needs to insert the external storage device, and the screen log can be obtained based on the configuration file content pre-stored in the external storage device, so that the developer can quickly analyze and locate the problem by combining the obtained log, and the tester does not need to invest energy to retest the problem. BRIEF DESCRIPTION OF DRAWINGS

[0052] In order to more clearly illustrate the specific embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the specific embodiments or prior art description will be briefly introduced below. In all the drawings, similar elements or parts are generally identified by similar reference numerals. In the drawings, each element or part is not necessarily drawn according to the actual scale.

[0053] Figure 1 is a screen log acquisition method flowchart provided by the present application;

[0054] Figure 2 is a screen log acquisition device structure schematic diagram provided by the present application;

[0055] Figure 3 is a hardware device structure diagram for screen log acquisition provided by the present application;

[0056] Figure 4 is an internal structure diagram of a computer device provided by the present application. DETAILED DESCRIPTION

[0057] The embodiments of the technical solutions of the present application will be described in detail below with reference to the drawings. The following embodiments are only used to more clearly illustrate the technical solutions of the present application, and therefore only serve as examples, and cannot limit the protection scope of the present application.

[0058] It should be noted that, unless otherwise specified, the technical terms or scientific terms used in the present application should be understood as the usual meaning understood by the skilled person in the field to which the present application belongs.

[0059] The present application provides a screen log acquisition method, device, equipment and storage medium, and the embodiments of the present application will be described below with reference to the drawings:

[0060] Please refer to Figure 1 , Figure 1 A screen log acquisition method is provided for embodiment 1 of the present application, and the specific steps of the method include:

[0061] S101, when an external storage device accessing the car machine system is identified, responding to the screen log acquisition demand of the external storage device accessing the car machine system;

[0062] S102 reads a pre-defined configuration description file in the external storage device;

[0063] S103 collects and exports corresponding screen log data according to the configuration of the configuration description file, and generates a screen log file;

[0064] S104 copies the screen log file to the external storage device, and displays a screen log export prompt.

[0065] The above step S101 further includes the following steps in response to the screen log acquisition requirement of the external storage device connected to the car machine system:

[0066] When an abnormality occurs in the central control screen, the factory mode is started based on the screen log acquisition requirement of the external storage device connected to the car machine system;

[0067] In the factory mode, the screen log acquisition command is sent to the screen driver based on the received screen log acquisition requirement through the Android middleware and the QNX middleware.

[0068] The pre-definition of the configuration description file in the above step S102 includes the following steps:

[0069] Obtain a function list by acquiring a plurality of functions mapped by different service applications of the car machine system;

[0070] Describe the operation content corresponding to different functions in the function list to obtain a description file; locate a configuration area in the description file, set the screen log type and log level parameter corresponding to the log operation type identifier in the configuration area in sequence, and define the log path of the screen log file export to generate the configuration description file;

[0071] The log level parameter includes the debug level, information level, warning level and error level of the screen log.

[0072] The screen log type includes the operating system screen log, hardware device screen log, user operation log, display content log, fault diagnosis log and security audit log.

[0073] In the above embodiment, the description file is obtained by describing the operation content corresponding to different functions in the function list, which includes the following steps:

[0074] A log operation type identifier is added to the description file in a self-defined text format to represent the operation to be performed by the description file;

[0075] An operation switch is set for the description file, and by switching the opening or closing mode of the operation switch, whether the operation of the description file is executed is set, and a state identifier indicating that the operation switch is in the opening and closing mode is added; if the state identifier is ON, it indicates that the operation switch is in the opening mode; if the state identifier is OFF, it indicates that the operation switch is in the closing mode.

[0076] When the operation switch is switched to the opening mode, the operation of the description file is executed; when the operation switch is switched to the closing mode, the operation of the description file does not need to be executed.

[0077] In the above step S103, the screen log file is generated by collecting and exporting the corresponding screen log according to the configuration of the configuration description file.

[0078] According to the screen log type and log level parameters in the configuration description file, screen-related log data is collected; the collected screen-related log data is packaged and summarized with the vehicle machine system log to generate a screen log file.

[0079] In the above embodiment, according to the screen log type and log level parameters in the configuration description file, screen-related log data is collected, which includes:

[0080] Reading the log operation type identifier in the configuration description file to identify the operation of the configuration description file;

[0081] According to the screen log type and log level parameters in the configuration description file, the log content required to be exported and the log level output by the vehicle machine are determined under the current operation.

[0082]

[0083] According to the log content required to be exported and the log level output by the vehicle machine, screen-related log information is collected,

[0084] Obtaining screen log data in the vehicle machine system that matches the requirements of the configuration description file.

[0085] In the above step S104, the screen log file is copied to the external storage device, the screen log file is copied to the external storage device, and the screen log export prompt is displayed, which includes: according to the log path defined in the configuration description file, the exported screen log file is copied to the directory connected to the external storage device.

[0086] Real-time receiving of progress signals in the log collection and file copying process, displaying the log collection progress and screen log file copying progress on the central control screen; after the screen log file is copied to the external storage device, the log export result is prompted on the central control screen.

[0087] ​To make the technical problems to be solved by the present application clearer, according to the above specific embodiments, the following examples are provided.

[0088] The following examples are not only suitable for exporting a conventional screen log, but also suitable for deep log collection under abnormal triggering and flexible log export configured by a user.

[0089] Example 1: Conventional screen log export

[0090] Scenario: A vehicle maintenance personnel needs to export a car machine system log for fault analysis.

[0091] Step: Device access and demand response

[0092] The maintenance personnel inserts a U disk into a car machine USB interface, the system detects that an external storage device is accessed, and automatically triggers a screen log acquisition process.

[0093] The system reads a ScreenLogConfig.xml configuration description file under a root directory of the U disk, and parses log types (such as “fault diagnosis log” and “hardware device screen log”) and log levels (“error level” and “warning level”) defined in the configuration description file.

[0094] According to the configuration file, the system captures a screen rendering log by calling a SurfaceFlinger service in an Android middleware, and simultaneously obtains hardware state data (such as backlight current and touch IC response time) from a screen driver layer by a QNX middleware.

[0095] The two types of logs are aligned according to timestamps, packaged as ScreenLog_20250627_1430.zip, and stored in a temporary directory.

[0096] The system copies the log file to the U disk according to a path specified in the configuration file / Udisk / Diagnostics / , and displays a progress bar (“Log collection: 100% | File copy: 45%”) on a central control screen.

[0097] After the copying is completed, a prompt box “The screen log has been exported to the U disk, and the file size is 23MB” is popped up.

[0098] Example 2: Deep log collection under abnormal triggering

[0099] Scenario: A user feedbacks that a central control screen frequently flashes, and needs to locate a hardware or software fault

[0100] Step: Abnormal monitoring and factory mode starting

[0101] The system monitors that a screen refresh rate is abnormal (such as detecting that a frame rate is lower than 30 FPS for three times in succession), automatically starts a factory mode, disables an entertainment application, and switches to a diagnosis interface.

[0102] Send log collection instruction to Window Manager Service through Android middleware, and send GET_PANEL_REGISTERS command to screen driver through QNX middleware to obtain register-level hardware log;

[0103] OS log: Capture the error stack in the Android system log related to SurfaceFlinger and Gralloc.

[0104] Hardware log: Record the EDID data and VCOM voltage fluctuation curve output by the screen driver.

[0105] User operation log: Trace back the touch coordinate sequence within the last 10 seconds before the splash screen (such as [(1024, 576), (1030, 580)...]).

[0106] Hierarchical export and path customization: Export complete log package according to DebugLevel=5 (highest debug level) in the configuration file and save it to the specified path / FlashDump / on the U disk.

[0107] The central control screen displays the hierarchical progress prompt "Collecting GPU memory leak log... (remaining 2 / 5 modules)" in real time.

[0108] In Example 2, by directly reading the screen driver registers through QNX middleware, hardware-level exceptions that cannot be reflected by traditional logs (such as VCOM voltage drift) can be captured.

[0109] Example 3: Flexible log export customized by users

[0110] Scenario: Developers need to test the touch response delay of the new version of UI.

[0111] Step: Dynamic definition of configuration file

[0112] Developers provide custom configuration files through U disk.

[0113] When the system parses the file, enable the "operation switch" to activate the touch coordinate collection function.

[0114] Log collection: Continuously record the screen display content (such as button highlight state, animation frame key frame) and touch events (such as TOUCH_DOWN(x=800, y=400)).

[0115] According to the requirements of the debug level, additional onDraw() method execution timestamps of UI threads are collected;

[0116] Real-time progress feedback and result verification.

[0117] The central control screen displays in two columns: "Log collection: touch points (15 / 20) | rendering frames (300 / 300)" and "File copy: 65%".

[0118] After the export is completed, the system generates an MD5 check file TouchDelayLogs.md5 for the developer to verify the data integrity.

[0119] The "operation switch" mechanism of embodiment 3 allows to enable / disable specific log modules on demand, avoiding the impact of full log on system performance (CPU occupancy is reduced by 17% when the switch is off).

[0120] Based on the same inventive concept, the embodiment of the present application also provides a screen log acquisition device for implementing the above-mentioned screen log acquisition method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above-mentioned embodiment method, so the specific limitations in one or more screen log acquisition device embodiments provided below can refer to the limitations of the screen log acquisition method in the above text, which will not be repeated here.

[0121] In one embodiment, the screen log acquisition device provided by the embodiment of the present application, as shown in Figure 2 includes an identification module 210, a reading module 220, a screen log generation module 230, and a display module 240, wherein:

[0122] The identification module 210 is configured to respond to the screen log acquisition requirement of the external storage device accessing the car machine system when the external storage device accessing the car machine system is identified.

[0123] The reading module 220 is configured to read a pre-defined configuration description file in the external storage device.

[0124] The screen log generation module 230 is configured to collect and export corresponding screen log data according to the configuration of the configuration description file, and generate a screen log file.

[0125] The display module 240 is configured to copy the screen log file to the external storage device and display a screen log export prompt.

[0126] The working process of the above device is as follows: the hardware structure of the above device is as shown in Figure 3 which includes two systems of QNX and Android, and a total of 7 parts: factory mode, Android middleware, QNX middleware, screen driver, screen hardware, system log, and system service. When the screen is abnormal, the specific process of log acquisition is as follows:

[0127] 1, Put the system U disk into a specific file (the specific file indicates the need to obtain the screen log), and then insert the U disk into the car system

[0128] 2, The system service recognizes the specific file, receives the demand for obtaining the screen log, and sends the demand to the factory mode

[0129] 3, The factory mode sends the screen log obtaining command to the screen driver through the Android middleware and the QNX middleware

[0130] 4, The screen driver operates the screen hardware, and collects the screen related log into the car system log

[0131] 5, After the screen log is collected into the car system log operation is completed, copy the car system log to the U disk, and constantly play the log copy progress during the collection process to avoid the user pulling out the U disk during the waiting process, affecting the log export

[0132] During the entire operation process, the user only needs to insert the U disk one action, which can complete the acquisition of the screen abnormal log, the operation is simple and effective, the developer can quickly analyze and locate the problem, the tester also does not need to invest energy to retest the problem, and the work efficiency of the research and development team is improved.

[0133] Further, in order to make the technical problems to be solved by the present application more clear, according to the specific implementation scheme of the above-mentioned screen log acquisition device, the following embodiments are provided.

[0134] Example 4: Assuming that a certain automobile manufacturer develops a new intelligent cockpit system, and frequently appears screen flickering, black screen and other abnormal problems. These problems seriously affect the user experience, and also bring great trouble to the development team. Since the existing log acquisition method cannot provide effective log information when the screen is abnormal, the developer is difficult to quickly locate the root cause of the problem, resulting in a long problem solving period and increased development cost.

[0135] In order to solve the above-mentioned problems, the automobile manufacturer decides to use the screen log acquisition device of the present application. The specific implementation steps are as follows:

[0136] Prepare the system U disk: the development team prepares a system U disk, and creates a specific marker file in the U disk, which is used to indicate the need to obtain the screen log.

[0137] Insert the U disk: when the screen appears abnormal, the user inserts the system U disk with the marker file into the car system.

[0138] System service recognition: after the system service of the car system detects the marker file in the U disk, it recognizes the user's demand for obtaining the screen log, and sends the demand to the factory mode.

[0139] Factory mode processing: After receiving the requirement of obtaining the screen log, the factory mode sends a command to the screen driver through the Android middleware and the QNX middleware to obtain the screen log.

[0140] Screen driver operation: After receiving the command, the screen driver operates the screen hardware and aggregates the screen-related log information into the log of the car system.

[0141] Log copying: After the screen log is aggregated into the car system log, the system automatically copies the car system log to the U disk. During the copying process, the system constantly plays the log copying progress to remind the user not to remove the U disk, so as to avoid affecting the log export.

[0142] By using the device of the present application, the developer can quickly obtain effective screen log information when the screen is abnormal. These log information provides detailed problem clues for the developer, so that they can quickly locate the root cause of the problem and take corresponding solving measures. Compared with the past, the problem solving period is greatly shortened, the development efficiency is significantly improved, and the human and material costs of the test personnel to reproduce the problem phenomenon are also reduced.

[0143] Although the device of the present application has been able to solve the problem of being unable to obtain effective log when the screen is abnormal, in actual application, some alternative solutions can be considered to further optimize the performance and function of the device. For example:

[0144] Wireless transmission: In addition to obtaining the log through the U disk, wireless transmission can also be considered to directly transmit the screen log to the developer's device. This way can further simplify the user's operation steps and improve the convenience of log acquisition.

[0145] Automatic triggering mechanism: In some cases, screen abnormalities may occur instantaneously, and the user may not have time to insert the U disk. In order to deal with this situation, an automatic triggering mechanism can be designed to automatically start the log acquisition process when the system detects a screen abnormality, without the need for the user to manually insert the U disk.

[0146] Real-time log synchronization: In order to ensure that the remote log acquisition can obtain complete log information, a real-time log synchronization mechanism can be designed to synchronize the screen log to the system log in real time. In this way, even if the log cannot be directly obtained when the screen is abnormal, the remotely acquired log can also contain complete screen log information.

[0147] Through the implementation of the above solutions, the performance and function of the device of the present application can be further improved, and the needs of different users can be better met.

[0148] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 4 As shown, the computer device includes a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. When executed by the processor, the computer program implements a screen log acquisition method. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device casing, or an external keyboard, touchpad, or mouse.

[0149] Those skilled in the art will understand that Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0150] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0151] When an external storage device connected to the vehicle infotainment system is detected, respond to the screen log retrieval request of the external storage device connected to the vehicle infotainment system.

[0152] Read the predefined configuration description file from the external storage device;

[0153] Based on the configuration in the configuration description file, collect and export the corresponding screen log data to generate a screen log file.

[0154] Copy the screen log file to an external storage device and display a prompt to export the screen log.

[0155] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0156] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when executed, can include the processes of the above-mentioned embodiment methods. Any reference to memory, storage, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration but not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0157] Any combination of the technical features of the above embodiments can be made. In order to make the description simple, all possible combinations of the technical features in the above embodiments are not described, but as long as the combination of the technical features does not exist, it should be considered as the scope of the present application.

[0158] The above embodiments only express several implementation manners of the present application, and the description is more specific and detailed, but it should not be understood as a limitation on the scope of the patent. It should be pointed out that for those skilled in the art, without departing from the concept of the present application, some modifications and improvements can be made, which are all within the protection scope of the present application. Therefore, the protection scope of the patent of the present application should be subject to the appended claims.

Claims

1. A method for obtaining screen logs, characterized in that, The method includes: When an external storage device connected to the vehicle infotainment system is detected, respond to the screen log retrieval request of the external storage device connected to the vehicle infotainment system. Read the predefined configuration description file from the external storage device; Based on the configuration in the configuration description file, collect and export the corresponding screen log data to generate a screen log file. Copy the screen log file to an external storage device and display a prompt to export the screen log.

2. The method as described in claim 1, characterized in that, Following the request to retrieve screen logs from the external storage device accessing the vehicle infotainment system, the following also includes: When an anomaly is detected in the central control screen, the factory mode is initiated based on the screen log acquisition requirements of the external storage device connected to the vehicle system. In factory mode, the Android middleware and QNX middleware send screen log retrieval commands to the screen driver based on the received screen log retrieval requirements.

3. The method as described in claim 1, characterized in that, The predefined features of the configuration description file include: Obtain multiple functions mapped to different service applications in the vehicle infotainment system and generate a function list; Describe the operation content corresponding to different functions in the function list to obtain a description file; locate the configuration area in the description file, set the screen log type and log level parameters corresponding to the log operation type identifier in the configuration area, and define the log path exported from the screen log file to generate a configuration description file; The log level parameters include the debug level, information level, warning level, and error level of the screen log; The screen log types include operating system screen logs, hardware device screen logs, user operation logs, display content logs, fault diagnosis logs, and security audit logs.

4. The method as described in claim 3, characterized in that, The description of the operation content corresponding to different functions in the function list, and the resulting description file, includes: A custom text format is used to add a log operation type identifier to the description file to indicate the operation that the description file needs to perform; An operation switch is set for the description file. By switching the on or off mode of the operation switch, the operation of the description file is set to whether it is executed, and a status flag is added to indicate that the operation switch is in the on or off mode. If the status flag is ON, it means that the operation switch is in the on mode; if it is OFF, it means that the operation switch is in the off mode. When the operation switch is switched to the ON mode, the operations in the description file will be executed; when the operation switch is switched to the OFF mode, the operations in the description file will not be executed.

5. The method as described in claim 1, characterized in that, The step of collecting and exporting corresponding screen logs and generating screen log files according to the configuration description file includes: Based on the screen log type and log level parameters in the configuration description file, collect screen-related log data; package the collected screen-related log data, and summarize it with the vehicle system log to generate a screen log file.

6. The method as described in claim 5, characterized in that, The step of collecting screen-related log data based on the screen log type and log level parameters in the configuration description file includes: Read the log operation type identifier in the configuration description file to identify the operation performed by the configuration description file; Under the current operation, based on the screen log type and log level parameters in the configuration description file, determine the package required for exporting logs. Includes log content and log levels output by the vehicle's infotainment system; Based on the required log content to be included in the exported logs and the log level output by the vehicle's infotainment system, collect relevant log information from the screen. Obtain screen log data from the vehicle infotainment system that matches the requirements of the configuration description file.

7. The method as described in claim 1, characterized in that, The step of copying the screen log file to an external storage device and displaying a screen log export prompt includes: copying the exported screen log file to the directory of the external storage device according to the log path predefined in the configuration description file; The system receives progress signals during log collection and file copying in real time, displays the log collection progress and log file copying progress on the central control screen, and displays the log export results on the central control screen after the log file is copied to an external storage device.

8. A screen log acquisition device, characterized in that, The device includes: The identification module is used to respond to the screen log acquisition request of the external storage device connected to the vehicle system when the external storage device connected to the vehicle system is identified. The read module is used to read predefined configuration description files from external storage devices. The screen log generation module is used to collect and export the corresponding screen log data according to the configuration description file and generate screen log files. The display module copies the screen log file to an external storage device and displays a prompt to export the screen log.

9. A computer device, comprising a memory and a processor, characterized in that, The memory stores a computer program, and when the processor executes the computer program, it performs the following steps: When an external storage device connected to the vehicle infotainment system is detected, respond to the screen log retrieval request of the external storage device connected to the vehicle infotainment system. Read the predefined configuration description file from the external storage device; Based on the configuration in the configuration description file, collect and export the corresponding screen log data to generate a screen log file. Copy the screen log file to an external storage device and display a prompt to export the screen log.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it performs the following steps: When an external storage device connected to the vehicle infotainment system is detected, respond to the screen log retrieval request of the external storage device connected to the vehicle infotainment system. Read the predefined configuration description file from the external storage device; Based on the configuration in the configuration description file, collect and export the corresponding screen log data to generate a screen log file. Copy the screen log file to an external storage device and display a prompt to export the screen log.

Images