CN116700740B

CN116700740B - Software repairing method and related device

Info

Publication number: CN116700740B
Application number: CN202211202898.1A
Authority: CN
Inventors: 彭光明
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-09-29
Filing date: 2022-09-29
Publication date: 2024-06-04
Anticipated expiration: 2042-09-29
Also published as: CN116700740A

Abstract

The embodiment of the application provides a software repairing method and a related device, and relates to the technical field of terminals. When the electronic equipment detects that the electronic equipment is started, starting the first partition mounting; loading the attribute of a first partition, wherein a patch mirror image with read-only attribute is stored in the first partition; after loading of the first partition is completed, the attributes of a second partition different from the first partition are loaded. Therefore, the electronic device can realize quick repair of the software by loading the patch image containing the read-only attribute, so that the time for repairing the software is saved, and the user experience is improved.

Description

Software repairing method and related device

Technical Field

The application relates to the technical field of terminals, in particular to a software repairing method and a related device.

Background

After the software of the electronic device is released, there may be some problems that need to be repaired.

In some implementations, the electronic device may download an upgrade package of a new software version that includes data information of the new software version. The electronic equipment installs the downloaded upgrade package of the new software version, and updates the software version to the latest version so as to repair the problem of the software.

However, in the above implementation, it takes a lot of time to install the upgrade package of the new software version, which affects the user experience.

Disclosure of Invention

The embodiment of the application provides a software repairing method and a related device, which save the time spent on software repairing and improve the user experience.

In a first aspect, an embodiment of the present application provides a software repairing method, applied to an electronic device, including:

when the starting-up is detected, starting up the first partition mounting; loading the attribute of a first partition, wherein a patch mirror image with read-only attribute is stored in the first partition; after loading of the first partition is completed, the attributes of a second partition different from the first partition are loaded.

Therefore, when the electronic device is started, the attribute of the first partition is loaded firstly, because the patch mirror image of the read-only attribute is stored in the first partition, the read-only attribute is modified when the first partition is loaded, and after the first partition is loaded, the electronic device reloads the attribute of the second partition, so that even if the read-only attribute which is the same as that of the first partition exists in the second partition, the value of the read-only attribute is modified when the first partition is loaded, the read-only attribute of the second partition cannot be revalidated, the loaded read-only attribute cannot be influenced when the attribute of the second partition is loaded, the modification of the read-only attribute of software by the patch mirror image of the loaded read-only attribute is realized, the electronic device does not need to reload the complete software package, the time spent for software restoration is reduced, and the user experience is improved.

In one possible implementation, the first partition has a patch image of the read-only property of the application program stored therein, and the second partition is used to store the application property of the application program. Thus, the situation that the application program has problems due to unreasonable attribute values can be repaired in a targeted manner through the patch image of the read-only attribute of the application program.

In one possible implementation, the read-only attribute includes msc.app_latch_interaction_right_angle, ro.vendor.mtk_pq_color_mode, or ro.netflix.bsp_rev. Thus, modification of different read-only attributes can be realized, and the richness of attribute modification is increased.

In one possible implementation manner, when the startup is detected, before the first partition mount is started, the method further includes: displaying a first interface, the first interface comprising: the system comprises prompt information for prompting the application program to be the latest version and a first button, wherein the first button comprises information for prompting the application program to need repairing; receiving a trigger for a first button; responsive to a trigger to the first button, displaying a second interface; the second interface includes a second button; receiving a trigger for a second button; and in response to triggering the second button, downloading the patch package of the application program, and storing the patch image of the read-only attribute of the application program in the patch package into the first partition.

For example, the first interface may be an interface shown in a in fig. 5, and the first button may be an area where the "software problem exists and needs to be repaired" prompt information is located in the interface shown in a in fig. 5. The second interface may be the interface shown as b in fig. 5. The second button may be a "download and install" control in the interface shown in b in fig. 5 when the function of automatic download under WLAN is off state in the interface shown in c in fig. 6, and may be an "install" control when the function of automatic download under WLAN is on state.

Therefore, when the application program is the latest version, the patch package is downloaded based on the triggering of the user, so that the user can autonomously select whether to download the patch package or not, and the user experience is improved.

In one possible implementation, the method further includes: after the patch mirror image of the read-only attribute of the application program in the patch package is stored in the first partition, displaying a third interface; the third interface includes a third button; receiving a trigger for a third button; in response to a trigger to the third button, the electronic device is restarted.

Illustratively, the third interface may be the interface shown in c in fig. 5, or the interface shown in b in fig. 3, or the interface shown in c in fig. 4, and the third button may be the "immediately restarted" control in the above-described interface.

Therefore, the electronic equipment is restarted under the condition of user consent, and the user experience is improved.

In one possible implementation manner, when the startup is detected, before the first partition mount is started, the method further includes: displaying a fourth interface, the fourth interface comprising: a first switch for controlling the on or off of the function of repairing the software problem at night, and a second switch for controlling the on or off of the function of installing the upgrade package at night; receiving an operation of setting the first switch to an on state; and restarting the electronic equipment when the electronic equipment is determined to be in an idle state within a preset time period.

The fourth interface may be, for example, the interface shown in fig. 6 b.

Therefore, the user can self-define the function of repairing the software problem at night to be started or closed, and when the function of repairing the software problem at night is started, the electronic equipment can be automatically restarted in an idle state, so that the electronic equipment can automatically complete software repair in the idle state, and the user experience is improved.

In one possible implementation, an electronic device includes a kernel layer that, when a boot-up is detected, initiates a first partition mount; loading the attribute of the first partition; after loading of the first partition is completed, loading the attribute of the second partition; comprising the following steps: when the starting-up is detected, starting up a first partition mount in a kernel layer; loading the attribute of the first partition in the kernel layer; after loading of the first partition is completed, the attributes of the second partition are loaded at the kernel layer.

In a second aspect, an embodiment of the present application provides a software repairing apparatus, where the software repairing apparatus may be an electronic device, or may be a chip or a chip system in the electronic device. The software repair device may include a display unit and a processing unit. When the software repair device is an electronic device, the display unit may be a display screen. The display unit is configured to perform the step of displaying to enable the electronic device to implement a software repair method as described in the first aspect or any one of the possible implementations of the first aspect. When the software repair device is an electronic device, the processing unit may be a processor. The software repair device may further comprise a storage unit, which may be a memory. The storage unit is configured to store instructions, and the processing unit executes the instructions stored in the storage unit, so that the electronic device implements a software repair method described in the first aspect or any one of possible implementation manners of the first aspect. When the software repair device is a chip or a system of chips within an electronic device, the processing unit may be a processor. The processing unit executes instructions stored by the storage unit to cause the electronic device to implement a software repair method as described in the first aspect or any one of the possible implementations of the first aspect. The memory unit may be a memory unit (e.g., a register, a cache, etc.) within the chip, or a memory unit (e.g., a read-only memory, a random access memory, etc.) within the electronic device that is external to the chip.

