WO2018126770A1 - 一种解决移动终端异常耗电的方法 - Google Patents

一种解决移动终端异常耗电的方法 Download PDF

Info

Publication number
WO2018126770A1
WO2018126770A1 PCT/CN2017/108160 CN2017108160W WO2018126770A1 WO 2018126770 A1 WO2018126770 A1 WO 2018126770A1 CN 2017108160 W CN2017108160 W CN 2017108160W WO 2018126770 A1 WO2018126770 A1 WO 2018126770A1
Authority
WO
WIPO (PCT)
Prior art keywords
name
current application
application
screen lock
bright screen
Prior art date
Application number
PCT/CN2017/108160
Other languages
English (en)
French (fr)
Inventor
刘可靖
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2018126770A1 publication Critical patent/WO2018126770A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3206—Monitoring of events, devices or parameters that trigger a change in power modality
    • G06F1/3228—Monitoring task completion, e.g. by use of idle timers, stop commands or wait commands
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234—Power saving characterised by the action undertaken
    • G06F1/325—Power saving in peripheral device
    • G06F1/3265—Power saving in display device

Definitions

  • the present disclosure relates to the field of mobile terminal technologies, and in particular, to a method, an apparatus, and a mobile terminal for solving abnormal power consumption of a mobile terminal.
  • the mobile terminal's operating system has an invisible screen mechanism that holds a bright screen lock. After the application holds the bright screen lock, the operating system will keep the screen of the mobile terminal intact.
  • the application such as photo, alarm clock, etc. needs to hold a bright screen lock to keep the screen intact when working, when the application exits or goes to When the background is running, the application releases the bright screen lock, the mobile terminal enters the screen, and the operating system goes to sleep to save power.
  • the operating system determines that the abnormally holds the bright screen lock or monitors the application to the background and continues to light up for a set period of time to notify the user.
  • the problem is that if the mobile terminal is not at the user's side, the user cannot handle the abnormal power consumption in time. Therefore, there is a need for a method, apparatus, and mobile terminal for solving abnormal power consumption of a mobile terminal to solve the above-mentioned technical problems existing in the related art.
  • the present disclosure provides a method, device, and mobile terminal for solving abnormal power consumption of a mobile terminal, which can actively handle abnormal power consumption, reduce power consumption of the mobile terminal, and improve user experience.
  • the technical solution adopted by the present disclosure is: monitoring a background switching operation before a current application occurs; forming a correspondence between a name of the current application and a corresponding status flag bit; and confirming existence of the current application based on the name of the current application
  • the name of the power-consuming application of the bright-screen lock is consistent with the name of the current application; based on the status identifier, the bright-screen lock identification position of the power-consuming application is the corresponding identifier.
  • the monitoring the background switching operation before the current application occurs includes: monitoring that the current application is switched from the foreground state to the background state; accordingly, forming the name and corresponding state of the current application
  • the correspondence between the flag bits includes: the current application is in a background state, and the state identifier position is 0.
  • the forming a correspondence between the name of the current application and the corresponding status flag bit is further included
  • the current application is in the foreground state, and the status identifier is set to 1.
  • the determining, according to the status identifier, the location of the bright screen lock of the power consumption application as a corresponding identifier comprising: if the status identifier position is 0, the location of the bright screen lock flag False; or, if the status flag is 1, the bright lock flag is set to true.
  • the method further includes: before the name of the application, confirming that the name of the power consumption application holding the bright screen lock is consistent with the name of the current application, the method further includes: in the current application
  • the bright screen lock is configured for the current application under the condition that it is in the background state and does not hold a bright screen lock.
  • the determining, according to the name of the application, that the name of the power consumption application holding the bright screen lock is consistent with the name of the current application including: holding the bright screen lock through the interface management module; receiving The name of the power consumption application sent by the interface management module; determining that the name of the power consumption application is consistent with the name of the current application.
  • the present disclosure further provides an apparatus for solving abnormal power consumption of a mobile terminal, comprising: a monitoring module configured to monitor a background switching operation before a current application occurs; a relationship forming module configured to form a name and corresponding of the current application Corresponding relationship of the status flag bits; the confirmation module is configured to confirm that the name of the power-consuming application holding the bright-screen lock is consistent with the name of the current application based on the name of the current application; And setting, according to the status identifier bit, the location of the bright screen lock identifier of the power consumption application as a corresponding identifier.
  • the monitoring module is configured to: monitor that the current application is switched from a foreground state to a background state; accordingly, the relationship forming module is configured to: the current application is in a background state, and the status identifier is The position is 0.
  • the relationship forming module is further configured to: the current application is in a foreground state, and the status identifier is set to 1.
  • the identification position bit module is configured to: if the status identification position is 0, the bright screen lock flag position is false; or, if the status identification position is 1, the bright screen is The lock flag is set to true.
  • the device further comprises a bright screen lock acquisition module configured to configure the bright screen lock for the current application under the condition that the current application is in a background state and does not hold a bright screen lock.
  • a bright screen lock acquisition module configured to configure the bright screen lock for the current application under the condition that the current application is in a background state and does not hold a bright screen lock.
  • the confirmation module is configured to: hold a bright screen lock through the interface management module; receive a name of the power consumption application sent by the interface management module; and determine a name and a location of the power consumption application The name of the current application is the same.
  • the present disclosure also provides a mobile terminal comprising the apparatus according to the above.
  • the present disclosure also provides a storage medium configured to store program code for performing the above The method of any of the preceding claims.
  • the present disclosure has at least the following effects:
  • the method for solving the abnormal power consumption of the mobile terminal provided by the present disclosure, when monitoring the background switching operation before the occurrence, the screen lock is performed on the screen of the mobile terminal based on the bright screen lock held by the application, and the method has low cost and saves the mobile terminal.
  • the power has improved the user experience.
  • FIG. 1 is a flowchart of a method for solving an abnormal power consumption of a mobile terminal according to a first embodiment of the present disclosure
  • FIG. 2 is a flowchart of a method for solving abnormal power consumption of a mobile terminal according to a second embodiment of the present disclosure
  • FIG. 3 is a flowchart of a method for solving abnormal power consumption of a mobile terminal according to a third embodiment of the present disclosure
  • FIG. 4 is a flowchart of a method for solving abnormal power consumption of a mobile terminal according to a fourth embodiment of the present disclosure
  • FIG. 5 is a block diagram of an apparatus for solving abnormal power consumption of a mobile terminal according to a fifth embodiment, a sixth embodiment, and a seventh embodiment of the present disclosure
  • FIG. 6 is a block diagram of an apparatus for solving abnormal power consumption of a mobile terminal according to an eighth embodiment of the present disclosure.
  • the method for abnormally consuming power of the mobile terminal reduces abnormal power consumption of the mobile terminal, improves the user experience, and the method is low in cost.
  • the method of abnormally consuming power consumption of the mobile terminal of the present disclosure and its respective steps will be described in detail below.
  • the method for solving the abnormal power consumption of the mobile terminal includes: Step S10: monitoring the background switching operation before the current application occurs.
  • Applications for applications installed on the mobile terminal such as video playback, camera recording, game software, etc.
  • the front-end switching operation includes the application switching from the foreground state to the background state, or the application is switched from the background state to the foreground state, as long as If the above-mentioned front and back office switching operations occur, they need to be monitored.
  • Step S20 Form a correspondence between the name of the current application and the corresponding status flag.
  • the status flag corresponds to the status of the current application after the background switching operation. For example, after the current application occurs before the background switching operation, the background flag is corresponding to the background status.
  • Step S30 Based on the name of the current application, confirm that the name of the power-consuming application holding the bright screen lock is consistent with the name of the current application. Traversing all power-hungry applications that hold a bright-screen lock to find a power-hungry application with a bright-screen lock, the power-consuming application The name of the sequence is the same as the name of the current application.
  • Step S40 Based on the status identifier, the bright screen lock identification position of the power consumption application is a corresponding identifier, and the bright screen lock identification position is expanded from the bright screen lock attribute structure held by the operating system to ensure each one. The power application holds the uniqueness of the lock.
  • the bright screen lock identification position of the power consumption application found in step S30 is the corresponding identifier. That is, if the identifier of the bright screen lock flag in the foreground state and the background state is different, the screen or the screen may be illuminated according to the difference of the bright screen lock flag of the power consumption application.
  • the current application in the above-mentioned background switching operation if the current application holds a bright screen lock, the current application is converted into a power consumption application, and the power consumption application mentioned in the present disclosure is held bright. Screen lock app.
  • step S10 monitoring the background switching operation before the current application occurs, including: step S100: monitoring out The current application is switched from the foreground state to the background state; correspondingly, step S20: forming a correspondence between the name of the current application and the corresponding status flag bit, including: step S200: the current application is in the background state, and the status identification location is 0.
  • step S40 based on the status identifier, the position of the bright screen lock of the power consumption application is the corresponding identifier, including: step S400: if the status identifier position is 0, the position of the bright screen lock flag is False. If the bright screen lock flag of the power-consuming application holding the bright screen lock is false, the screen of the mobile terminal is screened to reduce power consumption.
  • the method for solving the abnormal power consumption of the mobile terminal in this embodiment ensures the function of the application when the application is in the background state, does not actively turn off the application, and directly processes the abnormal power consumption, even if the user needs to be in the background state. When you switch to the foreground state, there will be no reopening of the application interface to affect the user experience.
  • step S20 forming a correspondence between the name of the current application and the corresponding status flag bit, further comprising: the current application is in the foreground state, and the status identification position is 1.
  • step S40 further includes: if the status identification position is 1, the position of the bright screen lock flag is true. The power-consuming application is in the foreground state, and the bright-screen lock flag of the bright-screen lock held by the power-consuming application is true, and the screen of the mobile terminal is illuminated.
  • a callback function is registered in the operating system, and the operating system monitors the front-end and background switching operations of the current application by using the callback function, and the current application that holds the bright screen lock by itself.
  • the operating system is based on the name of the current application.
  • the status flag bit is the corresponding identifier for the position of the bright screen lock flag, and then the screen of the mobile terminal is illuminated or processed according to the difference of the bright screen lock flag.
  • step S30 based on the name of the application, confirming that the name of the power-consuming application holding the bright screen lock is consistent with the name of the current application.
  • the method for solving the abnormal power consumption of the mobile terminal in this embodiment further includes: Step S50: configuring the bright screen lock for the current application under the condition that the current application is in the background state and does not hold the bright screen lock.
  • step S30 is performed again.
  • step S30 confirming the name of the power-consuming application holding the bright screen lock and the current application based on the name of the application.
  • the name of the program is consistent, including: step S300: holding a bright screen lock by the interface management module; step S301: receiving the name of the power consumption application sent by the interface management module; step S302: determining the name and current of the power consumption application
  • the names of the applications are the same.
  • the embodiment does not hold a bright screen lock for the current application itself, and holds a bright screen lock through the interface management module, for example, the current application is a current application that needs to hold a bright screen lock, such as a camera, an MP4, an alarm clock, an incoming call, and the like.
  • the operating system cannot obtain the name of the current application through the current application. Therefore, after the interface management module obtains the bright screen lock, the operating system receives the name of the power-consuming application that holds the bright screen lock sent by the interface management module. Determine that the name of the power-consuming application matches the name of the current application.
  • the device for solving the abnormal power consumption of the mobile terminal includes: a monitoring module 10 configured to monitor a background switching operation before the current application occurs; and the relationship forming module 20 is configured to form a current The correspondence between the name of the application and the corresponding status flag; the confirmation module 30 is configured to confirm that the name of the power-consuming application holding the bright-screen lock is consistent with the name of the current application based on the name of the current application; The bit module 40 is configured to position the bright screen lock of the power consuming application as a corresponding identifier based on the status identification bit.
  • This embodiment is only for the bright screen lock, but the above embodiment can be extended to FULL WAKELOCK, DIM WAKELOCK and SCREEN BRIGHT WAKELOCK, etc., which can make the mobile terminal bright or screen lock, and the same applies to this scheme.
  • the monitoring module 10 is configured to: monitor the current application to switch from the foreground state to the background state.
  • the module 20 is set to: the current application is in the background state, and the status identification position is 0.
  • the relationship forming module 20 is further configured to: the current application is in the foreground state, and the status identification position is set to 1.
  • the confirmation module 30 is configured to: hold the bright screen lock through the interface management module; receive the name of the power consumption application sent by the interface management module; determine the name of the power consumption application and the name of the current application Consistent.
  • the identification position bit module 40 is set to: if the status identification position is 0, the bright screen lock flag is set. The position is false; or, if the status flag is 1, the bright lock flag is set to true.
  • the apparatus for solving the abnormal power consumption of the mobile terminal in the embodiment further includes the bright screen lock acquisition module 50 being configured to: the current application is in the background state and is not held. Under the condition of a bright screen lock, configure a bright screen lock for the current application.
  • the present disclosure also provides a mobile terminal comprising the apparatus according to the above.
  • the method for solving the abnormal power consumption of the mobile terminal provided by the present disclosure, when monitoring the background switching operation before the occurrence, the screen lock is performed on the screen of the mobile terminal based on the bright screen lock held by the application, and the method has low cost and saves the mobile terminal.
  • the power has improved the user experience.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Telephone Function (AREA)

