Background App Keep-Alive Locks for Memory and Power Cleanup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional electronic devices automatically clean background applications based on memory and power consumption without considering user needs, often closing applications that the user still requires, thereby affecting user experience.
Innovation Solution
An electronic device implements an application keep-alive method by automatically adding intelligent locks to predicted user-needed applications and allowing manual locks, with distinct identifiers and customizable durations, and provides a multi-task interface for user control.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of energy
If the mobile phone automatically cleans background applications based on power consumption and memory occupation, then power usage and memory usage are optimized, but essential applications may be mistakenly closed affecting user experience
Solution Approach 1:
The system introduces user feedback mechanisms including lock icons displayed on application thumbnails and confirmation dialogs. When memory or power is insufficient, the system presents locked applications to the user and seeks confirmation before closing them. This feedback loop ensures that applications the user intends to keep are protected from automatic cleaning, resolving the contradiction between power optimization and application continuity.
Solution Approach 2:
The system enables applications to self-identify their importance to the user through the lock icon mechanism. Applications that users lock are automatically protected from cleaning operations. This self-service approach allows applications to autonomously indicate their criticality without requiring continuous user intervention, balancing power efficiency with reliable application maintenance.
2Quantity of substance
If the mobile phone kills background processes to free memory, then available memory increases, but user workflow continuity is interrupted
Solution Approach 1:
The system performs preliminary actions by pre-locking applications that users are likely to need based on usage patterns and application importance. The lock icon is displayed in advance, allowing users to identify and protect critical applications before memory pressure occurs. This preliminary protection prevents unnecessary application restarts when memory is freed, reducing time loss while still allowing memory optimization for non-critical applications.
3Use of energy by moving object
If the mobile phone closes applications consuming high power, then power consumption decreases, but user experience deteriorates when needed applications are closed
Solution Approach 1:
The system provides visual feedback through lock icons displayed on application thumbnails in the recent apps interface. Users can see which applications are protected from power-saving cleanup operations. This transparency allows users to understand the system's power management behavior and adjust their locking preferences accordingly, improving ease of operation while maintaining power efficiency.
Solution Approach 2:
The system dynamically changes the protection parameter (lock status) of applications based on user interaction and system conditions. Applications can transition between locked and unlocked states, allowing the system to adapt power consumption levels while maintaining user experience. When users lock applications, those parameters change to prevent closure, ensuring needed applications remain active despite power saving modes.
Data Source
AI summary
This application provides an application keep-alive method and an electronic device. The method includes: An electronic device automatically performs a first locking operation on a first application running in the background, where the first application is an application that a user needs to continue to use. The electronic device displays a multi-task interface, where the multi-task interface includes a first preview interface corresponding to a first application and a second preview interface corresponding to a second application. The electronic device displays a first identifier on the first preview interface of the multi-task interface to indicate that an application lock of a first type is added to the first application. The electronic device performs a second locking operation on the second application, and displays a second identifier on the second preview interface, so as to indicate that an application lock of a second type is added to the second application.