WO2021017935A1

WO2021017935A1 - Wakelock management method and electronic device

Info

Publication number: WO2021017935A1
Application number: PCT/CN2020/103128
Authority: WO
Inventors: 钱华君; 张贵文; 赵凡凡
Original assignee: 华为技术有限公司
Priority date: 2019-07-26
Filing date: 2020-07-20
Publication date: 2021-02-04
Also published as: CN110572866B; CN110572866A

Abstract

Provided are a wakelock management method and an electronic device, wherein same relate to the field of electronic devices. The problems of a system failing to sleep for a long time and of the high power consumption of a device due to abnormal lock holding of an application are solved, and the service life of the device is prolonged. The method comprises: a process creating a wakelock, wherein the process comprises a target process, and the target process comprises one or more of the following processes: a process of creating a wakelock by using a file node writing mode, and a process of creating a wakelock by using a mode of calling an interface corresponding to a kernel layer; storing an identifier of the target process in association with the wakelock created by the target process; when it is determined that the target process is exited abnormally, acquiring a wakelock corresponding to the identifier of the target process; and when it is determined that the wakelock corresponding to the identifier of the target process is in an activated state, releasing the wakelock.

Description

Management method and electronic equipment of wake lock

This application claims the priority of a Chinese patent application filed with the State Intellectual Property Office on July 26, 2019, the application number is 201910687713.2, and the application name is "a wake-lock management method and electronic equipment", the entire content of which is incorporated by reference In this application.

Technical field

This application relates to the field of electronic equipment, and in particular to a management method and electronic equipment of a wake-up lock.

Background technique

Nowadays, electronic devices such as mobile phones have become indispensable communication tools in people's daily life and work. By installing an application program (application, APP, hereinafter referred to as an application) in a mobile phone, the functions of the mobile phone can be improved to provide users with a richer experience. For applications installed in mobile phones, you can apply for a wakelock to ensure the normal operation of certain services.

Wakelock (wakelock) is a locking mechanism. As long as the application applies for this lock (or as long as the lock is held), the processor (central processing unit, CPU) of the mobile phone will always be in working state, and the system cannot enter the sleep state. , In order to ensure the normal operation of the corresponding business of the application. For example, the process used to implement the function of the application can create a wakelock, so that when the mobile phone screen is turned off, the mobile phone screen can still be woken up to display the prompt message of the application.

However, if the application is locked abnormally, the system will not be able to sleep, which will cause high power consumption and greatly shorten the battery life of the mobile phone.

Summary of the invention

The embodiments of the present application provide a wake lock management method and an electronic device, which solves the problem that the system cannot sleep for a long time due to the abnormal application of the lock, and the device consumes fast power, thereby prolonging the battery life of the device.

In order to achieve the foregoing objectives, the following technical solutions are adopted in the embodiments of this application:

In the first aspect, an embodiment of the present application provides a wakelock management method, which may include: a process of an electronic device creates a wakelock, the process includes a target process, and the target process may include one or more of the following processes: Create a wakelock process by writing file nodes, and create a wakelock process by invoking the corresponding interface of the kernel kernel layer of the electronic device; the electronic device associates the identifier of the target process with the wakelock created by the target process; the target process exits abnormally when it is determined When it is time, the wakelock corresponding to the identifier of the target process is obtained; when it is determined that the state of the wakelock corresponding to the identifier of the target process is active, the wakelock is released.

In the wakelock management method provided by the embodiments of the present application, for a wakelock created by writing a file node or calling the corresponding interface of the kernel layer, the process identifier is recorded at the kernel layer to bind it to the process resource of. In this way, after the corresponding process exits abnormally, the wakelock applied for by the process can be automatically released when the process exit processing is performed, avoiding abnormal application locks, ensuring that the system sleeps in time, and extending the battery life of the electronic device. In addition, the solution provided by this embodiment does not cause large system overhead and has universal applicability.

In a possible implementation, the target process of the electronic device creates a wakelock by writing a file node, which may include: the target process writes the name of the wakelock that the target process needs to create into the corresponding file node; the electronic device writes the target The process ID and the wakelock created by the target process are stored associative storage, which can include: the kernel layer obtains the target process ID, and creates a wake_source node at the kernel layer. The wake_source node includes the target process ID and the wakelock lock that the target process needs to create. name. In this way, for a process that creates a wakelock by writing a file node, when the wake_source node is created in the kernel layer, the identifier of the process to which the wake_source node belongs is written into the wake_source node, so as to realize the association between the wakelock created by the process and the process identifier.

In another possible implementation, the target process of the electronic device creates a wakelock by calling the corresponding interface of the kernel layer, which may include: the target process calls the corresponding interface of the kernel layer, and inputting the name of the wakelock that the target process needs to create; The electronic device stores the identifier of the target process in association with the wakelock created by the target process, which may include: obtaining the identifier of the target process at the kernel layer and creating a wake_source node at the kernel layer. The wake_source node includes the identifier of the target process and the wakelock created by the target process. The lock name. In this way, for a process that creates a wakelock by calling the corresponding interface of the kernel layer, when the wake_source node is created in the kernel layer, the identifier of the process to which the wake_source node belongs is written into the wake_source node, so that the wakelock created by the process is associated with the process identifier. .