Abstract

一种解决移动终端异常耗电的方法、装置及移动终端。所述解决移动终端异常耗电的方法包括：监测出当前应用程序发生前后台切换操作（S10）；形成所述当前应用程序的名称和相应的状态标志位的对应关系（S20）；基于所述当前应用程序的名称，确认存在持有亮屏锁的耗电应用程序的名称与所述当前应用程序的名称一致（S30）；基于所述状态标识位，将所述耗电应用程序的亮屏锁标识位置为相应的标识（S40），主动处理异常耗电，改善了用户体验。

Description

一种解决移动终端异常耗电的方法 技术领域
本公开涉及移动终端技术领域，尤其涉及一种解决移动终端异常耗电的方法、装置及移动终端。
背景技术
移动终端的操作***具有一种不灭屏机制，该种机制持有亮屏锁。应用程序持有亮屏锁后，操作***会保持移动终端的屏幕不灭，比如拍照、闹钟等应用程序需要持有亮屏锁，以在工作时保持屏幕不灭，当应用程序退出或者转至后台运行时应用程序释放亮屏锁，移动终端息屏，操作***进入睡眠，达到省电的目的。
但是，对于有些应用程序在前台持有亮屏锁，在转至后台并不释放亮屏锁，异常持有亮屏锁，比如某个游戏软件，在用户玩好后将游戏置于后台，移动终端显示屏一直不灭，导致移动终端操作***功耗增大，并且应用程序已经退至后台不可见，不息屏对于移动终端来说也是一种异常。
针对上述异常耗电的情况，通常的做法是操作***判断出异常持有亮屏锁或者监测到应用程序转至后台持续亮屏达到设定时间段后通知用户。存在的问题是，如果移动终端不在用户身边，用户不能及时处理上述异常耗电。因此，需要一种解决移动终端异常耗电的方法、装置及移动终端，以解决相关技术中存在的上述技术问题。
发明内容
本公开提供一种解决移动终端异常耗电的方法、装置及移动终端，可以主动处理异常耗电，降低移动终端耗电，改善了用户体验。
本公开采用的技术方案是：监测出当前应用程序发生前后台切换操作；形成所述当前应用程序的名称和相应的状态标志位的对应关系；基于所述当前应用程序的名称，确认存在持有亮屏锁的耗电应用程序的名称与所述当前应用程序的名称一致；基于所述状态标识位，将所述耗电应用程序的亮屏锁标识位置为相应的标识。
优选地，所述监测出当前应用程序发生前后台切换操作，包括：监测出所述当前应用程序从前台状态切换至后台状态；相应地，所述形成所述当前应用程序的名称和相应的状态标志位的对应关系，包括：所述当前应用程序处于后台状态，将所述状态标识位置为0。
优选地，所述形成所述当前应用程序的名称和相应的状态标志位的对应关系，还包 括：所述当前应用程序处于前台状态，将所述状态标识位置为1。
优选地，所述基于所述状态标识位，将所述耗电应用程序的亮屏锁标识位置为相应的标识，包括：若所述状态标识位置为0，则将所述亮屏锁标志位置为false；或者，若所述状态标识位置为1，则将所述亮屏锁标志位置为true。
优选地，所述基于所述应用程序的名称，确认存在持有亮屏锁的耗电应用程序的名称与所述当前应用程序的名称一致之前，所述方法还包括：在所述当前应用程序处于后台状态并且未持有亮屏锁的条件下，为所述当前应用程序配置所述亮屏锁。
优选地，所述基于所述应用程序的名称，确认存在持有亮屏锁的耗电应用程序的名称与所述当前应用程序的名称一致，包括：通过界面管理模块持有亮屏锁；接收所述界面管理模块发来的所述耗电应用程序的名称；判断出所述耗电应用程序的名称与所述当前应用程序的名称一致。
本公开还提供了一种解决移动终端异常耗电的装置，包括：监测模块，设置为监测出当前应用程序发生前后台切换操作；关系形成模块，设置为形成所述当前应用程序的名称和相应的状态标志位的对应关系；确认模块，设置为基于所述当前应用程序的名称，确认存在持有亮屏锁的耗电应用程序的名称与所述当前应用程序的名称一致；标识位置位模块，设置为基于所述状态标识位，将所述耗电应用程序的亮屏锁标识位置为相应的标识。
优选地，所述监测模块设置为：监测出所述当前应用程序从前台状态切换至后台状态；相应地，所述关系形成模块设置为：所述当前应用程序处于后台状态，将所述状态标识位置为0。
优选地，所述关系形成模块还设置为：所述当前应用程序处于前台状态，将所述状态标识位置为1。
优选地，所述标识位置位模块设置为：若所述状态标识位置为0，则将所述亮屏锁标志位置为false；或者，若所述状态标识位置为1，则将所述亮屏锁标志位置为true。
优选地，所述装置，还包括亮屏锁获取模块设置为：在所述当前应用程序处于后台状态并且未持有亮屏锁的条件下，为所述当前应用程序配置所述亮屏锁。
优选地，所述确认模块设置为：通过界面管理模块持有亮屏锁；接收所述界面管理模块发来的所述耗电应用程序的名称；判断出所述耗电应用程序的名称与所述当前应用程序的名称一致。
本公开还提供了一种移动终端，包括根据上文所述装置。
本公开还提供了一种存储介质，设置为存储程序代码，所述程序代码用于执行如上 任一项所述的方法。
采用上述技术方案，本公开至少具有下列效果：
本公开提供的解决移动终端异常耗电的方法，在监测到出现前后台切换操作时，基于应用程序持有的亮屏锁对移动终端屏幕进行亮灭屏处理，方法实现成本低，节省移动终端的电量，改善了用户体验。
附图说明
图1为本公开第一实施例解决移动终端异常耗电的方法的流程图；
图2为本公开第二实施例解决移动终端异常耗电的方法的流程图；
图3为本公开第三实施例解决移动终端异常耗电的方法的流程图；
图4为本公开第四实施例解决移动终端异常耗电的方法的流程图；
图5为本公开第五实施例、第六实施例和第七实施例解决移动终端异常耗电的装置的方框图；
图6为本公开第八实施例解决移动终端异常耗电的装置的方框图。
具体实施方式
为更进一步阐述本公开为达成预定目的所采取的技术手段及功效，以下结合附图及较佳实施例，对本公开进行详细说明如后。
本公开提供的移动终端异常耗电的方法，降低了移动终端异常耗电，改善了用户体验，并且该方法实现成本低。下面将详细地描述本公开的移动终端异常耗电的方法及其各个步骤。
第一实施例
如图1所示，本实施例提供的一种解决移动终端异常耗电的方法，包括：步骤S10：监测出当前应用程序发生前后台切换操作。对移动终端安装的应用程序，例如视频播放，camera录像，游戏软件等应用程序进行监测，前后台切换操作包括应用程序由前台状态切换至后台状态，或者应用程序由后台状态切换至前台状态，只要发生上述前后台切换操作，则需要监测出。步骤S20：形成当前应用程序的名称和相应的状态标志位的对应关系。该状态标识位对应当前应用程序在前后台切换操作后的状态，例如当前应用程序发生前后台切换操作后转至后台，则相应的状态标志位对应的是后台状态。步骤S30：基于当前应用程序的名称，确认存在持有亮屏锁的耗电应用程序的名称与当前应用程序的名称一致。遍历所有持有亮屏锁的耗电应用程序，查找出持有亮屏锁的耗电应用程序，该耗电应用程 序的名称与当前应用程序的名称一致。步骤S40：基于状态标识位，将耗电应用程序的亮屏锁标识位置为相应的标识，该亮屏锁标识位从操作***持有的亮屏锁属性结构体里扩展而来，保证每一个耗电应用程序持有锁的唯一性。基于步骤S20中设置的当前应用程序对应的状态标识位，将步骤S30查找出来的耗电应用程序的亮屏锁标识位置为相应的标识。即如果耗电应用程序处于前台状态和后台状态的亮屏锁标识位的标识不一样，可以根据该耗电应用程序的亮屏锁标识位的不同点亮屏幕或者息屏。上文中的当前应用程序在进行前后台切换操作后，若该当前应用程序持有亮屏锁，则该当前应用程序转为耗电应用程序，本公开提到的耗电应用程序为持有亮屏锁的应用程序。
第二实施例
如图2所示，在第一实施例的基础上，本实施例的解决移动终端异常耗电的方法中，步骤S10：监测出当前应用程序发生前后台切换操作，包括：步骤S100：监测出当前应用程序从前台状态切换至后台状态；相应地，步骤S20：形成当前应用程序的名称和相应的状态标志位的对应关系，包括：步骤S200：当前应用程序处于后台状态，将状态标识位置为0。
如图2所示，步骤S40：基于状态标识位，将耗电应用程序的亮屏锁标识位置为相应的标识，包括：步骤S400：若状态标识位置为0，则将亮屏锁标志位置为false。若持有亮屏锁的耗电应用程序的亮屏锁标志位为false，则将移动终端的屏幕进行息屏，减少耗电。本实施例的解决移动终端异常耗电的方法，应用程序处于后台状态时保证该应用程序的功能，不主动关掉该应用程序，直接处理异常耗电，即使用户需要将处于后台状态的应用程序再切换到前台状态时，也不会出现重新打开应用界面而影响用户体验。
另外，步骤S20：形成当前应用程序的名称和相应的状态标志位的对应关系，还包括：当前应用程序处于前台状态，将状态标识位置为1。相应地，步骤S40还包括：若状态标识位置为1，则将亮屏锁标志位置为true。耗电应用程序处于前台状态，并且该耗电应用程序持有的亮屏锁的亮屏锁标志位为true，那么将移动终端的屏幕点亮。
第一实施例和第二实施例中，在操作***中注册一个回调函数，通过该回调函数中实现操作***对当前应用程序进行前后台切换操作的监测，自己持有亮屏锁的当前应用程序可以直接将自己的当前应用程序的名称发送至操作***，并且根据完成前后台切换操作后的当前应用程序处于前台状态还是后台状态，置好相应的状态标志位，操作***根据当前应用程序的名称和状态标志位对亮屏锁标志位置为相应的标识，再根据亮屏锁标识位的不同，对移动终端的屏幕进行点亮或者息屏处理。
第三实施例
如图3所示，在第一实施例和第二实施例的基础上，步骤S30：基于应用程序的名称，确认持有亮屏锁的耗电应用程序的名称与当前应用程序的名称一致之前，本实施例的解决移动终端异常耗电的方法，还包括：步骤S50：在当前应用程序处于后台状态并且未持有亮屏锁的条件下，为当前应用程序配置亮屏锁。
本实施例针对当前应用程序处于前台状态时没有持有亮屏锁，当前应用程序从前台状态转至后台状态时，为该当前应用程序配置亮屏锁，由此该当前应用程序转为持有亮屏锁的耗电应用程序。然后再执行步骤S30。
第四实施例
如图4所示，在第一实施例、第二实施例和第三实施例的基础上，步骤S30：基于应用程序的名称，确认持有亮屏锁的耗电应用程序的名称与当前应用程序的名称一致，包括：步骤S300：通过界面管理模块持有亮屏锁；步骤S301：接收界面管理模块发来的耗电应用程序的名称；步骤S302：判断出耗电应用程序的名称与当前应用程序的名称一致。
该实施例针对当前应用程序自身不持有亮屏锁，通过界面管理模块持有亮屏锁，比如当前应用程序为照相机、MP4、闹钟、来电通话等需要持有亮屏锁的当前应用程序，操作***通过上述当前应用程序无法获取该当前应用程序的名称，因此在界面管理模块获取亮屏锁后，操作***接收界面管理模块发来的持有亮屏锁的耗电应用程序的名称后再判断耗电应用程序的名称与当前应用程序的名称一致。
第五实施例
如图5所示，本实施例提供的一种解决移动终端异常耗电的装置，包括：监测模块10，设置为监测出当前应用程序发生前后台切换操作；关系形成模块20，设置为形成当前应用程序的名称和相应的状态标志位的对应关系；确认模块30，设置为基于当前应用程序的名称，确认持有亮屏锁的耗电应用程序的名称与当前应用程序的名称一致；标识位置位模块40，设置为基于状态标识位，将耗电应用程序的亮屏锁标识位置为相应的标识。
本实施例仅是针对亮屏锁进行了说明，但是上述实施例可以扩展至FULL WAKELOCK、DIM WAKELOCK和SCREEN BRIGHT WAKELOCK等一切可以使移动终端亮屏或者息屏的锁，同样适用于此方案。
第六实施例
如图5所示，在第五实施例的基础上，本实施例的解决移动终端异常耗电的装置中，监测模块10设置为：监测出当前应用程序从前台状态切换至后台状态。相应地，关系形 成模块20设置为：当前应用程序处于后台状态，将状态标识位置为0。
作为优选地，关系形成模块20还设置为：当前应用程序处于前台状态，将状态标识位置为1。
在一实施例中，确认模块30设置为：通过界面管理模块持有亮屏锁；接收界面管理模块发来的耗电应用程序的名称；判断出耗电应用程序的名称与当前应用程序的名称一致。
第七实施例
如图5所示，在第六实施例的基础上，本实施例的解决移动终端异常耗电的装置中，标识位置位模块40设置为：若状态标识位置为0，则将亮屏锁标志位置为false；或者，若状态标识位置为1，则将亮屏锁标志位置为true。
第八实施例
如图6所示，在第五实施例的基础上，本实施例的解决移动终端异常耗电的装置，还包括亮屏锁获取模块50设置为：在当前应用程序处于后台状态并且未持有亮屏锁的条件下，为当前应用程序配置亮屏锁。
第九实施例
本公开还提供了一种移动终端，包括根据上文所述装置。
通过示例性实施例的说明，应当可对本公开为达成预定目的所采取的技术手段及功效得以更加深入且具体的了解，然而所附图示仅是提供参考与说明之用，并非用来对本公开加以限制。
工业实用性
本公开提供的解决移动终端异常耗电的方法，在监测到出现前后台切换操作时，基于应用程序持有的亮屏锁对移动终端屏幕进行亮灭屏处理，方法实现成本低，节省移动终端的电量，改善了用户体验。