The processing unit is used for starting the first partition mounting when the starting-up is detected;

the processing unit is also used for loading the attribute of the first partition, wherein the first partition stores the patch mirror image with the read-only attribute;

and the processing unit is also used for loading the attribute of a second partition after the loading of the first partition is completed, and the second partition is different from the first partition.

In one possible implementation, the first partition has a patch image of the read-only property of the application program stored therein, and the second partition is used to store the application property of the application program.

In one possible implementation, the read-only attribute includes msc.app_latch_interaction_right_angle, ro.vendor.mtk_pq_color_mode, or ro.netflix.bsp_rev.

In one possible implementation, the display unit is configured to display a first interface, where the first interface includes: the system comprises prompt information for prompting the application program to be the latest version and a first button, wherein the first button comprises information for prompting the application program to need repairing; the processing unit is also used for receiving the trigger of the first button; the display unit is also used for responding to the trigger of the first button and displaying a second interface; the second interface includes a second button; receiving a trigger for a second button; and the processing unit is also used for responding to the trigger of the second button, downloading the patch package of the application program and storing the patch mirror image of the read-only attribute of the application program in the patch package into the first partition.

In one possible implementation manner, the display unit is further configured to display a third interface after storing the patch image of the read-only attribute of the application program in the patch package into the first partition; the third interface includes a third button; the processing unit is also used for receiving the trigger of the third button; and the processing unit is also used for restarting the electronic equipment in response to the trigger of the third button.

In a possible implementation manner, the display unit is further configured to display a fourth interface, where the fourth interface includes: a first switch for controlling the on or off of the function of repairing the software problem at night, and a second switch for controlling the on or off of the function of installing the upgrade package at night; the processing unit is also used for receiving the operation of setting the first switch to the on state; the processing unit is further configured to restart the electronic device when the electronic device is determined to be in an idle state in a preset time period.

In one possible implementation manner, the processing unit is specifically configured to start the first partition mount when a start-up is detected; loading the attribute of the first partition; after loading of the first partition is completed, loading the attribute of the second partition; comprising the following steps: when the starting-up is detected, starting up a first partition mount in a kernel layer; loading the attribute of the first partition in the kernel layer; after loading of the first partition is completed, the attributes of the second partition are loaded at the kernel layer.

In a third aspect, an embodiment of the present application provides an electronic device, including a processor and a memory, the memory being configured to store code instructions, the processor being configured to execute the code instructions to perform the method described in the first aspect or any one of the possible implementations of the first aspect.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium having stored therein a computer program or instructions which, when run on a computer, cause the computer to perform the method described in the first aspect or any one of the possible implementations of the first aspect.

In a fifth aspect, embodiments of the present application provide a computer program product comprising a computer program which, when run on a computer, causes the computer to perform the method described in the first aspect or any one of the possible implementations of the first aspect.

In a sixth aspect, the present application provides a chip or chip system comprising at least one processor and a communication interface, the communication interface and the at least one processor being interconnected by wires, the at least one processor being adapted to execute a computer program or instructions to perform the method described in the first aspect or any one of the possible implementations of the first aspect. The communication interface in the chip can be an input/output interface, a pin, a circuit or the like.

In one possible implementation, the chip or chip system described above further includes at least one memory, where the at least one memory has instructions stored therein. The memory may be a memory unit within the chip, such as a register, a cache, etc., or may be a memory unit of the chip (e.g., a read-only memory, a random access memory, etc.).

It should be understood that, the second aspect to the sixth aspect of the present application correspond to the technical solutions of the first aspect of the present application, and the advantages obtained by each aspect and the corresponding possible embodiments are similar, and are not repeated.

Drawings

Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

fig. 2 is a software structural block diagram of an electronic device according to an embodiment of the present application;

FIG. 3 is an interface interaction schematic diagram of software repair according to an embodiment of the present application;

FIG. 4 is a schematic diagram of interface interaction for repairing a software problem by message notification according to an embodiment of the present application;

FIG. 5 is a schematic diagram of an interface for checking whether a software problem needs to be repaired according to an embodiment of the present application;

FIG. 6 is a schematic diagram of an interface of user-set automatic repair software according to an embodiment of the present application;

FIG. 7 is a schematic flow chart of a software repairing method according to an embodiment of the present application;

FIG. 8 is a schematic diagram of an interface corresponding to a property whose display area is rounded in the application start process when the property value of the property is false according to an embodiment of the present application;

FIG. 9 is a flowchart of another software repairing method according to an embodiment of the present application;

Fig. 10 is a schematic flow chart of the whole process from detection of a patch package to completion of startup according to an embodiment of the present application;

fig. 11 is a schematic hardware structure of a control device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a chip according to an embodiment of the present application.

Detailed Description

In order to facilitate the clear description of the technical solutions of the embodiments of the present application, the following simply describes some terms and techniques involved in the embodiments of the present application:

1. And (3) mounting: refers to hooking the storage device onto an existing directory such that the electronic device can access the storage device by accessing the directory.

2. Loading: the read-only attribute stored in the partition is read into the memory.

3. Read-only properties: which may also be referred to as ro attribute, means an attribute that can only be read and cannot be modified after the setting is completed.

4. Patch mirroring: including an image file of a patch for repairing the software.

5. Over the air (over the air technology, OTA) technology: is a technology for remotely upgrading firmware or software through an air interface of mobile communication, and can be used for upgrading the software of electronic equipment. For example, the server may push an OTA upgrade package to the electronic device over the air interface, and the electronic device may implement online upgrade of software in the electronic device based on the OTA upgrade package.

6. Other terms

In embodiments of the present application, the words "first," "second," and the like are used to distinguish between identical or similar items that have substantially the same function and effect. For example, the first chip and the second chip are merely for distinguishing different chips, and the order of the different chips is not limited. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ.

It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

8. Electronic equipment

The electronic device of the embodiment of the application can comprise a handheld device, a vehicle-mounted device and the like with an image processing function. For example, some electronic devices are: a mobile phone, a tablet, a palmtop, a notebook, a mobile internet device (mobile INTERNET DEVICE, MID), a wearable device, a Virtual Reality (VR) device, an augmented reality (augmented reality, AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in unmanned (SELF DRIVING), a wireless terminal in teleoperation (remote medical surgery), a wireless terminal in smart grid (SMART GRID), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (SMART CITY), a wireless terminal in smart home (smart home), a cellular phone, a cordless phone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal DIGITAL ASSISTANT, PDA), a handheld device with wireless communication functionality, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network, or a future evolved land mobile network (public land mobile network), and the like, without limiting the application.

By way of example, and not limitation, in embodiments of the application, the electronic device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In addition, in the embodiment of the application, the electronic equipment can also be terminal equipment in an internet of things (internet of things, ioT) system, and the IoT is an important component of the development of future information technology, and the main technical characteristics of the IoT are that the article is connected with a network through a communication technology, so that the man-machine interconnection and the intelligent network of the internet of things are realized.

