Native Android Execution via Host OS Component Replacement

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Android apps cannot run natively on non-Android devices due to reliance on a specific runtime environment, leading to user interface inconsistencies, data sharing issues, and high resource requirements, limiting their deployment to servers and desktops rather than mobile devices.

Innovation Solution

Converting Android apps to a binary format compatible with Host Operating Systems, replacing standard Android components with Host OS equivalents, and mixing Android-generated content with Host OS content to create a unified user interface, allowing Android apps to run natively on any environment.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a Virtual Machine is used to run Android apps on non-Android devices, then Android apps can execute on foreign Operating Systems, but resource usage increases significantly and device compatibility is limited

Engineering Contradiction:

Improveplatform compatibilityVSAvoidresource usage

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential Android runtime components needed to execute individual apps, rather than virtualizing the entire Android OS. This selective extraction approach allows Android apps to run on non-Android devices with minimal resource overhead, eliminating the need for a full Virtual Machine while maintaining platform compatibility.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The Android operating system is segmented into individual runtime components and subsystems that can be selectively invoked. Instead of requiring the complete Android OS environment, the system divides Android functionality into discrete, on-demand components that are loaded only when needed by specific apps, reducing overall resource consumption.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If a Virtual Machine is used to isolate Android environment from host, then Android apps can run on foreign OS, but user interface consistency deteriorates and user experience degrades

Engineering Contradiction:

Improvecross-platform executionVSAvoiduser interface consistency

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces an intermediary layer that translates between Android app interface elements and the host operating system's native interface conventions. This mediator enables Android apps to execute on foreign OS while automatically adapting the user interface to match host OS design guidelines, ensuring visual consistency and familiar interaction patterns without requiring full VM isolation.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If entire Virtual Machine is deployed to mobile devices, then Android apps can run on portable devices, but resource requirements exceed available device capacity

Engineering Contradiction:

Improvedevice portabilityVSAvoidresource capacity

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system implements partial action by loading only the specific Android runtime components and subsystems required for executing individual apps, rather than deploying a complete Android Virtual Machine. This selective loading approach enables mobile devices with limited resources to run Android apps by allocating only the necessary computational resources on-demand.

Inventive Principle:

Principle #16Partial or excessive action

4Productivity

If Android apps are converted to Host OS binary format, then native execution is achieved, but conversion complexity increases

Engineering Contradiction:

Improveexecution efficiencyVSAvoidconversion process complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent replaces the mechanical process of manual or incremental app conversion with an automated compilation system. The Android Runtime includes a compiler that automatically converts Android app bytecode into Host OS native binary format during the app execution setup, eliminating complex manual conversion processes and enabling seamless native execution.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS9875099B2Computer-implemented method and system for executing android apps natively on any environment

Publication Date: 2018.01.23 MECHDOME INC

AI summary

A method for executing Android apps nativelyon any environment comprises converting one or more Android applications to a binary format of other applications in the Host Operating System. The Android applications are in one of a source format and a binary format. Further, all equivalent components are replaced from a standard Android environment with ones provided by the Host OS using the Host Operating System's capabilities. Furthermore, Android applications are executed natively by a Host Operating System. Moreover, the method includes mixing Android generated with content created by the Host Operating System to generate a final screen and the user views and interacts with the final screen.