CN116795604B

CN116795604B - Processing method, device and equipment for application exception exit

Info

Publication number: CN116795604B
Application number: CN202311057040.5A
Authority: CN
Inventors: 滕家伟; 贾阳阳
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2023-08-22
Filing date: 2023-08-22
Publication date: 2023-12-12
Anticipated expiration: 2043-08-22
Also published as: CN116795604A

Abstract

The application discloses a processing method, a device and equipment for application abnormal exit. The method is applied to the electronic equipment and comprises the following steps: acquiring interface life cycles of N interfaces displayed in response to N opening operations of a first application, wherein the N opening operations are in one-to-one correspondence with the N interfaces, the corresponding interfaces are displayed based on each opening operation and flash back to a main interface of the electronic equipment after the corresponding interfaces are displayed, the interface life cycle of each interface is a time period between the moment when the electronic equipment creates each interface and the moment when the electronic equipment destroys each interface, and N is a positive integer; and under the condition that the interface life cycles of the N interfaces do not exceed the preset life cycle, automatically killing the first application so that the first application can normally run after restarting. The method can solve the problem that the interface of the application is abnormally exited after the application is started under the condition that the user does not need to participate, simplifies the user operation and improves the user experience.

Description

Processing method, device and equipment for application exception exit

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, and a device for processing application exception exit.

Background

At present, an application installed in an electronic device has a problem that an interface of the application exits to a main interface of the electronic device at the moment after the application is started, which is an abnormal condition, and can reduce user experience.

Aiming at the problem that the interface of the instant application after the electronic equipment starts the application is abnormally exited to the main interface of the electronic equipment, the electronic equipment is difficult to identify. When the user encounters the problem that the interface of the application is abnormally exited to the main interface of the electronic device after the application is started for many times, the user is required to manually kill the application or restart the electronic device to solve the abnormal situation, so that the operation of the user is complex and the experience of the user is poor.

Disclosure of Invention

The application provides a processing method, a device and equipment for abnormal exit of an application, which can solve the problem of abnormal exit of an application interface after application starting without user participation, simplify user operation and improve user experience.

In a first aspect, a method for processing abnormal exit of an application is provided, and the method is applied to an electronic device, and includes: acquiring interface life cycles of N interfaces displayed in response to N opening operations of a first application, wherein the N opening operations are in one-to-one correspondence with the N interfaces, the corresponding interfaces are displayed based on each opening operation and flash back to a main interface of the electronic equipment after the corresponding interfaces are displayed, the interface life cycle of each interface is a time period between the moment when the electronic equipment creates each interface and the moment when the electronic equipment destroys each interface, and N is a positive integer; and under the condition that the interface life cycles of the N interfaces do not exceed the preset life cycle, automatically killing the first application, so that the first application operates normally after restarting.

The main interface of the electronic device comprises at least an application icon of the first application. The main interface of the electronic device is also called a desktop initiator of the electronic device.

Based on the condition that each opening operation displays a corresponding interface and the corresponding interface is displayed and then the interface is flashed back to the main interface of the electronic device, and the interface life cycle of the interface corresponding to each opening operation does not exceed the preset life cycle, the problem that the first application abnormally exits to the main interface of the electronic device at the moment after the interface corresponding to each opening operation is started can be considered.

According to the technical scheme, under the conditions that the corresponding interface is displayed based on each opening operation, the corresponding interface is displayed and then the interface is flashed back to the main interface of the electronic equipment, and the interface life cycles of N interfaces corresponding to N opening operations do not exceed the preset life cycle, the electronic equipment automatically kills the first application, so that the problem that the interface of the application is abnormally exited after the application is started under the condition that the user is not required to participate in the method is solved, the user operation is simplified, and the user experience is improved.

In one possible implementation, N is a preset value.

N is a predetermined value, and the predetermined value is a finite upper limit value. The value of N may be predefined or dynamically adjusted. The value of N is not particularly limited, and may be set according to an actual scene. For example, N may be set equal to 1, 2, or 3, or the like, according to the user's use requirement. As another example, N is set equal to 2 or 4, etc., depending on the performance of the electronic device.

In the technical scheme, when N is a preset value and the life cycle of the interfaces of N interfaces corresponding to N opening operations does not exceed the preset life cycle, the electronic equipment can automatically kill the first application.

In another possible implementation, the N open operations are consecutive N operations detected by the electronic device.

In the technical scheme, when the electronic equipment detects the continuous N opening operations, and the interface life cycle of the interface corresponding to each opening operation does not exceed the preset life cycle, the electronic equipment can automatically kill the first application.

In another possible implementation, after the automatically killing the first application, the method further includes: and automatically starting the first application so that the first application normally operates after being restarted.

In the technical scheme, after the electronic equipment automatically kills the first application which has the abnormal exit of the application interface, the electronic equipment automatically restarts the first application so that the first application normally operates after restarting, and therefore, the method can improve the user experience without the participation of users.

In another possible implementation, after the automatically killing the first application, the method further includes: and starting the first application in response to user operation so that the first application runs normally after restarting.

In the technical scheme, after the electronic equipment automatically kills the first application which has the abnormal exit of the application interface, the electronic equipment restarts the first application in response to the user operation, so that the first application normally operates after restarting, and therefore, the method can meet the user requirement.

In another possible implementation manner, an operating system is installed in the electronic device, the operating system includes a detection processing service located at an application framework layer, and the method includes: the detection processing service obtains interface life cycles of the N interfaces; and the detection processing service automatically kills the first application under the condition that the interface life cycles of the N interfaces do not exceed the preset life cycle.

In another possible implementation manner, the operating system further includes a desktop initiator at an application layer, and an input management service and an activity management service at the application framework layer, where the detecting and processing service obtains interface life cycles of the N interfaces, and includes: the activity management service obtains the moment when the activity management service creates each interface and the moment when the electronic equipment destroys each interface; the activity management service sends the moment when the electronic equipment creates each interface and the moment when the electronic equipment destroys each interface to the detection processing service; and the detection processing service obtains the interface life cycle of each interface according to the time when the electronic equipment creates each interface and the time when the electronic equipment destroys each interface so as to obtain the interface life cycles of the N interfaces.

In another possible implementation manner, the operating system further includes a desktop initiator at an application layer, and an input management service and an activity management service at the application framework layer, where the detecting and processing service obtains interface life cycles of the N interfaces, and includes: the activity management service obtains the moment when the activity management service creates each interface and the moment when the electronic equipment destroys each interface; the activity management service obtains the interface life cycle of each interface according to the time when the electronic equipment creates each interface and the time when the electronic equipment destroys each interface; and the activity management service sends the interface life cycle of each interface to the detection processing service so that the detection processing service obtains the interface life cycles of the N interfaces.

In another possible implementation manner, the operating system further includes a desktop launcher at an application layer, and an input management service and an activity management service at the application framework layer, and before the detection processing service automatically kills the first application, the method further includes: transmitting each opening operation to the desktop initiator under the condition that the input management service detects the opening operation; notifying the activity management service to execute each opening operation under the condition that the desktop starter receives each opening operation; and the activity management service responds to each opening operation and displays an interface corresponding to each opening operation.

In a second aspect, a processing apparatus for application exception exit is provided, where the apparatus is applied to an electronic device, and the apparatus includes a processing unit, where the processing unit is configured to: acquiring interface life cycles of N interfaces displayed in response to N opening operations of a first application, wherein the N opening operations are in one-to-one correspondence with the N interfaces, the corresponding interfaces are displayed based on each opening operation and flash back to a main interface of the electronic equipment after the corresponding interfaces are displayed, the interface life cycle of each interface is a time period between the moment when the electronic equipment creates each interface and the moment when the electronic equipment destroys each interface, and N is a positive integer; and under the condition that the interface life cycles of the N interfaces do not exceed the preset life cycle, automatically killing the first application, so that the first application operates normally after restarting.

In a third aspect, there is provided an electronic device comprising means for performing any of the methods of the first aspect. The device may be a terminal device or a chip in the terminal device. The device may comprise an input unit and a processing unit.

When the device is a terminal device, the processing unit may be a processor and the input unit may be a communication interface; the terminal device may further comprise a memory for storing computer program code which, when executed by the processor, causes the terminal device to perform any of the methods of the first aspect.

When the device is a chip in a terminal device, the processing unit may be a processing unit inside the chip, and the input unit may be an output interface, a pin, a circuit, or the like; the chip may also include memory, which may be memory within the chip (e.g., registers, caches, etc.), or memory external to the chip (e.g., read-only memory, random access memory, etc.); the memory is for storing computer program code which, when executed by the processor, causes the chip to perform any of the methods of the first aspect.

In one possible implementation, the memory is used to store computer program code; a processor executing the computer program code stored by the memory, the processor for performing any one of the methods of the first aspect when the computer program code stored by the memory is executed.

In a fourth aspect, there is provided a computer readable storage medium storing computer program code which, when executed by an application exception exit processing apparatus, causes the application exception exit processing apparatus to perform any one of the application exception exit processing methods of the first aspect.

In a fifth aspect, there is provided a computer program product comprising: computer program code which, when run by an application exception handling device, causes the application exception handling device to perform any of the application exception handling methods of the first aspect.

It should be appreciated that the description of technical features, aspects, benefits or similar language in the present application does not imply that all of the features and advantages may be realized with any single embodiment. Conversely, it should be understood that the description of features or advantages is intended to include, in at least one embodiment, the particular features, aspects, or advantages. Therefore, the description of technical features, technical solutions or advantageous effects in this specification does not necessarily refer to the same embodiment. Furthermore, the technical features, technical solutions and advantageous effects described in the present embodiment may also be combined in any appropriate manner. Those of skill in the art will appreciate that an embodiment may be implemented without one or more particular features, aspects, or benefits of a particular embodiment. In other embodiments, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments.

Drawings

Fig. 1 is a schematic diagram of a hardware system of an electronic device 100 according to an embodiment of the present application.

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

Fig. 3 is a schematic diagram of a software architecture to which a processing method for application of exception exit is applied according to an embodiment of the present application.

Fig. 4 is a schematic diagram of a processing method for application exception exit according to an embodiment of the present application.

Fig. 5A is a schematic diagram of a main interface of the electronic device involved in the processing method for application exception exit provided in fig. 4.

FIG. 5B is a schematic diagram of an interface of a first application involved in the method for handling application exception exit provided in FIG. 4.

FIG. 5C is a schematic diagram of an interface of a first application involved in the method for handling application exception exit provided in FIG. 4.

Fig. 6 is a schematic diagram of another method for processing application exception exit according to an embodiment of the present application.

Fig. 7 is a schematic diagram of another method for processing an application exception exit according to an embodiment of the present application.

