CN116737258B - Method and related device for unloading application - Google Patents

Abstract

The embodiment of the application provides a method and a related device for unloading an application, and relates to the technical field of terminals. The method comprises the following steps: the terminal equipment receives an operation of uninstalling the SIM card application; at a first moment, stopping a component running in a target process by the SIM card application by the terminal equipment, and registering a registered component or a registered callback of the SIM card application in the target process, wherein the target process is a process in which the SIM card application and other applications co-process; and unloading the SIM card application by the terminal equipment at a second moment, wherein the second moment is later than the first moment. Therefore, when the SIM card application is unloaded, the operation of other services in the process of co-processing with the SIM card application is not influenced, and the user experience is improved.

Description

Method and related device for uninstalling application

Technical Field

The present application relates to the field of terminal technology, and in particular to a method for uninstalling an application and a related device.

Background technique

With the development of terminal technology, various types of applications can be installed in terminal devices, such as system applications, third-party applications, etc., and users can manage these applications in the terminal devices.

However, when the user cleans up the memory of the terminal device or manages the desktop of the terminal device and wants to uninstall some infrequently used system applications, other services may crash, giving the user a bad experience.

Summary of the invention

The embodiment of the present application provides a method and a related device for uninstalling an application. When a terminal device uninstalls a SIM card application, the terminal device can first stop the operation of some components of the SIM card application that cannot be deleted because they are running in the Phone process, or deregister some components or callbacks of the SIM card application that cannot be deleted because they are registered in the Phone process, and then execute the uninstallation process. Therefore, when the SIM card application is uninstalled, the operation of other services in the Phone process that shares the same process with the SIM card application is not affected, thereby improving the user experience.

Alternatively, when the terminal device uninstalls the SIM card application, the terminal device can restart the Phone process after executing the SIM card application uninstallation process. Because the SIM card application has been uninstalled when the Phone process is restarted, the SIM card application will not run in the Phone process, so the components of the SIM card application will not run or the components or callbacks of the SIM card application will not be registered in the Phone process, so that the SIM card application will not affect the Phone process. Therefore, when the SIM card application is uninstalled, it will not affect the operation of other services in the Phone process that share the SIM card application process, thereby improving the user experience.

In a first aspect, an embodiment of the present application provides a method for uninstalling an application, the method comprising:

The terminal device receives an operation to uninstall the SIM card application; at the first moment, the terminal device stops the components of the SIM card application running in the target process, and deregisters the components or registered callbacks of the SIM card application in the target process, and the target process is a process in which the SIM card application and other applications share the same process; at the second moment, the terminal device uninstalls the SIM card application, and the second moment is later than the first moment. In this way, when the SIM card application is uninstalled, the operation of other services in the process in which the SIM card application shares the same process with the SIM card application is not affected, thereby improving the user experience.

In a possible implementation, the components of the SIM card application running in the target process may include a service component; the components registered by the SIM card application in the target process may include a receiver component; the callbacks registered by the SIM card application in the target process may include a timer service callback AlarmManger.OnAlarmListener, and/or a callback callback. In this way, when uninstalling the SIM card application, the terminal device cannot delete the components of the SIM card application running in the target process, or the registered components or callbacks, so these components or callbacks need to be processed separately, so as to ensure the normal operation of the target process.

In a possible implementation, the terminal device stops the component of the SIM card application running in the target process, which may include: the terminal device calls a function to close the service component. In this way, before uninstalling the SIM card application, the terminal device can close the running service component to enable the target process to run normally, thereby not affecting other services in the target process.

In a possible implementation, the terminal device deregistering the component registered by the SIM card application in the target process may include: the terminal device calling a function to deregister the broadcast receiver Receiver component. In this way, before uninstalling the SIM card application, the terminal device can enable the target process to run normally by deregistering the broadcast receiver Receiver component, thereby not affecting other services in the target process.

In a possible implementation, the terminal device deregistering the callback registered by the SIM card application in the target process may include: the terminal device calling the function of deregistering the timed task callback AlarmManger.OnAlarmListener; and/or the terminal device calling the function of registering the callback callback. In this way, before uninstalling the SIM card application, the terminal device can make the target process run normally by deregistering the timed task callback AlarmManger.OnAlarmListener or deregistering the callback callback, so as not to affect other services in the target process.

In a possible implementation manner, before the terminal device receives the operation of uninstalling the SIM card application, the method may further include: the terminal device registers uninstall broadcast for the SIM card application.

According to the operation of uninstalling the SIM card application received by the terminal device, at the first moment, the terminal device stops the components of the SIM card application running in the target process, and de-registers the components or callbacks of the SIM card application registered in the target process, which may include: according to the operation, the terminal device sends an uninstall broadcast, and the uninstall broadcast may include the identifier of the SIM card application; when the terminal device determines through the SIM card application that the uninstall broadcast includes the identifier of the SIM card application, at the first moment, the terminal device stops the components of the SIM card application running in the target process, and de-registers the components or callbacks of the SIM card application registered in the target process.

In this way, when the user triggers the operation of uninstalling the application, the terminal device sends the uninstall broadcast so that the application or module registered for the uninstall broadcast can receive the uninstall broadcast, so that the related application or module can perform the operation of uninstalling the application after receiving the uninstall broadcast.

In a possible implementation, the terminal device registers an uninstall broadcast for the SIM card application, which may include: the terminal device adds a field Intent.ACTION_PACKAGE_REMOVED corresponding to the uninstall broadcast to the intent filter IntentFilter, and adds the identifier of the SIM card application. In this way, by registering the uninstall broadcast for the SIM card application, the terminal device can conveniently receive the uninstall broadcast of uninstalling the SIM card application and further execute the relevant uninstall process.

In a possible implementation, the target process may include a Phone process. In this way, the SIM card application and the Phone process are co-processed, so that SIM-related services can run normally and provide users with SIM-related services well.

In a second aspect, an embodiment of the present application provides another method for uninstalling an application, the method comprising:

The terminal device receives an operation to uninstall the SIM card application; at the third moment, the terminal device uninstalls the SIM card application; at the fourth moment, the terminal device restarts the target process, the target process is a process that the SIM card application shares with other applications, and the fourth moment is later than the third moment. In this way, when the SIM card application is uninstalled, the operation of other services in the Phone process that shares with the SIM card application is not affected, thereby improving the user experience.