Claims (14)

  1. 一种解决移动终端异常耗电的方法，其中，包括：
    监测出当前应用程序发生前后台切换操作；
    形成所述当前应用程序的名称和相应的状态标志位的对应关系；
    基于所述当前应用程序的名称，确认存在持有亮屏锁的耗电应用程序的名称与所述当前应用程序的名称一致；
    基于所述状态标识位，将所述耗电应用程序的亮屏锁标识位置为相应的标识。
  2. 根据权利要求1所述的方法，其中，所述监测出当前应用程序发生前后台切换操作，包括：
    监测出所述当前应用程序从前台状态切换至后台状态；
    相应地，所述形成所述当前应用程序的名称和相应的状态标志位的对应关系，包括：
    所述当前应用程序处于后台状态，将所述状态标识位置为0。
  3. 根据权利要求2所述的方法，其中，所述形成所述当前应用程序的名称和相应的状态标志位的对应关系，还包括：
    所述当前应用程序处于前台状态，将所述状态标识位置为1。
  4. 根据权利要求3所述的方法，其中，所述基于所述状态标识位，将所述耗电应用程序的亮屏锁标识位置为相应的标识，包括：
    若所述状态标识位置为0，则将所述亮屏锁标志位置为false；或者，
    若所述状态标识位置为1，则将所述亮屏锁标志位置为true。
  5. 根据权利要求2至4中任一项所述的方法，其中，所述基于所述应用程序的名称，确认存在持有亮屏锁的耗电应用程序的名称与所述当前应用程序的名称一致之前，所述方法，还包括：
    在所述当前应用程序处于后台状态并且未持有亮屏锁的条件下，为所述当前应用程序配置所述亮屏锁。
  6. 根据权利要求1所述的方法，其中，所述基于所述应用程序的名称，确认存在持有亮屏锁的耗电应用程序的名称与所述当前应用程序的名称一致，包括：
    通过界面管理模块持有亮屏锁；
    接收所述界面管理模块发来的所述耗电应用程序的名称；
    判断出所述耗电应用程序的名称与所述当前应用程序的名称一致。
  7. 一种解决移动终端异常耗电的装置，其中，包括：
    监测模块，设置为监测出当前应用程序发生前后台切换操作；
    关系形成模块，设置为形成所述当前应用程序的名称和相应的状态标志位的对应关系；
    确认模块，设置为基于所述当前应用程序的名称，确认存在持有亮屏锁的耗电应用程序的名称与所述当前应用程序的名称一致；
    标识位置位模块，设置为基于所述状态标识位，将所述耗电应用程序的亮屏锁标识位置为相应的标识。
  8. 根据权利要求7所述的装置，其中，所述监测模块设置为：
    监测出所述当前应用程序从前台状态切换至后台状态；
    相应地，所述关系形成模块设置为：
    所述当前应用程序处于后台状态，将所述状态标识位置为0。
  9. 根据权利要求8所述的装置，其中，所述关系形成模块，还设置为：
    所述当前应用程序处于前台状态，将所述状态标识位置为1。
  10. 根据权利要求9所述的装置，其中，所述标识位置位模块设置为：
    若所述状态标识位置为0，则将所述亮屏锁标志位置为false；或者，
    若所述状态标识位置为1，则将所述亮屏锁标志位置为true。
  11. 根据权利要求8至10中任一项所述的装置，其中，所述装置，还包括亮屏锁获取模块，设置为：
    在所述当前应用程序处于后台状态并且未持有亮屏锁的条件下，为所述当前应用程序配置所述亮屏锁。
  12. 根据权利要求7所述的装置，其中，所述确认模块设置为：
    通过界面管理模块持有亮屏锁；
    接收所述界面管理模块发来的所述耗电应用程序的名称；
    判断出所述耗电应用程序的名称与所述当前应用程序的名称一致。
  13. 一种移动终端，其中，包括根据权利要求7至12中任一项所述装置。
  14. 一种存储介质，设置为存储程序代码，所述程序代码用于执行权利要求1至6中任一项所述的方法。