Fig. 8 is a schematic diagram of another method for processing an application exception exit according to an embodiment of the present application.

Fig. 9 is a schematic diagram of a processing apparatus for application exception exit according to an embodiment of the present application.

Fig. 10 is a schematic diagram of a structure of an electronic device provided by the present application.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

In the description of the embodiments of the present application, unless otherwise indicated, "/" means or, for example, a/B may represent a or B; "and/or" herein is merely one association relationship describing an association object, meaning that three relationships may exist; for example, a and/or B may represent: a alone; both A and B are present; there are three cases B alone.

In the description of embodiments of the present application, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more features. In the description of the present embodiment, unless otherwise specified, the meaning of "plurality" is two or more.

The technical scheme provided by the application is described below.

The method for processing the application abnormal exit provided by the embodiment of the application can be applied to the electronic equipment. The hardware structure and the software structure of the electronic device will be described in detail with reference to the accompanying drawings.

The electronic device 100 may be a mobile phone, a smart screen, a tablet computer, a wearable electronic device, an in-vehicle electronic device, an augmented reality (augmented reality, AR) device, a Virtual Reality (VR) device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (personal digital assistant, PDA), a projector, an in-vehicle device, etc., and the specific type of the electronic device 100 is not limited in the embodiments of the present application.

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 (subscriber identification 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.

The configuration shown in fig. 1 does not constitute a specific limitation on the electronic apparatus 100. In other embodiments of the application, electronic device 100 may include more or fewer components than those shown in FIG. 1, or electronic device 100 may include a combination of some of the components shown in FIG. 1, or electronic device 100 may include sub-components of some of the components shown in FIG. 1. The components shown in fig. 1 may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units. For example, the processor 110 may include at least one of the following processing units: application processors (application processor, AP), modem processors, graphics processors (graphics processing unit, GPU), image signal processors (image signal processor, ISP), controllers, video codecs, digital signal processors (digital signal processor, DSP), baseband processors, neural-Network Processors (NPU). The different processing units may be separate devices or integrated devices.

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 can be called directly from the 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. For example, the processor 110 may include at least one of the following interfaces: inter-integrated circuit, I2C) interfaces, inter-integrated circuit audio (inter-integrated circuit sound, I2S) interfaces, pulse code modulation (pulse code modulation, PCM) interfaces, universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interfaces, mobile industry processor interfaces (mobile industry processor interface, MIPI), general-purpose input/output (GPIO) interfaces, SIM interfaces, USB interfaces.

The I2C interface is a bi-directional synchronous serial bus comprising a serial data line (SDA) and a serial clock line (derail clock line, SCL). In some embodiments, the processor 110 may contain multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, charger, flash, camera 193, etc., respectively, through different I2C bus interfaces. For example: the processor 110 may be coupled to the touch sensor 180K through an I2C interface, such that the processor 110 communicates with the touch sensor 180K through an I2C bus interface to implement a touch function of the electronic device 100.

The I2S interface may be used for audio communication. In some embodiments, the processor 110 may contain multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through the I2S interface, to implement a function of answering a call through the bluetooth headset.

PCM interfaces may also be used for audio communication to sample, quantize and encode analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM interface.

In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface to implement a function of answering a call through the bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus for asynchronous communications. The bus may be a bi-directional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is typically used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function.

In some embodiments, the audio module 170 may transmit an audio signal to the wireless communication module 160 through a UART interface, to implement a function of playing music through a bluetooth headset.

The MIPI interface may be used to connect the processor 110 with peripheral devices such as the display 194 and camera 193. The MIPI interfaces include camera serial interfaces (camera serial interface, CSI), display serial interfaces (display serial interface, DSI), and the like. In some embodiments, processor 110 and camera 193 communicate through a CSI interface to implement the photographing functions of electronic device 100. The processor 110 and the display 194 communicate via a DSI interface to implement the display functionality of the electronic device 100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal interface as well as a data signal interface.

In some embodiments, a GPIO interface may be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, and the sensor module 180. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, or a MIPI interface.

The USB interface 130 is an interface conforming to the USB standard specification, and may be, for example, a Mini (Mini) USB interface, a Micro (Micro) USB interface, or a C-type USB (USB Type C) interface. The USB interface 130 may be used to connect a charger to charge the electronic device 100, to transfer data between the electronic device 100 and a peripheral device, and to connect a headset to play audio through the headset. The USB interface 130 may also be used to connect other electronic devices 100, such as AR devices.

The connection relationships between the modules shown in fig. 1 are merely illustrative, and do not constitute a limitation on the connection relationships between the modules of the electronic device 100. Alternatively, the modules of the electronic device 100 may also use a combination of the various connection manners in the foregoing embodiments.

The charge management module 140 is used to receive power from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 140 may receive the current of the wired charger through the USB interface 130. In some wireless charging embodiments, the charge management module 140 may receive electromagnetic waves (current path shown in dashed lines) through a wireless charging coil of the electronic device 100. The charging management module 140 may also supply power to the electronic device 100 through the power management module 141 while charging the battery 142.

The power management module 141 is used for connecting the battery 142, and the charge 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 to power the processor 110, the internal memory 121, the display 194, the camera 193, the wireless communication module 160, and the like. The power management module 141 may also be used to monitor parameters such as battery capacity, battery cycle times, and battery state of health (e.g., leakage, impedance). Alternatively, the power management module 141 may be provided in the processor 110, or the power management module 141 and the charge management module 140 may be provided in the same device.

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, the modem processor, the baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the electronic device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution for wireless communication applied on the electronic device 100, such as at least one of the following: second generation (2) ^th generation, 2G) mobile communication solutions, third generation (3 ^th generation, 3G) mobile communication solution, fourth generation (4 ^th generation, 5G) mobile communication solution, fifth generation (5 ^th generation, 5G) mobile communication solution. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 150 may receive electromagnetic waves from the antenna 1, perform processes such as filtering and amplifying the received electromagnetic waves, and then transmit the electromagnetic waves to a modem processor for demodulation. The mobile communication module 150 may further amplify the signal modulated by the modem processor, and the amplified signal is converted into electromagnetic waves by the antenna 1 and radiated. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be in communication with at least the processor 110 Part of the modules are arranged in the same device.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through audio devices (e.g., speaker 170A, receiver 170B) or displays images or video through display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional module, independent of the processor 110.

Similar to the mobile communication module 150, the wireless communication module 160 may also provide wireless communication solutions applied on the electronic device 100, such as at least one of the following: wireless local area networks (wireless local area networks, WLAN), bluetooth (BT), bluetooth low energy (bluetooth low energy, BLE), ultra Wide Band (UWB), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication (near field communication, NFC), infrared (IR) technologies. The wireless communication module 160 may be one or more devices that integrate 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 transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, frequency modulate and amplify it, and convert the signal into electromagnetic waves to radiate via the antenna 2.

In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150 and antenna 2 of electronic device 100 is coupled to wireless communication module 160 such that electronic device 100 may communicate with networks and other electronic devices via wireless communication techniques. The wireless communication technology may include at least one of the following communication technologies: global system for mobile communications (global system for mobile communications, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, IR technologies. The GNSS may include at least one of the following positioning techniques: global satellite positioning system (global positioning system, GPS), global navigation satellite system (global navigation satellite system, GLONASS), beidou satellite navigation system (beidou navigation satellite system, BDS), quasi zenith satellite system (quasi-zenith satellite system, QZSS), satellite based augmentation system (satellite based augmentation systems, SBAS).

The electronic device 100 may implement display functions through a GPU, a display screen 194, and an application processor. 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 may be used to display images or video. The display 194 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Mini light-emitting diode (Mini LED), a Micro light-emitting diode (Micro LED), a Micro OLED (Micro OLED), or a quantum dot LED (quantum dot light emitting diodes, QLED). In some embodiments, the electronic device 100 may include 1 or N display screens 194, N being a positive integer greater than 1.

The electronic device 100 may implement a photographing function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, an application processor, and the like.

The ISP is used to process data fed back by the camera 193. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and is converted into an image visible to naked eyes. The ISP can carry out algorithm optimization on noise, brightness and color of the image, and can optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into a standard Red Green Blue (RGB), YUV, etc. format image signal. In some embodiments, electronic device 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the electronic device 100 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, or the like.

Video codecs are used to compress or decompress digital video. The electronic device 100 may support one or more video codecs. In this way, the electronic device 100 may play or record video in a variety of encoding formats, such as: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, and MPEG4.

The NPU is a processor which refers to the biological neural network structure, for example, refers to the transmission mode among human brain neurons to rapidly process input information, and can also be continuously self-learned. The NPU may implement functions such as intelligent cognition of the electronic device 100, for example: image recognition, face recognition, speech recognition, and text understanding.

The external memory interface 120 may be used to connect an external memory card, such as a Secure Digital (SD) card, to enable expanding the memory capabilities of the electronic device 100. The external memory card communicates with the processor 110 through an external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

The internal memory 121 may be used to store computer executable program code including instructions. The internal memory 121 may include a storage program area and a storage data area. Wherein the storage program area may store application programs required for at least one function (e.g., a sound playing function and an image playing function) of the operating system. The storage data area may store data (e.g., audio data and phonebooks) created during use of the electronic device 100. Further, the internal memory 121 may include a high-speed random access memory, and may also include a nonvolatile memory such as: at least one disk storage device, a flash memory device, and a universal flash memory (universal flash storage, UFS), etc. The processor 110 performs various processing methods of the electronic device 100 by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.

The electronic device 100 may implement audio functions, such as music playing and recording, through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, an application processor, and the like.

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

The speaker 170A, also referred to as a horn, is used to convert audio electrical signals into sound signals. The electronic device 100 may listen to music or hands-free conversation through the speaker 170A.

A receiver 170B, also referred to as an earpiece, converts the audio electrical signal into a sound signal. When a user uses the electronic device 100 to answer a phone call or voice message, the voice can be answered by placing the receiver 170B close to the ear.

Microphone 170C, also known as a microphone or microphone, is used to convert sound signals into electrical signals. When a user makes a call or transmits voice information, a sound signal may be input to the microphone 170C by sounding near the microphone 170C. The electronic device 100 may be provided with at least one microphone 170C. In other embodiments, the electronic device 100 may be provided with two microphones 170C to achieve a noise reduction function. In other embodiments, the electronic device 100 may also be provided with three, four, or more microphones 170C to perform functions such as identifying the source of sound and directing recordings. The processor 110 may process the electrical signal output by the microphone 170C, for example, the audio module 170 and the wireless communication module 160 may be coupled through a PCM interface, and after the microphone 170C converts the environmental sound into an electrical signal (such as a PCM signal), the electrical signal is transmitted to the processor 110 through the PCM interface; the electrical signal is subjected to volume analysis and frequency analysis from the processor 110 to determine the volume and frequency of the ambient sound.

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

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 may be of various types, such as a resistive pressure sensor, an inductive pressure sensor, or a capacitive pressure sensor. The capacitive pressure sensor may be a device comprising at least two parallel plates with conductive material, and when a force is applied to the pressure sensor 180A, the capacitance between the electrodes changes, and the electronic device 100 determines the strength of the pressure based on the change in capacitance. When a touch operation acts on the display screen 194, the electronic apparatus 100 detects the touch operation 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. In some embodiments, touch operations that act on the same touch location, but at different touch operation strengths, may correspond to different operation instructions. For example: executing an instruction for checking the short message when the touch operation with the touch operation intensity smaller than the first pressure threshold acts on the short message application icon; and executing the instruction of newly creating the short message when the touch operation with the touch operation intensity being larger than or equal to the first pressure threshold acts on the short message application icon.

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-axis, y-axis, and z-axis) 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 can also be used for scenes such as navigation and motion sensing games.

The air pressure sensor 180C is used to measure air pressure. In some embodiments, electronic device 100 calculates altitude from barometric pressure values measured by barometric pressure sensor 180C, aiding in positioning and navigation.

The magnetic sensor 180D includes a hall sensor. The electronic device 100 may detect the opening and closing of the flip cover using the magnetic sensor 180D. In some embodiments, when the electronic device 100 is a flip machine, the electronic device 100 may detect the opening and closing of the flip according to the magnetic sensor 180D. The electronic device 100 may set the characteristics of automatic unlocking of the flip cover according to the detected open-close state of the leather sheath or the open-close state of the flip cover.

The acceleration sensor 180E may detect the magnitude of acceleration of the electronic device 100 in various directions (typically, x-axis, y-axis, and z-axis). The magnitude and direction of gravity may be detected when the electronic device 100 is stationary. The acceleration sensor 180E may also be used to recognize the gesture of the electronic device 100 as an input parameter for applications such as landscape switching and pedometer.

The distance sensor 180F is used to measure a distance. The electronic device 100 may measure the distance by infrared or laser. In some embodiments, for example, in a shooting scene, the electronic device 100 may range using the distance sensor 180F to achieve fast focus.

The proximity light sensor 180G may include, for example, a light-emitting diode (LED) and a light detector, for example, a photodiode. The LED may be an infrared LED. The electronic device 100 emits infrared light outward through the LED. The electronic device 100 detects infrared reflected light from nearby objects using a photodiode. When the reflected light is detected, the electronic device 100 may determine that an object is present nearby. When no reflected light is detected, the electronic device 100 may determine that there is no object nearby. The electronic device 100 can use the proximity light sensor 180G to detect whether the user holds the electronic device 100 close to the ear for talking, so as to automatically extinguish the screen for power saving. The proximity light sensor 180G may also be used for automatic unlocking and automatic screen locking in holster mode or pocket mode.

The ambient light sensor 180L is used to sense ambient light level. The electronic device 100 may adaptively adjust the brightness of the display 194 based on the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust white balance when taking a photograph. Ambient light sensor 180L may also cooperate with proximity light sensor 180G to detect whether electronic device 100 is in a pocket to prevent false touches.

The fingerprint sensor 180H is used to collect a fingerprint. The electronic device 100 may utilize the collected fingerprint feature to perform functions such as unlocking, accessing an application lock, taking a photograph, and receiving an incoming call.

The temperature sensor 180J is for detecting temperature. In some embodiments, the electronic device 100 performs a temperature processing strategy using the temperature detected by the temperature sensor 180J. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, electronic device 100 performs a reduction in the performance of a processor located in the vicinity of temperature sensor 180J in order to reduce power consumption to implement thermal protection. In other embodiments, when the temperature is below another threshold, the electronic device 100 heats the battery 142 to avoid the low temperature causing the electronic device 100 to be abnormally shut down. In other embodiments, when the temperature is below a further threshold, the electronic device 100 performs boosting of the output voltage of the battery 142 to avoid abnormal shutdown caused by low temperatures.

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 180K 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 and at a different location than the display 194.

The bone conduction sensor 180M may acquire a vibration signal. In some embodiments, bone conduction sensor 180M may acquire a vibration signal of a human vocal tract vibrating bone pieces. The bone conduction sensor 180M may also contact the pulse of the human body to receive the blood pressure pulsation signal. In some embodiments, bone conduction sensor 180M may also be provided in a headset, in combination with an osteoinductive headset. The audio module 170 may analyze the voice signal based on the vibration signal of the sound portion vibration bone block obtained by the bone conduction sensor 180M, so as to implement a voice function. The application processor may analyze the heart rate information based on the blood pressure beat signal acquired by the bone conduction sensor 180M, so as to implement a heart rate detection function.

The keys 190 include a power-on key and an volume key. The keys 190 may be mechanical keys or touch keys. The electronic device 100 may receive a key input signal and implement a function related to the case input signal.

The motor 191 may generate vibration. The motor 191 may be used for incoming call alerting as well as for touch feedback. The motor 191 may generate different vibration feedback effects for touch operations acting on different applications. The motor 191 may also produce different vibration feedback effects for touch operations acting on different areas of the display screen 194. Different application scenarios (e.g., time alert, receipt message, alarm clock, and game) may correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

The indicator 192 may be an indicator light, which may be used to indicate a change in state of charge and charge, or may be used to indicate a message, missed call, and notification.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be inserted into the SIM card interface 195 to make contact with the electronic device 100, or may be removed from the SIM card interface 195 to make separation from the electronic device 100. The electronic device 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The same SIM card interface 195 may simultaneously insert multiple cards, which may be of the same type or of different types. The SIM card interface 195 may also be compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as communication and data communication. In some embodiments, electronic device 100 employs an embedded SIM (eSIM) card, which may be embedded in electronic device 100 and not separable from electronic device 100.

The hardware system of the electronic device 100 is described in detail above, and the software system of the electronic device 100 is described below. The software system may employ a layered architecture, an event driven architecture, a microkernel architecture, a micro-service architecture, or a cloud architecture, and the embodiment of the present application exemplarily describes the software system of the electronic device 100.

Fig. 2 is a block diagram illustrating a software configuration of an 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 implementations, the software architecture of the electronic device 100 may be divided into two layers: an application layer 210 and an operating system layer 250, wherein the operating system layer 250 may be an Android operating system.

The application layer 210 may include a series of application packages that may include camera, gallery, chat, map, calendar, music, gallery, talk, navigation, bluetooth, video, etc. applications. In other embodiments of the present application, the electronic device 100 may include more or fewer applications than the application layer shown in fig. 2, and the electronic device 100 may also include entirely different applications.

The operating system layer 250 is an application Framework layer 220, a core library layer 230, and a kernel layer 240, respectively, from top to bottom.

The application framework layer 220 provides application programming interfaces (Application Programming Interface, APIs) and programming frameworks for application programs of the application program layer, including various components and services to support the android development of the developer. The application framework layer 220 includes some predefined functions. As shown in fig. 2, the application framework layer 220 may include an activity management service (actiglymanager service), a display management service (displaymanageservice), an input management service (inputmanager service), a detection processing service, and the like.

The activity management service provides system service for managing activity (activity) running states for Android and is used for managing running states of other components in Android, and in particular, in the application, the activity management service can be used for managing task stacks (stacks for short).

The display management service is used to manage the lifecycle of the display, it decides how to control its logical display according to the currently connected physical display device and/or virtual display device, and sends notifications and the like to the system and applications when the state changes.

The input management service is used to manage input parts of the entire system, including a keyboard, a mouse, a touch screen, and the like.

The detection processing service is used for recording a user click event (for example, package name of an application displayed in a desktop of the electronic device and/or the number of times of clicking the application), recording a life cycle of an interface of the application, and judging whether the interface of the application is abnormally exited after the application in the electronic device is started. And under the condition that the detection processing service determines that the interface of the application is abnormally exited after the application is started, the application is automatically killed, so that the first application runs normally after being restarted. For example, the detection processing service may kill the application by invoking a kill process (killprocess).

The core library layer 230 is the core part of the operating system, and the core library contains 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 core library layer 230 includes a schedule enhancement module, an input/output service, a core service, a Graphics device interface, a Graphics Engine (Graphics Engine) implementing CPU or GPU Graphics processing, and the like. The scheduling enhancement module is used for identifying the state of each application based on the information acquired from the activity management service, the display management service and the input management service so as to further determine the scheduling mode corresponding to each application.

The kernel layer 240 includes a kernel scheduling execution module, a CPU driver, a GPU driver, a display controller driver, and the like. Each driver is used to abstract the hardware to hide a particular channel of the hardware so that the application can access (or call) the hardware. In the application, the internal scheduling execution module schedules the application based on the input of the scheduling enhancement module.

It should be understood that the software architecture block diagram shown in fig. 2 is merely an example, and other software architectures may alternatively be used, such as having different layers with respect to the software architecture of fig. 2, and different naming and/or placement positions of functional modules with respect to fig. 2, which is not limited by the present application.

Next, based on the software architecture shown in the embodiment of fig. 2, an exemplary diagram of a software architecture to which the method for processing abnormal exit is applied according to the embodiment of the present application is shown in fig. 3.

As shown in fig. 3, the application layer of the electronic device includes a desktop launcher and at least one application. The application framework layer of the electronic device includes input management services, activity management services, and detection processing services. It should be appreciated that the application framework layer shown in fig. 3 corresponds to the application framework layer shown in fig. 2, and that the at least one application shown in fig. 3 may be any one of the applications (e.g., camera, calendar, gallery, etc. applications) shown in fig. 2.

After the input detection service detects a user operation event (e.g., an operation to open a certain application), the input detection service transmits the user operation event to the desktop launcher. The user operation event is used to request that an interface of an application in the electronic device be displayed on a display screen of the electronic device. For example, the user operation event may be, but is not limited to, an operation of a user clicking or double clicking an application icon of an application in a desktop of the electronic device.

After the desktop initiator receives the user operation event, the desktop initiator notifies the activity management service to start the application in the electronic device clicked by the user operation event. Optionally, the desktop initiator further records identification information of an application corresponding to the user operation event. The identification information of the application is used to identify the application, for example, the identification information may be a package name of the application and/or a UID of the application.

In the case that the activity management service starts the application clicked by the user operation event, the electronic device will display the interface of the application, and at the same time, the activity management service will also acquire the time of creating the interface and the time of destroying the interface. Thereafter, the activity management service will send the 2 times obtained to the detection processing service.

