Interface display method, device, equipment, storage medium and program product

Abstract

Embodiments of the present application disclose an interface display method and device, equipment, a storage medium and a program product, and belong to the field of electronic equipment. The method comprises the following steps: in response to a list starting operation, a first system displays an application list interface, and the application list interface comprises applications running by the first system and a second system; in response to a selection operation on a first application in the application list interface, the first system sends an application starting message to the second system, the first application is an application running by the second system; and the second system starts the first application based on the application starting message and displays an application interface. The scheme provided by the embodiments of the present application can help to reduce the switching frequency between systems and avoid the increase of device power consumption caused by frequent system switching.

Description

Technical Field

[0001] This application relates to the field of electronic devices, and in particular to an interface display method, apparatus, device, storage medium, and program product. Background Technology

[0002] With the continuous development of science and technology, more and more electronic devices with different functions have emerged, bringing many changes to users' daily lives.

[0003] Besides simple functions like telling time and setting alarms, electronic devices can also perform more complex functions through installed applications. For example, users can use instant messaging applications to communicate instantly or use sleep monitoring applications to monitor sleep quality in real time. Summary of the Invention

[0004] This application provides an interface display method, apparatus, device, storage medium, and program product. The technical solution is as follows:

[0005] On one hand, embodiments of this application provide an interface display method, the method being used in an electronic device, the electronic device supporting the operation of a first system and a second system;

[0006] The method includes:

[0007] In response to the list launch operation, the first system displays an application list interface, which contains applications running by the first system and the second system.

[0008] In response to the selection of a first application in the application list interface, the first system sends an application launch message to the second system, wherein the first application is an application run by the second system;

[0009] The second system launches the first application and displays the application interface based on the application launch message.

[0010] On the other hand, embodiments of this application provide an interface display device for use in an electronic device, wherein the electronic device supports the operation of a first system and a second system;

[0011] The device includes:

[0012] The first system module is also configured to display an application list interface in response to a list launch operation, the application list interface containing applications run by the first system and the second system;

[0013] The first system module is further configured to send an application launch message to the second system module in response to a selection operation of the first application in the application list interface, wherein the first application is an application run by the second system.

[0014] The second system module is used to launch the first application and display the application interface based on the application launch message.

[0015] On the other hand, embodiments of this application provide an electronic device, which includes a processor and a memory; the processor includes at least a first processor and a second processor, the power consumption of the second processor is higher than that of the first processor, and the memory stores at least one instruction, which is executed by the processor to implement the interface display method described above.

[0016] On the other hand, embodiments of this application provide a computer-readable storage medium storing at least one instruction, which is executed by a processor to implement the interface display method as described above.

[0017] On the other hand, embodiments of this application provide a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the interface display method provided above.

[0018] For electronic devices that support dual systems, since users can launch applications running on either the first or second system through the application list interface, in this embodiment, the application list interface is displayed through the first system, and when a selection operation for an application running on the second system is received, the system switches to the second system to launch the application and display the application interface. This avoids the need to switch from the first system to the second system when displaying the application list interface, which helps to reduce the switching frequency between systems and avoids increased device power consumption due to frequent system switching. Attached Figure Description

[0019] Figure 1 This is a schematic diagram illustrating a dual-core communication software framework corresponding to a second processor, as shown in an exemplary embodiment of this application;

[0020] Figure 2 This is a schematic diagram illustrating a dual-core communication software framework corresponding to a first processor, as shown in an exemplary embodiment of this application;

[0021] Figure 3 A flowchart illustrating an exemplary embodiment of the present application shows a method for displaying an interface.

[0022] Figure 4 This is a schematic diagram of the interface switching process in a smartwatch, as illustrated in an exemplary embodiment of this application.

[0023] Figure 5 This is a schematic diagram of the interface illustrating the application layout editing process in an exemplary embodiment of this application;

[0024] Figure 6 This is a schematic diagram of the interface illustrating the application deletion process in an exemplary embodiment of this application;

[0025] Figure 7 This is a sequence diagram illustrating the interaction between systems during the application uninstallation process, as shown in an exemplary embodiment of this application.

[0026] Figure 8 This is a sequence diagram illustrating the interaction between systems during the application installation process, as shown in an exemplary embodiment of this application.

[0027] Figure 9 This is a timing diagram illustrating the interaction between systems under the first return operation, as shown in an exemplary embodiment of this application.

[0028] Figure 10 This is a timing diagram illustrating the interaction between systems under a second return operation, as shown in an exemplary embodiment of this application.

[0029] Figure 11 A structural block diagram of an interface display device provided in another embodiment of this application is shown;

[0030] Figure 12 A structural block diagram of an electronic device provided in an exemplary embodiment of this application is shown. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0032] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0033] In related technologies, electronic devices typically incorporate a single processor, which, through an operating system running on that processor, processes all system events generated during device operation. Therefore, this processor needs strong data processing capabilities and must remain operational throughout the device's lifespan. However, in everyday use, electronic devices often only require functions with low processing power demands. For example, smartwatches and smart bracelets primarily only need to display the time and provide notifications. Therefore, keeping the processor constantly active does not improve the performance of the electronic device; instead, it increases power consumption, resulting in shorter battery life (especially noticeable in wearable devices with smaller battery capacities).

