AOD Display Wake-Up Control for Faster Touch Activation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current always on display (AOD) procedures in electronic devices take a long time to initiate after a screen touch event in a screen-off state, leading to a slow user experience due to sequential power-on and initialization processes.
Innovation Solution
The touchscreen driver immediately notifies the display driver to perform power-on and initialization procedures upon detecting a screen touch event, allowing parallel execution of power-on and AOD start processes, reducing overall time consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If the touchscreen driver transfers the screen touching event to the AOD application first, then the AOD application starts the always on display procedure, but the power-on procedure of the display screen is delayed, resulting in long time consumption
Solution Approach 1:
The touchscreen driver performs preliminary action by directly notifying the display driver to execute the power-on procedure immediately upon detecting a screen touching event, before the AOD application is fully activated. This preliminary power-on action occurs in parallel with the AOD application startup, significantly reducing the overall time consumption of the always on display procedure.
2Productivity
If the display screen is powered on and initialized after the AOD application starts, then the processing order is simple, but the user experience is slow due to sequential execution
Solution Approach 1:
The system performs preliminary power-on and initialization of the display screen before the AOD application completes its startup. The touchscreen driver directly triggers the display driver to power on the screen, and this power-on process runs in parallel with the AOD application initialization, achieving faster activation without excessive complexity.
Solution Approach 2:
The display driver acts as an intermediary between the touchscreen driver and the display screen. When the touchscreen driver detects a touch event, it notifies the display driver, which then coordinates the power-on and initialization of the display screen independently of the AOD application's execution flow, enabling parallel processing.
3Loss of time
If the power-on procedure is performed in parallel with AOD start procedure, then time consumption is reduced, but the coordination between drivers and applications becomes more complex
Solution Approach 1:
The touchscreen driver performs preliminary notification to the display driver immediately upon detecting a touch event, triggering the power-on procedure to start in parallel with the AOD application startup. This preliminary action establishes the parallel execution framework without requiring complex ongoing coordination.
Solution Approach 2:
The display driver autonomously manages the power-on and initialization process after being notified by the touchscreen driver. It independently handles the timing, duration checking, and completion notification to the AOD application, reducing the coordination burden on the application layer while enabling parallel execution.
Data Source
AI summary
After a touchscreen driver receives a screen touching event in a screen-off state, the touchscreen driver immediately notifies a display driver to perform a power-on procedure, so that a display screen starts power-on and initialization in advance. Further, as in a related technology, the touchscreen driver transfers the screen touching event in the screen-off state to an always on display (AOD) application, and the AOD application starts an always on display procedure.