In a possible implementation, before the terminal device uninstalls the SIM card application, the process may further include: the terminal device displays a pop-up window, wherein the pop-up window includes an OK button, a Cancel button, and prompt information for prompting the risk of uninstalling the SIM card application.

The terminal device uninstalling the SIM card application may include: in response to the operation of the confirmation button, the terminal device uninstalls the SIM card application. In this way, during the uninstallation process, the terminal device prompts the user with a pop-up window to prompt the user of the risks of uninstalling the SIM card application, so that the user can understand the unknown risks in time and improve the user experience.

In a possible implementation, before the terminal device displays the pop-up window, the terminal device may also include: the terminal device determines that the SIM card application is a co-process application through the configuration file of the SIM card application. In this way, when the terminal device determines that the process corresponding to the uninstalled application is a co-process with other processes, it can restart the process so that the process no longer loads the relevant data of the uninstalled application, so that other services in the process can run normally.

In a possible implementation, the target process includes a Phone process. In this way, the SIM card application and the Phone process share the same process, which can enable SIM-related services to run normally and provide users with SIM-related services.

In a third aspect, an embodiment of the present application provides a device for uninstalling an application, which may be a terminal device, or a chip or chip system in a terminal device. The device for uninstalling an application may include a display unit and a processing unit. The display unit is used to implement any method related to display executed by the terminal device in the first aspect or any possible implementation of the first aspect, or in the second aspect or any possible implementation of the second aspect. The processing unit is used to implement any method related to processing executed by the terminal device in the first aspect or any possible implementation of the first aspect, or in the second aspect or any possible implementation of the second aspect. When the device for uninstalling an application is a terminal device, the processing unit may be a processor. The device for uninstalling an application may also include a storage unit, which may be a memory. The storage unit is used to store instructions, and the processing unit executes the instructions stored in the storage unit to enable the terminal device to implement a method described in the first aspect or any possible implementation of the first aspect, or in the second aspect or any possible implementation of the second aspect. When the device for uninstalling an application is a chip or chip system in a terminal device, the processing unit may be a processor. The processing unit executes the instructions stored in the storage unit to enable the terminal device to implement a method described in the first aspect or any possible implementation of the first aspect, or in the second aspect or any possible implementation of the second aspect. The storage unit may be a storage unit in the chip (e.g., a register, a cache, etc.), or a storage unit in the terminal device that is located outside the chip (e.g., a read-only memory, a random access memory, etc.).

Exemplarily, in implementing the first aspect or any possible implementation method of the first aspect, the processing unit is used to receive an operation to uninstall a SIM card application; is also used to stop components of the SIM card application running in a target process, and to deregister components or registered callbacks of the SIM card application in the target process; and is also used to uninstall the SIM card application.

In a possible implementation, the components of the SIM card application running in the target process include the service component; the components registered by the SIM card application in the target process include the receiver component; the callbacks registered by the SIM card application in the target process include the timer service callback AlarmManger.OnAlarmListener, and/or callback.

In a possible implementation, the processing unit is used to call a function for closing a service component.

In a possible implementation, the processing unit is used to call a function to register a broadcast receiver Receiver component.

In a possible implementation, the processing unit is configured to call a function for deregistering a scheduled task callback AlarmManger.OnAlarmListener; and/or call a function for deregistering a callback callback.

In one possible implementation, the processing unit is used to register an uninstall broadcast for a SIM card application; and is also used to send an uninstall broadcast, where the uninstall broadcast includes an identifier of the SIM card application; and is specifically used to, when determining through the SIM card application that the uninstall broadcast includes the identifier of the SIM card application, at the first moment, stop the component of the SIM card application running in the target process, and deregister the component or callback that has been registered by the SIM card application in the target process.

In a possible implementation manner, the processing unit is configured to add a field Intent.ACTION_PACKAGE_REMOVED corresponding to the uninstall broadcast to the intent filter IntentFilter, and add an identifier of the SIM card application.

In a possible implementation, the target process includes a Phone process.

Exemplarily, in implementing the second aspect or any possible implementation manner of the second aspect, the processing unit is used to receive an operation of uninstalling a SIM card application; is also used to uninstall the SIM card application; and is also used to restart a target process.

In a possible implementation, the display unit is used to display a pop-up window, which includes a confirmation button, a cancel button, and prompt information for prompting the risks of uninstalling the SIM card application.

The processing unit is used for uninstalling the SIM card application by the terminal device in response to the operation of the confirmation button.

In a possible implementation manner, the processing unit is configured to determine, through a configuration file of the SIM card application, whether the SIM card application is a co-process application.

In a possible implementation, the target process includes a Phone process.

In a fourth aspect, an embodiment of the present application provides an electronic device, comprising a processor and a memory, the memory being used to store code instructions, and the processor being used to run the code instructions to execute the uninstallation application method described in the first aspect or any possible implementation of the first aspect, or to execute the uninstallation application method described in the second aspect or any possible implementation of the second aspect.

In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is run on a computer, the computer executes the uninstallation application method described in the first aspect or any possible implementation of the first aspect, or executes the uninstallation application method described in the second aspect or any possible implementation of the second aspect.

In a sixth aspect, an embodiment of the present application provides a computer program product comprising a computer program. When the computer program runs on a computer, the computer executes the application uninstallation method described in the first aspect or any possible implementation of the first aspect, or executes the application uninstallation method described in the second aspect or any possible implementation of the second aspect.

In a seventh aspect, the present application provides a chip or a chip system, the chip or chip system comprising at least one processor and a communication interface, the communication interface and the at least one processor are interconnected by a line, and the at least one processor is used to run a computer program or instruction to execute the unloading application method described in the first aspect or any possible implementation of the first aspect, or to execute the unloading application method described in the second aspect or any possible implementation of the second aspect. Among them, the communication interface in the chip can be an input/output interface, a pin or a circuit, etc.

In a possible implementation, the chip or chip system described above in the present application further includes at least one memory, in which instructions are stored. The memory may be a storage unit inside the chip, such as a register, a cache, etc., or a storage unit of the chip (e.g., a read-only memory, a random access memory, etc.).

It should be understood that the third to seventh aspects of the present application correspond to the technical solutions of the first or second aspect of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

FIG2 is a schematic diagram of a software structure of a terminal device provided in an embodiment of the present application;

