CN113608753A

CN113608753A - Application uninstalling method, application recovery method, electronic device and storage medium

Info

Publication number: CN113608753A
Application number: CN202110788793.8A
Authority: CN
Inventors: 石方
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-07-13
Filing date: 2021-07-13
Publication date: 2021-11-05

Abstract

The application is used for providing an application uninstalling method, an application recovery method, an electronic device and a computer readable storage medium. The application unloading method comprises the following steps: receiving an application uninstalling operation for uninstalling a first application; responding to the application uninstalling operation, determining that the first application is a key application, and outputting first prompt information; the first prompt message is used for prompting the function of the first application to the user. In this application, when the first application to be uninstalled is a key application, the electronic device may output prompt information for prompting a user of a function of the first application. The user can confirm whether to continue uninstalling the application according to the information so as to avoid the application from being deleted by mistake.

Description

Application uninstalling method, application recovery method, electronic device and storage medium

Technical Field

The present application relates to the field of software technologies, and in particular, to an application uninstalling method, an application recovery method, an electronic device, and a computer-readable storage medium.

Background

In order to enrich the functions of an electronic device (e.g., a mobile phone), manufacturers of the electronic device may preset a certain number of system applications in the electronic device, such as a memo, a voice assistant, a screen recording, and the like. Some of the system applications are underlying applications (e.g., screen recording applications) that provide support for the functionality of the electronic device. When the user views such an application in the application list, the user may misunderstand that the application is an application having no actual function, and thus may wrongly delete the application.

After the application is deleted by mistake, the electronic equipment does not support the function corresponding to the application. For example, after the screen recording application is deleted by mistake, the electronic device will not support the screen recording function. The user may misunderstand that the electronic device has a fault, and the user experience is poor.

Disclosure of Invention

Some embodiments of the present application provide an application uninstalling method, an application recovery method, an electronic device, and a computer-readable storage medium, which are described below in various aspects, and embodiments and advantages of the following aspects may be mutually referenced.

In a first aspect, an application uninstalling method is provided in an electronic device, where the electronic device includes a first application; the method comprises the following steps: receiving an application uninstalling operation for uninstalling a first application; responding to the application uninstalling operation, determining that the first application is a key application, and outputting first prompt information; the first prompt message is used for prompting the function of the first application to the user.

According to the embodiment of the application, when the first application to be uninstalled is a key application, the electronic device may output prompt information for prompting a user of a function of the first application. The user can confirm whether to continue uninstalling the application according to the information so as to avoid the application from being deleted by mistake.

In some embodiments, determining that the first application is a critical application comprises: and determining the first application as a key application according to a preset key application list.

In some embodiments, the list of the key applications is a list preset in the electronic device when the electronic device leaves a factory, or a list acquired by the electronic device from a server for managing the applications.

According to the embodiment of the application, the key application list can be a list acquired from a server. Therefore, the list can be updated according to the user feedback so as to better meet the user requirements.

In some embodiments, an operating system of an electronic device includes an application layer and an application framework layer for providing services to the application layer; receiving an application uninstall operation for uninstalling a first application, comprising: the application program layer receives the application uninstalling operation and sends an application uninstalling request to the application program framework layer; in response to an application uninstalling operation, determining that a first application is a key application, and outputting first prompt information, including: the application framework layer determines that the first application is a key application in response to receiving the application uninstalling request; the application framework layer controls an output device of the electronic equipment to output first prompt information.

According to the implementation mode of the application, the original logic of the application layer is not changed, and the application is friendly to application developers.

In some embodiments, the first prompt message includes: text, sound, pictures, animations or video describing the functionality of the first application. According to the application implementation mode, the function information of the first application can be output in a more intuitive mode, so that the situation that the user deletes the application by mistake is avoided.

In some embodiments, the first application is a system application. The method and the device can avoid the situation that important system applications are deleted by mistake.

In a second aspect, the present application provides a method for recovering an uninstalled application, for an electronic device, the method including: receiving application starting operation for starting a first application; in response to receiving the application launch operation, determining that the first application is an application that has been uninstalled from the electronic device; and outputting second prompt information, wherein the second prompt information is used for prompting the user to install the first application.

According to the method and the device, the electronic equipment can automatically recover and start the target application based on the application starting operation, so that the user operation can be simplified, and the user experience is improved.

In some embodiments, the method further comprises: in response to receiving an application installation operation for confirming installation of the first application, installing the first application, wherein the application installation operation is an operation executed by a user according to the second prompt message; and starting to run the first application based on the first application is successfully installed.

In some embodiments, the first application is a system application; installing the first application includes: acquiring an application installation package of a first application from a first storage directory of the electronic equipment, wherein the first storage directory is a directory used by the electronic equipment for storing a system application installation package; the first application is installed based on the application installation package of the first application.

In a third aspect, an embodiment of the present application provides an electronic device, including: a memory to store instructions for execution by one or more processors of an electronic device; the processor, when executing the instructions in the memory, may cause the electronic device to perform the application uninstalling method provided in any embodiment of the first aspect of the present application, or perform the application starting method provided in any embodiment of the second aspect of the present application. The beneficial effects that can be achieved by the third aspect may refer to the beneficial effects of any embodiment of the first aspect of the present application or the beneficial effects of any embodiment of the second aspect of the present application, and are not described herein again.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium having instructions stored thereon, where the instructions, when executed on a computer, cause the computer to perform an application uninstalling method provided in any embodiment of the first aspect of the present application, or perform an application starting method provided in any embodiment of the second aspect of the present application. The beneficial effects that can be achieved by the fourth aspect can refer to the beneficial effects of any embodiment of the first aspect of the present application or the beneficial effects of any embodiment of the second aspect of the present application, and are not described herein again.

Drawings

Fig. 1 is an application scene schematic diagram of an application uninstalling method/application starting method provided in an embodiment of the present application;

fig. 2 is a first schematic view of a mobile phone interface provided in an embodiment of the present application;

fig. 3 is a software architecture diagram of a mobile phone according to an embodiment of the present application;

fig. 4 is a schematic flowchart of an application uninstalling method according to an embodiment of the present application;

fig. 5 is a schematic view of a mobile phone interface provided in the embodiment of the present application;

FIG. 6 is an interface diagram for prompting application functionality provided by an embodiment of the present application;

fig. 7 is a schematic flowchart of an application recovery method according to an embodiment of the present application;

FIG. 8 is an interface diagram for recovering an application provided by an embodiment of the present application;

FIG. 9 is an interface diagram for prompting an application start failure according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a mobile phone provided in an embodiment of the present application;

FIG. 11 shows a block diagram of an electronic device provided by an embodiment of the application;

fig. 12 shows a schematic structural diagram of a System On Chip (SOC) provided in an embodiment of the present application.

Detailed Description

Hereinafter, specific embodiments of the present application will be described in detail with reference to the accompanying drawings.

Fig. 1 shows an application scenario of an embodiment of the present application. Referring to fig. 1, a mobile phone 100 has a plurality of applications installed thereon, some of which are system applications, such as memo, alarm clock, and screen recording; part of the applications being third-party applications, e.g. Baidu maps^TMJitter tone^TMAnd the like.

The system application is an application that is preinstalled in the mobile phone 100 when the mobile phone 100 leaves the factory. A mobile phone manufacturer (e.g., glory, hua, millet, etc.) can realize necessary functions of the mobile phone 100 by presetting a certain number of system applications in the mobile phone 100, for example, the mobile phone 100 can have a telephone function (this kind of applications is also called "system necessary applications") by presetting a "telephone" application in the mobile phone 100; on the other hand, personalized functions of the brand of the mobile phone 100 can be enriched, for example, by adding a "voice assistant" application to the mobile phone 100, a user can operate the mobile phone 100 through a voice instruction in addition to operating the mobile phone 100 through a display interface of the mobile phone 100, for example, an application (e.g., an alarm clock application) on the mobile phone 100 is started through a voice instruction.

According to the requirements of some national laws and regulations or industry specifications, for unnecessary system applications, the terminal should open unloading authority for users, so that the users can unload the system applications according to the requirements. For example, according to the provisional regulations on the application software provisioning and distribution management of the mobile intelligent terminal (implemented in 7/1/2017) made by the ministry of industry and trust of the people's republic of china, in addition to the necessary system applications such as "bluetooth", "telephone", "application store", etc., other system applications provisioned in the mobile phone 100 should be set to be uninstallable.

When a user is uninstalling an application, some applications, especially system applications without desktop icons, may be deleted by mistake. Take the "screen recording" application shown in fig. 1 as an example. The screen recording application can record image data of the interface of the mobile phone 100 and audio data of the mobile phone 100 when running. The screen recording application is typically run in synchronization with other applications (e.g., game applications) on the cell phone 100 to record the running process of the other applications. Therefore, the screen recording application belongs to a support type application, and icons of the application may not be set on the desktop of the mobile phone 100. When the user views the application in the application list (such as the list shown in fig. 1), the user may mistakenly assume that the application is not needed, and thus mistakenly delete the application.

After deleting the screen recording application, the cell phone 100 will not support the screen recording function provided by the screen recording application. For example, referring to fig. 2, when the user clicks the "screen recording" button in the drop menu bar of the cell phone 100, the cell phone 100 will not respond. At this time, the user may misunderstand that the mobile phone has a fault, and the user experience is poor.

Therefore, the application uninstalling method is provided in the embodiments of the present application, and is used to avoid that a user deletes an application by mistake, so as to improve user experience.

According to the embodiment of the application, when the electronic device receives an application uninstalling operation for uninstalling a target application (also referred to as a "first application", for example, a screen recording application), the electronic device determines whether the target application is a key application according to a preset key application list. When the target application is a key application, the electronic device outputs (e.g., displays) prompt information (as first prompt information) for prompting a user for a function of the target application. The user can judge whether to continue uninstalling the application according to the prompt message so as to avoid mistakenly deleting the application.

The application does not limit the form of the electronic equipment, and the electronic equipment can be a mobile phone, a tablet, a notebook computer, a smart screen, vehicle-mounted equipment (such as a car machine and a vehicle-mounted navigator), wearable equipment (such as an intelligent bracelet/watch and an intelligent helmet) and other various forms as long as the electronic equipment can be operated and applied.

Specific embodiments of the present application are described below. In the embodiment of the present application, the mobile phone 100 is taken as an example of an electronic device, but it is understood that the present application is not limited thereto.

First, a software architecture of the mobile phone 100 in the embodiment of the present application is described. The software system of the mobile phone 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present invention uses an Android system with a layered architecture as an example to exemplarily illustrate a software structure of the mobile phone 100.

Fig. 3 is a block diagram of a software structure of the mobile phone 100 according to an embodiment of the present disclosure. The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer from top to bottom.

The application layer may include a series of application packages. As shown in FIG. 3, the application layer may include various applications shown in FIG. 1, such as a Baidu map^TMAlarm clock, tremble sound^TMScreen recording, etc.; the application layer may also include other applications than those shown in fig. 1, such as settings, launchers (launchers), system UI, calendar, WLAN, bluetooth, music, video, short messages, etc.

Among other things, system ui (systemui) applications are used to provide a user with system-level information display and interaction, such as a lock screen interface, a drop-down status bar (interface shown in fig. 2), left/right menu bars, a bottom navigation bar, and the like.

A Launcher application may provide desktop-based information to a userDisplaying and interacting. For example, the Launcher application may display a plurality of application icons (e.g., a hundredth map) on a desktop of the electronic device^TMWhen a user clicks an application icon, the Launcher application may request the application framework layer to launch the application.

The application framework layer provides an Application Programming Interface (API) and a programming framework for the application program of the application layer. The application framework layer includes a number of predefined functions.

As shown in FIG. 3, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, package manager, and the like.

A Package Manager (PMS) is used to manage application packages on the electronic device. For example, state information of an application on the electronic device (e.g., package name, authority, version number, etc. of the application) is recorded, installation, uninstallation, query service, etc. of the application are provided. In some embodiments, when an application on the electronic device changes (e.g., the application is uninstalled or upgraded), the PMS updates the state information of the application.

An Activity Manager (AMS) for providing a start-up service of an application. For example, when a user clicks on an icon of an application on the desktop, the Launcher application specifically starts the application by sending an application start request to the AMS.

The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.

The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide the communication functions of the handset 100. Such as management of call status (including on, off, etc.).

The resource manager provides various resources for the application, such as localized strings, icons, pictures, layout files, video files, and the like.

The notification manager enables the application to display notification information in the status bar, can be used to convey notification-type messages, can disappear automatically after a short dwell, and does not require user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, prompting text information in the status bar, sounding a prompt tone, vibrating the electronic device, flashing an indicator light, etc.

The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.

The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.

The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.

The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.

The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, and the like.

The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.

The 2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a sensor driver.

The following describes a specific process of the application uninstalling method provided in the embodiment of the present application.

[ EXAMPLES one ]

The embodiment is used for providing an application uninstalling method to prevent a user from deleting an application by mistake. In the present embodiment, an application that is easily deleted by mistake, namely, a "screen recording" application, is taken as an example of a target application (also referred to as a "first application"), but the present application is not limited thereto. In other embodiments, the target application may be a system application such as "voice assistant", "memo", "alarm clock", or may be a "Baidu map^TM"," tremble sound^TM"pay treasure^TM"and" love art^TM"wait for third party application. In addition, the target application may be an application without a desktop icon or an application with a desktop icon.

For simplicity, in the following description, the application layer of the mobile phone 100 (as an example of the electronic device) is simply referred to as "application layer", and the application framework layer of the mobile phone 100 is simply referred to as "framework layer".

Referring to fig. 4, the application uninstalling method provided in this embodiment includes the following steps:

s110: the application layer receives an application uninstall operation for uninstalling the target application.

In this embodiment, the mobile phone 100 receives an application uninstalling operation from a user through a setting application of an application layer. Specifically, after the user clicks an application management menu of the setting application, the application management interface 110 shown in fig. 1 may be entered. By clicking a control 111 corresponding to the screen recording application on the application management interface 110, the mobile phone 100 can display an application information interface 120 as shown in fig. 5. After the user clicks the "uninstall" button on the interface 120, the setup application receives the application uninstall operation.

But the application is not limited thereto. In other embodiments, the handset 100 may receive the application uninstall operation from the user in other ways. For example, in some embodiments, when the target application has a desktop icon, the handset 100 may receive an application uninstall operation based on the Launcher application. For example, the user may perform a set operation (e.g., a long press operation) on the target application desktop icon to call out an uninstall option of the target application. After the user selects the uninstall option, the Launcher application receives the application uninstall operation. In other embodiments, the user may send voice instructions to the voice assistant application of the cell phone 100 to receive application uninstall operations through the voice assistant application.

S120: the application layer sends an application offload request to the framework layer.

After receiving the application uninstalling operation, the application layer sends an application uninstalling request to the packet manager PMS of the framework layer. For example, an application offload request is sent to the PMS by calling the packagelnstaller. The application uninstall request may carry an identifier of the screen recording application. Illustratively, this identification is the package name "recordscreen.

S130: and the framework layer judges whether the target application is a key application.

And after receiving the application uninstalling request, the PMS judges whether the target application is a key application according to the application identifier carried in the request. If the target application is a key application, the PMS performs step S140 to output a prompt message to the user; if the target application is not a critical application, the PMS performs step S160 to perform an application uninstall operation.

Specifically, the mobile phone 100 stores a key application list, and the key application list includes application identifiers (for example, package names) of key applications of the mobile phone 100. After receiving the application uninstalling request, the PMS matches the application identifier carried in the request with the application identifier in the key application list, and determines whether the target application is the key application according to the matching result. If the application identifier of the target application is matched with the list, the target application is a key application (namely, the key application list is a white list); otherwise, the target application is not a critical application.

Table 1 is an example of the list of critical applications provided in this embodiment. Table 1 includes the application name, application package name, function description of the application, resource path of the application, and installation package path of the application of each key application. The file pointed by the resource path is an application function specification file, for example, memoite.png is a memo application function specification file (specifically, a file in a picture format); the file pointed by the installation package path is an installation package of the application. In some operating systems (e.g., Android), the installation package of the system application is not deleted after the system application is uninstalled.

TABLE 1 list of key applications

It should be noted that table 1 is an exemplary illustration of the key application list, the form of the application list is not limited thereto, and other modifications may be made by those skilled in the art. For example, in some embodiments, only some of the information in the above table, such as the application name and the application package name, may be included in the list. The information such as the function description, the resource path, and the installation package path may be stored in other manners or forms as long as the information can be associated with the application. In some other embodiments, the list of critical applications may include third party applications in addition to system applications.

In this embodiment, the application identifier carried by the application uninstall request is "recordscreen. After matching the application package name in table 1, the PMS confirms that the application identifier is the same as the package name of the screen recording application in table 1 (as a matching example), and thus, the PMS determines that the target application is a key application.

An exemplary manner of obtaining the list of critical applications is described below.

Example one: the key application list is a list preset in the mobile phone 100 before the mobile phone 100 leaves the factory. Before the mobile phone 100 leaves the factory, the device manufacturer adds the important application to the key application list to prevent the user from deleting the important application by mistake. Important applications may be applications that have a greater impact on the performance of the mobile phone 100 (e.g., voice assistants), applications that can significantly improve the user experience (e.g., screen recording), and so on.

Example two: the list of critical applications is a list downloaded by the handset 100 from a server, illustratively a server that manages applications by the device vendor. The server has a list of critical applications stored thereon, which may be periodically updated (e.g., deleted or added) by the device vendor based on user feedback. The handset 100 can download the updated list from the server to better fit the user's needs. Illustratively, the handset 100 may download the latest list of critical applications from the server periodically; and after the application uninstalling operation is received, downloading the latest key application list from the server in real time.

Example three: the list of critical applications is a list that the handset 100 obtains indirectly from a server. That is, the list of critical applications is a list obtained by the mobile phone 100 from a server through another device (referred to as a "transfer device"). Taking the transit device as a PC as an example, after the PC downloads the list of the key applications from the server, the mobile phone 100 obtains the list from the PC. In this way, the handset 100 can download the list of critical applications from the PC while offline (i.e., without accessing the internet). Illustratively, the PC obtains the list of key applications from the server through a terminal management application (e.g., sunglory mobile phone assistant Suite, Hisuite, millet assistant, etc.); the mobile phone 100 may obtain the list from the PC through short-distance communication methods such as NFC, bluetooth, WiFi, and the like. Illustratively, each time the mobile phone 100 establishes a communication connection with the PC (i.e., each time the communication state of the mobile phone 100 with the PC changes from a disconnected state to a connected state), the mobile phone 100 acquires the latest list of critical applications from the PC.

S140: the framework layer controls the mobile phone 100 to output the prompt information (as the first prompt information).

After determining that the screen recording application is the key application, the PMS controls the display screen of the mobile phone 100 to display prompt information to prompt the user of the function of the screen recording application, so as to avoid the user from deleting the application by mistake. Several examples of the hint information are given below.

Example one: the prompt message includes text describing the functions of the screen recording application. Fig. 6(a) shows an example of the prompt message. Referring to fig. 6(a), the mobile phone 100 displays a prompt message in the form of a prompt box 121, where the prompt message includes an explanatory text that "this application is a system application providing a screen recording function, and the screen recording function of the mobile phone is not available after uninstallation" to prompt the user of the screen recording application. Illustratively, the caption may be a caption acquired by the PMS from the column "function description" in table 1.

Example two: the prompt message includes a picture for describing the function of the screen recording application. Fig. 6(b) shows an example of the prompt message. Referring to fig. 6(b), unlike the first example, the prompt box 122 displayed by the mobile phone 100 includes a picture 122 in addition to the explanatory text in fig. 6 (a). The picture 122 is used to remind the user that the screen recording button of the pull-down menu bar will be disabled after the screen recording application is deleted. In this example, the electronic device may output the function information of the screen recording application in a more intuitive manner to avoid the user from deleting the application by mistake. Illustratively, the picture 122 may be a picture taken by the PMS according to the path described in the column "resource path" in table 1.

In the above example, the PMS outputs the prompt message through the display screen of the mobile phone 100. In other examples, the PMS may output the prompt message as a prompt tone through an audio output device (e.g., a speaker) of the mobile phone 100, or output the prompt message as vibration through a vibration output device (e.g., a motor) of the mobile phone 100, etc., as long as the function of the target application can be prompted to the user, which is not limited in the present application.

In addition, in other examples, the prompt information may further include sound, animation, video, or the like for describing the function of the target application to output the function information of the target application in a more intuitive manner. Further, the sound, animation or video resource involved in the prompt message may be a resource obtained by the PMS according to the path described in the column "resource path" in table 1. For example, when the target application is a memo, the PMS may acquire an animation file "memotote. That is to say, in this embodiment, by presetting a resource path in the key application list, the PMS can conveniently acquire various resource files for describing the application functions.

S150: and the framework layer confirms whether to continue uninstalling the target application according to the received user input.

In this embodiment, the PMS listens for user actions on the interface 120 to confirm whether to continue uninstalling the screen recording application. For example, when the user clicks the "confirm uninstall" button on the interface 120 shown in fig. 6(a) or fig. 6(b), the PMS determines to continue uninstalling the application, and performs the application uninstall step S160; when the user clicks the "cancel uninstall" button on the interface 120 shown in fig. 6(a) or fig. 6(b), the PMS terminates the application uninstall task and the method ends.

S160: the framework layer uninstalls the target application.

Specifically, the PMS executes the packageinstaler. uninstantall method to uninstall the screen recording application. For example, the PMS deletes a folder (e.g.,/data/app/recordScreen) corresponding to the screen recording application in the application installation directory, deletes a folder (e.g.,/data/data/recordScreen) corresponding to the screen recording application in the application data directory, and updates application state information recorded in the PMS, etc.

According to the application uninstalling method provided by the embodiment, when the electronic device receives an application uninstalling operation for uninstalling a target application, whether the target application is a key application is determined according to a built-in key application list. When the electronic equipment confirms that the target application is the key application, prompt information for prompting the function of the target application to the user is output, and the user can confirm whether to continue uninstalling the application according to the information. Therefore, the embodiment can reduce the misoperation of the user and avoid the application being deleted by mistake.

In addition, the present embodiment determines whether the target application is a critical application through a framework layer of the electronic device, and therefore, the application uninstalling method provided by the present embodiment may not change the original logic of the application layer. That is, after receiving the application uninstalling operation, the application layer sends an application uninstalling request to the framework layer according to the original logic. Therefore, the application uninstalling method provided by the embodiment can reduce the change of the application layer, and is friendly to application developers.

However, the present application is not limited thereto, and in other embodiments, each step (for example, the step S130 of determining whether the target application is a critical application) in the method provided in this embodiment may also be executed by the application layer.

In some implementations, when a user uninstalls a third-party application, the electronic device may investigate the reason for the uninstallation of the third-party application. In this embodiment, the prompt information may be output for the important system application to be uninstalled (i.e., the system application on the key application list), so as to prevent the user from deleting the important system application by mistake. Some important system applications are not provided with desktop icons, and therefore belong to applications which are easily deleted by a user by mistake. The embodiment can output the prompt information of the application, and can further ensure that the important system application is not deleted by mistake compared with a mode of only investigating the uninstalling reason of the third-party application.

The embodiment provides a method for avoiding the application from being unloaded by mistake. In some cases, after an application is misunloaded, the user may wish to recover the misdeleted application. In some implementations, to recover the deleted application, the user needs to manually download the installation package of the application from the application market and install the downloaded installation package, which is cumbersome to operate. In addition, for a system application such as a screen recording application, an installation package of the system application may not exist in the application market, that is, the user cannot download the installation package of the system application from the application market. Thus, when the user restores the system application, the user needs to manually search the installation package file in the electronic device to restore the application, which further increases the complexity of the operation.

Therefore, the embodiment of the application also provides a recovery method of the uninstalled application, which can recover the deleted application in a convenient manner, thereby simplifying user operation. The following is a detailed description.

[ example two ]

The present embodiment is configured to provide a method for recovering an uninstalled application, which is used to recover a target application that is uninstalled on a mobile phone 100 (as an example of an electronic device). In the present embodiment, a "screen recording" application is still taken as an example of the electronic device, but it is understood that the present application is not limited thereto.

Referring to fig. 7, the application recovery method provided in this embodiment includes the following steps:

s210: the cell phone 100 receives an application start operation for starting a target application.

Specifically, the system UI application on the cell phone 100 receives an application start operation from the user. The system UI application is used to provide system-level information display and interaction for the user, such as a drop-down status bar (interface shown in fig. 2), a left-side menu bar, and so forth. When the user clicks the "screen recording" button on the drop-down menu bar interface shown in fig. 2, the system UI application receives an application start operation for starting the screen recording application.

In this embodiment, the application start operation is a click operation performed by the user on the interface of the mobile phone 100, but the application is not limited thereto. In other embodiments, the application start operation may be a shortcut key operation (e.g., power key + volume up key), a finger joint operation, a gesture operation, a voice instruction, etc. from the user, which is not limited in this application.

In addition, the system UI application is taken as an example of an application that receives an application start operation, but the present application is not limited thereto. For example, when the user clicks a "screen recording" button embedded therein in the third-party application, the mobile phone 100 receives an application start operation through the third-party application; when the user performs the application start operation by means of the voice instruction, the mobile phone 100 receives the application start operation through the voice assistant application.

S220: the handset 100 determines whether the target application is available (i.e., whether the target application is already installed on the handset 100).

Specifically, the system UI application judges whether the screen recording application is available, and if the screen recording application is available, the system UI application normally starts the screen recording application; if not, the system UI application judges that the screen recording application has been uninstalled, and thus performs step S230 to ask the user whether to install the screen recording application.

The present embodiment does not limit the method for determining whether the target application is available for the system UI application, and several examples are given below.

Example one: the system UI application transmits an application start request for starting a screen recording application to a framework layer activity manager AMS (AMS is a system service for starting an application). When screen recording is available (namely, when the screen recording application is installed), the AMS normally starts the screen recording application; when the screen recording application is unavailable (i.e., when the screen recording application is not installed), the AMS returns a result that the screen recording application is unavailable to the system UI application.

Example two: the system UI application sends a query request to the framework layer packet manager PMS, and the PMS determines whether the screen recording application is available according to the application state information recorded by the PMS and returns a query result to the system UI application. When the query result shows that the screen recording application is available, the system UI application normally starts the application through the AMS; when the query result indicates that the screen recording application is not available, the system UI application performs step S230.

S230: the mobile phone 100 outputs a prompt message (as a second prompt message) to prompt the user to install the target application.

And when the system UI application determines that the screen recording application is unavailable, controlling the electronic equipment to output prompt information to prompt a user to install the target application. Illustratively, the system UI application controls the handset 100 display screen to display an interface 130 as shown in fig. 8 to prompt the user to install the screen recording application.

S240: the mobile phone 100 confirms whether to install the target application according to the received user operation.

Illustratively, the system UI application listens to user operations acting on the interface 130 to confirm whether or not to install the screen recording application. For example, when the user clicks the "resume application" button on the interface 130 according to the prompt information shown in fig. 8, the system UI application determines to install the target application, and performs the application installation step S250; when the user clicks the "cancel" button on the interface 130 shown in fig. 8, the system UI application determines that the target application is not installed, and performs step S260.

S250: the handset 100 installs and starts the target application.

Specifically, the system UI application sends an application installation request to the package manager PMS to install the screen recording application. After the screen recording application is installed successfully, the system UI application sends an application start request to the activity manager AMS to start the installed screen recording application.

In this embodiment, the screen recording application is a system application. Generally, the mobile phone 100 is preset with installation files of various system applications. Illustratively, the installation files for each system application are stored under the handset 100 vendor custom directory (as a first storage directory, e.g.,/system/preload directory). When a system application is uninstalled, the installation package of the system application is typically not deleted. When the PMS receives the application installation request, the installation package file of the screen recording application may be acquired from the storage directory of the system application installation package, and the screen recording application may be installed based on the installation package file.

In addition, the application installation request sent by the system UI application to the PMS may also carry a storage path of the target application installation package. For example, the system UI application may obtain the storage path of the target application installation package from the column "installation package path" of the key application list shown in table 1.

In other embodiments, when the target application is a third-party application, the application installation request sent by the system UI application to the PMS may carry a download address (e.g., a URL address) of the target application installation package. The PMS may acquire the application installation package file through the download address (e.g., download the installation package file from the application marketplace server), and install the target application based on the downloaded installation package file. Optionally, the installation package download address of the third-party application is stored in the key application list, so that the system UI application can obtain the download address conveniently.

S260: the handset 100 outputs information of the start failure of the target application.

When the user clicks "cancel" on the interface 130 shown in fig. 8, the system UI application determines not to restore the screen recording application, and displays information of application start failure, which may include the reason of application start failure, through the display screen of the mobile phone 100. Illustratively, the mobile phone 100 outputs information of the application start failure through the interface as shown in fig. 9.

According to the application recovery method provided by the embodiment, when the target application to be started does not exist on the electronic equipment, the electronic equipment can automatically install and start the target application according to the instruction of the user, and compared with a mode of manually downloading the installation package from an application market/manually searching the installation package from the electronic equipment and installing the application, the method can remarkably simplify the operation of the user, and therefore the user experience is improved.

In addition, the application recovery method provided in this embodiment is used as a convenient way for installing an application, and may be applied to, in addition to recovering an uninstalled application, installing a new application (an application that is not installed on the electronic device), and the application is not limited in this application.

Fig. 10 shows a schematic structural diagram of a mobile phone 100 according to an embodiment of the present application. The mobile phone 100 (as an example of an electronic device) may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) connector 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identification Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It is to be understood that the illustrated structure of the embodiment of the present invention does not specifically limit the mobile phone 100. In other embodiments of the present application, the handset 100 may include more or fewer components than shown, or some components may be combined, some components may be separated, or a different arrangement of components may be used. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

The processor can generate an operation control signal according to the instruction operation code and the timing signal to complete the control of instruction fetching and instruction execution.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110. If the processor 110 needs to reuse the instruction or data, it can be called directly from the memory. Avoiding repeated accesses reduces the latency of the processor 110, thereby increasing the efficiency of the system.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, and a Subscriber Identity Module (SIM) interface.

The I2C interface is a bi-directional synchronous serial bus that includes a serial data line (SDA) and a Serial Clock Line (SCL). In some embodiments, processor 110 may include multiple sets of I2C buses. The processor 110 may be coupled to the touch sensor 180K, the charger, the flash, the camera 193, etc. through different I2C bus interfaces, respectively. For example: the processor 110 may be coupled to the touch sensor 180K through an I2C interface, so that the processor 110 and the touch sensor 180K communicate through an I2C bus interface to implement the touch function of the mobile phone 100.

The I2S interface may be used for audio communication. In some embodiments, processor 110 may include multiple sets of I2S buses. The processor 110 may be coupled to the audio module 170 via an I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 may communicate audio signals to the wireless communication module 160 via the I2S interface, enabling answering of calls via a bluetooth headset.

The PCM interface may also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled by a PCM bus interface. In some embodiments, the audio module 170 may also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to implement a function of answering a call through a bluetooth headset. Both the I2S interface and the PCM interface may be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communications. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, a UART interface is generally used to connect the processor 110 with the wireless communication module 160. For example: the processor 110 communicates with a bluetooth module in the wireless communication module 160 through a UART interface to implement a bluetooth function. In some embodiments, the audio module 170 may transmit the audio signal to the wireless communication module 160 through a UART interface, so as to realize the function of playing music through a bluetooth headset.

MIPI interfaces may be used to connect processor 110 with peripheral devices such as display screen 194, camera 193, and the like. The MIPI interface includes a Camera Serial Interface (CSI), a Display Serial Interface (DSI), and the like. In some embodiments, the processor 110 and the camera 193 communicate through a CSI interface to implement the camera function of the handset 100. The processor 110 and the display screen 194 communicate through the DSI interface to implement the display function of the mobile phone 100.

The GPIO interface may be configured by software. The GPIO interface may be configured as a control signal and may also be configured as a data signal. In some embodiments, a GPIO interface may be used to connect the processor 110 with the camera 193, the display 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface may also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, and the like.

It should be understood that the connection relationship between the modules according to the embodiment of the present invention is only an exemplary illustration, and does not limit the structure of the mobile phone 100. In other embodiments of the present application, the mobile phone 100 may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

The USB connector 130 is a connector conforming to the USB standard specification, and can be used to connect the mobile phone 100 and a peripheral device, and specifically can be a standard USB connector (e.g., Type C connector), a Mini USB connector, a Micro USB connector, and the like. The USB connector 130 may be used to connect a charger to charge the mobile phone 100, and may also be used to transmit data between the mobile phone 100 and peripheral devices. And the earphone can also be used for connecting an earphone and playing audio through the earphone. The connector may also be used to connect other electronic devices, such as AR devices and the like. In some embodiments, processor 110 may support a Universal Serial Bus (Universal Serial Bus), which may have a standard specification of USB1.x, USB2.0, USB3.x, USB 4.

The wireless communication function of the mobile phone 100 can be realized by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, the baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in the handset 100 may be used to cover a single or multiple communication bands. Different antennas can also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed as a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 may provide a solution including wireless communication of 2G/3G/4G/5G, etc. applied to the handset 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication applied to the mobile phone 100, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), Bluetooth (BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, the antenna 1 of the handset 100 is coupled to the mobile communication module 150 and the antenna 2 is coupled to the wireless communication module 160 so that the handset 100 can communicate with networks and other devices through wireless communication techniques. The wireless communication technology may include global system for mobile communications (GSM), General Packet Radio Service (GPRS), code division multiple access (code division multiple access, CDMA), Wideband Code Division Multiple Access (WCDMA), time-division code division multiple access (time-division code division multiple access, TD-SCDMA), Long Term Evolution (LTE), LTE, BT, GNSS, WLAN, NFC, FM, and/or IR technologies, etc. The GNSS may include a Global Positioning System (GPS), a global navigation satellite system (GLONASS), a beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS), and/or a Satellite Based Augmentation System (SBAS).

The mobile phone 100 implements the display function through the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and an application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, video, and the like. The display screen 194 includes a display panel. The display panel may adopt a Liquid Crystal Display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (active-matrix organic light-emitting diode, AMOLED), a flexible light-emitting diode (FLED), a miniature, a Micro-oeld, a quantum dot light-emitting diode (QLED), and the like. In some embodiments, the cell phone 100 may include 1 or N display screens 194, with N being a positive integer greater than 1.

The mobile phone 100 may implement a shooting function through the ISP, the camera 193, the video codec, the GPU, the display 194, the application processor, and the like.

The ISP is used to process the data fed back by the camera 193. For example, when a photo is taken, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing and converting into an image visible to naked eyes. The ISP can also carry out algorithm optimization on the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in camera 193.

The camera 193 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing element converts the optical signal into an electrical signal, which is then passed to the ISP where it is converted into a digital image signal. And the ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into image signal in standard RGB, YUV and other formats. In some embodiments, the handset 100 may include 1 or N cameras 193, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process digital image signals and other digital signals. For example, when the handset 100 is in frequency bin selection, the digital signal processor is used to perform fourier transform or the like on the frequency bin energy.

Video codecs are used to compress or decompress digital video. Handset 100 may support one or more video codecs. Thus, the handset 100 can play or record video in a variety of encoding formats, such as: moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, and the like.

The NPU is a neural-network (NN) computing processor that processes input information quickly by using a biological neural network structure, for example, by using a transfer mode between neurons of a human brain, and can also learn by itself continuously. The NPU can realize applications such as intelligent recognition of the mobile phone 100, for example: image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to extend the storage capability of the mobile phone 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function. For example, files such as music, video, etc. are saved in an external memory card.

The internal memory 121 may be used to store computer-executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. The storage program area may store an operating system, an application program (such as a sound playing function, an image playing function, etc.) required by at least one function, and the like. The data storage area may store data (e.g., audio data, a phonebook, etc.) created during use of the handset 100, and the like. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (UFS), and the like. The processor 110 executes various functional applications of the cellular phone 100 and data processing by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor. The instructions stored in the internal memory 121 may include: when executed by at least one of the processors 110, causes the handset 100 to implement the application uninstallation method or the application recovery method provided by embodiments of the present application.

The mobile phone 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playing, recording, etc.

The audio module 170 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be disposed in the processor 110, or some functional modules of the audio module 170 may be disposed in the processor 110.

The speaker 170A, also called a "horn", is used to convert the audio electrical signal into an acoustic signal. The cellular phone 100 can listen to music through the speaker 170A or listen to a hands-free call.

The receiver 170B, also called "earpiece", is used to convert the electrical audio signal into an acoustic signal. When the cellular phone 100 receives a call or voice information, it is possible to receive voice by placing the receiver 170B close to the ear of the person.

The microphone 170C, also referred to as a "microphone," is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can input a voice signal to the microphone 170C by speaking the user's mouth near the microphone 170C. The handset 100 may be provided with at least one microphone 170C. In other embodiments, the handset 100 may be provided with two microphones 170C to achieve noise reduction functions in addition to collecting sound signals. In other embodiments, the mobile phone 100 may further include three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions.

The headphone interface 170D is used to connect a wired headphone. The earphone interface 170D may be the USB connector 130, or may be an open mobile electronic device platform (OMTP) standard interface of 3.5mm, or a cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The keys 190 include a power-on key, a volume key, and the like. The keys 190 may be mechanical keys. Or may be touch keys. The cellular phone 100 may receive a key input, and generate a key signal input related to user setting and function control of the cellular phone 100.

The motor 191 may generate a vibration cue. The motor 191 may be used for incoming call vibration cues, as well as for touch vibration feedback. For example, touch operations applied to different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 191 may also respond to different vibration feedback effects for touch operations applied to different areas of the display screen 194. Different application scenes (such as time reminding, receiving information, alarm clock, game and the like) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

Indicator 192 may be an indicator light that may be used to indicate a state of charge, a change in charge, or a message, missed call, notification, etc.

The SIM card interface 195 is used to connect a SIM card. The SIM card can be attached to and detached from the cellular phone 100 by being inserted into the SIM card interface 195 or being pulled out from the SIM card interface 195. The handset 100 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 195 may support a Nano SIM card, a Micro SIM card, a SIM card, etc. The same SIM card interface 195 can be inserted with multiple cards at the same time. The types of the plurality of cards may be the same or different. The SIM card interface 195 may also be compatible with different types of SIM cards. The SIM card interface 195 may also be compatible with external memory cards. The mobile phone 100 interacts with the network through the SIM card to implement functions such as communication and data communication. In some embodiments, the handset 100 employs esims, namely: an embedded SIM card. The eSIM card can be embedded in the mobile phone 100 and cannot be separated from the mobile phone 100.

Referring now to FIG. 11, shown is a block diagram of an electronic device 400 in accordance with one embodiment of the present application. The electronic device 400 may include one or more processors 401 coupled to a controller hub 403. For at least one embodiment, the controller hub 403 communicates with the processor 401 via a multi-drop Bus such as a Front Side Bus (FSB), a point-to-point interface such as a QuickPath Interconnect (QPI), or similar connection 406. Processor 401 executes instructions that control general types of data processing operations. In one embodiment, Controller Hub 403 includes, but is not limited to, a Graphics Memory Controller Hub (GMCH) (not shown) and an Input Output Hub (IOH) (which may be on separate chips) (not shown), where the GMCH includes a Memory and a Graphics Controller and is coupled to the IOH.

The electronic device 400 may also include a coprocessor 402 and memory 404 coupled to the controller hub 403. Alternatively, one or both of the memory and GMCH may be integrated within the processor (as described herein), with the memory 404 and coprocessor 402 coupled directly to the processor 401 and controller hub 403, with the controller hub 403 and IOH in a single chip.

The Memory 404 may be, for example, a Dynamic Random Access Memory (DRAM), a Phase Change Memory (PCM), or a combination of the two. Memory 404 may include one or more tangible, non-transitory computer-readable media for storing data and/or instructions therein. A computer-readable storage medium has stored therein instructions, and in particular, temporary and permanent copies of the instructions. The instructions may include: instructions that, when executed by at least one of the processors, cause the electronic device 400 to implement the method illustrated in fig. 4 and 7. When the instructions are executed on a computer, the computer is caused to execute the method disclosed in the first embodiment and/or the second embodiment.

In one embodiment, the coprocessor 402 is a special-purpose processor, such as, for example, a high-throughput Integrated Core (MIC) processor, a network or communication processor, compression engine, graphics processor, General-purpose computing on graphics processing unit (GPGPU), embedded processor, or the like. The optional nature of coprocessor 402 is represented in FIG. 11 by dashed lines.

In one embodiment, electronic device 400 may further include a Network Interface Controller (NIC) 406. Network interface 406 may include a transceiver to provide a radio interface for electronic device 400 to communicate with any other suitable device (e.g., front end module, antenna, etc.). In various embodiments, the network interface 406 may be integrated with other components of the electronic device 400. The network interface 406 may implement the functions of the communication unit in the above-described embodiments.

