Method for controlling startup of application and terminal device

• US 10,552,178 B2
• Filed: 01/09/2019
• Issued: 02/04/2020
• 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/243,601
• Publication Number:
  US 20190146813A1
• Time in Patent Office: 391 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 mobile terminal upon detecting a control instruction of starting the target application;

when a time length required for successfully starting the target application is greater than or equal to a preset time length, determining a percentage of current idle cores of the mobile terminal, and determining, according to a pre-stored 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; and

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.

2. The method of claim 1, further comprising:

determining whether a refresh rate of frames of a main thread of the target application is greater than or equal to an accelerating stop refresh rate of the target application based on that the time length required for successfully starting the target application is less than the preset time length; and

stopping 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 is greater than the accelerating stop refresh rate.

3. The method of claim 1, further comprising:

obtaining multiple history records that the mobile terminal 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 mobile terminal, and the accelerating startup time length is greater than the preset time length; 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.

4. The method of claim 2, further comprising:

obtaining multiple history records that the mobile terminal 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 mobile terminal, and the accelerating startup time length is greater than the preset time length; 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:

setting a work mode of at least one core of the mobile terminal to be a low power mode.

6. The method of claim 2, further comprising:

setting a work mode of at least one core of the mobile terminal to be a low power mode.

7. A non-transitory computer readable storage medium, being configured to store one or more programs;

the one or more programs, when executed, being operable with a processor to;

accelerate startup of a target application of a mobile terminal upon detecting a control instruction of starting the target application;

when a time length required for successfully starting the target application is greater than or equal to a preset time length, determine a percentage of current idle cores of the mobile terminal, and determine, according to a pre-stored 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; and

stop accelerating the startup of the target application when a time length of accelerating the startup of the target application is greater than or equal to the accelerating startup time length.

8. The non-transitory computer readable storage medium of claim 7, wherein the one or more programs are further operable with the processor to:

determine whether a refresh rate of frames of a main thread of the target application is greater than or equal to an accelerating stop refresh rate of the target application based on that 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 when the refresh rate of the frames of the main thread of the target application is greater than the accelerating stop refresh rate.

9. The non-transitory computer readable storage medium of claim 7, wherein the one or more programs are further operable with the processor to:

obtain multiple history records that the mobile terminal 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 mobile terminal, and the accelerating startup time length is greater than the preset time length; and

determine, 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 determine, 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 non-transitory computer readable storage medium of claim 7, wherein the one or more programs are further operable with the processor to:

set a work mode of at least one core of the mobile terminal to be a low power mode.

11. A mobile terminal comprising:

a processor;

a memory;

a communication interface; and

a communication bus;

the processor, the memory, and the communication interface being coupled with and communicating with each other via the communication bus;

the memory storing executable program codes;

the communication interface being configured for wireless communication;

the processor being configured to invoke the executable program codes in the memory to perform following acts;

accelerating startup of a target application of the mobile terminal upon detecting a control instruction of starting the target application;

when a time length required for successfully starting the target application is greater than or equal to a preset time length, determining a percentage of current idle cores of the mobile terminal, and determining, according to a pre-stored 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; and

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.

12. The mobile terminal of claim 11, wherein the processor is further configured to invoke the executable program codes in the memory to perform following acts:

determining whether a refresh rate of frames of a main thread of the target application is greater than or equal to an accelerating stop refresh rate of the target application based on that the time length required for successfully starting the target application is less than the preset time length; and

stopping 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 is greater than the accelerating stop refresh rate.

13. The mobile terminal of claim 11, wherein the processor is further configured to invoke the executable program codes in the memory to perform following acts:

obtaining multiple history records that the mobile terminal 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 mobile terminal, and the accelerating startup time length is greater than the preset time length; 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.

14. The mobile terminal of claim 12, wherein the processor is further configured to invoke the executable program codes in the memory to perform following acts:

obtaining multiple history records that the mobile terminal 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 mobile terminal, and the accelerating startup time length is greater than the preset time length; 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.

15. The mobile terminal of claim 11, wherein the processor is further configured to invoke the executable program codes in the memory to perform following acts:

setting a work mode of at least one core of the mobile terminal to be a low power mode.