The detection processing service can obtain the life cycle of the interface according to the received 2 moments associated with the interface. And then, detecting whether the processing service meets a certain condition according to the life cycle of the interface and the interface displayed after the electronic equipment displays the interface of the application, so as to determine the problem that the interface of the application is abnormally exited after the application is started. In the event that the detection processing service determines that an abnormal exit of the interface of the application has occurred after the application is started, the application is automatically killed (kill). For example, the detection processing service may kill the application by invoking a kill process.

Optionally, in the case where the detection processing service kills an application that has an abnormal exit, the activity management service may also restart the application so that the application can run normally after restarting.

It should be understood that fig. 3 is only illustrative, and does not limit any software architecture applicable to the method for processing application exception exit according to the embodiment of the present application.

As described above, in order to solve the problems existing in the conventional technology, the method for processing the application exception exit provided by the embodiment of the present application adopts the following technical scheme: the method comprises the steps that the electronic equipment obtains interface life cycles of N interfaces, which are displayed in response to N opening operations of a first application, the N opening operations are in one-to-one correspondence with the N interfaces, the corresponding interfaces are displayed on the basis of each opening operation, the interfaces are flashed back to a main interface of the electronic equipment after the corresponding interfaces are displayed, the interface life cycle of each interface is a time period between the moment when the electronic equipment creates each interface and the moment when the electronic equipment destroys each interface, and N is a positive integer; and under the condition that the interface life cycles of the N interfaces do not exceed the preset life cycle, the electronic equipment automatically kills the first application, so that the first application can normally operate after being restarted. The method can solve the problem that the interface of the application is abnormally exited after the application is started under the condition that the user does not need to participate, simplifies the user operation and improves the user experience.

Next, a method for processing application exception exit according to an embodiment of the present application will be described in detail with reference to fig. 4 to 8.

Fig. 4 is a schematic diagram of a processing method for application exception exit according to an embodiment of the present application. The method for processing the application exception exit provided by the embodiment of the application can be executed by the electronic equipment. It is understood that the electronic device may be implemented as software, or as a combination of software and hardware. By way of example, the electronic device in the embodiments of the present application may be, but is not limited to, the electronic device 100 shown in fig. 1. As shown in fig. 4, the processing method for application exception exit provided in the embodiment of the present application includes S410 and S420.

S410, the electronic device obtains interface life cycles of N interfaces displayed in response to N opening operations of the first application, the N opening operations are in one-to-one correspondence with the N interfaces, the corresponding interfaces are displayed based on each opening operation, the interfaces flash back to a main interface of the electronic device after the corresponding interfaces are displayed, the interface life cycle of each interface is a time period between the moment when the electronic device creates each interface and the moment when the electronic device destroys each interface, and N is a positive integer.

In the embodiment of the application, any one of the N opening operations is used for requesting the operation of displaying the application interface of the first application on the display screen of the electronic device.

In some implementations, the first interface presented after the electronic device opens the first application is an application interface of the first application, i.e., in such a scenario, the electronic device does not have an advertisement interface after the first application is opened. In this implementation, an interface corresponding to an open operation may be an application interface of the first application. For example, N interfaces corresponding to the N opening operations in S410 may be application interfaces of the first application.

For example, taking an electronic device as a mobile phone, before the electronic device responds to any one of N opening operations, the content displayed on the display screen of the electronic device may be as shown in fig. 5A, where the main interface of the electronic device includes a plurality of application icons of a plurality of applications. Thereafter, in response to the user clicking on the application icon of the memo 511 in the interface 510 (i.e., the main interface of the electronic device) as illustrated in fig. 5A, the content displayed by the display screen of the electronic device may be the content of the interface 520 (i.e., the interface of the memo application) as illustrated in fig. 5B.

In other implementations, the first interface presented after the electronic device opens the first application is an advertisement interface, and the second interface presented after browsing the advertisement interface for a predetermined period of time is an application interface of the first application. In this implementation, an interface corresponding to an open operation may be an advertisement interface of the first application. For example, N interfaces corresponding to the N opening operations in S410 may be advertisement interfaces of the first application. For example, some of the N interfaces corresponding to the N opening operations in S410 may be advertisement interfaces of the first application, and the remaining interfaces of the N interfaces except for some interfaces may be application interfaces of the first application.

For example, taking an electronic device as a mobile phone, before the electronic device responds to any one of N opening operations, the content displayed on the display screen of the electronic device may be as shown in fig. 5A, where the main interface of the electronic device includes a plurality of application icons of a plurality of applications. Thereafter, in response to the user clicking on the application icon of the memo 511 in the interface 510 (i.e., the main interface of the electronic device) as illustrated in fig. 5A, the content displayed by the display screen of the electronic device may be the content of the interface 530 (i.e., the advertisement interface of the memo application) as illustrated in fig. 5C.

In the embodiment of the present application, the continuity of the N opening operations is not particularly limited. In some implementations, the N open operations are consecutive N operations detected by the electronic device, in which the electronic device does not detect other operations for a period of time from detection of the 1 st open operation to the nth open operation. In other implementations, the N open operations are non-consecutive N operations detected by the electronic device, and in such implementations, the electronic device detects other operations within a period of time from detecting the 1 st open operation to the nth open operation. For example, taking N equal to 3 as an example, the electronic device may also detect an open operation for an application other than the first application within a period of time from detection of the 1 st open operation to the 3 rd open operation.

In the embodiment of the present application, N is a value with an upper limit, that is, N is not an infinite value, and the value of N is not specifically limited. In some implementations, N is a positive integer, and the value of N may be set according to actual requirements. For example, N may be set equal to 1, 2, or 3, or the like, according to the user's use requirement. In other implementations, N is a preset value, where N may be a predefined preset value, a dynamically adjusted preset value, or the like. For example, N may be a preset value predefined by the user, which is 2 or 3 or the like.

In the embodiment of the present application, the operation types of the N opening operations are not particularly limited. For example, any of the N open operations may be one of the following: single click operation by a user, multiple click operations by a user, or mouse button operations, etc.

In the embodiment of the application, the main interface of the electronic device is an interface at least comprising an application icon of the first application. The main interface of the electronic device may also be referred to as a desktop initiator of the electronic device. Optionally, in the case that other applications than the first application are also installed in the electronic device, the main interface of the electronic device may further include an interface of an application icon of the other applications. For example, taking the example that the first application is a memo application, the main interface of the electronic device may refer to the interface 510 shown in fig. 5A, where the interface 510 includes application icons of the memo application and application icons of other multiple applications.

In the embodiment of the application, the corresponding interface is displayed based on each opening operation, and the electronic equipment is flashed back to the main interface of the electronic equipment after the corresponding interface is displayed. It is understood that the electronic device does not detect and execute other operations during the period from the time when the electronic device displays the interface corresponding to each opening operation to the time when the interface corresponding to each opening operation is displayed and the interface is flashed back to the main interface of the electronic device. That is, the electronic device is a process of automatically flashing back from displaying the interface corresponding to each opening operation to flashing back to the main interface of the electronic device. It can also be understood that, in the process that the electronic device displays a corresponding interface based on each opening operation and the electronic device flashes back to the main interface of the electronic device after displaying the corresponding interface, the code logic called by the first application of the electronic device is normal code logic, that is, the electronic device cannot determine whether the interface of the first application displayed based on each opening operation is abnormally exited by detecting the called code.

In the embodiment of the present application, an activity is a visual user interface that is responsible for creating a screen window and placing User Interface (UI) components for user interaction. That is, the N interfaces are in one-to-one correspondence with the N activites, and each activitiy is used for displaying a corresponding interface on a display screen of the electronic device. Thus, the interface lifecycle of each interface is the period of time between the time when the electronic device created each interface to the time when the electronic device destroyed each interface. The time at which the electronic device creates each interface refers to the time at which the electronic device creates (create) the activity associated with each interface. The time when the electronic device destroys each interface refers to the time when the activity associated with each interface is destroyed (ondestor), or the time when the activity associated with each interface is stopped (ondestop). It can be appreciated that the time when the electronic device destroys each interface is earlier than or equal to the time when the electronic device flashes back to the main interface of the electronic device after displaying the corresponding interface.

Illustratively, table 1 below shows the method invoked by an electronic device in creating an activity to destroying an activity.

TABLE 1

In the embodiment of the present application, the manner of obtaining the time of creating each interface and the time of destroying each interface by the electronic device is not particularly limited. By way of example, the electronic device may obtain, by way of dotting, the time at which each interface was created and the time at which each interface was destroyed. Specifically, the electronic device adds a dotting code 1 in an event of creating the activity associated with each interface, and obtains the moment of creating the activity associated with each interface through the dotting code 1; and adding a dotting code 1 into the event of destroying the activity associated with each interface by the electronic equipment, and obtaining the moment of destroying the activity associated with each interface through the dotting code 1.

Optionally, before the electronic device performs S410, the following steps may be further performed: n opening operations are detected; in response to detecting each open operation, performing each open operation; and responding to executing each opening operation, displaying an interface corresponding to each opening operation, and backing to a main interface of the electronic equipment after displaying the interface corresponding to each opening operation. The time at which the N opening operations are detected by the electronic device is not particularly limited. For example, N opening operations and N detection times are in one-to-one correspondence, each detection time being a time when the electronic device detects the corresponding opening operation, and the N detection times are all different.

Optionally, the electronic device may further record the number of times the electronic device starts the first application, but the implementation manner of recording the number of times the electronic device starts the first application is not specifically limited, and may be set according to an actual scene.

Illustratively, the electronic device records the number of starts to launch the first application by performing the steps of: the electronic apparatus increases the value of a counter for recording the number of starts of the first application by 1 in response to each of the N opening operations. In the above implementation manner, the electronic device may learn, through the value of the counter, the number of times the current electronic device starts the first application, so that the electronic device may determine, through whether the value of the counter is equal to the value of N, whether the current electronic device has successfully detected N opening operations.

S420, the electronic device automatically kills the first application under the condition that the interface life cycles of the N interfaces do not exceed the preset life cycle, so that the first application can normally run after being restarted.

The preset life cycle is a preset time period, and the length of the preset time period is not particularly limited, and can be set according to actual application requirements. For example, the preset lifecycle may be, but is not limited to, 500 milliseconds (ms), 600ms, or the like.

Killing the first application refers to terminating the process of the first application, thereby freeing up memory space of the electronic device that is occupied by the process of the first application.

The interface life cycle of each of the N interfaces does not exceed the preset life cycle, which means that the interface life cycle of each of the N interfaces does not exceed the preset life cycle.