[0034] In order to reduce the power consumption of electronic devices while ensuring their performance, in one possible implementation, the electronic device is equipped with at least a first processor and a second processor with different processing performance and power consumption, which are used to run the first system and the second system respectively (i.e., dual-core dual system), and a system switching mechanism is designed for the dual-core dual system.

[0035] During the operation of an electronic device, a first system running on a low-power processor handles events requiring low performance processing while keeping the high-power processor in a sleep state (correspondingly, the second system running on the high-power processor is also in a sleep state). This sleep state reduces the power consumption of the electronic device while fulfilling its basic functions. When an event requiring high performance processing occurs (such as when an application is launched), the high-power processor is woken up, and the second system is switched to handle the event, ensuring that the triggered event can be responded to and processed in a timely manner to meet the performance requirements of the electronic device.

[0036] To avoid frequent switching between systems, in this embodiment, the first system, in addition to displaying the main system interface and the applications running on the first system, is also responsible for displaying the application list interface. When a user selects an application running on the first system through the application list interface, the electronic device does not need to switch systems; instead, it continues to launch the application and display the application interface through the first system. When a user selects an application running on the second system through the application list interface, the first system sends an application launch message to the second system and switches to the second system to launch the application and display the application interface.

[0037] Since users can launch applications running on either the first or second system through the application list interface, having the application list interface displayed on the first system ensures that applications running on the second system can be launched normally, while avoiding the problem of frequent switching between systems caused by users having to switch to the second system to launch applications running on the first system. This also helps reduce the power consumption of electronic devices.

[0038] In this embodiment, the first processor and the second processor operate asynchronously, and the first system and the second system need to achieve system communication (or dual-core communication). In one possible application scenario, the first system is a real-time operating system (RTOS) running on a microcontroller unit (MCU), and the second system is an Android operating system running on a central processing unit (CPU).

[0039] like Figure 1 As shown, this application illustrates a dual-core communication software framework for the Android operating system, as illustrated in an exemplary embodiment. This dual-core communication software framework follows the design principles of "low coupling, high reliability, and high reusability," and includes module development for the Kernel, HIDL (Hardware Abstraction Layer Interface Description Language), Native Service, Framework Service, Framework API, and APP (Application) components.

[0040] The APP module includes functional modules such as Launcher, Settings, and SystemUI; the Framework API module includes management modules such as MCUManager, SensorManager, and LocationManager; the Framework Service module includes service modules such as MCUManagerService, SystemSensorManager, and LocationManagerService; the Native Service module includes service modules such as dccservice and Sensorservice; the HIDL module includes modules such as SensorHAL and GPS HAL; and the Kernel module includes DCC Transfer Drivers such as dcc_data, MCU_sensor, and MCU_gps.

[0041] As the interface layer connecting the upper and lower layers in the dual-core communication software framework, the transport layer shields the application layer from the transmission details of the lower layer (data link layer) of the system, providing a service channel for application scenarios. The application layer, as the main provider of services, responds to human-computer interaction and transmits the data generated during the human-computer interaction process through the transport layer, as well as responding to external data requests.

[0042] RTOS is designed using the peer-to-peer principle. Taking a smartwatch as an example, such as... Figure 2 As shown, it illustrates a dual-core communication software framework for an RTOS according to an exemplary embodiment of this application.

[0043] The dual-core communication software framework of RTOS is divided into the Application Layer, Service Layer, Framework Layer, Hardware Abstraction Layer, and Platform Layer.

[0044] The application layer includes modules such as watch face, Daily Tracker, Messagecenter, Voice around Apps, Health Apps, and Settings; the service layer includes modules such as Sport & Health task, System manager task, AMS (Activity Management Service), Audio Service, Log Service, OFTP Service (Odette File Transfer Protocol Service), BT Service, Delegate Service, RPC Service, Sensor Service, and Storage Service; the framework layer includes modules such as Message Pub, UIFramework, G2D Engine, Audio Middleware, Preference, and File. The framework modules include system (file system), Algorithms, and AsyncEvent (in-process asynchronous events); the hardware abstraction layer includes hardware abstraction modules such as Screen / TP (screen / touchscreen) and sensors; the platform layer includes Board Support Package (BSP) and Low-level Driver. The BSP includes Screen / TP, Codec (encoder / decoder), sensors, Flash, PSRAM (pseudo-static random access memory), etc., while the Low-level Driver includes UART (Universal Asynchronous Receiver / Transmitter), ADC (Analog-to-Digital Converter), GPIO (General Purpose Input / Output), SPI (Serial Peripheral Interface), I2C (Integrated Circuit Bus), IOS (Input / Output System), PCM (Pulse Code Modulation), I2S (Integrated Audio Bus), and HWTimer (Hardware Timer).

[0045] It should be noted that the above dual-core communication software framework is for illustrative purposes only. Those skilled in the art can add, delete or modify the framework according to actual needs. The embodiments of this application do not limit the specific structure of the dual-core communication software framework.