The electronic device in the embodiment of the application may also be referred to as: a terminal device, a User Equipment (UE), a Mobile Station (MS), a Mobile Terminal (MT), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, a user equipment, or the like.

In an embodiment of the present application, the electronic device or each network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (central processing unit, CPU), a memory management unit (memory management unit, MMU), and a memory (also referred to as a main memory). The operating system may be any one or more computer operating systems that implement business processes through processes (processes), such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer comprises applications such as a browser, an address book, word processing software, instant messaging software and the like.

The electronic device can set attributes for system settings, processes and the like during running, and the attributes can be used for recording information exchange between the system settings or the processes. By way of example, an attribute may be in a string format, an attribute may have a name and an attribute value, and an attribute may be globally visible in a software system.

In order to facilitate unified management of the attributes, the electronic device may set an attribute system through which the attributes are managed. For example, during the compilation of software, the attribute system may store the attributes of the compilation process into a build.

In some versions of the application, there may be a problem with the application caused by unreasonable attribute value setting, for example, in the version of the application, there may be a problem with the application running caused by unreasonable read-only attribute setting, and after the application is released, the application may need to be repaired by modifying the read-only attribute of the software. Or for example, a property in the version of the application may be problematic, and the property may be on in the version of the application, and the property may need to be modified to control the property to be off.

In some implementations, to repair the property, the electronic device may download an upgrade package of a new software version, replace the upgrade package of an old software version with the upgrade package of the new software version, and implement modifications to the read-only property or other properties. The read-only attribute or other attributes in the upgrade package of the new software version are configured in the product/odm of the new software version, and after the electronic device downloads the upgrade package of the new software version, the electronic device can be powered off and restarted, and all the attributes in the upgrade package of the new software version can be loaded in the process of starting the electronic device. For example, the electronic device may load the attributes in the product/odm, vendor/default. Prog, vendor/build. Prog, vendor_ dlkm/etc/build. Prog, system/build. Prog, etc. attribute files, thereby implementing modification of the read-only attribute of the software.

However, the upgrade package of the new software version contains a large amount of data of the software, so that a great amount of time is required for downloading the upgrade package and installing the new software version by the electronic device, and the user cannot use the electronic device in the process of starting up and installing the new software version by the electronic device, thereby affecting the user experience.

In other implementations, the electronic device may modify the properties of the software through a parameter upgrade function. For example, when the electronic device is started and restarted, the attributes in the attribute files such as the vendor/default. Prog, vendor/build. Prog, vendor_ dlkm/etc/build. Prog, system/build. Prog and the like are loaded based on the loading sequence of the attribute files defined by the system, and then the attributes corresponding to the parameter upgrading function are loaded based on the loading sequence. Because the loading of the read-only attribute in the attribute file is already realized in the attribute loading process based on the attribute loading sequence defined by the system, when the loading of the attribute corresponding to the parameter upgrading function is executed later, the modification of the read-only attribute cannot be realized.

In other implementations, when the electronic device is booted, an overlay technique may be used to load the attributes in the cold patch file. However, the process of loading the attributes in the attribute files such as the vendor/default, vendor/build, vendor_ dlkm/etc/build, system/build, etc. by the electronic device is earlier than the process of loading the attributes in the cold patch file. For example, the electronic device loads the attributes in the attribute files such as vendor/default, vendor/build, vendor_ dlkm/etc/build, system/build, etc. 2s after the electronic device is started, and loads the attributes in the cold patch file by using the overlay technology 6 seconds after the electronic device is started. Because the loading of the read-only attribute in the attribute file is realized in the attribute loading based on the attribute file, and the modification of the read-only attribute cannot be realized when the attribute loading based on the cold patch file is executed later, the method for loading the software attribute in the cold patch file by using the overlay technology cannot modify the read-only attribute of the software.

In view of this, the embodiment of the application provides a software repairing method, when an electronic device detects that a boot is started, a read-only attribute to be modified is loaded first, so that the read-only attribute to be modified is modified first, and then the electronic device reloads the attribute in an application program version.

In order to better understand the embodiments of the present application, the following describes the structure of the electronic device according to the embodiments of the present application:

Fig. 1 shows a schematic configuration of an electronic device 100. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identity module (subscriberidentification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It should be understood that the illustrated structure of the embodiment of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the application, electronic device 100 may include more or fewer components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processingunit, GPU), an image signal processor (IMAGE SIGNAL processor, ISP), a controller, a video codec, a digital signal processor (DIGITAL SIGNAL processor, DSP), a baseband processor, and/or a neural-Network Processor (NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to reuse the instruction or data, it may be called from memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby improving the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an integrated circuit (inter-INTEGRATED CIRCUIT, I2C) interface, an integrated circuit built-in audio (inter-INTEGRATED CIRCUITSOUND, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purposeinput/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.

The wireless communication function of the electronic device 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The electronic device 100 implements display functions through a GPU, a display screen 194, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, and the like. The display 194 includes a display panel. The display panel may employ a Liquid Crystal Display (LCD) screen (liquid CRYSTAL DISPLAY), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-34 diode, a flexible light-emitting diode (FLED), miniled, microLed, micro-oLed, a quantum dot light-emitting diode (quantum dot lightemitting diodes, QLED), or the like. In some embodiments, the electronic device 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The pressure sensor 180A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A may be disposed on the display screen 194. The pressure sensor 180A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. The capacitance between the electrodes changes when a force is applied to the pressure sensor 180A. The electronic device 100 determines the strength of the pressure from the change in capacitance. When a touch operation is applied to the display screen 194, the electronic apparatus 100 detects the touch operation intensity according to the pressure sensor 180A. The electronic device 100 may also calculate the location of the touch based on the detection signal of the pressure sensor 180A.

The gyro sensor 180B may be used to determine a motion gesture of the electronic device 100. In some embodiments, the angular velocity of electronic device 100 about three axes (i.e., x, y, and z axes) may be determined by gyro sensor 180B. The gyro sensor 180B may be used for photographing anti-shake. For example, when the shutter is pressed, the gyro sensor 180B detects the shake angle of the electronic device 100, calculates the distance to be compensated by the lens module according to the angle, and makes the lens counteract the shake of the electronic device 100 through the reverse motion, so as to realize anti-shake. The gyro sensor 180B may also be used for navigating, somatosensory game scenes.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically three axes). The magnitude and direction of gravity may be detected when the electronic device 100 is stationary. The method can also be used for identifying the gesture of the electronic equipment, and is applied to application programs such as horizontal and vertical screen switching, pedometers and the like.

The touch sensor 180K, also referred to as a "touch device". The touch sensor 180K may be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, which is also called a "touch screen". The touch sensor 180K is for detecting a touch operation acting thereon or thereabout. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 194. In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device 100 at a different location than the display 194.

The software system of the electronic device 100 may employ a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture, among others. In the embodiment of the application, taking an Android system with a layered architecture as an example, a software structure of the electronic device 100 is illustrated.

Fig. 2 is a block diagram of a software architecture of the electronic device 100 according to an embodiment of the present application.

The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun rows (Android runtime) and system libraries, and a kernel layer, respectively.

The application layer may include a series of application packages.

As shown in FIG. 2, the application package may include applications for cameras, system user interfaces (systemUI), phones, maps, phones, music, settings, desktops (desktop), video, social, and the like.

The application framework layer provides an application programming interface (application programming interface, API) and programming framework for the application of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 2, the application framework layers may include a Window Manager (WMS), a content provider, a resource manager, a view system (view), a notification manager, and the like.

The window manager is used for managing window programs. The window manager may obtain the display screen size, determine if there is a status bar, lock the screen, touch the screen, drag the screen, intercept the screen, etc.

The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc.

The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.

The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.

The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the electronic device vibrates, and an indicator light blinks, etc.

Android runtime include core libraries and virtual machines. Android runtime is responsible for scheduling and management of the android system.

The core library consists of two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), etc.