The electronic device displays a corresponding interface based on each opening operation, and flashes back to the main interface of the electronic device after displaying the corresponding interface, and the interface life cycle of the interface corresponding to each opening operation does not exceed the preset life cycle.

In the embodiment of the present application, the implementation manner of automatically killing the first application by the electronic device is not particularly limited. For example, if the life cycle of the interfaces of the N interfaces does not exceed the preset life cycle, the electronic device automatically kills the first application, including: and under the condition that the interface life cycles of the N interfaces do not exceed the preset life cycle, the electronic equipment invokes the killing process to automatically kill the first application. As another example, the electronic device may also kill the first application based on methods of killing one application in conventional techniques.

In the embodiment of the application, after the electronic equipment determines that the interface life cycles of N interfaces corresponding to N opening operations of the first application exceed the preset life cycle, and the corresponding interfaces are displayed based on each opening operation and the corresponding interfaces are displayed to flash back to the main interface of the electronic equipment, the electronic equipment can also start the first application after automatically killing the first application so as to better meet the user requirements and improve the user experience.

In some implementations, after the electronic device automatically kills the first application, the method further includes: the electronic device automatically starts the first application so that the first application normally operates after restarting.

In other implementations, after the electronic device automatically kills the first application, the method further includes: and the electronic equipment responds to the new opening operation of the user, and starts the first application so that the first application runs normally after being restarted.

Optionally, the value of the counter in the electronic device for recording the number of times of starting the first application is equal to N, and the electronic device may further execute the following steps after executing S420: the value of the counter is cleared.

It should be understood that the method for processing the application exception exit shown in fig. 4 is merely illustrative, and does not limit the method for processing the application exception exit provided by the present application.

In the embodiment of the application, when the electronic equipment displays the corresponding interface based on each opening operation, and the corresponding interface is displayed to flash back to the main interface of the electronic equipment, and the life cycle of the interfaces of the N interfaces corresponding to the N opening operations does not exceed the preset life cycle, the electronic equipment automatically kills the first application, so that the method can solve the problem that the interface of the application is abnormally exited after the application is started without participation of a user, simplify the user operation, and improve the user experience.

In the following, an electronic device having the structure shown in fig. 1 and fig. 3 will be taken as an example, and another method for processing abnormal exit by using an embodiment of the present application will be specifically described with reference to fig. 6. It will be understood that the processing method of application exception exit described in fig. 6 is a specific example of the processing method of application exception exit described in fig. 4, and the method described in fig. 6 is only illustrative, and does not constitute any limitation on the processing method of application exception exit provided in the present application.

Fig. 6 is a schematic diagram of another method for processing application exception exit according to an embodiment of the present application. In the embodiment of the application, the electronic equipment for executing the processing method of the abnormal exit of the application comprises an operating system layer, wherein the application layer in the operating system layer comprises an application program 1 and a desktop starter, and the application framework layer in the operating system layer comprises an input management service, an activity management service and a detection processing service. The method illustrated in fig. 6 includes S601 to S607, by way of example. Next, S601 to S607 will be described in detail.

S601, the input management service of the electronic device sends each opening operation to a desktop starter of the electronic device when detecting each opening operation in N opening operations, wherein N is a positive integer. Accordingly, the desktop initiator receives each open operation from the input management service.

In S601, N opening operations and N interfaces are in one-to-one correspondence. The electronic device displays a corresponding interface based on each of the N opening operations and flashes back to a main interface of the electronic device after displaying the corresponding interface. The interface lifecycle of each of the N interfaces refers to a time period between a time when the activity management service of the electronic device creates each interface and a time when the activity management service destroys each interface.

The N opening operations, the N interfaces, and the interface life cycles of each of the N interfaces in S601 are the same as the N opening operations, the N interfaces, and the interface life cycles of the N interfaces in S410, respectively, and details not described herein may be referred to in the related description in S410.

S602, in a case where the desktop initiator receives each opening operation, the desktop initiator notifies the activity management service of the electronic device to execute each opening operation. Accordingly, the activity management service receives notification from the desktop initiator to perform each open operation.

The notification timing of the desktop initiator to notify the activity management service to perform each opening operation is not particularly limited. For example, after the desktop initiator receives each open operation, the desktop initiator immediately notifies the activity management service to perform each open operation. For another example, after the desktop initiator receives each open operation, the desktop initiator notifies the campaign management service to perform each open operation after a short period of time.

S603, the activity management service of the electronic device performs each opening operation.

The activity management service sequentially performs each of the N open operations according to a detection time at which the input management service detects the N open operations. For example, taking N opening operations as an example, the opening operation detected at time 1 and the opening operation detected at time 2, the time 1 is earlier than the time 2, in this scenario, the activity management service performs the opening operation detected at time 1 first and then performs the opening operation detected at time 2.

S604, the activity management service obtains the time when the activity management service created each interface and the time when the electronic device destroyed each interface.

The activity management service performs S604 described above, and the principle of the electronic device described in S410 that the electronic device obtains the time when the electronic device creates each interface and the time when the electronic device destroys each interface is the same, except that the execution bodies of S604 and S410 are different, and details not described in detail herein may refer to the related description in S410 above.

S605, the activity management service transmits, to the detection processing service of the electronic device, the time at which each interface is created and the time at which each interface is destroyed by the electronic device. Accordingly, the detection processing service receives the time of creating each interface from the activity management service and the time of destroying each interface by the electronic device.

S606, the detection processing service obtains the interface life cycle of each interface according to the time when the electronic device creates each interface and the time when the electronic device destroys each interface, so as to obtain the interface life cycles of N interfaces.

Optionally, the detection processing service may also record the number of times the electronic device starts the first application, but the implementation manner of recording the number of times the detection processing service starts the first application is not specifically limited, and may be set according to the actual situation.

For example, the detection processing service records the number of starts of starting the first application by performing the steps of: the input management service sends each opening operation to the desktop manager in response to detecting each opening operation of the N opening operations; the desktop manager sends the identification information of the first application corresponding to each opening operation to the detection processing service; the detection processing service increases the value of a counter for recording the number of starts of the first application by 1 in response to receiving the identification information of the first application corresponding to each opening operation. The identification information of the first application is used for identifying the first application, and the identification information of the first application is not particularly limited. For example, the identification information of the first application may be, but is not limited to, a package name of the first application or a UID of the first application.

As another example, the detection processing service records the number of starts to launch the first application by performing the steps of: the detection processing service increases the value of a counter for recording the number of starts of the first application by 1 in response to each of the N opening operations. In the above implementation manner, the number of times that the current detection processing service starts the first application may be known by the detection processing service through the value of the counter, so that the detection processing service may determine whether the current detection processing service has successfully detected N open operations through whether the value of the counter is equal to the value of N.

S604 to S606 are one implementation manner of obtaining the interface life cycles of the N interfaces, where after the detection processing service obtains the time of creating the interface and the time of destroying the interface, the detection processing service obtains the interface life cycle of the interface according to the time of creating the interface and the time of destroying the interface.

Optionally, the steps S604 to S606 may be replaced by the following steps: the method comprises the steps that an activity management service obtains the moment when the activity management service creates each interface and the moment when the electronic equipment destroys each interface; the activity management service obtains the interface life cycle of each interface according to the time when the electronic equipment creates each interface and the time when the electronic equipment destroys each interface; the activity management service sends the interface lifecycle of each interface to the detection processing service so that the detection processing service obtains the interface lifecycles of the N interfaces. In this implementation, after the activity management service obtains the time of creating the interface and the time of destroying the interface, the activity management service obtains the interface life cycle of the interface according to the time of creating the interface and the time of destroying the interface. Thereafter, the campaign management service sends the interface lifecycle of the interface to the detection processing service, such that the detection processing service obtains the interface lifecycle of the interface.

S607, the detection processing service automatically kills the first application under the condition that the life cycle of the N interfaces does not exceed the preset life cycle.

The detection processing service performs the same principle as the electronic device performs the above S420S 607, and details not described here in detail may be referred to the relevant description in S420 above.

Optionally, the value of the counter for recording the number of starts of the first application in the detection processing service is equal to N, and the detection processing service may further perform the following steps after performing S607 as described above: the value of the counter is cleared. The detection processing service is a service application within the electronic device, and the counter for recording the number of starts of the first application may be stored in a memory space allocated to the detection processing service by the electronic device.

It should be understood that the method for processing the application exception exit shown in fig. 6 is merely illustrative, and does not limit the method for processing the application exception exit provided by the present application.

In the embodiment of the application, the electronic equipment automatically kills the first application under the conditions that the corresponding interface is displayed on the basis of each opening operation, the corresponding interface is displayed and the interface is flashed back to the main interface of the electronic equipment, and the interface life periods of N interfaces corresponding to N opening operations do not exceed the preset life period, so that the method can solve the problem that the interface of the application is abnormally exited after the application is started without participation of a user, simplify the user operation and improve the user experience.

In the following, an electronic device having the structure shown in fig. 1 and fig. 3 will be taken as an example, and in conjunction with fig. 7, a further processing method for application exception exit provided in an embodiment of the present application will be specifically described. It will be understood that the processing method of application exception exit described in fig. 7 is a specific example of the processing method of application exception exit described in fig. 4, and the method described in fig. 7 is only illustrative, and does not constitute any limitation on the processing method of application exception exit provided in the present application.

Fig. 7 is a schematic diagram of another method for processing an application exception exit according to an embodiment of the present application. In the embodiment of the application, the electronic equipment for executing the processing method of the abnormal exit of the application comprises an operating system layer, wherein the application layer in the operating system layer comprises an application program 1 and a desktop starter, and the application framework layer in the operating system layer comprises an input management service, an activity management service and a detection processing service. The method illustrated in fig. 7 includes S701 to S712, by way of example. Next, S701 to S712 will be described in detail.

S701, the input management service acquires a user click event.

The user click event in S701 described above is used to request that the interface of the application 1 of the electronic device be displayed on the display screen of the electronic device. It will be appreciated that the user click event described above is a specific example of an open operation in the method provided in fig. 4 described above. The above-described application program 1 is a specific example of the first application in the method provided in fig. 4 described above.

In the embodiment of the present application, the user click event may be an event that the user clicks an application icon of the application 1 in a desktop initiator of the electronic device, where the desktop initiator of the electronic device includes at least one icon of the application, and the icon of the at least one application includes an application icon of the application 1.

In the embodiment of the application, the input management service can sense the event that the user clicks the electronic equipment, and the input management service of the electronic equipment acquires the user click event, which comprises the following steps: in response to a user clicking on a desktop initiator of the electronic device, the input manager service obtains a user click event.

