CN113138857A

CN113138857A - Memory cleaning method, mobile terminal and storage medium

Info

Publication number: CN113138857A
Application number: CN202110605481.9A
Authority: CN
Inventors: 高启杰
Original assignee: Shanghai Chuanying Information Technology Co Ltd
Current assignee: Shanghai Chuanying Information Technology Co Ltd
Priority date: 2021-05-31
Filing date: 2021-05-31
Publication date: 2021-07-20

Abstract

The application discloses a memory cleaning method, a mobile terminal and a storage medium, wherein the memory cleaning method comprises the following steps: acquiring the memory fragmentation degree of the mobile terminal, and when the memory fragmentation degree is greater than or equal to a first degree and/or less than a second degree, performing memory fragmentation cleaning on the mobile terminal according to a first memory cleaning strategy; and when the memory fragmentation degree is greater than or equal to the second degree, performing memory fragmentation cleaning on the mobile terminal according to a second memory cleaning strategy. By the aid of the method and the device, automatic memory fragment cleaning can be realized, and efficiency is higher and more timely.

Description

Memory cleaning method, mobile terminal and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a memory cleaning method, a mobile terminal, and a storage medium.

Background

With the development of science and technology, mobile terminals are widely applied to daily life of people, and applications (apps) carried by mobile terminals are more and more, and in the process of designing and implementing the application, the inventor finds that at least the following problems exist: the user is not turned off habitually, which causes a large amount of memory fragments of the mobile terminal, however, in some implementations, the memory fragments can only be cleaned manually by the user, and there are problems of untimely cleaning and low efficiency.

The foregoing description is provided for general background information and is not admitted to be prior art.

Disclosure of Invention

In view of the above technical problems, the present application provides a memory cleaning method, a mobile terminal and a storage medium, which can realize automatic memory fragment cleaning with higher efficiency and more timeliness.

In order to solve the above technical problem, the present application provides a memory cleaning method, including:

acquiring the fragmentation degree of a memory of the mobile terminal;

when the memory fragmentation degree is greater than or equal to a first degree and/or less than a second degree, performing memory fragmentation cleaning on the mobile terminal according to a first memory cleaning strategy; and/or the presence of a gas in the gas,

and when the memory fragmentation degree is greater than or equal to the second degree, performing memory fragmentation cleaning on the mobile terminal according to a second memory cleaning strategy.

Optionally, the obtaining the memory fragmentation degree of the mobile terminal includes: and acquiring the memory fragmentation degree of the mobile terminal according to a preset period.

Optionally, the obtaining the memory fragmentation degree of the mobile terminal includes: and when the failure of the memory application is detected, acquiring the memory fragmentation degree of the mobile terminal.

Optionally, performing memory fragment cleaning on the mobile terminal according to a first memory cleaning policy, including:

and when the set time is up, controlling the mobile terminal to restart according to a first restarting mode so as to clear up the memory fragments.

Optionally, controlling the mobile terminal to restart according to a first restart mode to clean up the memory fragments includes:

and controlling the mobile terminal to restart, and in the process of restarting, controlling the volume of the sound output by the mobile terminal to be less than or equal to a preset volume threshold value, and/or controlling the brightness of a display panel of the mobile terminal to be less than or equal to a preset brightness threshold value.

Optionally, controlling the volume of the sound output by the mobile terminal to be less than or equal to the preset volume threshold refers to: controlling the mobile terminal to be in a mute state;

controlling the brightness of the display panel of the mobile terminal to be less than or equal to the preset brightness threshold means: and controlling the mobile terminal to be in a black screen state.

Optionally, before performing memory fragment cleaning on the mobile terminal according to the second memory cleaning policy, the method further includes:

outputting memory cleaning prompt information, wherein optionally, the memory cleaning prompt information is used for prompting a user whether to clean the memory fragments;

and when an acknowledgement clearing instruction is received, optionally, when an acknowledgement clearing instruction input by a user for the memory clearing prompt information is received, executing a step of clearing memory fragments of the mobile terminal according to a second memory clearing strategy.

Optionally, when a clear cancel instruction is received, or optionally, when a clear cancel instruction input by a user for the memory clear prompt information is received, performing memory fragment clearing on the mobile terminal according to the first memory clear policy.

Optionally, performing memory fragment cleaning on the mobile terminal according to a second memory cleaning policy, including:

and controlling the mobile terminal to restart according to the second restart mode so as to clear up the memory fragments.

if the application running in the foreground is detected to exist, cleaning the memory fragmentation of the first application to be cleaned, and optionally, the first application to be cleaned is an application other than the application running in the foreground.

determining a second application to be cleaned, optionally, the second application to be cleaned is an application running in a background and/or the running time of the background exceeds a preset time threshold;