The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver. In the embodiment of the application, the kernel layer is used for executing the mounting of the first partition, loading the attribute of the first partition, and loading the attribute of the second partition after the loading of the first partition is completed.

In order to more clearly describe the software repairing method provided by the embodiment of the application, the application scene of the embodiment of the application is described.

After the software of the electronic equipment is released, a technician can test the service condition of the software or collect the use experience of a user in an investigation mode to find that the software has the problem of needing to be repaired. For example, the problem that when the front portrait photographing defaults to close the beauty is found in a certain type of equipment by software, the photographed photos turn red is found.

When the problem existing in the software can be repaired by modifying the corresponding read-only attribute, a technician can configure the read-only attribute to be modified on the device according to the problem existing in the software, and the device can manufacture the read-only attribute to be modified into an OTA package according to the configuration requirement of the technician and upload the OTA package to the server.

For example, the technician's configuration requirements may include instructions for instructing that the read-only properties to be modified be made into an OTA package, the model of the electronic device or software version for which the OTA package is intended. The step of making the read-only attribute to be modified into an OTA packet may include: and writing the read-only attribute to be modified into an attribute file according to an instruction for indicating the read-only attribute to be modified into an OTA packet, manufacturing the attribute file containing the read-only attribute to be modified into a patch mirror image, and further manufacturing the OTA packet according to the patch mirror image. The manufactured OTA packet may further include an electronic device model or a software version for which the OTA packet is intended.

It can be understood that the model number or the software version of the electronic device targeted by the OTA packet corresponds to the electronic device that needs to be repaired by software.

After receiving the OTA packet, the server can push the OTA packet to the corresponding electronic device according to the model or software version of the electronic device.

For example, a technician finds that problem 1 exists in software with a software version of 1.0 that needs to be repaired, and problem 1 can be repaired by modifying read-only property 1. The technician can reconfigure the read-only attribute 1, make an OTA packet according to the configured read-only attribute 1 by using the device, and upload the OTA packet to the server, where the OTA packet may include the aimed software version 1.0. And the server pushes the OTA packet to the electronic equipment with the version of the used software of 1.0 according to the software version aimed at by the OTA packet.

When the electronic device receives the OTA packet pushed by the server, the following several possible interface interaction manners may exist. The possible interface interactions for software repair according to embodiments of the present application will be described in detail below in conjunction with a user interface.

Thus, the server can accurately push according to the software version aimed by the OTA package or the model of the electronic equipment.

Fig. 3 is an interface interaction schematic diagram of software repair according to an embodiment of the present application.

One possible implementation, when the electronic device detects an OTA packet pushed by the server for repairing a software problem, the electronic device may display an interface as shown in a in fig. 3, where the interface includes a prompt box 301. The prompt box 301 includes prompt information for prompting that "there is a software problem that needs to be repaired, repair the software problem that needs to download and install an update package," control that will be described later, "and" download and install "control.

The prompt box 301 may be displayed through a floating window, or may be displayed in a split screen or card form, and the size of the prompt box 301 may be smaller than or equal to the screen size of the electronic device. The specific display form and interface size of the prompt box 301 are not limited in this embodiment of the present application.

The prompt box 301 may be displayed below the screen of the electronic device, or may be displayed above or beside the screen of the electronic device, and the display form and the display position of the prompt box 301 are not limited herein.

In the interface shown in a in fig. 3, when the user wants to repair the software, the user may click on the "download and install" control, and then the electronic device receives a click operation for the "download and install" control, and in response to the click operation, the electronic device may download an update package, which may be an OTA package, from the server. The OTA package is installed after the downloading is completed, and an interface shown as b in fig. 3 may be displayed after the installation of the OTA package is completed.

For example, the electronic device may download the OTA packet to the user data area, and install the OTA packet after the downloading is completed, and the process of installing the OTA packet may include: and writing the image file in the OTA packet into a partition which is created in advance and used for storing the patch image.

The interface shown as b in fig. 3 includes a confirmation box 302, the confirmation box 302 including prompt information for prompting "whether to restart the device to complete the software fix," an "immediate restart" control, and a "cancel" control.

The confirmation box 302 may be displayed through a floating window, or may be displayed in the form of a split screen or card, and the size of the confirmation box 302 may be less than or equal to the screen size of the electronic device. The particular display form and interface size of the confirmation box 302 is not limited in this regard.

The confirmation frame 302 may be displayed below the screen of the electronic device, or may be displayed above or beside the screen of the electronic device, and the display form and the display position of the confirmation frame 302 are specifically not limited herein.

In the interface shown in b in fig. 3, when the user agrees to restart the device to fix the software problem, the user may click on the "immediately restart" control in the confirmation box 302, and the electronic device receives a click operation for the "immediately restart" control, and executes a shutdown and restart procedure in response to the click operation. In the starting-up process of the electronic device, an interface shown in c in fig. 3 may be displayed, where the interface includes a system identifier and a prompt message for prompting the device to "start up", and the system identifier may be a text, an image, etc., which is not limited in the embodiment of the present application.

The electronic device may execute the software repairing method provided by the embodiment of the present application when the electronic device displays the interface shown in c in fig. 3. The specific implementation process will be described in detail in the following embodiments, which will not be described in detail herein. After the electronic device is started, an interface shown as d in fig. 3 may be displayed. The interface shown in fig. 3 d includes a repair result prompt box 303, where the repair result prompt box 303 is used to prompt completion of the software repair and content of the software repair.

The repair result prompt box 303 can be displayed through a floating window, and also can be displayed through a split screen or a card, and the size of the repair result prompt box 303 can be smaller than or equal to the screen size of the electronic device. The specific display form and interface size of the repair result prompt box 303 are not limited in this embodiment of the present application.

The repair result prompt box 303 may be displayed below the screen of the electronic device, or may be displayed above or beside the screen of the electronic device, and specifically, the display form and the display position of the repair result prompt box 302 are not limited herein.