S702, the input management service sends a user click event to the desktop initiator. Accordingly, the desktop initiator receives a user click event from the input management service.

S703, in a case where the user click event is that the user clicks an icon of the application 1 in the desktop launcher of the electronic device, the desktop launcher determines to launch the application 1.

In the embodiment of the application, when the user clicks the icon of the application program in the desktop launcher of the electronic device, the desktop launcher determines that the corresponding application program needs to be launched. In the case where the user click event is a click of an icon (e.g., wallpaper) of a non-application in the desktop launcher of the electronic device, the desktop launcher determines that the application need not be launched, i.e., in such an implementation, S704 to S712 below need not be performed either.

S704, the desktop launcher notifies the activity management service to launch application 1. Accordingly, the activity management service receives notification of the start application 1 from the desktop launcher.

S705, the activity management service starts the application 1, and obtains the time 1 of creating the interface 1 and the time 2 of destroying the interface 1, the interface 1 being the interface displayed after the application 1 is started.

Interface 1 in S705 above is a specific example of one of N interfaces in the method provided in fig. 4 above.

In the embodiment of the application, an activity is a visual user interface responsible for creating a screen window and placing UI components for user interaction. The method called by the campaign management service when creating the campaign to destroy the campaign may be found in the various methods shown in table 1 above. Therefore, in the embodiment of the present application, the time 1 when the interface 1 is created may be understood as the time when the (create) activity1 is created, where the activity1 is used to display the interface 1 on the display screen of the electronic device. The time 2 of destroying the interface 1 can be understood as the time of destroying (ondestor) activity1 or the time of stopping (ondestop) activity 1.

The activity management server may obtain time 1 and time 2 by dotting. In some implementations, the activity management service adds a dotting code 1 in the event of creating activity1, and obtains the moment of creating activity1 through the dotting code 1; and adding a dotting code 1 in the event of destroying the activity1, and obtaining the moment of destroying the activity1 through the dotting code 1.

S706, the activity management service transmits time 1 of creating the interface 1 and time 2 of destroying the interface 1 to the detection processing service. Accordingly, the detection processing service receives the time 1 of creating the interface 1 and the time 1 of destroying the interface 1 from the activity management service.

S707, the detection processing service determines the time from time 2 to time 1 as the life cycle of the interface 1.

After the activity management service performs S706 and the detection processing service performs S707 described above, that is, the activity management service obtains the time 1 and the time 2, the 2 times are sent to the detection processing service, so that the detection processing service determines the life cycle of the interface 1 according to the 2 times.

Optionally, the activity management service executing the above S706 and the detection processing service executing the above S707 may be replaced by the following steps: the activity management service determines the period from the time 2 to the time 1 as the life cycle of the interface 1; the campaign management service sends the lifecycle of the interface 1 to the detection processing service so that the detection processing service receives the lifecycle of the interface 1 from the campaign management service.

S708, the detection processing service determines whether the life cycle of the interface 1 exceeds 500 ms.

In the embodiment of the application, if the detection processing service judges that the life cycle of the interface 1 exceeds 500ms, the phenomenon of abnormal exit does not occur when the desktop of the electronic equipment displays the interface 1; if the detection processing service determines that the life cycle of the interface 1 does not exceed 500ms, it is considered that there may be a problem of abnormal exit when the desktop of the electronic device displays the interface 1, and in this implementation, the detection processing service needs to perform further determination to determine whether there is actually a problem of abnormal exit of the interface 1 displayed on the desktop of the electronic device if the life cycle of the interface 1 does not exceed 500 ms.

The detection processing service performs S708 described above, that is, the detection processing service determines whether the life cycle of the interface 1 exceeds 500ms, including: in the case where the detection processing service judges that the life cycle of the interface 1 does not exceed 500ms, S709 to S712 are continued to be executed; in the case that the detection processing service determines that the life cycle of the interface 1 exceeds 500ms, that is, the problem of abnormal exit does not occur when the desktop of the electronic device displays the interface 1, no processing is executed later, that is, the processing flow is ended.

It should be understood that 500ms in S708 is a preset life cycle, and may be set according to practical situations. For example, the value of the one preset life cycle may be determined according to the processor performance of the electronic device. For another example, the value of the preset life cycle may be determined according to the memory size of the electronic device.

S709, the detection processing service requests the activity management service to acquire the name of the interface 2 displayed on the desktop of the electronic device at the current moment.

The current time is the next time after time 2. That is, interface 2 is the first interface displayed on the desktop of the electronic device after the desktop of the electronic device exits from the state of display interface 1.

In the embodiment of the present application, the interface 2 and the interface 1 are two different interfaces, and the interface 2 is not particularly limited. For example, interface 2 may be an interface of application 1, in which case, after the desktop of the electronic device exits from displaying one interface of application 1 (i.e., interface 1), the desktop of the electronic device displays another interface of application 1 (i.e., interface 2). As another example, interface 2 may be a desktop initiator of an electronic device, in which case the desktop of the electronic device displays the desktop initiator after the desktop of the electronic device exits from displaying one of the interfaces of application 1 (i.e., interface 1).

S710, the activity management service transmits the name of the interface 2 to the detection processing service.

The detection processing service executing S709 described above and the activity management service executing S710 described above are steps in which the detection processing service actively requests the acquisition of the name of the interface 2 from the activity management service.

Optionally, the activity management service may also send the name of the interface 2 to the detection processing service when executing S706 described above. Therefore, the step S706 may be replaced by the following steps: the activity management service sends the name of the interface 2, the time 1 of creation of the interface 1, and the time 2 of destruction of the interface 1 to the detection processing service.

S711, the detection processing service determines whether the interface 2 is a desktop initiator.

In the case where the interface 2 in the above S711 is a desktop initiator, the interface 2 in the above S711 may be understood as a specific example of a main interface of the electronic device in the method provided in the above fig. 4.

The detection processing service executes S711, that is, if the life cycle of the interface 1 does not exceed 500ms, the detection processing service determines whether the interface 2 displayed on the desktop of the electronic device is a desktop initiator after the desktop of the electronic device exits from the state of the display interface 1.

In the embodiment of the application, under the condition that the life cycle of the interface 1 does not exceed 500ms, the detection processing service judges that the interface 2 displayed on the desktop of the electronic device is a desktop starter after the desktop of the electronic device exits from the state of the display interface 1, and considers the problem of abnormal exit after the application 1 is started; under the condition that the life cycle of the interface 1 does not exceed 500ms, the detection processing service judges that the interface 2 displayed on the desktop of the electronic device is not a desktop starter after the desktop of the electronic device exits from the state of the display interface 1, and considers that the problem of abnormal exit does not occur after the application 1 is started.

The detection processing service executes S711, that is, the detection processing service determines whether the interface 2 is a desktop initiator, including: if the detection processing service determines that the interface 2 is a desktop starter, S712 is continued; in the case that the detection processing service determines that the interface 2 is not a desktop starter, that is, the phenomenon of abnormal exit does not occur when the desktop of the electronic device displays the interface 1, no processing is executed later, that is, the processing flow is ended.

S712, the detection processing service invokes the killing process to automatically kill the application 1, so that the application 1 runs normally after restarting.

In the embodiment of the present application, killing the application 1 refers to terminating the process of the application 1, thereby releasing the memory space of the electronic device occupied by the process of the application 1.

The detection processing service executes S712, that is, in the case that the life cycle of the interface 1 of the application 1 is not more than 500ms and the interface 2 is a desktop starter of the electronic device, the killing process is invoked to automatically kill the application 1, so that the application 1 runs normally after restarting. That is, in the above implementation manner, in the case where the detection processing service determines that the problem of abnormal exit occurs after the application 1 is started, the detection processing service may call the killing process to automatically kill the application 1, so that the application 1 can be normally operated after the application 1 is restarted.

The detection processing service executes S712 described above, that is, the detection processing service invokes the killing process to automatically kill the application 1, including: the detection processing service acquires a process identifier of a process of the application program 1; the detection processing service calls the killing process to automatically kill the process of the application program 1 corresponding to the process identification.

Optionally, after the detection processing service performs S712 described above, the following steps may also be performed: in response to detecting that the processing service invokes the killing process to automatically kill the application 1, the invoking the starting process restarts the application 1 so that the application 1 operates normally after restarting.

It should be understood that the method for processing the application exception exit shown in fig. 7 is merely illustrative, and does not limit the method for processing the application exception exit provided by the present application. For example, the preset life cycle 500ms may be set according to the performance of the processor of the electronic device, where the value of the preset life cycle is smaller when the performance of the processor of the electronic device is higher; under the condition that the performance of a processor of the electronic equipment is low, the value of the preset life cycle is large.

In the embodiment of the application, whether the interface 1 of the display application program 1 of the electronic device has abnormal exit after the first application is started is determined according to the life cycle of the interface 1 corresponding to the detected user click event and whether the interface 2 corresponding to the user click event meets a certain condition. In the event that it is determined that there is an abnormal exit of the interface 1 of the electronic device display application 1 after the start of the application 1, the application 1 is automatically killed. In the processing process, the electronic equipment does not need to be restarted manually or the application program 1 does not need to be killed manually by a user, so that the user experience is optimized. Meanwhile, under the condition that the interface 1 of the application program 1 is abnormally exited after the application program 1 is started, the system of the electronic equipment automatically kills the application program 1, so that the subsequent application program 1 can normally run after being restarted. In summary, the method provided by the embodiment of the application can solve the problem that the interface of the application frequently exits abnormally after the application is started without the participation of the user, simplifies the user operation and improves the user experience.

In the following, an electronic device having the structure shown in fig. 1 and fig. 3 will be taken as an example, and in conjunction with fig. 8, a further processing method for application exception exit provided in an embodiment of the present application will be specifically described. It will be understood that the processing method of application exception exit described in fig. 8 is a specific example of the processing method of application exception exit described in fig. 4, and the method described in fig. 8 is only illustrative, and does not constitute any limitation on the processing method of application exception exit provided in the present application.

Fig. 8 is a schematic diagram of another method for processing an application exception exit according to an embodiment of the present application. In the embodiment of the application, the electronic equipment for executing the processing method of the abnormal exit of the application comprises an operating system layer, wherein the application layer in the operating system layer comprises an application program 1 and a desktop starter, and the application framework layer in the operating system layer comprises an input management service, an activity management service and a detection processing service. The method illustrated in fig. 8 includes S801 to S816, by way of example. Next, S801 to S816 will be described in detail.

S801, the input management service acquires a user click event.

The principle of the input management service acquiring the user click event in S801 is the same as that of the input management service acquiring the user click event in S701, and details not described in detail herein may be referred to in the related description in S701.