[0046] Please refer to Figure 3The diagram illustrates a flowchart of an interface display method provided in an exemplary embodiment of this application. This embodiment uses the application of the method to an electronic device, where the electronic device supports running a first system and a second system, as an example for illustration. The method may include the following steps.

[0047] Step 301: In response to the list launch operation, the first system displays an application list interface, which contains applications running by the first system and the second system.

[0048] In some embodiments, the power consumption of the first system is lower than that of the second system, so the electronic device tends to keep the first system in a wake-up state for a long time, while the second system only switches to a wake-up state when processing specific tasks.

[0049] In one possible implementation, the electronic device includes a first processor and a second processor, wherein the processing performance of the first processor is lower than that of the second processor (both the processing power and speed of the first processor are lower than those of the second processor), and the power consumption of the first processor is lower than that of the second processor. Accordingly, the second system (run by the second processor) is capable of processing events processed by the first system (run by the first processor), but the first system may not necessarily be capable of processing events processed by the second system.

[0050] In another possible implementation, the electronic device may also be equipped with a single processor, with the first system and the second system running on different cores of the processor, wherein the core running the second system has higher processing performance than the core running the first system.

[0051] For example, taking a smartwatch as an electronic device, the first processor is an MCU, the second processor is a CPU, the first system is an RTOS, and the second system is an Android system. Correspondingly, the events that the first system can handle include scenarios with low processing performance requirements or weak interaction scenarios such as watch face display, watch face interface switching, and notification message display; the events that the second system can handle include scenarios with high processing performance requirements or strong interaction scenarios such as answering calls, replying to messages, watch face editing, and function settings.

[0052] In one possible implementation, the operating modes of the electronic device include a performance mode, a hybrid mode, and a low-power mode. In the performance mode, both the second processor and the first processor remain awake (correspondingly, both the first system and the second system are awake). In the low-power mode, only the first processor remains awake, while the second processor remains off (i.e., the first system is awake and the second system is off). In the hybrid mode, when events are processed through the first system, the second processor is in standby mode and can switch between sleep and wake states (i.e., when the first system is awake, the second system can be either awake or sleep).

[0053] Optionally, in the wake-up state, system-related data is cached in memory (RAM) for easy access. In the hibernation state, most of the processor's hardware modules are shut down, and system-related data is stored in the hard disk (ROM), which is then written into memory when switching to the wake-up state.

[0054] Unlike smartphones and other electronic devices with strong interactive attributes, wearable devices, as auxiliary electronic devices, have only weak interactions with users in most usage scenarios. For example, in most situations, users only use smartwatches to raise their wrists to check the time. Therefore, when the wearable device processes events through the first system, it controls the second processor to be in a sleep state (the second system is in a sleep state), thereby reducing the overall power consumption of the wearable device. For ease of explanation, the following embodiments use wearable devices as an example.

[0055] The application list interface serves as an entry point for users to launch applications and is frequently used during the operation of electronic devices. To reduce the power consumption of electronic devices, in this embodiment, the application list interface is rendered and displayed by a first system. In addition to displaying the application list interface, the first system is also responsible for displaying its main system interface and the application interfaces of the applications running on the first system. When the electronic device is a smartwatch, the main system interface can be a watch face.

[0056] Optionally, if a list launch operation is received while the first system is displaying the main system interface, the first system will switch the main system interface to the application list interface; if a list launch operation is received while the first system is running an application, the first system will switch the currently displayed application interface to the application list interface.

[0057] Optionally, if a list launch operation is received during the operation of the application in the second system, the second system switches to the first system, and the first system displays the application list interface.

[0058] The list activation operation can be a touch operation (operating on the touch screen of an electronic device), a button operation (pressing the physical button of an electronic device), a voice operation, etc., and this application embodiment does not limit it.

[0059] Optionally, applications in the application list interface may be displayed as icons and / or text, but this embodiment does not limit this.

[0060] Indicative, such as Figure 4 As shown, taking a smartwatch as an example, the first system currently displays the watch face interface 41. When a press operation on the crown is received, the first system switches the watch face interface 41 to the application list interface 42, which displays the application icons of various applications.

[0061] Step 302: In response to the selection of the first application in the application list interface, the first system sends an application launch message to the second system. The first application is an application run by the second system.

[0062] For each application displayed in the application list interface, the user can trigger the application launch by selecting an operation, which can be a click operation, a long press operation, a press operation, etc. This embodiment does not limit this.

[0063] Since the application selected by the user may be run by either the first system or the second system, the first system needs to determine which system the selected application should run on. In one possible implementation, when it is determined that the selected first application is run by the second system, the first system sends an application startup message to the second system, thereby instructing the second system to perform a system switch and run the first application.

[0064] In order to enable the first system to distinguish between applications run by the first system and applications run by the second system, in one possible implementation, each application in the application list interface is provided with a corresponding running system identifier, which is used to characterize the system running the application.

[0065] In response to the selection of the first application in the application list interface, the first system obtains the running system identifier corresponding to the first application. The running system identifier is used to identify the system running the application. If the running system identifier indicates that the first application is run by the second system, the first system sends an application startup message to the second system.

[0066] Optionally, the operating system identifier is set by the first system or the second system and stored in the storage space of the first system.

