CN111581159A - Junk file cleaning method, terminal and computer storage medium - Google Patents

Junk file cleaning method, terminal and computer storage medium Download PDF

Info

Publication number
CN111581159A
CN111581159A CN202010324957.7A CN202010324957A CN111581159A CN 111581159 A CN111581159 A CN 111581159A CN 202010324957 A CN202010324957 A CN 202010324957A CN 111581159 A CN111581159 A CN 111581159A
Authority
CN
China
Prior art keywords
junk
cleaning
application
file
files
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202010324957.7A
Other languages
Chinese (zh)
Inventor
朱璐娜
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Microphone Holdings Co Ltd
Shenzhen Transsion Holdings Co Ltd
Original Assignee
Shenzhen Microphone Holdings Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Microphone Holdings Co Ltd filed Critical Shenzhen Microphone Holdings Co Ltd
Priority to CN202010324957.7A priority Critical patent/CN111581159A/en
Publication of CN111581159A publication Critical patent/CN111581159A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
    • G06F16/162—Delete operations
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
    • G06F9/5016—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals the resource being the memory

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Mathematical Physics (AREA)
  • Human Computer Interaction (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Stored Programmes (AREA)

Abstract

The application relates to a junk file cleaning method, a terminal and a computer storage medium, wherein the junk file cleaning method is applied to the terminal and comprises the following steps: monitoring an event of the terminal; analyzing at least one preset scene in the terminal according to the event; and clearing the junk files based on the preset scene. By the method, the junk files can be cleared based on different scenes, and users can clear the junk files at any time and quickly in the process of using the terminal.

Description

Junk file cleaning method, terminal and computer storage medium
Technical Field
The application relates to the technical field of terminals, in particular to a junk file cleaning method, a terminal and a computer storage medium.
Background
With the rapid development of terminal technology, the functions of mobile terminals such as mobile phones and tablet computers are also improved, and the mobile terminals become one of the common tools in daily life and work.
In the process of using the terminal, junk files are generated due to various operations, the junk files occupy the memory of the terminal to a certain extent and affect the operation performance of the terminal, but the current way of cleaning the junk files is single, so that a user cannot clean the junk files at any time and quickly in the process of using the terminal, accumulation of the junk files is caused, and user experience is affected.
Disclosure of Invention
In view of the above technical problems, the present application provides a junk file cleaning method, a terminal, and a computer storage medium, which enable a user to quickly clean a junk file at any time during a terminal using process.
In order to solve the above technical problem, the present application provides a junk file cleaning method, including:
monitoring an event of the terminal;
analyzing at least one preset scene in the terminal according to the event;
and clearing the junk files based on the preset scene.
Wherein the event comprises at least one of:
memory use value, interface opening operation, application management operation and cleaning interval timing duration of junk files.
Wherein the at least one preset scene comprises at least one of:
opening a cleaning interface, enabling the cleaning interval of the junk files to reach a preset time length, enabling the memory use value to be larger than or equal to a preset value, installing the application, uninstalling the application, deleting the application content and quitting the application.
Wherein, clear up junk file based on the preset scene includes:
prompting a junk file to be cleaned based on the preset scene;
and cleaning the junk files to be cleaned according to the received operation.
Wherein, the prompting of the junk file to be cleaned based on the preset scene comprises the following steps:
when the current corresponding preset scene is a cleaning interface, classifying and displaying garbage files to be cleaned according to different file types on the cleaning interface; and/or the presence of a gas in the gas,
when the current corresponding preset scene is that the cleaning interval of the junk files reaches the preset time length, prompting the junk files to be cleaned according to the quantity of the junk files accumulated in the preset time length; and/or the presence of a gas in the gas,
when the current corresponding preset scene is that the memory use value is greater than or equal to the preset value, prompting the garbage file to be cleaned according to the current memory use value; and/or the presence of a gas in the gas,
when the current corresponding preset scene is the installation application, prompting the junk files to be cleaned according to the currently installed application; and/or the presence of a gas in the gas,
and when the current corresponding preset scene is the uninstalled application, prompting the junk files to be cleaned according to the currently uninstalled application.
Wherein, when the cleaning interval of the garbage file in the currently corresponding preset scene reaches a preset time length and/or the currently corresponding preset scene is a memory usage value greater than or equal to a preset value, the garbage file to be cleaned is cleaned according to the received operation, including:
opening an interface for cleaning the junk files to be cleaned according to the prompt;
and clearing the corresponding junk files according to the operation received by the interface.
When the current corresponding preset scene is an installation application and/or when the current corresponding preset scene is an uninstallation application, clearing the junk file to be cleared according to the received operation, including:
and clearing the corresponding junk files according to the operation received by the application management interface.
Wherein, the clearing the garbage file to be cleared according to the received operation comprises:
when the received operation is a cleaning operation, cleaning a junk file corresponding to the cleaning operation; and/or the presence of a gas in the gas,
and when the received operation is the neglect operation, the garbage file to be cleaned is not cleaned.
The application provides a second junk file cleaning method, which includes:
monitoring an application management event;
and when the monitored application management event conforms to a corresponding scene in at least one application management scene, cleaning the junk files according to the corresponding application management scene.
In a second method for cleaning junk files, cleaning junk files according to corresponding application management scenarios includes:
prompting a junk file to be cleaned according to the corresponding application management scene;
and cleaning the junk files to be cleaned according to the received operation.
In a second junk file cleaning method, the cleaning the junk file to be cleaned according to the received operation includes:
and clearing the corresponding junk files according to the operation received by the application management interface.
The present application further provides a terminal, including a memory and a processor, where the memory is configured to store at least one program instruction, and the processor is configured to implement the garbage file cleaning method as described above by loading and executing the at least one program instruction.
The present application further provides a computer storage medium having computer program instructions stored thereon; the computer program instructions, when executed by a processor, implement the garbage file cleaning method as described above.
As described above, the junk file cleaning method, the terminal and the computer storage medium of the present application monitor an event of the terminal, analyze at least one preset scene in the terminal according to the event, and clean the junk file based on the preset scene. By the method, the junk files can be cleared based on different scenes, and users can clear the junk files at any time and quickly in the process of using the terminal.
On the other hand, the junk file cleaning method, the terminal and the computer storage medium monitor the application management events, and when the monitored application management events conform to corresponding scenes in at least one application management scene, the junk files are cleaned according to the corresponding application management scenes. By the method, the junk files can be cleared based on different application management scenes, and users can clear the junk files at any time and quickly in the application using process.
Drawings
Fig. 1 is a flowchart illustrating a garbage file cleaning method according to a first embodiment;
FIG. 2 is a flowchart illustrating a garbage file cleaning method according to a second embodiment;
fig. 3 is one of the structural diagrams of the terminal shown according to the third embodiment;
fig. 4 is a second schematic structural diagram of the terminal shown in fig. 3.
Detailed Description
The following description of the embodiments of the present application is provided for illustrative purposes, and other advantages and capabilities of the present application will become apparent to those skilled in the art from the present disclosure.
In the following description, reference is made to the accompanying drawings that describe several embodiments of the application. It is to be understood that other embodiments may be utilized and that mechanical, structural, electrical, and operational changes may be made without departing from the spirit and scope of the present application. The following detailed description is not to be taken in a limiting sense, and the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.
First embodiment
Fig. 1 is a flowchart illustrating a garbage file cleaning method according to a first embodiment. Referring to fig. 1, the junk file cleaning method of the embodiment is applied to a terminal, and includes:
step 110, monitoring an event of the terminal;
step 120, analyzing at least one preset scene in the terminal according to the event;
and step 130, cleaning the junk files based on the preset scene.
The event comprises at least one preset event in a memory use value, an interface opening operation, an application management operation and a cleaning interval timing duration of the junk file.
Various events of the terminal, such as a plurality of scenes corresponding to the operation and use processes, are preset, and when the operation and use processes of the terminal are consistent with the scenes, the junk files to be cleaned can be timely and accurately identified, so that a user is prompted.
In this embodiment, the at least one preset scenario includes at least one of:
opening a cleaning interface, enabling the cleaning interval of the junk files to reach a preset time length, enabling the memory use value to be larger than or equal to a preset value, installing the application, uninstalling the application, deleting the application content and quitting the application.
The preset scene is the opening of the cleaning interface, the corresponding preset event to be monitored is interface opening operation, and when the interface opening operation is the operation of opening the cleaning interface, the preset scene of opening the cleaning interface is met. The preset scene is that the cleaning interval of the junk files reaches the preset time length, the corresponding preset event to be monitored is the cleaning interval timing time length of the junk files, and when the cleaning interval timing time length of the junk files reaches the preset time length, the preset scene that the cleaning interval of the junk files reaches the preset time length is met. The preset scene is that the memory usage value is greater than or equal to the preset value, the corresponding preset event to be monitored is the memory usage value, and when the memory usage value exceeds the preset value, the preset scene is in accordance with the memory usage value being greater than or equal to the preset value. The preset scene is an installation application, the corresponding preset event to be monitored is an application management operation, and when the application management operation is the operation of installing the application, the preset scene of installing the application is met. The preset scene is an uninstalled application, the corresponding preset event to be monitored is an application management operation, and when the application management operation is the operation of uninstalling the application, the preset scene of the uninstalled application is met. The preset scene is application content deletion, the corresponding preset event to be monitored is application management operation, and when the application management operation is application content deletion, the preset scene is in accordance with the application content deletion. The preset scene is an exit application, the corresponding preset event to be monitored is an application management operation, and when the application management operation is the operation of exiting the application, the preset scene of exiting the application is met.
When the cleaning interface is opened, the user can manually clean the junk files. A certain amount of junk files may accumulate when the clearance interval for junk files reaches a preset time period, such as 3 days or other time period set by the system or set by the user. When the memory usage value is greater than or equal to a predetermined value, the garbage file may occupy more memory, and the predetermined value is, for example, 60% of the total memory value or other values set by the system or the user. When installing an application, data such as an installation package that needs to be used may be left. When an application is uninstalled, an uninstall residual file may be left. When application content is deleted, there may be some content associated with the deleted content that is not deleted. Upon exiting the application, some unused cache data may be left. That is to say, under these scenes, the user has a need to clear up the junk files, and through the setting of these preset scenes, the vast majority of situations that the junk files may be generated or the junk files are accumulated more in the terminal can be covered, and the clear-up scenes run through the actual use process of the terminal, so that the junk files can be cleared up in time and quickly.
In this embodiment, the step 130 of cleaning up the junk file based on the preset scene may include:
prompting a junk file to be cleaned based on a preset scene;
and cleaning the garbage files to be cleaned according to the received operation.
When the monitored preset event conforms to a corresponding scene in at least one preset scene, the junk file to be cleaned is prompted according to the corresponding preset scene, that is, under different preset scenes, prompting can be performed in different modes.
When the current corresponding preset scene is the cleaning interface, classifying and displaying the garbage files to be cleaned according to different file types on the cleaning interface. When a user wants to actively clean the junk files, a cleaning interface can be opened, at the moment, all the junk files in the terminal are searched, the searched junk files are classified and displayed according to different file types, the file types comprise cache junk, memory junk, waste application program installation packages and the like, and when the junk files are displayed, the prompt information comprises the display file types, the corresponding junk file number, the junk file details and the like, so that the user can operate as required.
And when the cleaning interval of the garbage files reaches the preset time length in the current corresponding preset scene, prompting the garbage files to be cleaned according to the quantity of the garbage files accumulated in the preset time length. The preset time is, for example, 3 days or other time set by a system or a user, timing is restarted after cleaning the junk files each time, and when the timing time reaches the preset time, prompting is performed, including prompting the number of the junk files accumulated in the preset time, and also prompting how to perform the operation of junk cleaning. The prompt interface may be displayed in a drop-down menu or in a top menu bar.
And when the current corresponding preset scene is that the memory use value is greater than or equal to the preset value, prompting the garbage file to be cleaned according to the current memory use value. The preset value is, for example, 60% of the total memory value or other values set by the system or the user, and when the memory usage value exceeds the preset value, a prompt is made, including prompting the current memory usage value or prompting the ratio of the current memory usage value to the total memory, and also prompting how to perform garbage cleaning operation. The prompt interface may be displayed in a drop-down menu or in a top menu bar.
And when the current corresponding preset scene is the installation application, prompting the junk files to be cleaned according to the currently installed application. When the application management operation is the operation of installing the application, the preset scene of installing the application is met, at the moment, whether a waste application program installation package exists in the terminal is detected, if the waste application program installation package is detected, prompt is carried out, and the waste application program installation package can be the installation package of the application installed at this time or all waste application program installation packages in the terminal. And when prompting, prompting the occupied space of the installation package of the currently installed application. The prompt interface may be displayed at the current application management interface.
And when the current corresponding preset scene is the uninstalled application, prompting the junk files to be cleaned according to the currently uninstalled application. And when the application management operation is the operation of unloading the application, the preset scene of the unloading application is met, whether the junk file corresponding to the application exists in the terminal is detected, if so, prompting is carried out, and during prompting, the occupied space of the residual junk file of the currently unloaded application is prompted. The prompt interface may be displayed at the current application management interface.
The above several preset scenes only need to satisfy one type, and can prompt the cleaning of the junk files, if two or more types are simultaneously satisfied, the prompt is respectively performed, for example, when the current corresponding preset scene is that the cleaning interval of the junk files reaches the preset time length and the application is installed, the current application management interface prompts the junk files to be cleaned, and then the current application management interface still continues to prompt the junk files to be cleaned when the cleaning interval reaches the preset time length.
In actual implementation, the prompts of different preset scenes may be the same, for example, when at least one preset scene is satisfied, a preset interface is displayed to prompt a junk file to be cleaned.
After the junk files to be cleaned are prompted, the user can perform relevant operations to process the junk files.
When the current corresponding preset scene is the cleaning interface, cleaning the garbage files to be cleaned according to the received operation, including:
and clearing the junk files of the corresponding file types according to the operation received by the clearing interface.
When the current corresponding preset scene is the cleaning interface, the garbage files to be cleaned are classified and displayed on the cleaning interface according to different file types, and at the moment, a user can clean the corresponding garbage files on the cleaning interface according to the file types, including cleaning part of the garbage files or cleaning all the garbage files.
When the cleaning interval of the garbage file in the corresponding preset scene reaches a preset time length and/or the corresponding preset scene is greater than or equal to a preset memory use value, cleaning the garbage file to be cleaned according to the received operation, including:
receiving an operation of opening an interface for cleaning junk files to be cleaned;
and cleaning the corresponding junk files according to the operation received by the interface.
And displaying a prompt interface in a pull-down menu or a top menu bar when the cleaning interval of the garbage file reaches a preset time length and/or the memory usage value of the current corresponding preset scene is greater than or equal to a preset value. In the prompt interface, a user can click a 'clear' button to directly clear junk files, or further open an interface for clearing the junk files to be cleared, the interface is operated to clear the junk files, in the interface, the junk files to be cleared can be classified and displayed according to different file types, and the user can clear corresponding junk files according to the file types, including clearing part of the junk files or clearing all the junk files.
When the preset scene that corresponds at present is installation application, and/or, when the preset scene that corresponds at present is uninstallation application, clear up the junk file of treating the clearance according to the operation of receiving, include:
and clearing the corresponding junk files according to the operation received by the application management interface.
When the current corresponding preset scene is the installation application and/or when the current corresponding preset scene is the uninstallation application, the prompt can be directly performed on the current application management interface, and the user can clean the corresponding junk files by operating the application management interface. The application management interface may be different according to different application management operations, for example, when the application is uninstalled, the application management interface may be a desktop, and when the application is installed, the application management interface may be an interface of an application mall.
In an embodiment, after the to-be-processed junk file is prompted, if the received operation is a cleaning operation, the junk file corresponding to the cleaning operation is cleaned, and if the received operation is an ignoring operation, the to-be-cleaned junk file is not cleaned and can be prompted in another prompting mode. For example, the user selects to ignore the operation after installing the application, and if the installation package is not cleared, the user may prompt when the user opens the clearing interface for manual clearing.
In actual implementation, in step 130, the junk file may be automatically cleared in the background according to the preset scenes without prompting the user, all the preset scenes may be automatically cleared in the background, or the junk file may be automatically cleared in the background when the current corresponding preset scene is the designated preset scene. For example, when the currently corresponding preset scene is a preset time period when the cleaning interval of the junk files reaches the preset time period, and/or when the currently corresponding preset scene is a preset memory usage value greater than or equal to the preset value, the junk files can be automatically cleaned in the background, so that the junk file cleaning process of different scenes can better meet the use habits of users.
The junk file cleaning method of the embodiment prompts the junk files to be cleaned based on at least one preset scene, and cleans the junk files to be cleaned according to the received operation, so that the junk files can be cleaned based on different scenes, and a user can clean the junk files at any time and quickly in the process of using the terminal.
Second embodiment
Fig. 2 is a flowchart illustrating a garbage file cleaning method according to a second embodiment. Referring to fig. 2, the junk file cleaning method of the embodiment is applied to a terminal, and includes:
step 210, prompting the garbage file to be cleaned based on at least one application management scene.
A plurality of scenes corresponding to the application management process of the terminal are preset, and when the operation and use processes of the terminal are consistent with the scenes, the junk files to be cleaned can be timely and accurately identified in the application use process, so that a user is prompted.
In this embodiment, the at least one application management scenario includes at least one of installing an application, uninstalling an application, deleting application content, and exiting an application. When installing an application, data such as an installation package that needs to be used may be left. When an application is uninstalled, an uninstall residual file may be left. When application content is deleted, there may be some content associated with the deleted content that is not deleted. Upon exiting the application, some unused cache data may be left. That is to say, under these scenes, the user has a need to clear the junk files, and through the setting of these preset scenes, the vast majority of situations that the junk files may be generated during the application use process can be covered, and the clear scenes run through the actual application process of the application, so that the junk files can be cleared in time and quickly.
In this embodiment, the process of prompting the garbage file to be cleaned based on at least one application management scenario may include:
monitoring an application management event;
and when the monitored application management event conforms to a corresponding scene in at least one application management scene, prompting the junk files to be cleaned according to the corresponding application management scene.
Wherein, corresponding to at least one application management scene, the application management event comprises at least one of an operation of installing the application, an operation of uninstalling the application, an operation of deleting the application content and an operation of exiting the application. When the monitored application management event conforms to a corresponding scene in at least one application management scene, the junk files to be cleaned are prompted according to the corresponding application management scene, that is, under different application management scenes, prompting can be performed in different modes.
And when the current corresponding preset scene is the installation application, prompting the junk files to be cleaned according to the currently installed application. When the preset scene of the application is met, whether a waste application program installation package exists in the terminal is detected, if the waste application program installation package is detected, prompt is carried out, and the waste application program installation package can be the installation package of the application installed at this time or all waste application program installation packages in the terminal. And when prompting, prompting the occupied space of the installation package of the currently installed application. The prompt interface may be displayed at the current application management interface.
And when the current corresponding preset scene is the uninstalled application, prompting the junk files to be cleaned according to the currently uninstalled application. When the preset scene of the uninstalled application is met, whether a junk file corresponding to the application exists in the terminal is detected, if so, prompting is carried out, and during prompting, the occupied space of the residual junk file of the currently uninstalled application is prompted. The prompt interface may be displayed at the current application management interface.
When the current corresponding preset scene is application content deletion, for example, chat records are deleted, and the junk files to be cleaned are prompted according to the deleted content. And when the preset scene of the deleted application content is met, detecting the content which is related to or repeated with the deleted content in the current application, and prompting if the content is detected, wherein during prompting, the occupied space of the junk file corresponding to the deleted content is prompted. The prompt interface may be displayed at the current application management interface.
When the current corresponding preset scene is the application quit, the junk files to be cleaned are prompted according to data generated in the application using period. And when the preset scene of exiting the application is met, detecting a junk file in the data generated in the period of using the application, and if the junk file is detected, prompting, wherein the prompting comprises the occupied space of the junk file generated in the period of using the application. The prompt interface may be displayed at the current application management interface.
The cleaning of the junk files can be prompted only by meeting one preset scene. In actual implementation, the prompts of different application management scenarios may also be the same, for example, when at least one application management scenario is satisfied, a preset interface is displayed to prompt a junk file to be cleaned.
And step 220, cleaning the garbage files to be cleaned according to the received operation.
After the junk files to be cleaned are prompted, the user can perform relevant operations to process the junk files. In this embodiment, the prompt may be directly performed on the current application management interface, and the user may clean the corresponding junk file by performing an operation on the application management interface. The application management interface may be different according to different application management events, for example, when an application is uninstalled, the application management interface may be a desktop, when an application is installed, the application management interface may be an interface of an application mall, and when application content is deleted and the application exits, the application management interface is an interface of a current application.
In an embodiment, after the to-be-processed junk file is prompted, if the received operation is a cleaning operation, the junk file corresponding to the cleaning operation is cleaned, and if the received operation is an ignoring operation, the to-be-cleaned junk file is not cleaned and can be prompted in another prompting mode. For example, the prompt may be made when the user opens the cleaning interface for manual cleaning.
The junk file cleaning method, the terminal and the computer storage medium of the embodiment prompt the junk file to be cleaned based on at least one application management scene, and clean the junk file to be cleaned according to the received operation. By the method, the junk files can be cleared based on different application management scenes, and users can clear the junk files at any time and quickly in the application using process.
Third embodiment
Fig. 3 is one of the structural diagrams of the terminal shown according to the third embodiment. Referring to fig. 3, the terminal 10 of the present embodiment includes a memory 102 and a processor 106, where the memory 102 is configured to store at least one program instruction, and the processor 106 is configured to implement the garbage file cleaning method according to the first embodiment to the second embodiment by loading and executing the at least one program instruction.
Referring to fig. 4, in actual implementation, the terminal 10 includes a memory 102, a memory controller 104, one or more processors 106 (only one of which is shown), a peripheral interface 108, a radio frequency module 150, a positioning module 112, a camera module 114, an audio module 116, a screen 118, and a key module 160. These components communicate with each other via one or more communication buses/signal lines 122.
It will be appreciated that the configuration shown in fig. 4 is merely illustrative and that terminal 10 may include more or fewer components than shown in fig. 4 or may have a different configuration than shown in fig. 4. The components shown in fig. 4 may be implemented in hardware, software, or a combination thereof.
The memory 102 may be used to store software programs and modules, such as program instructions/modules corresponding to the garbage file cleaning method in the embodiment of the present application, and the processor 106 executes various functional applications and data processing by executing the software programs and modules stored in the storage controller 104, so as to implement the above garbage file cleaning method.
The memory 102 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 102 may further include memory located remotely from the processor 106, which may be connected to the terminal 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof. Access to the memory 102 by the processor 106, and possibly other components, may be under the control of the memory controller 104.
Peripheral interface 108 couples various input/output devices to the CPU and memory 102. The processor 106 executes various software, instructions within the memory 102 to perform various functions of the terminal 10 and to perform data processing.
In some embodiments, the peripheral interface 108, the processor 106, and the memory controller 104 may be implemented in a single chip. In other examples, they may be implemented separately from the individual chips.
The rf module 150 is used for receiving and transmitting electromagnetic waves, and implementing interconversion between the electromagnetic waves and electrical signals, so as to communicate with a communication network or other devices. Rf module 150 may include various existing circuit elements for performing these functions, such as an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a Subscriber Identity Module (SIM) card, memory, and so forth. The rf module 150 may communicate with various networks such as the internet, an intranet, a wireless network, or with other devices via a wireless network. The wireless network may comprise a cellular telephone network, a wireless local area network, or a metropolitan area network. The Wireless network may use various Communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile Communication (GSM), Enhanced Data GSM Environment (EDGE), wideband Code division multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), bluetooth, Wireless Fidelity (WiFi) (e.g., Institute of Electrical and Electronics Engineers (IEEE) standard IEEE802.11 a, IEEE802.11 b, IEEE802.1 g, and/or IEEE802.11 n), Voice over Internet Protocol (VoIP), world wide Internet Microwave Access (Microwave for Wireless Communication), other suitable protocols for short message service (Max), and any other suitable Communication protocols, and may even include those protocols that have not yet been developed.
The positioning module 112 is used for acquiring the current position of the terminal 10. Examples of the positioning module 112 include, but are not limited to, a global positioning satellite system (GPS), a wireless local area network-based positioning technology, or a mobile communication network-based positioning technology.
The camera module 114 is used to take a picture or video. The pictures or videos taken may be stored in the memory 102 and transmitted through the radio frequency module 150.
Audio module 116 provides an audio interface to a user that may include one or more microphones, one or more speakers, and audio circuitry. The audio circuitry receives audio data from the peripheral interface 108, converts the audio data to electrical information, and transmits the electrical information to the speaker. The speaker converts the electrical information into sound waves that the human ear can hear. The audio circuitry also receives electrical information from the microphone, converts the electrical information to voice data, and transmits the voice data to the peripheral interface 108 for further processing. The audio data may be retrieved from the memory 102 or through the radio frequency module 150. In addition, the audio data may also be stored in the memory 102 or transmitted through the radio frequency module 150. In some examples, the audio module 116 may also include an earphone jack for providing an audio interface to a headset or other device.
The screen 118 provides an output interface between the terminal 10 and the user. In particular, screen 118 displays video output to the user, the content of which may include text, graphics, video, and any combination thereof. Some of the output results are for some of the user interface objects. It is understood that the screen 118 may also include a touch screen. The touch screen provides both an output and an input interface between the terminal 10 and a user. In addition to displaying video output to users, touch screens also receive user input, such as user clicks, swipes, and other gesture operations, so that user interface objects respond to these user input. The technique of detecting user input may be based on resistive, capacitive, or any other possible touch detection technique. Specific examples of touch screen display units include, but are not limited to, liquid crystal displays or light emitting polymer displays.
The key module 160 also provides an interface for user input to the terminal 10, and the user can press different keys to cause the terminal 10 to perform different functions.
The present application further provides a computer storage medium having computer program instructions stored thereon; the computer program instructions, when executed by a processor, implement the garbage file cleaning method according to the first to second embodiments.
In practical implementation, the computer storage medium is applied to the terminal shown in fig. 3 or fig. 4, so that the junk files can be cleared based on different scenes, and a user can clear the junk files at any time and quickly in the process of using the terminal.
The above embodiments are merely illustrative of the principles and utilities of the present application and are not intended to limit the application. Any person skilled in the art can modify or change the above-described embodiments without departing from the spirit and scope of the present application. Accordingly, it is intended that all equivalent modifications or changes which can be made by those skilled in the art without departing from the spirit and technical concepts disclosed in the present application shall be covered by the claims of the present application.