FIG3 is a schematic diagram of a method for cleaning an application provided in an embodiment of the present application;

FIG4 is a schematic diagram of a pop-up window prompt when a terminal device uninstalls an application provided in an embodiment of the present application;

FIG5 is a schematic diagram of a flow chart of a method for uninstalling an application provided in an embodiment of the present application;

FIG6 is a schematic diagram of a method for uninstalling an application provided in an embodiment of the present application;

FIG7 is a schematic diagram of another method for uninstalling an application provided in an embodiment of the present application;

FIG8 is a schematic diagram of the structure of a chip provided in an embodiment of the present application.

Detailed ways

In order to clearly describe the technical solutions of the embodiments of the present application, some terms and technologies involved in the embodiments of the present application are briefly introduced below:

1. 3GPP protocol: It is the globally applicable technical specifications and technical reports developed by the 3rd Generation Partnership Project (3GPP) for the third generation mobile system, which realizes the smooth transition from 2G network to 3G network and ensures the backward compatibility of future technologies.

2. Ril: The radio interface layer (Ril) is responsible for data communication between the terminal device and the mobile network, including data transmission, command sending, and response message parsing. Ril can also provide a general application programming interface (application programming interface, API) for applications in the application layer. For example, Ril can provide APIs related to phone calls, text messages, network status, and subscriber identity module (SIM) card status.

3. CatService module: can receive and parse the data related to the SIM card application tool kit (STK) sent by Ril, and can also send the parsed data to STK.

4. STK: SIM card application tool kit (STK) is a basic SIM card service application tool defined by the 3GPP protocol. STK application (APP) can also be called SIM card application.

The STK APP may contain a series of protocol instructions for SIM card interaction. Based on the protocol instructions, the STK APP may interact with the program in the SIM card to implement the operation of the program in the SIM card, and then the terminal device may implement the SIM card related services provided by the operator. Among them, the series of protocol instructions for SIM card interaction may also be called SIM card instructions.

Exemplarily, when the terminal device receives an operation of the user clicking on the STK APP on the desktop, the terminal device can open the STK APP in response to the operation. The menu reported by the SIM card can be displayed in the interface of the STK APP. When the STK APP monitors that the user clicks on the relevant menu, the STK APP can pass the received STK-related instructions to the CatService module. After receiving the instruction, the CatService module processes the instruction into the format required by Ril and passes it to Ril. Ril can process the instruction through the modem and pass it to the SIM card, and then the SIM card can process the instruction based on the service provided by the operator.

5. Phone process: It is a system process in the Android system. Phone process can execute phone calls, text messages, Internet access and other related services. Phone process is the startup process of the terminal device. After the terminal device is started, the Phone process continues to run. If the Phone process exits abnormally during operation, the terminal device can automatically restart the Phone process.

6. Terminology

In the embodiments of the present application, words such as "first" and "second" are used to distinguish the same or similar items with substantially the same functions and effects. For example, the first chip and the second chip are only used to distinguish different chips, and their order is not limited. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit them to be different.

It should be noted that in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

In the embodiments of the present application, "at least one" refers to one or more, and "plurality" refers to two or more. "And/or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character "/" generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a-b, a--c, b-c, or a-b-c, where a, b, c can be single or multiple.

7. Terminal equipment