[0067] In one possible implementation, the first system sends an application startup message to the second system via dual-core communication. This application startup message includes at least the application startup data of the first application. For example, the application startup data could be the application package name of the first application.

[0068] It should be noted that if the second system is in a dormant state, the first system needs to wake up the second system first. The first system can wake up the second system by sending an interrupt, but this embodiment does not limit this.

[0069] Step 303: The second system launches the first application based on the application startup message and displays the application interface.

[0070] In the wake-up state, the second system determines the first application to be launched based on the application launch message, and then launches the first application and displays its application interface.

[0071] In one possible implementation, since the screen control permissions of the electronic device are located in the first system when displaying the application list interface, the second system first needs to obtain screen control permissions from the first system, and then display the application interface of the first application through the screen after obtaining screen control permissions.

[0072] Indicative, such as Figure 4 As shown, when a click operation is received on the weather application 421 in the application list interface 42, since the weather application 421 is an application running on the second system, the first system sends an application launch message to the second system. The second system launches the weather application 421 based on the application launch message and displays the weather application interface 43.

[0073] In some embodiments, the application list interface includes a fourth application running by the first system. In response to the selection operation of the fourth application in the application list interface, the first system launches the fourth application and displays the application interface without the need for system switching.

[0074] Indicative, such as Figure 4 As shown, when a click operation is received on the heart rate application 422 in the application list interface 42, since the heart rate application 422 is an application run by the first system, the first system starts the heart rate application 422 and displays the heart rate measurement interface 44.

[0075] In summary, for electronic devices that support dual systems, since users can launch applications running on either the first or second system through the application list interface, in this embodiment, the application list interface is displayed through the first system, and when a selection operation for an application running on the second system is received, the system switches to the second system to launch the application and display its interface. This avoids the need to switch from the first to the second system when displaying the application list interface, which helps reduce the frequency of system switching and prevents increased device power consumption caused by frequent system switching.

[0076] When the first system is used to display the main system interface, application interface (applications run by the first system), and application list interface, and the second system is used to display the application interface (applications run by the second system), the system status of each system during interface switching may include the following:

[0077] 1. When an electronic device changes from a screen-off state to a screen-on state, the first system controls the screen to display the system's main interface, while the second system enters a sleep state.

[0078] 2. When a main interface switching operation is received, the first system switches the main interface (e.g., switches the watch face of the smartwatch), while the second system enters a sleep state.

[0079] 3. The first system controls the screen to display the application interface. When the main interface startup operation is received, the first system controls the screen to display the system main interface, and the second system is in sleep mode.

[0080] 4. The second system controls the screen to display the application interface. When the main interface is activated, the first system controls the screen to display the system's main interface, and the second system switches to sleep mode.

[0081] 5. The first system controls the screen to display the main interface of the system. When a startup operation or a list startup operation is received for an application under the first system, the first system controls the screen to display the application interface or application list interface, and the second system is in a sleep state.

[0082] 6. The first system controls the screen to display the system's main interface. When it receives a startup operation for an application under the second system, the first system wakes up the second system, and the second system controls the screen to display the application interface.

[0083] 7. The first system displays the main system interface. When a list launch operation is received, the first system displays the application list interface, while the second system is in sleep mode.

[0084] 8. The first system controls the screen to display the application interface. When a list start operation is received, the first system controls the screen to display the application list interface, and the second system is in sleep mode.

[0085] 9. The second system controls the screen to display the application interface. When a list start operation is received, the second system switches to the first system. The first system controls the screen to display the application list interface, and the second system switches to sleep mode.

[0086] 10. The first system controls the screen to display the application list interface. When a startup operation is received for an application under the first system, the first system controls the screen to display the application interface, and the second system is in a sleep state.

[0087] 11. The first system controls the screen to display the application list interface. When it receives a startup operation for an application under the second system, the first system wakes up the second system, and the second system controls the screen to display the application interface.

[0088] As can be seen from the above, the second system will only be woken up and the application will be launched by the first system when the application of the second system needs to be launched. This increases the proportion of the first system's runtime during the operation of the electronic device, which helps to reduce the device's power consumption and avoids frequent switching between systems.

[0089] In one possible implementation, during the process of displaying the application list, the first system obtains the application identifier and application layout information of at least one stored application, and then displays the application list interface based on the application identifier and application layout information, wherein the application layout information is used to characterize the layout of each application identifier in the application list interface.

[0090] Optionally, the application identifier and application layout information are stored in the storage space corresponding to the first system and maintained and updated by the first system.

[0091] Optionally, the application identifier may include the application icon, application name, etc., but this embodiment does not limit this.

[0092] Optionally, the application layout information includes the display position and size of the application icon in the application list, the font and size of the application name, etc. This embodiment does not limit the specific content included in the application layout information.

[0093] When using electronic devices, users can adjust the layout of applications in the application list interface according to their own needs, such as adjusting the display position of applications in the application list interface, pinning frequently used applications to the top of the list, etc.

[0094] In one possible implementation, in response to a layout editing operation on a second application in the application list interface, the first system updates the application list interface, wherein the second application is an application run by either the first or second system. Furthermore, since the applications included in the application list interface do not change after the layout editing operation, the first system only needs to update the application layout information.

[0095] Optionally, the layout editing operation includes icon movement operation (such as long-pressing and dragging the application icon), pinning operation (such as long-pressing the application icon to bring up the editing menu and clicking the pinning option in the editing menu), etc. The embodiments of this application do not limit the specific method of layout editing operation.

[0096] Indicative, such as Figure 5 As shown, the first system displays an application list interface 51. When a long press and drag operation is received on the clock application icon 511, and the end point of the long press and drag operation is located at the heart rate application icon 512, the first system swaps the display positions of the clock application icon 511 and the heart rate application icon 512 in the application list interface 51, and updates the corresponding layout information of the clock application icon 511 and the heart rate application icon 512 in the application layout information.

[0097] In addition to editing the layout of applications in the application list interface, users can also uninstall applications from the application list interface as needed. In one possible implementation, in response to an uninstallation operation of a third application from the application list interface, the first system updates the application list interface; the third application is an application run by the first system or the second system.

[0098] Since the applications listed in the application list change after a deletion, the first system needs to update the stored application identifiers and application layout information. Optionally, the first system deletes the application identifier corresponding to the third application and updates the application layout information.

[0099] Indicative, such as Figure 6 As shown, the first system displays an application list interface 61. When a long press operation is received on the sleep application icon 611, a delete control is displayed in the upper right corner of the sleep application icon 611. When a click operation is received on the delete control, the first system deletes the sleep application icon 611 from the application list interface 61, and deletes the application identifier and layout information corresponding to the sleep application.

[0100] In one possible implementation, when the first system receives an uninstallation operation for the third application, it determines the system running the third application based on the running system identifier corresponding to the third application. When the third application is run by the first system, the first system deletes the application data of the third application, thereby freeing up the storage space of the first system.

[0101] When the third application is run by the second system, since the relevant data of the third application is stored in the storage space of the second system, the first system also needs to notify the second system to uninstall the third application (the first system only deletes the application icon in the application list interface).

[0102] In one possible implementation, if the third application is run by the second system, the first system sends an application uninstallation message to the second system, and the second system uninstalls the third application based on the application uninstallation message. Optionally, the application uninstallation message includes the application identifier of the third application.

[0103] Regarding the timing of the first system sending the application uninstallation message, in some embodiments, when the first system receives the uninstallation operation and the second system is in a woken-up state, the first system sends the application uninstallation message to the second system (after receiving the application uninstallation message, the second system uninstalls the application in the background, while the screen display is still controlled by the first system). When the first system receives the uninstallation operation and the second system is in a sleep state, the first system sends the application uninstallation message to the second system the next time it wakes up, avoiding frequent wake-ups of the second system.

[0104] Indicative, such as Figure 7 As shown, during the process of the first system displaying the application list interface, when an uninstallation operation is received, the first system updates the application list interface based on the uninstallation operation (removing the application icon of the application to be uninstalled from the application list interface) and determines the system running the application to be uninstalled. When the application to be uninstalled is run by the second system, the first system sends an application uninstallation message to the second system. Upon receiving the application uninstallation message, the second system performs the application uninstallation.

[0105] Besides uninstalling applications through the application list interface when the first system is running in the foreground, when the second system is running in the foreground, the second system can install new applications, delete existing applications, or update existing applications through its running app store. In this case, to ensure that the applications displayed in the application list interface are updated synchronously, in one possible implementation, the second system sends an application list update message to the first system. This application list update message includes at least one of application installation messages, application uninstallation messages, and application update messages. Correspondingly, the first system updates the stored application identifiers and application layout information based on the application list update message.

[0106] Optionally, the application installation message contains the application identifier of the newly installed application, the application uninstallation message contains the application identifier of the application to be uninstalled, and the application update message contains the application identifier of the application to be updated.

[0107] In some embodiments, in response to an application installation operation (installation via an app store or installation based on an obtained application installation package), the second system sends an application installation message to the first system. The first system adds an application identifier based on the application installation message and updates the application layout information (at least adding layout information for the newly installed application).

[0108] In response to an application uninstallation operation (either via an app store or through application management software), the second system sends an application uninstallation message to the first system. Based on the application uninstallation message, the first system deletes the application identifier of the application to be uninstalled and updates the application layout information (at least deleting the layout information of the application to be uninstalled).

[0109] In response to an application update operation (triggered manually or automatically by the user), the second system sends an application update message to the first system. Based on the application update message, the first system updates the application's application identifier.

[0110] Indicative, such as Figure 8 As shown, when the second system is running in the foreground and receives an application installation operation, it installs the application and sends an application installation message containing the application identifier to the first system. Upon receiving the application installation message, the first system adds the application identifier and updates the application layout information. Subsequently, the first system displays the application list interface based on the updated application layout information and the application identifier.

[0111] In other possible implementations, when the second system is in a wake-up state, in response to a language change operation, the second system sends a language update message to the first system, and the first system updates the stored application identifier based on the language update message. For example, when the system language is changed from Chinese to English, the second system sends a language update message containing the English name of the application to the first system, so that the first system updates the stored Chinese name of the application to the English name of the application.

[0112] In other possible implementations, when the second system is in a wake-up state, in response to a display mode change operation, the second system sends a display mode update message to the first system, and the first system updates the application layout information based on the display mode update message. This display mode update message indicates the need to update at least one of the following: font, font size, application icon size, and application icon view (list view or grid view). For example, when a user switches the display mode to senior mode, the first system increases the application icon size and the font size of the application name based on the display mode change message sent by the second system.

[0113] After using the first application, the user can switch the first system back to the foreground by returning. In one possible implementation, in response to the return operation, the second system sends an interface switching message to the first system. This interface switching message indicates the target interface of the first system to be displayed.

[0114] Since the screen control permissions of the electronic device reside in the second system when displaying the application interface of the first application, the first system, upon receiving the interface switching message, obtains screen control permissions from the second system and displays the target interface based on the interface switching message. This target interface is either the main system interface or the application list interface of the first system. For example, when the electronic device is a smartwatch, the main system interface could be the watch face.

[0115] The target interface displayed by the first system differs depending on the type of return operation.

[0116] In some embodiments, in response to a first return operation, the second system sends a first interface switching message to the first system based on the first return operation. The first interface switching message is used to instruct the first system to switch the display of the system's main interface.

[0117] In one possible implementation, the first interface switching message includes a first identifier. When the first system recognizes the first identifier, it switches to display the system's main interface.

[0118] In an illustrative example, when the electronic device is a smartwatch, when a screen covering operation is received (even if the screen is covered by a hand, the screen covering operation can be identified by detecting the number of touch point coordinates), the second system sends a first interface switching message to the first system.

[0119] In response to the second return operation, the second system sends a second interface switching message to the first system based on the first return operation. The second interface switching message is used to instruct the first system to switch the display of the application list interface.

[0120] In one possible implementation, the second return operation differs from the first return operation, and the second interface switching message contains a second identifier different from the first identifier. Upon recognizing the second identifier, the first system switches to displaying the application list interface.

[0121] In an illustrative example, when the electronic device is a smartwatch, the second system sends a second interface switching message to the first system when a press operation on the crown is received.

[0122] In one possible implementation, when the first system displays the target interface, the second system switches from a wake-up state to a sleep state to reduce power consumption. However, when the user triggers the switch to display the application list interface on the first system via a second back operation, they will typically continue to select and launch other applications from the application list interface. If the subsequently selected application is run by the second system, the second system needs to be woken up again, resulting in the second system frequently switching between sleep and wake-up states in a short period of time.

[0123] To avoid frequent state switching of the second system within a short period, in one possible implementation, after the second system sends a first interface switching message to the first system based on a first back operation, the second system switches from a wake-up state to a sleep state. Since the user typically does not continue to launch applications running on the second system after triggering the switch to display the system's main interface on the first system through the first back operation, the second system immediately switches to a sleep state after sending the first interface switching message to the first system, thereby reducing device power consumption.

[0124] Indicative, such as Figure 9 As shown, when the second system displays the application interface, upon receiving the first return operation, the second system sends a first interface switching message to the first system and switches to sleep mode. Based on this first interface switching message, the first system obtains screen control permissions from the second system and controls the screen to display the system's main interface.

[0125] In another possible implementation, after the second system sends a second interface switching message to the first system based on the first return operation, the second system remains awake for a specified wake-up time. During this wake-up time, the first system has screen control permissions for the device, while the second system runs in the background. Upon reaching the wake-up time limit and without receiving an application launch message from the first system, the second system switches from the awake state to a sleep state.

[0126] Since users typically launch other applications after triggering the switch to the application list interface on the first system via the second return operation, the second system does not immediately switch to sleep mode after sending the first interface switch message to the first system. Instead, it remains awake for a specified wake-up time (e.g., 1 second, 2 seconds, etc.). If the first system receives an application selection operation from the application list interface within this wake-up time, and the selected application is run by the second system, the first system sends an application launch message to the second system. Because the second system remains awake, it does not need to switch states and can directly launch the application. This avoids frequent state switching of the second system and improves application launch speed (because it eliminates the process of switching from sleep mode to wake-up mode).

[0127] Indicative, such as Figure 10 As shown, when the second system displays the application interface, upon receiving a second return operation, the second system sends a second interface switching message to the first system and remains awake. Based on this second interface switching message, the first system obtains screen control permissions from the second system and controls the screen to display the application list interface. If no application launch message is received from the first system within the wake-up time, the second system switches to sleep mode.

[0128] Please refer to Figure 11This diagram illustrates a structural block diagram of an interface display device according to an embodiment of this application. The device can be implemented as all or part of an electronic device through software, hardware, or a combination of both. The device includes:

[0129] The first system module 1101 is also configured to display an application list interface in response to a list launch operation, wherein the application list interface contains applications run by the first system and the second system.

[0130] The first system module 1101 is further configured to send an application startup message to the second system module 1102 in response to the selection operation of the first application in the application list interface, wherein the first application is an application run by the second system.

[0131] The second system module 1102 is used to launch the first application and display the application interface based on the application launch message.

[0132] Optionally, the first system module 1101 is used to obtain application identifiers and application layout information of at least one stored application, wherein the application layout information is used to characterize the layout of each application identifier in the application list interface.

[0133] The first system module 1101 is used to display the application list interface based on the application identifier and the application layout information.

[0134] Optionally, the first system module 1101 is further configured to update the application list interface in response to a layout editing operation of the second application in the application list interface, wherein the second application is run by the first system or the second system.

[0135] The first system module 1101 is used to update the application layout information.

[0136] Optionally, the first system module 1101 is further configured to update the application list interface in response to an uninstallation operation of a third application in the application list interface, wherein the third application is run by the first system or the second system.

[0137] The first system module 1101 is used to delete the application identifier corresponding to the third application and update the application layout information.

[0138] Optionally, if the third application is run by the second system, the first system module 1101 is further configured to send an application uninstallation message to the second system module 1102;

[0139] The second system module 1102 is used to uninstall the third application based on the application uninstallation message.

[0140] Optionally, the second system module 1102 is further configured to send an application list update message to the first system module 1101, wherein the application list update message includes at least one of an application installation message, an application uninstallation message, and an application update message;

[0141] The first system module 1101 is used to update the stored application identifier and the application layout information based on the application list update message.

[0142] Optionally, the second system module 1102 is further configured to send an interface switching message to the first system module 1101 based on the return operation in response to the return operation;

[0143] The first system module 1101 is used to obtain screen control permissions from the second system module 1102 and display a target interface based on the interface switching message. The target interface is the main system interface of the first system or the application list interface.

[0144] Optionally, the second system module 1102 is used for:

[0145] In response to the first return operation, a first interface switching message is sent to the first system module 1101 based on the first return operation. The first interface switching message is used to instruct the first system to switch to display the system main interface.

[0146] In response to the second return operation, a second interface switching message is sent to the first system module 1101 based on the first return operation. The second interface switching message is used to instruct the first system to switch to display the application list interface.

[0147] Optionally, when the second system module 1102 sends a first interface switching message to the first system module 1101 based on the first return operation, the second system module 1102 is also used to switch from a wake-up state to a sleep state.

[0148] When the second system module 1102 sends a second interface switching message to the first system module 1101 based on the first return operation, the second system module 1102 is further configured to:

[0149] Maintain wake-up state for the duration of wake-up hold;

[0150] In response to reaching the specified wake-up duration and not receiving an application startup message, the system switches from the wake-up state to the sleep state.

[0151] Optionally, the first system module 1101 is used for:

[0152] In response to the selection operation of the first application in the application list interface, the running system identifier corresponding to the first application is obtained, and the running system identifier is used to characterize the system running the application;

[0153] When the operating system identifier indicates that the first application is run by the second system, the application startup message is sent to the second system module 1102.

[0154] Optionally, the first system module 1101 is used for:

[0155] In response to the selection of a fourth application in the application list interface, the fourth application is launched and its interface is displayed. The fourth application is an application run by the first system.

[0156] Optionally, the power consumption of the first system is lower than that of the second system.

[0157] In summary, for electronic devices that support dual systems, since users can launch applications running on either the first or second system through the application list interface, in this embodiment, the application list interface is displayed through the first system, and when a selection operation for an application running on the second system is received, the system switches to the second system to launch the application and display its interface. This avoids the need to switch from the first to the second system when displaying the application list interface, which helps reduce the frequency of system switching and prevents increased device power consumption caused by frequent system switching.

[0158] Please refer to Figure 12 This diagram illustrates a structural block diagram of an electronic device provided in an exemplary embodiment of this application. The electronic device in this application may include one or more components such as a processor 1210 and a memory 1220.

[0159] Optionally, the processor 1210 includes at least a first processor 1211 and a second processor 1212, wherein the first processor 1211 is used to run a first system, and the second processor 1212 is used to run a second system. The power consumption of the first processor 1211 is lower than that of the second processor 1212, and the performance of the first processor 1211 is lower than that of the second processor 1212. The processor 1210 connects various parts within the electronic device using various interfaces and lines. It performs various functions of the electronic device and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 1220, and by calling data stored in the memory 1220. Optionally, the processor 1210 can be implemented using at least one hardware form selected from Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 1210 can integrate one or more of the following: a central processing unit (CPU), a graphics processing unit (GPU), a neural network processing unit (NPU), and a modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content displayed on the touchscreen; the NPU implements artificial intelligence (AI) functions; and the modem handles wireless communication. It is understood that the modem can also be implemented as a separate chip without being integrated into the processor 1210.

[0160] The memory 1220 may include random access memory (RAM) or read-only memory (ROM). Optionally, the memory 1220 may include a non-transitory computer-readable storage medium. The memory 1220 may be used to store instructions, programs, code, code sets, or instruction sets. The memory 1220 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the various method embodiments described below, etc.; the data storage area may store data created according to the use of the electronic device (such as audio data, phone book, etc.).

[0161] The electronic device in this embodiment further includes a communication component 1230 and a display component 1240. The communication component 1230 can be a Bluetooth component, a WiFi component, an NFC component, etc., used to communicate with external devices (servers or other terminal devices) via wired or wireless networks; the display component 1240 is used to display a graphical user interface and / or receive user interaction operations.

