Android system upgrade methods, devices, and terminal equipment

Abstract

This application discloses an Android system upgrade method, apparatus, and terminal device. The method includes: in response to an upgrade command, performing an upgrade operation on Android system files in the system partition; compiling interface files into a vendor partition located at the hardware abstraction layer using a pre-determined compilation mechanism; and, if the upgraded Android system files pass verification, determining that the Android system upgrade is complete. This application solves the technical problem of low system stability caused by the inability to find interface files after an Android system upgrade.

Description

Technical Field

[0001] This application relates to the field of hardware control technology, and more specifically, to an Android system upgrade method and apparatus, and a terminal device. Background Technology

[0002] Currently, the definition of new hardware function interfaces in the Android system is compiled to the system partition by default, while the implementation of hardware functions is compiled to the vendor partition. When upgrading the native high version system partition of the Android system, the new hardware interface definition is not found in the original vendor partition because the high version system partition does not contain the definition of new hardware interface. This leads to abnormal operation of the Android system.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This application provides an Android system upgrade method, apparatus, and terminal device to at least solve the technical problem of low system stability caused by the inability to find interface files after an Android system upgrade.

[0005] According to one aspect of the embodiments of this application, an Android system task execution method is provided, including: in response to an upgrade instruction, performing an upgrade operation on Android system files in a system partition; compiling interface files into a vendor partition located in the hardware abstraction layer through a predetermined compilation mechanism; and determining that the Android system upgrade is complete if the upgraded Android system files pass verification.

[0006] Optionally, the interface file is compiled into the vendor partition located in the hardware abstraction layer through a predetermined compilation mechanism, including: obtaining a predefined file name and file version number; generating the interface file based on the predefined file name and file version number; verifying the interface file, and compiling the interface file into the vendor partition if the verification is successful.

[0007] Optionally, the interface file is verified, including: obtaining the hash value, file name, and version number of the interface file; verifying the hash value, file name, and version number of the interface file in sequence; and determining that the interface file has passed verification if the hash value, file name, and version number of the interface file all pass verification.

[0008] Optionally, the hash value, file name, and version number of the interface file are verified by means of the following methods: if the hash value of the interface file is consistent with a predetermined hash value, the hash value of the interface file is verified; if the file name of the interface file contains the target field, the file name of the interface file is verified; and if the version number of the interface file is consistent with a preset version number, the version number of the interface file is verified.

[0009] Optionally, the verification of the upgraded Android system file can be determined by the following methods: sending a call instruction for the target interface to the interface file located in the vendor partition through the upgraded Android system file; if the interface file calls the target interface normally, the verification of the upgraded Android system file can be determined.

[0010] Optionally, the target interface may include a hardware interface.

[0011] According to another aspect of the embodiments of this application, a terminal device is also provided, including: a memory and a processor, wherein the memory has Android system files and interface files installed, wherein the Android system files are installed in the system partition of the memory, and the interface files are compiled into the vendor partition of the memory through a predetermined compilation mechanism; the processor responds to an upgrade instruction to perform an upgrade operation on the Android system files in the system partition, and if the upgraded Android system files pass verification, it is determined that the Android system upgrade is complete.

[0012] According to another aspect of the embodiments of this application, an Android system upgrade apparatus is also provided, comprising: an upgrade module, configured to perform an upgrade operation on Android system files in a system partition in response to an upgrade command; a compilation module, configured to compile interface files into a vendor partition located in the hardware abstraction layer through a predetermined compilation mechanism; and a verification module, configured to determine that the Android system upgrade is complete if the upgraded Android system files pass verification.

[0013] According to another aspect of the embodiments of this application, a non-volatile storage medium is also provided, the non-volatile storage medium including a stored program, wherein, when the program is running, it controls the device where the non-volatile storage medium is located to execute the above-described Android system upgrade method.

[0014] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory and a processor, wherein the processor is used to run a program, wherein the program executes the above-described Android system upgrade method when running.

[0015] In this embodiment, in response to an upgrade command, an upgrade operation is performed on the Android system files in the system partition; the interface files are compiled into the vendor partition located in the hardware abstraction layer using a predetermined compilation mechanism; and if the upgraded Android system files pass verification, the method for completing the Android system upgrade is determined. By compiling the interface files into the vendor partition located in the hardware abstraction layer according to a predetermined compilation mechanism, the purpose of transferring the interface files from the system partition is achieved. This avoids the deletion of the original interface files in the system partition during the upgrade process, thereby solving the technical problem of low system stability caused by the inability to find the interface files after the Android system upgrade version. Attached Figure Description