The terminal device of the embodiment of the present application may also be any form of electronic device. For example, the electronic device may include a handheld device with mobile communication function, a vehicle-mounted device, etc. For example, some electronic devices are: mobile phones, tablet computers, PDAs, laptop computers, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (public land mobile The embodiments of the present application do not limit this.

As an example but not limitation, in the embodiments of the present application, the electronic device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

In addition, in the embodiments of the present application, the electronic device can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects people and machines and things.

The electronic devices in the embodiments of the present application may also be referred to as: terminal equipment, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.

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

Exemplarily, FIG1 shows a schematic structural diagram of an electronic device.

The electronic device may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 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 button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a SIM card interface 195, etc. 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, etc.

It is to be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the electronic device. In other embodiments of the present application, the electronic device may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (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. Different processing units may be independent devices or integrated into one or more processors.

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

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. If the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (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, a SIM card interface, and/or a USB interface, etc.

It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present invention is only a schematic illustration and does not constitute a structural limitation of the electronic device. In other embodiments of the present application, the electronic device may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

The electronic device implements the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the 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 change display information.

The electronic device can realize the shooting function through ISP, camera 193, video codec, GPU, display screen 194 and application processor.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device. 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 and videos can be stored in the external memory card.

The internal memory 121 can be used to store computer executable program codes, and the executable program codes include instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (universal flash storage, UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device by running instructions stored in the internal memory 121, and/or instructions stored in a memory provided in the processor. For example, the method for uninstalling an application in an embodiment of the present application may be executed.

FIG2 is a software structure diagram of a terminal device in an embodiment of the present application. 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 software interfaces. In some embodiments, the Android system is divided into four layers, namely, from top to bottom, the application layer, the application framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer.

The application layer can include a series of application packages. As shown in Figure 2, the application package can include SIM card, phone, SMS, memo, camera and other applications. The applications corresponding to these application packages can be system applications or third-party applications.

The application framework layer is also called the Framework layer, which can provide API and programming framework for the applications in the application layer. The application framework layer includes some pre-defined functions.

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

The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, touch the screen, drag the screen, capture the screen, etc.

The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, the terminal device vibrates, the indicator light flashes, etc.

Content providers are used to implement data sharing between different applications, allowing one program to access data in another program while ensuring the security of the accessed data.

The view system can be responsible for the application interface drawing and event processing.

Android runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes the java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection. For example, in the embodiment of the present application, the virtual machine can be used to perform functions such as uninstalling applications.

The system library may include multiple functional modules, such as media libraries, function libraries, graphics processing libraries (such as OpenGL ES), etc.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The function library provides developers with API interfaces for multiple services, making it easy for developers to quickly integrate and implement various functions.

The graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis and layer processing.

The kernel layer is the layer between hardware and software. The kernel layer may include display driver, camera driver, audio driver, CPU driver, USB driver, battery driver, etc.

Applications in terminal devices can support uninstallation. In some implementations, when a user uninstalls an application, the application process can be closed and the application data of the application can be deleted in the Framework layer of the terminal system to release memory resources in the terminal device system. However, if the uninstalled application is shared with other processes, the process shared with the application will not be closed in the Framework layer when the application is uninstalled, resulting in that after the application data of the application is deleted, the process may still use the application data of the deleted application, causing the process to fail, and the service corresponding to the process may crash.

For example, taking the uninstallation of STK APP as an example, since STK APP is executed in the Phone process, or it can be understood that STK APP and Phone are co-processes, and STK APP is the startup application of the terminal device, after the terminal device is started, STK APP can be started and run continuously. When STK APP is uninstalled, the application data of STK APP can be deleted, but the Phone process will not be closed. Therefore, some components of STK APP running in the Phone process will not be deleted, and some components or callbacks of STK APP registered in the Phone process will not be deleted, and these components or callbacks may still run in the Phone process.

During the operation of these components or callbacks, the application data of the deleted STK APP may be called, which may cause the Phone process to run incorrectly and crash. The corresponding phone calls, text messages, Internet access and other services of the Phone process may be temporarily unavailable, giving users a bad experience.

For example, in a possible implementation, in the scenario where the terminal device modifies the system language, it may involve the situation where the corresponding services of the STK APP are run in the Phone process. For example, the SIM card can support several different languages. When the terminal device receives the user's operation to modify the system language of the terminal device, the terminal device can send a system broadcast in response to the operation. The system broadcast is used to notify that the system language has been modified. In the Phone process, the STK APP can receive the system broadcast and perform the corresponding business processing flow of the STK.

However, when the STK APP is uninstalled, the broadcast receiver registered by the STK APP for receiving the broadcast of the modified system language will not be deleted, and the broadcast receiver will still receive the broadcast of the modified system language in the Phone process. After receiving the broadcast, the broadcast receiver will perform the corresponding business processing flow of STK. However, since the application data of the STK APP has been deleted, the broadcast receiver cannot call the application data of the deleted STK APP in the Phone process, which will cause the execution process of the Phone process to fail, the Phone process will crash, etc., and then affect other businesses running in the Phone process.

In another possible implementation, in the scenario of inserting or removing a SIM card from a terminal device, the situation of running the corresponding service of the STK APP in the Phone process may be involved. For example, when the terminal device receives an operation of inserting or removing a SIM card from a user, the terminal device may send a broadcast in response to the operation, and the broadcast is used to notify the insertion or removal of the SIM card. In the Phone process, the STK APP may receive the broadcast and process the relevant service processes of inserting or removing a SIM card.

However, when the STK APP is uninstalled, the broadcast receiver registered by the STK APP for receiving broadcasts of inserting or removing the SIM card will not be deleted, and the broadcast receiver will still receive broadcasts of inserting or removing the SIM card in the Phone process. After receiving the broadcast, the broadcast receiver will perform the corresponding business processing flow of STK. However, since the application data of the STK APP has been deleted, the broadcast receiver cannot call the application data of the deleted STK APP in the Phone process, resulting in errors in the execution process of the Phone process, the Phone process crashes, etc., which in turn affects other services running in the Phone process.

In view of this, in an application uninstallation method provided in an embodiment of the present application, when a terminal device uninstalls an STK APP, the terminal device may first stop the operation of some components of the STK APP that cannot be deleted because they are running in the Phone process, or deregister some components or callbacks of the STK APP that cannot be deleted because they are registered in the Phone process, and then execute the uninstallation process. Therefore, when the STK APP is uninstalled, the operation of other services in the Phone process that shares the same process with the STK APP will not be affected, thereby improving the user experience.

Alternatively, when the terminal device uninstalls the STK APP, the terminal device can restart the Phone process after executing the STK APP uninstallation process. Because the STK APP has been uninstalled when the Phone process is restarted, the STK APP will not run in the Phone process. Therefore, the components of the STK APP will not run or the components or callbacks of the STK APP will not be registered in the Phone process, so that the STK APP will not affect the Phone process. Therefore, when the STK APP is uninstalled, it will not affect the operation of other services in the Phone process that share the STK APP process, thereby improving the user experience.

The following describes in detail the method for uninstalling applications in the embodiments of the present application through specific embodiments. The following embodiments can be combined with each other or implemented independently, and the same or similar concepts or processes may not be described in detail in some embodiments.

In an application uninstallation method of an embodiment of the present application, before the STK APP is uninstalled, the terminal device may first stop the operation of some components of the STK APP that cannot be deleted because they are running in the Phone process, or deregister some components or callbacks of the STK APP that cannot be deleted because they are registered in the Phone process. Exemplarily, the components that need to be stopped from running in the Phone process or the components or callbacks registered in the Phone process that need to be deregistered may include: a service Service component, a receiver Receiver component, a timer service callback AlarmManger.OnAlarmListener, and a callback callback, etc. Among them, the receiver Receiver component may include a broadcast receiver BrooastcastReceiver component.

It is understandable that there may be other components in the STK APP that need to stop running in the Phone process or need to deregister some components or callbacks registered in the Phone process, etc., which is not limited in the embodiments of the present application.

In a possible implementation, FIG3 shows a schematic diagram of the method for uninstalling an application according to an embodiment of the present application, taking uninstalling the STK APP as an example. The specific steps may be:

S301: Register and uninstall broadcast.

The terminal device can register an uninstall broadcast for the STK APP. It is understandable that the terminal device can register an uninstall broadcast based on the STK APP, or it can register an uninstall broadcast for the STK APP based on other applications or modules in the terminal device, which is not limited in the embodiments of the present application. Among them, the terminal device can register an uninstall broadcast when the STK APP is started, or it can register an uninstall broadcast in other applications or modules. The specific process of registering and uninstalling broadcast is not limited in the embodiments of the present application.

For example, when the STK APP application is started, the STK APP registers the uninstall broadcast as an example. The process of registering the uninstall broadcast may include:

STK APP can add the field Intent.ACTION_PACKAGE_REMOVED corresponding to the uninstall broadcast to the intent filter IntentFilter, and add the package name of the STK APP.

Furthermore, the STK APP can call a function for registering a broadcast receiver to complete the uninstall broadcast registration. The function for registering a broadcast receiver includes, for example, registerReceiver().

S302: Determine whether to uninstall the STK APP.

When the terminal device receives an operation triggered by the user to uninstall the STK APP, the terminal device may send an uninstall broadcast in response to the operation, wherein the uninstall broadcast may include the package name of the STK APP.

When the STK APP receives the uninstall broadcast sent by the terminal device, it can determine whether the package name carried in the uninstall broadcast is the package name corresponding to the STK APP.

If the STK APP determines that there is no package name corresponding to the STK APP in the uninstall broadcast, it is determined not to uninstall the STK APP.

If STK APP determines that the package name corresponding to STK APP is in the uninstall broadcast, STK APP is determined to be uninstalled, and STK APP can stop the components running in the Phone process, or deregister some components or callbacks registered in the Phone process, etc. It can also be understood as STK APP cleaning up the components running in the Phone process or some components or callbacks registered in the Phone process, etc.

The specific cleaning method may refer to the description of S303 below.

S303: Clean up components or callbacks.

For example, for the service component, when the STK APP determines that the application itself is uninstalled, the STK APP can determine whether the service is running. If the service is running, the STK APP can call a function to close the service component, such as the stopService() function, to stop the operation of the Service component and complete the memory release of the Service component.

For the broadcast receiver Receiver component, when the STK APP determines that the application itself is uninstalled, the STK APP can determine whether there is a registered broadcast receiver Receiver. If there is a registered broadcast receiver Receiver, the STK APP can call the function to register the broadcast receiver Receiver component, such as the unRegisterReceiver() function, to stop the operation of the Receiver component and complete the memory release of the Receiver component.

For the timed service callback AlarmManger.OnAlarmListener, when STK APP determines that the application itself is uninstalled, STK APP can determine whether there is a registered timed task callback AlarmManger.OnAlarmListener. If there is a registered timed task callback AlarmManger.OnAlarmListener in STK APP, STK APP can execute the function of deregistering the timed task callback AlarmManger.OnAlarmListener, such as the cancel() function, to complete the memory release of the timed task callback AlarmManger.OnAlarmListener.

For callbacks, when STK APP determines that the application itself is uninstalled, STK APP can determine whether there is a registered callback in the Phone process. If there is a registered callback in the Phone process, STK APP can call the function to register the callback to stop the callback from running and complete the memory release of the callback.

Exemplarily, Table 1 summarizes the cleaning solutions for the above-mentioned components or callbacks.

Table 1

In the embodiment of the present application, before the STK APP is uninstalled, the terminal device may first stop the operation of some components of the STK APP that cannot be deleted because they are running in the Phone process, or deregister some components or callbacks of the STK APP that cannot be deleted because they are registered in the Phone process, and then execute the uninstallation process. In this way, the STK APP memory can be cleaned up and the application uninstalled without the user's awareness, thereby improving the user experience.

It is understandable that when the STK APP is uninstalled, some components of the STK APP running in the Phone process will not be deleted, or some components or callbacks of the STK APP registered in the Phone process will not be deleted. These components or callbacks may call the application data of the deleted STK APP during the running of the Phone process, which may cause the Phone process to run incorrectly and crash. This can be recovered by restarting the Phone process. Because the STK APP has been uninstalled when the Phone process is restarted, the STK APP will not run in the Phone process, so the components of the STK APP will not run or the components or callbacks of the STK APP will not be registered in the Phone process, which will not cause the Phone process to run incorrectly and crash.

Therefore, when the STK APP is uninstalled, it can instruct the terminal device to restart the Phone process, so that the Phone process will not crash due to some components of the STK APP or some callbacks calling the application data of the deleted STK APP, and other related services in the Phone process (such as phone calls, text messages, Internet access, etc.) can run normally.

In addition, since restarting the Phone process may cause other related services (such as phone calls, text messages, Internet access, etc.) running in the Phone process to be unavailable for a short period of time, the user can perceive it. Therefore, when the STK APP instructs the terminal device to restart the Phone process, the terminal device can display a pop-up window to the user to prompt the possible impact of uninstalling the STK APP, and the user can decide whether to continue uninstalling the STK APP.

For example, Figure 4 provides a schematic diagram of an interface in which a terminal device displays a pop-up window for uninstalling an application when an STK APP is uninstalled. As shown in Figure 4, a pop-up window 401 may be displayed on the interface of the terminal device, and the pop-up window 401 may display an icon 402 of the STK APP, an uninstallation prompt title 403, uninstallation prompt information 404, an OK button 405, and a Cancel button 406.

Among them, the uninstall prompt title 403 may include "Do you want to uninstall the SIM card application?", and the uninstall prompt information 404 may include "This application is a system application. After uninstallation, it may cause calls, text messages, Internet access and other services to be temporarily unavailable." The specific content information of the uninstall prompt title 403 and the uninstall prompt information 404 is not limited in the embodiment of the present application. When the terminal device receives the operation of the user triggering the confirmation button 405, the terminal device can execute the process of uninstalling the application based on the STK APP. When the terminal device receives the operation of the user triggering the cancel button 406, the terminal device can cancel the display of the pop-up window 401 and does not execute the process of uninstalling the application.

Corresponding to the scenario of restarting the process after uninstalling the application shown in FIG4 , FIG5 is an exemplary flowchart of uninstalling the application provided by an embodiment of the present application. The specific steps may be:

S501: Receive an operation for triggering uninstallation of an application.

Exemplarily, the operation for triggering the uninstallation of an application may include: a user long pressing the application icon of the application on the desktop of the terminal device to trigger the operation of the uninstall button; it may also include: a user finding the application in the application management in the setting interface of the terminal device and triggering the operation of the uninstall button. The specific operation for uninstalling the application is not limited in the embodiments of the present application.

S504, the terminal device displays a pop-up window in the interface, which may include: a cancel button, an OK button, and information for prompting the user of possible impacts after uninstalling the application. Specifically, the pop-up window for uninstalling the application and the prompt information can be displayed with reference to the interface corresponding to FIG. 4, which will not be repeated here.

S505: When the terminal device receives the user's operation of triggering the cancel button, the terminal device may cancel the display of the pop-up window. Meanwhile, the terminal device may not need to execute the process of uninstalling the application.

S506: When the terminal device receives an operation of the user triggering a confirmation button, the terminal device may execute an uninstallation process.

Exemplarily, the uninstallation process may include deleting the installation files and application data corresponding to the application by calling a function for deleting the application in the package manager service (PMS), and clearing the system memory information of the terminal device.

S507: After the terminal device executes the uninstallation process, the terminal device may restart the process of the common process.

In a possible implementation of restarting a process, the terminal device may close the process based on a process closing function in the activity manager ActivityManager, and may start the process based on a process starting function.

S508: Complete uninstallation of the application.

The method for uninstalling an application provided in an embodiment of the present application can display a pop-up window to the user in the terminal device interface before the application is uninstalled, prompting the user of the impact of uninstalling the application and restarting the process that shares the same process with the application. This allows the operation of other services in the process that shares the same process with the application to be not affected when the application is uninstalled, thereby improving the user experience.

Optionally, S502 may be included between S501 and S504.

S502: Determine whether the application is a common process.

Before the application is uninstalled, the terminal device can determine whether the application is a co-process application. In one possible implementation, if the "android:process" attribute in the content corresponding to the application field in the application configuration file is configured with the identifier of other processes, it means that the application and other processes are co-processes. Exemplarily, taking the application as STKAPP as an example, if the "android:process" attribute in the content corresponding to the application field in the STK APP configuration file is configured as "android:process="com.android.Phone", it means that the STK APP and the Phone process are co-processes.

If the identifiers of other processes can be found in the configuration file of the application, it means that the application is a co-process application, and step S504 can be executed. If the identifiers of other processes are not found in the configuration file of the application, it means that the application is not a co-process application, and step S503 can be executed.

S503: If the application is not a co-process application, the terminal device may execute an uninstallation process of the application. The uninstallation process may refer to the description of S506 above, which will not be described in detail.

In this way, when the terminal device uninstalls the application, the terminal device can uninstall the application based on the uninstallation process of the embodiment of the present application. For example, the application can be a co-process application or a non-co-process application.

Specifically, FIG6 is a schematic diagram of a SIM card service processing method provided by an embodiment of the present application. The method includes:

S601: The terminal device receives an operation to uninstall a SIM card application.

In the embodiment of the present application, the operation of uninstalling the SIM card application may include: the user long presses the application icon of the SIM card application on the desktop of the terminal device to trigger the operation of the uninstall button; it may also include: the user finds the SIM card application in the application management of the setting interface of the terminal device and triggers the operation of the uninstall button. The specific operation of uninstalling the SIM card application is not limited in the embodiment of the present application.

S602. According to the operation of uninstalling the SIM card application received by the terminal device, at the first moment, the terminal device stops the components of the SIM card application running in the target process, and deregisters the components or registered callbacks of the SIM card application in the target process, where the target process is a process shared by the SIM card application and other applications.

In the embodiment of the present application, the first moment may be the moment when the terminal device cleans up components or callbacks of the SIM card application.

The specific execution process of the terminal device stopping the components of the SIM card application running in the target process, and deregistering the registered components or registered callbacks of the SIM card application in the target process can refer to the relevant description of the cleanup of components or callbacks in S303 in the embodiment corresponding to Figure 3 above, which will not be repeated here.

The target process may be a process corresponding to the execution of the SIM card application. For example, the SIM card application may be a common process with the Phone process, and the target process may be the Phone process.

S603: At a second moment, the terminal device uninstalls the SIM card application, and the second moment is later than the first moment.

In the embodiment of the present application, the second moment may be the moment when the terminal device uninstalls the SIM card application. It is understandable that the terminal device may execute the process of uninstalling the SIM card application only after executing the process of cleaning up the components or callbacks of the SIM card application in S602.

In the embodiment of the present application, before the SIM card application is uninstalled, the terminal device can first clean up the components or callbacks of the SIM card application, and then execute the uninstallation process. In this way, the SIM card application memory can be cleaned up and the application can be uninstalled without the user's awareness, thereby improving the user experience.

Optionally, based on the embodiment corresponding to Figure 6, the component of the SIM card application running in the target process may include a service component; the component registered by the SIM card application in the target process may include a Receiver component; the callback registered by the SIM card application in the target process may include a timer service callback AlarmManger.OnAlarmListener, and/or callback.

In the embodiment of the present application, when uninstalling the SIM card application, the terminal device cannot delete the components running in the target process, or the registered components or callbacks of the SIM card application, so these components or callbacks need to be processed separately to ensure the normal operation of the target process.

Optionally, based on the embodiment corresponding to FIG. 6 , the terminal device stops the component of the SIM card application running in the target process, which may include: the terminal device calls a function of closing the service component.

In the embodiment of the present application, the terminal device can determine whether the service Service is running. If the service Service is running, the terminal device can call a function to close the service Service component. The function can refer to the relevant description of S303 in the embodiment corresponding to Figure 3. The specific method of closing the service Service component is not limited in the embodiment of the present application.

Before uninstalling the SIM card application, the terminal device can shut down the running service component to enable the target process to run normally, thereby not affecting other services in the target process.

Optionally, based on the embodiment corresponding to FIG. 6 , the terminal device deregistering the component of the SIM card application that has been registered in the target process may include: the terminal device calling a function to deregister the broadcast receiver Receiver component.

In the embodiment of the present application, the terminal device can determine whether there is a registered broadcast receiver Receiver. If there is a registered broadcast receiver Receiver, the terminal device can call a function to deregister the broadcast receiver Receiver component. The function can refer to the relevant description of S303 in the embodiment corresponding to Figure 3. The specific method of deregistering the broadcast receiver Receiver component is not limited in the embodiment of the present application.

Before uninstalling the SIM card application, the terminal device can register the broadcast receiver Receiver component to enable the target process to run normally without affecting other services in the target process.

Optionally, based on the embodiment corresponding to Figure 6, the terminal device deregisters the callback registered by the SIM card application in the target process, which may include: the terminal device calls the function to register the scheduled task callback AlarmManger.OnAlarmListener; and/or the terminal device calls the function to register the callback callback.

In the embodiment of the present application, the terminal device can determine whether there is a registered timed task callback AlarmManger.OnAlarmListener. If there is a registered timed task callback AlarmManger.OnAlarmListener in the terminal device, the terminal device can execute a function to deregister the timed task callback AlarmManger.OnAlarmListener. Alternatively, the terminal device can determine whether there is a registered callback callback. If there is a registered callback callback in the terminal device, the terminal device can execute a function to deregister the callback callback.

Among them, the function of deregistering the scheduled task callback AlarmManger.OnAlarmListener or the function of deregistering the callback callback can refer to the relevant description of S303 in the embodiment corresponding to Figure 3. The specific method of deregistering the scheduled task callback AlarmManger.OnAlarmListener or the method of deregistering the callback callback function is not limited in the embodiments of this application.

Before uninstalling the SIM card application, the terminal device can enable the target process to run normally by registering the scheduled task callback AlarmManger.OnAlarmListener or registering the callback callback, so as not to affect other services in the target process.

Optionally, based on the embodiment corresponding to FIG. 6 , before the terminal device receives the operation of uninstalling the SIM card application, the method may further include: the terminal device registers an uninstall broadcast for the SIM card application.

According to the operation of uninstalling the SIM card application received by the terminal device, at the first moment, the terminal device stops the components of the SIM card application running in the target process, and de-registers the components or callbacks of the SIM card application registered in the target process, which may include: according to the operation, the terminal device sends an uninstall broadcast, and the uninstall broadcast may include the identifier of the SIM card application; when the terminal device determines through the SIM card application that the uninstall broadcast includes the identifier of the SIM card application, at the first moment, the terminal device stops the components of the SIM card application running in the target process, and de-registers the components or callbacks of the SIM card application registered in the target process.

In an embodiment of the present application, when a user triggers an operation to uninstall an application, the terminal device may send an uninstall broadcast. It is understandable that the application that the user triggers to uninstall may be a SIM card application, or may be another third-party application or a system application, which is not limited in the embodiment of the present application. When a user triggers an operation to uninstall a SIM card application, the uninstall broadcast sent by the terminal device may include an identifier of the SIM card application, for example, the uninstall broadcast may include the package name of the SIM card application.

The process of determining that the uninstall broadcast includes the identification of the SIM card application can refer to the relevant description of S302 in the embodiment corresponding to Figure 3, which will not be repeated here. When the user triggers the operation of uninstalling the application, the terminal device sends the uninstall broadcast so that the application or module registered for the uninstall broadcast can receive the uninstall broadcast, so that the related application or module can perform the operation of uninstalling the application after receiving the uninstall broadcast.

Optionally, based on the embodiment corresponding to FIG. 6 , the terminal device registers an uninstall broadcast for the SIM card application, which may include: the terminal device adds a field Intent.ACTION_PACKAGE_REMOVED corresponding to the uninstall broadcast to the intent filter IntentFilter, and adds an identifier of the SIM card application.

In the embodiment of the present application, the process of registering uninstall broadcast can refer to the relevant description of S301 in the embodiment corresponding to Figure 3, which will not be repeated. By registering uninstall broadcast for SIM card application, the terminal device can conveniently receive the uninstall broadcast of uninstalling SIM card application and further execute the relevant uninstall process.

Optionally, based on the embodiment corresponding to FIG. 6 , the target process may include a Phone process.

In the embodiment of the present application, the Phone process is a system process in the terminal device. The Phone process can continue to run after the terminal device is turned on. The SIM card application and the Phone process share the same process, which can enable SIM-related services to operate normally and provide users with SIM-related services.

Specifically, FIG7 is a schematic diagram of another SIM card service processing provided by an embodiment of the present application. The method may include:

S701: The terminal device receives an operation to uninstall a SIM card application.

In the embodiment of the present application, the operation of receiving the uninstallation of the SIM card application can refer to the relevant description of S601 in the embodiment corresponding to FIG. 6 above, and will not be repeated here.

S702: At the third moment, the terminal device uninstalls the SIM card application.

In the embodiment of the present application, the third moment may be the moment when the terminal device uninstalls the SIM card application. It is understandable that after receiving the operation of uninstalling the SIM card application, the terminal device may execute the process of uninstalling the SIM card application, so that after the terminal device responds to the user's operation of uninstalling the application, the terminal device memory can be cleaned up in time.

S703. At a fourth moment, the terminal device restarts the target process, where the target process is a process shared by the SIM card application and other applications. The fourth moment is later than the third moment.

In the embodiment of the present application, the fourth moment may be the moment when the terminal device restarts the target process, that is, the fourth moment may be the moment when the terminal device executes the process of uninstalling the SIM card application and restarts the process that is a common process with the SIM card application. Restarting the process that is a common process with the SIM card application can make the process no longer load the relevant data of the SIM card application, so that other services in the process can run normally.

Optionally, based on the embodiment corresponding to FIG. 7 , before the terminal device uninstalls the SIM card application, the process may further include: the terminal device displays a pop-up window including a confirmation button, a cancel button, and prompt information for prompting the risks of uninstalling the SIM card application.

The terminal device uninstalling the SIM card application may include: in response to an operation on a confirmation button, the terminal device uninstalling the SIM card application.

In the embodiment of the present application, the pop-up window displayed by the terminal device can refer to the pop-up window shown in FIG. 4, which will not be described in detail. When the user triggers the OK button, it means that the user chooses to uninstall the SIM card application, and the terminal device can execute the process of uninstalling the SIM card application. During the uninstallation process, the terminal device prompts the user with a pop-up window to remind the user of the risks of uninstalling the SIM card application, so that the user can understand the unknown risks in time and improve the user experience.

Optionally, based on the embodiment corresponding to FIG. 7 , before the terminal device displays the pop-up window, the method may further include: the terminal device determines that the SIM card application is a co-process application through a configuration file of the SIM card application.

In the embodiment of the present application, the terminal device can determine whether the SIM card application is a co-process application through the configuration file of the SIM card application by referring to the relevant description of S502 in the embodiment corresponding to FIG. 5 above, and will not be repeated here. Specifically, the method for the terminal device to determine whether the application is a co-process application is not limited in the embodiment of the present application.

When the terminal device determines that the process corresponding to the uninstalled application is shared with other processes, it can restart the process so that the process no longer loads the relevant data of the uninstalled application, so that other services in the process can run normally.

Optionally, based on the embodiment corresponding to FIG. 7 , the target process includes a Phone process.

In the embodiment of the present application, the Phone process is a system process in the terminal device. The Phone process can continue to run after the terminal device is turned on. The SIM card application and the Phone process share the same process, which can enable SIM-related services to operate normally and provide users with SIM-related services.

The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. In order to realize the above functions, it includes hardware structures and/or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the method steps of each example described in the embodiment disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.

The embodiment of the present application can divide the functional modules of the device for implementing the method of uninstalling the application according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

FIG8 is a schematic diagram of the structure of a chip provided in an embodiment of the present application. The chip 800 includes one or more (including two) processors 801 , a communication line 802 , a communication interface 803 and a memory 804 .

In some implementations, the memory 804 stores the following elements: executable modules or data structures, or a subset thereof, or an extended set thereof.

The method described in the above embodiment of the present application can be applied to the processor 801, or implemented by the processor 801. The processor 801 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware or software instructions in the processor 801. The above processor 801 can be a general processor (for example, a microprocessor or a conventional processor), a digital signal processor (digital signal processing, DSP), an application specific integrated circuit (application specific integrated circuit, ASIC), a field-programmable gate array (field-programmable gate array, FPGA) or other programmable logic devices, discrete gates, transistor logic devices or discrete hardware components. The processor 801 can implement or execute the methods, steps and logic block diagrams related to each processing disclosed in the embodiment of the present application.

The steps of the method disclosed in the embodiment of the present application can be directly embodied as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. Among them, the software module can be located in a mature storage medium in the field such as a random access memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable read only memory (EEPROM). The storage medium is located in the memory 804, and the processor 801 reads the information in the memory 804 and completes the steps of the above method in combination with its hardware.

The processor 801 , the memory 804 , and the communication interface 803 may communicate with each other via the communication line 802 .

In the above embodiments, the instructions stored in the memory for execution by the processor may be implemented in the form of a computer program product, wherein the computer program product may be pre-written in the memory, or may be downloaded and installed in the memory in the form of software.

The present application embodiment also provides a computer program product including one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a server or data center that includes one or more available media integrated. For example, the available medium may include a magnetic medium (e.g., a floppy disk, a hard disk or a tape), an optical medium (e.g., a digital versatile disc (DVD)), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.

The embodiments of the present application also provide a computer-readable storage medium. The methods described in the above embodiments can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. Computer-readable media may include computer storage media and communication media, and may also include any medium that can transfer a computer program from one place to another. The storage medium may be any target medium that can be accessed by a computer.

As a possible design, the computer readable medium may include a compact disc read-only memory (CD-ROM), RAM, ROM, EEPROM or other optical disc storage; the computer readable medium may include a magnetic disk storage or other magnetic disk storage device. Moreover, any connection line may also be appropriately referred to as a computer readable medium. For example, if the software is transmitted from a website, server or other remote source using a coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology (such as infrared, radio and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while optical discs reproduce data optically using lasers.

The present application embodiment is described with reference to the flowchart and/or block diagram of the method, device (system) and computer program product according to the embodiment of the present application. It should be understood that each process and/or box in the flowchart and/or block diagram, and the combination of the process and/or box in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions can be provided to the processing unit of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processing unit of the computer or other programmable data processing device produce a device for realizing the function specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.

Claims (14)

1. A method of offloading an application, the method comprising:

the terminal equipment receives an operation of uninstalling the SIM card application;

According to the operation, at a first moment, stopping a component operated by the SIM card application in a target process by the terminal equipment, and registering a registered component or a registered callback of the SIM card application in the target process, wherein the target process is a process of the SIM card application and other applications in a co-process manner;

And unloading the SIM card application by the terminal equipment at a second moment, wherein the second moment is later than the first moment.

2. The method of claim 1, wherein the components of the SIM card application running in the target process comprise a Service component; the registered components of the SIM card application in the target process comprise a Receiver component; the registered callbacks of the SIM card application in the target process comprise a timing service callback AlarmManger.OnAlarmListener and/or a callback.

3. The method according to claim 2, wherein the terminal device stops components of the SIM card application running in the target process, comprising:

The terminal device invokes a function that closes the Service component.

4. A method according to claim 2 or 3, wherein the terminal device de-registering components of the SIM card application registered in the target process, comprising:

the terminal device invokes a function to register a Receiver component of the broadcast Receiver.

5. A method according to claim 2 or 3, wherein the terminal device de-registering a callback registered by the SIM card application in the target process, comprising:

The terminal equipment calls a function of a deregistering timing task callback AlarmManger. OnAlarmListener;

And/or the terminal equipment calls a function for registering callback.

6. A method according to any of claims 1-3, characterized in that the terminal device, before receiving the operation of uninstalling the SIM card application, further comprises: the terminal equipment registers and uninstalls broadcasting for the SIM card application;

According to the operation, at a first moment, the terminal device stops a component of the SIM card application running in a target process, and registers a registered component or callback of the SIM card application in the target process, including:

According to the operation, the terminal equipment sends an unloading broadcast, wherein the unloading broadcast comprises an identifier of the SIM card application;

When the terminal device determines that the uninstallation broadcast comprises the identification of the SIM card application through the SIM card application, the terminal device stops a component of the SIM card application running in the target process and registers a registered component or callback of the SIM card application in the target process at the first moment.

7. The method of claim 6, wherein the terminal device registering for offloading broadcasts for the SIM card application, comprising:

the terminal device adds a field Intent. Action_ PACKAGE _REMOVED corresponding to the uninstalled broadcast to the intention filter INTENTFILTER, and adds an identifier of the SIM card application.

8. A method according to any of claims 1-3, wherein the target process comprises a Phone process.

9. A method according to any one of claims 1-3, wherein the method further comprises:

And restarting the target process by the terminal equipment at a fourth time, wherein the fourth time is later than the second time.

10. The method of claim 9, wherein before the terminal device uninstalls the SIM card application, further comprising:

the terminal equipment displays a popup window, wherein the popup window comprises a determination button, a cancel button and prompt information for prompting the risk existing in the process of unloading the SIM card application;

The terminal device uninstalling the SIM card application comprises: and responding to the operation of the determination button, and unloading the SIM card application by the terminal equipment.

11. The method of claim 10, wherein before the terminal device displays the popup window, further comprising:

and the terminal equipment judges that the SIM card application is a co-process application through the configuration file of the SIM card application.

12. A terminal device, comprising: memory for storing a computer program, and a processor for executing the computer program to perform the method of uninstalling an application as claimed in any of claims 1-11.

13. A computer readable storage medium storing instructions that, when executed, cause a computer to perform the method of offloading an application of any one of claims 1-11.

14. A computer program product comprising a computer program which, when run, causes an electronic device to perform the method of uninstalling an application as claimed in any one of claims 1-11.