WO2011130971A1 - 删除文件的方法及移动终端 - Google Patents
删除文件的方法及移动终端 Download PDFInfo
- Publication number
- WO2011130971A1 WO2011130971A1 PCT/CN2010/075642 CN2010075642W WO2011130971A1 WO 2011130971 A1 WO2011130971 A1 WO 2011130971A1 CN 2010075642 W CN2010075642 W CN 2010075642W WO 2011130971 A1 WO2011130971 A1 WO 2011130971A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- file
- mobile terminal
- module
- program
- installation path
- Prior art date
Links
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
Definitions
- the present invention relates to the field of communications, and in particular to a method for deleting a file and a mobile terminal.
- BACKGROUND With the development of the times, the hardware and software of mobile phones are becoming more and more complex, and the functions are more and more, people's requirements for mobile phone software are getting higher and higher, and third-party software is becoming more and more abundant.
- the smartphone software platform on the market has a Nokia-led Sybian system, a Windows Mobile platform led by ⁇ Qisoft, and other platforms that are improved by Google and other vendors based on Google. Apple-led The IPhone platform, as well as Linux systems supported by many vendors.
- a primary object of the present invention is to provide a method for deleting a file and a mobile terminal to solve at least one of the above problems.
- a method for deleting a file comprising: a mobile terminal determining an installation path of a program; and deleting a generated file in the installation path. Further, after the mobile terminal determines the installation path of the program, the method further includes: determining the installation path At the location of the mobile terminal.
- deleting the generated file in the installation path includes: if the installation path is in the memory area of the mobile terminal, obtaining the file deletion permission of the memory area, deleting the generated file according to the permission; further, deleting the generated file in the installation path
- the method includes: if the installation path is in the memory area of the mobile terminal, obtaining the permission to delete the memory area file; obtaining the file type of the generated file; and determining the file type in the configuration file corresponding to the program in the mobile terminal and the file type of the generated file. Correspondence deletes the generated file, where the configuration file saves all file types when the program is started.
- deleting the generated file in the installation path further includes: if the installation path is in the external storage device of the mobile terminal, directly deleting the generated file; further, deleting the generated file in the installation path further includes: if the installation path is at the mobile terminal In the external storage device, the generated file is deleted according to the correspondence between the file type in the configuration file corresponding to the program in the mobile terminal and the file type of the generated file, wherein the configuration file saves all file types when the program is started.
- the generated file of the deletion program includes: determining whether the file type saved in the generated file and the configuration file are consistent; if the determination result is no, deleting the generated file File; If the judgment result is yes, it is judged again whether the program can be started, and if the judgment result is no, the generated file is deleted.
- a mobile terminal including: a determining module, configured to determine an installation path of a program; and a first deleting module, configured to delete a generated file in the installation path. Further, the mobile terminal further includes: a first determining module, configured to determine a location of the installation path at the mobile terminal.
- the first deletion module further includes a second deletion module, where the second deletion module includes: a first acquisition module, configured to acquire a file deletion permission and a file type read permission in the memory area; If the installation path is in the memory area of the mobile terminal, the file type in the configuration file is corresponding to the type of the generated file; the second determining module is configured to determine whether all the corresponding files exist in the memory area; the third deleting module, For deleting the generated file when the judgment result is no; the second corresponding module, if the installation path is in the external memory of the mobile terminal, corresponding to the file type in the configuration file and the type of the generated file; Determining whether there is all corresponding files in the external memory; the fourth deleting module is used to determine whether the result is no, Delete the generated file of the program.
- the second deletion module includes: a first acquisition module, configured to acquire a file deletion permission and a file type read permission in the memory area; If the installation path is in the memory area of the mobile terminal, the file type in the configuration file is corresponding to
- the first deletion module further includes a fifth deletion module, where the fifth deletion module includes: a second acquisition module, if the installation path is in the memory area of the mobile terminal, used to obtain the permission to delete the memory area file; The deletion module is configured to delete the generated file according to the permission; the seventh deletion module, if the installation path is in the external storage device of the mobile terminal, is used to directly delete the generated file.
- the installation path of the obtained file is deleted, and the generated file in the installation path is deleted, which solves the problem that the generated file cannot be deleted during the failure of the mobile terminal installation or uninstallation process, thereby saving the use space of the mobile phone and the storage medium, and improving the use space. User satisfaction.
- FIG. 1 is a flow chart of a method for deleting a file according to an embodiment of the present invention
- FIG. 2 is a flow chart 1 of a preferred embodiment of the present invention
- FIG. 3 is a flow chart of a preferred embodiment of the present invention
- 2 is a flow chart of a clear selection procedure according to an embodiment of the present invention
- FIG. 5 is a flowchart of a clear selection procedure according to an embodiment of the present invention
- FIG. 6 is a mobile according to an embodiment of the present invention.
- Figure 7 is a block diagram showing the structure of a mobile terminal according to an embodiment of the present invention.
- Figure 8 is a block diagram showing a preferred structure of a mobile terminal according to an embodiment of the present invention;
- Figure 9 is a block diagram showing a preferred embodiment of the present invention.
- Step S10 The mobile terminal determines an installation path of the program.
- Step S20 Delete the generated file in the installation path.
- an application in which a mobile terminal has a problem during program installation or uninstallation may cause incomplete installation, missing key files, etc. during the installation or uninstallation process, and the generated partial file user does not have permission. And the path is deleted.
- the mobile terminal saves the use space of the mobile terminal and the external storage by determining the installation path of the program after the installation or uninstallation fails, and saves the use space of the mobile terminal and the external storage, thereby preventing the user from re-flashing , improved user experience.
- the method further comprises: determining a location of the installation path at the mobile terminal. Since the program can be installed in the memory area of the mobile terminal and the external memory, the position of the installation path of the program can be quickly located by this embodiment.
- deleting the generated file in the installation path includes: if the installation path is in the memory area of the mobile terminal, obtaining the permission to delete the memory area file, and deleting the generated file according to the permission.
- the program selected by the user can be deleted in batches. For example: Whether or not these programs work properly. Use the uninstallation function to uninstall the program. If the uninstallation fails, the program has a problem.
- the upper application management process determines the installation path and obtains the delete permission of the files generated in the installation path. (If installed in the phone memory, install the program exclusive. The file deletion permission in the memory area is given to the application management process, and then all generated files are cleared to achieve the purpose of the program.
- the file is deleted by deleting the permission of the file in the memory area, and the memory space is saved.
- deleting the generated file in the installation path includes: if the installation path is in the memory area of the mobile terminal, obtaining the permission to delete the memory area file; obtaining the file type of the generated file; according to the file in the configuration file corresponding to the program in the mobile terminal The correspondence between the type and the file type of the generated file deletes the generated file, where the configuration file saves all file types when the program is started.
- the file area deletion permission and the configuration file are first obtained, and then the generated file is deleted according to the file type of the configuration file and the file type of the generated file, thereby saving memory. space.
- deleting the generated file in the installation path further includes: directly deleting the generated file if the installation path is in an external storage device of the mobile terminal.
- a direct deletion operation is performed on the generated file installed in the external storage device, thereby saving the use space of the external storage device.
- deleting the generated file in the installation path further includes: if the installation path is in the external storage device of the mobile terminal, according to the correspondence between the file type in the configuration file corresponding to the program in the mobile terminal and the file type of the generated file Delete the generated file, where the configuration file saves all file types when the program starts.
- a direct deletion operation is performed on the generated file installed in the external storage device, thereby saving the use space of the external storage device.
- the generated file of the deletion program according to the correspondence between the configuration file and the generated file corresponding to the program in the mobile terminal includes: determining whether the file type saved in the generated file and the configuration file are consistent; if the determination result is negative, deleting the generated file File; If the judgment result is yes, it is judged whether the program can be started; if the judgment result is no, the generated file is deleted.
- This embodiment can be used to batch detect a program selected by a user, and delete a program in which a file is missing or a file is corrupted.
- a special area is set, and the area address is visible to the upper application management process (such as a virtual machine), and the special area stores a configuration file, which stores various files necessary for the startup program to be started.
- Type list (such as java program will generate *.ii, *.ss, *.ap, *jar, *.tmp, _suit.dat file, file save the download path according to pcsl save format 4, ie. jar and.
- the path of jad, *.ss stores the content of the security option corresponding to the application
- *.ap stores the application attribute information read from the MANIFEST.MF file of *.jad and *.jar
- *.jar stores the jar file, *. top It is a temporary file, used to store image information, to speed up the loading speed. If the switch that generates the temporary image is closed during the mutation, the file will not be generated.
- the _suit.dat file stores the id number of the program.
- the upper application management process determines the program corresponding to the installation file type (such as java) and the installation path
- the configuration file in the special area is corresponding to the file generated in the installation file type and the installation path (if it is installed in the memory of the mobile phone, the file in the exclusive memory area of the program installation is deleted and the permission to read the file type is assigned to the application management process) . If a file cannot be found, it will prompt the user that the file is missing, cannot be started, whether it is deleted, the user can choose to delete and skip, and select to delete the program-specific memory area or external storage device installation folder to achieve the cleanup process.
- the installation file type such as java
- the user can set the scan time for the above deletion operation, and can be set to periodically scan regularly, or can be started at any time according to the user's wishes. If it is a regular time scan, it will be at the set time point, in the user interface (User Interface, Referred to as UI) The interface pops up a prompt box for the user to choose whether to scan and clean.
- the user can perform a file deletion operation according to the time set by the system or according to the requirements of the system, thereby improving the flexibility of deleting files in time.
- the program installation directory to be scanned may be set to be default or non-default. If it is non-default, after selecting the scan, the user selects a specific installation directory.
- Step S202 A user manually opens a startup option.
- Step S204 setting the scan processing task to be started periodically or periodically, reaching the timing or the periodic scanning time.
- Step 4 gathers S206, clears and detects the cleanup task to start.
- step S208 it is determined whether the default scan folder has been set.
- step S210 the default folder is opened.
- step S212 the mobile phone menu is opened for the user to select a program or a directory.
- Step S302 initiating a clearing and detecting cleanup task.
- this step uses the operational steps of the embodiment shown in FIG. 2.
- step S304 the user identifies the program identifier to be processed.
- step S306 the user selects all clears to process the selected program; in step S308, the user selects the detection cleanup to process the selected program.
- step S310 a prompt for cleaning up is obtained on the UI interface.
- step S312 the task ends.
- 4 is a flow chart of a clear selection procedure according to an embodiment of the present invention, including the following steps: Step 4: S402, the user selects all to clear.
- step S404 the program management process uses the uninstallation function to uninstall the program and determines whether the uninstallation is successful.
- Step S406 if the uninstallation fails in step 4, the management process determines the file installation path.
- Step S408, obtaining a file installation path through S404, and determining to install in a program-installed dedicated memory area.
- Step S410 determining that the installation path is in an external storage device.
- the program management process is given the right to enter the program to install the exclusive area file deletion.
- FIG. 5 is a flowchart of a clear selection procedure according to an embodiment of the present invention, including the following steps: Step S502, the user selects detection cleanup.
- step S504 the program installation path and the program type are determined. If it is determined that the installation path is in the mobile phone memory, step S506 is performed. If it is determined that the installation path is in the external storage device, step S508 is performed. Step S506, the installation path is in the memory of the mobile phone, and the program management process is given the right to delete the file in the memory of the mobile phone and read the file type.
- Step S508 the installation path is in the external storage device, and directly corresponding to the file type list and the generated file in the configuration file; if the installation path is in the memory, according to the file type obtained after obtaining the permission and the file type in the configuration file correspond.
- the configuration file details the file types required for various installers (such as . jad, .sis ) to start. Its relationship with the program management process is shown in Figure 6.
- step S510 it is determined whether all the corresponding files can be found. If the determination result is yes, step S517 is performed, otherwise, step S512 is performed. In step S512, if the file is missing, the user is prompted to clear the program. Step S514, selecting mega or clear.
- step S516 all the programs to be cleaned are executed cyclically.
- Step 4 gathers S517 and starts the program.
- step S5108 it is determined whether the program is successfully started. If the determination result is yes, step S520 is performed, otherwise step S522 is performed.
- Step 4 gathers S520, and if the startup is successful, the program is closed.
- Step 4 gathers S522, the startup fails, the file is damaged, and the user chooses whether to delete it. The user can choose to skip or clear (step S514), and then loop through all the programs to be cleaned up (step S516).
- FIG. 6 is a schematic diagram of a configuration file of a mobile terminal according to an embodiment of the present invention. As shown in FIG.
- the mobile terminal associates a file type of a configuration file with a file type of a generated file, and may pass The upper management is done to complete.
- the upper management process configuration file memory address is visible to the upper management process, and the process may be a virtual machine or other form (determined by the operating system), and the configuration file stores a list of generated file types that should exist after the various installers are installed, and The file storage area does not change and is written to death in the mobile terminal system.
- the corresponding file type list in the configuration file is corresponding to the generated file, and the corresponding failure indicates that the file is missing.
- FIG. 7 is a structural block diagram of a mobile terminal according to an embodiment of the present invention, where the mobile terminal includes a determining module
- FIG. 8 is a block diagram of a preferred structure of the mobile terminal according to the embodiment of the present invention. The following is a detailed description of the structure: The mobile terminal further includes: a first determining module 82, connected to the determining module 72, for determining that the determining module 72 determines The installation path is at the location of the mobile terminal.
- the first deletion module 74 includes a second deletion module 84.
- the second deletion module 84 includes: a first acquisition module 841, configured to acquire a file deletion permission and a file type read permission in the memory area; the first corresponding module 842, the connection To the first obtaining module 841, if the installation path is in the memory area of the mobile terminal, for matching the file type in the configuration file with the type of the generated file; the second determining module 843 is connected to the first corresponding module 842, Determining whether there is a corresponding file in the memory area; the third deleting module 844 is connected to the second determining module 843, configured to delete the generated file when the second determining module 843 determines that the result is no; the second corresponding module 845, if The installation path is in the external memory of the mobile terminal, and the file type in the configuration file is corresponding to the type of the generated file.
- the third determining module 846 is connected to the second corresponding module 845, and is configured to determine that the second corresponding module 845 determines the external device. Whether there is all corresponding files in the memory; the fourth deleting module 847 is connected to the third determining module 846 for the third determining Block 846 the determination result is NO, the program generates a deleted file.
- the first deletion module 74 further includes a fifth deletion module 86.
- the fifth deletion module 86 includes: a second acquisition module 862, connected to the first determination module 82, and configured to acquire a memory area if the installation path is in a memory area of the mobile terminal.
- the third deletion module 864 is configured to obtain the permission deletion generation file according to the second acquisition module 862; the seventh deletion module 866 is connected to the first determination module 82, if the installation path In the external storage device of the mobile terminal, it is used to directly delete the generated file.
- FIG. 9 is a structural block diagram of a preferred embodiment of the present invention, including a user interaction module 92, a scanning module 94, a determination module 96, and a processing module 98.
- the above structure is described in detail below.
- the user interaction module 92 is used to implement the following functions: 1) The user selects the processing time: Periodically or immediately manually.
- the user selects the program directory and specific files to be processed.
- the directory can be either default or non-default.
- Scanning module 94 Used to implement the following functions:
- the judgment module 96 is used to implement the following functions:
- the processing module 98 is configured to implement the following functions: 1) Clear files from your phone's memory or external storage device.
- the user deleting the program installed on the folder A that cannot be normally operated includes the following steps: Step 1: In the user interaction module, according to the module function 1), function 2), the function is selected, and the function is selected. Three in the detection cleanup function. Step 2: Perform the functions of 1), 3), 4) in the scanning module according to the user's selection in the user interaction module. Step 3: According to the running result of the scanning module, in the judgment module, the judgment is made 2).
- Step 4 If the result of the determination is yes, then proceed to the processing module 2) (in this case, step 5 - step 6 is also required), otherwise the interactive module function 4) is performed, and the module function 1) or 2) is processed. Step 5, providing the processing result to the judgment module function 3). Step 6, the judgment result, if it can be started, enter the processing module function 3), otherwise the user selects the corresponding function in the processing module through the interaction module function 4), that is, the function 1) or the function 2). Step 7: Perform the corresponding function of the processing module.
- the installation program can be cleared in batches according to the user's requirements, and the installation program can be detected in batches to completely clean up the program that cannot be started, saving the space for using the mobile phone and the storage medium, and also using some useless program icons in the mobile phone. Completely removed, avoiding the pain of users needing to re-brush, and improving the satisfaction of users.
- the mobile terminal described in the device embodiment corresponds to the foregoing method embodiment, and the specific implementation process has been described in detail in the method embodiment, and is not described herein.
- the above modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices.
- the computing device may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
- the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps are fabricated as a single integrated circuit module.
- the invention is not limited to any specific combination of hardware and software.
- the above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Telephone Function (AREA)
- Storage Device Security (AREA)
Description
删除文件的方法及移动终端 技术领域 本发明涉及通信领域,具体而言, 涉及一种删除文件的方法及移动终端。 背景技术 随着时代发展, 手机的硬件和软件越来越复杂, 功能越来越多, 人们对 手机软件的要求也越来越高, 第三方软件越来越丰富。 目前市面上的智能手 机软件平台有以诺基亚为主导的 Sybian ***, 以 ^啟软为主导的 Windows Mobile平台, 以谷歌为主导的 Android和其他厂商在 Android基础上改进的 其他平台, 苹果公司主导的 IPhone平台, 以及众多厂商所支持的 Linux*** 等。 在体验着手机给人们带来的便利和科技感的同时, 由于各种***的差异 和形形色色的第三方软件,在使用移动终端过程中也给人们带来诸多的不便。 个人开发者和各种良莠不齐的公司都在从事手机软件的开发, 因为技术 和风格上的差异, 软件的稳定性和可靠性都难以评估, 再加上用户使用水平 的差异, 在安装、 使用或者卸载软件的过程中, 都会产生很多垃圾文件, 这 些垃圾文件会造成***变慢, 影响用户使用等问题。 在移动终端安装或者卸载过程中出现问题的应用程序, 这些程序在安装 或者卸载的过程中出错后将会导致程序安装不完全或关键文件缺失等现象, 生成的部分文件用户没有权限和路径进行清除, 但是这种文件多了以后会导 致手机性能的下降。 且现有技术中的手机平台一般是经过一系列复杂的处理 方法, 需要重新刷机, 给人们的使用上带来很多不便。 发明内容 本发明的主要目的在于提供一种删除文件的方法及移动终端, 以解决上 述问题至少之一。 才艮据本发明的一个方面, 提供了一种删除文件的方法, 包括: 移动终端 确定程序的安装路径; 删除安装路径中的生成文件。 进一步地, 移动终端确定程序的安装路径之后, 还包括: 判断安装路径
在移动终端的位置。 进一步地, 删除安装路径中的生成文件包括: 如果安装路径在移动终端 的内存区域中, 获取内存区域的文件删除的权限, 才艮据权限删除生成文件; 进一步地, 删除安装路径中的生成文件包括: 如果安装路径在移动终端 的内存区域中, 获取内存区域文件删除的权限; 获取生成文件的文件类型; 才艮据移动终端中程序对应的配置文件中的文件类型和生成文件的文件类型的 对应关系删除生成文件, 其中, 配置文件保存程序启动时的全部文件类型。 进一步地, 删除安装路径中的生成文件还包括: 如果安装路径在移动终 端的外置存储装置中, 直接删除生成文件; 进一步地, 删除安装路径中的生成文件还包括: 如果安装路径在移动终 端的外置存储装置中, 才艮据移动终端中程序对应的配置文件中的文件类型和 生成文件的文件类型的对应关系删除生成文件, 其中, 配置文件保存程序启 动时的全部文件类型。 进一步地, 才艮据移动终端中程序对应的配置文件和生成文件的对应关系 删除程序的生成文件包括: 判断生成文件和配置文件中保存的文件类型是否 一致; 如果判断结果为否, 则删除生成文件; 如果判断结果为是, 再次判断 是否能启动该程序, 如果判断结果为否, 则删除生成文件。 根据本发明的另一方面, 提供了一种移动终端, 包括: 确定模块, 用于 确定程序的安装路径; 第一删除模块, 用于删除安装路径中的生成文件。 进一步地, 移动终端还包括: 第一判断模块, 用于判断安装路径在移动 终端的位置。 进一步地, 第一删除模块还包括第二删除模块, 其中, 第二删除模块包 括: 第一获取模块, 用于获取内存区域中文件删除的权限和文件类型读取的 权限; 第一对应模块, 如果安装路径在移动终端的内存区域中, 用于将配置 文件中的文件类型和生成文件的类型对应; 第二判断模块, 用于判断内存区 域中是否存在全部的对应文件; 第三删除模块, 用于在判断结果为否时, 删 除生成文件; 第二对应模块, 如果安装路径在移动终端的外置存储器中, 将 配置文件中的文件类型和生成文件的类型对应; 第三判断模块, 用于判断外 置存储器中是否存在全部的对应文件; 第四删除模块, 用于判断结果为否时,
删除程序的生成文件。 进一步地, 第一删除模块还包括第五删除模块, 其中, 第五删除模块包括: 第二获取模块,如果安装路径在移动终端的内存区域中, 用于获取内存区域文件删除的权限; 第六删除模块, 用于才艮据权限删除生成 文件; 第七删除模块, 如果安装路径在移动终端的外置存储装置中, 用于直 接删除生成文件。 通过本发明, 釆用获取文件的安装路径, 删除安装路径中 的生成文件, 解决了移动终端安装或者卸载程序失败过程中生成文件不能删 除的问题, 节省了手机和存储介质的使用空间, 提升了用户使用的满意度。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部 分, 本发明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的 不当限定。 在附图中: 图 1是才艮据本发明实施例的删除文件的方法的流程图; 图 2是 居本发明优选实施例的流程图一; 图 3是 居本发明优选实施例的流程图二; 图 4是才艮据本发明实施例的清除选择程序的流程图; 图 5是才艮据本发明实施例的清除选择程序的流程图; 图 6是才艮据本发明实施例的移动终端配置文件的示意图; 图 7是 居本发明实施例移动终端的结构框图; 图 8是 居本发明实施例移动终端的优选的结构框图; 图 9是 居本发明优选实施例的结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在 不冲突的情况下, 本申请中的实施例及实施例中的特征可以相互组合。 图 1是才艮据本发明实施例的删除文件的方法的流程图, 该方法包括如下 的步 4聚:
步骤 S 10, 移动终端确定程序的安装路径; 步骤 S20 , 删除安装路径中的生成文件。 在相关技术中, 移动终端在进行程序安装或者卸载过程中出现问题的应 用程序, 这些程序在安装或者卸载过程中出错后会导致安装不完全, 关键文 件缺失等问题, 生成的部分文件用户没有权限和路径进行删除, 在该实施例 中, 移动终端通过确定安装或者卸载失败后程序的安装路径, 并删除安装路 径中的生成文件, 节省了移动终端和外置存储的使用空间, 避免用户重新刷 机, 提高了用户体验度。 优选地, 在步 4聚 S 10之后, 还包括: 判断安装路径在移动终端的位置。 由于程序可以安装在移动终端的内存区域和外置存储器中, 通过该实施 例可以快速定位程序的安装路径的位置。 优选地, 删除安装路径中的生成文件包括: 如果安装路径在移动终端的 内存区域中, 获取内存区域文件删除的权限, 根据权限删除生成文件。 通过该优选实施例的删除方法, 可以进行批量删除用户选择的程序。 例如: 无论这些程序是否能正常运行。使用程序自带卸载功能卸载程序, 如果卸载失败则说明程序有问题, 上层应用管理进程确定出安装路径, 并取 得安装路径中生成的文件的删除权限 (如果安装在手机内存中, 将程序安装 专属内存区域中文件删除的权限赋予该应用管理进程 ),之后清除所有生成文 件以达到清除程序的目的。 通过该优选实施例, 对于安装在内存中的文件, 通过获取内存区域文件 删除的权限, 删除生成文件, 节省了内存空间。 优选地, 删除安装路径中的生成文件包括: 如果安装路径在移动终端的 内存区域中, 获取内存区域文件删除的权限; 获取生成文件的文件类型; 根 据移动终端中程序对应的配置文件中的文件类型和生成文件的文件类型的对 应关系删除生成文件, 其中, 配置文件保存程序启动时的全部文件类型。 通过该优选实施例, 对于安装在内存中的文件, 首先获取内存区域文件 删除的权限和配置文件, 然后才艮据配置文件的文件类型和生成文件的文件类 型, 删除生成文件, 从而节省了内存空间。
优选地, 删除安装路径中的生成文件还包括: 如果安装路径在移动终端 的外置存储装置中, 直接删除生成文件。 通过该优选实施例, 对于安装在外置存储装置中的生成文件进行直接删 除操作, 从而节省了外置存储装置的使用空间。 优选地, 删除安装路径中的生成文件还包括: 如果安装路径在移动终端 的外置存储装置中, 才艮据移动终端中程序对应的配置文件中的文件类型和生 成文件的文件类型的对应关系删除生成文件, 其中, 配置文件保存程序启动 时的全部文件类型。 通过该优选实施例, 对于安装在外置存储装置中的生成文件进行直接删 除操作, 从而节省了外置存储装置的使用空间。 优选地, 才艮据移动终端中程序对应的配置文件和生成文件的对应关系删 除程序的生成文件包括: 判断生成文件和配置文件中保存的文件类型是否一 致; 如果判断结果为否, 则删除生成文件; 如果判断结果为是, 判断是否能 启动该程序; 如果判断结果为否, 则删除生成文件。 该实施例可以用于批量检测用户选择的程序, 删除文件缺少或文件损坏 的程序。 在手机内存中的程序安装专属内存区域中, 设置了一个专区, 专区 地址对上层应用管理进程 (如虚拟机) 可见, 该专区存放一个配置文件, 该 文件存放各种安装程序启动时必需的文件类型列表 (如 java程序安装后会生 成 *.ii,*.ss,*.ap,*jar,*.tmp,_suit.dat文件, 文件按照 pcsl存 4诸格式保存下载 路径,即. jar和. jad的路径 ,*.ss存储应用对应安全选项的内容, *.ap存储从 *.jad 和 *.jar的 MANIFEST.MF文件中读取的应用属性信息 ,*.jar存放 jar文件, *. top 是临时文件, 用于存放图片信息, 起到加快加载速度作用, 在变异中 如果把产生临时图片的开关关闭后, 就不会有这个文件产生, 另外 _suit.dat 文件存放程序的 id号, 供虚拟机进行调用, 这些文件中除了 *.tmp文件都不 能缺少或损坏否则无法启动程序), 当上层应用管理进程判断出程序对应安装 文件类型 (如 java ) 和安装路径时, 会将专区中的配置文件按照安装文件类 型和安装路径中生成的文件 (如果安装在手机内存中, 将程序安装专属内存 区域中文件删除以及对文件类型读取的权限赋予该应用管理进程)进行对应。 如果发现有文件无法对应, 会提示用户文件缺少, 无法启动, 是否删除, 用 户可以选择删除和跳过, 选择删除则格式化该程序专属内存区域或外置存储 设备安装文件夹以达到清除程序的目的, 选择跳过则继续执行检测下一个程
序; 如果不缺少文件, 则启动该程序, 如果启动成功, 直接 kill该程序进程, i如启动失败, 则提示用户文件损坏, 无法启动, 并提示用户是否删除, 用 户可以选择删除和跳过, 如果选择删除, 则格式化该程序专属内存区域或外 置存储装置中的安装文件夹以达到清除程序的目的, 如果选择跳过则继续执 行检测下一个程序。 通过该优选实施例, 对于不能正常启动, 但是生成文件的文件类型和配 置文件保存的文件类型一致的程序文件进行删除文件, 保证了文件删除的彻 底性, 节省了移动终端的内存或外置存储装置的使用空间。 优选地, 用户可以对上述的删除操作设置扫描时间, 可以设置为定期定 时扫描, 也可以按用户意愿随时启动, 如果是定期定时扫描, 则会在设置的 时间点, 在用户接口 ( User Interface , 简称为 UI ) 界面弹出提示框供用户选 择是否进行扫描清理。 通过该优选实施例, 用户可以按照***设定的时间或者自身要求进行文 件删除操作, 提高了删除文件在时间上的灵活性。 优选地, 需要扫描的程序安装目录可以设置为默认的或非默认的, 如果 是非默认的则在选择扫描后, 由用户进行选择具体安装目录。 通过该优选实施例,用户可以对默认或者非默认目录进行有选择的扫描, 提高了删除文件的灵活性。 为了帮助理解上述实施例, 下面进一步描述本发明的其他多个优选实施 例。 图 2是 居本发明优选实施例的流程图一, 包括如下步骤: 步骤 S202, 用户手动打开启动选项。 步骤 S204, 设置为定时或定期启动扫描处理任务, 到达定时或定期扫描 时间。 步 4聚 S206, 清除和检测清理任务启动。 步骤 S208, 判断默认扫描文件夹是否已设置。 步骤 S210, 打开默认文件夹。
步骤 S212, 打开手机菜单, 供用户选择程序或目录。 通过该实施例, 用户可以按照***设定的时间或者自身要求进行文件删 除操作, 并且可以设置默认菜单或者通过用户选择程序或目录, 提高了删除 文件在时间上的灵活性和操作上的便利。 图 3是才艮据本发明优选实施例的流程图二, 包括以下步骤: 步骤 S302, 启动清除和检测清理任务。 优选地, 该步骤釆用图 2所示实施例的操作步骤。 步骤 S304, 由用户勾选需要处理的程序标识。 步骤 S306, 用户选择全部清除对选择的程序进行处理; 步骤 S308, 用户选择检测清理清除对选择的程序进行处理。 步骤 S310, 在 UI界面得出清理结束的提示。 步骤 S312, 结束任务。 图 4是才艮据本发明实施例的清除选择程序的流程图, 包括如下步骤: 步 4聚 S402, 用户选择全部清除。 步骤 S404,程序管理进程使用程序自带卸载功能卸载程序并判断是否卸 载成功。 步骤 S406, 如果步 4聚 S404中卸载失败, 则管理进程判断文件安装路径。 步骤 S408 , 通过 S404获得了文件安装路径, 判断出安装在程序安装专 属内存区域中。 步骤 S410, 判断出安装路径在外置存储装置。 步骤 S412, 赋予程序管理进程进入程序安装专属区域文件删除的权限。 步骤 S414, 删除安装地址的生成文件。 步骤 S416, 如果步骤 S404中卸载成功, 循环执行完所有要清除的程序。
图 5是才艮据本发明实施例的清除选择程序的流程图, 包括如下步骤: 步骤 S502 , 用户选择检测清理。 步骤 S504, 判断程序安装路径和程序类型, 如果判断出安装路径在手机 内存中, 则执行步骤 S506, 如果判断出安装路径在外置存储装置中, 则执行 步骤 S508。 步骤 S506, 安装路径在手机内存中, 则赋予程序管理进程对手机内存中 的文件删除以及对文件类型读取的权限。 步骤 S508, 安装路径在外置存储装置中, 直接将配置文件中对应的文件 类型列表和生成文件进行对应; 如果安装路径在内存中, 根据获取权限后得 到的文件类型和配置文件中的文件类型进行对应。 需要说明的是, 配置文件详细列举了各种安装程序 (如. jad,.sis ) 启动时 必需的文件类型。 它和程序管理进程的关系见图 6。 步骤 S510, 判断是否全部能找到对应文件, 如果判断结果为是, 执行步 骤 S517, 否则, 执行步骤 S512。 步骤 S512, 文件缺失, 则提示用户是否清除该程序。 步骤 S514, 选择兆过或者清除。 步骤 S516, 循环执行完所有要检测清理的程序。 步 4聚 S517, 启动该程序。 步骤 S518 , 判断是否成功启动该程序, 如果判断结果为是, 执行步骤 S520, 否则执行步骤 S522。 步 4聚 S520, 启动成功, 则关闭该程序。 步 4聚 S522, 启动失败, 提示文件损坏, 有用户选择是否删除。 用户可以 选择跳过或清除 (步骤 S514 ), 接着循环执行完所有要检测清理的程序 (步 骤 S516 )。 图 6是才艮据本发明实施例的移动终端配置文件的示意图, 如图 6所示, 移动终端将配置文件的文件类型和生成文件的文件类型进行对应, 可以通过
上层管理进行来完成。 优选地, 上层管理进程配置文件内存地址对上层管理进程可见, 该进程 可以是虚拟机或者其它形式(由操作***决定), 配置文件存放各种安装程序 安装后应该存在的生成文件类型列表, 且该文件存储区域不会变动在移动终 端***中写死。 当用户选择完全检测清理时, 会将配置文件中对应的文件类 型列表和生成文件进行对应, 对应失败则表明文件缺失。 需要说明的是, 在附图的流程图示出的步骤可以在诸如一组计算机可执 行指令的计算机***中执行, 并且, 虽然在流程图中示出了逻辑顺序, 但是 在某些情况下, 可以以不同于此处的顺序执行所示出或描述的步骤。 图 7是才艮据本发明实施例移动终端的结构框图, 移动终端包括确定模块
72和删除模块 74 , 下面对上述结构进行详细描述: 确定模块 72 , 用于确定程序的安装路径; 第一删除模块 74 , 连接至确 定模块 72 , 用于删除安装路径中的生成文件。 图 8是 居本发明实施例移动终端的优选的结构框图, 下面对该结构进 行详细描述: 上述移动终端还包括: 第一判断模块 82 , 连接至确定模块 72, 用于判 断确定模块 72确定的安装路径在移动终端的位置。 第一删除模块 74包括第二删除模块 84: 第二删除模块 84包括: 第一获取模块 841 , 用于获取内存区域中文件删 除的权限和文件类型读取的权限; 第一对应模块 842 , 连接至第一获取模块 841 , 如果安装路径在移动终端的内存区域中, 用于将配置文件中的文件类 型和生成文件的类型对应; 第二判断模块 843 , 连接至第一对应模块 842 , 用于判断内存区域中是否存在全部的对应文件; 第三删除模块 844 , 连接至 第二判断模块 843 , 用于在第二判断模块 843判断结果为否时, 删除生成文 件; 第二对应模块 845 , 如果安装路径在移动终端的外置存储器中, 将配置 文件中的文件类型和生成文件的类型对应; 第三判断模块 846 , 连接至第二 对应模块 845 , 用于判断第二对应模块 845判断外置存储器中是否存在全部 的对应文件; 第四删除模块 847, 连接至第三判断模块 846 , 用于第三判断 模块 846判断结果为否时, 删除程序的生成文件。
第一删除模块 74还包括第五删除模块 86: 第五删除模块 86 包括: 第二获取模块 862, 连接至第一判断模块 82, 如果安装路径在移动终端的内存区域中 ,用于获取内存区域文件删除的权限; 第六删除模块 864, 第二获取模块 862, 用于才艮据第二获取模块 862获取权 限删除生成文件; 第七删除模块 866, 连接至第一判断模块 82, 如果安装路 径在移动终端的外置存储装置中, 用于直接删除生成文件。 图 9是 居本发明优选实施例的结构框图, 包括用户交互模块 92, 扫描 模块 94, 判断模块 96, 处理模块 98, 下面对上述结构进行详细描述。 用户交互模块 92用于实现下述功能: 1 ) 用户选择处理时间: 定时定期或立即手动处理。
2 )用户选择需要处理的程序目录和具体文件, 目录可以是默认的, 也可 以是非默认的。
3 ) 用户选择完全清除或检测清理选择的所有文件。
4 ) 用户选择清除有问题的程序或跳过部清除。 扫描模块 94: 用于实现下述功能:
1 ) 扫描文件的安装位置。
2 ) 扫描程序的自带卸载程序。
3 ) 扫描生成文件类型。
4) 扫描配置文件。 判断模块 96用于实现下述功能:
1 ) 判断自带卸载程序能否卸载成功。
2) 判断配置文件和生成文件能否完全对应。
3 ) 判断程序能否启动。 处理模块 98用于实现下述功能:
1 ) 清除手机内存或外置存储设备中的文件。
2 ) 跳过不清除程序。
3 ) 启动队列中的程序。
4 ) 退出程序。 5 ) 使用自带卸载程序卸载。
6 ) 对下一个程序进行处理, 直到最后一个程序。 本发明还提供了一个优选实施例, 结合了上述多个优选实施例的技术方 案, 下面结合图 4和 9来详细描述。 在本实施例中, 用户删除安装在文件夹 A上不能正常运行的程序包括以 下步 4聚: 步骤 1 : 在进入用户交互模块中, 按照该模块功能 1 )、 功能 2 ) 进行启 动, 选择功能三中的检测清理功能。 步骤 2, 根据用户交互模块中用户的选择, 在扫描模块进行 1 )、 3 )、 4 ) 功能。 步骤 3 , 根据扫描模块运行结果, 在判断模块, 进行判断 2 )。 步骤 4, 如果判断结果为是, 则接着进入处理模块 2 ) (这时还需要执行 步骤 5-步骤 6 ), 否则接着进行交互模块功能 4 ), 处理模块功能 1 ) 或 2 )。 步骤 5 , 将处理结果提供给判断模块功能 3 )。 步骤 6, 居判断结果, 如果能启动则进入处理模块功能 3 ), 否则由用 户通过交互模块功能 4 ) 选择处理模块中的相应功能,即功能 1 ) 或功能 2 )。 步骤 7 , 执行处理模块相应功能。 通过本发明, 能够按用户需求批量清除安装程序, 也可以批量检测安装 程序进而将有问题无法启动的程序完全清理, 节省了手机和存储介质的使用 空间, 也可以将手机中一些无用的程序图标彻底删除, 避免了用户需要重新 刷机的痛苦, 提升了用户使用的满意度。
需要说明的是,装置实施例中描述的移动终端对应于上述的方法实施例, 其具体的实现过程在方法实施例中已经进行过详细说明, 在此不再赞述。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可 以用通用的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布 在多个计算装置所组成的网络上, 可选地, 它们可以用计算装置可执行的程 序代码来实现, 从而, 可以将它们存储在存储装置中由计算装置来执行, 并 且在某些情况下, 可以以不同于此处的顺序执行所示出或描述的步骤, 或者 将它们分别制作成各个集成电路模块, 或者将它们中的多个模块或步骤制作 成单个集成电路模块来实现。 这样, 本发明不限制于任何特定的硬件和软件 结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的 ^"神和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。
Claims
1. 一种删除文件的方法, 其特征在于, 包括:
移动终端确定程序的安装路径;
删除所述安装路径中的生成文件。
2. 居权利要求 1所述的方法, 其特征在于, 在移动终端确定程序的安装 路径之后, 还包括:
判断所述安装路径在所述移动终端的位置。
3. 根据权利要求 2所述的方法, 其特征在于, 删除所述安装路径中的生成 文件包括:
如果所述安装路径在所述移动终端的内存区域中, 获取所述内存区 域的文件删除的权限, 居所述权限删除所述生成文件。
4. 根据权利要求 2所述的方法, 其特征在于, 删除所述安装路径中的生成 文件包括:
如果所述安装路径在所述移动终端的内存区域中, 获取所述内存区 域文件删除的权限;
获取所述生成文件的文件类型;
才艮据移动终端中所述程序对应的配置文件中的文件类型和所述生成 文件的文件类型的对应关系删除所述生成文件, 其中, 所述配置文件保 存所述程序启动时的全部文件类型。
5. 根据权利要求 2所述的方法, 其特征在于, 删除所述安装路径中的生成 文件还包括:
如果所述安装路径在所述移动终端的外置存储装置中, 直接删除所 述生成文件。
6. 根据权利要求 2所述的方法, 其特征在于, 删除所述安装路径中的生成 文件还包括:
如果所述安装路径在所述移动终端的外置存储装置中, 根据所述移 动终端中所述程序对应的配置文件中的文件类型和所述生成文件的文件 类型的对应关系删除所述生成文件, 其中, 所述配置文件保存所述程序 启动时的全部文件类型。
7. 根据权利要求 4或 6所述的方法, 其特征在于, 根据移动终端中所述程 序对应的配置文件和所述生成文件的对应关系删除所述程序的生成文件 包括:
判断所述生成文件和所述配置文件中保存的文件类型是否一致; 如果判断结果为否, 则删除所述生成文件;
如果判断结果为是, 再次判断是否能启动该程序, 如果判断结果为 否, 则删除所述生成文件。
8. —种移动终端, 其特征在于, 包括:
确定模块, 用于确定所述程序的安装路径;
第一删除模块, 用于删除所述安装路径中的生成文件。
9. 根据权利要求 8所述的移动终端, 其特征在于, 还包括:
第一判断模块, 用于判断所述安装路径在所述移动终端的位置。
10. 根据权利要求 8所述的移动终端, 其特征在于, 所述第一删除模块还包 括第二删除模块, 其中, 所述第二删除模块包括: 第一获取模块, 用于获取所述内存区域中文件删除的权限和文件类 型读取的权限; 第一对应模块, 如果所述安装路径在所述移动终端的内存区域中, 用于将所述配置文件中的文件类型和所述生成文件的类型对应;
第二判断模块,用于判断所述内存区域中是否存在全部的对应文件; 第三删除模块, 用于在所述第二判断模块判断结果为否时, 删除所 述生成文件;
第二对应模块,如果所述安装路径在所述移动终端的外置存储器中, 将所述配置文件中的文件类型和所述生成文件的类型对应;
第三判断模块, 用于判断所述外置存储器中是否存在全部的对应文 件; 第四删除模块, 用于在所述第三判断模块的判断结果为否时, 删除 所述程序的生成文件。
11. 根据权利要求 8所述的移动终端, 其特征在于, 所述第一删除模块还包 括第五删除模块, 其中, 所述第五删除模块包括:
第二获取模块, 如果所述安装路径在所述移动终端的内存区域中, 用于获取所述内存区域文件删除的权限;
第六删除模块, 用于才艮据所述权限删除所述生成文件; 第七删除模块, 如果所述安装路径在所述移动终端的外置存储装置 中, 用于直接删除所述生成文件。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2010101650530A CN101876914A (zh) | 2010-04-23 | 2010-04-23 | 删除文件的方法及移动终端 |
CN201010165053.0 | 2010-04-23 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011130971A1 true WO2011130971A1 (zh) | 2011-10-27 |
Family
ID=43019476
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2010/075642 WO2011130971A1 (zh) | 2010-04-23 | 2010-08-02 | 删除文件的方法及移动终端 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101876914A (zh) |
WO (1) | WO2011130971A1 (zh) |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104679562B (zh) * | 2011-01-04 | 2018-06-05 | 北京奇虎科技有限公司 | 一种强力卸载软件的方法及*** |
CN102222027B (zh) * | 2011-06-20 | 2017-07-04 | 中兴通讯股份有限公司 | 终端恢复出厂设置方法及装置 |
CN102279892A (zh) * | 2011-09-07 | 2011-12-14 | 盛乐信息技术(上海)有限公司 | 临时文件清理方法及*** |
CN106445622A (zh) * | 2012-06-20 | 2017-02-22 | 青岛海信移动通信技术股份有限公司 | 应用程序卸载方法、卸载装置及移动终端 |
CN103577417B (zh) * | 2012-07-23 | 2019-02-22 | 腾讯科技(深圳)有限公司 | 清理桌面的方法和装置 |
CN103678349B (zh) * | 2012-09-10 | 2017-09-26 | 腾讯科技(深圳)有限公司 | 一种垃圾数据过滤方法和装置 |
CN102981721A (zh) * | 2012-11-05 | 2013-03-20 | 广东欧珀移动通信有限公司 | 一种删除应用程序的方法、装置及移动终端 |
CN102999606B (zh) * | 2012-11-21 | 2015-12-23 | 东莞宇龙通信科技有限公司 | 软件删除方法及装置 |
CN103838601B (zh) * | 2013-11-29 | 2017-04-19 | 北京奇虎科技有限公司 | 一种垃圾数据清理方法和装置 |
CN103617065A (zh) * | 2013-12-13 | 2014-03-05 | 广州市久邦数码科技有限公司 | 一种强力卸载移动终端***软件的***及方法 |
CN104881299A (zh) * | 2014-02-28 | 2015-09-02 | 可牛网络技术(北京)有限公司 | 一种应用程序冻结方法及装置 |
CN103838843A (zh) * | 2014-03-03 | 2014-06-04 | 联想(北京)有限公司 | 一种文件处理方法及电子设备 |
CN104317840A (zh) * | 2014-10-10 | 2015-01-28 | 北京金山安全软件有限公司 | 一种文件清理方法、装置及终端 |
CN104991948A (zh) * | 2015-07-14 | 2015-10-21 | 谢蓓 | 一种安卓手机的文件删除提示方法及*** |
CN105069085A (zh) * | 2015-07-31 | 2015-11-18 | 上海斐讯数据通信技术有限公司 | 清理环境变量路径的方法及*** |
CN105138925B (zh) * | 2015-09-25 | 2019-03-29 | 联想(北京)有限公司 | 一种信息处理方法及电子设备 |
CN106126074B (zh) * | 2016-06-21 | 2020-09-11 | 北京小米移动软件有限公司 | 界面中元素的处理方法及装置 |
CN106201601B (zh) * | 2016-06-30 | 2019-11-26 | 北京奇虎科技有限公司 | 一种文件清理方法、电子设备及服务器 |
CN106201595A (zh) * | 2016-06-30 | 2016-12-07 | 北京奇虎科技有限公司 | 一种应用程序的清理控制方法及装置 |
CN109918340B (zh) * | 2019-03-18 | 2021-07-02 | 维沃移动通信有限公司 | 一种文件处理方法及终端设备 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1874563A (zh) * | 2006-06-15 | 2006-12-06 | 中山大学 | 一种手机程序与文件管理***及方法 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1953592A (zh) * | 2005-10-20 | 2007-04-25 | 乐金电子(中国)研究开发中心有限公司 | 移动通信终端及应用程序的资源管理方法 |
CN101256498A (zh) * | 2008-03-25 | 2008-09-03 | 中兴通讯股份有限公司 | 终端驱动卸载的方法和装置 |
CN101477460A (zh) * | 2008-12-17 | 2009-07-08 | 三星电子(中国)研发中心 | 浏览器应用在手持设备上的制作和定制方法 |
-
2010
- 2010-04-23 CN CN2010101650530A patent/CN101876914A/zh active Pending
- 2010-08-02 WO PCT/CN2010/075642 patent/WO2011130971A1/zh active Application Filing
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1874563A (zh) * | 2006-06-15 | 2006-12-06 | 中山大学 | 一种手机程序与文件管理***及方法 |
Non-Patent Citations (2)
Title |
---|
LI ZHI: "Intelligent optimization of smart phone", ELECTRONICS WORLD, no. 1, January 2008 (2008-01-01), pages 52 - 53 * |
SHI LU: "Deleting installation program of smart phone more thoroughly", ELECTRONICS WORLD, no. 4, April 2008 (2008-04-01), pages 55 - 56 * |
Also Published As
Publication number | Publication date |
---|---|
CN101876914A (zh) | 2010-11-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2011130971A1 (zh) | 删除文件的方法及移动终端 | |
US10235149B2 (en) | Preinstalled application management method for mobile terminal and mobile terminal | |
CN102043655B (zh) | 一种强力卸载软件的方法及*** | |
US9098370B2 (en) | Apparatus and methods for improving uninstall process | |
CN105094903B (zh) | 对固件进行升级的方法及装置 | |
WO2017067448A1 (zh) | 一种无线固件升级方法、***及计算机存储介质 | |
CN102831035B (zh) | 备份信息的方法及装置 | |
CN104317623B (zh) | 移动终端预置应用程序的管理方法和移动终端 | |
CN107368343B (zh) | 一种基于安卓***的终端开机方法、终端及存储介质 | |
CN102346673A (zh) | 一种手机***升级的方法及装置 | |
WO2017161831A1 (zh) | 一种应用处理方法、装置和电子设备 | |
WO2018099253A1 (zh) | 一种自启动方法及装置 | |
CN103124276A (zh) | 一种扩展通信终端存储空间的方法及通信终端 | |
US20100017863A1 (en) | Portable storage apparatus for providing working environment migration service and method thereof | |
CN105468504A (zh) | 程序测试方法及装置 | |
CN111258613A (zh) | 固件升级方法、装置、电子设备以及存储介质 | |
CN108459868A (zh) | 一种软件启动方法、装置、终端和存储介质 | |
WO2020057134A1 (zh) | 移动终端的控制方法及移动终端 | |
WO2014067368A1 (zh) | 资源预览图的获取方法、装置以及设备 | |
CN103218235A (zh) | 终端和软件安装方法 | |
CN103365674B (zh) | 一种基于移动终端的插件管理方法、装置和*** | |
CN107273135B (zh) | 恢复终端设备出厂设置的方法 | |
CN109634782A (zh) | 一种***健壮性的检测方法、装置、存储介质及终端 | |
CN106886556A (zh) | 一种优化存储空间的方法及装置 | |
CN106569912A (zh) | 一种移动终端恢复出厂设置的方法及*** |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10850103 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 10850103 Country of ref document: EP Kind code of ref document: A1 |