and cleaning the memory fragmentation of the second application to be cleaned.

Optionally, the method further comprises:

outputting a memory cleaning time setting interface;

acquiring target memory clearing time, and optionally acquiring target memory clearing time input by a user aiming at the memory clearing time setting interface;

and when the target memory cleaning time is up, cleaning the memory fragments of the mobile terminal.

Optionally, the method further comprises:

and outputting memory cleaning result prompt information, wherein optionally, the memory cleaning result prompt information is used for indicating the cleaning degree of the memory fragments.

The application also provides a mobile terminal, wherein the mobile terminal comprises: the memory is stored with a program, and the program is executed by the processor to realize the steps of the memory cleaning method.

The present application further provides a readable storage medium, wherein the readable storage medium stores thereon a computer program, and the computer program, when executed by a processor, implements the steps of the memory cleaning method as described above.

As described above, the memory fragment cleaning method provided in the embodiment of the present application is applied to a mobile terminal, and the memory fragments are automatically cleaned by selecting different memory fragment cleaning methods according to different degrees of memory fragmentation, so that a tedious manual memory fragment cleaning method is changed, and the efficiency is higher and more timely by automatically cleaning the memory fragments.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

Fig. 1 is a schematic diagram of a hardware structure of a mobile terminal implementing an embodiment of the present application;

fig. 2 is a communication network system architecture diagram according to an embodiment of the present application;

fig. 3 is a schematic flowchart of a memory scrubbing method according to an embodiment of the present disclosure;

fig. 4 is a schematic diagram of a memory clearing time setting interface according to an embodiment of the present disclosure;

FIG. 5 is a schematic diagram of a user interface provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of another user interface provided by embodiments of the present application;

fig. 7 is a schematic diagram of a restart interface of a mobile terminal according to an embodiment of the present disclosure;

fig. 8a is a schematic diagram of a memory cleaning result prompt information interface according to an embodiment of the present application;

fig. 8b is a schematic diagram of another memory cleaning result prompt information interface provided in the embodiment of the present application;

fig. 9 is a comparison graph of performance changes of memory fragments with the use time of a mobile terminal according to an embodiment of the present disclosure;

fig. 10 is a schematic diagram of a memory fragmentation cleaning apparatus according to an embodiment of the present application.

The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings. With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the recitation of an element by the phrase "comprising an … …" does not exclude the presence of additional like elements in the process, method, article, or apparatus that comprises the element, and further, where similarly-named elements, features, or elements in different embodiments of the disclosure may have the same meaning, or may have different meanings, that particular meaning should be determined by their interpretation in the embodiment or further by context with the embodiment.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context. Also, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms "comprises," "comprising," "includes" and/or "including," when used in this specification, specify the presence of stated features, steps, operations, elements, components, items, species, and/or groups, but do not preclude the presence, or addition of one or more other features, steps, operations, elements, components, species, and/or groups thereof. The terms "or," "and/or," "including at least one of the following," and the like, as used herein, are to be construed as inclusive or mean any one or any combination. For example, "includes at least one of: A. b, C "means" any of the following: a; b; c; a and B; a and C; b and C; a and B and C ", again for example," A, B or C "or" A, B and/or C "means" any of the following: a; b; c; a and B; a and C; b and C; a and B and C'. An exception to this definition will occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some way.

It should be understood that, although the steps in the flowcharts in the embodiments of the present application are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, in different orders, and may be performed alternately or at least partially with respect to other steps or sub-steps of other steps.

The words "if", as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.

It should be noted that step numbers such as S102 and S103 are used herein for the purpose of more clearly and briefly describing the corresponding contents, and do not constitute a substantial limitation on the sequence, and those skilled in the art may perform S103 and then S102 in the specific implementation, but these steps should be within the scope of the present application.

It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for the convenience of description of the present application, and have no specific meaning in themselves. Thus, "module", "component" or "unit" may be used mixedly.

The mobile terminal may be implemented in various forms. For example, the mobile terminal described in the present application may include mobile terminals such as a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, and the like, and fixed terminals such as a Digital TV, a desktop computer, and the like.

The following description will be given taking a mobile terminal as an example, and it will be understood by those skilled in the art that the configuration according to the embodiment of the present application can be applied to a fixed type terminal in addition to elements particularly used for mobile purposes.

Referring to fig. 1, which is a schematic diagram of a hardware structure of a mobile terminal for implementing various embodiments of the present application, the mobile terminal 100 may include: RF (Radio Frequency) unit 101, WiFi module 102, audio output unit 103, a/V (audio/video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 1 is not intended to be limiting of mobile terminals, which may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

The following describes each component of the mobile terminal in detail with reference to fig. 1:

the radio frequency unit 101 may be configured to receive and transmit signals during information transmission and reception or during a call, and specifically, receive downlink information of a base station and then process the downlink information to the processor 110; in addition, the uplink data is transmitted to the base station. Typically, radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 can also communicate with a network and other devices through wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA2000(Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division duplex Long Term Evolution), and TDD-LTE (Time Division duplex Long Term Evolution).

WiFi belongs to short-distance wireless transmission technology, and the mobile terminal can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 102, and provides wireless broadband internet access for the user. Although fig. 1 shows the WiFi module 102, it is understood that it does not belong to the essential constitution of the mobile terminal, and may be omitted entirely as needed within the scope not changing the essence of the invention.

The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output as sound when the mobile terminal 100 is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, and the like.

The a/V input unit 104 is used to receive audio or video signals. The a/V input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, the Graphics processor 1041 Processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphic processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 may receive sounds (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, or the like, and may be capable of processing such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 101 in case of a phone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.

The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor that adjusts brightness of the display panel 1061 according to brightness of ambient light, and a proximity sensor that turns off the display panel 1061 and/or a black screen when the mobile terminal 100 moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.

The display unit 106 is used to display information input by a user or information provided to the user. The Display unit 106 may include a Display panel 1061, and the Display panel 1061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 107 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the mobile terminal. Alternatively, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect a touch operation performed by a user on or near the touch panel 1071 (e.g., an operation performed by the user on or near the touch panel 1071 using a finger, a stylus, or any other suitable object or accessory), and drive a corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of a touch detection device and a touch controller. Optionally, the touch detection device detects a touch orientation of a user, detects a signal caused by a touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 110, and can receive and execute commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. Optionally, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like, and are not limited thereto.

Alternatively, the touch panel 1071 may cover the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although the touch panel 1071 and the display panel 1061 are shown in fig. 1 as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, and is not limited herein.

The interface unit 108 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and external devices.

The memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a program storage area and a data storage area, and optionally, the program storage area may store an operating system, an application program (such as a sound playing function, an image playing function, and the like) required by at least one function, and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 109 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by operating or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor, optionally, the application processor mainly handles operating systems, user interfaces, application programs, etc., and the modem processor mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.

The mobile terminal 100 may further include a power supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, so as to manage charging, discharging, and power consumption management functions via the power management system.

Although not shown in fig. 1, the mobile terminal 100 may further include a bluetooth module or the like, which is not described in detail herein.

In order to facilitate understanding of the embodiments of the present application, a communication network system on which the mobile terminal of the present application is based is described below.

Referring to fig. 2, fig. 2 is an architecture diagram of a communication Network system according to an embodiment of the present disclosure, where the communication Network system is an LTE system of a universal mobile telecommunications technology, and the LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and an IP service 204 of an operator, which are in communication connection in sequence.

Optionally, the UE201 may be the mobile terminal 100 described above, and is not described herein again.

The E-UTRAN202 includes eNodeB2021 and other eNodeBs 2022, among others. Alternatively, the eNodeB2021 may be connected with other enodebs 2022 through a backhaul (e.g., X2 interface), the eNodeB2021 is connected to the EPC203, and the eNodeB2021 may provide the UE201 access to the EPC 203.

The EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving gateway) 2034, a PGW (PDN gateway) 2035, and a PCRF (Policy and Charging Rules Function) 2036, and the like. Optionally, the MME2031 is a control node that handles signaling between the UE201 and the EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as home location register (not shown) and holds subscriber specific information about service characteristics, data rates, etc. All user data may be sent through SGW2034, PGW2035 may provide IP address assignment for UE201 and other functions, and PCRF2036 is a policy and charging control policy decision point for traffic data flow and IP bearer resources, which selects and provides available policy and charging control decisions for a policy and charging enforcement function (not shown).

The IP services 204 may include the internet, intranets, IMS (IP Multimedia Subsystem), or other IP services, among others.

Although the LTE system is described as an example, it should be understood by those skilled in the art that the present application is not limited to the LTE system, but may also be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems.

Based on the above mobile terminal hardware structure and communication network system, various embodiments of the present application are provided.

Referring to fig. 3, fig. 3 is a schematic flowchart illustrating a memory cleaning method according to an embodiment of the present disclosure. The method of the embodiment of the present application may be performed by the mobile terminal shown in fig. 1, which may be applied to the communication network system shown in fig. 2. The memory cleaning method shown in fig. 3 may include the following steps:

s301, obtaining the memory fragmentation degree of the mobile terminal.

Optionally, a memory fragment is a "fragmented memory" and is used to describe all unusable memories in a system.

In an embodiment of the present application, the memory fragments include internal memory fragments and/or external memory fragments.

Optionally, the internal memory fragmentation may be: when the memory allocation algorithm dynamically allocates the memory with the predetermined size to the user, the memory with the predetermined size is not the memory limited by the fixed allocation mechanism, and the generated memory is called as an internal memory fragment. For example, assuming that all memory allocations must start at an address divisible by 4, 8, or 16 or because of the limitations of the paging mechanism of the MMU, the memory allocation algorithm is determined to allocate a memory block of a predetermined size to a client, when a client requests a memory block of 43 bytes, it may get a bit larger byte of 44 bytes, 48 bytes, etc., because there is no memory of the appropriate size, and the excess space resulting from rounding off the required size is called an internal fragment.

The external memory fragments may be: when the memory allocation algorithm dynamically allocates the memory with the predetermined size to the user, frequent allocation and recycling of physical pages by the memory allocation algorithm may cause a large number of continuous small page blocks to be included in the allocated pages, which is an external memory fragment. For example, there is a block with a total of 100 units of contiguous free memory space, ranging from 0 to 99. If a memory block is requested from the memory block, for example, 10 units, the requested memory block is in an interval of 0 to 9, and if a memory block is requested again, for example, 5 units, the memory block obtained from the second block should be in an interval of 10 to 14. If the first block of memory block is released, then a block of memory larger than 10 units, for example, 20 units, is applied. Since the memory block just released cannot satisfy the new request, only 20 units of memory blocks can be allocated starting from 15. The state of the whole memory space is 0-9 idle, 10-14 occupied, 15-34 occupied and 25-99 idle. Wherein 0-9 is a memory fragment. If 10-14 are occupied all the time and the space applied later is larger than 10 units, 0-9 are never used and finally become external memory fragments.

In an embodiment, the memory fragmentation degree of the mobile terminal may be obtained according to a preset period, where the preset period may be a memory fragmentation clearing period manually set by a user, or may also be a system default memory fragmentation clearing period, and the preset period may be, for example, 4 hours, 1 day, and the like.

In another embodiment, the memory fragmentation degree of the mobile terminal may be automatically obtained when a memory application failure is detected. For example, when a certain application (e.g., a video application) configured by the mobile terminal is started, the application needs to apply for the memory, and when the memory application result indicates that the memory application fails, the memory fragmentation degree of the mobile terminal can be automatically obtained.

In this embodiment, the memory fragmentation degree may be used to indicate a usage number of the memory fragments (the usage number is used to indicate how much memory resources of the memory are occupied, for example, 10M), or the memory fragmentation degree is used to indicate a ratio of the memory fragments to the memory.

In a feasible implementation manner, the manner of obtaining the memory fragmentation degree of the mobile terminal may be: and acquiring the memory fragmentation degree of the mobile terminal through the existing application program interface of the kernel preset on the mobile terminal. Optionally, the application program interface may be some predefined interfaces (such as functions and HTTP interfaces), or a contract for linking different components of the software system, where the interface or the contract may be preset in an application of the mobile terminal (such as a video application, a search application, and the like), and the interface or the contract is used to directly call an interface or a contract of a certain application to implement when another application needs to use some function of the certain application that has been preset with the interface or the contract.

In the embodiment of the application, after the memory fragmentation degree of the mobile terminal is obtained, the memory fragmentation degree is compared with a preset first degree and a preset second degree. When the memory fragmentation degree is greater than or equal to the first degree, and/or less than the second degree, executing step S302; and/or, when the degree of memory fragmentation is greater than or equal to the second degree, performing step S303. Optionally, the second degree is greater than the first degree, and the first degree and the second degree are respectively preset thresholds of memory fragmentation degrees set on the mobile terminal, where the first degree and the second degree may be preset thresholds of memory fragmentation degrees manually set by a user, or may be preset thresholds of memory fragmentation degrees default by the system. When the memory fragmentation degree is used for indicating the number of the memory fragments, the first degree and the second degree are number thresholds, for example, the first degree is 50M, and the second degree is 100M; when the memory fragmentation degree is used to indicate the proportion of the memory fragments in the memory, the first degree and the second degree are a proportion threshold, for example, the first degree is 30% and the second degree is 50%.

S302, when the memory fragmentation degree is larger than or equal to the first degree and/or smaller than the second degree, performing memory fragmentation cleaning on the mobile terminal according to a first memory cleaning strategy.

In the embodiment of the application, when the acquired memory fragmentation degree is greater than or equal to the first degree and/or is less than the second degree, memory fragmentation cleaning is performed on the mobile terminal according to a first memory cleaning strategy, which includes the following three conditions: the first method may be that when the acquired memory fragmentation degree is greater than or equal to the first degree and less than the second degree, the memory fragmentation is performed on the mobile terminal according to a first memory cleaning policy. The second method may be that when the acquired memory fragmentation degree is greater than or equal to the first degree, no matter whether the acquired memory fragmentation degree is less than the second degree, the memory fragmentation is cleared for the mobile terminal according to the first memory clearing policy. The third method may be that, no matter whether the obtained memory fragmentation degree is greater than or equal to the first degree, as long as the obtained memory fragmentation degree is less than the second degree, the memory fragmentation is performed on the mobile terminal according to the first memory cleaning policy.

In this embodiment of the present application, performing memory fragment cleaning on the mobile terminal according to the first memory cleaning policy may be: and determining the current system time on the mobile terminal, and controlling the mobile terminal to restart according to a first restarting mode when the system time is consistent with the set time, namely when the set time is up, so as to clean the memory fragments.

Optionally, the set time may be, for example, 11 pm, and optionally, the set time may be manually set by a user or may be a default memory fragmentation cleaning period of the system. For example, a memory clearing time setting interface is displayed, the memory clearing time setting interface may be as shown in fig. 4, the time (e.g., 8:00 am shown in the figure) input by the user with respect to the memory clearing time setting interface is determined as the memory clearing time, that is, the set time, and when the system time on the mobile terminal reaches the set time, the memory fragments of the mobile terminal may be automatically cleared by restarting the mobile terminal.

In an embodiment, the controlling the mobile terminal to restart according to a first restart mode to clean up the memory fragments may be: and controlling the mobile terminal to restart, and controlling the volume of the sound output by the mobile terminal to be less than or equal to a preset volume threshold value in the process of restarting. Optionally, controlling the volume of the sound output by the mobile terminal to be less than or equal to the preset volume threshold may refer to controlling the mobile terminal to be in a mute state; or, it may refer to controlling the mobile terminal to emit a smaller sound instead of muting completely. For example, the preset volume threshold of the mobile terminal is 30 db noise, and the output noise of the mobile terminal when the mobile terminal is restarted is 20 db noise, which indicates that the mobile terminal is in a mute state.

In an embodiment, the controlling the mobile terminal to restart according to a first restart mode to clean up the memory fragments may be: and controlling the mobile terminal to restart, and controlling the brightness of a display panel of the mobile terminal to be less than or equal to a preset brightness threshold value in the restarting process. Optionally, controlling the brightness of the display panel of the mobile terminal to be less than or equal to the preset brightness threshold may refer to controlling the display panel of the mobile terminal to be in a black screen state; or, it may refer to controlling the display panel of the mobile terminal to display a smaller brightness instead of a completely black screen (as shown in fig. 7, which is a schematic diagram illustrating a restart of the mobile terminal in a mute and black screen state). For example, the preset brightness threshold of the mobile terminal is 0.5 candela per square meter, and the brightness of the display panel of the mobile terminal at the restart is 0.2 candela per square meter, which indicates that the mobile terminal is in a black screen state.

In an embodiment, the controlling the mobile terminal to restart according to a first restart mode to clean up the memory fragments may be: and controlling the mobile terminal to restart, and in the process of restarting, controlling the volume of the sound output by the mobile terminal to be less than or equal to a preset volume threshold, and optionally controlling the brightness of a display panel of the mobile terminal to be less than or equal to a preset brightness threshold.

Optionally, when the degree of fragmentation of the memory is less than the first degree, the memory fragments of the mobile terminal may be cleaned according to a third cleaning policy. In an embodiment, the clearing the memory fragments of the mobile terminal according to the third clearing policy may be: the method includes the steps of clearing up memory fragments corresponding to applications except applications currently used by a user (for example, if the user uses an instant messaging application currently, clearing up the memory fragments corresponding to the applications except the instant messaging application), and in the clearing process, keeping the mobile terminal in a starting state (including a screen-on state or a screen-off state), namely, the mobile terminal is not controlled to restart to clear up the memory fragments. By adopting the mode, the mobile terminal can be cleaned under the condition that the user uses the mobile terminal, and the use of the user is not influenced.

In another embodiment, the clearing the memory fragments of the mobile terminal according to the third clearing policy may further include: and cleaning memory fragments corresponding to the applications with the running time length of the background exceeding a preset time length threshold. For example, the applications running in the background include an instant messaging application, a map application and a short video application, the running time of the instant messaging application is 3min, the running time of the map application is 5min, and if the preset running time threshold is 4min, only the memory fragments corresponding to the map application are cleaned. According to the situation, the mobile terminal can intelligently divide the storage space of the memory fragments of the memory for each application, so that when the memory fragments of a specific application are cleaned, the storage positions of the memory fragments can be quickly found, the cleaning of the memory fragments can be quickly completed, and meanwhile, the mistaken cleaning is avoided and the influence on the normal use of the application which does not need to be cleaned is avoided.

And S303, when the memory fragmentation degree is greater than or equal to the second degree, performing memory fragmentation cleaning on the mobile terminal according to a second memory cleaning strategy.

In an embodiment, the performing memory fragment cleaning on the mobile terminal according to the second memory cleaning policy may be: and controlling the mobile terminal to restart according to the second restart mode so as to clear up the memory fragments. Optionally, the second restart mode may be that the mobile terminal is restarted immediately when a confirmation clearing instruction input by the user for the memory clearing prompt information is received. For example, when the current memory fragmentation degree of the mobile terminal is greater than or equal to the second degree, a memory cleaning prompt message is displayed on a display interface of the mobile terminal (for example, it is prompted that the memory occupation ratio of an application running on the current mobile terminal is 89%, and the use of the mobile terminal is slow), and when a confirmation cleaning instruction input by a user for the memory cleaning prompt message is received, the mobile terminal is restarted according to a second restarting mode to clean the memory fragmentation. In an embodiment, when a clear cancel instruction input by a user for the memory clear prompt information is received, the mobile terminal may be restarted according to the first restart mode.

In this embodiment of the application, performing memory fragment cleaning on the mobile terminal according to the second memory cleaning policy may further be: if it is detected that there is an application (e.g., a video application) running in the foreground, cleaning the memory fragmentation of the first application to be cleaned, optionally, the first application to be cleaned may be an application other than the application running in the foreground.

In this embodiment of the application, performing memory fragment cleaning on the mobile terminal according to the second memory cleaning policy may further be: determining a second application to be cleaned (for example, a search application), optionally, the second application to be cleaned may be an application running in the background and/or having a background running time length exceeding a preset time length threshold, and cleaning memory fragments of the second application to be cleaned.

In an embodiment, after the mobile terminal is restarted in the first restart manner or the second restart manner, the static and dynamic boot-up flag maps of the mobile terminal are displayed, as shown in fig. 5 and fig. 6, respectively, and optionally, the static boot-up flag map may be: displaying a static mark display of 'fragmentation finishing' in a middle area of the mobile terminal; the dynamic boot marker map may be: the dynamic logo display of ' memory fragmentation causes system performance degradation, and ' fragmentation adjustment ' is being tried for improving your system performance for you. Alternatively, the static and dynamic logo displays may dynamically make the specific operating state of the mobile terminal clear to the customer, and the logo may also make the customer unaware that the handset has been restarted, causing additional concerns. Alternatively, the static logo may be a display interface where the mobile terminal remains stationary upon restart (e.g., the identifier, which may be "in fragmentation adjustment," remains stationary in the display interface); the dynamic logo may be displayed in a dynamic interface (e.g., a "fragmentation adjustment" logo may be displayed cyclically from left to right in the display interface) when the mobile terminal is restarted. Meanwhile, the static mark map and the dynamic mark map may be interface displays of the mobile terminal manually set by the user, or interface displays of the mobile terminal default by the system.

In an embodiment, after the mobile terminal is restarted in the first restart manner or the second restart manner, the memory cleaning result is displayed, as shown in fig. 8a and 8b, the memory cleaning result of "cleaning XXX memory fragments" is displayed in the upper area of the current display interface. The memory cleaning result is used for indicating the cleaning degree of the memory fragments. For example, it may be displayed that "80% of the memory fragments have been cleared for you by the memory fragmentation reboot mode", or it may be displayed that "200M of the memory fragments have been cleared for you by the memory fragmentation reboot mode", and the effect of clearing the memory fragments according to the embodiment of the present application is visually displayed by displaying how many memory fragments have been cleared.

Fig. 9 is a performance comparison diagram of a memory cleaning method according to an embodiment of the present application. Optionally, the abscissa represents the number of days of use of the mobile terminal, and the ordinate represents the performance status value of the mobile terminal; along with the increase of the number of days of use, the performance change of the mobile terminal is not obvious, a water level with good performance is always kept, and the performance change of the mobile terminal before the scheme is adopted is linearly reduced; therefore, it can be seen that the memory fragment cleaning method adopted in the embodiment of the present application can automatically clean the memory fragments in the mobile terminal, and optionally, the data in fig. 9 is obtained through experiments.

Referring to fig. 10, fig. 10 is a schematic structural diagram of a memory fragment cleaning apparatus according to an embodiment of the present disclosure. The memory fragmentation cleaning apparatus 600 includes an obtaining unit 601, a processing unit 602, and a display unit 603, where:

an obtaining unit 601, configured to obtain a fragmentation degree of a memory;

a processing unit 602, configured to perform memory fragmentation cleaning on the mobile terminal according to a first memory cleaning policy when the memory fragmentation degree is greater than or equal to a first degree and/or is less than a second degree; and/or the presence of a gas in the gas,

the processing unit 602 is further configured to perform memory fragmentation cleaning on the mobile terminal according to a second memory cleaning policy when the memory fragmentation degree is greater than or equal to a second degree;

a display unit 603, configured to display information of a memory fragment cleaning result after the memory fragment is cleaned;

the display unit 603 is further configured to display a display state of the mobile terminal during restarting after the mobile terminal is restarted according to the first memory cleaning policy and/or the second memory cleaning policy;

the display unit 603 is further configured to display memory clearing time setting information;

in some embodiments, the obtaining unit 601, when obtaining the memory fragmentation degree, is specifically configured to: and acquiring the memory fragmentation degree of the mobile terminal according to a preset period. Optionally, the preset period may be a memory fragment clearing period manually set by a user, or may be a default memory fragment clearing period of the system. The preset period may be, for example, 4 hours, 1 day, etc.

In some embodiments, the obtaining unit 601, when obtaining the memory fragmentation degree, is specifically configured to: and when the failure of the memory application is detected, acquiring the memory fragmentation degree of the mobile terminal.

In some embodiments, after obtaining the memory fragmentation degree, the processing unit 601 is specifically configured to: and judging different degrees of memory fragmentation of the mobile terminal, and automatically cleaning according to corresponding cleaning strategies according to the different degrees of memory fragmentation.

In some embodiments, when determining that the degree of memory fragmentation is greater than or equal to the first degree, and/or less than the second degree, the processing unit 602 is specifically configured to: and performing memory fragment cleaning on the mobile terminal according to the first memory cleaning strategy, wherein an implementation method of performing memory fragment cleaning on the mobile terminal in the first cleaning strategy is the same as the method of performing memory fragment cleaning on the mobile terminal in the step S302, and details are not repeated here.

In some embodiments, when determining that the degree of memory fragmentation is greater than or equal to the second degree, the processing unit 602 is specifically configured to: and performing memory fragment cleaning on the mobile terminal according to a second memory cleaning strategy, wherein an implementation method of performing memory fragment cleaning on the mobile terminal in the second cleaning strategy is the same as the method of performing memory fragment cleaning on the mobile terminal in the step S303, and is not described herein again.

In some embodiments, the processing unit 602 performs memory fragmentation cleaning on the mobile terminal according to a first memory cleaning policy, specifically to: and when the set time is reached, controlling the mobile terminal to restart according to a first restart mode to clean the memory fragments, wherein optionally, the first restart mode is consistent with the first restart mode in the step S302, and details are not repeated here.

In some embodiments, the processing unit 602 controls the mobile terminal to restart according to a first restart mode to clean up the memory fragments, and is specifically configured to: the method comprises the steps of controlling the mobile terminal to restart, and controlling the volume of sound output by the mobile terminal to be smaller than or equal to a preset volume threshold value and/or controlling the brightness of a display screen of the mobile terminal to be smaller than or equal to a preset brightness threshold value in the process of restarting, wherein the control of the volume of sound output by the mobile terminal to be smaller than or equal to the preset volume threshold value means that: controlling the mobile terminal to be in a mute state; controlling the brightness of the display screen of the mobile terminal to be less than or equal to the preset brightness threshold value means: and controlling the mobile terminal to be in a black screen state.

In some embodiments, the processing unit 602 performs memory fragmentation cleaning on the mobile terminal according to a second memory cleaning policy, specifically to: and controlling the mobile terminal to restart according to a second restart mode to clean up the fragmentation of the memory, wherein optionally, the second restart mode is consistent with the second restart mode in the step S303, and details are not repeated here.

In some embodiments, the processing unit 602 performs memory fragmentation cleaning on the mobile terminal according to the second memory cleaning policy, and is further specifically configured to: and if detecting that the foreground running application exists, cleaning the memory fragments of the first application to be cleaned, wherein the first application to be cleaned is an application except the foreground running application.

In some embodiments, the processing unit 602 performs memory fragmentation cleaning on the mobile terminal according to the second memory cleaning policy, and is further specifically configured to: determining a second application to be cleaned, wherein the second application to be cleaned is an application in background operation and/or the background operation time length exceeds a preset time length threshold, and cleaning memory fragments of the second application to be cleaned.

In some embodiments, before the display unit 603 performs memory fragmentation cleaning on the mobile terminal according to the second memory cleaning policy, the display unit is specifically configured to: and displaying memory cleaning prompt information, wherein the memory cleaning prompt information is used for prompting a user whether to clean the memory fragments.

In some embodiments, the display unit 603 is specifically configured to, after performing memory fragment cleaning on the mobile terminal according to the first memory cleaning policy and/or performing memory fragment cleaning on the mobile terminal according to the second memory cleaning policy: and displaying memory cleaning result prompt information, wherein the memory cleaning result prompt information is used for indicating the cleaning degree of the memory fragments.

It should be noted that the operations performed by the units of the apparatus shown in fig. 10 may be related to the method embodiment described above. And will not be described in detail herein. The above units can be realized by hardware, software or a combination of hardware and software.

The application also provides a mobile terminal, which comprises a storage, a user interface and a processor, wherein the storage is stored with an application program interface, and the application program interface realizes the steps of the memory fragment cleaning method in any embodiment. Optionally, the user interface includes input devices including a sound pickup device, a touch screen, and the like, and output devices including a speaker, a display panel, and the like.

The present application further provides a computer-readable storage medium, in which a program is stored, and the program is executed by a processor to implement the steps of the memory cleaning method in any of the above embodiments.

In the embodiments of the mobile terminal and the computer-readable storage medium provided in the present application, all technical features of the embodiments of the memory cleaning method are included, and the expanding and explaining contents of the specification are basically the same as those of the embodiments of the mobile terminal method, and are not described herein again.

Embodiments of the present application also provide a computer program product, which includes computer program code, when the computer program code runs on a computer, the computer is caused to execute the method in the above various possible embodiments.

Embodiments of the present application further provide a chip, which includes a memory and a processor, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device in which the chip is installed executes the method in the above various possible embodiments.

The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.

The steps in the method of the embodiment of the application can be sequentially adjusted, combined and deleted according to actual needs.

The units in the device in the embodiment of the application can be merged, divided and deleted according to actual needs.

In the present application, the same or similar term concepts, technical solutions and/or application scenario descriptions will be generally described only in detail at the first occurrence, and when the description is repeated later, the detailed description will not be repeated in general for brevity, and when understanding the technical solutions and the like of the present application, reference may be made to the related detailed description before the description for the same or similar term concepts, technical solutions and/or application scenario descriptions and the like which are not described in detail later.

In the present application, each embodiment is described with emphasis, and reference may be made to the description of other embodiments for parts that are not described or illustrated in any embodiment.

The technical features of the technical solution of the present application may be arbitrarily combined, and for brevity of description, all possible combinations of the technical features in the embodiments are not described, however, as long as there is no contradiction between the combinations of the technical features, the scope of the present application should be considered as being described in the present application.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, a controlled terminal, or a network device) to execute the method of each embodiment of the present application.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The procedures or functions according to the embodiments of the present application are all or partially generated when the computer program instructions are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., coaxial cable, fiber optic, digital subscriber line) or wirelessly (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, memory Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are included in the scope of the present application.

Claims

1. A method for memory cleaning, the method comprising:

acquiring the fragmentation degree of a memory of the mobile terminal;

2. The method according to claim 1, wherein the performing memory fragmentation cleaning on the mobile terminal according to the first memory cleaning policy comprises:

3. The method according to claim 2, wherein the controlling the mobile terminal to restart according to a first restart mode to clean up memory fragments comprises:

4. The method according to any one of claims 1 to 3, wherein before performing memory fragmentation cleaning on the mobile terminal according to the second memory cleaning policy, the method further comprises:

outputting memory cleaning prompt information;

and when receiving the confirmation clearing instruction, executing the step of clearing the memory fragments of the mobile terminal according to a second memory clearing strategy.

5. The method of claim 4, further comprising:

and when a clearing canceling instruction is received, clearing memory fragments of the mobile terminal according to the first memory clearing strategy.

6. The method according to any one of claims 1 to 3, wherein the performing memory fragmentation cleaning on the mobile terminal according to the second memory cleaning policy comprises at least one of:

controlling the mobile terminal to restart according to a second restart mode so as to clean up memory fragments;

and if detecting that the foreground running application exists, cleaning the memory fragments of the first application to be cleaned.

7. The method according to any one of claims 1 to 3, wherein the performing memory fragmentation cleaning on the mobile terminal according to the second memory cleaning policy comprises:

determining a second application to be cleaned;

and cleaning the memory fragments of the second application to be cleaned.

8. The method according to any one of claims 1 to 3, further comprising:

outputting a memory cleaning time setting interface;

acquiring target memory cleaning time;

9. A mobile terminal, characterized in that the mobile terminal comprises: memory, processor, wherein the memory has stored thereon a program which, when executed by the processor, carries out the steps of the memory cleaning method according to any one of claims 1 to 8.

10. A readable storage medium, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the memory cleaning method according to any one of claims 1 to 8.