PCT/CN2017/108160 2017-01-03 2017-10-28 一种解决移动终端异常耗电的方法 WO2018126770A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710000684.9A CN108268116B (zh) 2017-01-03 2017-01-03 一种解决移动终端异常耗电的方法、装置及移动终端
CN201710000684.9 2017-01-03

Publications (1)

Publication Number Publication Date
WO2018126770A1 true WO2018126770A1 (zh) 2018-07-12

Family

ID=62771521

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/108160 WO2018126770A1 (zh) 2017-01-03 2017-10-28 一种解决移动终端异常耗电的方法

Country Status (2)

Country Link
CN (1) CN108268116B (zh)
WO (1) WO2018126770A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110134219A (zh) * 2019-05-13 2019-08-16 深圳传音通讯有限公司 应用程序后台耗电处理方法及装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110572866B (zh) * 2019-07-26 2021-03-30 华为技术有限公司 一种唤醒锁的管理方法及电子设备
CN112565508B (zh) * 2019-09-26 2022-07-22 华为技术有限公司 处理方法及移动设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101788926A (zh) * 2009-12-28 2010-07-28 中兴通讯股份有限公司 J2me应用前台切换的资源调配方法及装置
JP2014075093A (ja) * 2012-10-05 2014-04-24 Sharp Corp 情報処理端末およびプログラム
CN106055073A (zh) * 2016-05-31 2016-10-26 广东欧珀移动通信有限公司 一种基于亮屏锁的处理方法和装置
CN106502372A (zh) * 2016-11-28 2017-03-15 珠海市魅族科技有限公司 一种应用控制的方法及移动终端

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110040989A1 (en) * 2009-06-22 2011-02-17 David Keyes Keyes Systems and methods for managing power consumption of mobile computing devices
CN104731302B (zh) * 2013-12-20 2018-01-12 北京猎豹移动科技有限公司 一种移动终端省电操作的方法及***
US9841802B2 (en) * 2014-02-20 2017-12-12 Qualcomm Incorporated Wake lock management through application monitoring
CN105653903B (zh) * 2015-12-18 2019-10-08 小米科技有限责任公司 应用程序权限的管理方法及装置
CN105867590A (zh) * 2016-03-28 2016-08-17 乐视控股（北京）有限公司 一种移动终端的应用程序控制方法及装置
CN106055077A (zh) * 2016-05-31 2016-10-26 广东欧珀移动通信有限公司 一种基于唤醒锁的处理方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101788926A (zh) * 2009-12-28 2010-07-28 中兴通讯股份有限公司 J2me应用前台切换的资源调配方法及装置
JP2014075093A (ja) * 2012-10-05 2014-04-24 Sharp Corp 情報処理端末およびプログラム
CN106055073A (zh) * 2016-05-31 2016-10-26 广东欧珀移动通信有限公司 一种基于亮屏锁的处理方法和装置
CN106502372A (zh) * 2016-11-28 2017-03-15 珠海市魅族科技有限公司 一种应用控制的方法及移动终端

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110134219A (zh) * 2019-05-13 2019-08-16 深圳传音通讯有限公司 应用程序后台耗电处理方法及装置
CN110134219B (zh) * 2019-05-13 2024-03-19 深圳传音通讯有限公司 应用程序后台耗电处理方法及装置