In another possible implementation, the electronic device may receive the software repair message when the electronic device detects an OTA packet pushed by the server to repair the software problem. Fig. 4 is an interface interaction schematic diagram of repairing a software problem through message notification according to an embodiment of the present application.

When the electronic device receives the software repair message, an interface as shown by a in fig. 4 may be displayed. In the interface shown as a in fig. 4, the electronic device may display the interface shown as b in fig. 4 if a trigger operation (e.g., a pull-down notification or a click notification) for opening the software repair message is received.

The interface shown in b in fig. 4 may include a prompt 401 for a software repair message, a prompt for message 1, and a prompt for message 2. The prompt box 401 of the software repair message includes prompt information for prompting that "there is a software problem that needs to be repaired, repair the software problem that needs to download and install an update package," ignore "control, and" download and install "control.

For example, when the user wants to repair the software, the user may click on the "download and install" control in the prompt box 401 of the software repair message, and then the electronic device receives a click operation for the "download and install" control, and in response to the click operation, the electronic device may download an update package from the server, where the update package may be an OTA package. The OTA package is installed after the downloading is completed, and an interface shown as c in fig. 4 may be displayed after the installation of the OTA package is completed. The interface includes a restart device prompt 402, a prompt for message 1, and a prompt for message 2. The restart device prompt box 402 includes prompt information for prompting "install complete, whether the restart device completes software repair", a control for "immediately restart", and a control for "cancel".

In the interface shown as b in fig. 4, if the software repair message is not triggered for a period of time, or a trigger to close the software repair message is received (e.g., the user clicks the "ignore" control), the prompt box 401 of the software repair message may cancel the display and the electronic device continues to display the desktop.

In the interface shown in c in fig. 4, when the user agrees to restart the device to fix the software problem, the user may click on the "immediately restart" control in the restart device prompt box 402, and the electronic device receives a click operation for the "immediately restart" control, and executes a shutdown and restart process in response to the click operation. The interface displayed in the startup process of the electronic device may be the interface shown in c in fig. 3.

In the interface shown as c in fig. 4, if the user clicks the "cancel" control, restarting the device prompt 402 may cancel the display and the electronic device continues to display the desktop.

In another possible implementation, the user may actively see if there is a software problem to repair. Situations that require the user to actively see if there are software problems to repair may include any of the following: when the electronic device detects the OTA packet pushed by the server and used for repairing the software problem, the electronic device does not display a prompt box 301 in the interface shown as a in fig. 3, the electronic device does not display a software repair message in the interface shown as a in fig. 4, the user clicks a control "later" in the prompt box 301, and a control "neglect" in a prompt box 401 of the software repair message in the interface shown as b in fig. 4.

FIG. 5 is a schematic diagram of an interface for checking whether a software problem needs to be repaired according to an embodiment of the present application.

The user can trigger in the setting application in sequence according to the sequence of "setting-system and updating-software updating", when the electronic device receives the operation for the software updating in the setting application, the software version upgrade package and the OTA package for repairing the software problem can be detected, and when the software version is detected to be the latest version, but the software problem needs to be repaired, the interface as shown in the figure 5a can be displayed. The interface includes a system identification, a system version, a prompt for prompting that the software version is the latest version, a prompt for prompting that a software problem exists and needs to be repaired, and a control for checking for update.

In the interface shown in fig. 5a, when the user clicks the area where the prompt message "the software problem needs to be repaired" is located, the electronic device receives a clicking operation for the area where the prompt message "the software problem needs to be repaired" is located, and displays the interface shown in fig. 5 b in response to the clicking operation. The interface includes a content description of the update package and a "download and install" control that is needed to fix the software problem.

In the interface shown in fig. 5 b, when the user wants to repair the software, the user may click on the "download and install" control, and then the electronic device receives a click operation on the "download and install" control, and in response to the click operation, the electronic device may download an update package from the server, where the update package may be an OTA package, and after the downloading is completed, the OTA package may be installed. The interface shown as c in fig. 5 may be displayed after the installation of the OTA packet is completed. The interface comprises prompt information for prompting that installation is finished, whether restarting the device is finished with software repair, a control for immediately restarting the device and a control for canceling the device.

In the interface shown in c in fig. 5, when the user agrees to restart the device to fix the software problem, the "immediate restart" control may be clicked, and then the electronic device receives a clicking operation for the "immediate restart" control, and executes a shutdown and restart procedure in response to the clicking operation. In the process of starting up the electronic device, the interface shown in c in fig. 3 may be displayed.

The interface interactions shown in fig. 3-5 all require the user to manually select to download and install the OTA package, and manually select whether to restart the device to complete the software repair. In one possible implementation, a user may automatically execute a software repair procedure when the user checks that a software problem exists on the electronic device and needs to be repaired.

FIG. 6 shows a schematic interface diagram of a user setting automatic repair software.

For example, the user may set the auto repair software in a software update of the interface setting application as shown in fig. 5 a. When the electronic device displays an interface as shown in a of fig. 5, the user can click on the control 601, and the electronic device receives a click operation of the control 601 by the user, and in response to the operation, displays an interface as shown in a of fig. 6.

In the interface shown as a in fig. 6, the user may click on the control of "native setting", and the electronic device receives an operation for the control of "native setting", and in response to the operation, displays the interface shown as b in fig. 6.

The interface shown in b in fig. 6 includes a switch control corresponding to a function automatically downloaded under WLAN, a switch control corresponding to a function of installing an upgrade package at night, a switch control corresponding to a function of repairing a software problem at night, and a switch control corresponding to a cooperatively updated function. In the interface shown in b in fig. 6, the function of installing the upgrade package at night and the function of collaborative updating are both in an on state, and the function of automatically downloading the WLAN and the function of repairing the software problem at night are in an off state.

In the interface shown in b in fig. 6, when the user can click on the switch control corresponding to the function of the night repair software problem, the electronic device receives a click operation of the switch control corresponding to the function of the night repair software problem, and in response to the operation, controls the function of the night repair software problem to be in an on state, and displays the interface shown in c in fig. 6. In the interface, the switch control corresponding to the function of repairing the software problem at night is changed to be in the same state as the switch control corresponding to other functions.

Therefore, when the function of repairing the software problem at night is in an on state, the electronic equipment can automatically download and restart the update package for repairing the software problem at night (for example, 02:00-04:00) and when the electronic equipment is in an idle state, so that an optional software repairing mode is provided for a user, the operation flow of the user during software repairing is simplified, and the user experience is improved.

In a possible implementation, when the function of automatic downloading in WLAN in the interface shown in c in fig. 6 is in a closed state and the electronic device detects the OTA packet pushed by the server and used for repairing the software problem, the OTA packet is not automatically downloaded, and the electronic device may display the interface shown in fig. 3 or fig. 4. When the function of automatic downloading under the WLAN is in an on state, the electronic device may automatically download the OTA packet under the WLAN, and the interface displayed by the electronic device is an interface in which the "download and install" control in the interfaces shown in fig. 3, 4 and 5 is replaced by the "download" control, and the "download and install" in the prompt information is replaced by the "install" interface.