In another possible implementation manner, when the electronic device determines that the target process exits abnormally, acquiring the wakelock corresponding to the identifier of the target process may include: when the target process exits abnormally, the kernel layer obtains the wake_source containing the identifier of the target process. Node; when the electronic device determines that the state of the wakelock corresponding to the target process's identifier is the active state, releasing the wakelock may include: the kernel layer deactivates the wake_source node when the state of the wake_source node containing the target process's identifier is determined to be the active state . In this way, after the process exits abnormally, the wakelock as a process management resource can be automatically released when the process exit processing is performed at the kernel layer.

In another possible implementation manner, the aforementioned target process may be an application process, a local native process or a kernel process.

In the second aspect, an embodiment of the present application provides an electronic device. The electronic device may include a processor and a memory; the processor and the memory are coupled, and the memory is used to store computer program codes. The computer program codes include computer instructions. When the electronic device is executed, the electronic device is caused to perform the following operations: the process creates a wakelock wakelock, the process includes the target process, and the target process includes one or more of the following processes: the process of creating the wakelock by writing to the file node, and calling the electronic device The kernel kernel layer of the kernel layer corresponds to the interface to create the wakelock process; the target process identifier and the wakelock created by the target process are associated and stored; when the target process is determined to exit abnormally, the wakelock corresponding to the target process identifier is obtained; When the state of the wakelock corresponding to the mark is activated, the wakelock is released.

In a possible implementation, the target process creates a wakelock by writing a file node, including: the target process writes the lock name of the wakelock that the target process needs to create into the corresponding file node; and the target process identifier and the target process The created wakelock associated storage includes: the kernel layer obtains the identifier of the target process, and the wake_source node is created at the kernel layer. The wake_source node includes the identifier of the target process and the name of the wakelock that the target process needs to create.

In another possible implementation, the target process creates wakelock by calling the corresponding interface of the kernel layer, including: the target process calls the corresponding interface of the kernel layer, and enters the lock name of the wakelock that the target process needs to create; The identifier and wakelock associated storage created by the target process include: the kernel layer obtains the identifier of the target process and creates a wake_source node at the kernel layer. The wake_source node includes the identifier of the target process and the name of the wakelock that the target process needs to create.

In another possible implementation manner, when it is determined that the target process exits abnormally, obtaining the wakelock corresponding to the target process identifier includes: when the target process exits abnormally, the kernel layer obtains the wake_source node containing the target process identifier; When determining that the state of the wakelock corresponding to the identifier of the target process is the active state, releasing the wakelock includes: when the kernel layer determines that the state of the wake_source node containing the identifier of the target process is the active state, deactivating the wake_source node.

In another possible implementation, the target process may be an application process, a local native process or a kernel process.

In a third aspect, embodiments of the present application provide a computer storage medium, the computer storage medium includes computer instructions, when the computer instructions run on an electronic device, the electronic device executes the first aspect or a possible implementation of the first aspect The wake lock management method described in any of the methods.

In a fourth aspect, the embodiments of the present application provide a computer program product, which when the computer program product runs on a computer, causes the computer to execute the wake-up as described in the first aspect or any one of the possible implementations of the first aspect Lock management method.

In a fifth aspect, an embodiment of the present application provides a device that has a function of implementing the behavior of an electronic device in the method of the first aspect. The function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions, for example, a creation unit or module, an acquisition unit or module, and a release unit or module.

It should be understood that the description of technical features, technical solutions, beneficial effects or similar language in this application does not imply that all the features and advantages can be realized in any single embodiment. On the contrary, it can be understood that the description of the features or beneficial effects means that a specific technical feature, technical solution or beneficial effect is included in at least one embodiment. Therefore, the descriptions of technical features, technical solutions, or beneficial effects in this specification do not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions, and beneficial effects described in this embodiment can also be combined in any appropriate manner. Those skilled in the art will understand that the embodiments can be implemented without one or more specific technical features, technical solutions, or beneficial effects of the specific embodiments. In other embodiments, additional technical features and beneficial effects may also be identified in specific embodiments that do not reflect all the embodiments.

Description of the drawings

Figure 1 is a schematic diagram of a network architecture applied to an APT scenario provided by the prior art;

FIG. 2 is a simplified schematic diagram of a system architecture provided by an embodiment of the application;

FIG. 3 is a schematic flowchart of a wake lock management method provided by an embodiment of the application;

FIG. 4 is a schematic diagram of the composition of a wake lock management device provided by an embodiment of the application.

Detailed ways

For an application in an electronic device, the electronic device usually creates multiple processes for it to execute different services to implement corresponding functions. Among these services, the execution of some services (such as the display of prompt messages) requires the system to be in a working state all the time and cannot sleep. Android (Android) provides a lock mechanism, wakelock, as long as the lock system cannot enter sleep. Therefore, the process used to implement the function of the application can create a wakelock to ensure that the system will not sleep during the execution of the corresponding service.

Generally speaking, the processes in the Android system can be divided into three categories: application processes, native processes and kernel processes. The application process may refer to the process created by the application. The native process may refer to a process created in the native layer of the Android system of the electronic device to provide local services or system library functions. The process created in the kernel mode can be called a kernel process, such as a kernel driver process. In addition, the native process and the kernel process are generally resident, that is, they have been created when the system starts, and when an application needs to implement the corresponding function, it can provide the corresponding service.