Also Published As

Publication number Publication date
CN108268116B (zh) 2022-06-07
CN108268116A (zh) 2018-07-10

Similar Documents

Publication Publication Date Title
WO2018126770A1 (zh) 一种解决移动终端异常耗电的方法
US10080194B2 (en) Method, device, and computer-readable storage medium for awaking electronic equipment
US20170083220A1 (en) Method and apparatus for controlling devices
WO2016029706A1 (zh) 终端的业务处理方法及装置
US20160062843A1 (en) Methods and devices for backing up file
JP2019505031A (ja) 端末ベースのウェイクロック制御の方法、装置及び端末
CN108829229B (zh) 屏幕控制方法、装置、存储介质及智能终端
US9706170B2 (en) Communication apparatus, communication system, and communication management system
JP6658941B2 (ja) 撮像装置、撮像方法、及びプログラム
CN106411574B (zh) 一种管理控制方法和装置
CN101854253B (zh) 一种自动恢复监控和存储的方法及其监控***
US10018981B2 (en) Monitoring removal of an automation control panel
WO2017051312A1 (en) A method of enabling a lock button of a mobile device with an ios operating system to be used by a user to effect an action
CN104516704A (zh) 一种多屏***中应用激活控制方法、装置及移动终端
CN101984641B (zh) 移动终端的背光控制方法及移动终端
CN112099990A (zh) 一种容灾备份方法、装置、设备及机器可读存储介质
WO2016177219A1 (zh) 一种功耗异常检测方法及装置
CN110493135B (zh) 通信装置、控制方法以及计算机可读存储介质
CN110019065B (zh) 日志数据的处理方法、装置及电子设备
CN103809980A (zh) 一种信息处理方法、信息处理装置和电子设备
US20110291833A1 (en) Intercom exchange
JP6413257B2 (ja) 伝送端末、伝送システム、及びプログラム
CN110662280A (zh) 运行模式的切换方法及装置、可读存储介质、电子设备
JP2011066789A (ja) 携帯アプリケーション操作システムおよび該システムを組み込んだ携帯電話ならびにそのためのプログラム
US11662704B1 (en) Monitoring removal of an automation control panel

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: 17890287

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: 17890287

Country of ref document: EP

Kind code of ref document: A1