S802, the input management service sends a user click event to the desktop initiator. Accordingly, the desktop initiator receives a user click event from the input management service.

S803, in a case where the user click event is that the user clicks an icon of the application 1 in the desktop launcher of the electronic device, the desktop launcher determines to launch the application 1.

S804, the desktop launcher notifies the activity management service to launch the application 1. Accordingly, the activity management service receives notification of the start application 1 from the desktop launcher.

The respective modules in the electronic device perform the principles of S801 to S804 described above, and are the same as those of S701 to S704 described above, and details not described here in detail may be referred to the descriptions of S701 to S704 described above.

S805, the desktop initiator transmits the package name of the application 1 to the detection processing service. Accordingly, the detection processing service receives the package name of the application 1 from the desktop initiator.

In the embodiment of the application, each application program has a package name, and the package names of different application programs are different, namely, the inclusion of each application program is used for uniquely identifying each application program. Therefore, the package name of the application 1 in S805 described above is used to identify the application 1.

Alternatively, the packet name of the application 1 may be replaced by the UID of the application 1, which is not limited specifically. It will be appreciated that a UID is a unique identification number assigned to an application by the system when the application is running in the system, i.e., the UIDs of different applications are different.

Optionally, the package name of the application 1 may be replaced by the following: the package name of application 1 and the UID of application 1.

S806, the detection processing service increments the value of the counter 1 for recording the number of starts of the application 1 by 1.

Counter 1 in S806 described above is a specific example of a counter in the method provided in fig. 4 described above.

In the embodiment of the present application, the value of the counter 1 of the detection processing service record before the detection processing service is executed S806 is not particularly limited. For example, the value of the counter 1 is 0 before the detection processing service performs S806, and the value of the counter 1 is 1 after the detection processing service performs S806. For another example, the value of the counter 1 is 1 before the detection processing service performs S806, and the value of the counter 1 is 2 after the detection processing service performs S806.

In the embodiment of the present application, the value of the counter 1 is M before the detection processing service executes S806, and in the embodiment of the present application, the m+1st time starts the application 1, where M is an integer greater than or equal to 0.

For example, in the case where the value of the counter 1 is 0 before the detection processing service executes S806, the application 1 is started for the first time in the embodiment of the present application. For another example, in the case where the value of the counter 1 is 1 before the detection processing service executes S806, the application 1 is started 2 nd time in the embodiment of the present application.

Alternatively, when the detection processing service performs S806 described above, the detection processing service may also record the packet name of the application 1.

In the embodiment of the present application, the packet name of the application 1 and the recording form of the counter 1 recorded in the detection processing service are not particularly limited. For example, the detection processing service may use the packet name of the application 1 and the numerical value of the counter 1 recorded in text form. As another example, the detection processing service may record the packet name of the application 1 and the value of the counter 1 using a two-dimensional data table.

S807, the activity management service starts the application 1, and acquires the time 1 at which the interface 1 is created and the time 2 at which the interface 1 is destroyed, the interface 1 being the interface displayed after the application 1 is started.

The principle of the activity management service executing the above S807 is the same as that of the activity management service executing the above S705, and details not described here in detail can be found in the related description in the above S705.

S808, the activity management service transmits time 1 at which the interface 1 is created and time 2 at which the interface 1 is destroyed to the detection processing service. Accordingly, the detection processing service receives the time 1 of creating the interface 1 and the time 2 of destroying the interface 1 from the activity management service.

S809, the detection processing service determines the time from time 2 to time 1 as the life cycle of the interface 1.

After the activity management service performs S808 and the detection processing service performs S809 described above, that is, the activity management service obtains the time 1 and the time 2, the 2 times are sent to the detection processing service, so that the detection processing service determines the life cycle of the interface 1 according to the 2 times.

Optionally, the activity management service performing the above S808 and the detection processing service performing the above 809 may be replaced with the following steps: the activity management service determines the period from the time 2 to the time 1 as the life cycle of the interface 1; the campaign management service sends the lifecycle of the interface 1 to the detection processing service so that the detection processing service receives the lifecycle of the interface 1 from the campaign management service.

S810, the detection processing service determines whether the life cycle of the interface 1 exceeds 500ms.

In the embodiment of the application, if the life cycle of the detection processing service interface 1 exceeds 500ms, the phenomenon that the desktop of the electronic device is abnormally exited when the desktop of the electronic device displays the interface 1 can be considered; if the life cycle of the detection processing service interface 1 does not exceed 500ms, it may be considered that there may be a problem of abnormal exit when the desktop of the electronic device displays the interface 1, and in this implementation, the detection processing service needs to further perform a further judgment to determine whether there is actually a problem of abnormal exit of the interface 1 displayed on the desktop of the electronic device if the life cycle of the interface 1 does not exceed 500ms.

The detection processing service performs S809 described above, that is, the detection processing service determines whether the life cycle of the interface 1 exceeds 500ms, including: if the detection processing service determines that the life cycle of the interface 1 exceeds 500m, S811 is continued; in the case where the detection processing service judges that the life cycle of the interface 1 does not exceed 500m, S812 to S818 are continued to be executed.

It should be understood that 500ms in S810 is a preset life cycle (i.e., a specific example of the preset life cycle in the method provided in fig. 4) and may be set according to the actual application. For example, the value of the one preset life cycle may be determined according to the processor performance of the electronic device. For another example, the value of the preset life cycle may be determined according to the memory size of the electronic device.

S811, the detection processing service clears the value of the counter 1 for recording the number of starts of the application 1.

After the detection processing service clears the value of the counter 1, the value of the counter 1 is zero.

The detection processing service performs S811 described above, that is, in the case where the life cycle of the interface 1 exceeds 500ms, the detection processing service clears the value of the recorded counter 1. That is, in the case where it is determined that no abnormal exit has occurred after the start of the application 1 running in the electronic device, the detection processing service clears the content recorded before, and no processing is executed later, that is, the processing flow is ended.

Alternatively, if the packet name of the application 1 is recorded when the detection processing service executes S806, the detection processing service needs to clear the recorded packet name of the application 1 when the detection processing service executes S811.

S812, the detection processing service requests the activity management service to obtain the name of the interface 2 displayed on the desktop of the electronic device at the current moment.

The principle of the detection processing service performing S812 above is the same as the principle of the detection processing service performing S709 above, and details not described here in detail can be found in the related description in S709 above.

S813, the activity management service transmits the name of the interface 2 to the detection processing service. Accordingly, the detection processing service receives the name of the interface 2 from the activity management service.

The principle of the detection processing service performing S813 above is the same as that of the detection processing service performing S710 above, and details not described here in detail can be found in the relevant description of S710 above.

S814, the detection processing service determines whether the interface 2 is a desktop initiator.

In the case where the interface 2 in S814 is a desktop initiator, the interface 2 in S814 may be understood as a specific example of a main interface of the electronic device in the method provided in fig. 4.

The detection processing service executes S814, that is, if the life cycle of the interface 1 does not exceed 500ms, the detection processing service determines whether the desktop of the electronic device is the desktop initiator or not after the desktop of the electronic device exits from the state of the display interface 1.

In the embodiment of the present application, the detection processing service determines whether the interface 2 is a desktop initiator, including: in the case where the detection processing service judges that the interface 2 is a desktop starter, S815 to S816 are continued to be executed; in the case where the detection processing service determines that the interface 2 is not a desktop initiator, S811 is continued to be executed.

It will be appreciated that the detection processing service executes S811 after executing S814 described above, i.e., the detection processing service clears the recorded counter 1 value in the case where the life cycle of the interface 1 does not exceed 500ms and the interface 2 is not a desktop initiator. In this implementation, the problem of abnormal exit after startup does not occur after the application 1 is started.

For example, a user clicks on a news application in a desktop launcher of an electronic device, after which the desktop of the electronic device displays an advertising interface for the news application, and then the desktop of the electronic device displays a news interface for the news application, wherein the lifecycle of the advertising interface is less than 500ms.

S815, the detection processing service determines whether the value of the counter 1 is 2 or more.

After the detection processing service executes S815, if it is determined that the value of the counter 1 is greater than or equal to 2, S816 is continuously executed; if it is determined that the value of the counter 1 is less than 2, and thereafter, if the input management service of the electronic device acquires a new user click event again, each module in the electronic device may further execute the method described in S802 to S815.

The value 2 in S815 is a preset number of times (i.e., an example of the preset value involved in the method provided in fig. 4), and the preset number of times is not specifically limited, and may be set according to the actual application scenario. For example, the preset number of times may be 1, 2, 3, or the like.

S816, the detection processing service invokes the killing process to automatically kill the application 1, so that the application 1 runs normally after restarting.

The detection processing service performs the principle of S816 described above, that is, in the case that the user performs a two-click event on the application 1 installed in the electronic device, the life cycle of the interface 1 of the application 1 displayed by the electronic device in response to each click event does not exceed 500ms, and the interface 2 displayed after the electronic device exits from the display interface 1 is a desktop starter of the electronic device, the detection processing service invokes the killing process to kill the application 1, so that the application 1 operates normally after restarting.

In the above implementation manner, under the condition that the application program 1 is started twice in succession and abnormal exits occur, the detection processing service invokes the killing process to automatically kill the application program 1, so that under the condition that frequent abnormal exits occur in the application program 1, the application program 1 is actively killed, and the user experience can be improved.

The principle of the detection processing service performing S816 is the same as that of the detection processing service performing S712, and details not described here in detail can be found in the relevant description of S712.

Optionally, after the detection processing service performs S816 described above, the detection processing service may further perform the following steps: the recorded counter 1 value is cleared.

Optionally, after the detection processing service performs S816 described above, the detection processing service may further perform the following steps: in response to detecting that the processing service invokes the killing process to kill the application 1, the starting process is invoked to restart the application 1 so that the application 1 operates normally after restarting.

It should be understood that the method for processing the application exception exit shown in fig. 8 is merely illustrative, and does not limit the method for processing the application exception exit provided by the present application.

In the embodiment of the application, whether the interface 1 of the display application program 1 of the electronic device has abnormal exit after the first application is started is determined according to the life cycle of the interface 1 corresponding to the detected user click event, the times of the user click event and whether the interface 2 corresponding to the user click event meets certain conditions. In the event that it is determined that there is an abnormal exit of the interface 1 of the electronic device display application 1 after the start of the application 1, the application 1 is automatically killed. In the processing process, the electronic equipment does not need to be restarted manually or the application program 1 does not need to be killed manually by a user, so that the user experience is optimized. Meanwhile, under the condition that the interface 1 of the application program 1 is abnormally exited after the application program 1 is started, the system of the electronic equipment automatically kills the application program 1, so that the subsequent application program 1 can normally run after being restarted. In summary, the method provided by the embodiment of the application can solve the problem that the interface of the application frequently exits abnormally after the application is started without the participation of the user, simplifies the user operation and improves the user experience.

