CN107679161B - File processing method of electronic terminal and electronic terminal - Google Patents
File processing method of electronic terminal and electronic terminal Download PDFInfo
- Publication number
- CN107679161B CN107679161B CN201710898462.3A CN201710898462A CN107679161B CN 107679161 B CN107679161 B CN 107679161B CN 201710898462 A CN201710898462 A CN 201710898462A CN 107679161 B CN107679161 B CN 107679161B
- Authority
- CN
- China
- Prior art keywords
- file
- event
- target file
- determining
- application program
- 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.)
- Active
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
Abstract
The invention provides an electronic terminal file processing method and an electronic terminal, wherein the method comprises the steps of obtaining record information corresponding to a target file, wherein the record information is used for recording a th event that a history file corresponding to the target file is deleted and second events which occur after the th event is ended each time, the history file and the target file are files which are stored in a th path and are identical, the second events are events in a preset event set, determining that the frequency of occurrence of the second events corresponding to th events is larger than a preset value, and determining that the target file is a non-junk file when the junk file is selected.
Description
Technical Field
The present invention relates to electronic terminals, and in particular, to a file processing method for types of electronic terminals and an electronic terminal.
Background
An electronic terminal is understood to be a terminal having a processor and a memory, where the processor reads codes in the memory and can execute corresponding functions, and in particular, can run an operating system and application programs under the operating system. During operation, a file is created in memory.
However, since the suffix name, the path position and the like all depend on prior experience, if the experience is wrong, the file is deleted because the file is identified as a junk file, so that the operation of the program or the system is influenced, and in the related art, the influence of the file deletion on the operation of the program or the system is difficult to limit.
Disclosure of Invention
The invention provides a file processing method of an electronic terminal and the electronic terminal, which aim to solve the technical problem that the influence of file deletion on the operation of a program or a system is difficult to limit.
According to the aspect of the invention, there is provided a file processing method of kinds of electronic terminals, comprising:
acquiring recording information corresponding to a target file, wherein the recording information is used for recording th events that history files corresponding to the target file are deleted and second events that occur after the th event is ended each time, and the history files and the target file are files which are stored in a th path and are the same;
determining that the occurrence frequency of the second event corresponding to the th event is greater than a preset value;
and when the junk file is selected, determining that the target file is a non-junk file.
Optionally, the events in the preset event set include at least :
automatically creating another history file corresponding to the target file;
automatically deleting th file associated with the target file;
automatically deleting specific data recorded in a second file associated with the target file;
and the operation of the application program corresponding to the target file is wrong.
Optionally, before the obtaining of the record information corresponding to the target file, the method further includes:
detecting a kth event;
detecting a kth second event;
recording the kth event and the kth second event.
Optionally, before the step of detecting the kth second event, the method further includes:
and determining that the application program corresponding to the target file is closed and then opening the application program again.
Optionally, the application program corresponding to the target file includes at least :
an application program corresponding to the th path;
an application running in foreground upon detection of an th event;
the application with the most occupied memory when detecting the th event;
the application with the highest processor occupancy when the th event is detected.
Optionally, before the detecting the kth second event, determining that the preset time is not exceeded.
Optionally, before the detecting of the kth event, the method further comprises deleting the history file so that the kth event occurs.
Optionally, when selecting the junk file, before determining that the target file is a non-junk file, the method further includes:
and determining that the application program corresponding to the target file is not deleted.
According to a second aspect of the present invention, there is provided electronic terminals, comprising:
the acquisition module is used for acquiring recording information corresponding to a target file, wherein the recording information is used for recording th events that history files corresponding to the target file are deleted and times of second events which occur after the th event is ended, and the history files and the target file are files which are stored in a th path and are the same;
an determining module, configured to determine that the number of times of occurrence of the second event corresponding to the th event is greater than a preset value:
and the second determining module is used for determining that the target file is a non-junk file when the junk file is selected.
Optionally, the events in the preset event set include at least :
automatically creating another history file corresponding to the target file;
automatically deleting th file associated with the target file;
automatically deleting specific data recorded in a second file associated with the target file;
and the operation of the application program corresponding to the target file is wrong.
Optionally, the electronic terminal further includes:
an th detection module to detect a kth event;
the second detection module is used for detecting a kth second event;
and the recording module is used for recording the kth th event and the kth second event.
Optionally, the electronic terminal further includes:
and the third determining module is used for determining that the application program corresponding to the target file is opened again after being closed.
Optionally, the application program corresponding to the target file includes at least :
an application program corresponding to the th path;
an application running in foreground upon detection of an th event;
the application with the most occupied memory when detecting the th event;
the application with the highest processor occupancy when the th event is detected.
Optionally, the electronic terminal further includes:
and a fourth determination module for determining that the preset th time has not been exceeded.
Optionally, the electronic terminal further includes:
a deletion module to delete the history file such that the Kth event occurs.
According to a third aspect of the present invention there is provided electronic terminals comprising a memory, a processor and a computer program, the computer program being stored in the memory, the processor running the computer program to perform the methods of the various possible designs of aspects and .
According to a fourth aspect of the present invention, there is provided storage media comprising a readable storage medium and a computer program for implementing the methods of the various possible designs of aspects and .
According to the file processing method of the electronic terminal and the electronic terminal, the record information corresponding to the target file is obtained, the record information is used for recording th events that history files corresponding to the target file are deleted, second events occur after the th event is finished each time, the history files and the target file are files which are stored in a th path and are the same, the second event corresponding to the th event is determined to occur more times than a preset value, repeated occurrences of the second event after the th event are regarded as file deletion not to be independent events, and the repeated occurrences may affect the system or program operation, and further when the junk file is selected, the target file is determined to be a non-junk file, and the situation that the deletion of the target file due to the fact that the target file is determined to be the junk file affects the program or the system operation again is avoided.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic illustration of an application scenario of the present invention ;
FIG. 2 is a flowchart illustrating a file processing method of the electronic terminal according to the present invention;
FIG. 3 is a flowchart illustrating a file processing method of the electronic terminal according to a second embodiment of the present invention;
FIG. 4 is an interface schematic of a document processing interface of the electronic terminal of the present invention;
FIG. 5 is a schematic diagram of the electronic terminal of of the present invention;
FIG. 6 is a second schematic structural diagram of an electronic terminal according to the present invention;
fig. 7 is a schematic structural diagram three of the electronic terminal of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only partial embodiments of of the present invention, rather than all embodiments.
Furthermore, the terms "comprises" and "comprising," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a series of steps or elements is not necessarily limited to the expressly listed steps or elements, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
FIG. 1 is a diagram illustrating an application scenario of the present invention , where an electronic terminal may include a processor and a memory, where the processor may read code from the memory, run an operating system, and execute applications under the operating system.
Example 1
FIG. 2 is a flowchart illustrating a file processing method of an electronic terminal according to the present invention, and referring to FIG. 2, the method includes:
s11: and acquiring the record information corresponding to the target file.
Recording information for recording the th event that the history file corresponding to the target file is deleted and second events occurring after the th event is ended.
The th event is an event of deleting the history file, which may be an event generated according to a deleting operation by a user, or an event of automatically deleting the history file.
The second event may be understood as an event that occurs automatically by the terminal after the th event, and may specifically be an event in a preset event set, the type of the event is not limited to any , and the second event may be any event, and the time when the second event occurs may be any time after the th event ends.
The history file is the same file as the target file, and it is understood that the history file and the target file are the same file stored in the th path, in other words, the difference between the history file and the target file is that the target file is the file still stored at present, and the history file is the same file which has been deleted.
And S12, determining that the number of times of the second event corresponding to the th event is greater than a preset value.
The second event can be determined to have causal relationship with the th event by the above step S12, and the second event which repeatedly occurs for many times can be regarded as the influence of the deletion of the file on the operation of the program or the system in step .
S13: and when the junk file is selected, determining that the target file is a non-junk file.
Junk files are understood to be files that are considered to be deleted without being used. By determining the target file as a non-junk file, the file can be prevented from being deleted again, i.e., the influence of deleting the file on the operation of the program or the system can be avoided.
In the file processing method of the electronic terminal, by obtaining the record information corresponding to the target file, where the record information is used to record the th event that the history file corresponding to the target file is deleted, and the th second event that occurs after the th event is ended each time, where the history file and the target file are files that are stored in the th path and are the same, and determining that the number of times the second event corresponding to the th event occurs is greater than a preset value, the repeated occurrence of the second event after the th event is regarded as a file deletion not as an individual event, which may affect the system or the program operation, and further, when the junk file is selected, the target file is determined to be a non-junk file, so that the target file is prevented from being deleted due to being determined to be a junk file, which affects the program or the system operation again.
Example 2
FIG. 3 is a flowchart illustrating a second method for processing files of an electronic terminal according to the present invention, referring to FIG. 3, the method includes:
s21, the history file is deleted so that the Kth event occurs, wherein K is any integer.
The th event at the K time can be any times of deletion of the history file, and the th event can be understood as an event of deletion of the history file, which can be an event generated according to a deletion operation of a user, and can also be automatic deletion of the history file.
The history file is the same file as the target file, and it is understood that the history file and the target file are the same file stored in the th path, in other words, the difference between the history file and the target file is that the target file is the file still stored at present, and the history file is the same file which has been deleted.
Meanwhile, in the step S21, the terminal may automatically delete the history file to enable the th event to occur, and the application scenario may be that the history file is deleted as a test means, and in the specific implementation process, a corresponding code may be written in advance to implement a deletion test of a specific file, and by detecting an event occurring after deletion, if a second event occurs, recording is performed.
In other cases without implementing step S21, the th event may only be the deletion of the file under the normal operation of the application program, for example, regular deletion of the stored file by a part of the application program, that is, deletion of the file after reaching a preset regular time, the th event may also be the deletion of the garbage file that occurs when the occurrence frequency of the corresponding second event is not greater than the preset value and is determined to be the garbage file.
S22, the Kth event is detected.
In embodiments, the detection of the th event may be listening to the generation and execution of a delete command or listening to a file change, and the deletion of any file may be detected without departing from the scope of the present invention.
In examples, the file may be deleted M times, that is, M times of th events occur, but only N times of second events occur correspondingly, where M is an integer greater than or equal to 2, N is an integer less than M and greater than or equal to 1.
After step S22, step S25 may be implemented: the kth second event is detected.
The kth second event may be a second event occurring after the kth event ends.
After steps S22 and S25, step S26 may be performed to record the Kth event and the Kth second event.
Among embodiments, between step S22 and step S25, the method may further include:
s23: and determining that the application program corresponding to the target file is closed and then opening the application program again.
In the related art, in order to save storage space, files of a part of applications may be automatically cleaned after the applications are closed, however, the files may be files that are not necessary for program execution but are files that will be used when certain functions are executed, such as avatars in social applications, chat background pictures, and the like. Through the setting of the step S23, the detection of the second event can be applicable to such a scenario, so that the application range of the method of this embodiment is effectively widened, and for the automatically cleaned file after the application program is closed, the implementation of the step S23 can make the detection of the second event more targeted.
The application program corresponding to the target file may include at least :
the application program corresponding to the th path, the application program running in foreground when the th event is detected, the application program with the most occupied memory when the th event is detected, and the application program with the highest processor occupancy rate when the th event is detected.
The th path can be understood as a storage path of the history file and the object file, and in the related art, the generated file of the application program can be correspondingly stored under a specific file path, so that the corresponding relationship between the application program and the file can be accurately determined through the file path.
By using the event as a time node, an application program running in the foreground, an application program occupying the most memory, or an application program having the highest time processor occupancy rate is determined as an application program corresponding to the target file, and it can be understood that the application programs running in the foreground or the background have high association with deletion of the file.
Meanwhile, since there may be a plurality of corresponding applications, the corresponding step S23 may be understood that the closing and opening of the plurality of applications have occurred.
In another embodiments, the closing of the application program can also be understood to include both the application program not running in the foreground and the application program not running in the background, and the opening of the application program includes both the foreground running of the application program and the background running of the application program.
In contrast, in the embodiment adopting step S23, if the application is not closed or opened again, the corresponding second event is not recorded.
Among embodiments, between step S22 and step S25, the method may further include:
and S24, determining that the preset time is not exceeded.
Through the setting of the time, only a second event which occurs in hours after the event can be taken as a second event corresponding to the event, and the second event which occurs beyond the time can be regarded as an event with lower relevance to the event, so that the second event is not included in the recording range, and the pertinence of determining the second event can be improved, so that the recorded information can relatively more objectively and accurately reflect the condition of file processing.
In examples, the step S24 may be specifically limited to determine that the cumulative time of the booting operation of the electronic terminal exceeds the preset th time, which is applicable to a scenario where the electronic terminal is rebooted after being powered off for a long time, and may be listed as that the electronic terminal is stolen or is temporarily not used due to reasons such as going abroad, etc.
In an embodiment that employs both steps S23 and S24, wherein in , when the th event occurs, the accumulated calculation of the time after the th event is started, and in the accumulated calculation of the time, if the process of step S24 occurs and the th time is not reached, the recording can be performed, it can also be understood that the starting time of the accumulated calculation time is based on the end of the th event, the ending time is based on the occurrence of the second event, and step S24 needs to occur in the time period between the starting time and the ending time, and the time period between the starting time and the ending time needs to be less than the th time.
However, the sequence order is not limited to the sequence relation listed above, and step S24 may not be performed after step S23.
In another specific implementation, when the event is ended, the accumulated calculation is started relative to the time after the event is ended, and when step S24 occurs, the accumulated calculation time is suspended until the execution of step S24 is completed, and the accumulated calculation is not continued.
Other steps can be designed between the steps S22 and S25 according to different application scenarios and different application programs, which can be understood that the conditions for the second event and the logical relationship between the th event and the second event can be varied according to different application scenarios and different application programs.
For example, between step S22 and step S25, the following may be included: logging out and logging in the account of the corresponding application program; the invocation of the corresponding application by other applications is initiated, etc.
Further, steps S21 to S26 may be applied to recording any second event, and it is also understood that steps S21 to S26 may be repeatedly performed.
S27: and acquiring the record information corresponding to the target file.
Recording information for recording the th event that the history file corresponding to the target file is deleted and second events occurring after the th event is ended.
The th event is an event of deleting the history file, which may be an event generated according to a deleting operation by a user, or an event of automatically deleting the history file.
The second event may be understood as an event that occurs automatically by the terminal after the th event, and may specifically be an event in a preset event set, the type of the event is not limited to any , and the second event may be any event, and the time when the second event occurs may be any time after the th event ends.
The history file is the same file as the target file, and it is understood that the history file and the target file are the same file stored in the th path, in other words, the difference between the history file and the target file is that the target file is the file still stored at present, and the history file is the same file which has been deleted.
The events in the preset event set include at least :
the method comprises the steps of automatically creating another history file corresponding to the target file, automatically deleting th file related to the target file, automatically deleting data recorded in a second file related to the target file, and enabling an application program corresponding to the target file to run in an error.
For the application program in which the target corresponding another history file is automatically created, the application scenario may be understood as an application program applied to regularly delete files, such as an avatar picture or a chat background image of a social application program, in which, when the file, for example, the pictures, is deleted due to reaching a preset regular time or occurrence of a preset regular event, the application program runs, or a dialog box is opened, the file needs to be reloaded, that is, another history file corresponding to the target file is created again, it is apparent that the event is not a separate event.
For the application program corresponding to the target file to run wrongly, the application scenario may be understood that deletion of the file may cause operation failure and error reporting or flash quitting of the application program, and even if operation failure and error reporting or flash quitting of the application program is not caused, part of display content may not be displayed or part of functions may not be realized, which may not only be perceived by a user through interaction, such as abnormal sound, missing display content, no response to key clicking, and the like, but also may include that the user may not be perceived through interaction, such as collecting flow information, collecting battery information, and the like, and if these pieces of information are not collected, the user may not perceive.
The scene of the application of the file can be understood that if deletion of a single file causes deletion of other files or deletion of recorded data, the deletion of the single file can be regarded as existence of the target file and influence on existence or data change of other files, and the target file is no longer an independent event, so that the corresponding file is determined to be a non-junk file, linkage change of stored files can be effectively avoided, and the running safety of a system and an application program is guaranteed.
And S28, determining that the number of times of the second event corresponding to the th event is greater than a preset value.
The second event can be determined to have causal relationship with the th event by the above step S28, and the second event which repeatedly occurs for many times can be regarded as the influence of the deletion of the file on the operation of the program or the system in step .
S29: and when the junk file is selected, determining that the target file is a non-junk file.
Junk files are understood to be files that are considered to be deleted without being used. By determining the target file as a non-junk file, the file can be prevented from being deleted again, i.e., the influence of deleting the file on the operation of the program or the system can be avoided.
Referring to fig. 4, a scan process of junk files may be triggered by clicking a "storage space clear" button in the interface, wherein in embodiments, the implementation of step S27 may be triggered, in other embodiments, the implementation of step S29 may be triggered, and before the "junk file scan result" illustrated in fig. 4 is output and displayed, it may be understood that step S29 is completed.
Further, before step S29, the method may further include: and determining that the application program corresponding to the target file is not deleted. In this embodiment, if the corresponding application program is deleted, the information recorded based on the application program does not have a reference function, so that the corresponding target file does not need to be retained, and the corresponding recorded information can be deleted.
In the file processing method of the electronic terminal, by obtaining the record information corresponding to the target file, where the record information is used to record the th event that the history file corresponding to the target file is deleted, and the th second event that occurs after the th event is ended each time, where the history file and the target file are files that are stored in the th path and are the same, and determining that the number of times the second event corresponding to the th event occurs is greater than a preset value, the repeated occurrence of the second event after the th event is regarded as a file deletion not as an individual event, which may affect the system or the program operation, and further, when the junk file is selected, the target file is determined to be a non-junk file, so that the target file is prevented from being deleted due to being determined to be a junk file, which affects the program or the system operation again.
Example 3
Fig. 5 is a schematic structural diagram of an electronic terminal of the present invention, and referring to fig. 5, the electronic terminal includes:
an obtaining module 301, configured to obtain recording information corresponding to a target file, where the recording information is used to record an th event that a history file corresponding to the target file is deleted, and times of second events that occur after the th event is ended each time, where the history file and the target file are files that are stored in a th path and are the same;
an determining module 302, configured to determine that the number of times of occurrence of the second event corresponding to the event is greater than a preset value:
the second determining module 303 determines that the target file is a non-junk file when a junk file is selected.
The electronic terminal provided in this embodiment obtains record information corresponding to a target file, where the record information is used to record an th event that a history file corresponding to the target file is deleted, and second events that occur after the th event is ended each time, where the history file and the target file are files that are stored in a th path and are the same, and determines that the number of times the second event corresponding to the th event occurs is greater than a preset value, the repeatedly occurring file deletion of the second event after the th event is regarded as not an individual event, which may affect a system or program operation, and further determines that the target file is a non-junk file when the junk file is selected, thereby avoiding that the deletion of the target file due to the fact that the target file is determined as a junk file affects the program or system operation again.
Example 4
Fig. 6 is a schematic structural diagram of an electronic terminal of the present invention, and referring to fig. 6, the electronic terminal includes:
an obtaining module 407, configured to obtain recording information corresponding to a target file, where the recording information is used to record an th event that a history file corresponding to the target file is deleted, and times of second events that occur after the th event is ended each time, where the history file and the target file are files that are stored in a th path and are the same;
an determining module 408, configured to determine that the number of times of occurrence of the second event corresponding to the event is greater than a preset value:
the second determining module 409 is configured to determine that the target file is a non-junk file when a junk file is selected.
Optionally, the events in the preset event set include at least :
automatically creating another history file corresponding to the target file;
automatically deleting th file associated with the target file;
automatically deleting specific data recorded in a second file associated with the target file;
and the operation of the application program corresponding to the target file is wrong.
Optionally, the electronic terminal further includes:
an th detection module 402 for detecting a kth event;
a second detecting module 405, configured to detect a kth second event;
a recording module 406, configured to record the kth th event and the kth second event.
Optionally, the electronic terminal further includes:
a third determining module 403, configured to determine that the application corresponding to the target file is closed and then opened again.
Optionally, the application program corresponding to the target file includes at least :
an application program corresponding to the th path;
an application running in foreground upon detection of an th event;
the application with the most occupied memory when detecting the th event;
the application with the highest processor occupancy when the th event is detected.
Optionally, the electronic terminal further includes:
a fourth determination module 404 for determining that the preset th time has not been exceeded.
Optionally, the electronic terminal further includes:
a deleting module 401, configured to delete the history file, so that the kth event occurs.
The electronic terminal provided in this embodiment obtains record information corresponding to a target file, where the record information is used to record an th event that a history file corresponding to the target file is deleted, and second events that occur after the th event is ended each time, where the history file and the target file are files that are stored in a th path and are the same, and determines that the number of times the second event corresponding to the th event occurs is greater than a preset value, the repeatedly occurring file deletion of the second event after the th event is regarded as not an individual event, which may affect a system or program operation, and further determines that the target file is a non-junk file when the junk file is selected, thereby avoiding that the deletion of the target file due to the fact that the target file is determined as a junk file affects the program or system operation again.
Example 5
Fig. 7 is a schematic structural diagram of an electronic terminal in accordance with the present invention, referring to fig. 7, the electronic terminal 50 includes a processor 51 and a memory 52, wherein:
a memory 52 for storing a computer program, which may also be a flash (flash memory).
The processor 51 is configured to execute the execution instructions stored in the memory to implement the steps in the methods of the foregoing embodiments 1 and 2. Reference may be made in particular to the description relating to the preceding method embodiment.
Alternatively, the memory 52 may be separate or integrated with the processor 51.
When the memory 52 is a device independent from the processor 51, the electronic terminal 50 may further include:
a bus 53 for connecting the memory 52 and the processor 51.
Example 6
The present embodiment provides readable storage media, in which execution instructions are stored, and when at least processors of the terminal execute the execution instructions, the sending device executes the methods provided by the above-mentioned various embodiments.
Example 7
The application also provides program products comprising executable instructions stored on a readable storage medium, at least processors of the terminal can read the executable instructions from the readable storage medium, and at least processors execute the executable instructions to cause the electronic terminal to implement the methods provided by the various embodiments described above.
The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.
Claims (9)
1, A file processing method of electronic terminal, characterized by comprising:
acquiring recording information corresponding to a target file, wherein the recording information is used for recording th events that history files corresponding to the target file are deleted and second events that occur after the th event is ended each time, and the history files and the target file are files which are stored in a th path and are the same;
determining that the occurrence frequency of the second event corresponding to the th event is greater than a preset value;
when selecting a junk file, determining that the target file is a non-junk file;
the events in the preset event set include at least :
automatically creating another history file corresponding to the target file;
automatically deleting th file associated with the target file;
automatically deleting data recorded in a second file associated with the target file;
and the operation of the application program corresponding to the target file is wrong.
2. The method according to claim 1, wherein before the obtaining the record information corresponding to the target file, the method further comprises:
detecting a kth event;
detecting a kth second event;
recording the kth event and the kth second event.
3. The method of claim 2, wherein prior to detecting the kth second event, further comprising:
and determining that the application program corresponding to the target file is closed and then opening the application program again.
4. The method of claim 3, wherein the application program corresponding to the object file comprises at least :
an application program corresponding to the th path;
an application running in foreground upon detection of an th event;
the application with the most occupied memory when detecting the th event;
the application with the highest processor occupancy when the th event is detected.
5. The method of claim 2, wherein prior to detecting the kth second event, determining that a preset time has not been exceeded.
6. The method of claim 2, wherein prior to detecting the kth event, further comprising deleting a history file to cause the kth event to occur.
7. The method of claim 1, wherein selecting the junk file further comprises, before determining that the target file is a non-junk file: and determining that the application program corresponding to the target file is not deleted.
An electronic terminal of type, comprising:
the acquisition module is used for acquiring recording information corresponding to a target file, wherein the recording information is used for recording th events that history files corresponding to the target file are deleted and times of second events which occur after the th event is ended, and the history files and the target file are files which are stored in a th path and are the same;
an determining module, configured to determine that the number of times of occurrence of the second event corresponding to the th event is greater than a preset value:
the second determining module is used for determining the target file as a non-junk file when the junk file is selected;
the events in the preset event set include at least :
automatically creating another history file corresponding to the target file;
automatically deleting th file associated with the target file;
automatically deleting data recorded in a second file associated with the target file;
and the operation of the application program corresponding to the target file is wrong.
An electronic terminal of 9, , comprising a memory, a processor, and a computer program, the computer program being stored in the memory, the processor running the computer program to perform the method of any of claims 1 to 7 and .
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710898462.3A CN107679161B (en) | 2017-09-28 | 2017-09-28 | File processing method of electronic terminal and electronic terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710898462.3A CN107679161B (en) | 2017-09-28 | 2017-09-28 | File processing method of electronic terminal and electronic terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107679161A CN107679161A (en) | 2018-02-09 |
| CN107679161B true CN107679161B (en) | 2020-01-31 |
Family
ID=61138445
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710898462.3A Active CN107679161B (en) | 2017-09-28 | 2017-09-28 | File processing method of electronic terminal and electronic terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107679161B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2007279922A (en) * | 2006-04-04 | 2007-10-25 | Canon Inc | Document management system and its control method |
| CN105260438A (en) * | 2015-09-30 | 2016-01-20 | 联想(北京)有限公司 | File management method and electronic device |
| CN105653582A (en) * | 2015-12-21 | 2016-06-08 | 联想(北京)有限公司 | File management method of electronic equipment and electronic equipment |
-
2017
- 2017-09-28 CN CN201710898462.3A patent/CN107679161B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2007279922A (en) * | 2006-04-04 | 2007-10-25 | Canon Inc | Document management system and its control method |
| CN105260438A (en) * | 2015-09-30 | 2016-01-20 | 联想(北京)有限公司 | File management method and electronic device |
| CN105653582A (en) * | 2015-12-21 | 2016-06-08 | 联想(北京)有限公司 | File management method of electronic equipment and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107679161A (en) | 2018-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110515820B (en) | Server fault maintenance method and device, server and storage medium | |
| JP6334733B2 (en) | Method and apparatus for recommending solutions based on user actions | |
| CN105472417B (en) | Method and device for acquiring video player abnormity | |
| JP6259522B2 (en) | Software fault location method, apparatus and equipment | |
| US10169137B2 (en) | Dynamically detecting and interrupting excessive execution time | |
| US20130024466A1 (en) | System event logging system | |
| CN114077525A (en) | Abnormal log processing method and device, terminal equipment, cloud server and system | |
| US20180081762A1 (en) | Information processing device | |
| CN107679161B (en) | File processing method of electronic terminal and electronic terminal | |
| CN111159051B (en) | Deadlock detection method, deadlock detection device, electronic equipment and readable storage medium | |
| CN116225915A (en) | Automatic testing method and device for private cloud project delivery based on business inspection | |
| JP2006331026A (en) | Message analysis system and message analysis program | |
| KR101941105B1 (en) | A method of collectively managing the occurrence of errors in the hardware included in the computer system and performing backup and recovery to inform the external terminal | |
| US10572661B2 (en) | Automated blackbox inference of external origin user behavior | |
| CN106130815B (en) | Board level testing method and device | |
| JP5453871B2 (en) | Event determination device, event determination program, and event determination method | |
| CN113613063B (en) | Application anomaly reduction method, device and storage medium | |
| KR101793263B1 (en) | A method of collectively managing the occurrence of errors in the hardware included in the computer system and performing backup and recovery to inform the external terminal | |
| JP4057045B1 (en) | Misoperation judgment system | |
| CN105511848A (en) | Method and device for detecting DLL | |
| CN110837433A (en) | Performance optimization method and device and electronic equipment | |
| CN110781146A (en) | Event storage method, power terminal and computer-readable storage medium | |
| CN112416735A (en) | Application program detection method and device, terminal equipment and storage medium | |
| KR20170138368A (en) | A method of collectively managing the occurrence of errors in the hardware included in the computer system and performing backup and recovery to inform the external terminal | |
| CN110333985B (en) | Method and device for recording operation information of mobile 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |