Method, device and terminal equipment for controlling an android app

Abstract

The application provides a method and device for controlling an Android APP and a terminal device, and relates to the technical field of computer control. According to the method, the Windows terminal device can create a shortcut for the Android APP in the commonly used control areas such as the start menu, settings, control panel and desktop based on the Android emulator platform, so that the user can easily view, start, uninstall or change the Android APP at the corresponding shortcut location of the Windows terminal device. Since the method can realize the same way of operating the Android APP on the Windows operating system as the way of operating the Windows software, it conforms to the conventional operation habits of Windows users, and the user does not need to manually trigger the emulator to start and use the Android APP by operating the main interface of the emulator, so that the method can improve the user experience.

Description

Technical Field

[0001] This application relates to the field of computer control technology, and in particular to a method, apparatus and terminal device for controlling an Android APP. Background Technology

[0002] With the further convergence of personal computers (PCs) and mobile phones, PCs running Windows are increasingly able to use Android applications (apps) on mobile devices via emulator virtualization technology. Users can use Android apps on Windows through emulator software.

[0003] Currently, to use Android apps on a PC, an emulator is typically installed. Users can then perform various actions on the emulator to download, launch, or uninstall the Android app. Specifically, to launch an Android app on a PC, the user first needs to find and launch the emulator software. The emulator's main interface will then appear on the PC desktop. The user then needs to locate the Android app's icon on the emulator's main interface and interact with it to launch and run the app. Alternatively, if the desired Android app is not displayed on the emulator's main interface, the user needs to find and launch the app store app within the emulator's main interface. The app will then be downloaded and installed. Once installed, the installed app's icon will appear on the emulator's main interface for the user to select and use. Similarly, to uninstall an Android app on a PC, the user still needs to launch the emulator, locate the app's icon on the emulator's main interface, and then uninstall it.

[0004] The process of using Android apps on a PC requires a series of operations on the emulator's main interface to download, launch, or uninstall the Android app, which is cumbersome and affects the user experience. Summary of the Invention

[0005] This application provides a method, apparatus, and terminal device for controlling Android apps, which enables convenient operation of Android apps on a Windows operating system without the need to install, open, or uninstall Android apps through the main interface of an emulator, thus improving the user experience.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] Firstly, this application provides a method for controlling an Android app on a Windows operating system. This method is applied to a terminal device running a Windows operating system and includes:

[0008] In response to a user's installation, opening, or uninstallation of a target Android APP on the terminal device, the target Android APP is installed, opened, or uninstalled via an Android emulator. The target Android APP is an application suitable for the Android operating system.

[0009] When the target Android APP is installed on the Android emulator, a shortcut icon of the target Android APP is displayed on the terminal device;

[0010] Alternatively, when the target Android APP is launched on the Android emulator, the running interface of the target Android APP is displayed on the desktop of the terminal device;

[0011] Alternatively, if the target Android app is uninstalled on the Android emulator, the shortcut icon of the target Android app can be deleted from the terminal device.

[0012] The proposed solution allows Windows terminal devices to create shortcuts for Android apps in frequently used control areas based on an Android emulator platform. This enables convenient control of Android apps on the Windows operating system (e.g., downloading, launching, uninstalling, or modifying them), just like operating Windows software on a Windows operating system. This aligns with the conventional operating habits of Windows users, eliminating the need for users to manually launch the emulator or operate the Android app through the emulator's main interface. Therefore, this solution enhances the user experience.

[0013] In a possible implementation of the first aspect, the above-mentioned response to a user's installation, opening, or uninstallation of the target Android APP on the terminal device, via the Android emulator, includes:

[0014] In response to a user's installation, opening, or uninstallation of a target Android app on the terminal device, the Android emulator is launched in the background of the terminal device to install, open, or uninstall the target Android app.

[0015] From the user's perspective, the proposed solution works because the emulator runs in the background and is not displayed in the foreground (i.e., the Windows operating system desktop). Therefore, the user is unaware of the emulator and intuitively feels as if they are directly controlling an Android app on the Windows operating system. This aligns with the conventional operating habits of Windows users and thus improves the user experience.

[0016] In a possible implementation of the first aspect, displaying a shortcut icon for the target Android app on the terminal device includes:

[0017] The Android emulator calls the Windows operating system's first application programming interface (API) to create a shortcut to the target Android app on the terminal device, triggering the display of the shortcut icon of the target Android app on the terminal device.

[0018] In a possible implementation of the first aspect, displaying a shortcut icon for the target Android app on the terminal device includes:

[0019] A shortcut icon for the target Android app is displayed in the start menu of the terminal device;

[0020] And / or, display a shortcut icon for the target Android app in the uninstall or change program interface under the control panel of the terminal device;

[0021] And / or, display a shortcut icon for the target Android app on the desktop of the terminal device;

[0022] And / or, display a shortcut icon for the target Android app in the application function interface under the settings of the terminal device.

[0023] This solution allows Windows terminal devices to create shortcuts for Android apps in commonly used control areas such as the Start Menu, Settings, Control Panel, and Desktop, based on an Android emulator platform. This makes it convenient for users to view, launch, uninstall, or modify Android apps from the corresponding shortcut locations on the Windows terminal device.

[0024] In one possible implementation of the first aspect, the filename corresponding to the shortcut icon includes preset characters and the application name of the target Android APP; wherein, the preset characters can be blank characters or invisible characters.

[0025] Among the possible implementations of the first aspect, the above method also includes:

[0026] In response to a user's triggered installation operation on the target Android APP on the terminal device, the first installation package of the target Android APP is downloaded;

[0027] The first installation package of the target Android APP is stored in a shared path on the terminal device.

[0028] In one possible implementation of the first aspect, downloading the first installation package of the target Android APP includes: downloading the first installation package of the target Android APP from an app store;

[0029] The step of responding to the user's triggered installation operation on the target Android APP on the terminal device includes: responding to the user's triggered installation operation on the installation control corresponding to the target Android APP in the application market.

[0030] In one possible implementation of the first aspect, if the application market is an exe file and is installed on the terminal device, then when the exe file is launched, the running interface of the application market is presented on the terminal device; or, if the application market is an exe file and is associated with an application market apk installed in the Android emulator, then when the terminal device receives a user's instruction to run the exe file, the application market apk in the Android emulator is launched, and the running interface of the application market is displayed on the terminal device.

[0031] In a possible implementation of the first aspect, installing the target Android app via the Android emulator includes:

[0032] The application market sends the application name information and installation package storage path information of the target Android APP to the Android emulator through inter-process communication;

[0033] The Android emulator obtains the first installation package of the target Android APP according to the shared path indicated by the installation package storage path information of the target Android APP and the application name information of the target Android APP.

[0034] The Android emulator loads the first installation package of the target Android APP through the Android system to install the target Android APP.

[0035] Among the possible implementations of the first aspect, the above method also includes:

[0036] When the target Android APP is installed on the Android emulator, the Android emulator obtains the application information of the target Android APP. The application information of the target Android APP includes the package name, application icon, application name, version information, screen orientation information, installation time and / or name identifier corresponding to the target Android APP.

[0037] The Android emulator generates a second installation package associated with the shortcut icon of the target Android APP in the terminal device based on the application information of the target Android APP. The second installation package includes the application name corresponding to the target Android APP, application configuration information, a driver for starting the target Android APP, and a driver for uninstalling / updating the target Android APP.

[0038] In a possible implementation of the first aspect, after installing the target Android app, the method further includes:

[0039] The Android emulator sends a first response message to the application market via inter-process communication. The first response message includes the package name of the target Android APP and the result that the target Android APP has been installed.

[0040] Based on the first response message, the app store updates the display of the installation control corresponding to the target Android APP in the app store to an activation control.

[0041] In a possible implementation of the first aspect, the above-mentioned response to a user's operation to open the target Android APP on the terminal device, opening the target Android APP via the Android emulator, includes:

[0042] In response to the user's opening operation on the shortcut icon of the target Android APP, the terminal device calls the driver program for opening the target Android APP in the second installation package associated with the shortcut icon of the target Android APP, triggers the Android emulator to enable the APP opening function; and reads the package name of the target Android APP from the application configuration information of the second installation package and sends the package name of the target Android APP to the Android emulator.

[0043] The Android emulator locates the target Android APP in the emulator based on the package name of the target Android APP, draws the first window corresponding to the target Android APP on the terminal device, and opens the target Android APP through the Android system, placing the running interface of the target Android APP into the first window.

[0044] In a possible implementation of the first aspect, the above-mentioned response to a user's uninstallation operation on the target Android APP on the terminal device, uninstalling the target Android APP via the Android emulator, includes:

[0045] In response to the user's uninstall operation on the shortcut icon of the target Android APP on the terminal device, the terminal device calls the driver for uninstalling the target Android APP in the second installation package corresponding to the target Android APP, triggers the Android emulator to enable the APP uninstallation function; and reads the package name of the target Android APP from the application configuration information of the second installation package, and sends the package name of the target Android APP to the Android emulator.

[0046] The Android emulator locates the target Android app within itself based on the app's package name and then uninstalls the target Android app through the Android system.

[0047] In a possible implementation of the first aspect, deleting the shortcut icon of the target Android app on the terminal device includes:

[0048] The Android emulator calls the second API of the Windows operating system to delete the shortcut icon of the target Android APP and the second installation package from the terminal device.

[0049] In a possible implementation of the first aspect, after uninstalling the target Android app, the method further includes:

[0050] The Android emulator sends a second response message to the application market in the terminal device via inter-process communication. The second response message includes the package name of the target Android APP and the result that the target Android APP has been uninstalled.

[0051] Based on the second response message, the app market updates the display of the launch control corresponding to the target Android app as an installation control.

[0052] Secondly, this application provides a method for controlling an Android app, which is applied to an Android emulator, and the method includes:

[0053] The Android emulator installs, opens, or uninstalls the target Android APP according to the first instruction; the first instruction is triggered by the user performing the installation, opening, or uninstallation operation on the target Android APP on a terminal device running a Windows operating system, and the target Android APP is an application suitable for the Android operating system;

[0054] When the target Android APP is installed on the Android emulator, the Android emulator creates a shortcut to the target Android APP on the terminal device;

[0055] Alternatively, when the target Android APP is launched on the Android emulator, the Android emulator displays the running interface of the target Android APP on the desktop of the terminal device;

[0056] Alternatively, if the target Android app is uninstalled by the Android emulator, the Android emulator may delete the shortcut of the target Android app from the terminal device.

[0057] This solution allows Android emulators to create shortcuts for Android apps in the common control areas of Windows terminal devices, enabling convenient control of Android apps on the Windows operating system (e.g., downloading, launching, uninstalling, or modifying them). This is similar to operating Windows software on a Windows operating system, conforming to the conventional operating habits of Windows users, without requiring users to manually trigger the emulator to start or to operate the Android app through the emulator's main interface. Therefore, this solution can improve the user experience.

[0058] In the second possible implementation, the aforementioned Android emulator installs, opens, or uninstalls the target Android app according to the first instruction, including:

[0059] In response to the first instruction, the Android emulator starts in the background;

[0060] The Android emulator installs, opens, or uninstalls the target Android app according to the first instruction.

[0061] In a possible implementation of the second aspect, the aforementioned Android emulator creates a shortcut to the target Android app on the terminal device, including:

[0062] The Android emulator calls the Windows operating system's first application programming interface (API) to create a shortcut to the target Android app on the terminal device, triggering the display of the shortcut icon of the target Android app on the terminal device.

[0063] In a possible implementation of the second aspect, the aforementioned Android emulator creates a shortcut to the target Android app on the terminal device, including:

[0064] The Android emulator creates a shortcut to the target Android app in the start menu of the terminal device;

[0065] And / or, the Android emulator creates a shortcut to the target Android APP in the uninstall or change program interface under the control panel of the terminal device;

[0066] And / or, the Android emulator creates a shortcut to the target Android APP on the desktop of the terminal device;

[0067] And / or, the Android emulator creates a shortcut to the target Android APP in the application function interface under the settings of the terminal device.

[0068] In a possible implementation of the second aspect, the filename corresponding to the shortcut icon includes preset characters and the application name of the target Android APP; wherein, the preset characters can be blank characters or invisible characters.

[0069] In a possible implementation of the second aspect, the first instruction is triggered by the user installing the target Android APP through an application market installed on the terminal device;

[0070] The Android emulator installs the target Android app according to the first instruction, including:

[0071] The Android emulator receives the first instruction sent by the application market through inter-process communication. The first instruction includes the application name information and installation package storage path information of the target Android APP.

[0072] The Android emulator obtains the first installation package of the target Android APP according to the shared path indicated by the installation package storage path information of the target Android APP and the application name information of the target Android APP.

[0073] The Android emulator loads the first installation package of the target Android APP through the Android system to install the target Android APP.

[0074] In possible implementations of the second aspect, the above method also includes:

[0075] When the target Android APP is installed on the Android emulator, the Android emulator obtains the application information of the target Android APP. The application information of the target Android APP includes the package name, application icon, application name, version information, screen orientation information, installation time and / or name identifier corresponding to the target Android APP.

[0076] The Android emulator generates a second installation package associated with the shortcut icon of the target Android APP in the terminal device based on the application information of the target Android APP. The second installation package includes the application name corresponding to the target Android APP, application configuration information, a driver for starting the target Android APP, and a driver for uninstalling / updating the target Android APP.

[0077] In a possible implementation of the second aspect, after the Android emulator installs the target Android app according to the first instruction, the method further includes:

[0078] The Android emulator sends a first response message to the application market in the terminal device via inter-process communication. The first response message includes the package name of the target Android APP and the result that the target Android APP has been installed.

[0079] In a possible implementation of the second aspect, the first instruction is triggered by the user performing an opening operation on the shortcut icon of the target Android APP in the terminal device, or by the user performing an opening operation on the opening control corresponding to the target Android APP in the application market in the terminal device.

[0080] The Android emulator launches the target Android APP according to the first instruction, including: when the target Android APP is installed on the Android emulator, in response to the first instruction, the Android emulator calls the driver program for launching the target Android APP in the second installation package associated with the shortcut icon of the target Android APP, thereby triggering the Android system to launch the target Android APP;

[0081] The Android emulator displays the running interface of the target Android APP on the desktop of the terminal device, including: the Android emulator draws a first window for the target Android APP on the desktop of the terminal device, and adds the running interface of the target Android APP to the first window through the Android system.

[0082] In a possible implementation of the second aspect, the aforementioned Android emulator draws a first window for the target Android APP on the desktop of the terminal device, including:

[0083] The Android emulator draws the first window on the desktop of the terminal device according to the landscape and portrait screen information corresponding to the target Android APP.

[0084] In a possible implementation of the second aspect, when the screen orientation information indicates landscape mode, the horizontal dimension of the first window drawn by the Android emulator is greater than its vertical dimension. When the screen orientation information indicates portrait mode, the vertical dimension of the first window drawn by the Android emulator is greater than its horizontal dimension.

[0085] In a possible implementation of the second aspect, the first instruction is triggered by the user performing an uninstallation operation on the shortcut icon of the target Android APP in the terminal device;

[0086] The Android emulator uninstalls the target Android APP according to the first instruction, including: the Android emulator calls the driver for uninstalling the target Android APP in the second installation package corresponding to the target Android APP according to the first instruction, reads the package name of the target Android APP from the application configuration information of the second installation package, finds the target Android APP according to the package name of the target Android APP, and uninstalls the target Android APP through the Android system.

[0087] In a possible implementation of the second aspect, after uninstalling the target Android app, the method further includes:

[0088] The Android emulator sends a second response message to the application market in the terminal device via inter-process communication. The second response message includes the package name of the target Android APP and the result that the target Android APP has been uninstalled.

[0089] Thirdly, this application provides a device for controlling an Android app, the device including units for performing the methods described in the first aspect above. This device can correspond to performing the methods described in the first aspect above; for a brief description of the units in this device, please refer to the description in the first aspect above, and for simplicity, it will not be repeated here.

[0090] Fourthly, this application provides a device for controlling an Android app, the device including units for performing the methods described in the second aspect above. This device can correspond to performing the methods described in the second aspect above; for a brief description of the units in this device, please refer to the description in the second aspect above, and for simplicity, it will not be repeated here.

[0091] The methods described in the first or second aspect above can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the aforementioned functions. For example, a processing module or unit.

[0092] Fifthly, this application provides a terminal device including a processor coupled to a memory for storing computer programs or instructions. The processor executes the computer programs or instructions stored in the memory, causing the method in the first aspect to be performed. For example, the processor executes the computer programs or instructions stored in the memory, causing the device to perform the method in the first aspect.

[0093] Sixthly, this application provides a terminal device including a processor coupled to a memory for storing computer programs or instructions. The processor executes the computer programs or instructions stored in the memory, causing the method in the second aspect to be performed. For example, the processor executes the computer programs or instructions stored in the memory, causing the device to perform the method in the second aspect.

[0094] In a seventh aspect, this application provides a computer-readable storage medium having a computer program (also referred to as instructions or code) stored thereon for implementing the method of the first aspect. For example, when the computer program is executed by a computer, it enables the computer to perform the method of the first aspect.

[0095] Eighthly, this application provides a computer-readable storage medium having a computer program (also referred to as instructions or code) stored thereon for implementing the method of the second aspect. For example, when the computer program is executed by a computer, it enables the computer to perform the method of the second aspect.

[0096] In a ninth aspect, this application provides a chip including a processor. The processor is configured to read and execute a computer program stored in a memory to perform the methods of the first aspect and any possible implementation thereof. Optionally, the chip further includes a memory connected to the processor via a circuit or wire.

[0097] In a tenth aspect, this application provides a chip including a processor. The processor is configured to read and execute a computer program stored in a memory to perform the methods of the second aspect and any possible implementation thereof. Optionally, the chip further includes a memory connected to the processor via a circuit or wire.

[0098] In one aspect, this application provides a computer program product comprising a computer program (also referred to as instructions or code), which, when executed by a computer, causes the computer to implement the method in the first aspect.

[0099] In a twelfth aspect, this application provides a computer program product comprising a computer program (also referred to as instructions or code) that, when executed by a computer, causes the computer to implement the method of the second aspect.

[0100] It is understood that the beneficial effects of the third to twelfth aspects mentioned above can be found in the relevant descriptions in the first or second aspects mentioned above, and will not be repeated here. Attached Figure Description

[0101] Figure 1 This is a schematic diagram of the interface for using an Android app on a PC in the prior art.

[0102] Figure 2 This is one of the flowcharts illustrating the method for controlling the installation of an Android app provided in this application embodiment.

[0103] Figure 3 This is one of the interface diagrams illustrating the method for controlling the installation of an Android APP provided in this application embodiment, applied to a PC.

[0104] Figure 4 The second schematic diagram of the interface of the method for controlling the installation of Android APP provided in the embodiments of this application applied to a PC.

[0105] Figure 5 The third schematic diagram of the interface of the method for controlling the installation of Android APP provided in the embodiments of this application applied to a PC.

[0106] Figure 6 The fourth schematic diagram of the interface of the method for controlling the installation of Android APP provided in the embodiments of this application applied to a PC.

[0107] Figure 7 The fifth schematic diagram of the interface of the method for controlling the installation of Android APP provided in the embodiments of this application applied to a PC.

[0108] Figure 8 This is a second flowchart illustrating the method for controlling the installation of an Android app provided in this application embodiment.

[0109] Figure 9 The sixth schematic diagram of the interface of the method for controlling the installation of Android APP provided in this application embodiment applied to a PC.

[0110] Figure 10 This is one of the flowcharts illustrating the method for controlling the opening of an Android app provided in this application embodiment.

[0111] Figure 11 This is a second flowchart illustrating the method for controlling the opening of an Android app provided in this application embodiment.

[0112] Figure 12 The diagram illustrates the interface of the method for controlling the opening of an Android app provided in this embodiment of the application on a PC.

[0113] Figure 13 This is one of the flowcharts illustrating the method for controlling the uninstallation of an Android app provided in this application embodiment.

[0114] Figure 14 This is a second flowchart illustrating the method for controlling the uninstallation of an Android app provided in this application embodiment.

[0115] Figure 15This is a schematic diagram illustrating the naming of desktop shortcuts in the method for controlling the installation of Android apps provided in this application embodiment.

[0116] Figure 16 This is a flowchart illustrating a method for controlling the installation, opening, or uninstallation of an Android app, as provided in an embodiment of this application.

[0117] Figure 17 This is one of the structural schematic diagrams of a device for controlling an Android APP provided in an embodiment of this application.

[0118] Figure 18 This is a second schematic diagram of a device for controlling an Android APP, provided in an embodiment of this application.

[0119] Figure 19 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Detailed Implementation

[0120] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0121] In this article, the term "and / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The symbol " / " in this article indicates that the related objects are in an "or" relationship; for example, A / B means A or B.

[0122] The terms "first" and "second," etc., used in the specification and claims herein are used to distinguish different objects, not to describe a specific order of objects. For example, "first response message" and "second response message," etc., are used to distinguish different response messages, not to describe a specific order of response messages.

[0123] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0124] In the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more, for example, multiple processing units means two or more processing units, multiple elements means two or more elements, etc.

[0125] An Android emulator is software that allows you to run and simulate the Android system on a PC, and to install, run, and uninstall Android apps. After installing the emulator on your PC, you can operate it from the emulator's main interface to trigger the download, launch, or uninstallation of Android apps. This allows you to use Android apps on your PC. See below for reference. Figure 1 This document provides an exemplary description of how to use an Android app on a Windows operating system PC in existing technical solutions.

[0126] like Figure 1 As shown, to launch an Android app on a PC, first locate the emulator software 12 on the PC's desktop 11 and trigger the emulator 12 to start. This will display the emulator's main interface 13 on the PC's desktop 11. Then, locate the Android app's icon (e.g., game app 14) on the emulator's main interface 13 and interact with the Android app's icon to trigger the Android app to start and run.

[0127] See again Figure 1 If the Android app that the user needs is not present in the emulator's main interface 13, the user needs to find the app market 15 in the emulator's main interface 13 and trigger the app market to start. The user can then download and install the Android app through the app market. After installation, the icon of the installed Android app will be displayed in the emulator's main interface 13 for the user to select and use.

[0128] See again Figure 1 If you need to uninstall an Android app on your PC, you still need to start the emulator (12), find the Android app's icon (e.g., game app icon 14) on the emulator's main interface (13), and then uninstall the Android app by clicking its icon (14). For example, you can click the Android app's icon to trigger the uninstall option, and then click the uninstall option to uninstall the app.

[0129] It can be seen that, based on the current technical solutions for using Android apps on a Windows PC via an Android emulator, the operation of using (installing, launching, and uninstalling) Android apps on a Windows PC is limited by the main interface of the Android emulator and the steps are cumbersome and complicated. Furthermore, the operation of using Android apps on a Windows PC is different from the operation of Windows applications, which does not conform to the conventional operating habits of Windows users, thus affecting the user experience.

[0130] Therefore, this application provides a method, apparatus, and terminal device for controlling an Android app on a Windows operating system. This solution allows operating an Android app on a Windows operating system in the same way as operating Windows software, without requiring the user to manually launch an emulator or interact with the Android app through the emulator's main interface. From the user's perspective, since the emulator runs in the background and is not displayed in the foreground (i.e., the Windows desktop), the user is unaware of the emulator and intuitively feels as if they are directly controlling the Android app on the Windows operating system. This aligns with the conventional operating habits of Windows users, thus improving the user experience.

[0131] It should be noted that the terminal device in this application embodiment can be a terminal device with a Windows operating system. In actual implementation, the method provided in this application embodiment can also be applied to terminal devices with other operating systems (such as iOS operating system), and this application embodiment does not make specific limitations. For ease of explanation, the method for controlling Android APP provided in this application will be described below using the Windows operating system as an example.

[0132] In addition, for ease of explanation, the following will refer to terminal devices running the Windows operating system as Windows terminal devices, apps for the Android operating system as Android apps, and apps for the Windows operating system as Windows apps.

[0133] In this embodiment, developers can develop software programs that implement the method for controlling an Android app provided in this embodiment, based on the system architecture of the Windows operating system. This allows the method for controlling the Android app to run on the Windows operating system. That is, a terminal device or processor can implement the method for controlling an Android app provided in this embodiment by running the software program on the Windows operating system.

[0134] It should also be noted that the method for controlling an Android APP on a Windows operating system provided in this application embodiment can be applied to various types of existing Android emulators, and the solution in this application implements the corresponding functions by installing a mobile application engine on a Windows terminal device.

[0135] Optionally, the Windows terminal device in this application embodiment can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can be a tablet computer, a laptop computer, a PDA, an in-vehicle terminal, etc., while a non-mobile terminal can be a personal computer (PC), a television (TV), an ATM, or a self-service machine, etc. This application embodiment does not make specific limitations.

[0136] The execution subject of the method for controlling an Android APP provided in this application embodiment can be the aforementioned Windows terminal device (e.g., PC), or it can be a functional module and / or functional entity in the terminal device capable of implementing the method for controlling the Android APP. The specific implementation can be determined according to actual usage requirements, and this application embodiment does not impose any limitations. The following description uses a Windows terminal device as an example, combined with the accompanying drawings, to executively illustrate the method for controlling an Android APP provided in this application embodiment.

[0137] First, the method for controlling an Android app provided in this application can be applied to Windows terminal devices that have an Android emulator installed. Through the Android emulator, Android apps can be installed, opened, and uninstalled on the Windows terminal device. With this solution, when an Android app is downloaded via an Android emulator, a corresponding app shortcut (i.e., a shortcut entry) can be added and displayed in the common control area of ​​the Windows terminal device. Furthermore, these app shortcuts on the Windows terminal device allow for convenient and quick opening or uninstallation of the Android app. Compared to existing technologies, this solution eliminates the need to display the main interface of the Android emulator on the terminal device during the installation, opening, and / or uninstallation of Android apps on a Windows terminal device, and also eliminates the need for user operation within the Android emulator's main interface. With this solution, users can operate Android apps on a Windows operating system in the same way they operate Windows software on a Windows operating system, conforming to the conventional operating habits of Windows users.

[0138] The following describes in detail, with reference to the accompanying drawings, the specific implementation methods of installing, opening, and uninstalling an Android APP implemented using the embodiments of this application.

[0139] Figure 2 This is a flowchart illustrating a method for controlling an Android app according to an embodiment of this application. This control method is applied to control the installation process of an Android app on a Windows terminal device. (Refer to...) Figure 2 As shown, the method for controlling the Android APP includes the following steps S210-S230.

[0140] S210, the Windows terminal device detected that the user triggered an installation operation on the target Android APP.

[0141] The aforementioned target Android APP is an application that is compatible with the Android operating system, that is, an application that can run under the support of the Android operating system.

[0142] In some embodiments, the Windows terminal device may have Android app stores (or app marketplaces) installed. These app stores provide installation packages for installing target Android apps, and their interfaces may display installation controls for the target Android apps. In this case, when a user triggers installation by clicking the installation control for the target Android app in the Android app store interface, the Windows terminal device can detect the user's installation action.

[0143] In one possible embodiment, the Android app market for Windows terminal devices can be an exe file installed on the Windows terminal device. When the exe file is launched, the Android app market interface can be displayed without launching an emulator application.

[0144] In another possible embodiment, the Android app market on the Windows terminal device can be an EXE file, which is associated with an Android app market APK installed within the emulator application. When the terminal device receives a user's command to run the EXE file, it launches the Android app market APK within the emulator application and displays the Android app market's interface on the Windows terminal device.

[0145] In cases where the installation of a target Android app is triggered through the app store, the Windows terminal device will typically download (i.e. obtain) the installation package of the target Android app from the app store and store the installation package of the target Android app in a shared path on the Windows terminal device.

[0146] In other embodiments, if a user clicks the download control corresponding to the target Android APP on a webpage of a Windows terminal device, the Windows terminal device can respond to the user's operation by downloading (i.e. obtaining) the installation package of the target Android APP and storing it in a shared path on the Windows terminal device; furthermore, if the user clicks the downloaded installation package of the target Android APP to trigger installation, the Windows terminal device can detect the user's trigger installation operation on the target Android APP.

[0147] It is understood that in actual implementation, the methods by which the Windows terminal device obtains the installation package of the target Android APP are not limited to the methods listed above. For example, it can also be a file copy method, a wireless transmission method, or any other possible implementation method. The specific method can be determined according to the actual usage requirements, and this application embodiment does not limit it.

[0148] S220, in response to the triggered installation operation, the Windows terminal device starts an Android emulator in the background and instructs the Android emulator to install the target Android app.

[0149] In response to the triggered installation operation, the Windows terminal device can start and run the Android emulator in the background. In this case, the main interface of the Android emulator is not displayed on the desktop of the Windows terminal device, and the process of the Android emulator installing the target Android APP also runs automatically in the background of the Windows terminal device.

[0150] Thus, from a user experience perspective, installing an Android app on a Windows device is similar to installing a Windows app on a Windows device, making the process of installing an Android app on a Windows device more convenient.

[0151] S230: If the Android emulator reports that the target Android app has been installed, the Windows terminal device will display a shortcut icon for the target Android app.

[0152] In some embodiments, if the target Android app is already installed on the Android emulator, the Android emulator can call the application programming interface (API) in the Windows operating system used to install Android apps to create a shortcut to the target Android app on the Windows terminal device, thereby triggering the Windows terminal device to add and display the shortcut icon of the target Android app on the terminal device.

[0153] Optionally, in this embodiment of the application, the creation of a shortcut for the target Android APP on a Windows terminal device can be implemented in at least one of the following possible methods:

[0154] Method 1: Windows terminal devices can add and display a shortcut icon for the target Android app in the Start menu. This shortcut icon can include the Android app's application icon and application name.

[0155] One feature is the addition of a shortcut icon for Android apps to the Start menu on Windows devices, providing users with a quick access point to Android apps and making it easier for them to find and use them.

[0156] On the one hand, this solution allows users to perform similar operations to those on Windows terminal devices to find Android apps. In actual implementation, such as... Figure 3 As shown, users can open the "Start" control 102 on the Windows terminal device desktop 101 to trigger the display of the Start menu 103 (or Start menu bar), and then directly find the shortcut icon 104 of the installed Android app in the Start menu. This makes finding Android apps on Windows terminal devices consistent with the usual operating habits of Windows users, thereby improving the user experience.

[0157] On the other hand, this solution allows users to operate through the Start Menu, such as clicking the Android app shortcut icon in the Start Menu to trigger the Android app to open and run. This achieves the goal of quickly launching the Android app. Users can also operate through the Start Menu, such as clicking the app uninstall option to trigger a jump to the corresponding uninstallation interface. This achieves the goal of quickly uninstalling the Android app.

[0158] This application embodiment enables the management of Android apps using the Windows Start Menu, solving the complexity of managing Android apps through an Android emulator and simplifying the user's operation of using Android apps on the Windows operating system.

[0159] Method 2, such as Figure 4 As shown, Windows terminal devices can add and display a shortcut icon 105 for the target Android app on the desktop 101. This shortcut icon can include the Android app's application icon and application name.

[0160] Method 3, such as Figure 5 As shown, Windows terminal devices can add and display a shortcut icon 107 for the target Android APP in the Uninstall / Change Programs interface 106 under Control Panel. The shortcut icon can include the application icon and application name of the Android APP.

[0161] If a user clicks and selects the shortcut icon 107, an "Uninstall / Change" control 108 will pop up. The user can operate on the "Uninstall / Change" control 108 to trigger the uninstallation, modification or repair of the selected Android APP.

[0162] Method four, such asFigure 6 As shown, Windows terminal devices can add and display a shortcut icon 110 for the target Android APP in the application function interface 109 under settings. The shortcut icon can include the application icon and application name of the Android APP.

[0163] In actual implementation, if the user clicks and selects the shortcut icon 110, an "Update" control 111 and an "Uninstall" control 112 will pop up. The user can operate on the "Update" control 111 to trigger the function update or modification of the selected Android APP, or the user can operate on the "Uninstall" control 112 to trigger the uninstallation of the selected Android APP.

[0164] This solution allows users to find, open, and uninstall Android apps on Windows devices in the same way they would with Windows apps, conforming to the usual operating habits of Windows users and thus improving the user experience.

[0165] Therefore, according to methods one and two above, after adding shortcuts to the Windows Start Menu or desktop, users can find the Android app shortcut icon in the Start Menu and / or desktop, and can launch the Android app by interacting with these shortcut icons. According to methods three and four above, after adding shortcuts in the Uninstall / Update program interface under the Windows Control Panel or the Applications feature interface under Settings, users can find the Android app shortcut icon in the Control Panel -> Programs -> Uninstall a program interface, and / or the Windows Settings -> Applications feature interface, and can uninstall or update the Android app by interacting with these shortcut icons. Thus, this solution allows users to more conveniently use Android apps on their Windows PCs.

[0166] It should be noted that the specific method for adding shortcuts can be preset by the system or customized by the user. For example, during the shortcut addition process, the user can be prompted to confirm whether to add the shortcut according to the system settings. If the user agrees, the shortcut will be added according to the system settings; if not, the user can change the system's preset shortcut options. The system's preset shortcut options may include at least one of the four methods mentioned above, and may also include any other possible methods, which can be determined according to actual usage needs. This application embodiment does not limit this.

[0167] In this embodiment, the Windows Start Menu, Settings, Control Panel, and Desktop are used as common control areas of the Windows operating system. By adding shortcuts to Android apps in these common control areas, app management is facilitated, and Android apps can be more easily compatible with the Windows operating system.

[0168] The following is combined Figure 7 The method for controlling an Android app provided in this application embodiment will be illustrated by taking the installation of an Android app on a Windows terminal device through an app store as an example.

[0169] like Figure 7 As shown in (a), an Android app icon 113 is displayed on the desktop 101 of the Windows terminal device. Figure 7 As shown in (b), in response to a user's input on the app icon 113 in the app market, the Windows terminal device can display the Android app market interface 114 on the desktop 101 of the Windows terminal device. This interface 114 displays at least one Android app option, and each Android app option corresponds to an installation control. If the user triggers installation by clicking the installation control 115 corresponding to the Android app 1 option (e.g., xx game), the Windows terminal device can detect the user's triggered installation operation on Android app 1. Figure 7 As shown in (c), after Android APP 1 is installed, the application icon 116 of Android APP 1 (xx game) is displayed on the desktop 101 of the Windows terminal device. Of course, as with the other three methods mentioned above, a shortcut icon for Android APP 1 can also be added and displayed in other areas of the Windows terminal device.

[0170] The proposed solution displays the application icon of the downloaded Android app on the Windows desktop. Users can then launch the Android app by clicking the application icon on the Windows desktop, thus solving the problem of poor integration between Android apps and the Windows operating system.

[0171] Optionally, an Android emulator may include two functional modules: an emulator and an Android system. These two modules can interact to implement the functions of the Android emulator. The method for controlling Android APP installation provided in this application embodiment can be implemented through an application market, an emulator, and the Android system. The following describes the method in conjunction with... Figure 8 This example illustrates the interaction process between the app store, emulator, and Android system when installing an Android app on a Windows device. Figure 8As shown, the interaction process includes the following steps S301-S309.

[0172] S301, in response to the user's trigger operation to install the Android APP, downloads the Android APP installation package from the application market and places the installation package in the shared path.

[0173] The installation package for an Android app can have the .apk extension.

[0174] S302, the app market sends the application name information and installation package storage path information (i.e., shared path information) of the Android APP to the emulator through inter-process communication (IPC).

[0175] The application name of this Android app can be referred to as AppName.

[0176] S303, the emulator sends the application name and shared path information of the Android APP to the Android system through inter-system message communication.

[0177] S304, the Android system identifies and obtains the Android APP's installation package based on the application name information of the Android APP, according to the shared path information indicated by the shared path information of the Android APP.

[0178] S305, the Android system loads the installation package of the Android APP to install the Android APP.

[0179] S306: The Android system sends application information of Android apps to the emulator through inter-system message communication.

[0180] Optionally, the application information (denoted as AppInfo) of an Android app may include the package name (denoted as packageName), application icon (denoted as icon), application name (denoted as name), version information (denoted as version), orientation information (denoted as orientation), installation time (denoted as installTime), and name identifier (denoted as exeId) corresponding to the Android app. It should be noted that the information included in the application information of the Android app here is an exemplary example, and the specific information included can be determined according to actual usage needs. This application embodiment does not limit it.

[0181] S307, the emulator generates the corresponding installation package for Android apps.

[0182] The installation package generated by the emulator here is different from the installation package downloaded from the app store mentioned earlier. For easy distinction, the installation package downloaded from the app store will be referred to as the first installation package, and the installation package generated by the emulator will be referred to as the second installation package.

[0183] In this embodiment, when installing an Android app via the Android system, the emulator can obtain the Android app's application information and call the API in the Windows operating system used for installing Android apps. Based on the Android app's application information, a second installation package is generated on the Windows terminal device. This second installation package can be stored in the relevant directory of the Android emulator on the Windows terminal device.

[0184] The second installation package may include the application name corresponding to the Android app, application configuration information (denoted as config.ini), a driver for starting the Android app (denoted as AppName.exe), and a driver for uninstalling the Android app (denoted as uninstall.exe); the application configuration information typically includes the package name of the Android app. It should be noted that the information included in the second installation package is an exemplary list, and the specific information included can be determined according to actual usage requirements; this embodiment does not impose limitations.

[0185] S308, an emulator for creating shortcuts to Android apps on Windows operating systems.

[0186] If the target Android app is already installed on the Android emulator, the emulator can create a shortcut to the target Android app on the Windows terminal device, thereby triggering the Windows terminal device to add and display the shortcut icon of the target Android app. For example, as mentioned above, shortcuts to the Android app can be created in four locations on a Windows PC: ① Windows Start menu, ② Settings -> Apps, ③ Control Panel -> Uninstall a program, and ④ Desktop.

[0187] The shortcut icons for the added Android apps are associated with the second installation package, with the shortcut icons pointing to the second installation package. For example, when a user clicks the Android app's shortcut icon to launch the app, the content within the second installation package (i.e., AppName.exe) pointed to by the shortcut icon executes and passes the launch command, enabling the Android app to launch via an Android emulator. Similarly, when a user clicks the Android app's shortcut icon to uninstall it, the content within the second installation package (i.e., uninstall.exe) pointed to by the shortcut icon executes and passes the uninstall command, enabling the Android app to be uninstalled via an Android emulator.

[0188] In this embodiment of the application, based on the Android emulator scenario, a shortcut is created for the Android APP in the Android emulator on the Windows terminal device, so that users can view, launch, uninstall or modify the Android APP at the corresponding shortcut location on the Windows terminal device.

[0189] S309, the emulator sends the package name of the Android APP and the APP installation result to the application market through inter-process communication.

[0190] In cases where the app installation result indicates that the Android app has been installed, the app store can find the Android app based on its package name and then provide the corresponding installation control (such as...). Figure 7 (b) As shown in 115) The update display is shown as "Open Control" or "Open Control" (e.g.) Figure 9 (As shown in Figure 117).

[0191] It should be noted that the above process of installing Android apps on Windows terminal devices via emulators is all performed in the background, without the need to display the emulator's main interface and perform download and installation operations on the main interface as required by existing technologies. Therefore, the solution proposed in this application can enable users to conveniently and quickly install Android apps on Windows terminal devices.

[0192] It's understandable that users can launch Android apps not only through a shortcut on the Windows operating system, but also through the corresponding launch control in the app store.

[0193] In this embodiment, the Windows terminal device obtains Android APP software information from the Android emulator platform based on the Android emulator, and after the Android APP software is installed, it can create a shortcut for the Android APP in the common control area of ​​the Windows terminal device, so as to enable users to operate the Android APP conveniently and quickly on the Windows PC.

[0194] The previous article introduced how to control the installation of Android apps on Windows terminal devices. The following article, with reference to the accompanying diagrams, describes how to control the opening and running of Android apps on Windows terminal devices.

[0195] Figure 10 This is a flowchart illustrating a method for controlling an Android app according to an embodiment of this application. This control method is applied to the process of controlling the opening of an Android app on a Windows terminal device. (Refer to...) Figure 10 As shown, the method includes the following steps S410-S430.

[0196] S410, the Windows terminal device detected that the user triggered the opening operation of the target Android APP.

[0197] For example, as described above, users can operate on the shortcut icon of an Android app to trigger the app to open, or they can operate on the corresponding app launch control in the app store to trigger the app to open.

[0198] S420, in response to the triggered start operation, the Windows terminal device instructs the Android emulator to start and run the target Android APP.

[0199] In this embodiment of the application, when the target Android APP has been installed on the Windows terminal device through the Android emulator, the Windows terminal device responds to the user's triggering operation on the shortcut icon of the target Android APP in the Windows terminal device, calls the driver (i.e. AppName.exe) in the second installation package associated with the shortcut icon of the target Android APP to open the target Android APP, and instructs the Android emulator to open and run the target Android APP.

[0200] In some embodiments, when the Android emulator is not running, the Windows terminal device responds to the user's trigger to start the Android emulator in the background and instructs the Android emulator to start and run the target Android APP.

[0201] S430: If the Android emulator reports that the target Android app is already open, the Windows terminal device will display a first window on the desktop of the Windows terminal device, and the running interface of the target Android app will be displayed in the first window.

[0202] The Android emulator can launch the target Android app through the Android system, draw a window, and then place the running interface of the target Android app into that window. This allows the Windows terminal device to display the window on the desktop, where the running interface of the target Android app is displayed.

[0203] The method for controlling the opening of an Android APP provided in this application embodiment can be implemented through an application market, an emulator, and the Android system. The following describes the method in conjunction with... Figure 11 This example illustrates the interaction flow between the Windows terminal device (processor), the emulator, and the Android system when controlling the launch of an Android app on a Windows terminal device. For example... Figure 11 As shown, the interaction process includes the following steps S501-S507, where S501 is either S501A or S501B as described below.

[0204] S501A responds to the user's activation trigger operation on the shortcut icon of the Android APP, calls the driver (i.e. AppName.exe) in the second installation package associated with the shortcut icon of the Android APP to open the target Android APP, and obtains the package name of the Android APP from the second installation package.

[0205] In response to the activation trigger operation, the Windows terminal device calls the driver (i.e., AppName.exe) in the second installation package corresponding to the target Android APP to activate the application running function of the emulator; and reads the package name of the Android APP from the application configuration information of the second installation package.

[0206] S501B responds to the user's operation on the corresponding launch control of the Android APP in the app store, calls the driver (i.e. AppName.exe) in the second installation package associated with the shortcut icon of the Android APP to launch the target Android APP, and directly obtains the package name of the Android APP from the app store.

[0207] As can be seen from S501A and S501B above, when the Android APP is launched via a shortcut, the Windows terminal device needs to read the Android APP's package name from the application configuration information (i.e., config.ini) in the second installation package. In contrast, when the Android APP is launched via the app store, the Windows terminal device can directly obtain the Android APP's package name from the app store without having to read the package name from the application configuration information (i.e., config.ini) in the second installation package.

[0208] It should be noted that either S501A or S501B can be implemented.

[0209] In S502, Windows terminal devices send the package name of an Android app to the emulator via inter-process communication and instruct the emulator to launch the Android app.

[0210] S503, the emulator draws a window for the Android app, and this window has a window identifier (ID).

[0211] The emulator can find the Android app in the emulator based on the app's package name and create the corresponding window for the Android app on the Windows terminal device.

[0212] S504, the emulator sends the package name and window ID of the Android APP to the Android system through inter-system message communication.

[0213] S505: The Android system launches an Android app and displays the target Android app's running interface in this window.

[0214] S506: The Android system communicates with the emulator via inter-system messaging to return the package name of the Android app and the app launch result.

[0215] The S507 emulator uses inter-process communication to send feedback to the app store regarding the package name of the Android app and the app launch result.

[0216] In cases where the app launch result indicates that the Android app is open, Windows devices can display the running interface of the Android app on the desktop.

[0217] Optionally, the Android emulator can draw a first window on a Windows terminal device (e.g., the desktop) based on the screen orientation information corresponding to the Android app, to host the Android app's interface. The display format (landscape or portrait) of the first window can be determined based on the screen orientation information, thus determining whether the Android app's interface is displayed in landscape or portrait mode. Here, portrait mode refers to the first window's vertical dimension being larger than its horizontal dimension, and landscape mode refers to the first window's horizontal dimension being larger than its vertical dimension.

[0218] Specifically, if the screen orientation information indicates landscape mode, the Android app's interface will be displayed in landscape mode on the Windows desktop; if the screen orientation information indicates portrait mode, the Android app's interface will be displayed in portrait mode on the Windows desktop.

[0219] For example, such as Figure 12 As shown in (a), the landscape / portrait information corresponding to Android APP 118 (such as the xx game in the figure) indicates that the running interface of the xx game APP is displayed in landscape mode, and the running interface 119 of the xx game APP after it is opened is displayed in landscape mode.

[0220] For example, such as Figure 12 As shown in (b), the landscape / portrait information of Android APP 120 (such as Smart Life in the figure) indicates that the running interface of the Smart Life APP is displayed in portrait mode, and the running interface 121 of the Smart Life APP after it is opened is displayed in portrait mode.

[0221] It should be noted that the process of launching an Android app on a Windows terminal device via an emulator is all performed in the background, without the need to display the emulator's main interface and perform the launching operation on the main interface as required by existing technologies. Therefore, the solution proposed in this application can enable users to conveniently and quickly launch Android apps on Windows terminal devices.

[0222] The previous article introduced how to control the installation and opening of Android apps on Windows terminal devices. The following article, with accompanying illustrations, introduces how to control the uninstallation of Android apps on Windows terminal devices.

[0223] Figure 13 This is a flowchart illustrating a method for controlling an Android app according to an embodiment of this application. This control method is applied to control the uninstallation process of an Android app on a Windows terminal device. (Refer to...) Figure 13 As shown, the method includes the following steps S610-S630.

[0224] S610, the Windows terminal device detected that the user triggered an uninstallation operation on the target Android APP.

[0225] For example, as described above, users can uninstall the Android app by clicking on its shortcut icon. Alternatively, this can be done through Settings -> Apps on a Windows device; or through Control Panel -> Uninstall a program on a Windows device.

[0226] S620, in response to the triggered uninstall operation, the Windows terminal device instructs the Android emulator to uninstall the target Android app.

[0227] In this embodiment of the application, when the target Android APP has been installed on the Windows terminal device through the Android emulator, the Windows terminal device responds to the user's trigger uninstallation operation on the shortcut icon of the target Android APP in the Windows terminal device, calls the driver (i.e. uninstall.exe) in the second installation package associated with the shortcut icon of the target Android APP to uninstall the target Android APP, and instructs the Android emulator to uninstall the target Android APP.

[0228] In some embodiments, when the Android emulator is not running, the Windows terminal device responds to the user's uninstallation request by launching the Android emulator in the background and instructing the Android emulator to uninstall the target Android app.

[0229] S630: If the Android emulator reports that the target Android app has been uninstalled, the Windows terminal device will delete the shortcut icon and second installation package of the target Android app from the terminal device.

[0230] The method for controlling the uninstallation of Android apps provided in this application can be implemented through application markets, emulators, and the Android system. The following describes the method in conjunction with...Figure 14 This example illustrates the interaction flow between the Windows terminal device (processor), the emulator, and the Android system when controlling the uninstallation of an Android app on a Windows terminal device. For example... Figure 14 As shown, the interaction process includes the following steps S701-S706, where S701 is either S701A or S701B as described below.

[0231] S701A, in response to the user's uninstallation trigger operation on the shortcut icon of the Android APP, calls the driver (i.e. uninstall.exe) in the second installation package associated with the shortcut icon of the Android APP for uninstalling the target Android APP, and obtains the package name of the Android APP.

[0232] In response to the uninstallation trigger operation, the Windows terminal device calls the driver (i.e. uninstall.exe) in the second installation package corresponding to the target Android APP to uninstall the target Android APP, triggering the emulator to start the application uninstallation function; and reads the package name of the Android APP from the application configuration information of the second installation package.

[0233] S701B responds to the user's operation on the uninstall control corresponding to the Android APP in the app store, calls the driver (i.e. uninstall.exe) in the second installation package associated with the shortcut icon of the Android APP for uninstalling the target Android APP, and the Windows terminal device directly obtains the package name of the Android APP from the app store.

[0234] As can be seen from S701A and S701B above, when the Android APP is uninstalled via a shortcut, the Windows terminal device needs to read the Android APP's package name from the application configuration information (i.e., config.ini) in the second installation package. In contrast, when the Android APP is uninstalled via the app store, the Windows terminal device can directly obtain the Android APP's package name from the app store without having to read the package name from the application configuration information (i.e., config.ini) in the second installation package.

[0235] It should be noted that either S701A or S701B can be implemented.

[0236] In S702, Windows terminal devices send the package name of an Android app to the emulator via inter-process communication and instruct the emulator to uninstall the Android app.

[0237] In S703, the emulator forwards the package name of the Android app to the Android system through inter-system message communication.

[0238] S704, uninstalling Android apps on Android systems.

[0239] In other words, the emulator finds the Android app in the emulator based on the app's package name and then uninstalls the Android app through the Android system.

[0240] In S705, the Android system communicates with the emulator via inter-system messaging to report the package name of the Android app and the app uninstallation result.

[0241] The S706 emulator uses inter-process communication to send the package name of the Android app and the app uninstallation result to the Windows terminal device.

[0242] On the one hand, when the APP uninstallation result indicates that the Android APP has been uninstalled, the emulator can call the API in the Windows operating system used to uninstall APPs, delete the shortcut icon of the Android APP on the Windows terminal device, and delete the second installation package of the Android APP.

[0243] On the other hand, if the app uninstallation result indicates that the Android app has been uninstalled, the app store on the Windows terminal device can find the Android app based on its package name and then open the corresponding launch control or open control (such as...) for the Android app. Figure 9 As shown in Figure 117, the update is displayed as the installation control (e.g., ...). Figure 7 (as shown in (b) of 115).

[0244] It should be noted that the above process of uninstalling Android apps on Windows terminal devices via an emulator is all implemented in the background, without the need to display the emulator's main interface and perform the uninstallation operation on the main interface as required by existing technologies. Therefore, the solution of this application can enable users to conveniently and quickly uninstall Android apps on Windows terminal devices.

[0245] It should be noted that the above embodiments are executor-based using a terminal device as the execution subject. In actual implementation, the execution subject may specifically be the central processing unit (CPU) in the terminal device.

[0246] Optionally, in this embodiment, the shortcut icons for the Android app and the Windows app can have the same display style, eliminating the need for user differentiation. This ensures a seamless user experience for both the Windows and Android apps on Windows devices. Alternatively, the shortcut icons can have different display styles for easier user identification, allowing for targeted operations on the Windows and Android apps respectively. Specifically, whether the shortcut icons have the same display style can be determined based on actual usage needs, and this embodiment does not impose such a limitation.

[0247] Optionally, in this embodiment, the filename corresponding to the shortcut icon includes preset characters and the application name of the target Android app. The preset characters can be whitespace (Unicode) characters or invisible characters.

[0248] Optionally, the number of preset characters can be one or more, which can be determined according to actual usage requirements. This application embodiment does not limit this.

[0249] Optionally, the embodiments of this application do not limit the position of the preset character. For example, the preset character can be placed before the application name of the target Android APP, after the application name of the target Android APP, or in the application name of the target Android APP. The specific position can be determined according to the actual usage requirements, and the embodiments of this application do not limit it.

[0250] It's important to note that the difference between whitespace characters and invisible characters is that whitespace characters are displayed, while invisible characters are not. For example, adding a space in the middle of "App Market" will display "App Market"; however, adding an invisible character in the middle of "App Market" will still display "App Market". In some embodiments, an invisible character can be added before the application name. To the user, the application name appears unchanged, thus avoiding name duplication and preventing user confusion.

[0251] For example, such as Figure 15 As shown in (a), the desktop shortcut name 122 for the Windows App Store includes the application name "App Store" but does not contain any other characters; the desktop shortcut name 123 for the Android App Store includes both the application name "App Store" and the invisible character 124. That is, Android apps and Windows apps differ in their desktop shortcut naming. Furthermore, regarding the display effect, as shown... Figure 15As shown in (b), the desktop shortcut name 125 in the Android app market and the desktop shortcut name 126 in the Windows app market have the same display effect. Thus, by using invisible characters as placeholders before the Android app's name, special processing is ensured for shortcuts belonging to the emulator, allowing Android apps installed via the emulator to have the same name as Windows apps on the Windows desktop.

[0252] Thus, compared with the existing technology of solving the name duplication problem by adding the emulator name suffix to the application name, the embodiments of this application add preset characters to the file name corresponding to the shortcut icon, which can avoid the problem of Android APP and Windows APP having the same name on the Windows desktop.

[0253] Optionally, in this embodiment of the application, the number of whitespace characters in the filenames corresponding to each shortcut icon can be recorded in the database of the Windows terminal device. This can be represented by exe_id, and apps with the same filename can be distinguished based on the number of whitespace characters. For example, this can be used to assist in app uninstallation.

[0254] Next, let's combine... Figure 16 The method for controlling an Android app provided in this application embodiment will be described exemplarily. It is assumed that two software programs, an app store and an emulator, are installed on a Windows PC. Figure 16 This illustration shows a schematic diagram of the interaction process between the application market and the emulator in an embodiment of this application, as well as the process of ultimately generating or deleting shortcuts on a Windows terminal device. Figure 16 As shown, the app market acts as the app market client (AppMarketClient), which functions as an app launcher (AppLauncher) client. It can launch installed apps (InstallApp), launched apps (LauncherApp), and uninstalled apps (UninstallApp). Correspondingly, the emulator acts as the app market server (AppMarketServer), which also functions as an app launcher (AppLauncher) server. It can launch installed apps, launched apps (LauncherApp), and uninstalled apps. The app market and the emulator interact via IPC communication.

[0255] Specifically, after installing an Android app through the app store on a Windows terminal device, the Windows operating system's AppLauncher sends the Android app's app information (i.e., AppMessage, such as the app name and installation package storage path) to the emulator's AppLauncher via IPC communication. Then, it sends the Android app's app information to the emulator's AppService module via a message queue. This AppService module then calls the Windows API interface to generate a shortcut for the Android app in the Windows operating system. In other words, this embodiment uses the AppLauncher to transmit app information, and the emulator uses this information to create a shortcut for the installed Android app in the Windows operating system, making it more convenient and faster for users to use Android apps on their Windows PCs. As mentioned above, the shortcut location can include at least one of the following: ① Windows Start menu bar, ② Settings -> Apps, ③ Control Panel -> Programs -> Uninstall a program, ④ Desktop shortcut. Similar to the above method, the Android app shortcut can be deleted when uninstalling the Android app. The emulator's AppLauncher can generate a second installation package in the Windows operating system, writing the app information into the Windows operating system, and then calling the app information through the Windows operating system's API.

[0256] The embodiments of this application enable convenient and quick management of Android apps on Windows PCs. The process of managing Android apps on Windows PCs is no different from managing Windows apps.

[0257] Since the proposed solution manages Android apps through the Start Menu in the Windows operating system, and the process of uninstalling Android apps through the Start Menu, Settings, and Control Panel all conform to the common operating habits of Windows users, it helps to broaden the product's user base.

[0258] It should also be noted that in the embodiments of this application, "greater than" can be replaced with "greater than or equal to", "less than or equal to" can be replaced with "less than", or "greater than or equal to" can be replaced with "greater than", and "less than" can be replaced with "less than or equal to".

[0259] The various embodiments described herein can be independent solutions or combinations thereof based on their inherent logic, and all such solutions fall within the protection scope of this application.

[0260] It is understood that the methods and operations implemented by the terminal device in the above-described method embodiments can also be implemented by components (such as chips or circuits) that can be used in the terminal device.

[0261] The method embodiments provided in this application have been described above. The apparatus embodiments provided in this application will be described below. It should be understood that the description of the apparatus embodiments corresponds to the description of the method embodiments. Therefore, any content not described in detail can be referred to the method embodiments above. For the sake of brevity, it will not be repeated here.

[0262] The foregoing mainly describes the solutions provided by the embodiments of this application from the perspective of method steps. It is understood that, in order to achieve the above functions, the terminal device implementing this method includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of protection of this application.

[0263] This application embodiment can divide the terminal device into functional modules based on the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, other feasible division methods may exist. The following description uses the division of functional modules according to each function as an example.

[0264] Figure 17 This is a schematic block diagram of a device 810 for controlling an Android app on a Windows operating system, provided in an embodiment of this application. The device 810 can be used to perform the actions performed by the Windows terminal device in the method embodiments described above. The device 810 includes a detection unit 811, a processing unit 818, and a display unit 813.

[0265] The detection unit 811 is used to detect the user's installation, opening, or uninstallation operations on the target Android APP on the terminal device;

[0266] The processing unit 812 is configured to respond to the user's installation, opening, or uninstallation operation of the target Android APP on the terminal device, and to install, open, or uninstall the target Android APP through an Android emulator. The target Android APP is an application applicable to the Android operating system.

[0267] Display unit 813, used for:

[0268] When the target Android APP is installed on the Android emulator, a shortcut icon of the target Android APP is displayed on the terminal device;

[0269] Alternatively, when the target Android APP is launched on the Android emulator, the running interface of the target Android APP is displayed on the desktop of the terminal device;

[0270] Alternatively, if the target Android app is uninstalled on the Android emulator, the shortcut icon of the target Android app can be deleted from the terminal device.

[0271] The proposed solution allows Windows terminal devices to create shortcuts for Android apps in frequently used control areas based on an Android emulator platform. This enables convenient control of Android apps on the Windows operating system (e.g., downloading, launching, uninstalling, or modifying them), just like operating Windows software on a Windows operating system. This aligns with the conventional operating habits of Windows users, eliminating the need for users to manually launch the emulator or operate the Android app through the emulator's main interface. Therefore, this solution enhances the user experience.

[0272] In some embodiments, the processing unit 812 is specifically used to: in response to a user's installation, opening, or uninstallation operation of a target Android APP on the terminal device, launch the Android emulator in the background of the terminal device, and install, open, or uninstall the target Android APP through the Android emulator.

[0273] From the user's perspective, the proposed solution works because the emulator runs in the background and is not displayed in the foreground (i.e., the Windows operating system desktop). Therefore, the user is unaware of the emulator and intuitively feels as if they are directly controlling an Android app on the Windows operating system. This aligns with the conventional operating habits of Windows users and thus improves the user experience.

[0274] In some embodiments, the display unit 813 is specifically used to: call the first application programming interface (API) of the Windows operating system to create a shortcut of the target Android APP on the terminal device, and trigger the display unit 813 to display the shortcut icon of the target Android APP on the terminal device.

[0275] In some embodiments, the display unit 813 is specifically used for:

[0276] A shortcut icon for the target Android app is displayed in the start menu of the terminal device;

[0277] And / or, display a shortcut icon for the target Android app in the uninstall or change program interface under the control panel of the terminal device;

[0278] And / or, display a shortcut icon for the target Android app on the desktop of the terminal device;

[0279] And / or, display a shortcut icon for the target Android app in the application function interface under the settings of the terminal device.

[0280] This solution allows Windows terminal devices to create shortcuts for Android apps in commonly used control areas such as the Start Menu, Settings, Control Panel, and Desktop, based on an Android emulator platform. This makes it convenient for users to view, launch, uninstall, or modify Android apps from the corresponding shortcut locations on the Windows terminal device.

[0281] In some embodiments, the filename corresponding to the shortcut icon includes preset characters and the application name of the target Android APP; wherein, the preset characters can be blank characters or invisible characters.

[0282] Optionally, in some embodiments, the above-described device 810 further includes a download unit and a storage unit;

[0283] The download unit is used to download the first installation package of the target Android APP in response to the user's triggered installation operation on the terminal device.

[0284] A storage unit is used to store the first installation package of the target Android APP in a shared path in the terminal device.

[0285] In some embodiments, the download unit is specifically used to: download the first installation package of the target Android APP from the application market;

[0286] The processing unit 812 responds to the user's triggered installation operation on the target Android APP on the terminal device, including: the processing unit 812 responds to the user's triggered installation operation on the installation control corresponding to the target Android APP in the application market.

[0287] In some embodiments, the display unit 813 is further configured to:

[0288] If the application market is an exe file and is installed on the terminal device, then when the exe file is launched, the running interface of the application market will be displayed on the terminal device.

[0289] Alternatively, if the application market is an exe file and is associated with an application market apk installed in the Android emulator, then when a user's command to run the exe file is received, the application market apk in the Android emulator is launched, and the application market's running interface is displayed on the terminal device.

[0290] Optionally, in some embodiments, the above-mentioned device 810 further includes a transceiver unit, which is used to send the application name information and installation package storage path information of the target Android APP to the Android emulator through inter-process communication;

[0291] Furthermore, the Android emulator obtains the first installation package of the target Android APP according to the shared path indicated by the installation package storage path information of the target Android APP and the application name information of the target Android APP.

[0292] Furthermore, the Android emulator loads the first installation package of the target Android APP through the Android system to install the target Android APP.

[0293] In some embodiments, when the target Android APP is installed on the Android emulator, the Android emulator obtains the application information of the target Android APP. The application information of the target Android APP includes the package name, application icon, application name, version information, screen orientation information, installation time and / or name identifier corresponding to the target Android APP.

[0294] Furthermore, the Android emulator generates a second installation package associated with the shortcut icon of the target Android APP in the terminal device based on the application information of the target Android APP. The second installation package includes the application name corresponding to the target Android APP, application configuration information, a driver for starting the target Android APP, and a driver for uninstalling / updating the target Android APP.

[0295] In some embodiments, the transceiver unit is further configured to: after the Android emulator installs the target Android APP, send a first response message to the application market via inter-process communication, the first response message including the package name of the target Android APP and the result that the target Android APP has been installed;

[0296] Furthermore, based on the first response message, the app store updates the installation control corresponding to the target Android app in the app store to an activation control.

[0297] In some embodiments, the processing unit 812 is specifically used to: respond to the user's opening operation on the shortcut icon of the target Android APP, call the driver for opening the target Android APP in the second installation package associated with the shortcut icon of the target Android APP, and trigger the Android emulator to enable the APP opening function.

[0298] The transceiver unit is also configured to: read the package name of the target Android APP from the application configuration information of the second installation package, and send the package name of the target Android APP to the Android emulator;

[0299] Furthermore, the Android emulator locates the target Android APP in the Android emulator based on the package name of the target Android APP, draws the first window corresponding to the target Android APP on the terminal device, and opens the target Android APP through the Android system, placing the running interface of the target Android APP into the first window.

[0300] In some embodiments, the processing unit 812 is specifically configured to: respond to the user's uninstallation operation on the shortcut icon of the target Android APP in the terminal device, call the driver for uninstalling the target Android APP in the second installation package corresponding to the target Android APP, trigger the Android emulator to enable the APP uninstallation function; and read the package name of the target Android APP from the application configuration information of the second installation package, and send the package name of the target Android APP to the Android emulator.

[0301] Furthermore, the Android emulator locates the target Android app within itself based on the app's package name and uninstalls the target Android app through the Android system.

[0302] In some embodiments, the above-mentioned deletion of the shortcut icon of the target Android APP in the terminal device includes: the Android emulator calling the second API of the Windows operating system to delete the shortcut icon of the target Android APP and the second installation package in the terminal device.

[0303] In some embodiments, the transceiver unit is further configured to: after the target Android APP is uninstalled by the Android emulator, the Android emulator sends a second response message to the application market in the terminal device through inter-process communication, the second response message including the package name of the target Android APP and the result that the target Android APP has been uninstalled;

[0304] Furthermore, based on the second response message, the app store updates the display of the launch control corresponding to the target Android app as an installation control.

[0305] The apparatus 810 according to the embodiments of this application can correspond to the execution of the method described in the embodiments of this application, and the above and other operations and / or functions of the units in the apparatus 810 are respectively for implementing the corresponding process of the method, which will not be repeated here for the sake of brevity.

[0306] Figure 18 This is a schematic block diagram of a device 820 for controlling an Android app, provided in an embodiment of this application. The device 820 can be used to perform the actions executed by the Android emulator in the method embodiments described above. The device 820 includes a processing unit 821.

[0307] Processing unit 821 is configured to: install, open, or uninstall a target Android APP according to a first instruction; the first instruction is triggered by a user performing an installation, opening, or uninstallation operation on the target Android APP on a terminal device running a Windows operating system, and the target Android APP is an application applicable to the Android operating system;

[0308] When the target Android APP is installed on the Android emulator, the Android emulator creates a shortcut to the target Android APP on the terminal device;

[0309] Alternatively, when the target Android APP is launched on the Android emulator, the Android emulator displays the running interface of the target Android APP on the desktop of the terminal device;

[0310] Alternatively, if the target Android app is uninstalled by the Android emulator, the Android emulator may delete the shortcut of the target Android app from the terminal device.

[0311] This solution allows Android emulators to create shortcuts for Android apps in the common control areas of Windows terminal devices, enabling convenient control of Android apps on the Windows operating system (e.g., downloading, launching, uninstalling, or modifying them). This is similar to operating Windows software on a Windows operating system, conforming to the conventional operating habits of Windows users, without requiring users to manually trigger the emulator to start or to operate the Android app through the emulator's main interface. Therefore, this solution can improve the user experience.

[0312] In some embodiments, the processing unit 821 is specifically used for:

[0313] In response to the first instruction, start the Android emulator in the background;

[0314] According to the first instruction, install, open, or uninstall the target Android APP.

[0315] In some embodiments, the processing unit 821 is specifically used for:

[0316] The system calls the Windows operating system's first application programming interface (API) to create a shortcut to the target Android app on the terminal device, triggering the display of the shortcut icon of the target Android app on the terminal device.

[0317] In some embodiments, the processing unit 821 is specifically used for:

[0318] Create a shortcut to the target Android app in the Start menu of the terminal device;

[0319] And / or, create a shortcut to the target Android APP in the uninstall or change program interface under the control panel of the terminal device;

[0320] And / or, create a shortcut to the target Android APP on the desktop of the terminal device;

[0321] And / or, create a shortcut to the target Android APP in the application function interface under the settings of the terminal device.

[0322] In some embodiments, the filename corresponding to the shortcut icon includes preset characters and the application name of the target Android APP; wherein, the preset characters can be blank characters or invisible characters.

[0323] In some embodiments, the first instruction may be triggered by a user installing the target Android APP through an application market installed on the terminal device.

[0324] In this case, the processing unit 821 is specifically used for:

[0325] The system receives the first instruction sent by the application market through inter-process communication. The first instruction includes the application name information and installation package storage path information of the target Android APP.

[0326] According to the shared path indicated by the installation package storage path information of the target Android APP, the first installation package of the target Android APP is obtained according to the application name information of the target Android APP;

[0327] The target Android APP is installed by loading the first installation package of the target Android APP through the Android system.

[0328] In some embodiments, the above-described apparatus 820 further includes a transceiver unit 822;

[0329] The transceiver unit 822 is used to: when the processing unit 821 installs the target Android APP, obtain the application information of the target Android APP, the application information of the target Android APP including the package name, application icon, application name, version information, screen orientation information, installation time and / or name identifier corresponding to the target Android APP;

[0330] The processing unit 821 is further configured to: generate a second installation package associated with a shortcut icon of the target Android APP in the terminal device according to the application information of the target Android APP, wherein the second installation package includes an application name corresponding to the target Android APP, application configuration information, a driver for starting the target Android APP, and a driver for uninstalling / updating the target Android APP.

[0331] In some embodiments, the transceiver unit 822 is further configured to: after the processing unit 821 installs the target Android APP according to the first instruction, send a first response message to the application market in the terminal device through inter-process communication, the first response message including the package name of the target Android APP and the result that the target Android APP has been installed.

[0332] In some embodiments, the first instruction may be triggered by the user opening the shortcut icon of the target Android APP on the terminal device, or by the user opening the corresponding control of the target Android APP in the application market on the terminal device.

[0333] Specifically, the processing unit 821 is used to: when the processing unit 821 has installed the target Android APP, in response to the first instruction, call the driver program in the second installation package associated with the shortcut icon of the target Android APP for opening the target Android APP, and trigger the Android system to open the target Android APP.

[0334] Specifically, the processing unit 821 is further configured to: draw a first window for the target Android APP on the desktop of the terminal device, and add the running interface of the target Android APP to the first window through the Android system.

[0335] In some embodiments, drawing a first window for the target Android APP on the desktop of the terminal device includes:

[0336] Based on the landscape and portrait screen information corresponding to the target Android APP, the first window is drawn on the desktop of the terminal device.

[0337] In some embodiments, when the landscape / portrait information indicates landscape mode, the horizontal dimension of the drawn first window is greater than its vertical dimension. When the landscape / portrait information indicates portrait mode, the vertical dimension of the drawn first window is greater than its horizontal dimension.

[0338] In some embodiments, the first instruction may be triggered by a user performing an uninstallation operation on the shortcut icon of the target Android APP on the terminal device.

[0339] Accordingly, the processing unit 821 is further configured to: according to the first instruction, call the driver program for uninstalling the target Android APP in the second installation package corresponding to the target Android APP, read the package name of the target Android APP from the application configuration information of the second installation package, find the target Android APP according to the package name of the target Android APP, and uninstall the target Android APP through the Android system.

[0340] In some embodiments, the transceiver unit 822 is further configured to: after the target Android APP is uninstalled, the Android emulator sends a second response message to the application market in the terminal device via inter-process communication, the second response message including the package name of the target Android APP and the result that the target Android APP has been uninstalled.

[0341] The apparatus 820 according to the embodiments of this application can correspond to the execution of the method described in the embodiments of this application, and the above and other operations and / or functions of the units in the apparatus 820 are respectively for implementing the corresponding process of the method, which will not be described again here for the sake of brevity.

[0342] Figure 19This is a schematic structural diagram of a terminal device 900 provided in an embodiment of this application. The terminal device 900 includes: a processor 910, a memory 920, a communication interface 930, and a bus 940.

[0343] The processor 910 can be connected to the memory 920. The memory 920 can be used to store program code and data. Therefore, the memory 920 can be an internal storage unit of the processor 910, an external storage unit independent of the processor 910, or a component that includes both internal and external storage units. It should be noted that... Figure 19 The processor 910 in the terminal device 900 shown can correspond to Figure 17 The processing unit 812 in the device 810 or corresponding to Figure 18 The processing unit 821 in the device 820.

[0344] Optionally, the terminal device 900 may also include a bus 940. The memory 920 and communication interface 930 can be connected to the processor 910 via the bus 940. The bus 940 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. This bus 940 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 19 The symbol is represented by only one line, but this does not mean that there is only one bus or one type of bus.

[0345] It should be understood that in the embodiments of this application, the processor 910 may be a CPU. The processor may also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor. Alternatively, the processor 910 may employ one or more integrated circuits to execute related programs to implement the technical solutions provided in the embodiments of this application.

[0346] The memory 920 may include read-only memory and random access memory, and provides instructions and data to the processor 910. A portion of the processor 910 may also include non-volatile random access memory. For example, the processor 910 may also store device type information.

[0347] When the terminal device 900 is running, the processor 910 executes computer execution instructions in the memory 920 to perform the operation steps of the above method.

[0348] It should be understood that the terminal device 900 according to the embodiments of this application may correspond to the device 810 or device 820 in the embodiments of this application, and the above and other operations and / or functions of each unit in device 810 or device 820 are respectively for implementing the corresponding process of the above method. For the sake of brevity, they will not be described in detail here.

[0349] Optionally, in some embodiments, this application also provides a computer-readable medium storing program code that, when run on a computer, causes the computer to perform the methods described in the above aspects.

[0350] Optionally, in some embodiments, this application also provides a computer program product comprising: computer program code, which, when run on a computer, causes the computer to perform the methods described above.

[0351] In this embodiment, the terminal device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer may include hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system layer can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer may include applications such as browsers, address books, word processing software, and instant messaging software.

[0352] This application does not impose any particular limitation on the specific structure of the execution subject of the method provided in this application embodiment. As long as it is possible to communicate according to the method provided in this application embodiment by running a program that records the code of the method provided in this application embodiment. For example, the execution subject of the method provided in this application embodiment can be a terminal device or a network device, or a functional module in a terminal device or network device that can call and execute a program.

[0353] Various aspects or features of this application can be implemented as methods, apparatus, or articles of manufacture using standard programming and / or engineering techniques. As used herein, the term "article of manufacture" can encompass a computer program accessible from any computer-readable device, carrier, or medium. For example, computer-readable media can include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact discs (CDs), digital versatile discs (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.).

[0354] The various storage media described herein may represent one or more devices and / or other machine-readable media used for storing information. The term "machine-readable media" may include, but is not limited to, wireless channels and various other media capable of storing, containing and / or carrying instructions and / or data.

[0355] It should be understood that the processor mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0356] It should also be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM can include a variety of forms, such as: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0357] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0358] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0359] Those skilled in the art will recognize that the units and steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of protection of this application.

[0360] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0361] In the embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection of apparatuses or units may be electrical, mechanical, or other forms.

[0362] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0363] In addition, the functional units in the various embodiments of this application can be integrated into one unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0364] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium and includes several instructions that cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0365] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.

[0366] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for controlling an Android application (APP), applied to a terminal device running a Windows operating system, wherein the terminal device has Android emulator software installed, and the Android emulator runs in the background, characterized in that, The method includes: In response to a user's installation, opening, or uninstallation of a target Android APP on the terminal device, the target Android APP is installed, opened, or uninstalled using a second installation package generated by the Android emulator. The target Android APP is an application applicable to the Android operating system. The second installation package is associated with a shortcut icon of the target Android APP and includes a driver for opening the target Android APP and a driver for uninstalling / updating the target Android APP. When the target Android app is installed on the Android emulator, a shortcut icon for the target Android app is displayed on the terminal device; or, When the target Android app is launched on the Android emulator, the running interface of the target Android app is displayed on the desktop of the terminal device; or, If the target Android app is uninstalled on the Android emulator, delete the shortcut icon of the target Android app on the terminal device.

2. The method according to claim 1, characterized in that, In response to a user's installation, opening, or uninstallation of a target Android app on the terminal device, the installation, opening, or uninstallation of the target Android app via the Android emulator includes: In response to a user's installation, opening, or uninstallation of a target Android app on the terminal device, the Android emulator is launched in the background of the terminal device to install, open, or uninstall the target Android app.

3. The method according to claim 1, characterized in that, Displaying the shortcut icon of the target Android app on the terminal device includes: The Android emulator calls the Windows operating system's first application programming interface (API) to create a shortcut to the target Android app on the terminal device, triggering the display of the shortcut icon of the target Android app on the terminal device.