The following will schematically describe a flow embodiment of a software repair method provided by an embodiment of the present application. It should be noted that "at … …" in the embodiment of the present application may be an instant when a certain situation occurs, or may be a period of time after a certain situation occurs, which is not particularly limited in the embodiment of the present application. Fig. 7 is a schematic flow chart of a software repairing method according to an embodiment of the present application. As shown in fig. 7, the method includes:

s701: and when the electronic equipment detects the starting-up start, starting the first partition mounting.

The first partition is a storage space pre-created in the electronic device for storing the patch image. The names of the first partition and the patch image may be the same or different, which is not limited in the embodiment of the present application. For example, if the patch image used by the software repair is a patch image, the first partition may be a patch partition.

In one possible implementation, the electronic device power-on may be based on a received operation for device restart, e.g., the operation for device restart may include any of the following: in the interface shown as b in fig. 3, the user clicks the "immediately restart" control in the confirm box 302; in the interface shown in c of FIG. 4, the user clicks the "immediately restarted" control in the restart device prompt box 402; the user clicks the "immediately restart" control in the interface shown as c in fig. 5. The foregoing embodiments may be referred to specifically, and the embodiments of the present application are not repeated.

In another possible implementation, the electronic device may be automatically powered on when the night repair software problem is in an on state. For example, in the on state of the night repair software problem, the electronic device may automatically install the update package for repairing the software problem that has been downloaded and restart the device at night when the electronic device is in the idle state.

The electronic device reads the patch image stored in the first partition, and the first partition can be mounted to the first directory, and the patch image stored in the first partition is read through the first directory. The first directory is a directory which is created in advance and used for mounting the partition corresponding to the patch image.

S702: the electronic device loads the attributes of the first partition.

Wherein the first partition stores a patch image with read-only properties. The read-only attribute in the patch image may be a read-only attribute corresponding to the problem to be repaired by the software, and the read-only attribute may be stored in an attribute file of the patch image. The number of the read-only attributes stored in the patch image can be 1 or more, and the embodiment of the application does not limit the number of the read-only attributes in the patch image.

For example, the electronic device may obtain the read-only attribute in the attribute file of the patch image, and load the read-only attribute into the memory of the electronic device.

S703: after loading of the first partition is completed, the electronic device loads the attribute of a second partition, which is different from the first partition.

In the second partition of the embodiment of the present application, a plurality of attribute files may be stored, for example, attribute files such as system/build.prog, vendor/default.prog, vendor/build.prog, vendor_ dlkm/etc/build.prog, where an attribute in any attribute file may include a read-only attribute or a non-read-only attribute.

For example, the electronic device may load the attributes of the second partition into the memory.

In one possible implementation, there may be read-only attributes in the second partition that are the same name as the attributes in the first partition but have different attribute values. When the electronic device loads the attribute of the first partition, the attribute value corresponding to the first partition is loaded into the memory, so that the electronic device loads the read-only attribute in the second partition, which can be regarded as invalid loading, and the attribute value of the read-only attribute in the memory cannot be modified into the attribute value corresponding to the second partition.

It will be appreciated that after the electronic device completes loading the second partition, an interface may be displayed as shown by d in fig. 3.

Based on this, in the embodiment of the present application, when the electronic device detects that the boot is started, the attribute of the first partition is loaded first, because the first partition stores the patch image of the read-only attribute, the read-only attribute can be modified when the first partition is loaded, and after the first partition is loaded, the electronic device reloads the attribute of the second partition, so that even if the read-only attribute same as the first partition exists in the second partition, because the values of the read-only attribute are modified when the first partition is loaded, the read-only attribute of the second partition cannot be revalidated, so that the loaded read-only attribute cannot be influenced when the attribute of the second partition is loaded, the modification of the read-only attribute of software by the patch image loaded with the read-only attribute is realized, the electronic device does not need to reload the complete software package, the time spent in software repair is reduced, and the user experience is improved.

The software repairing method provided by the embodiment of the application can be suitable for repairing various software problems, and the software repairing process corresponding to different software problems is described in detail below by taking the first partition as a patch partition as an example.

In one possible implementation, the software problem with the electronic device may be that the display area is not rounded during application launch. The read-only attribute msc.app_laboratory_interaction_right_angle is an attribute that a display area is a round corner in the process of starting an application, when an attribute value of the attribute is false, the display area is a round corner in the process of starting the application, and when the attribute value is true, the display area is not a right angle in the process of starting the application.

Fig. 8 shows a schematic interface corresponding to the attribute with rounded display area when the attribute value is false during application start.

In the interface shown as a in fig. 8, when the user can click on the memo icon displayed on the desktop, the electronic device receives a click operation on the memo icon, and in response to the click operation, a starting animation of the memo is displayed, wherein the starting animation can be composed of multiple memo thumbnails, any two thumbnails are different in size, the starting animation is formed by sequentially and rapidly displaying the two thumbnails in order from small to large on the interface of the electronic device, and an area 801 in the interface shown as b in fig. 8 is one thumbnail in the starting animation.

Since the read-only attribute msc.app_laboratory_interaction_right_angle attribute value is false, four corners corresponding to the thumbnails of the memo are rounded in the interface shown in b in fig. 8. After displaying the interface shown in b in fig. 8, the animation is started to continue displaying until the interface shown in c in fig. 8 is displayed. In the interface shown in c in fig. 8, the memo interface fills the screen of the electronic device.

For example, when the read-only attribute msc.app_laboratory_interaction_right_angle attribute value is true, four corners corresponding to the region 801 in the interface shown in b in fig. 8 may be right angles (not shown in the figure). As shown in any interface of fig. 8, four corners of the screen of the electronic device are rounded, and when the memo interface reaches the screen of the full electronic device, the situation that the four corners of the memo interface cannot be matched with the four corners of the screen of the electronic device may occur.

The software repairing method provided by the embodiment of the application can be used for modifying the attribute of the display region fillet in the application starting process. Referring to fig. 9, fig. 9 is a schematic flow chart of another software repairing method according to an embodiment of the application.

As shown in fig. 9, the software repair method may include:

S901: the electronic device downloads and installs the OTA package.

The OTA packet may include a patch image, where configured read-only attributes are stored: msc.app_laboratory_animation_right_angle=false.

The interface interaction process corresponding to the downloading and installing of the OTA packet by the electronic device can be described by referring to the above embodiment, and the embodiment of the present application is not repeated.

The electronic device can download the OTA packet to the user data area, and after the downloading is completed, the image file in the OTA packet can be written into the pre-created partition for storing the patch image, and the following steps are continuously executed:

S902: the electronic device is powered off and restarted.

For example, the electronic device may be turned off and restarted according to the received operation for restarting the device, or the electronic device may be automatically turned on when the night repair software problem is turned on. The operation for restarting the device and the description of the night repair software problem being in the on state can be referred to the content described in the above embodiment, and the embodiments of the present application are not repeated.