The function of the application can be realized by one or more of the above three types of processes. In this embodiment, the wakelock created by the process for implementing the function of the application can be regarded as the wakelock of the application, or a lock held by the application. The application can hold one or more wakelocks. In addition, when the process exits, it also needs to release the wakelock it created. It should be noted that, in an electronic device, as long as a process applies for a wakelock, or as long as an application holds a lock, the CPU of the electronic device will not sleep and is always working.

Currently, processes can create/release wakelocks in the following ways:

Method 1. Create/release wakelock by invoking the corresponding interface of PowerManagerService. For example, the wakelock is created by calling the acquire interface of PowerManagerService, and the wakelock is released by calling the release interface of PowerManagerService.

Method 2. Create wakelock by calling acquire_wake_lock interface, and release wakelock by calling release_wake_lock interface.

Method 3. Create/release a wakelock by directly writing to the file node, such as writing the lock name of the wakelock to be created to the corresponding file node. For example, create wakelock by writing file /sys/power/wake_lock, and release wakelock by writing file /sys/power/wake_unlock.

Method 4. Create/release wakelock by calling the corresponding interface of the kernel layer. For example, create wakelock by calling wake_lock/wake_lock_timeout, and release wakelock by calling wake_unlock/wake_lock_active.

Among them, the application process generally creates/releases wakelock through method 1. The native process can create/release wakelock by way 2 or way 3. The kernel process uses method 4 to create/release wakelock.

However, the above method of releasing wakelock only takes effect when the process exits normally. In the case where the process exits abnormally, such as the process exits abnormally when it cross-bounds access, the above-mentioned method of releasing wakelock cannot take effect. In other words, when the process exits abnormally, the wakelock created by it cannot be released normally, or the release will be missed, which will cause the system to fail to sleep and cause high power consumption. Among them, the situation in which the process used to implement the function of the application exits but the wakelock applied for is not released is called abnormal application lock holding.

In the prior art, in order to avoid the occurrence of abnormal lock-holding of applications, the Power Manager Service (PMS) of the electronic device can detect the lock-holding application state through the binder mechanism. When the application is abnormal, the electronic device can detect that the application is not responding through the binder mechanism. At this time, the electronic device will actively release the wakelock held by the application. But the binder mechanism can only release the wakelock created by the above method 1 or method 2, and it cannot take effect for the wakelock created by the above method 3 and method 4.

For the wakelock created by the above method 3 or method 4, the following two detection mechanisms can be used to detect the application of abnormal holding lock. Mechanism 1. The lock-holding application detects whether there is an abnormal lock-holding situation in the application according to the end of the service. If the application's business has ended, but the wakelock requested by the process executing the business is not released, it is determined that the application is holding the lock abnormally. At this time, the corresponding wakelock can be released. Mechanism 2. The system monitors all lock-holding applications in a manner similar to a watchdog. If an application does not respond within a period of time, it is considered that the application is abnormal, or it is determined that the application is abnormally locked. At this point, the wakelock held by the application can be released.

However, in the above mechanism 1, the application cannot accurately identify the end of the service, that is, a misjudgment may occur. For example, the service has ended, but the application does not recognize it. In addition, when the application is abnormal, the detection mechanism will also fail. In this way, there will still be situations where the application locks abnormally. In the above mechanism 2, the system needs to poll and monitor all lock-holding applications, which will bring greater system overhead. In addition, this monitoring mechanism needs to modify the implementation of the application so that it can register watchdogs, which is not universal. That is to say, for the wakelock created by the above method 3 or method 4, the current mechanism cannot well solve the problem of the system cannot sleep and the device consumes high power due to the abnormal lock holding of the application.

The embodiment of the present application provides a method for managing wake locks. For a wakelock created by the above method 3 or method 4, after the corresponding process exits abnormally, the wakelock applied for by the process can be automatically released to avoid the application of abnormal lock holding situations. Ensure that the system sleeps in time, extending the battery life of electronic devices. In addition, the solution provided by this embodiment does not cause large system overhead and has universal applicability.

Exemplarily, the electronic devices described in the embodiments of this application may be mobile phones, tablet computers, desktop computers, laptops, handheld computers, notebook computers, ultra-mobile personal computers (UMPC), netbooks, As well as cellular phones, personal digital assistants (PDA), augmented reality (AR)\virtual reality (VR) devices, wearable devices (such as smart watches), media players, etc. The application embodiment does not impose special restrictions on the specific form of the device.

The implementation of the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings.

Please refer to FIG. 1, which is a schematic structural diagram of an electronic device provided by an embodiment of this application. As shown in FIG. 1, the electronic device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, and a battery 142, Antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, earphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, A display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

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

The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), and an image signal processor. (image signal processor, ISP), controller, memory, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (NPU) Wait. Among them, the different processing units may be independent devices or integrated in one or more processors.

The controller can be the nerve center and command center of the electronic device. The controller can generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching and executing instructions.

A memory may also be provided in the processor 110 to store instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can store instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to use the instruction or data again, it can be directly called from the memory. Repeated accesses are avoided, the waiting time of the processor 110 is reduced, and the efficiency of the system is improved.

In some embodiments, the processor 110 may include one or more interfaces. The interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, and a universal asynchronous transmitter (universal asynchronous transmitter) interface. receiver/transmitter, UART) interface, mobile industry processor interface (MIPI), general-purpose input/output (GPIO) interface, SIM interface, and/or USB interface, etc.

The charging management module 140 is used to receive charging input from the charger. Among them, the charger can be a wireless charger or a wired charger. While the charging management module 140 charges the battery 142, it can also supply power to the electronic device through the power management module 141.

The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and/or the charge management module 140, and supplies power to the processor 110, the internal memory 121, the external memory, the display screen 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle times, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 may also be provided in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may also be provided in the same device.

The wireless communication function of the electronic device can be realized by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, and the baseband processor.

The antenna 1 and the antenna 2 are used to transmit and receive electromagnetic wave signals.

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G and the like applied to electronic devices. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves by the antenna 1, and perform processing such as filtering, amplifying and transmitting the received electromagnetic waves to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor, and convert it into electromagnetic waves for radiation via the antenna 1.

The wireless communication module 160 can provide applications in electronic devices including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), and global navigation satellite systems. (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, perform frequency modulation, amplify it, and convert it into electromagnetic wave radiation via the antenna 2.

In some embodiments, the antenna 1 of the electronic device is coupled with the mobile communication module 150, and the antenna 2 is coupled with the wireless communication module 160, so that the electronic device can communicate with the network and other devices through wireless communication technology. The wireless communication technologies may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband Code division multiple access (wideband code division multiple access, WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC , FM, and/or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou navigation satellite system (BDS), quasi-zenith satellite system (quasi -zenith satellite system, QZSS) and/or satellite-based augmentation systems (SBAS).

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

The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can adopt liquid crystal display (LCD), organic light-emitting diode (OLED), active-matrix organic light-emitting diode or active-matrix organic light-emitting diode (active-matrix organic light-emitting diode). emitting diode, AMOLED, flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device may include 1 or N display screens 194, and N is a positive integer greater than 1.

Electronic equipment can realize shooting functions through ISP, camera 193, video codec, GPU, display 194, and application processor.

The ISP is used to process the data fed back from the camera 193. ISP can also optimize the image noise, brightness, and skin color. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or videos. In some embodiments, the electronic device may include 1 or N cameras 193, and N is a positive integer greater than 1.

Digital signal processors are used to process digital signals. Video codecs are used to compress or decompress digital video. The electronic device can support one or more video codecs.

NPU is a neural-network (NN) computing processor. By drawing on the structure of biological neural networks, for example, the transfer mode between human brain neurons, it can quickly process input information and can continuously learn by itself. NPU can realize the intelligent cognition of electronic devices and other applications, such as: image recognition, face recognition, voice recognition, text understanding, etc.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device. The external memory card communicates with the processor 110 through the external memory interface 120 to realize the data storage function. For example, save music, video and other files in an external memory card.

The internal memory 121 may be used to store computer executable program code, where the executable program code includes instructions. The processor 110 executes various functional applications and data processing of the electronic device by running instructions stored in the internal memory 121. For example, in the embodiment of the present application, the processor 110 may automatically release the wakelock applied for by the process after the process exits abnormally by executing the instructions stored in the internal memory 121. The internal memory 121 may include a storage program area and a storage data area. Among them, the storage program area can store an operating system, at least one application program (such as a sound playback function, an image playback function, etc.) required by at least one function. The data storage area can store data (such as audio data, phone book, etc.) created during the use of the electronic device. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash storage (UFS), etc.

The electronic device can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. For example, music playback, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal for output, and is also used to convert an analog audio input into a digital audio signal. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be provided in the processor 110, or part of the functional modules of the audio module 170 may be provided in the processor 110.

The speaker 170A, also called a "speaker", is used to convert audio electrical signals into sound signals. The electronic device can listen to music through the speaker 170A, or listen to a hands-free call.

The receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device answers a call or voice message, it can receive the voice by bringing the receiver 170B close to the human ear.

The microphone 170C, also called "microphone", "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can approach the microphone 170C through the mouth to make a sound, and input the sound signal to the microphone 170C. The electronic device may be provided with at least one microphone 170C.

The earphone interface 170D is used to connect wired earphones. The earphone interface 170D may be a USB interface 130, or a 3.5mm open mobile terminal platform (OMTP) standard interface, or a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor may be provided on the display screen 194. There are many types of pressure sensors, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc.

The gyroscope sensor can be used to determine the movement posture of the electronic device. In some embodiments, the angular velocity of the electronic device around three axes (ie, x, y, and z axes) can be determined by a gyroscope sensor. The gyroscope sensor can be used for shooting anti-shake. The gyroscope sensor can also be used for navigation and somatosensory game scenes.

The air pressure sensor is used to measure air pressure. In some embodiments, the electronic device calculates the altitude based on the air pressure value measured by the air pressure sensor to assist positioning and navigation. The magnetic sensor includes a Hall sensor. The electronic device can use a magnetic sensor to detect the opening and closing of the flip holster. The acceleration sensor can detect the magnitude of the acceleration of the electronic device in all directions (usually three-axis). The magnitude and direction of gravity can be detected when the electronic device is stationary. It can also be used to identify the posture of electronic devices, and used in applications such as horizontal and vertical screen switching, pedometers and so on. Distance sensor, used to measure distance.

The proximity light sensor may include, for example, a light emitting diode (LED) and a light detector, such as a photodiode. The electronic device emits infrared light through the light-emitting diode. Electronic equipment uses photodiodes to detect infrared reflected light from nearby objects to determine whether there are objects near the electronic equipment.

The ambient light sensor is used to sense the brightness of the ambient light. The electronic device can adaptively adjust the brightness of the display screen 194 according to the perceived brightness of the ambient light. The ambient light sensor can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor can also cooperate with the proximity light sensor to detect whether the electronic device is in the pocket to prevent accidental touch.

The fingerprint sensor is used to collect fingerprints. Electronic devices can use the collected fingerprint characteristics to unlock fingerprints, access application locks, take photos with fingerprints, and answer calls with fingerprints.

The temperature sensor is used to detect temperature. In some embodiments, the electronic device uses the temperature detected by the temperature sensor to execute the temperature processing strategy.

Touch sensor, also called "touch panel". The touch sensor may be provided on the display screen 194, and the touch screen is composed of the touch sensor and the display screen 194, which is also called a “touch screen”. The touch sensor is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. The visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor may also be disposed on the surface of the electronic device, which is different from the position of the display screen 194.

Bone conduction sensors can acquire vibration signals. In some embodiments, the bone conduction sensor can obtain the vibration signal of the vibrating bone mass of the human voice. The bone conduction sensor can also contact the human pulse and receive the blood pressure pulse signal. In some embodiments, the bone conduction sensor may also be provided in the earphone.

The button 190 includes a power button, a volume button, and so on. The button 190 may be a mechanical button. It can also be a touch button. The electronic device can receive key input and generate key signal input related to user settings and function control of the electronic device. The motor 191 can generate vibration prompts. The motor 191 can be used for incoming call vibration notification, and can also be used for touch vibration feedback. The indicator 192 may be an indicator light, which may be used to indicate the charging status, power change, or to indicate messages, missed calls, notifications, and so on.

The SIM card interface 195 is used to connect to the SIM card. The SIM card can be inserted into the SIM card interface 195 or pulled out from the SIM card interface 195 to achieve contact and separation with the electronic device. The electronic device can support 1 or N SIM card interfaces, and N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. The electronic device interacts with the network through the SIM card to realize functions such as call and data communication. In some embodiments, the electronic device adopts eSIM, that is, an embedded SIM card. The eSIM card can be embedded in the electronic device and cannot be separated from the electronic device.

The software system of the electronic device can adopt a layered architecture, event-driven architecture, micro-core architecture, micro-service architecture, or cloud architecture. The embodiment of the present application takes an Android system with a layered architecture as an example to illustrate the software structure of an electronic device.

FIG. 2 is a schematic diagram of the software structure of an electronic device provided by an embodiment of the application. The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Communication between layers through software interface. As shown in FIG. 2, in some embodiments, the Android system is divided into four layers, from top to bottom, the application layer, the application framework layer (framework), the native layer, and the kernel layer.

Among them, the application layer may include a series of application packages. For example, the application package may include applications such as WeChat, Amazon, calendar, call, map, music player, video player, short message, etc.

The application framework layer provides application programming interfaces (application programming interface, API) and programming frameworks for applications in the application layer to provide support for the operation of applications in the application layer.

The native layer is used to provide system services, location services, touch services, display services, etc. for applications in the application layer.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, sensor driver, location driver (such as GPS driver) and so on.

In this embodiment, when the system is started, the electronic device creates a native process and/or a kernel process for providing corresponding services. In addition, when the application of the application layer of the electronic device is started, a corresponding application process is created. In this way, by using one or more of these processes, the corresponding functions of the application can be realized. For example, when the system is started, the electronic device creates a native process 1 and a kernel process 1 for providing location services. Then, native process 1 and kernel process 1 can provide corresponding location services to implement applications such as Amazon's location function.

Exemplarily, the technical solutions involved in the following embodiments can all be implemented in an electronic device having the foregoing hardware architecture and software architecture. The control method provided by the embodiment of the present application will be described in detail below with reference to the drawings and application scenarios.

FIG. 3 is a schematic flowchart of a wake lock management method provided by an embodiment of the application. As shown in Figure 3, the method may include:

S301. The process of the electronic device creates a wakelock.

For an application in an electronic device, the electronic device creates multiple processes for it to execute corresponding services to realize the functions of the application. In the created process, the business performed by some processes requires the system to be in a working state and cannot sleep. These processes can create wakelocks to ensure that the system does not sleep during the execution of the corresponding services.

Generally, the operating system of the electronic device is the Android system as an example. Referring to Figure 2, the processes in the Android system can be divided into three categories: application processes, native processes and kernel processes. The function of the application can be realized through one or more of these three types of processes. In this embodiment, the wakelock created by the process for implementing the function of the application can be regarded as the wakelock of the application, or a lock held by the application. The application can hold one or more wakelocks.

The current process can create/release wakelock in the following four ways:

Method 1. Create/release wakelock by calling the corresponding interface of PowerManagerService.

Method 3. Create/release a wakelock by directly writing to the file node, for example, by writing the lock name of the wakelock that the process needs to create to the corresponding file node.

Method 4. Create/release wakelock by calling the corresponding interface of the kernel layer.

Exemplarily, for the application process, the wakelock can be created/released through the above method 1. The native process can create/release wakelock by way 2 or way 3. The kernel process can create/release wakelock through method 4. In addition, a wakelock created in any way will eventually create a wake_source node in the kernel layer.

For example, take the application process (such as process A) using method 1 to create a wakelock as an example. When process A needs the system not to sleep during the business it is executing, process A can use the power saving management service (PowerMangerService) provided by the application framework layer to call the acquire interface of PowerManagerService to create a wakelock. For example, the wakelock created by process A is called wakelock_A. Specifically, process A calls the acquire interface of PowerManagerService and enters the lock name of wakelock_A that process A needs to create. The native layer can obtain the identity of process A according to the call, such as PID_A, and call the acquire_wake_lock interface to write the identity of process A in the corresponding file node, such as /sys/power/wake_lock, that is, the locks of PID_A and wakelock_A name. After that, the wakelock_A of process A is created.

For another example, take a native process (such as process B) using method 2 to create a wakelock as an example. Process B can create a wakelock by calling the corresponding interface, such as acquire_wake_lock, when the business it is executing requires that the system does not sleep. For example, the wakelock created by process B is called wakelock_B. Specifically, process B inputs the lock name of wakelock_B that process B needs to create by calling the interface acquire_wake_lock. The native layer can obtain the identity of process B according to the call, such as PID_B, and write the identity of process B in the corresponding file node, such as /sys/power/wake_lock, that is, the lock names of PID_B and wakelock_B. After that, the wakelock_B of process B is created.

For another example, take a native process (such as process C) using method 3 to create a wakelock as an example. Process C can create a wakelock by writing a file node when the business it is executing requires that the system does not sleep. For example, the wakelock created by process C is called wakelock_C. Specifically, the process C can directly write the lock name of the wakelock_C that the process C needs to create in the corresponding file node, such as /sys/power/wake_lock. After that, the wakelock_C of process C is created.

For another example, take the kernel process (such as process D) using method 4 to create a wakelock as an example. When process D needs the system not to sleep during the business it is executing, process D can call the corresponding interface of the kernel layer, such as wake_lock/wake_lock_timeout, and enter the name of the wakelock that process D needs to create. For example, the wakelock created by process D is called wakelock_D. After that, the wakelock_D of process D is created.

S302. The electronic device stores the identifier of the target process in association with the wakelock created by the target process. The target process includes one or more of the following processes: a process that creates a wakelock by writing a file node, and calls a corresponding interface at the kernel layer. Way to create a wakelock process.

Currently, resources such as file handles, occupied memory, and sockets of a process are used as resources managed by the process, and are automatically released when the process exits. In this embodiment, wakelock can also be used as a resource managed by the process to achieve the purpose of automatically releasing the wakelock created by the process when it exits. Among them, for a process that uses the above method 1 and method 2 to create a wakelock, when it exits abnormally, the wakelock created by it can be released through the binder mechanism. Since this mechanism is not applicable to processes that create wakelocks using the above methods 3 and 4, in this embodiment, only the processes that create wakelocks using the above methods 3 and 4 can be used as process management. A resource.

Specifically, for a process that creates a wakelock by writing a file node and by calling the corresponding interface of the kernel layer, such as a target process, when a corresponding wake_source node is created at the kernel layer, the kernel layer can create a wakelock and a wakelock created by the target process. The identification of the target process is stored in association. For example, the kernel layer stores the wake_source node created in the kernel layer in association with the PID of the process to which the wake_source node belongs. In this way, the wakelock created by it can be used as a resource for process management to facilitate subsequent management.

For example, in combination with the example in S301, process C creates wakelock by writing file nodes. After process C writes the lock name of wakelock_C that needs to be created into the corresponding file node, after completing the creation of wakelock_C, the kernel layer can obtain the identity of the process C, namely PID_C, and create the wake_source node of process C in the kernel layer. For example, when it is called wake_source node C, the PID of process C, that is, PID_C and the lock name of wakelock_C to be created by process C, can be written into the wake_source node C, so that the created wake_source node C and the process to which wake_source node C belongs The PID is associated.

For another example, in combination with the example in S301, process D creates wakelock by calling the corresponding interface of the kernel layer. In process D, by calling the corresponding interface of the kernel layer, enter the lock name of wakelock_D that process D needs to create, and after completing the creation of wakelock_D, the kernel layer can obtain the identity of process D, namely PID_D, and in the kernel layer. Create the wake_source node of process D, for example, when it is called wake_source node D, the PID of process D, namely PID_D and the lock name of wakelock_D to be created by process D, can be written into the wake_source node D, so as to create wake_source node D It is associated with the PID of the process to which the wake_source node D belongs.

Of course, for a process that uses method 1 to create a wakelock, such as process A in the example of S301, and a process that uses method 2 to create a wakelock, such as process B, after process A and process B complete the creation of wakelock, the kernel layer will also Correspondingly, a wake_source node is created at the kernel layer, and the wake_source node may include the lock name of the wakelock that the corresponding process needs to create. For example, the kernel layer creates wake_source node A for process A in the kernel layer, and the wake_source node A includes the lock name of wakelock_A that process A needs to create. For another example, the kernel layer creates a wake_source node B for process B in the kernel layer, and the wake_source node B includes the lock name of wakelock_B that process B needs to create.

S303. When determining that the target process exits abnormally, the electronic device acquires a wakelock corresponding to the identifier of the target process.

S304. The electronic device releases the wakelock when determining that the state of the wakelock corresponding to the identifier of the target process is the active state.

If the process used to implement the function of the application exits but the wakelock it applied for is not released, it can be considered that the application is holding the lock abnormally. In order to avoid this situation, for processes that create wakelock using the above methods 1 and 2, such as process A and process B in the example of S301, when they exit abnormally, the PMS of the electronic device can detect the abnormal hold of the application through the binder mechanism. In the lock situation, it is detected that process A or process B has exited, but the wakelock created by it has not been released. At this time, the electronic device will actively release the wakelock created by the process. For processes that create wakelocks using the above methods 3 and 4, such as process C and process D in the example of S301, when they exit abnormally, the above binder mechanism does not apply.

In this embodiment, the electronic device can trigger the process exit processing at the kernel layer when determining the target process, such as process C or process D, which exits abnormally. For example, the kernel layer can clean up the file handle, occupied memory, socket and other resources of the target process. In addition, the kernel layer can also execute the above S303-S304 to release the wakelock created by the target process. Specifically, the kernel layer may obtain the wakelock corresponding to the identifier of the target process. Then, when it is determined that the state of the wakelock corresponding to the identifier of the target process is the active state, the wakelock is released.

For example, when the process C exits abnormally, the kernel layer of the electronic device can obtain the wake_source node containing the C's identity of the process. For example, the kernel layer determines that the wake_source node C contains the C's identity of the process. At this time, when the kernel layer determines that the state of the wake_source node C is the active state, it means that the wakelock created by the process C has not been released, and the kernel layer can release the wake_source node C. For another example, when the process D exits abnormally, the kernel layer of the electronic device can obtain the wake_source node containing the ID of the process D, for example, the kernel layer determines that the wake_source node D contains the ID of the process D. At this time, when the kernel layer determines that the state of the wake_source node D is the active state, it means that the wakelock created by the process D has not been released, and the kernel layer can release the wake_source node D. This can avoid the application of abnormal lock holding situations. Among them, the specific processing of releasing the corresponding wake_source node may be to deactivate the wake_source node to ensure that the system can sleep in time.

Other embodiments of the present application also provide a computer storage medium. The computer storage medium may include computer instructions. When the computer instructions run on an electronic device, the electronic device executes the execution of the electronic device in the embodiment shown in FIG. 3. The various steps.

Other embodiments of the present application also provide a computer program product, which when the computer program product runs on a computer, causes the computer to execute each step performed by the electronic device in the embodiment shown in FIG. 3.

Other embodiments of the present application also provide a chip system, which can be applied to electronic devices; the chip system can include one or more interface circuits and one or more processors; the interface circuits and the processors are interconnected by wires; The interface circuit is used to receive signals from the memory of the electronic device and send signals to the processor. The signals include computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device executes the method in the corresponding embodiment of FIG. 3.

Other embodiments of the present application also provide an electronic device. The electronic device may include a processor and a memory; the processor and the memory are coupled, and the memory is used to store computer program codes. The computer program codes include computer instructions. When the device is executed, the electronic device is caused to execute the method in the corresponding embodiment in FIG. 3.

Other embodiments of the present application also provide a wake lock management device, which has the function of realizing the behavior of the electronic device in the corresponding embodiment in FIG. 3 above. The function can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions, for example, a creation unit or module, an acquisition unit or module, a release unit or module, and so on.

As shown in FIG. 4, the device may include a creation unit 401, an acquisition unit 402, and a release unit 403.

The creation unit 401 is used for a process to create a wakelock wakelock. The process may include a target process, and the target process may include one or more of the following processes: a process for creating a wakelock by writing a file node, and calling the corresponding interface of the kernel layer Create a wakelock process in a way; associate the target process identifier with the wakelock created by the target process.

The acquiring unit 402 is configured to acquire the wakelock corresponding to the identifier of the target process when it is determined that the target process exits abnormally.

The releasing unit 403 is configured to release the wakelock when it is determined that the state of the wakelock corresponding to the identifier of the target process is the active state.

Further, the creation unit 401 is specifically used for the target process to write the lock name of the wakelock that the target process needs to create into the corresponding file node, obtain the identifier of the target process, and create a wake_source node in the kernel layer, and the wake_source node includes the target process The identifier and the lock name of the wakelock that the target process needs to create.

Further, the creation unit 401 is specifically used for the target process to call the corresponding interface of the kernel layer, to input the lock name of the wakelock that the target process needs to create; to obtain the identifier of the target process, to create a wake_source node in the kernel layer, and the wake_source node includes the target process The identifier and the lock name of the wakelock that the target process needs to create.

Further, the obtaining unit 402 is specifically configured to obtain the wake_source node containing the identifier of the target process when the target process exits abnormally.

The releasing unit 403 is specifically configured to deactivate the wake_source node when it is determined that the state of the wake_source node containing the identifier of the target process is the active state.

Further, the aforementioned target process may be an application process, a local native process or a kernel process.

The computer storage medium, computer program product, electronic device, wake lock management device, and chip system provided in the embodiment of the application are used to execute the method in the corresponding embodiment of FIG. 3 above, so the same effect can be achieved, and will not be omitted here. Repeat.

Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of the description, only the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned functions can be allocated as needed. It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed device and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods, for example, multiple units or components may be It can be combined or integrated into another device, or some features can be omitted or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate parts may or may not be physically separate. The parts displayed as units may be one physical unit or multiple physical units, that is, they may be located in one place, or they may be distributed to multiple different places. . Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application are essentially or the part that contributes to the prior art, or all or part of the technical solutions can be embodied in the form of software products, which are stored in a storage medium There are several instructions to make a device (which may be a single-chip microcomputer, a chip, etc.) or a processor (processor) execute all or part of the steps of the method described in each embodiment of the application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

The above are only specific implementations of this application, but the protection scope of this application is not limited to this. Any change or replacement within the technical scope disclosed in this application shall be covered by the protection scope of this application . Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A management method of wake lock, characterized in that the method includes:

A process of the electronic device creates a wakelock wakelock, the process includes a target process, and the target process includes one or more of the following processes: a process that creates a wakelock by writing a file node, and uses a kernel kernel that calls the electronic device The wakelock process is created in the way that the layer corresponds to the interface;

The electronic device associates and stores the identifier of the target process and the wakelock created by the target process;

When determining that the target process exits abnormally, the electronic device acquires a wakelock corresponding to the identifier of the target process;

The electronic device releases the wakelock when determining that the state of the wakelock corresponding to the identifier of the target process is the active state.
The method according to claim 1, wherein:

The target process of the electronic device creates a wakelock in a way of writing a file node, including:

The target process writes the lock name of the wakelock that the target process needs to create into the corresponding file node;

The electronic device associates and stores the identifier of the target process and the wakelock created by the target process, including:

The kernel layer obtains the identifier of the target process, and creates a wake_source node in the kernel layer. The wake_source node includes the identifier of the target process and the lock name of the wakelock to be created by the target process.
The method according to claim 1, wherein:

The target process of the electronic device creates a wakelock by calling the corresponding interface of the kernel layer, including:

The target process calls the corresponding interface of the kernel layer, and enters the lock name of the wakelock that the target process needs to create;

The electronic device associates and stores the identifier of the target process and the wakelock created by the target process, including:

The kernel layer obtains the identifier of the target process, and creates a wake_source node in the kernel layer. The wake_source node includes the identifier of the target process and the lock name of the wakelock that the target process needs to create.
The method according to claim 2 or 3, wherein:

When the electronic device determines that the target process exits abnormally, acquiring the wakelock corresponding to the identifier of the target process includes:

When the target process exits abnormally, the kernel layer obtains the wake_source node containing the identifier of the target process;

When the electronic device determines that the state of the wakelock corresponding to the identifier of the target process is the active state, releasing the wakelock includes:

The kernel layer deactivates the wake_source node when determining that the state of the wake_source node containing the identifier of the target process is the active state.
The method according to any one of claims 1-4, wherein the target process is an application process, a local native process or a kernel process.
An electronic device, characterized in that the electronic device comprises: a processor and a memory; the processor is coupled to the memory, and the memory is used to store computer program code, and the computer program code includes computer instructions. When the computer instruction is executed by the electronic device, the electronic device is caused to perform the following operations:

The process creates a wakelock wakelock, the process includes a target process, and the target process includes one or more of the following processes: a process that creates a wakelock by writing a file node, and uses a corresponding interface that calls the kernel kernel layer of the electronic device The way to create a wakelock process;

Store the identifier of the target process in association with the wakelock created by the target process;

When it is determined that the target process exits abnormally, obtaining a wakelock corresponding to the identifier of the target process;

When it is determined that the state of the wakelock corresponding to the identifier of the target process is the active state, the wakelock is released.
7. The electronic device according to claim 6, wherein the target process uses a file node writing method to create a wakelock, comprising:

The target process writes the lock name of the wakelock that the target process needs to create into the corresponding file node;

The associating and storing the identifier of the target process and the wakelock created by the target process includes:

The kernel layer obtains the identifier of the target process, and creates a wake_source node in the kernel layer. The wake_source node includes the identifier of the target process and the lock name of the wakelock to be created by the target process.
The electronic device according to claim 6, wherein the target process uses the kernel layer corresponding interface to create the wakelock, comprising:

The target process calls the corresponding interface of the kernel layer, and enters the lock name of the wakelock that the target process needs to create;

The associating and storing the identifier of the target process and the wakelock created by the target process includes:

The kernel layer obtains the identifier of the target process, and creates a wake_source node in the kernel layer. The wake_source node includes the identifier of the target process and the lock name of the wakelock that the target process needs to create.
The electronic device according to claim 7 or 8, wherein when it is determined that the target process exits abnormally, obtaining a wakelock corresponding to the identifier of the target process comprises:

When the target process exits abnormally, the kernel layer obtains the wake_source node containing the identifier of the target process;

When it is determined that the state of the wakelock corresponding to the identifier of the target process is the active state, releasing the wakelock includes:

The kernel layer deactivates the wake_source node when determining that the state of the wake_source node containing the identifier of the target process is the active state.
The electronic device according to any one of claims 6-9, wherein the target process is an application process, a local native process or a kernel process.
A computer storage medium, characterized in that the computer storage medium includes computer instructions, and when the computer instructions run on an electronic device, the electronic device is caused to execute the electronic device according to any one of claims 1-5 The management method of wake lock.
A computer program product, characterized in that when the computer program product runs on a computer, the computer is caused to execute the wake lock management method according to any one of claims 1-5.