4. The method according to claim 1, characterized in that, Displaying the shortcut icon of the target Android app on the terminal device includes: Display a shortcut icon for the target Android app in the start menu of the terminal device; and / or, A shortcut icon for the target Android app is displayed in the uninstall or change program interface under the control panel of the terminal device; and / or, Display a shortcut icon for the target Android app on the desktop of the terminal device; and / or, A shortcut icon for the target Android app is displayed in the application function interface under the settings of the terminal device.

5. The method according to claim 3 or 4, characterized in that, The filename corresponding to the shortcut icon includes preset characters and the application name of the target Android APP; wherein, the preset characters are blank characters or invisible characters.

6. The method according to any one of claims 1 to 4, characterized in that, The method further includes: In response to a user's triggered installation operation on the target Android APP on the terminal device, the first installation package of the target Android APP is downloaded; The first installation package of the target Android APP is stored in a shared path on the terminal device.

7. The method according to claim 6, characterized in that, The step of downloading the first installation package of the target Android APP includes: downloading the first installation package of the target Android APP from an app store; The step of responding to the user's triggered installation operation on the target Android APP on the terminal device includes: responding to the user's triggered installation operation on the installation control corresponding to the target Android APP in the application market.

8. The method according to claim 7, characterized in that, Displaying the running interface of the target Android APP on the desktop of the terminal device includes: If the application market is an EXE file and installed on the terminal device, then when the EXE file is launched, the application market's interface will be displayed on the terminal device; or, If the application market is an exe file and is associated with an application market apk installed in the Android emulator, then when a user's command to run the exe file is received, the application market apk in the Android emulator is launched, and the running interface of the application market is displayed on the terminal device.

9. The method according to claim 7 or 8, characterized in that, The process of installing the target Android app through the Android emulator includes: The application market sends the application name information and installation package storage path information of the target Android APP to the Android emulator through inter-process communication; The Android emulator obtains the first installation package of the target Android APP according to the shared path indicated by the installation package storage path information of the target Android APP and the application name information of the target Android APP. The Android emulator loads the first installation package of the target Android APP through the Android system to install the target Android APP.

10. The method according to any one of claims 1 to 4 or any one of claims 7 to 8, characterized in that, Before generating the second installation package, the method further includes: when the target Android APP is installed on the Android emulator, the Android emulator obtains the application information of the target Android APP, the application information of the target Android APP including the package name, application icon, application name, version information, screen orientation information, installation time and / or name identifier corresponding to the target Android APP. The second installation package also includes the application name and application configuration information corresponding to the target Android APP.

11. The method according to any one of claims 7 to 8, characterized in that, After installing the target Android app, the method further includes: The Android emulator sends a first response message to the application market via inter-process communication. The first response message includes the package name of the target Android APP and the result that the target Android APP has been installed. Based on the first response message, the app store updates the display of the installation control corresponding to the target Android APP in the app store to an activation control.

12. The method according to any one of claims 1 to 4 or any one of claims 7 to 8, characterized in that, The step of responding to a user's operation to open a target Android app on the terminal device, and opening the target Android app through the Android emulator, includes: In response to the user's opening operation on the shortcut icon of the target Android APP, the terminal device calls the driver program for opening the target Android APP in the second installation package associated with the shortcut icon of the target Android APP, triggers the Android emulator to enable the APP opening function; and reads the package name of the target Android APP from the application configuration information of the second installation package and sends the package name of the target Android APP to the Android emulator. The Android emulator locates the target Android APP in the emulator based on the package name of the target Android APP, draws the first window corresponding to the target Android APP on the terminal device, and opens the target Android APP through the Android system, placing the running interface of the target Android APP into the first window.

13. The method according to any one of claims 1 to 4 or any one of claims 7 to 8, characterized in that, The step of uninstalling the target Android app via the Android emulator in response to a user's uninstallation operation on the terminal device includes: In response to the user's uninstall operation on the shortcut icon of the target Android APP on the terminal device, the terminal device calls the driver for uninstalling the target Android APP in the second installation package corresponding to the target Android APP, triggers the Android emulator to enable the APP uninstallation function; and reads the package name of the target Android APP from the application configuration information of the second installation package, and sends the package name of the target Android APP to the Android emulator. The Android emulator locates the target Android app within itself based on the app's package name and then uninstalls the target Android app through the Android system.

14. The method according to any one of claims 1 to 4 or any one of claims 7 to 8, characterized in that, Deleting the shortcut icon of the target Android APP from the terminal device includes: The Android emulator calls the second API of the Windows operating system to delete the shortcut icon and the second installation package corresponding to the target Android APP on the terminal device.

15. The method according to any one of claims 7 to 8, characterized in that, After uninstalling the target Android app, the method further includes: The Android emulator sends a second response message to the application market in the terminal device via inter-process communication. The second response message includes the package name of the target Android APP and the result that the target Android APP has been uninstalled. Based on the second response message, the app market updates the display of the launch control corresponding to the target Android app as an installation control.

16. A method for controlling an Android application (APP), applied to an Android emulator, characterized in that, The Android emulator runs in the background, and the method includes: The Android emulator installs, starts, or uninstalls the target Android APP using a second installation package generated by the Android emulator according to a first instruction; the first instruction is triggered by the user performing an installation, starting, or uninstallation operation on the target Android APP on a terminal device running a Windows operating system, and the target Android APP is an application applicable to the Android operating system; the second installation package is associated with a shortcut icon of the target Android APP and includes a driver for starting the target Android APP and a driver for uninstalling / updating the target Android APP; When the target Android app is installed on the Android emulator, the Android emulator creates a shortcut to the target Android app on the terminal device; or, When the target Android app is launched on the Android emulator, the Android emulator displays the running interface of the target Android app on the desktop of the terminal device; or, When the target Android app is uninstalled by the Android emulator, the Android emulator deletes the shortcut of the target Android app from the terminal device.

17. The method according to claim 16, characterized in that, The Android emulator installs, starts, or uninstalls the target Android app according to the first instruction, including: In response to the first instruction, the Android emulator starts in the background; The Android emulator installs, opens, or uninstalls the target Android app according to the first instruction.

18. The method according to claim 16, characterized in that, The Android emulator creates a shortcut to the target Android app on the terminal device, including: The Android emulator calls the Windows operating system's first application programming interface (API) to create a shortcut to the target Android app on the terminal device, triggering the display of the shortcut icon of the target Android app on the terminal device.

19. The method according to claim 16, characterized in that, The Android emulator creates a shortcut to the target Android app on the terminal device, including: The Android emulator creates a shortcut to the target Android app in the start menu of the terminal device; and / or, The Android emulator creates a shortcut to the target Android app in the uninstall or change program interface under the control panel of the terminal device; and / or, The Android emulator creates a shortcut to the target Android app on the desktop of the terminal device; and / or, The Android emulator creates a shortcut to the target Android app in the application function interface under the settings of the terminal device.

20. The method according to claim 18 or 19, characterized in that, The filename corresponding to the shortcut icon includes preset characters and the application name of the target Android APP; wherein, the preset characters are blank characters or invisible characters.

21. The method according to any one of claims 16 to 19, characterized in that, The first instruction is triggered when the user installs the target Android APP through the application market installed on the terminal device; The Android emulator installs the target Android app according to the first instruction, including: The Android emulator receives the first instruction sent by the application market through inter-process communication. The first instruction includes the application name information and installation package storage path information of the target Android APP. The Android emulator obtains the first installation package of the target Android APP according to the shared path indicated by the installation package storage path information of the target Android APP and the application name information of the target Android APP. The Android emulator loads the first installation package of the target Android APP through the Android system to install the target Android APP.

22. The method according to any one of claims 16 to 19, characterized in that, Before generating the second installation package, the method further includes: When the target Android APP is installed on the Android emulator, the Android emulator obtains the application information of the target Android APP. The application information of the target Android APP includes the package name, application icon, application name, version information, screen orientation information, installation time and / or name identifier corresponding to the target Android APP. The second installation package also includes the application name and application configuration information corresponding to the target Android APP.

23. The method according to claim 21, characterized in that, After the Android emulator installs the target Android app according to the first instruction, the method further includes: The Android emulator sends a first response message to the application market in the terminal device via inter-process communication. The first response message includes the package name of the target Android APP and the result that the target Android APP has been installed.

24. The method according to any one of claims 16 to 19, characterized in that, The first instruction is triggered by the user opening the shortcut icon of the target Android APP on the terminal device, or by the user opening the corresponding control of the target Android APP in the app store on the terminal device. The Android emulator launches the target Android APP according to the first instruction, including: when the target Android APP is installed on the Android emulator, in response to the first instruction, the Android emulator calls the driver program for launching the target Android APP in the second installation package associated with the shortcut icon of the target Android APP, triggering the Android system to launch the target Android APP; The Android emulator displays the running interface of the target Android APP on the desktop of the terminal device, including: the Android emulator draws a first window for the target Android APP on the desktop of the terminal device, and adds the running interface of the target Android APP to the first window through the Android system.

25. The method according to claim 24, characterized in that, The Android emulator draws a first window for the target Android APP on the desktop of the terminal device, including: The Android emulator draws the first window on the desktop of the terminal device according to the landscape and portrait screen information corresponding to the target Android APP.

26. The method according to claim 25, characterized in that, When the landscape / portrait information indicates landscape mode, the horizontal dimension of the first window drawn by the Android emulator is greater than its vertical dimension; When the screen orientation information indicates portrait orientation, the vertical dimension of the first window drawn by the Android emulator is greater than its horizontal dimension.

27. The method according to any one of claims 16 to 19 or any one of claims 23, 25 and 26, characterized in that, The first instruction is triggered by the user performing an uninstall operation on the shortcut icon of the target Android APP on the terminal device; The Android emulator uninstalls the target Android APP according to the first instruction, including: the Android emulator calls the driver for uninstalling the target Android APP in the second installation package corresponding to the target Android APP according to the first instruction, reads the package name of the target Android APP from the application configuration information of the second installation package, finds the target Android APP according to the package name of the target Android APP, and uninstalls the target Android APP through the Android system.

28. The method according to claim 23, 25 or 26, characterized in that, After uninstalling the target Android app, the method further includes: The Android emulator sends a second response message to the application market in the terminal device via inter-process communication. The second response message includes the package name of the target Android APP and the result that the target Android APP has been uninstalled.

29. A terminal device, characterized in that, The device includes a processor coupled to a memory, the processor being configured to execute a computer program or instructions stored in the memory to cause the terminal device to implement the method as described in any one of claims 1 to 15 or the method as described in any one of claims 16 to 28.

30. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when run on a terminal device, causes the terminal device to perform the method as described in any one of claims 1 to 15 or the method as described in any one of claims 16 to 28.

Images