S903: the electronic equipment detects the starting-up start-up, and the patch partition is mounted under a specific pre-created directory.

For example, a patch image stored by a patch partition may include a property file patch. Prop in which a read-only property, false msc. Latch. App_latch_isolation_right_angle=false, is stored.

When the electronic equipment detects the starting-up, the mounting of the patch partition under a pre-established specific directory can be determined through a pre-configured file system table. The preconfigured file system table may include the partition to be mounted, the mounting position of the partition, the mounting sequence of the partition, and the like.

The electronic device may mount other partitions under the directory corresponding to the electronic device through a preconfigured file system table, where the mounting of the other partitions is not limited in the embodiment of the present application, and the other partitions are partitions in the electronic device except the patch partition.

S904: and the electronic equipment loads the attribute with the display area being a round angle in the application starting process into the memory through the pre-created specific catalogue.

The electronic device obtains an attribute file patch, prop, in the patch image through a pre-created specific directory, and loads the msc, app_latch_operation_right_angle=false in the patch image into a memory of the electronic device, so that a read-only attribute msc, app_latch_operation_right_angle attribute value is false, that is, a state corresponding to an attribute with a rounded display area in an application starting process is an on state.

S905: after the loading of the patch partition is completed, the electronic equipment loads the attributes of other partitions.

For example, after completing the loading of the patch partition, the electronic device may load the attributes in the attribute file of the other partition, e.g., the electronic device may load the attributes in the following attribute files: system/build.pro, vendor/default.pro, vendor/build.pro, vendor_ dlkm/etc/build.pro.

Among the attributes of other partitions may be attributes where the display area is rounded during application launch, e.g., the presence of msc. Since the attribute value of the read-only attribute msc.counter.app_laboratory_operation_right_angle is already set to false in the application start process, the attribute value true in the attribute of other partitions cannot be validated, and the attribute value of the read-only attribute msc.counter.app_laboratory_operation_right_angle is still false.

Therefore, after the read-only attribute in the patch. Prop is loaded, the attribute in the reloaded other attribute files cannot influence the read-only attribute in the patch. Prop, and the read-only attribute is modified. Because the OTA packet with the read-only attribute is smaller, the time spent for downloading and installing the OTA packet and restarting the device is less, and the experience is improved.

In a possible implementation, the software repairing method provided by the embodiment of the application can repair the problem that the shot photo is reddish when the default shooting of the front portrait closes the beauty, the corresponding attribute of the problem is the coding rendering parameter attribute of the video playing and the camera, and the attribute is the read-only attribute ro.vendor.mtk_pq_color_mode in the file vendor/build.prop. The problem can be repaired by modifying the attribute value corresponding to the read-only attribute ro.vendor.mtk_pq_color_mode from 3 to 1.

For example, the electronic device may download and install an OTA packet for modifying the read-only attribute ro.vendor.mtk_pq_color_mode. After the installation is completed, the electronic device is restarted to modify the attribute value of the ro.vendor.mtk_pq_color_mode. The OTA packet may include a patch image, where the patch image may include ro.vendor.mtk_pq_color_mode=1.

When the electronic equipment detects that the electronic equipment is started, other partitions except the patch partition can be mounted under the corresponding directory, and the patch partition containing the read-only attribute ro.vendor.mtk_pq_color_mode is mounted under the specific directory which is created in advance. After the mounting is completed, the ro.vendor.mtk_pq_color_mode=1 can be obtained through a pre-created specific directory, and is loaded into the memory of the electronic device.

When the electronic device is loaded with ro.vendor.mtk_pq_color_mode=1, the attributes in other partitions may be loaded, and the description of the above embodiments may be referred to for loading the attributes in other partitions, which is not repeated in the embodiments of the present application.

Therefore, the electronic equipment can use the OTA package containing the patch image to modify the attribute value of the read-only attribute ro.vendor.mtk_pq_color_mode, and the problem that the shot photo is reddish when the front portrait shooting default closing beauty is repaired is realized.

In one possible implementation, the user account may view the high-definition video using the old video software version when the old video software version is the high-definition member account, but may not view the high-definition video under the new video software version after upgrading the old video software version to the new video software version. The software repairing method provided by the embodiment of the application can repair the problem that the high-definition video cannot be watched by the updated new video software version.

The inability of the new software version to view the high-definition video may be caused by an error in the attribute value of the high-definition membership authentication information attribute ro. The high-definition member authentication information attribute ro.netflix.bsp_rev is a read-only attribute.

By using the software repairing method described in the above embodiment, the attribute value of the high-definition member authentication information attribute ro.netflix.bsp_rev can be modified to repair the problem that the high-definition video cannot be watched by the new software version.

In summary, according to the software repairing method provided by the embodiment of the application, the software can be repaired in a manner of repairing the read-only property, and the time required by the repairing process is shorter, so that the user experience is improved.

In combination with the software problem repairing methods corresponding to the three software problems, fig. 10 shows a flow chart of the whole process from the detection of the patch package to the completion of the startup.

The whole process from checking the patch package to the completion of the power-on process can comprise the following steps:

s1001, detecting whether an update patch package exists in an application program.

The detection of whether an update exists may be performed in real time, or may be performed after the user clicks a control "check update" in an interface shown in a in fig. 5, or may be performed automatically, which is not limited by the embodiment of the present application. Detecting whether an update exists includes detecting whether a software version exists that requires an update and whether a patch package exists for repairing a software problem.

S1002, detecting a patch package.

The patch package may be, for example, an OTA package storing a patch image of the read-only property to be repaired.

S1003, downloading a patch package: the patch package is stored in the user data area.

S1004, installing a patch package: the patch image of the patch package is written to the patch partition.

S1005, the patch package is successfully installed, and a user is reminded of restarting the device.

For example, the interface for reminding the user to restart the device may refer to the interface shown in b in fig. 3, the interface shown in c in fig. 4, or the interface shown in c in fig. 5, which is not described in detail in the embodiments of the present application.

S1006, restarting the device.

S1007, mounting other partitions.

Other partitions are other than the patch partition and may include system, vendor or the like.

S1008, mounting the patch partition.

S1009, loading the read-only attribute to be repaired in the attribute file of the patch partition to the memory.

S1010, loading attributes in attribute files of other partitions into a memory.

S1011, finishing starting, and reading the loaded attribute in the memory by the application layer.

Based on the method, the patch mirror image of the read-only attribute to be repaired is stored in the patch package, and the attributes of other partitions are loaded after the read-only attribute to be repaired in the patch partition is loaded, so that the attributes of the other partitions cannot influence the read-only attribute to be repaired, and the read-only attribute is modified. And the patch package is smaller, so that the time spent on downloading and installing the patch package and restarting the equipment is reduced, and the user experience is improved.

In order to implement the above functions, the device for implementing software repair includes a hardware structure and/or a software module for implementing each function. Those of skill in the art will readily appreciate that the present application may be implemented in hardware or a combination of hardware and computer software, as the method steps of the examples described in connection with the embodiments disclosed herein. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

