Method for controlling startup of application and terminal device

• US 10,509,661 B2
• Filed: 08/23/2018
• Issued: 12/17/2019
• Est. Priority Date: 05/31/2016
• Status: Active Grant

• Current Assignee: ZEKU Technology Corporation Limited
• Original Assignee: Guangdong OPPO Mobile Telecommunications Corporation Limited
• Inventors: Zeng, Yuanqing
• Primary Examiner(s): Rashid, Wissam
• Application Number:
  US16/110,315
• Publication Number:
  US 20180365037A1
• Time in Patent Office: 481 Days
• CPC Class Codes: G06F 9/445 Program loading or initiating bootstrapping G06F9/4401; security arrangements for program loading or initiating G06F21/57
• CPC Class Codes: G06F 9/44578 Preparing or optimising for loading
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A method for controlling application includes following operations. Startup of a target application of a terminal device is accelerated in response a control instruction of starting the target application. Accelerating the startup of the target application is stopped when a duration of accelerating the startup of the target application reaches a preset value, based on that a time length required for successfully starting the target application is greater than or equal to a preset time length, or accelerating the startup of the target application is stopped when a refresh rate of frames of a main thread of the target application reaches or exceeds a preset refresh rate, based on that the time length required for successfully starting the target application is less than the preset time length. A related terminal device is also provided.

Claims

1. A method for controlling application, comprising:

accelerating startup of a target application of a terminal device in response to a control instruction of starting the target application;

determining a percentage of current idle cores of the terminal device when a time length required for successfully starting the target application is greater than or equal to a preset time length, and determining, according to a mapping relationship between accelerating startup time lengths of the target application and percentages of idle cores, an accelerating startup time length corresponding to the percentage of the current idle cores;

stopping accelerating the startup of the target application based on a determination that a time length of accelerating the startup of the target application is greater than or equal to the accelerating startup time length corresponding to the percentage of the current idle cores;

monitoring a refresh rate of frames of a main thread of the target application during the accelerating the startup of the target application, when the time length required for successfully starting the target application is less than the preset time length; and

stopping the accelerating the startup of the target application based on a determination that the refresh rate of the frames of the main thread of the target application reaches or exceeds a preset refresh rate.

2. The method of claim 1, wherein the preset refresh rate is a maximum value of multiple history refresh rates of the frames of the main thread of the target application, and each of the history refresh rates was recorded by the terminal device at a time point that the target application was successfully started.

3. The method of claim 1, wherein the preset refresh rate is an average value of multiple history refresh rates of the frames of the main thread of the target application, and each of the history refresh rates was recorded by the terminal device at a time point that the target application was successfully started.

4. The method of claim 1, wherein the time length required for successfully starting the target application is determined according to:

obtaining multiple history records that the terminal device accelerated the startup of the target application, wherein each of the history records contains an accelerating startup time length of the target application and a percentage of idle cores of the terminal device; and

determining, according to the multiple history records, an average time length of the accelerating startup time lengths contained in the multiple history records to be the time length required for successfully starting the target application, and determining, according to the multiple history records, the mapping relationship between accelerating startup time lengths of the target application and percentages of idle cores.

5. The method of claim 1, further comprising:

after the stopping accelerating the startup of the target application, setting a work mode of each of at least one of the cores of the terminal device to be a low power mode.

6. The method of claim 1, wherein determining the percentage of the current idle cores of the terminal device comprises:

determining the percentage of the current idle cores according to m idle cores in n cores of the terminal device, wherein m and n are integers, and m is less than n.

7. A terminal device comprising:

at least one processor; and

a computer readable memory, coupled to the at least one processor and storing at least one computer executable instruction therein which, when executed by the at least one processor, causes the at least one processor to;

accelerate startup of a target application of the terminal device in response to a control instruction of starting the target application;

determine a percentage of current idle cores of the terminal device when a time length required for successfully starting the target application is greater than or equal to a preset time length, and determining, according to a mapping relationship between accelerating startup time lengths of the target application and percentages of idle cores, an accelerating startup time length corresponding to the percentage of the current idle cores;

stop accelerating the startup of the target application based on a determination that a time length of accelerating the startup of the target application is greater than or equal to the accelerating startup time length corresponding to the percentage of the current idle cores;

monitor a refresh rate of frames of a main thread of the target application during the accelerating the startup of the target application, when the time length required for successfully starting the target application is less than the preset time length; and

stop the accelerating the startup of the target application based on a determination that the refresh rate of the frames of the main thread of the target application reaches or exceeds a preset refresh rate.

8. The terminal device of claim 7, wherein the preset refresh rate is an average value of multiple history refresh rates of the frames of the main thread of the target application, and each of the history refresh rates was recorded by the terminal device at a time point that the target application was successfully started.

9. The terminal device of claim 7, wherein the at least one processor is caused to determine the time length required for successfully starting the target application according to:

obtaining multiple history records that the terminal device accelerated the startup of the target application, wherein each of the history records contains an accelerating startup time length of the target application and a percentage of idle cores of the terminal device; and

determining, according to the multiple history records, an average time length of the accelerating startup time lengths contained in the multiple history records to be the time length required for successfully starting the target application, and determining, according to the multiple history records, the mapping relationship between accelerating startup time lengths of the target application and percentages of idle cores.

10. The terminal device of claim 7, wherein the at least one processor is further caused to:

set a work mode of each of at least one of the cores of the terminal device to be a low power mode after stopping accelerating the startup of the target application.

11. The terminal device of claim 7, wherein the at least one processor caused to determine the percentage of the current idle cores of the terminal device is further caused to:

determine the percentage of the current idle cores according to m idle cores in n cores of the terminal device, wherein m and n are integers, and m is less than n.

12. A terminal device comprising:

at least one processor; and

a computer readable memory, coupled to the at least one processor and storing at least one computer executable instruction therein which, when executed by the at least one processor, causes the at least one processor to;

accelerate startup of a target application of the terminal device in response to a control instruction of starting the target application;

stop accelerating the startup of the target application when a duration of accelerating the startup of the target application reaches or exceeds a preset value, based on that a time length required for successfully starting the target application is greater than or equal to a preset time length;

monitor a refresh rate of frames of a main thread of the target application during the accelerating the startup of the target application, when the time length required for successfully starting the target application is less than the preset time length; and

stop accelerating the startup of the target application based on a determination that the refresh rate of the frames of the main thread of the target application reaches or exceeds a preset refresh rate.

13. The terminal device of claim 12, wherein the at least one processor is further caused to:

set a work mode of each of at least one of cores of the terminal device to be a low power mode after stopping accelerating the startup of the target application.