Claims (10)

1. A junk file cleaning method is applied to a terminal and is characterized by comprising the following steps:
monitoring an event of the terminal;
analyzing at least one preset scene in the terminal according to the event;
and clearing the junk files based on the preset scene.
2. A junk file cleaning method in accordance with claim 1 wherein the event comprises at least one of:
memory use value, interface opening operation, application management operation and cleaning interval timing duration of junk files.
3. A junk file cleaning method according to claim 1 wherein the at least one predetermined scenario comprises at least one of:
opening a cleaning interface, enabling the cleaning interval of the junk files to reach a preset time length, enabling the memory use value to be larger than or equal to a preset value, installing the application, uninstalling the application, deleting the application content and quitting the application.
4. The junk file cleaning method according to claim 1 wherein the cleaning of junk files based on the predetermined scenario comprises:
prompting a junk file to be cleaned based on the preset scene;
and cleaning the junk files to be cleaned according to the received operation.
5. The junk file cleaning method according to claim 4 wherein the prompting of the junk file to be cleaned based on the predetermined scenario comprises:
when the current corresponding preset scene is a cleaning interface, classifying and displaying garbage files to be cleaned according to different file types on the cleaning interface; and/or the presence of a gas in the gas,
when the current corresponding preset scene is that the cleaning interval of the junk files reaches the preset time length, prompting the junk files to be cleaned according to the quantity of the junk files accumulated in the preset time length; and/or the presence of a gas in the gas,
when the current corresponding preset scene is that the memory use value is greater than or equal to the preset value, prompting the garbage file to be cleaned according to the current memory use value; and/or the presence of a gas in the gas,
when the current corresponding preset scene is the installation application, prompting the junk files to be cleaned according to the currently installed application; and/or the presence of a gas in the gas,
and when the current corresponding preset scene is the uninstalled application, prompting the junk files to be cleaned according to the currently uninstalled application.
6. The junk file cleaning method according to claim 4 or 5, wherein the currently corresponding preset scenario is that a cleaning interval of the junk file reaches a preset time length, and/or when the currently corresponding preset scenario is that a memory usage value is greater than or equal to a preset value, the cleaning the junk file to be cleaned according to the received operation comprises:
opening an interface for cleaning the junk files to be cleaned according to the prompt;
and clearing the corresponding junk files according to the operation received by the interface.
7. The junk file cleaning method according to claim 4 or 5, wherein when the current corresponding preset scenario is an installation application, and/or when the current corresponding preset scenario is an uninstallation application, the cleaning the junk file to be cleaned according to the received operation comprises:
and clearing the corresponding junk files according to the operation received by the application management interface.
8. The junk file cleaning method of claim 4 wherein the cleaning the junk file to be cleaned according to the received operation comprises:
when the received operation is a cleaning operation, cleaning a junk file corresponding to the cleaning operation; and/or the presence of a gas in the gas,
and when the received operation is the neglect operation, the garbage file to be cleaned is not cleaned.
9. A terminal, comprising a memory for storing at least one program instruction and a processor for implementing the garbage file cleaning method according to any one of claims 1 to 8 by loading and executing the at least one program instruction.
10. A computer storage medium having computer program instructions stored thereon; the computer program instructions, when executed by a processor, implement the garbage file cleaning method of any one of claims 1 to 8.
CN202010324957.7A 2020-04-23 2020-04-23 Junk file cleaning method, terminal and computer storage medium Pending CN111581159A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010324957.7A CN111581159A (en) 2020-04-23 2020-04-23 Junk file cleaning method, terminal and computer storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010324957.7A CN111581159A (en) 2020-04-23 2020-04-23 Junk file cleaning method, terminal and computer storage medium

Publications (1)

Publication Number Publication Date
CN111581159A true CN111581159A (en) 2020-08-25

Family

ID=72111578

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010324957.7A Pending CN111581159A (en) 2020-04-23 2020-04-23 Junk file cleaning method, terminal and computer storage medium

Country Status (1)

Country Link
CN (1) CN111581159A (en)

Similar Documents

Publication Publication Date Title
CN109213539B (en) Memory recovery method and device
CN107291586B (en) Application program analysis method and device
CN107797841B (en) Window control method and device, terminal equipment and storage medium
CN107465841B (en) Fault information reporting method and terminal
CN107562539B (en) Application program processing method and device, computer equipment and storage medium
CN107871015B (en) Log data processing method and device, terminal and readable storage medium
CN108334345B (en) Application processing method and device, readable storage medium and mobile terminal
CN106341365B (en) New account information deleting method and device
CN113039516A (en) Method and device for processing application program and electronic equipment
CN105468504A (en) Program test method and device
CN112805988B (en) Call control method and device, computer readable storage medium and electronic equipment
CN112997471B (en) Audio channel switching method and device, readable storage medium and electronic equipment
CN110568925A (en) lock screen display control method, terminal and computer storage medium
CN110032430B (en) Application program processing method and device, electronic equipment and computer readable storage medium
CN109375995B (en) Application freezing method and device, storage medium and electronic equipment
CN111581159A (en) Junk file cleaning method, terminal and computer storage medium
CN113039517A (en) Audio resource calling method and device and electronic equipment
CN111143580B (en) Multimedia data storage method and device, storage medium and electronic equipment
CN113170305B (en) Application downloading and installing method and related product
CN113672301A (en) Application processing method, mobile terminal and storage medium
CN113039524A (en) Audio resource processing method and device, computer readable storage medium and electronic equipment
CN106304087B (en) Anti-wifi hijacking method and device
CN107204882B (en) Method and equipment for filtering data packet and mobile terminal
CN112997131A (en) Audio resource release method and device and electronic equipment
CN111290672A (en) Image display method and device, storage medium and terminal

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination