Method for Controlling Application and Terminal Device

• US 20190146813A1
• Filed: 01/09/2019
• Published: 05/16/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
• Granted Patent: US 10,552,178 B2
• Time in Patent Office: 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:

obtaining a reference startup time length of a target application of a mobile terminal when a control instruction of starting the target application is detected;

accelerating startup of the target application when the reference startup time length is greater than or equal to a preset time length, obtaining a reference percentage of idle resources of 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 resources of the cores, an accelerating startup time length corresponding to the reference percentage of the idle resources of the 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;

obtaining the reference percentage of the idle resources of the cores of the mobile terminal comprises;

determining the reference percentage of the idle resources of the cores of the mobile terminal according to m idle cores of n cores of the mobile terminal;

or determining the reference percentage of the idle resources of the cores of the mobile terminal according to the m idle cores of the n cores of the mobile terminal and a percentage of remaining idle resources of each of n-m running cores.

2. The method of claim 1, further comprising:

accelerating the startup of the target application based on a determination that the reference startup time length is less than the preset time length, and 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; 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, wherein accelerating the startup of the target application comprises:

adjusting a work frequency of at least one core of the mobile terminal to be a preset frequency; and

starting the target application via all idle resources of the cores of the mobile terminal.

4. The method of claim 2, wherein accelerating the startup of the target application comprises:

adjusting a work frequency of at least one core of the mobile terminal to be a preset frequency; and

starting the target application via all idle resources of the cores of the mobile terminal.

5. The method of claim 1, wherein the method further comprises the following before the control instruction of starting the target application of the mobile terminal is detected:

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 resources of the 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 reference startup time length of 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 resources of the cores.

6. The method of claim 2, wherein the method further comprises the following before the control instruction of starting the target application of the mobile terminal is detected:

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 resources of the 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 reference startup time length of 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 resources of the cores.

7. The method of claim 1, wherein the method further comprises the following after stopping accelerating the startup of the target application:

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

8. The method of claim 2, wherein the method further comprises the following after stopping accelerating the startup of the target application:

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

9. A mobile terminal comprising:

a time length obtaining unit, configured to obtain a reference startup time length of a target application of the mobile terminal when a control instruction of starting the target application of the mobile terminal is detected;

a first accelerating startup unit, configured to accelerate startup of the target application when the reference startup time length is greater than or equal to a preset time length, obtain a reference percentage of idle resources of 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 resources of the cores, an accelerating startup time length corresponding to the reference percentage of the idle resources of the cores; and

a first accelerating stop unit, configured to 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;

the first accelerating startup unit configured to obtain the reference percentage of the idle resources of the cores of the mobile terminal is configured to;

determine the reference percentage of the idle resources of the cores of the mobile terminal according to m idle cores of n cores of the mobile terminal;

or

determine the reference percentage of the idle resources of the cores of the mobile terminal according to the m idle cores of the n cores of the mobile terminal and a percentage of remaining idle resources of each of n-m running cores.

10. The mobile terminal of claim 9, further comprising:

a second accelerating startup unit, configured to accelerate the startup of the target application when the reference startup time length is less than the preset time length, and 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; and

a second accelerating stop unit, configured to 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.

11. The mobile terminal of claim 9, wherein the first accelerating startup unit configured to accelerate the startup of the target application is configured to or the second accelerating startup unit configured to accelerate the startup of the target application is configured to:

adjust a work frequency of at least one core of the mobile terminal to be a preset frequency; and

start the target application via all idle resources of the cores of the mobile terminal.

12. The mobile terminal of claim 9, further comprising:

a record obtaining unit, configured to obtain multiple history records that the mobile terminal accelerated the startup of the target application before the time length obtaining unit detects the control instruction of starting the target application of the mobile terminal, wherein each of the history records contains an accelerating startup time length of the target application and a percentage of idle resources of the cores of the mobile terminal, and the accelerating startup time length is greater than the preset time length; and

a mapping relationship determining unit, configured to 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 reference startup time length of 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 resources of the cores.

13. The mobile terminal of claim 9, further comprising:

a low power consumption control unit, configured to set a work mode of at least one core of the mobile terminal to be a low power mode when the first accelerating stop unit or the second accelerating stop unit stops accelerating the startup of the target application.

14. 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;

obtaining a reference startup time length of a target application of a mobile terminal when a control instruction of starting the target application is detected;

accelerating startup of the target application when the reference startup time length is greater than or equal to a preset time length, obtaining a reference percentage of idle resources of 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 resources of the cores, an accelerating startup time length corresponding to the reference percentage of the idle resources of the 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; and

the processor being configured to invoke the executable program codes in the memory to perform obtaining the reference percentage of the idle resources of the cores of the mobile terminal is configured to perform following acts;

determining the reference percentage of the idle resources of the cores of the mobile terminal according to m idle cores of n cores of the mobile terminal;

or

determining the reference percentage of the idle resources of the cores of the mobile terminal according to the m idle cores of the n cores of the mobile terminal and a percentage of remaining idle resources of each of n-m running cores.

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

accelerating the startup of the target application based on a determination that the reference startup time length is less than the preset time length, and 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; 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.

16. The mobile terminal of claim 14, wherein the processor being configured to invoke the executable program codes in the memory to perform accelerating the startup of the target application is configured to perform following acts:

adjusting a work frequency of at least one core of the mobile terminal to be a preset frequency; and

starting the target application via all idle resources of the cores of the mobile terminal.

17. The mobile terminal of claim 15, wherein the processor being configured to invoke the executable program codes in the memory to perform accelerating the startup of the target application is configured to perform following acts:

adjusting a work frequency of at least one core of the mobile terminal to be a preset frequency; and

starting the target application via all idle resources of the cores of the mobile terminal.

18. The mobile terminal of claim 14, wherein the processor is further configured to invoke the executable program codes in the memory to perform following acts before the control instruction of starting the target application of the mobile terminal is detected:

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 resources of the 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 reference startup time length of 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 resources of the cores.

19. The mobile terminal of claim 15, wherein the processor is further configured to invoke the executable program codes in the memory to perform following acts before the control instruction of starting the target application of the mobile terminal is detected:

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 resources of the 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 reference startup time length of 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 resources of the cores.

20. The mobile terminal of claim 14, wherein the processor is further configured to invoke the executable program codes in the memory to perform following acts after stopping accelerating the startup of the target application:

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