The electronic device 400 may further include an Input/Output (I/O) device 405. I/O405 may include: a user interface designed to enable a user to interact with the electronic device 400; the design of the peripheral component interface enables peripheral components to also interact with the electronic device 400; and/or sensors are designed to determine environmental conditions and/or location information associated with electronic device 400.

It is noted that fig. 11 is merely exemplary. That is, although fig. 11 shows that the electronic device 400 includes a plurality of devices, such as a processor 401, a controller hub 403, a memory 404, etc., in practical applications, a device using the methods of the present application may include only a part of the devices of the electronic device 400, and for example, may include only the processor 401 and the network interface 406. The nature of the alternative device in fig. 11 is shown in dashed lines.

Referring now to fig. 12, shown is a block diagram of a System on Chip (SoC) 500 in accordance with an embodiment of the present application. In fig. 12, like parts have the same reference numerals. In addition, the dashed box is an optional feature of more advanced socs. In fig. 12, the SoC500 includes: an interconnect unit 550 coupled to the processor 510; a system agent unit 580; a bus controller unit 590; an integrated memory controller unit 540; a set or one or more coprocessors 520 which may include integrated graphics logic, an image processor, an audio processor, and a video processor; a Static Random Access Memory (SRAM) unit 530; a Direct Memory Access (DMA) unit 560. In one embodiment, coprocessor 520 comprises a special-purpose processor, such as, for example, a network or communication processor, compression engine, General-purpose computing on graphics processing units (GPGPU), a high-throughput MIC processor, or an embedded processor, among others.

Static Random Access Memory (SRAM) unit 530 may include one or more tangible, non-transitory computer-readable media for storing data and/or instructions. A computer-readable storage medium has stored therein instructions, and in particular, temporary and permanent copies of the instructions. The instructions may include: instructions that when executed by at least one of the processors cause the SoC to implement the method as shown in fig. 4, 7. The instructions, when executed on a computer, cause the computer to perform the methods disclosed in embodiment one and/or embodiment two above.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone.

The method embodiments of the present application may be implemented in software, magnetic, firmware, etc.

Program code may be applied to input instructions to perform the functions described herein and generate output information. The output information may be applied to one or more output devices in a known manner. For purposes of this application, a processing system includes any system having a Processor such as, for example, a Digital Signal Processor (DSP), a microcontroller, an Application Specific Integrated Circuit (ASIC), or a microprocessor.

The program code may be implemented in a high level procedural or object oriented programming language to communicate with a processing system. The program code can also be implemented in assembly or machine language, if desired. Indeed, the mechanisms described herein are not limited in scope to any particular programming language. In any case, the language may be a compiled or interpreted language.

One or more aspects of at least one embodiment may be implemented by representative instructions stored on a computer-readable storage medium, which represent various logic in a processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. These representations, known as "Intellectual Property (IP) cores," may be stored on a tangible computer-readable storage medium and provided to a number of customers or production facilities to load into the manufacturing machines that actually manufacture the logic or processors.

In some cases, an instruction converter may be used to convert instructions from a source instruction set to a target instruction set. For example, the instruction converter may transform (e.g., using a static binary transform, a dynamic binary transform including dynamic compilation), morph, emulate, or otherwise convert the instruction into one or more other instructions to be processed by the core. The instruction converter may be implemented in software, hardware, firmware, or a combination thereof. The instruction converter may be on the processor, off-processor, or partially on and partially off-processor.

Claims

1. An application uninstalling method is used for an electronic device, and is characterized in that the electronic device comprises a first application; the method comprises the following steps:

receiving an application uninstall operation for uninstalling the first application;

responding to the application uninstalling operation, determining that the first application is a key application, and outputting first prompt information; the first prompt message is used for prompting the function of the first application to a user.

2. The method of claim 1, wherein the determining that the first application is a critical application comprises:

and determining the first application as a key application according to a preset key application list.

3. The method according to claim 1, wherein the list of critical applications is a list preset in the electronic device at a factory of the electronic device, or a list acquired by the electronic device from a server for managing applications.

4. The method of claim 1, wherein the operating system of the electronic device comprises an application layer and an application framework layer for providing services to the application layer;

the receiving an application uninstall operation to uninstall the first application includes:

the application program layer receives the application uninstalling operation and sends an application uninstalling request to the application program framework layer;

the determining that the first application is a key application in response to the application uninstalling operation, and outputting first prompt information includes:

the application framework layer determines that the first application is a critical application in response to receiving the application uninstall request;

and the application program framework layer controls an output device of the electronic equipment to output the first prompt message.

5. The method of claim 1, wherein the first prompt comprises: text, sound, pictures, animations or video describing the functionality of the first application.

6. The method of claim 1, wherein the first application is a system application.

7. A method for recovering an uninstalled application, for an electronic device, the method comprising:

receiving application starting operation for starting a first application;

in response to receiving the application launch operation, determining that the first application is an application that has been uninstalled from the electronic device;

and outputting second prompt information, wherein the second prompt information is used for prompting a user to install the first application.

8. The method of claim 7, further comprising:

in response to receiving an application installation operation for confirming installation of the first application, installing the first application, wherein the application installation operation is an operation executed by a user according to the second prompt message;

based on successfully installing the first application, launching and running the first application.

9. The method of claim 7, wherein the first application is a system application; the installing the first application comprises:

acquiring an application installation package of the first application from a first storage directory of the electronic equipment, wherein the first storage directory is a directory used by the electronic equipment for storing a system application installation package;

installing the first application based on an application installation package of the first application.

10. An electronic device, comprising:

a memory to store instructions for execution by one or more processors of the electronic device;

a processor that, when executing the instructions in the memory, causes the electronic device to perform the method of any of claims 1-9.

11. A computer-readable storage medium having instructions stored thereon, which when executed on a computer, cause the computer to perform the method of any one of claims 1 to 9.