According to the embodiment of the application, the device for realizing the software repairing method can be divided into the functional modules according to the method example, for example, each functional module can be divided corresponding to each function, and two or more functions can be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.

Fig. 11 is a schematic hardware structure of a control device according to an embodiment of the present application, as shown in fig. 11, where the control device includes a processor 1101, a communication line 1104, and at least one communication interface (illustrated in fig. 11 by taking a communication interface 1103 as an example).

The processor 1101 may be a general purpose central processing unit (central processing unit, CPU), microprocessor, application Specific Integrated Circuit (ASIC), or one or more integrated circuits for controlling the execution of the programs of the present application.

Communication line 1104 may include circuitry for communicating information between the components described above.

Communication interface 1103 uses any transceiver-like device for communicating with other devices or communication networks, such as ethernet, wireless local area network (wireless local area networks, WLAN), etc.

Possibly, the control device may also comprise a memory 1102.

The memory 1102 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (ELECTRICALLY ERASABLE PROGRAMMABLE READ-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory) or other optical disk storage, a compact disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be separate and coupled to the processor via communication line 1104. The memory may also be integrated with the processor.

The memory 1102 is used for storing computer-executable instructions for implementing the aspects of the present application, and is controlled by the processor 1101 for execution. The processor 1101 is configured to execute computer-executable instructions stored in the memory 1102, thereby implementing the garbage collection method provided by the embodiment of the present application.

Possibly, the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not limited in particular.

In a particular implementation, the processor 1101 may include one or more CPUs, such as CPU0 and CPU1 of FIG. 11, as an embodiment.

In a specific implementation, as an embodiment, the control device may include a plurality of processors, such as processor 1101 and processor 1105 in fig. 11. Each of these processors may be a single-core (single-CPU) processor or may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

Fig. 12 is a schematic structural diagram of a chip according to an embodiment of the present application. Chip 1200 includes one or more (including two) processors 1201, communication lines 1202, communication interface 1203, and memory 1204.

In some implementations, the memory 1204 stores the following elements: executable modules or data structures, or a subset thereof, or an extended set thereof.

The method described in the above embodiments of the present application may be applied to the processor 1201 or implemented by the processor 1201. The processor 1201 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in the processor 1201 or by instructions in the form of software. The processor 1201 may be a general purpose processor (e.g., a microprocessor or a conventional processor), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gates, transistor logic, or discrete hardware components, and the processor 1201 may implement or perform the methods, steps, and logic diagrams related to the disclosed processes in the embodiments of the present application.

The steps of the method disclosed in connection with the embodiments of the present application may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in any well-known storage medium such as ram, rom, or EEPROM (ELECTRICALLY ERASABLE PROGRAMMABLE READ ONLY MEMORY, EEPROM). The storage medium is located in the memory 1204, and the processor 1201 reads information in the memory 1204 and performs the steps of the method described above in combination with its hardware.

The processor 1201, the memory 1204, and the communication interface 1203 may communicate with each other via the communication line 1202.

In the above embodiments, the instructions stored by the memory for execution by the processor may be implemented in the form of a computer program product. The computer program product may be written in the memory in advance, or may be downloaded in the form of software and installed in the memory.

Embodiments of the present application also provide a computer program product comprising one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL), or wireless (e.g., infrared, wireless, microwave, etc.), or semiconductor media (e.g., solid state disk (solid state STATE DISK, SSD)), the computer-readable storage medium may be any available medium that can be stored by the computer or a data storage device such as a server, data center, etc., comprising an integration of one or more available media.

The embodiment of the application also provides a computer readable storage medium. The methods described in the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. Computer readable media can include computer storage media and communication media and can include any medium that can transfer a computer program from one place to another. The storage media may be any target media that is accessible by a computer.

As one possible design, the computer-readable medium may include compact disk read-only memory (CD-ROM), RAM, ROM, EEPROM, or other optical disk storage; the computer readable medium may include disk storage or other disk storage devices. Moreover, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, includes Compact Disc (CD), laser disc, optical disc, digital versatile disc (DIGITAL VERSATILE DISC, DVD), floppy disk and blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Claims

1. A method of software repair, for use with an electronic device, the method comprising:

When the electronic equipment is detected to be started, starting a first partition mount;

Loading the attribute of the first partition, wherein a patch mirror image with read-only attribute is stored in the first partition, and the read-only attribute in the patch mirror image is the read-only attribute corresponding to the problem to be repaired of the software;

After loading of a first partition is completed, loading attributes of a second partition, wherein the second partition is different from the first partition;

the first partition is used for storing patch images of read-only attributes of the application program, and the second partition is used for storing application attributes of the application program.

2. The method of claim 1, wherein the read-only attribute comprises msc.app_laboratory_interaction_right_angle, ro.vendor.mtk_pq_color_mode, or ro.netflix.bsp_rev.

3. The method according to claim 1 or 2, wherein when a boot-up is detected, before the first partition mount is started, further comprising:

Displaying a first interface, the first interface comprising: the system comprises prompt information for prompting the application program to be the latest version and a first button, wherein the first button comprises information for prompting the application program to need to be repaired;

receiving a trigger for the first button;

responsive to a trigger to the first button, displaying a second interface; the second interface includes a second button;

receiving a trigger for the second button;

and in response to the triggering of the second button, downloading a patch package of the application program, and storing a patch image of the read-only attribute of the application program in the patch package into the first partition.

4. A method according to claim 3, characterized in that the method further comprises:

After the patch mirror image of the read-only attribute of the application program in the patch package is stored in the first partition, a third interface is displayed; the third interface includes a third button;

receiving a trigger for the third button;

And restarting the electronic device in response to the triggering of the third button.

5. The method according to claim 1 or 2, wherein when a boot-up is detected, before the first partition mount is started, further comprising:

displaying a fourth interface, the fourth interface comprising: a first switch for controlling the on or off of the function of repairing the software problem at night, and a second switch for controlling the on or off of the function of installing the upgrade package at night;

receiving an operation of setting the first switch to an on state;

and restarting the electronic equipment when the electronic equipment is determined to be in an idle state within a preset time period.

6. The method of any of claims 1-2, 4, wherein the electronic device includes a kernel layer that initiates the first partition mount when a power-on boot is detected; loading the attribute of the first partition; after loading of the first partition is completed, loading attributes of the second partition, including:

When the starting-up is detected, starting a first partition mount in the kernel layer;

loading the attribute of the first partition in the kernel layer;

And after the loading of the first partition is completed, loading the attribute of the second partition in the kernel layer.

7. An electronic device, comprising: a memory for storing a computer program and a processor for executing the computer program to perform the method of any of claims 1-6.

8. A computer readable storage medium storing instructions that, when executed, cause a computer to perform the method of any one of claims 1-6.

9. A computer program product comprising a computer program which, when run, causes an electronic device to perform the method of any of claims 1-6.