[0162] In addition, those skilled in the art will understand that the structure of the electronic device shown in the above figures does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements. For example, the electronic device may also include radio frequency circuits, input units, sensors, audio circuits, speakers, microphones, power supplies, etc., which will not be described in detail here.

[0163] This application also provides a computer-readable storage medium storing at least one instruction, which is executed by a processor to implement the interface display method as described in the above embodiments.

[0164] This application provides a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. The processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the interface display method provided in the above embodiments.

[0165] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0166] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for displaying an interface, characterized in that, The method is used in an electronic device that supports the operation of a first system and a second system, wherein the power consumption of the first system is lower than that of the second system. The method includes: In response to the list launch operation, the first system displays an application list interface, which contains applications running by the first system and the second system, while the second system is in a dormant state. In response to the selection of a first application in the application list interface, the first system sends an application launch message to the second system, wherein the first application is an application run by the second system; When the second system switches from a sleep state to a wake-up state, the second system launches the first application and displays the application interface based on the application launch message; In response to the first return operation, the second system sends a first interface switching message to the first system based on the first return operation. The first interface switching message is used to instruct the first system to switch to displaying the system's main interface; the second system switches from a wake-up state to a sleep state. In response to the second return operation, the second system sends a second interface switching message to the first system based on the first return operation. The second interface switching message is used to instruct the first system to switch to displaying the application list interface. The second system maintains a wake-up state for the wake-up hold duration. In response to the wake-up hold duration being reached and no application startup message being received, the second system switches from the wake-up state to a sleep state. The first system obtains screen control permissions from the second system and displays a target interface based on the interface switching message. The target interface is the main interface of the first system or the application list interface.

2. The method according to claim 1, characterized in that, The first system displays an application list interface, including: The first system acquires the application identifier and application layout information of at least one application stored in the system. The application layout information is used to characterize the layout of each application identifier in the application list interface. The first system displays the application list interface based on the application identifier and the application layout information.

3. The method according to claim 2, characterized in that, The method further includes: In response to a layout editing operation of the second application in the application list interface, the first system updates the application list interface, and the second application is run by the first system or the second system. The first system updates the application layout information.

4. The method according to claim 2, characterized in that, The method further includes: In response to an uninstallation operation of a third application in the application list interface, the first system updates the application list interface, and the third application is run by the first system or the second system; The first system deletes the application identifier corresponding to the third application and updates the application layout information.

5. The method according to claim 4, characterized in that, When the third application is run by the second system, the method further includes: The first system sends an application uninstallation message to the second system; The second system uninstalls the third application based on the application uninstall message.

6. The method according to claim 2, characterized in that, The method further includes: The second system sends an application list update message to the first system, the application list update message including at least one of application installation message, application uninstallation message and application update message; The first system updates the stored application identifier and the application layout information based on the application list update message.

7. The method according to any one of claims 1 to 6, characterized in that, In response to the selection of a first application in the application list interface, the first system sends an application launch message to the second system, including: In response to the selection operation of the first application in the application list interface, the first system obtains the running system identifier corresponding to the first application, and the running system identifier is used to characterize the system running the application. When the operating system identifier indicates that the first application is run by the second system, the first system sends the application launch message to the second system.

8. The method according to any one of claims 1 to 6, characterized in that, The method further includes: In response to the selection of a fourth application in the application list interface, the first system launches the fourth application and displays the application interface, wherein the fourth application is an application run by the first system.

9. An interface display device, characterized in that, The device is used in an electronic device, which supports the operation of a first system and a second system, wherein the power consumption of the first system is lower than that of the second system. The device includes: The first system module is also configured to display an application list interface in response to a list launch operation, the application list interface containing applications run by the first system and the second system, the second system being in a dormant state; The first system module is further configured to send an application launch message to the second system module in response to a selection operation of the first application in the application list interface, wherein the first application is an application run by the second system. When the second system switches from a dormant state to a wake-up state, the second system module is used to launch the first application based on the application launch message and display the application interface; The second system module is further configured to respond to the first return operation by sending a first interface switching message to the first system module based on the first return operation, wherein the first interface switching message is used to instruct the first system to switch to displaying the main system interface; the second system module is further configured to switch from a wake-up state to a sleep state. In response to the second return operation, a second interface switching message is sent to the first system module based on the first return operation. The second interface switching message is used to instruct the first system to switch to displaying the application list interface. The second system module is also used to maintain the wake-up state for a wake-up hold duration. In response to the wake-up hold duration being reached and no application startup message being received, the wake-up state is switched to the sleep state. The first system module is further configured to obtain screen control permissions from the second system module and display a target interface based on the interface switching message, wherein the target interface is the system main interface or the application list interface of the first system.

10. An electronic device, characterized in that, The electronic device includes a processor and a memory; the memory stores at least one instruction, which is executed by the processor to implement the interface display method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, The storage medium stores at least one instruction, which is executed by a processor to implement the interface display method as described in any one of claims 1 to 8.

12. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium; a processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to implement the interface display method as described in any one of claims 1 to 8.

Images