Android Customized Key Processing via Bypass Module

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Android input system cannot process user-customized keys without modifying the Android framework, leading to integration failures and system splits, as well as inability to synchronize and merge patches.

Innovation Solution

A processing method and device that utilize a key driver module and intermediate block module to map and convert key scan codes into specific key codes, bypassing the Android framework layer to send them to application programs for processing, thereby extending the Linux input driver to handle customized keys without affecting the Android system.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the Android framework is modified to add customized keys as predefined key values, then the Android input system can process user-customized keys, but integration of modified Android frameworks from multiple users fails and the Android backbone system splits

Engineering Contradiction:
Improvecustomized key processing capabilityVSAvoidAndroid framework integration stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the key processing system into three distinct layers: the Linux input driver layer (unchanged), the Android framework layer (unchanged), and a new customized key processing layer (block service block). This segmentation allows customized key functionality to be added without modifying the core Android framework, thereby maintaining integration stability while achieving customization capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary block service block that mediates between the Linux input driver and the Android framework. This intermediary component captures customized key events from the driver and translates them into Android-compatible key events, enabling customized key processing without directly modifying the Android framework structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If the Android framework is modified to add customized keys, then user-customized keys can be processed, but the modified Android framework cannot synchronize and merge patches related to the Android system

Engineering Contradiction:
Improvecustomized key processing capabilityVSAvoidpatch synchronization and merging
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent extracts the customized key processing functionality from the Android framework and places it in a separate block service block. This extraction ensures that the core Android framework remains unchanged and can continue to receive and apply patches normally, while the customized key functionality is maintained independently in the block service block.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent implements preliminary action by pre-configuring customized key mappings in the block service block before the Android framework is loaded. This allows customized key functionality to be established in advance without requiring modifications to the Android framework source code, thereby preserving the ability to synchronize and merge system patches.

Inventive Principle:
Principle #10Preliminary action

3Ease of manufacture

If customized keys are implemented without modifying the Android framework, then patch synchronization is maintained, but the Android input system cannot process user-customized keys

Engineering Contradiction:
Improvepatch synchronization capabilityVSAvoidcustomized key processing capability
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent introduces an intermediary block service block that acts as a bridge between the unchanged Android framework and the customized key processing requirements. This intermediary component translates customized key events into formats compatible with the Android framework, enabling customized key processing without modifying the framework itself and thus maintaining patch synchronization capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent applies parameter changes by transforming customized key events into equivalent Android framework key event parameters. The block service block converts customized key scan codes into corresponding Android key codes, allowing the unchanged Android framework to process customized keys through parameter transformation rather than structural modification.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11539825B2Processing method of customized key based on android platform and processing device using the same
Publication Date: 2022.12.27 REALTEK SEMICON CORP
  • US11539825B2 patent drawing
  • US11539825B2 patent drawing
  • US11539825B2 patent drawing

AI summary

A processing method of a customized key based on an Android platform includes receiving a key value of an input key, mapping the key value to a key scan code, identifying a to-be-blocked key according to the key scan code, converting, when the input key is the to-be-blocked key, the key scan code into a specific key code by a key block module, and sending, by bypassing an Android framework layer by the key block module, the specific key code to an application program for processing.