The method for handling the application exception exit according to the embodiment of the present application is described in detail above with reference to fig. 1 to 8, and the device embodiment of the present application will be described in detail below with reference to fig. 9 and 10. It should be understood that, the processing device for application exception exit in the embodiment of the present application may execute the foregoing processing methods for application exception exits in the embodiment of the present application, that is, the following specific working processes of various products may refer to the corresponding processes in the foregoing method embodiments.

Fig. 9 is a schematic diagram of a processing apparatus for application exception exit according to an embodiment of the present application. For example, the processing apparatus 900 for application exception exit shown in fig. 9 is applied to an electronic device, and the processing apparatus 900 for application exception exit includes a processing unit 910. Next, the function of the processing unit 910 will be specifically explained.

The processing unit 910 is configured to: acquiring interface life cycles of N interfaces displayed in response to N opening operations of a first application, wherein the N opening operations are in one-to-one correspondence with the N interfaces, the corresponding interfaces are displayed based on each opening operation and flash back to a main interface of the electronic equipment after the corresponding interfaces are displayed, the interface life cycle of each interface is a time period between the moment when the electronic equipment creates each interface and the moment when the electronic equipment destroys each interface, and N is a positive integer; and under the condition that the interface life cycles of the N interfaces do not exceed the preset life cycle, automatically killing the first application, so that the first application operates normally after restarting.

In one possible implementation, N is a preset value.

In another possible implementation, the N open operations are non-consecutive N operations detected by the electronic device.

In another possible implementation, the processing unit 910 is further configured to: after the automatically killing the first application, performing the following operations: and automatically starting the first application so that the first application normally operates after being restarted.

In another possible implementation manner, the processing unit 910 has an operating system installed therein, where the operating system includes a detection processing service located in an application framework layer, and the detection processing service is used for: acquiring interface life cycles of the N interfaces; the detection processing service is used for: and under the condition that the interface life cycles of the N interfaces do not exceed the preset life cycle, automatically killing the first application.

In another possible implementation manner, the operating system further includes a desktop initiator at an application layer, and an input management service and an activity management service at the application framework layer, where the activity management service is used for: acquiring the moment when the activity management service creates each interface and the moment when the electronic equipment destroys each interface; the activity management service is further configured to: the moment when the electronic equipment creates each interface and the moment when the electronic equipment destroys each interface are sent to the detection processing service; the detection processing service is further configured to: and obtaining the interface life cycle of each interface according to the time when the electronic equipment creates each interface and the time when the electronic equipment destroys each interface so as to obtain the interface life cycles of the N interfaces.

In another possible implementation manner, the operating system further includes a desktop initiator at an application layer, and an input management service and an activity management service at the application framework layer, where the activity management service is used for: acquiring the moment when the activity management service creates each interface and the moment when the electronic equipment destroys each interface; the activity management service is further configured to: obtaining an interface life cycle of each interface according to the moment when the electronic equipment creates each interface and the moment when the electronic equipment destroys each interface; the activity management service is further configured to: and sending the interface life cycle of each interface to the detection processing service so that the detection processing service obtains the interface life cycles of the N interfaces.

In another possible implementation manner, the operating system further includes a desktop initiator at an application layer, and an input management service and an activity management service at the application framework layer, where the input management service is used for: transmitting each opening operation to the desktop initiator under the condition that the input management service detects the opening operation; the desktop starter is used for: notifying the activity management service to execute each opening operation under the condition that the desktop starter receives each opening operation; the activity management service is configured to: and responding to each opening operation, and displaying an interface corresponding to each opening operation.

The processing apparatus 900 for application exception exit is embodied in the form of a functional unit. The term "unit" herein may be implemented in software and/or hardware, without specific limitation.

For example, a "unit" may be a software program, a hardware circuit or a combination of both that implements the functions described above. The hardware circuitry may include application specific integrated circuits (application specific integrated circuit, ASICs), electronic circuits, processors (e.g., shared, proprietary, or group processors, etc.) and memory for executing one or more software or firmware programs, merged logic circuits, and/or other suitable components that support the described functions.

Thus, the elements of the examples described in the embodiments of the present application can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether such functionality is implemented as hardware or software 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.

Fig. 10 is a schematic diagram of a structure of an electronic device provided by the present application. The dashed lines in fig. 10 indicate that the unit or the module is optional. The electronic device 1000 may be configured to implement the method for handling application exception exits described in the method embodiments above.

The electronic device 1000 includes one or more processors 1001, and the one or more processors 1001 may support a method for processing application exception exits in an embodiment of a method for implementing the electronic device 1000. The processor 1001 may be a general purpose processor or a special purpose processor. For example, the processor 1001 may be a central processing unit (central processing unit, CPU), digital signal processor (digital signal processor, DSP), application specific integrated circuit (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA), or other programmable logic device such as discrete gates, transistor logic, or discrete hardware components.

The processor 1001 may be configured to control the electronic device 1000, execute a software program, and process data of the software program. The electronic device 1000 may also include a communication unit 1005 to enable input (reception) and output (transmission) of signals.

For example, the electronic device 1000 may be a chip, the communication unit 1005 may be an input and/or output circuit of the chip, or the communication unit 1005 may be a communication interface of the chip, which may be an integral part of a terminal device or other electronic device.

For another example, the electronic device 1000 may be a terminal device, the communication unit 1005 may be a transceiver of the terminal device, or the communication unit 1005 may be a transceiver circuit of the terminal device.

The electronic device 1000 may include one or more memories 1002 having a program 1004 stored thereon, where the program 1004 is executable by the processor 1001 to generate instructions 1003, so that the processor 1001 executes the processing method for application exception exit described in the above method embodiment according to the instructions 1003.

Optionally, the memory 1002 may also have data stored therein. Alternatively, the processor 1001 may also read data stored in the memory 1002, which may be stored at the same memory address as the program 1004, or which may be stored at a different memory address than the program 1004.

The processor 1001 and the memory 1002 may be provided separately or may be integrated together; for example, integrated on a System On Chip (SOC) of the terminal device.

Illustratively, the memory 1002 may be configured to store a related program 1004 of the method for handling an application exception exit provided in the embodiment of the present application, and the processor 1001 may be configured to call the related program 1004 of the method for handling an application exception exit stored in the memory 1002, to execute the method for handling an application exception exit in the embodiment of the present application.

The present application also provides a computer program product, which when executed by the processor 1001, implements the method for processing application exception exit according to any one of the method embodiments of the present application.

The computer program product may be stored in the memory 1002, for example, the program 1004, and the program 1004 is finally converted into an executable object file capable of being executed by the processor 1001 through preprocessing, compiling, assembling, and linking.

The application also provides a computer readable storage medium, on which a computer program is stored, which when executed by a computer implements the method for handling application exception exit according to any of the method embodiments of the application. The computer program may be a high-level language program or an executable object program.

The computer-readable storage medium is, for example, a memory 1002. The memory 1002 may be a volatile memory or a nonvolatile memory, or the memory 1002 may include both a volatile memory and a nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM).

In the present application, "at least one" means one or more, and "a plurality" means two or more. "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.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software 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.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative; for example, the division of the units is only one logic function division, and other division modes can be adopted in actual implementation; for example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. The method for processing the abnormal exit is characterized by being applied to the electronic equipment, and comprises the following steps:

acquiring interface life cycles of N interfaces displayed in response to N opening operations of a first application, wherein the N opening operations are in one-to-one correspondence with the N interfaces, the corresponding interfaces are displayed based on each opening operation and flash back to a main interface of the electronic equipment after the corresponding interfaces are displayed, the interface life cycle of each interface is a time period between the moment when the electronic equipment creates each interface and the moment when the electronic equipment destroys each interface, and N is a positive integer;

Under the condition that the interface life cycles of the N interfaces do not exceed the preset life cycle, automatically killing the first application, so that the first application runs normally after restarting;

an operating system is installed in the electronic device, the operating system comprises a detection processing service located in an application framework layer, and the method comprises the following steps:

the detection processing service obtains interface life cycles of the N interfaces;

the detection processing service automatically kills the first application under the condition that the interface life cycles of the N interfaces do not exceed the preset life cycle;

the operating system further includes a desktop starter located at an application layer, and an input management service and an activity management service located at the application framework layer, where the detection processing service obtains an interface life cycle of the N interfaces, and the detection processing service includes:

the activity management service obtains the moment when the activity management service creates each interface and the moment when the electronic equipment destroys each interface;

the activity management service sends the moment when the electronic equipment creates each interface and the moment when the electronic equipment destroys each interface to the detection processing service;

And the detection processing service obtains the interface life cycle of each interface according to the time when the electronic equipment creates each interface and the time when the electronic equipment destroys each interface so as to obtain the interface life cycles of the N interfaces.

2. The method of claim 1, wherein N is a predetermined value.

3. The method of claim 1 or 2, wherein the N open operations are consecutive N operations detected by the electronic device.

4. The method of claim 1 or 2, wherein after the automatically killing the first application, the method further comprises:

and automatically starting the first application so that the first application normally operates after being restarted.

5. The method according to claim 1 or 2, wherein the operating system further comprises a desktop launcher at an application layer, and an input management service and an activity management service at the application framework layer, and the detecting and processing service obtains interface life cycles of the N interfaces, including:

The activity management service obtains the interface life cycle of each interface according to the time when the electronic equipment creates each interface and the time when the electronic equipment destroys each interface;

and the activity management service sends the interface life cycle of each interface to the detection processing service so that the detection processing service obtains the interface life cycles of the N interfaces.

6. The method of claim 1 or 2, wherein the operating system further comprises a desktop launcher at an application layer, and an input management service and an activity management service at the application framework layer, the method further comprising, before the detection processing service automatically kills the first application:

transmitting each opening operation to the desktop initiator under the condition that the input management service detects the opening operation;

notifying the activity management service to execute each opening operation under the condition that the desktop starter receives each opening operation;

and the activity management service responds to each opening operation and displays an interface corresponding to each opening operation.

7. The method of claim 1 or 2, wherein the N open operations are non-consecutive N operations detected by the electronic device.

8. An electronic device comprising a processor and a memory, the memory for storing a computer program, the processor for calling and running the computer program from the memory, such that the processor performs the method of handling application exception exit according to any one of claims 1 to 7.

9. A chip comprising a processor that, when executing instructions, performs the method of handling application exception exit as claimed in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, causes the processor to execute the method of handling application exception exit according to any one of claims 1 to 7.