[0016] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0017] Figure 1 This is a hardware structure block diagram of a computer terminal (or mobile device) for an Android system upgrade method according to an embodiment of this application.

[0018] Figure 2 This is a flowchart of an Android system upgrade method according to this application;

[0019] Figure 3 A schematic diagram of an optional terminal device structure according to this application;

[0020] Figure 4 This is a schematic diagram of an optional Android system upgrade device according to an embodiment of this application. Detailed Implementation

[0021] To enable those skilled in the art to better understand the present application, the technical methods of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present application.

[0022] In related technologies, the new hardware function interface files of the Android system are compiled to the system partition by default, while the hardware function implementation is compiled to the vendor partition. When upgrading the system partition of the original Android system partition separately, since the new hardware interface files are not added to the system partition, the new system partition will delete the interface files in the original system partition after the upgrade. As a result, the files in the original vendor partition cannot find the hardware interface files in the upgraded system partition, which leads to abnormal operation of the Android system.

[0023] According to an embodiment of this application, an embodiment of an Android system upgrade method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Also, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0024] The methods and embodiments provided in this application can be executed on mobile terminals, computer terminals, cloud servers, or similar computing devices. Figure 1 A hardware block diagram of a computer terminal (or mobile device) for implementing an Android system upgrade method is shown. Figure 1 As shown, the computer terminal 10 (or mobile device 10) may include one or more processors 102 (shown as 102a, 102b, ..., 102n in the figure) 102 (processor 102 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission module 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0025] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10 (or mobile device). As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0026] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the Android system upgrade method in this embodiment. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby realizing the aforementioned Android system upgrade method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0027] The transmission module 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission module 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission module 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0028] The display can be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer terminal 10 (or mobile device).

[0029] In the above-described operating scenario, this application provides an embodiment of an Android system upgrade method. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0030] Figure 2 This is a flowchart of an Android system upgrade method according to an embodiment of this application, such as... Figure 2 As shown, the method includes the following steps:

[0031] Step S202: In response to the upgrade command, perform an upgrade operation on the Android system files in the system partition;

[0032] Step S204: Compile the interface file into the vendor partition located in the hardware abstraction layer using a predetermined compilation mechanism;

[0033] Step S206: If the upgraded Android system files pass verification, confirm that the Android system upgrade is complete.

[0034] By following the steps above, the interface files can be compiled into the vendor partition located in the hardware abstraction layer according to a predetermined compilation mechanism, thereby achieving the purpose of transferring the interface files from the system partition. This avoids the system partition deleting the original interface files during the upgrade process, and solves the technical problem of low system stability caused by not being able to find the interface files after the Android system upgrade version.

[0035] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0036] It should be further explained that in practical application scenarios, the fastboot tool (a system upgrade tool) can be used to separately burn a higher version of the system file, i.e., upgrade the system file to a higher version. After the higher version system file is successfully upgraded, the Android system is run. At this time, the interface files corresponding to the newly added hardware function modules can be found in the vendor partition, thereby enabling the Android system to run normally.

[0037] In step S202, the upgrade command includes, but is not limited to, being triggered by a control on the display interface, such as mouse click, touch screen click, and other triggering operations that can trigger the upgrade operation; during the upgrade process of the Android system files in the system partition, the original old version of the Android system files and other files in the system partition will be deleted, such as the original interface files in the system partition; in an optional manner, the upgrade operation of the Android system files is to replace the original low version of the Android system files in the system with a high version of the Android system files.

[0038] In step S204, the interface files include, but are not limited to, files used to call interfaces. In actual application scenarios, debugging hardware devices, such as calling the camera, various sensors, and adjusting the volume of the speaker, all require calling the hardware interface through the interface files. Calling instructions are sent to the corresponding interface files through the instruction set of the Android system files, for example, calling the camera interface. It is understandable that in related technologies, because the interface files are compiled in the system partition, if the original interface files in the system partition are deleted during the upgrade process, the upgraded Android system files cannot find the corresponding interface files, thus preventing the normal calling of the corresponding hardware.

[0039] In step S206, one optional verification method is that after the Android system file is upgraded, if no errors occur during the operation of the Android system file and the interface can be called normally, it indicates that the upgraded Android system file has passed verification and the Android system upgrade is complete. For example, if the camera is called normally and the found interface file is the same as the interface file corresponding to the camera, it can be determined that the upgraded Android system file has passed verification.

[0040] The following detailed embodiments illustrate steps S202 to S206.

[0041] In step S204, the interface file is compiled into the vendor partition located in the hardware abstraction layer according to a predetermined editing mechanism. The specific editing mechanism is as follows:

[0042] Obtain the predefined file name and file version number; generate the interface file based on the predefined file name and file version number; verify the interface file, and if the verification is successful, compile the interface file into the vendor partition.

[0043] In related technologies, the filename of Android system interface files must contain the "android.hareware" field, and a tool needs to be defined to define such interface files in the system partition. One optional definition tool is vndk (vendor native development kit). To compile the interface files into the vendor partition of the Hardware Abstraction Layer (HAL), a new filename needs to be predefined using vndk. The new filename must contain the target field: hardware. One optional filename is ecarx.hardware. The prefix ecarx can be defined as needed. A script generates the corresponding interface file based on the predefined filename and a pre-determined file version number, and compiles the interface file into the vendor partition. In practical application scenarios, the file version number can be pre-set according to requirements.

[0044] The generated interface files need to be verified to prevent them from being tampered with. Once it is confirmed that the generated interface files have not been tampered with, the interface files are compiled into the vendor partition.

[0045] In one alternative approach, the hash value, filename, and version number of the interface file can be verified sequentially. For example, the hash value, filename, and version number of the interface file can be obtained. If the hash value, filename, and version number of the interface file all pass verification, the interface file is determined to have passed verification.

[0046] It should be noted that the hash value of the interface file can be determined by inputting the interface file into hash value calculation software or by using system commands. If the hash value of the interface file changes, it can be determined that the interface file has been tampered with.

[0047] Understandably, during the verification of the interface file, if the hash value of the interface file matches the predetermined hash value, the hash value of the interface file is determined to have passed verification; if the file name of the interface file contains the target field, the file name of the interface file is determined to have passed verification; and if the file version number of the interface file matches the preset file version number, the file version number of the interface file is determined to have passed verification.

[0048] It should be further explained that verifying the file name and version number of the interface file is to determine whether the interface file is compatible with the vendor partition, so as to avoid the file not being recognized by the vendor partition because the file name does not contain the target field. Verifying the file version number of the interface file can ensure that the interface file version is the same, so as to ensure that the interface file can run normally after being compiled into the vendor partition.

[0049] In some embodiments of this application, after compiling the interface file into the vendor partition, if there are any newly added interface files, it can be first determined whether the filename of the newly added interface file contains the target field. If the filename of the newly added interface file contains the target field, the newly added interface file is compiled into the vendor partition. It can be understood that the system identifies the newly added file through the target field to determine whether the newly added file is a qualified interface file.

[0050] The method provided in this application can be applied to interface files for controlling hardware, such as calling the camera of a terminal device to perform a shooting task. In another application scenario, during the upgrade of the system file version in the Android system installed on the terminal device, other applications are also upgraded. The method provided in this application can also be used to directly call the hardware interface. For example, when the system file is upgraded from Android 9.0 to Android 10.0, and the instant messaging tool installed on the terminal device is upgraded from version 1.0 to version 2.0, the instant messaging tool can call the terminal device's camera to take a picture through the interface file corresponding to the terminal device's camera.

[0051] This application also provides a terminal device, such as Figure 3 As shown, it includes: a memory 30 and a processor 32. The memory 30 contains Android system files and interface files. The Android system files are installed in the system partition of the memory, and the interface files are compiled into the vendor partition of the memory through a predetermined compilation mechanism. In response to the upgrade command, the processor 32 performs an upgrade operation on the Android system files in the system partition. If the upgraded Android system files pass the verification, it is determined that the Android system upgrade is complete.

[0052] It should be noted that the aforementioned terminal devices include, but are not limited to, vehicles, mobile phones, tablets, and other terminal devices that can be controlled by installing the Android system.

[0053] This application also provides an upgrade device for an Android system, such as Figure 4It includes: an upgrade module 40, used to perform upgrade operations on the Android system files in the system partition in response to upgrade instructions; a compilation module 42, used to compile the interface files into the vendor partition located in the hardware abstraction layer through a predetermined compilation mechanism; and a verification module 44, used to determine that the Android system upgrade is complete if the upgraded Android system files pass verification.

[0054] The compilation module 42 includes: a compilation submodule, which is used to obtain a predefined file name and file version number; generate an interface file based on the predefined file name and file version number; verify the interface file; and, if the verification is successful, compile the interface file into the vendor partition.

[0055] The compilation submodule includes: a verification unit, which obtains the hash value, filename, and version number of the interface file; it sequentially verifies the hash value, filename, and version number of the interface file; if all three pass verification, the interface file is deemed to have passed verification. The verification unit also includes a verification subunit, which determines that the hash value of the interface file passes verification if it matches a predetermined hash value; the filename of the interface file passes verification if it contains the target field; and the file version number of the interface file passes verification if it matches a preset version number.

[0056] The verification module 44 includes a verification submodule, which is used to send a call instruction for the target interface to the interface file located in the vendor partition through the upgraded Android system file. If the interface file calls the target interface normally, it is determined that the upgraded Android system file passes the verification. The target interface includes a hardware interface.

[0057] According to another aspect of the embodiments of this application, a non-volatile storage medium is also provided, including a stored program, wherein, when the program is running, it controls the device where the non-volatile storage medium is located to execute the above-described Android system upgrade method.

[0058] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory and a processor, wherein the processor is used to run a program, wherein the program executes the above-described Android system upgrade method when running.

[0059] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0060] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0061] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0062] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0063] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0064] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical approach of this application, in essence, or the part that contributes to the prior art, or all or part of the technical approach, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0065] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. An upgrading method of an Android system, characterized in that, The method comprises the following steps: in response to an upgrade instruction, performing an upgrade operation on an Android system file in a system partition; compiling an interface file into a vendor partition at a hardware abstraction layer through a predetermined compilation mechanism, and deleting an original hardware function interface file of an old version of the Android system file in the system partition during the upgrade operation; in a case where the upgraded Android system file passes verification, determining that the Android system is upgraded, and the interface file is a new hardware function interface file; compiling the interface file into the vendor partition at the hardware abstraction layer through the predetermined compilation mechanism, comprising: obtaining a pre-defined file name and a file version number; generating the interface file according to the pre-defined file name and the file version number; verifying the interface file, and compiling the interface file into the vendor partition in a case where the verification is passed, wherein the pre-defined file name contains a target field: hardware.

2. The method of claim 1, wherein, verifying the interface file, comprising: obtaining a hash value of the interface file, a file name of the interface file, and a file version number of the interface file; verifying the hash value of the interface file, the file name of the interface file, and the file version number of the interface file in sequence, and determining that the interface file passes verification in a case where the hash value of the interface file, the file name of the interface file, and the file version number of the interface file all pass verification.

3. The method of claim 2, wherein, determining that the hash value of the interface file passes verification in a case where the hash value of the interface file is consistent with a pre-determined hash value; determining that the file name of the interface file passes verification in a case where the file name of the interface file contains a target field; determining that the file version number of the interface file passes verification in a case where the file version number of the interface file is consistent with a pre-set file version number. determining that the upgraded Android system file passes verification by the following method, comprising:

4. The method of claim 1, wherein, sending a calling instruction of a target interface to the interface file in the vendor partition through the upgraded Android system file, and determining that the upgraded Android system file passes verification in a case where the interface file normally calls the target interface. The target interface comprises a hardware interface.

5. The method of claim 4, wherein, The method comprises the following steps:

6. A terminal device, characterized by comprising: a memory and a processor, the memory being installed with an Android system file and an interface file, wherein the Android system file is installed in a system partition in the memory, and the interface file is compiled into a vendor partition of the memory through a predetermined compilation mechanism; the processor performs an upgrade operation on the Android system file in the system partition in response to an upgrade instruction, and determines that the Android system is upgraded in a case where the upgraded Android system file passes verification. The method comprises the following steps:

7. An apparatus for upgrading an Android system, characterized by comprising: an upgrade module, configured to perform an upgrade operation on an Android system file in a system partition in response to an upgrade instruction; ​ The compiling module is configured to compile the interface file into a vendor partition at a hardware abstraction layer through a predetermined compiling mechanism, and delete original hardware function interface files of old version Android system files in the system partition during the upgrading operation; The verifying module is configured to determine that the Android system is upgraded when the upgraded Android system files pass the verification, the interface file is a new hardware function interface file, and the compiling of the interface file into the vendor partition at the hardware abstraction layer through the predetermined compiling mechanism comprises: obtaining a predefined file name and a file version number; generating the interface file according to the predefined file name and the file version number; verifying the interface file, and compiling the interface file into the vendor partition when the verification is passed, wherein the predefined file name contains a target field: hardware.

8. A non-volatile storage medium, characterized by The non-volatile storage medium comprises a stored program, wherein the non-volatile storage medium controls a device in which the non-volatile storage medium is located to execute the upgrading method of the Android system according to any one of claims 1 to 5 when the program is running.

9. An electronic device, comprising: The device comprises a memory and a processor, and the processor is configured to run a program, wherein the device executes the upgrading method of the Android system according to any one of claims 1 to 5 when the program is running.

Images