Display method, electronic equipment and readable storage medium

Abstract

The invention relates to the technical field of computers, in particular to a display method, electronic equipment and a readable storage medium. The method comprises the following steps: when two devices carry out data transmission, a display interface similar to a blank screen display state can be entered under the condition that a user does not interact with the devices for a long time, only key information of a data transmission process is displayed, and display parameters such as display brightness and a screen refreshing frame rate of the devices are lowered. Therefore, the display power consumption of the equipment can be reduced.

Description

Technical Field

[0001] This application relates to the field of computer technology, and particularly to a display method, an electronic device, and a readable storage medium. Background Art

[0002] When a user replaces an old electronic device with a new one, it is necessary to migrate the data in the old device to the new device. For example, Figure 1A and Figure 1B respectively show schematic diagrams of the interfaces when migrating data during the replacement of an old mobile phone 10 and a new mobile phone 20. Figure 1A In, the interface of the old mobile phone 10 displays data sending information. For example, each application icon, the corresponding application name (such as contacts, messages, call records, notes, recordings, etc.), the data sending progress percentage, rate, remaining sending time, a prompt message to remind the user not to leave the current interface, and a "Cancel" control to cancel the data migration process, etc. Figure 1B In, the interface of the new mobile phone 20 also displays data receiving information. For example, each application icon, the corresponding application name (such as contacts, messages, call records, notes, recordings, etc.), the data receiving progress of each application, rate, remaining receiving time, a prompt message to remind the user not to leave the current interface, and a "Cancel" control to cancel the data migration process, etc. For example, Figure 1A shows that the data of the recording application is currently being migrated, and the total migrated data is currently 1.99 GB.

[0003] Due to the large storage space and large amount of stored data of current electronic devices, it takes a certain amount of time for data migration. During this process, the interfaces of the old and new devices are in a constantly lit state, continuously displaying the data migration information of each application, resulting in relatively high display power consumption in the scenario of replacing devices. Summary of the Invention

[0004] To reduce the display power consumption of old and new devices in the data transmission scenario, this application provides a display method, an electronic device, and a readable storage medium.

[0005] In a first aspect, this application provides a display method for an electronic device. The method includes: the first electronic device displays a first data transmission interface for data transmission with the second electronic device, where the first data transmission interface has a first display brightness, and the first data transmission interface includes multiple transmission information items; the first electronic device displays a second data transmission interface, where the second data transmission interface has a second display brightness, and the second data transmission interface displays some of the transmission information items among the multiple transmission information items; where the second display brightness is less than the first display brightness.

[0006] It can be understood that in the present application, the above-mentioned first electronic device and second electronic device may respectively refer to the old mobile phone 10 and the new mobile phone 20 mentioned in the embodiments of the present application; the first data transmission interface may refer to the data sending interface of the old mobile phone 10 mentioned in the embodiments of the present application, or the data receiving interface of the new mobile phone 20. The multiple transmission information items may refer to various application icons, application names of each application (such as contacts, messages, call records, notes, recordings, etc.), data sending or receiving progress percentages, rates, remaining data sending or receiving times, prompt messages for prompting the user not to leave the current interface, and controls for canceling the data migration process, etc. in the embodiments of the present application. The second data transmission interface may refer to the cloned AOD interface of the old mobile phone 10 (which is also a data sending interface) mentioned in the embodiments of the present application, or the cloned AOD interface of the new mobile phone 20 (which is also a data receiving interface). The partial transmission information items may refer to data sending or receiving progress, rate, and remaining data sending or receiving time, etc. mentioned in the embodiments of the present application.

[0007] Based on the above solution, in a scenario where data is transmitted between multiple devices, such as in a mobile phone replacement scenario, the display interface of the first electronic device may display the second data transmission interface when meeting corresponding conditions. The second data transmission interface may only display partial transmission information items of the data transmission, and display parameters such as the screen display brightness and screen refresh frame rate of the first electronic device are reduced, thereby reducing the display power consumption of the first electronic device and improving the user's mobile phone replacement experience.

[0008] In a possible implementation of the above first aspect, the multiple transmission information items include the data transmission progress percentage, data transmission rate, amount of data already transmitted, remaining data transmission time, names, icons, and transmission status of the multiple transmission information items.

[0009] It can be understood that data transmission may refer to data sending or data receiving mentioned in the embodiments of the present application.

[0010] In a possible implementation of the above first aspect, the second display brightness is 0% - 30% of the first display brightness.

[0011] It can be understood that the first display brightness may refer to the normal display brightness of 100% mentioned in the embodiments of the present application, and the second display brightness may refer to any display brightness less than or equal to 30% of the normal display brightness mentioned in the embodiments of the present application. For example, 25%, 10%, 0, which are not limited herein.

[0012] It can be understood that the second display brightness may refer to the display brightness when the display brightness of the device is adjusted to the display brightness when the screen is blacked out, that is, the background brightness of the device interface is adjusted to the darkest, while there are still display elements in the device interface, such as text, etc.

[0013] In a possible implementation of the first aspect described above, the first electronic device displays a second data transmission interface, including: determining whether the first data transmission interface meets the interface switching condition; corresponding to the first data transmission interface meeting the interface switching condition, the first electronic device displays the second data transmission interface.

[0014] In a possible implementation of the first aspect described above, the interface switching condition includes that the first data transmission interface does not receive a first operation within a preset duration; the first operation includes a click operation, a double-click operation, a swipe operation, and a press operation received on the screen of the first electronic device.

[0015] It can be understood that the interface switching condition may further include that the first electronic device receives a voice command.

[0016] In a possible implementation of the first aspect described above, the interface switching condition further includes that the first data transmission interface does not detect a notification pop-up window within a preset duration.

[0017] In a possible implementation of the first aspect described above, determine whether the second data transmission interface receives a first operation or detects a notification pop-up window; corresponding to the second data transmission interface receiving a first operation or detecting a notification pop-up window and the data transmission not being completed, the first electronic device exits the display of the second data transmission interface, and the first electronic device displays the first data transmission interface.

[0018] In a possible implementation of the first aspect described above, determine whether the first electronic device has completed data transmission; corresponding to the first electronic device completing data transmission, the first electronic device exits the display of the second data transmission interface, and the first electronic device displays a data transmission completion interface.

[0019] It can be understood that the data transmission completion interface may refer to the data migration success interface mentioned in the embodiments of the present application.

[0020] In a possible implementation of the first aspect described above, the first data transmission interface has a first screen refresh rate, and the second data transmission interface has a second screen refresh rate, and the second screen refresh rate is less than the first screen refresh rate.

[0021] It can be understood that the first screen refresh rate may refer to any screen refresh rate in the range of 60HZ to 360HZ mentioned in the embodiments of the present application, such as screen refresh rates of 60HZ, 75HZ, 120HZ, 144HZ, 165HZ, 240HZ, 360HZ, etc. The second screen refresh rate may refer to a screen refresh rate of 30HZ or less than 30HZ mentioned in the embodiments of the present application.

[0022] In a second aspect, an embodiment of the present application provides an electronic device, including a memory for storing instructions; and a processor for executing the instructions to implement the display method provided by the first aspect and various possible implementations of the first aspect.

[0023] In a third aspect, an embodiment of the present application provides a readable storage medium, on which instructions are stored, and when the instructions are executed on an electronic device, the display method provided by the first aspect and various possible implementations of the first aspect is implemented.

[0024] In a fourth aspect, an embodiment of the present application further provides a computer program product, including a computer program / instructions, and when the computer program / instructions are executed by a processor, the display method provided by the first aspect and various possible implementations of the first aspect is implemented. Description of the Drawings

[0025] Figure 1A Fig. shows a schematic diagram of an interface when an old mobile phone 10 changes the phone and migrates data.

[0026] Figure 1B Fig. shows a schematic diagram of an interface when a new mobile phone 20 changes the phone and migrates data.

[0027] Figure 2A According to some embodiments provided by the present application, Fig. shows another schematic diagram of an interface when an old mobile phone 10 changes the phone and migrates data.

[0028] Figure 2B According to some embodiments provided by the present application, Fig. shows another schematic diagram of an interface when a new mobile phone 20 changes the phone and migrates data.

[0029] Figure 3 According to some embodiments provided by the present application, Fig. shows a schematic diagram of the structure when an old mobile phone 10 and a new mobile phone 20 change the phone.

[0030] Figure 4 According to some embodiments provided by the present application, Fig. shows a schematic diagram of the process of a display method from the perspective of the UI interface of an old mobile phone 10.

[0031] Figure 5A According to some embodiments provided by the present application, Fig. shows a schematic diagram of the main interface of an old mobile phone 10.

[0032] Figure 5B According to some embodiments provided by the present application, Fig. shows an application interface diagram of the "phone change and clone" application of an old mobile phone 10.

[0033] Figure 5C According to some embodiments provided by the present application, Fig. shows a scanning code interface diagram of an old mobile phone 10.

[0034] Figure 6A According to some embodiments provided by the present application, a schematic diagram of the main interface of a new mobile phone 20 is shown;

[0035] Figure 6B According to some embodiments provided by the present application, an application interface diagram of the "Mobile Phone Clone" application of a new mobile phone 20 is shown;

[0036] Figure 6C According to some embodiments provided by the present application, a schematic diagram of the interface of a new mobile phone 20 displaying different device types is shown;

[0037] Figure 6D According to some embodiments provided by the present application, a two-dimensional code interface diagram of the new mobile phone 20 corresponding to the selection of "Honor device" is shown;

[0038] Figure 7A According to some embodiments provided by the present application, an interface diagram of the new mobile phone 20 displaying the prompt message "Please select the data to be migrated on the old device" is shown;

[0039] Figure 7B According to some embodiments provided by the present application, an interface diagram of the old mobile phone 10 displaying the data to be migrated available for selection is shown;

[0040] Figure 7C According to some embodiments provided by the present application, a schematic diagram of the data sending interface 740 of the old mobile phone 10 is shown;

[0041] Figure 7D According to some embodiments provided by the present application, a schematic diagram of the clone AOD interface 730 of the old mobile phone 10 is shown;

[0042] Figure 7E According to some embodiments provided by the present application, a schematic diagram of the data receiving interface 750 of the new mobile phone 20 is shown;

[0043] Figure 7F According to some embodiments provided by the present application, a schematic diagram of the clone AOD interface 760 of the new mobile phone 20 is shown;

[0044] Figure 7G According to some embodiments provided by the present application, a schematic diagram of the data migration success interface 770 of the old mobile phone 10 is shown;

[0045] Figure 7H According to some embodiments provided by the present application, a schematic diagram of the data migration success interface 780 of the new mobile phone 20 is shown;

[0046] Figure 8According to some embodiments provided by the present application, a schematic flow chart of a display method described at the system level based on the old mobile phone 10 is shown;

[0047] Figure 9 According to some embodiments provided by the present application, a schematic macro flow chart of data migration of the old mobile phone 10 is shown;

[0048] Figure 10 According to some embodiments provided by the present application, a schematic implementation flow chart of a display method of the new mobile phone 20 is shown;

[0049] Figure 11 According to some embodiments provided by the present application, a schematic flow chart of a display method executed based on the system service of the new mobile phone 20 is shown.

[0050] Figure 12 According to some embodiments provided by the present application, a schematic macro flow chart of data migration of the new mobile phone 20 is shown;

[0051] Figure 13A According to some embodiments provided by the present application, a schematic structural diagram of the data migration process of the old mobile phone 10 is shown;

[0052] Figure 13B According to some embodiments provided by the present application, a schematic structural diagram of the data migration process of the new mobile phone 20 is shown;

[0053] Figure 14A According to some embodiments provided by the present application, a schematic diagram of the interface 140 of the mobile phone 30 for sending video data based on Bluetooth is shown;

[0054] Figure 14B According to some embodiments provided by the present application, a schematic diagram of the interface 141 of the mobile phone 40 for receiving video data based on Bluetooth is shown;

[0055] Figure 14C According to some embodiments provided by the present application, a schematic diagram of another interface 142 of the mobile phone 30 for sending video data based on Bluetooth is shown;

[0056] Figure 14D According to some embodiments provided by the present application, a schematic diagram of another interface 143 of the mobile phone 40 for receiving video data based on Bluetooth is shown;

[0057] Figure 15A According to some embodiments provided by the present application, a schematic diagram of the interface of the mobile phone 30 for sharing video data based on near field communication (NFC) is shown;

[0058] Figure 15BAccording to some embodiments provided by the present application, a schematic diagram of an interface for a mobile phone 40 to receive video data based on NFC is shown;

[0059] Figure 15C According to some embodiments provided by the present application, a schematic diagram of an interface for a mobile phone 30 to share video data based on NFC is shown;

[0060] Figure 15D According to some embodiments provided by the present application, a schematic diagram of another interface for a mobile phone 40 to receive video data based on NFC is shown;

[0061] Figure 16 According to some embodiments provided by the present application, a schematic diagram of the structure of a mobile phone is shown. Detailed implementation manners

[0062] The illustrative embodiments of the present application include, but are not limited to, a display method, an electronic device, and a readable storage medium.

[0063] It can be understood that the electronic device in the embodiments of the present application can also be referred to as a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc. The terminal device can be a mobile phone, a smart TV, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.

[0064] It can be understood that the display method described in the embodiments of the present application is applicable to various data transmission scenarios, such as the "switching machine cloning" application scenario involved above, and short-range data transmission between terminals via Bluetooth, near field communication (NFC), etc. Hereinafter, the data transmission between terminals via the "switching machine cloning" application will be taken as an example for illustration.

[0065] It can be understood that in the data transmission scenarios to which the display method provided in the embodiments of the present application is applied, the data transmitted between multiple devices can be various types of application program data or data (compressed) packages such as video data, audio data, files, folders, picture data, etc. The type of the transmitted data is not limited herein.

[0066] The technical solution of the present application will be introduced below in conjunction with the accompanying drawings.

[0067] It can be understood that the new device and the old device can be switched based on applications such as "Switching Machine Clone". The "Switching Machine Clone" application is a convenient and secure switching application that can transfer the data on the old device to the new device when switching between the new and old devices.

[0068] As mentioned above, since it takes a certain amount of time for data migration, and during this process, the interfaces of the new and old devices remain lit, continuously displaying the data migration information of each application, resulting in relatively high display power consumption in the switching device scenario.

[0069] In some solutions, in order to reduce the display power consumption of the new and old devices during device switching, the display brightness of the new and old devices can be reduced during device switching, thereby reducing power consumption. However, in this solution, the interface brightness of the new and old devices is too low, which makes it impossible for users to clearly see the data migration information, and even users may mistakenly think that the phone has entered the screen-off state, resulting in the user being unable to view the data migration progress in real time and affecting the user's device switching experience.

[0070] To solve the above problems, an embodiment of the present application provides a display method. Specifically, when data is transferred between two devices, this method can enter a display interface similar to the screen-off state when the user has no interaction with the device for a long time, etc., such as only displaying the key information of the data transfer process, and reducing display parameters such as the display brightness and screen refresh rate of the device to reduce the display power consumption of the device.

[0071] For example, when switching between the new and old devices, this method sets the data migration interfaces of the new and old devices to only display key information, and reduces the background brightness, such as reducing it to the black screen display state. The black screen display state means that the background brightness of the device interface is adjusted to the darkest, while there are still display elements in the device interface, such as text, etc. Similar to the screen-off display of the device; the screen refresh rate of the device can also be reduced, such as adjusting the screen refresh rate from 120HZ to less than or equal to 30HZ.

[0072] It can be understood that in some embodiments, the above key information may include data migration progress, rate, remaining migration time, etc., which are not limited herein.

[0073] In addition, it can be understood that the background brightness of the data migration interface can be adjusted to be less than or equal to 30% of the normal display brightness of the device, or the data migration interface can be directly black-screen displayed. For example, if the normal display brightness of the device is 100%, the range of the background brightness of the data migration interface can be less than 30% of the normal display brightness. For example, the background brightness can be adjusted to 25%, 10%, or even directly 0, and the data migration interface is directly black-screen displayed.

[0074] It can be understood that in some other embodiments, the data migration interface can also be displayed in a locked screen state to prevent the user from accidentally touching the data migration interface and affecting the data migration progress, which is not limited herein. Based on this, in the scenario of switching between old and new devices, the display interfaces of the old and new devices can only display the key information of data migration, and the screen refresh rate, screen display brightness, etc. of the old and new devices are reduced, so that the display power consumption during device switching is reduced.

[0075] For example, Figure 2A and Figure 2B respectively show schematic diagrams of the interfaces during data migration when switching between another old mobile phone 10 and a new mobile phone 20.

[0076] Figure 2A In, the interface 210 of the old mobile phone 10 can be displayed in a black screen state and can only display the key information of data migration. For example: the key information 211 "Sending", the key information 212 "5.5%", indicating the percentage of data sending progress, the key information 213: "4.92 GB has been sent", "Rate 118 MB / s", "Remaining time for sending data 13 minutes", etc. If the user wants to return to the data sending interface of the old mobile phone 10 as shown in Figure 1A shown, then the operation control 214 "Tap to return" in Figure 2A can be clicked.

[0077] Figure 2B In, the interface 220 of the new mobile phone 20 can be displayed in a black screen state and can only display the key information of data migration. For example: the key information 221 "Receiving", the key information 222 "5.5%", indicating the percentage of data receiving progress, the key information 223: "4.92 GB has been received", "Rate 118 MB / s", "Remaining time for receiving data 13 minutes", etc. If the user wants to return to the data receiving interface of the new mobile phone 20 as shown in Figure 1B shown, then the operation control 224 "Tap to return" in Figure 2B can be clicked.

[0078] It can be understood that the key information of data migration can be any predetermined key information related to data migration. For example, it can be the data sending progress percentage, data receiving progress percentage, rate, remaining sending time, remaining receiving time, etc. as described above, which is not limited herein.

[0079] To facilitate understanding of the specific solution for data migration when switching between old and new devices. The following combines Figure 3 to illustrate the specific process of switching between old and new devices.

[0080] Specifically, Figure 3 shows a schematic structural diagram when switching between an old mobile phone 10 and a new mobile phone 20.

[0081] It can be understood that in some embodiments, the process of migrating data when replacing an old device with a new one can also be referred to as replacement cloning. The old device can be referred to as the replacement cloning sender, and the new device can be referred to as the replacement cloning receiver.

[0082] As Figure 3 shown, Figure 3 shows the user interface (UI) side and the system side of the old mobile phone 10 as the replacement cloning sender; and, the user interface (UI) side and the system side of the new mobile phone 20 as the replacement cloning receiver. The UI sides of the old mobile phone 10 and the new mobile phone 20 can both include a UI process and a service process. Specifically:

[0083] Some services in the UI process of the old mobile phone 10 can be implemented by modules corresponding to the services. For example, a connection module 150, a session management module 160, a transmission client module 170, and a data backup module 180. Some services in the UI process of the new mobile phone 20 can be implemented by modules corresponding to the services. For example, a connection module 250, a session management module 260, a transmission server module 270, and a data recovery module 280. Among them:

[0084] The connection module 150 and the connection module 250 can be used to implement communication connections between electronic devices based on connection methods such as Wi-Fi. For example, based on the connection module 150 and the connection module 250, the old mobile phone 10 can communicate with the new mobile phone 20.

[0085] A session can be established between the session management module 160 and the session management module 260 based on session service signaling. For example, the session management module 160 of the old mobile phone 10 can send a session establishment request to the session management module 260 of the new mobile phone 20. The session establishment request usually can include the identification information of the called party, such as the identification information of the new mobile phone 20. After the session management module 260 receives the session establishment request sent by the session management module 160, it then sends a received session establishment request to the session management module 260 to confirm and accept the session establishment request of the calling party, such as the session establishment request of the old mobile phone 10. Based on this, the old mobile phone 10 and the new mobile phone 20 can establish a session. After the old mobile phone 10 and the new mobile phone 20 establish a session, the session management module 160 and the session management module 260 can send socket messages to each other. For example, it can be the version number of any application program. Furthermore, the new mobile phone 20 can determine whether the new mobile phone 20 has the ability to receive and process the data of the application program based on the version number of the application program sent by the old mobile phone 10.

[0086] The transmission client module 170 can be used to send the data to be migrated of the old mobile phone 10 to the transmission server module 270; the transmission server module 270 can be used to receive the data to be migrated of the old mobile phone 10 sent by the transmission client module 170.

[0087] The data backup module 180 can be used to back up the data to be migrated in the old mobile phone 10 that needs to be sent to the new mobile phone 20. It can be backed up to the temporary cache directory of the old mobile phone 10, so that the transmission client module 170 can compress the data to be migrated in the temporary cache directory and send it to the transmission server module 270 of the new mobile phone 20. Furthermore, the data recovery module 280 of the new mobile phone 20 can obtain the compressed package corresponding to the data to be migrated of the old mobile phone 10 from the transmission server module 270 of the old mobile phone 10, then store it in the temporary cache directory of the new mobile phone 20, decompress the compressed package corresponding to the data to be migrated, and recover and store the data to be migrated in the new mobile phone 20.

[0088] The UI process can communicate with the service process through the Android Interface Definition Language (AIDL), that is, the UI process can send call instructions to the service process based on AIDL.

[0089] For example, the UI process of the old mobile phone 10 can send a call instruction to its service process through AIDL, so that the service process of the old mobile phone 10 can obtain the data to be migrated that needs to be sent to the new mobile phone 10 from the system side of the old mobile phone 10. Furthermore, the data backup module 180 can back up the data to be migrated and send it to the data recovery module 280 of the new mobile phone 20.

[0090] For example, the UI process of the new mobile phone 20 can send a call instruction to its service process through AIDL, so that the service process of the new mobile phone 20 can decompress and store the data to be migrated received by the data recovery module 280 in the new mobile phone 20.

[0091] The system services of both the old mobile phone 10 and the new mobile phone 20 can include the SurfaceFlinger service. The SurfaceFlinger service is located in the service process. The SurfaceFlinger service can listen to the changes in the system layers of the old mobile phone 10 and the new mobile phone 20 by calling back the changes in the interface display state. For example, if the application A in the old mobile phone 10 is opened and the application interface of the application A is displayed on the screen of the old mobile phone 10, then based on the callback of the interface display state change by the SurfaceFlinger service, the change in the system layer of the old mobile phone 10 can be monitored, that is, a new system layer corresponding to the application interface of the application A is added. The SurfaceFlinger service can be automatically started when the electronic device is powered on.

[0092] It can be understood that since the Surfaceflinger service monitors the changes of the device's system layers, and the changes of the UI interface can be reflected in the changes of the system layers, the monitoring result can be used to determine whether the current device's UI interface is the data migration interface corresponding to the scene of changing devices. For example, the data migration interface can be the cloned AOD interface 210 (also a data sending interface) of the old mobile phone 10 shown in 2A above and the cloned AOD interface 220 (also a data receiving interface) of the new mobile phone 20 shown in 2B above. If so, and when other relevant conditions are met, the power interface can be called through the Surfaceflinger service to make the device's UI interface enter the AOD mode. The display parameters such as the screen display brightness and the screen refresh frame rate of the device's UI interface in the AOD mode can be reduced, thereby reducing the screen display power consumption of the device.

[0093] It can be understood that since the Surfaceflinger service is responsible for monitoring the changes of the device's system layers, the monitoring frequency of the Surfaceflinger service for the system layers can be preset to be the same as the screen refresh frame rate of the old mobile phone 10 or the new mobile phone 20. For example, the screen refresh frame rates of the old mobile phone 10 and the new mobile phone 20 are: 30HZ - 360HZ, such as 30HZ, 60HZ, 75HZ, 120HZ, 144HZ, 165HZ, 240HZ, 360HZ, etc. Then the monitoring frequencies of the old mobile phone 10 and the new mobile phone 20 for the system layers can also be: 30HZ - 360HZ, such as 30HZ, 60HZ, 75HZ, 120HZ, 144HZ, 165HZ, 240HZ, 360HZ, etc., which is not limited here.

[0094] It can be understood that the data to be migrated of the old mobile phone 10 can be stored in the storage spaces corresponding to the basic data (database, DB) 190, the package manager service (PMS) 191, and the file backup 192 on the system side. The new mobile phone 20 can decompress the data to be migrated obtained from the old mobile phone 10 and store it in the basic data 290, the package manager service 291, and the file backup 292 on the system side of the new mobile phone 20, which is not limited here.

[0095] It can be understood that the system side of the old mobile phone 10 and the new mobile phone 20 can also provide system framework services including battery management system (BMS) services, activity manager service (AMS), input / output (IO) operations, database reading and writing, media library operations, etc., which are not limited herein.

[0096] To further illustrate the display method provided by the embodiments of the present application, the following will be based on the relevant flow schematic diagrams to detail the specific process of applying the display method provided by the embodiments of the present application on the old mobile phone 10 and the new mobile phone 20.

[0097] The following will first detail the specific implementation process of the display method provided by the embodiments of the present application on the old mobile phone 10.

[0098] Figure 4 According to the embodiments of the present application, a schematic diagram of the implementation process of a display method is shown.

[0099] It can be understood that in some embodiments of the present application, Figure 4 the execution subject of each step in the shown process can be the above-mentioned old mobile phone 10. In other embodiments, Figure 4 the execution subject of each step in the shown process can also be electronic devices such as tablet computers, smart wearable devices, smart home devices, in-vehicle devices, etc., which are not limited herein.

[0100] Specifically, Figure 4 the shown process may include the following steps:

[0101] S101: Scan the QR code displayed on the new mobile phone based on the clone application.

[0102] In some embodiments, in order to realize the replacement of the old mobile phone 10 and the new mobile phone 20, the old mobile phone 10 can scan the QR code displayed in the "clone application" of the new mobile phone 20 based on the "clone application" to establish a connection between the old mobile phone 10 and the new mobile phone 20, so as to start the replacement process of the old and new mobile phones.

[0103] As an example, Figures 5A to 5C According to the embodiments of the present application, a schematic diagram of the interface for the old mobile phone 10 to establish a connection with the new mobile phone 20 based on the "replacement clone" application is shown.

[0104] Referring to Figure 5A , the main interface 510 displayed on the old mobile phone 10 includes an icon 511 of the "replacement clone" application. The user can click on the icon 511 of the "replacement clone" application on the old mobile phone 10 to enter the application interface 520 of the "replacement clone" application on the old mobile phone 10.

[0105] Reference Figure 5B , on the application interface 520 of the "Phone Clone" running on the old phone 10, there are prompt messages 521 "Quickly migrate data such as contacts, photos, and daily life to the new device", selection control 522 "This is the new device", and selection control 523 "This is the old device". At this time, the user can click on the option "This is the new device" on the application interface 520 displayed on the old phone 10. Correspondingly, the old phone 10 can display an interface 530 as shown in Figure 5C .

[0106] Reference Figure 5C , in the interface 530 displayed on the old phone 10, there is a prompt message 531 "Please open the 'Phone Clone' on the new phone and select 'This is the new phone' to obtain the hotspot QR code" to prompt the user on how to connect the old phone 10 to the new phone 20 through operations. The interface 530 also includes a scan control 532 and a prompt message 533 "Connection not successful? Connect manually".

[0107] Figures 6A to 6D According to an embodiment of the present application, a schematic diagram of an interface for a new phone 20 to establish a connection with an old phone 10 based on the "Phone Clone" application is shown.

[0108] Reference Figure 6A , in the interface 610 displayed on the new phone 20, there is an icon 612 of the "Phone Clone" application. The user can click on the icon 612 of the "Phone Clone" application on the new phone 20 to enter the application interface 620 of the "Phone Clone" application on the new phone 20.

[0109] Reference Figure 6B , on the application interface 620 of the "Phone Clone" running on the new phone 20, there are prompt messages 621 "Quickly migrate data such as contacts, photos, and daily life to the new device", selection control 622 "This is the new device", and selection control 623 "This is the old device". At this time, the user can click on the option "This is the new device" on the interface 620 displayed on the new phone 20. Correspondingly, the new phone 20 can display an interface 630 as shown in Figure 6C .

[0110] Reference Figure 6C , in the interface 630 displayed on the new phone 20, items of different device types are shown, including "Type A device" 631, "Type B device" 632, "Type C device" 633, "Type D device" 634, etc., for the user to select based on the device type of the new phone 20. For example, if the new phone 20 is a Type A device, the user clicks on and selects the "Type A device". Correspondingly, the new phone 20 can display an interface 640 as shown in Figure 6D . Figure 6D shows the corresponding interface 640 after selecting the "Type A device".

[0111] Reference Figure 6D , on the display interface 640 of the new mobile phone 20, a QR code 641 for the old device to scan and connect is displayed, as well as a prompt message 642 "Open 'Switch and Clone' on the old device, select 'This is the old device' and scan the QR code above to establish a connection", and "If you cannot connect by scanning the QR code, please click here to refresh the network and then scan the code again to retry"; the prompt message 643 "Other connection methods: click 'Manual connection' below the QR code scanning interface on the old device to connect to the following WiFi" and other operation prompt messages for assisting the user in establishing a connection between the old and new devices are not limited herein.

[0112] Based on the above, it is possible to use Figure 5C the scanning control 532 of the old mobile phone 10 shown in Figure 6D to scan the QR code 641 of the new mobile phone 20 shown in

[0113] S102: In response to the user's operation of selecting data, determine the data to be sent.

[0114] In some embodiments, based on the above step S101, the old mobile phone 10 and the new mobile phone 20 have established a communication connection, and further, the data to be migrated to the new mobile phone 20 can be selected on the old mobile phone 10.

[0115] Reference Figure 7A Regarding the interface 710 of the new mobile phone 20 shown in

[0116] Reference Figure 7B Regarding the 720 of the old mobile phone 10 shown in

[0117] Based on the user clicking "Next", the old mobile phone 10 can display a data sending interface 730 as shown in Figure 7C , and the new mobile phone 20 can display a data receiving interface 750 as shown in Figure 7E . It can be understood that the information displayed on the data sending interface 730 can refer to the data sending interface shown in the above Figure 1A , and the information displayed on the data receiving interface 750 can refer to the above Figure 1BThe data sending interface shown will not be elaborated here.

[0118] S103: Display the data sending interface.

[0119] In some embodiments, based on the above Figure 7B In [the above], after the user clicks "Next", the old mobile phone 10 displays the Figure 7C data sending interface 730 as shown. In the data sending interface 730, data sending information is displayed. The data sending information may include various application icons, corresponding application names (such as contacts, messages, call records, notes, recordings, etc.), the percentage of data sending progress, rate, and remaining sending time for each application. Moreover, the data sending interface of the old mobile phone 10 may display a prompt message "Do not leave this page" to prompt the user not to leave the data migration page to avoid interruption during the data migration process. It also includes a "Cancel" control for canceling the data migration process of the old mobile phone 10.

[0120] S104: Determine whether the data has been sent successfully.

[0121] If the judgment result is yes, then perform the following step S105, and the old mobile phone 10 displays a cloning completion interface.

[0122] If the judgment result is no, then perform step S106 to determine whether a user operation is received or a notification pop-up window is detected on the data sending interface within a preset duration.

[0123] Exemplarily, during the process of the old mobile phone 10 sending the data to be migrated to the new mobile phone 20, the old mobile phone 10 can determine in real time whether the data to be migrated has been sent successfully.

[0124] In some embodiments, the old mobile phone 10 can detect in real time whether the sending of the data to be migrated is completed. If the old mobile phone 10 has completed the sending of the data to be migrated, it can display a data migration success interface. For example, Figure 7G shows a data migration success interface 770 displayed on the old mobile phone 10 after the data has been sent successfully. In the interface 770, prompt messages 771 "Please do not clean up the data temporarily after sending is completed to avoid data omission and inability to retrieve", 772 "117 items migrated successfully", 772 "Trade in for new, green environmental protection, reuse of idle mobile phones", and an operation control 773 indicating "Got it" are displayed. Based on this, the old mobile phone 10 can determine that the data to be migrated has been sent successfully.

[0125] In some other embodiments, if the old mobile phone 10 displays Figure 7C the data sending interface 730 of the old mobile phone 10 as shown, it can be determined that the data to be migrated has not been sent successfully.

[0126] S105: Display the cloning completion interface.

[0127] In some embodiments, if the old mobile phone 10 has completed the sending of the data to be migrated, the old mobile phone 10 may display a data migration success interface 770 as shown in Figure 7G . The prompt message 771 "Sending completed" shown in Figure 7G can indicate that the old mobile phone 10 has completed the sending of the data to be migrated. And Figure 7G a prompt message for trade-in can also be displayed. For example: "Trade-in, green environmental protection, reuse of idle mobile phones", etc., which are not limited herein.

[0128] It can be understood that the success of data migration can mean that the sending of the data to be migrated is completed, or that the cloning of the data to be migrated is completed, that is, the old mobile phone 10 has successfully sent the data to be migrated; the success of data migration can also mean that the old mobile phone 10 has successfully sent the data to be migrated, and the new mobile phone 20 has successfully received (restored) the data to be migrated, and the old mobile phone 10 and the new mobile phone 20 have completed the replacement of mobile phones.

[0129] S106: Determine whether a user operation is received or a notification pop-up window is detected on the data sending interface within a preset duration.

[0130] If the judgment result is yes, return to continue to execute this step S106 for judgment.

[0131] If the judgment result is no, execute the following step S107, add an AOD layer, and the old mobile phone 10 displays a cloned AOD interface 740 as shown in Figure 7D .

[0132] Exemplarily, after determining that the data has not been sent completed based on the above step S104, it can be further determined whether Figure 7C a user operation is received or a notification pop-up window is detected on the data sending interface 730 of the old mobile phone 10 shown in within a preset duration. The preset duration can be any reasonably set duration, including any value within 0s to 30s. For example, it is determined whether the screen of the old mobile phone 10 has not been clicked or voice-activated by the user for 15s continuously, or it is determined whether the screen of the old mobile phone 10 has not detected a notification pop-up window for 15s continuously.

[0133] It can be understood that using 15s as a time unit to judge whether there is no operation on the data sending interface in the embodiments of the present application is only an exemplary illustration. In other embodiments, the preset duration can also be any duration less than or equal to 1 minute, such as 5s, 10s, 12s, 30s, etc., which are not limited herein.

[0134] It can be understood that the cloned AOD interface displayed on the old mobile phone 10 can refer to the cloned AOD interface 740 (which is also a data sending interface) of the old mobile phone 10 as shown in Figure 7D .Figure 7C Compared with the data sending interface 730 of the old mobile phone 10 shown, Figure 7D The cloned AOD interface 740 of the old mobile phone 10 shown can be understood as a data sending interface that controls a partial area of the screen of the old mobile phone 10 to light up without lighting up the entire screen of the old mobile phone 10, and only continuously displays the key information of data migration.

[0135] It can be understood that it can be determined based on whether the old mobile phone 10 recognizes operations such as clicks, long presses, and swipes by the user within a preset duration or whether the old mobile phone 10 receives a voice command issued by the user Figure 7C whether the data sending interface 730 of the old mobile phone 10 shown is operated, which is not limited here.

[0136] S107: Display the cloned AOD interface.

[0137] In some embodiments, when it is determined that Figure 7C the data sending interface 730 of the old mobile phone 10 shown has no operation or no notification pop-up window is detected for a preset duration, an AOD layer is added to the screen of the old mobile phone 10, and the old mobile phone 10 displays the cloned AOD interface 740 as shown in Figure 7D Shown. As shown in Figure 7D , only the key information of data migration can be displayed in the cloned AOD interface of the old mobile phone 10. For example: "Sending", data sending progress percentage "5.5%", "4.92GB sent", "Rate 118MB / second", "Remaining time for sending data 13 minutes", etc. It can be understood that if the user wants to return to the data sending interface 730 of the old mobile phone 10 as shown in Figure 7C , then the "Tap to return" in Figure 7D can be clicked.

[0138] Figure 7D Compared with the data sending interface 730 of the old mobile phone 10 shown above Figure 7C , the display elements on the cloned AOD interface 740 of the old mobile phone 10 are fewer, the display brightness is lower, and the display power consumption is lower.

[0139] S108: Determine whether the data sending is completed, or whether the cloned AOD interface receives a user operation, or a notification pop-up window is detected.

[0140] If the judgment result is yes, then execute the following step S109 to exit the display of the cloned AOD interface.

[0141] If the judgment result is no, then return to this step S108 to continue the judgment.

[0142] When it is determined based on the above step S107 that the cloned AOD interface as shown has been displayed on the old mobile phone 10Figure 7D For the cloned AOD interface 740 shown, it is possible to further determine whether the data to be migrated has been sent successfully or whether, as Figure 7D shown in the cloned AOD interface 740, a user operation has been received, or a notification pop-up window has been detected.

[0143] S109: Exit the display of the cloned AOD interface.

[0144] In some embodiments, when, based on the above step S108, it is determined that Figure 7D the cloned AOD interface 740 of the old mobile phone 10 shown has been operated, such as clicked, long-pressed, swiped, or voice-activated, and the data to be migrated has been sent successfully, the AOD layer can be removed, that is, the old mobile phone 10 does not display the cloned AOD interface 740 as Figure 7D shown, but instead displays the data migration success interface 770 as shown in Figure 7G .

[0145] In some other embodiments, when, based on the above step S108, it is determined that the cloned AOD interface 740 of the old mobile phone 10 has been operated, such as clicked, long-pressed, or voice-activated, but the data to be migrated has not been sent successfully yet, the AOD layer can be removed, that is, the old mobile phone 10 does not display the cloned AOD interface 740 as Figure 7D shown, but instead displays the data sending interface 730 of the old mobile phone 10 as shown in Figure 7C .

[0146] In some other embodiments, when a notification pop-up window appears in the cloned AOD interface 740 of the old mobile phone 10, the old mobile phone 10 also exits the display of the cloned AOD interface 740 as Figure 7D shown, but instead displays the data sending interface 730 of the old mobile phone 10 as shown in Figure 7C .

[0147] Based on the above solution, in the scenario of changing mobile phones, the display interface of the old mobile phone 10 can enter the cloned AOD interface 740 as shown in Figure 7D under corresponding conditions, only displaying the key information of data migration, and the screen display brightness, screen refresh frame rate, etc. of the old mobile phone 10 are reduced, so that the display power consumption of the old mobile phone 10 during the process of changing mobile phones is reduced, improving the user experience of changing mobile phones.

[0148] Combined with the above Figure 4 shown implementation process of the display method, Figure 8 According to the embodiments of the present application, a schematic flow diagram of a display method for executing system services based on the old mobile phone 10 is provided.

[0149] It can be understood that in the embodiments of the present application, Figure 8The execution entity of each step in the shown process can be the system service of the old mobile phone 10, such as the Serviceflinger service. In some other embodiments, Figure 8 the execution entity of each step in the shown process can also be the system service of electronic devices such as tablet computers, smart wearable devices, smart home devices, in-vehicle devices, etc., which is not limited herein.

[0150] Refer to Figure 8 , and the specific process includes:

[0151] S201: Boot up.

[0152] In some embodiments, the old mobile phone 10 can start up the Service flinger service and run it when booting up.

[0153] It can be understood that the Serviceflinger service can listen to the change of the system layer of the old mobile phone 10 by calling back the change of the interface display state of the device.

[0154] S202: Register the callback for the change of the interface display state.

[0155] In some embodiments, the Serviceflinger service can register the interface display state callback with the Service Manager, and listen to the change of the system display layer corresponding to the change of the display interface in real time by calling back the change of the interface display state of the device.

[0156] As an example, the code called back by the Serviceflinger service can be, for example, "com.hihonor.android.clone / com.hihonor.android.clone.activity.sender.OldPhoneExecuteActivity", where OldPhone can represent the old mobile phone 10, and based on this, it can represent that the old mobile phone 10 displays Figure 7C the data sending interface 730 shown, and when performing data migration, that is, sending the data to be migrated.

[0157] S203: Based on the change of the interface display state, determine whether the old mobile phone 10 is displaying the data sending interface.

[0158] If the judgment result is yes, then execute the following step S204, that is, listen to the change of the system layer of the old mobile phone 10.

[0159] If the judgment result is no, then execute the following step S212, that is, do not listen to the change of the system layer of the old mobile phone 10, but judge whether the system of the old mobile phone 10 is in the low power consumption mode.

[0160] Exemplarily, based on the change in the display state of the Serviceflinger callback interface in step S202, the obtained interface display state can be used to determine whether the old mobile phone 10 is currently displaying a data sending interface 730 as shown in Figure 7C shown.

[0161] S204: Monitor the change in the system layer of the old mobile phone 10.

[0162] In some embodiments, based on step S202, it is determined that the old mobile phone 10 enters a data sending interface 730 as shown in Figure 7C shown. The Serviceflinger service of the old mobile phone 10 can obtain the change in the interface display state of the old mobile phone 10 by callback. Based on the data sending interface 730 shown for the old mobile phone 10, the Serviceflinger service of the old mobile phone 10 can start monitoring the change in the system layer of the old mobile phone 10. Figure 7C shown.

[0163] S205: Based on the monitoring result, determine whether there is a change in the system display layer of the old mobile phone 10.

[0164] If the judgment result is yes, then execute the following step S206, that is, traverse the system layer cache of the old mobile phone 10.

[0165] If the judgment result is no, then return to step S204 to continue the judgment.

[0166] Based on the monitoring of the system layer of the old mobile phone 10 in step S204, it can be determined whether there is a change in the system display layer of the old mobile phone 10. For example, the system layer of the old mobile phone 10 increases or decreases.

[0167] S206: Traverse the system layer cache of the old mobile phone 10.

[0168] In some embodiments, by traversing the system layer cache of the old mobile phone 10, it can be used to determine whether the cloned AOD layer corresponding to the cloned AOD interface of the old mobile phone 10 exists and is at the top layer of the system layer cache.

[0169] It can be understood that the system layer cache of the old mobile phone 10 can be used to temporarily store the system layer of the old mobile phone 10. When it is determined in step S205 above that the system layer of the old mobile phone 10 has changed, the Serviceflinger service can traverse the system layer cache of the old mobile phone 10 to determine whether there are new or reduced system layers in the system layer cache of the old mobile phone 10.

[0170] For example, when the old mobile phone 10 changes from Figure 7C the data sending interface 730 shown to Figure 7DWhen cloning the AOD interface 740 as shown, a system layer corresponding to the cloned AOD interface is newly added to the system layer cache of the old mobile phone 10. Based on this, by traversing the system layer cache of the old mobile phone 10, the Serviceflinger service can find that a cloned AOD layer corresponding to the cloned AOD interface is newly added in the old mobile phone 10.

[0171] S207: Determine whether the cloned AOD layer of the old mobile phone 10 exists and is at the top layer.

[0172] If the judgment result is yes, then execute the following step S208 to continue to determine whether there is a notification pop-up window displayed on the old mobile phone 10.

[0173] If the judgment result is no, then execute the following step S212 to determine whether the system of the old mobile phone 10 is in the low-power mode.

[0174] By traversing the system layer cache of the old mobile phone 10 in the above step S206, it can be determined whether the cloned AOD layer of the old mobile phone 10 exists and is at the top layer. If the cloned AOD layer of the old mobile phone 10 exists and is at the top layer, it can indicate that the screen of the old mobile phone 10 meets one of the prerequisite conditions for entering the AOD mode.

[0175] When the cloned AOD layer of the old mobile phone 10 exists and is at the top layer, it is necessary to further determine that there is no notification pop-up window displayed in the cloned AOD interface corresponding to the cloned AOD layer. When there is no notification pop-up window displayed in the cloned AOD interface, the system of the old mobile phone 10 also needs to meet the condition that it is not in the low-power mode for the screen of the old mobile phone 10 to enter the AOD mode.

[0176] In some embodiments, the Serviceflinger service of the old mobile phone 10 can traverse the system layer cache of the old mobile phone 10 to determine whether the cloned AOD layer of the old mobile phone 10 exists and is at the top layer of the system layer cache of the old mobile phone 10.

[0177] For example, the Serviceflinger service of the old mobile phone 10 can traverse the system layer cache of the old mobile phone 10. If it is found that the system layer ID at the top layer of the system layer cache of the old mobile phone 10 includes "clone_device_aod_view", it can indicate that the cloned AOD layer of the old mobile phone 10 exists and is at the top layer of the system layer cache of the old mobile phone 10.

[0178] It can be understood that the cloned AOD layer of the old mobile phone 10 can refer to the system layer corresponding to the cloned AOD interface 740 above Figure 7D in.

[0179] It can be understood that the low-power mode refers to a mode in which the system of the electronic device operates with low display power consumption. In the low-power mode, the screen refresh frame rate of the electronic device and the power consumption of screen-related loads are both low. The screen-related loads may include the screen refresh frame rate, the screen display brightness, etc., which are not limited herein.

[0180] S208: Determine whether there is a notification pop-up window displayed.

[0181] If the judgment result is no, then execute the following step S209 to determine whether the system of the old mobile phone 10 is in the low-power mode.

[0182] If the judgment result is yes, then execute the following step S212 to determine whether the system of the old mobile phone 10 is in the low-power mode.

[0183] In some embodiments, when based on the above step S207, it is determined that there is a cloned AOD layer in the system layer cache of the old mobile phone 10 and it is at the top layer of the system layer cache of the old mobile phone 10. Then, it can be further determined whether there is a notification pop-up window displayed in the old mobile phone 10 through the Serviceflinger service callback.

[0184] S209: Determine whether the system is currently in the low-power mode.

[0185] If the judgment result is yes, then end the process.

[0186] If the judgment result is no, then execute the following step S210 to call the power interface to notify the screen of the old mobile phone 10 to enter the AOD mode.

[0187] In some embodiments, when based on the above step S208, it is determined that there is no notification pop-up window displayed in the old mobile phone 10, indicating that the cloned AOD layer of the old mobile phone 10 exists and is at the top layer of the system layer cache of the old mobile phone 10. Further, determine whether the system of the old mobile phone 10 is in the low-power mode.

[0188] S210: Call the power interface to control the screen to enter the AOD mode.

[0189] In some embodiments, based on the determination in step S209 that the system of the old mobile phone 10 is not in the low-power mode, and combined with the determination in steps S207 - S208 that the cloned AOD layer of the old mobile phone 10 exists and is at the top layer of the system layer cache of the old mobile phone 10, and there is no notification pop-up window displayed in the old mobile phone 10, then the power interface can be called through the Serviceflinger service to control the screen of the old mobile phone 10 to enter the AOD mode. Among them, the AOD mode means that the brightness of the screen of the old mobile phone 10 is reduced or directly blacked out, and only the key information of data migration is displayed.

[0190] S211: Control to reduce the screen refresh frame rate and the CPU screen-related load.

[0191] In some embodiments, after the screen of the old mobile phone 10 enters the AOD mode, the Serviceflinger service can control to reduce the screen refresh frame rate and the CPU screen-related load of the old mobile phone 10. For example, the default screen refresh frame rate of 60HZ or 120HZ when the old mobile phone 10 is normally displayed is reduced to less than or equal to 30HZ. Also for example, the Serviceflinger service can control to reduce the CPU screen-related load, such as reducing the CPU's handling of screen contrast, color, resolution, etc.

[0192] S212: Determine whether the system is currently in the low-power mode.

[0193] If the determination result is yes, then execute the following step S213, call the power interface to notify the screen of the old mobile phone 10 to exit the AOD mode.

[0194] If the determination result is no, then end the process.

[0195] Exemplarily, when it is determined based on step S203 that the old mobile phone 10 does not display the data sending interface 730 as shown Figure 7C then do not listen to the system layer change of the old mobile phone 10, and determine whether the system of the old mobile phone 10 is in the low-power mode through the Serviceflinger service.

[0196] Or, when it is determined based on step S207 that the cloned AOD layer of the old mobile phone 10 does not exist and is not at the top layer of the system layer cache of the old mobile phone 10, or there is a notification pop-up window displayed on the old mobile phone 10. Further determine whether the system of the old mobile phone 10 is in the low-power mode.

[0197] S213: Call the power interface to control the screen to exit the AOD mode.

[0198] In some embodiments, when it is determined based on step S212 that the system of the old mobile phone 10 is in the low-power mode, or when it is determined based on step S207 that the current cloned AOD layer of the old mobile phone 10 does not exist, and it is determined based on S208 that there is a notification pop-up window displayed on the old mobile phone 10, then the Serviceflinger service can call the power interface to control the screen of the old mobile phone 10 to exit the AOD mode. Based on the fact that the system of the old mobile phone 10 is not in the scenario where it needs to enter the AOD mode, the screen of the old mobile phone 10 can exit the AOD mode and run in the normal working state.

[0199] S214: Control to restore the screen refresh frame rate and the CPU screen-related processing strategy.

[0200] In some embodiments, after the screen of the old mobile phone 10 exits the AOD mode, the screen refresh rate and the CPU screen-related load of the old mobile phone 10 can be restored through the Serviceflinger service. For example, the default screen refresh rate of the old mobile phone 10, which is 60HZ or 120HZ, is reduced to less than or equal to 30HZ, where 60HZ or 120HZ can be the screen refresh rate of the old mobile phone 10 when it is in a normal operating state. For another example, the Serviceflinger service can notify the CPU to restore the load processing policy for the screen of the old mobile phone 10, such as restoring the screen brightness, screen contrast, color, resolution, etc. of the old mobile phone 10.

[0201] It can be understood that using "30HZ" as the screen refresh rate of the old mobile phone 10 in the AOD mode in the embodiments of the present application is only an exemplary illustration. In some other embodiments, the screen refresh rate of the old mobile phone 10 in the AOD mode can also be less than or equal to 30HZ, which is not limited herein.

[0202] It can be understood that using "60HZ or 120HZ" as the default screen refresh rate of the old mobile phone 10 in the embodiments of the present application is only an exemplary illustration. In some other embodiments, the default screen refresh rate of the old mobile phone 10 can also be 60HZ to 360HZ, such as 75HZ, 144HZ, 165HZ, 240HZ, 360HZ, etc., which is not limited herein.

[0203] Based on the above solution, in the mobile phone replacement scenario, the display interface of the old mobile phone 10 can enter the cloned AOD interface 740 as shown, which only displays the key information for data migration, and the screen display brightness, screen refresh rate, etc. of the old mobile phone 10 are reduced, so that the display power consumption of the old mobile phone 10 during mobile phone replacement is reduced, and the user's mobile phone replacement experience is also improved. Figure 7D shown, only displaying the key information for data migration, and the screen display brightness, screen refresh rate, etc. of the old mobile phone 10 are reduced, so that the display power consumption of the old mobile phone 10 during mobile phone replacement is reduced, and the user's mobile phone replacement experience is also improved.

[0204] It can be understood that in some embodiments, the Figure 4 shown display method and the Figure 8 shown implementation process of the display method based on the combined system service of the old mobile phone 10 can be combined.

[0205] For example, Figure 9 According to the embodiments of the present application, a schematic diagram of the macroscopic process of data migration of an old mobile phone 10 is shown. As Figure 9 shown, this macroscopic process can include the steps executed by the old mobile phone 10 shown above and the steps executed by the Serviceflinger service shown above. The following combines Figure 4 shown and Figure 8 shown. The following combines with Figure 4 , Figure 8 and Figure 9The implementation process shown details the logical relationship between the steps executed by the old mobile phone 10 and the steps executed by the Serviceflinger service.

[0206] Specifically, when the UI interface of the old mobile phone 10 enters Figure 7C the data sending interface 730 shown in S103, in S202, the change in the display state of the interface can be called back based on the Serviceflinger service, and then in S203, it can be determined that the UI interface of the old mobile phone 10 is displaying Figure 7C the data sending interface 730 shown.

[0207] When the UI interface of the old mobile phone 10 enters Figure 7G the data migration success interface 770 of the old mobile phone 10 shown in S105, in S202, the change in the display state of the interface can be called back based on the Serviceflinger service, and then in S203, it can be determined that the UI interface of the old mobile phone 10 does not display Figure 7C the data sending interface 730 shown.

[0208] When a new AOD layer is added to the old mobile phone 10 in S107 and the old mobile phone 10 displays Figure 7D the cloned AOD interface 740 of the old mobile phone 10 shown, that is, when the old mobile phone 10 changes from Figure 7C the data sending interface 730 shown to Figure 7D the cloned AOD interface 740 shown, in S204, the change in the system layer of the old mobile phone 10 can be monitored based on the Serviceflinger service. For example, a new Figure 7D system layer corresponding to the cloned AOD interface 740 of the old mobile phone 10 shown is added to the system layer cache of the old mobile phone 10.

[0209] When the old mobile phone 10 does not display Figure 7D the cloned AOD interface 740 of the old mobile phone 10 shown in S109, that is, when the old mobile phone 10 changes from Figure 7D the cloned AOD interface 740 shown to Figure 7C the data sending interface 730 shown, in S204, the change in the system layer of the old mobile phone 10 can be monitored based on the Serviceflinger service of the old mobile phone 10. For example, the system layer cache of the old mobile phone 10 decreases by Figure 7D the system layer corresponding to the cloned AOD interface 740 of the old mobile phone 10 shown.

[0210] Based on the above, through the System Service Serviceflinger service of the old mobile phone 10, the change in the interface display status can be called back to monitor the change in the system layer of the old mobile phone 10 in real time. Finally, according to the operating mode of the system of the old mobile phone 10, such as the low-power mode and the non-low-power mode, and by calling the power interface, the screen of the old mobile phone 10 can work in the screen display mode corresponding to the system operating mode.

[0211] For example, when the system of the old mobile phone 10 is not in the low-power mode but meets the conditions for being in the low-power mode. Exemplarily, the cloned AOD layer of the old mobile phone 10 exists and is at the top layer of the system layer cache of the old mobile phone 10, and there is no notification pop-up window display on the UI interface of the old mobile phone 10. Then, the power interface can be called to make the screen of the old mobile phone 10 enter the AOD mode to reduce the screen display power consumption of the old mobile phone 10.

[0212] Again, for example, when the system of the old mobile phone 10 is in the low-power mode but does not meet the conditions for being in the low-power mode. Exemplarily, the old mobile phone 10 does not display the data sending interface 730 as shown in Figure 7C The cloned AOD layer of the old mobile phone 10 does not exist and is not at the top layer of the system layer cache of the old mobile phone 10, and there is a notification pop-up window display on the UI interface of the old mobile phone 10. Then, the power interface can be called to make the screen of the old mobile phone 10 exit the AOD mode.

[0213] It can be understood that in the Figure 9 In the process shown, S201 can be executed before S101; S202 and S203 can be executed after S103 and before S107; S204 can be executed after S107, or executed after S109, which is not limited herein.

[0214] Based on the above solution, in the scenario of changing mobile phones, the display interface of the old mobile phone 10 can enter the cloned AOD interface 740 as shown in Figure 7D under corresponding conditions, only display the key information of data migration, and the screen of the old mobile phone 10 enters the AOD mode. The screen display brightness, screen refresh frame rate, etc. of the old mobile phone 10 are reduced, so that the display power consumption of the old mobile phone 10 during mobile phone replacement is reduced, improving the user experience of mobile phone replacement.

[0215] Next, a detailed description will be given of the specific implementation process of the display method provided in the embodiments of the present application on the new mobile phone 20.

[0216] Figure 10 According to the embodiments of the present application, a schematic diagram of the implementation process of another display method is shown.

[0217] It can be understood that in the embodiments of the present application, Figure 10The execution entity of each step in the shown process may be the new mobile phone 20. In some other embodiments, Figure 10 the execution entity of each step in the shown process may also be an electronic device such as a tablet computer, a smart wearable device, a smart home device, a vehicle-mounted device, etc., which is not limited herein.

[0218] Specifically, Figure 10 the shown process may include the following steps:

[0219] S301: Display a QR code based on the cloning application.

[0220] In some embodiments, in order to implement the replacement of the old mobile phone 10 with the new mobile phone 20, the old mobile phone 10 needs to scan the QR code displayed on the new mobile phone 20 to establish a connection between the old mobile phone 10 and the new mobile phone 20, so as to start the replacement process of the old and new mobile phones.

[0221] Therefore, the new mobile phone 20 needs to display the QR code 641 as shown in the above Figure 6D for the scanning control 532 of the old mobile phone 10 in Figure 5C to scan the QR code 641 displayed on the new mobile phone 20 in Figure 6D to implement the connection between the new mobile phone 20 and the old mobile phone 10.

[0222] S302: Establish a connection with the old mobile phone 10.

[0223] In some embodiments, based on the above step S301, after the old mobile phone 10 scans the QR code 641 displayed on the new mobile phone 20, the connection between the new mobile phone 20 and the old mobile phone 10 can be achieved. For example Figure 7A it is shown in the interface 710 of the new mobile phone 20 that the old mobile phone 10 and the new mobile phone 20 have been successfully connected, and a prompt message 711 "Please select the data to be migrated on the old device" is displayed.

[0224] S303: Display a data receiving interface.

[0225] In some embodiments, based on Figure 7B the user clicks "Next", the new mobile phone 20 receives the data to be migrated sent from the old mobile phone 10 and displays the data receiving interface 750 of the new mobile phone 20 as shown in Figure 7E . Figure 7EIn the data receiving interface 750 shown, data receiving information is displayed. The data receiving information may include various application icons, corresponding application names (such as contacts, messages, call records, notes, recordings, etc.), the percentage of data receiving progress, rate, remaining receiving time, etc. of each application. Moreover, the data receiving interface 750 of the new mobile phone 20 may display a prompt message "Do not leave this page" to prompt the user not to leave the data migration page to avoid interruption during the data migration process. It also includes a "Cancel" control for canceling the data migration process of the new mobile phone 20.

[0226] S304: Determine whether the data has been received or restored completely.

[0227] If the judgment result is yes, then execute the following step S305, display the cloning completion interface, and the current process can be ended.

[0228] If the judgment result is no, then continue to execute the following step S306 to determine whether the data receiving interface has received a user operation or detected a notification pop-up window within a preset duration.

[0229] In some embodiments, during the process of the new mobile phone 20 receiving the data to be migrated sent by the old mobile phone 10, the new mobile phone 20 can detect in real time whether the data to be migrated has been received completely. If the new mobile phone 20 has received or restored the data to be migrated completely, then a data migration success interface can be displayed. For example, Figure 7H Shows a data migration success interface 780 displayed on the new mobile phone 20 after the data has been received. In the interface 780, prompt messages 781 "77GB of data has been migrated, total time taken is 24 minutes", 782 "117 items have been migrated successfully", 783 "1 item has failed to migrate", and an operation control 784 indicating "Complete" are displayed. Based on this, it can be determined that the data to be migrated has been received or restored completely.

[0230] In some other embodiments, if the new mobile phone 20 displays the data receiving interface 750 of the new mobile phone 20 as described above Figure 7E shown, then it can be determined that the data to be migrated has not been received or restored completely.

[0231] S305: Display the cloning completion interface.

[0232] In some embodiments, if the new mobile phone 20 has completed the reception or restoration of the data to be migrated, then the data migration success interface 780 as Figure 7H shown can be displayed on the new mobile phone 20. As Figure 7H the prompt message 781 "Migration completed" shown in it can indicate that the new mobile phone 20 has completed the reception or restoration of the data to be migrated. And Figure 7HIt can also display the amount of data that the new mobile phone 20 has received or restored, the total time taken, the number of successfully migrated items, and the number of failed migration items. For example: "77GB of data has been migrated", "The total time taken is 24 minutes", "117 items have been successfully migrated", "1 item has failed to migrate", etc. There is no limitation here.

[0233] It can be understood that successful data migration can mean that data reception or restoration is completed, or that data cloning is completed. It can be understood that the new mobile phone 20 has successfully received or restored the data to be migrated, and the new mobile phone 20 and the old mobile phone 10 have completed the replacement of mobile phones.

[0234] S306: Determine whether the data reception interface has received a user operation or detected a notification pop-up window within a preset duration.

[0235] If the judgment result is yes, continue to execute step S306.

[0236] If the judgment result is no, execute the following step S307, add an AOD layer, and the new mobile phone 20 displays the cloned AOD interface.

[0237] Exemplarily, after determining that the data has not been completely sent based on the above step S304, it can be further determined Figure 7E whether the data reception interface 750 of the new mobile phone 20 shown has received a user operation or detected a notification pop-up window within a preset duration. This preset duration can be any reasonably set duration, including any value within 0s to 30s. For example, determine whether the screen of the new mobile phone 20 has not been clicked or voice-activated by the user for 15s continuously, or determine whether the screen of the new mobile phone 20 has not detected a notification pop-up window for 15s continuously.

[0238] It can be understood that using 15s as a time unit to determine whether there is no operation on the data sending interface in the embodiments of the present application is only an exemplary illustration. In other embodiments, the preset duration can also be any duration less than or equal to 1 minute, such as 5s, 10s, 12s, 30s, etc. There is no limitation here.

[0239] It can be understood that the cloned AOD interface here can refer to the cloned AOD interface 760 of the new mobile phone 20 as shown in Figure 7F and can also be called the data reception AOD interface of the new mobile phone 20. Figure 7F Compared with the data reception interface 750 of the new mobile phone 20 shown above Figure 7E the cloned AOD interface 760 of the new mobile phone 20 can be understood as a data reception interface that controls a partial area of the screen of the new mobile phone 20 to light up and only continuously displays the key information of data migration without lighting up the entire screen of the new mobile phone 20.

[0240] In some embodiments, it can be determined based on whether the new mobile phone 20 recognizes a user's click, long press, key operation within a preset time, such as 15 s, or whether the new mobile phone 20 receives a voice command issued by the user, Figure 7F whether the data receiving interface of the new mobile phone 20 shown is operated.

[0241] It can be understood that using 15 s as a time unit to determine whether there is no operation on the data sending interface in the embodiments of the present application is only an exemplary illustration. In some other embodiments, the preset time can also be less than or equal to 1 min, such as 5 s, 10 s, 12 s, 30 s, etc., which is not limited herein.

[0242] S307: Display the cloned AOD interface.

[0243] In some embodiments, when it is determined that Figure 7F after the data receiving interface 750 of the new mobile phone 20 shown has not detected an operation for 15 s, an AOD layer is added to the screen of the new mobile phone 20, and the cloned AOD interface 760 as shown in Figure 7E is displayed on the new mobile phone 20. As shown in Figure 7E , only key information of data migration can be displayed in the cloned AOD interface 760 of the new mobile phone 20. For example: "Receiving", data receiving progress percentage "5.5%", "Received 4.92 GB", "Rate 118 MB / s", "Remaining time for receiving data 13 minutes", etc.

[0244] Figure 7E Compared with the data receiving interface 750 of the new mobile phone 20 shown above in Figure 7F , the cloned AOD interface 760 of the new mobile phone 20 has fewer display elements, lower display brightness, and lower display power consumption.

[0245] It can be understood that if the user wants to return to the data sending interface 750 of the old mobile phone 10 as shown in Figure 7E , they can click "Tap to return" in Figure 7F .

[0246] S308: Determine whether the cloned AOD interface receives a user operation, or data receiving or recovery is completed, or a notification pop-up window is detected.

[0247] If the judgment result is yes, execute the following step S309 to exit the display of the cloned AOD interface.

[0248] If the judgment result is no, return to this step S308 to continue the judgment.

[0249] When it is determined based on the above step S307 that the cloned AOD interface as shown in Figure 7FThe cloned AOD interface 760 shown can be further used to determine, for example, Figure 7F whether the cloned AOD interface 760 shown has been operated, or whether the data to be migrated has been received or restored, or whether a notification pop-up window has been detected.

[0250] S309: Exit the display of the cloned AOD interface.

[0251] In some embodiments, when, based on the above step S308, it is determined that the cloned AOD interface 760 of the new mobile phone 20 shown, for example, Figure 7F has been operated such as clicked, long-pressed, voice-activated, etc., and the data to be migrated has been received or restored, then the AOD layer can be removed, that is, the new mobile phone 20 does not display the cloned AOD interface 760 shown Figure 7F , but instead displays the data migration success interface 780 shown Figure 7H as shown in.

[0252] In other embodiments, when, based on the above step S308, it is determined that the cloned AOD interface 760 of the new mobile phone 20 has been operated such as clicked, long-pressed, voice-activated, etc., but the data to be migrated has not been received or restored yet, then the AOD layer can be removed, that is, the new mobile phone 20 does not display the cloned AOD interface 760 shown Figure 7F , but instead displays the data receiving interface 750 shown Figure 7E as shown in.

[0253] In other embodiments, when pop-up information appears in the cloned AOD interface 760 of the new mobile phone 20, the new mobile phone 20 also exits the display of the cloned AOD interface 760 shown Figure 7F , but instead displays the data receiving interface 750 of the new mobile phone 20 shown Figure 7E as shown in.

[0254] Based on the above solution, in the scenario of changing mobile phones, the display interface of the new mobile phone 20 can enter the display of the cloned AOD interface 760 shown Figure 7F under corresponding conditions, only displaying the key information of data migration, and the screen display brightness, screen refresh frame rate, etc. of the new mobile phone 20 are reduced, so that the display power consumption of the new mobile phone 20 during mobile phone replacement is reduced, improving the user experience of mobile phone replacement.

[0255] Combined with the above Figure 10 shown implementation process of the display method, Figure 11 According to the embodiments of the present application, a flow diagram of a display method for executing system services based on the new mobile phone 20 is provided.

[0256] It can be understood that in the embodiments of the present application, Figure 11The execution entity of each step in the shown process may be a system service of the new mobile phone 20, such as the Serviceflinger service. In some other embodiments, Figure 11 the execution entity of each step in the shown process may also be a system service of an electronic device such as a tablet computer, a smart wearable device, a smart home device, a vehicle-mounted device, etc., which is not limited herein.

[0257] Refer to Figure 11 , and the specific process includes:

[0258] S401: Boot up.

[0259] In some embodiments, when the new mobile phone 20 boots up, it can start the process where the Surfaceflinger service is located and run the Surfaceflinger service. That is, the Surfaceflinger service can be started and run when the new mobile phone 20 boots up.

[0260] S402: Register a callback for the change in the interface display status.

[0261] In some embodiments, the Serviceflinger service can register an interface display status callback with the Service Manager, and by calling back the change in the interface display status of the device, it can listen in real time to the change in the system display layer corresponding to the change in the display interface.

[0262] As an example, the code for the callback of the Serviceflinger service may be, for example, "com.hihonor.android.clone / com.hihonor.android.clone.activity.receiver.NewPhoneExecuteActivity", where NewPhone can represent the new mobile phone 20, and based on this, it can represent that the new mobile phone 20 displays Figure 7E the data reception interface 750 shown, and during data migration, that is, receiving the data to be migrated.

[0263] S403: Based on the change in the interface display status, determine whether the new mobile phone 20 is currently displaying a data reception or recovery interface.

[0264] If the judgment result is yes, then execute the following step S404, that is, listen to the change in the system layer of the new mobile phone 20.

[0265] If the judgment result is no, then execute the following step S412, that is, do not listen to the change in the system layer of the new mobile phone 20, but determine whether the system of the new mobile phone 20 is in the low-power mode.

[0266] Exemplarily, based on the change in the display state of the Serviceflinger callback interface in step S402, the obtained interface display state can be used to determine whether the new mobile phone 20 is currently displaying as Figure 7E the data receiving interface 750 shown.

[0267] S404: Monitor the change in the system layer of the new mobile phone 20.

[0268] In some embodiments, based on step S402, it is determined that the new mobile phone 20 displays as Figure 7E the data receiving interface 750 shown. The Serviceflinger service of the new mobile phone 20 can callback the change in the state of the display interface of the new mobile phone 20. Based on the new mobile phone 20 being Figure 7E the data receiving interface 750 shown, the Serviceflinger service of the new mobile phone 20 can enable the monitoring of the change in the system layer of the new mobile phone 20.

[0269] S405: Based on the monitoring result, determine whether there is a change in the system display layer of the new mobile phone 20.

[0270] Based on the monitoring of the system layer of the new mobile phone 20 in step S404, it can be determined whether there is a change in the system display layer of the new mobile phone 20. For example, the system layer of the new mobile phone 20 increases or decreases.

[0271] If the judgment result is yes, then execute the following step S406, that is, traverse the system layer cache of the new mobile phone 20.

[0272] If the judgment result is no, then return to this step S404 to continue the judgment.

[0273] S406: Traverse the system layer cache of the new mobile phone 20.

[0274] In some embodiments, by traversing the system layer cache of the new mobile phone 20, it can be used to determine whether the cloned AOD layer corresponding to the cloned AOD interface 760 of the new mobile phone 20 exists and is at the top layer of the system layer cache.

[0275] It can be understood that the system layer cache of the new mobile phone 20 can be used to temporarily store the system layer of the new mobile phone 20. When it is determined in the above step S405 that the system layer of the new mobile phone 20 has changed, the Serviceflinger service can traverse the system layer cache of the new mobile phone 20 to determine whether there are new or reduced system layers in the system layer cache of the new mobile phone 20.

[0276] For example, when the new mobile phone 20 changes from Figure 7E the data receiving interface 750 shown to Figure 7FWhen the cloned AOD interface 760 as shown is involved, a system layer corresponding to the cloned AOD interface 760 is newly added to the system layer cache of the new mobile phone 20. Based on this, by traversing the system layer cache of the new mobile phone 20, the Serviceflinger service can find that a cloned AOD layer corresponding to the cloned AOD interface 760 is newly added in the new mobile phone 20.

[0277] S407: Determine whether the cloned AOD layer of the new mobile phone 20 exists and is at the top layer.

[0278] If the judgment result is yes, then execute the following step S408 to continue to determine whether there is a notification pop-up window displayed on the new mobile phone 20.

[0279] If the judgment result is no, then execute the following step S412 to determine whether the system of the new mobile phone 20 is in the low-power mode.

[0280] By traversing the system layer cache of the new mobile phone 20 in the above step S306, it can be determined whether the cloned AOD layer of the new mobile phone 20 exists and is at the top layer. If the cloned AOD layer of the new mobile phone 20 exists and is at the top layer, it can indicate that the screen of the new mobile phone 20 meets one of the prerequisite conditions for entering the AOD mode.

[0281] When the cloned AOD layer of the new mobile phone 20 exists and is at the top layer, it is necessary to further determine that there is no notification pop-up window displayed in the cloned AOD interface 760 corresponding to the cloned AOD layer. When there is no notification pop-up window displayed in the cloned AOD interface 760, the system of the new mobile phone 20 also needs to meet the condition that it is not in the low-power mode for the screen of the new mobile phone 20 to enter the AOD mode.

[0282] In some embodiments, the Serviceflinger service of the new mobile phone 20 can traverse the system layer cache of the new mobile phone 20 to determine whether the cloned AOD layer of the new mobile phone 20 exists and is at the top layer of the system layer of the new mobile phone 20.

[0283] For example, the Serviceflinger service of the new mobile phone 20 can traverse the system layer cache of the new mobile phone 20. If it is found that the system layer ID at the top layer of the system layer cache of the new mobile phone 20 includes "clone_device_aod_view", it can indicate that the cloned AOD layer of the new mobile phone 20 exists and is at the top layer of the system layer cache of the new mobile phone 20.

[0284] It can be understood that the cloned AOD layer of the new mobile phone 20 can refer to the system layer corresponding to the cloned AOD interface 760 above Figure 7F in.

[0285] It can be understood that the low-power mode refers to a mode in which the electronic device operates with a lower display power consumption. In the low-power mode, the screen refresh frame rate and the power consumption of screen-related loads of the electronic device are both low. The screen-related loads may include the refresh frame rate, brightness, and resolution.

[0286] S408: Determine whether a notification pop-up window is displayed.

[0287] If the judgment result is no, then execute the following step S409 to determine whether the system of the new mobile phone 20 is in the low-power mode.

[0288] If the judgment result is yes, then execute the following step S412 to determine whether the system of the new mobile phone 20 is in the low-power mode.

[0289] In some embodiments, when it is determined based on the above step S407 that there is a cloned AOD layer in the system layer cache of the new mobile phone 20 and it is at the top layer of the system layer cache of the new mobile phone 20, the Serviceflinger service can be further used to call the process status change to determine whether there is a notification pop-up window displayed in the new mobile phone 20.

[0290] S409: Determine whether the system is currently in the low-power mode.

[0291] If the judgment result is yes, then end the process.

[0292] If the judgment result is no, then execute the following step S410 to call the power interface to notify the screen of the new mobile phone 20 to enter the AOD mode.

[0293] In some embodiments, when it is determined in the above step S408 that there is no notification pop-up window displayed in the new mobile phone 20, it means that the cloned AOD layer of the new mobile phone 20 exists and is at the top layer of the system layer cache of the new mobile phone 20. Further, determine whether the system of the new mobile phone 20 is in the low-power mode.

[0294] S410: Call the power interface to control the screen to enter the AOD mode.

[0295] In some embodiments, based on the determination in step S409 that the system of the new mobile phone 20 is not in the low-power mode, and combined with the determination in steps S407 - S408 that the cloned AOD layer of the new mobile phone 20 exists and is at the top layer of the system layer cache of the new mobile phone 20, and there is no notification pop-up window displayed in the new mobile phone 20, the power interface can be called through the Serviceflinger service to control the screen of the new mobile phone 20 to enter the AOD mode. Among them, the AOD mode means that the brightness of the screen of the new mobile phone 20 is reduced or directly blacked out, and only the key information of data migration is displayed.

[0296] S411: Control to reduce the screen refresh frame rate and the CPU screen-related load.

[0297] In some embodiments, when the screen of the new mobile phone 20 enters the AOD mode, the screen refresh frame rate and the CPU screen-related load of the new mobile phone 20 can be reduced. For example, the default screen refresh frame rate of 60HZ or 120HZ when the new mobile phone 20 is normally displayed is reduced to 30HZ. For another example, the Serviceflinger service can control the recovery of the processing policies related to the CPU screen-related load, such as reducing the CPU's control over the screen contrast, color, resolution, etc.

[0298] S412: Determine whether the system is currently in the low-power mode.

[0299] Exemplarily, when it is determined based on step S403 that the new mobile phone 20 does not display the data reception interface 750 as Figure 7E shown, then the change of the system layer of the new mobile phone 20 is not monitored, and it is determined whether the system of the new mobile phone 20 is in the low-power mode.

[0300] Or, when it is determined based on step S407 that the cloned AOD layer of the new mobile phone 20 does not exist and is not at the top layer of the system layer of the new mobile phone 20, or there is a notification pop-up window displayed on the new mobile phone 20. Further determine whether the system of the new mobile phone 20 is in the low-power mode.

[0301] If the judgment result is yes, then execute the following step S413, call the power interface to notify the screen of the new mobile phone 20 to exit the AOD mode.

[0302] If the judgment result is no, then end the process.

[0303] S413: Call the power interface to control the screen to exit the AOD mode.

[0304] In some embodiments, when it is determined based on step S412 that the system of the new mobile phone 20 is in the low-power mode, or when it is determined based on step S407 that the current cloned AOD layer of the new mobile phone 20 does not exist, and based on S408 and there is a notification pop-up window displayed on the new mobile phone 20, then the power interface can be called through the Serviceflinger service to control the screen to exit the AOD mode. At this time, the system of the new mobile phone 20 is not in the scenario where it needs to enter the AOD mode, so the screen of the new mobile phone 20 can exit the AOD mode and run in the normal working state.

[0305] S414: Control to restore the screen refresh frame rate and the CPU screen-related processing policies.

[0306] In some embodiments, when the screen of the new mobile phone 20 exits the AOD mode, the screen refresh rate of the new mobile phone 20 and the CPU screen-related processing policy can be restored. For example, the default screen refresh rate of the new mobile phone 20, which is 60HZ or 120HZ, can be reduced to 30HZ, where 60HZ or 120HZ can be the screen refresh rate when the new mobile phone 20 is in a normal operating state. For another example, the Serviceflinger service can control the restoration of the CPU screen-related processing policy, such as restoring the screen brightness, screen contrast, color, resolution, etc. of the new mobile phone 20.

[0307] It can be understood that using "30HZ" as the screen refresh rate of the new mobile phone 20 in the AOD mode in the embodiments of the present application is only an exemplary illustration. In other embodiments, the screen refresh rate of the new mobile phone 20 in the AOD mode can also be less than or equal to 30HZ, which is not limited herein.

[0308] It can be understood that using "60HZ or 120HZ" as the default screen refresh rate of the new mobile phone 20 in the embodiments of the present application is only an exemplary illustration. In other embodiments, the default screen refresh rate of the new mobile phone 20 can also be 60HZ to 360HZ, such as 75HZ, 144HZ, 165HZ, 240HZ, 360HZ, etc., which is not limited herein.

[0309] Based on the above solution, in the scenario of changing mobile phones, the display interface of the new mobile phone 20 can enter the cloned AOD interface 760 as shown in Figure 7F under corresponding conditions, only display the key information of data migration, and the screen display brightness, screen refresh rate, etc. of the new mobile phone 20 are reduced, so that the display power consumption of the new mobile phone 20 during the process of changing mobile phones is reduced, and the user experience of changing mobile phones is improved.

[0310] It can be understood that in some embodiments, the Figure 10 shown display method and the Figure 11 shown flow schematic diagram of the display method based on the combined system service of the new mobile phone 20 can be combined.

[0311] For example, Figure 12 According to the embodiments of the present application, a macroscopic flow schematic diagram of data migration by the new mobile phone 20 is shown. As Figure 12 shown, this macroscopic process can include the steps executed by the new mobile phone 20 shown above in Figure 10 and the steps executed by the Serviceflinger service shown above in Figure 12 . The following combines Figure 10 , Figure 11 and Figure 12The process shown details the logical relationship between the steps executed by the new mobile phone 20 and the steps executed by the Serviceflinger service.

[0312] Specifically, when the UI interface of the new mobile phone 20 in S303 enters Figure 7E the data receiving interface 750 shown, in S402, a callback for the change in process state can be performed based on the Serviceflinger service, and in S403, it can be determined whether the UI interface of the new mobile phone 20 is displaying Figure 7E the data receiving interface 750 shown.

[0313] When the UI interface of the new mobile phone 20 in S305 enters Figure 7H the cloning completion interface 780 of the new mobile phone 20 shown, in S402, a callback for the change in the interface display state can be performed based on the Serviceflinger service, and in S403, it can be determined that the UI interface of the new mobile phone 20 does not display the data receiving interface 750.

[0314] When a new AOD layer is added to the new mobile phone 20 in S307 and the new mobile phone 20 displays Figure 7F the cloned AOD interface 760 of the new mobile phone 20 shown, that is, when the new mobile phone 20 changes from Figure 7E the data receiving interface 750 shown to Figure 7F the cloned AOD interface 760 shown, in S404, the change in the system layer of the new mobile phone 20 can be monitored based on the Serviceflinger service, that is, a new Figure 2B system layer corresponding to the cloned AOD interface 760 of the new mobile phone 20 shown is added to the system layer cache of the new mobile phone 20.

[0315] When the new mobile phone 20 does not display Figure 7F the cloned AOD interface 760 of the new mobile phone 20 shown in S309, that is, when the new mobile phone 20 changes from Figure 7F the cloned AOD interface 760 shown to Figure 7E the data receiving interface 750 shown, in S404, the change in the system layer of the new mobile phone 20 can be monitored based on the Serviceflinger service of the new mobile phone 20, that is, the Figure 7F system layer corresponding to the cloned AOD interface 760 of the new mobile phone 20 shown is reduced in the system layer cache of the new mobile phone 20.

[0316] Based on the above, through the system service Serviceflinger service callback of the new mobile phone 20, the changes in the system layer of the new mobile phone 20 can be monitored in real time. Finally, according to the operating mode of the system of the new mobile phone 20, such as the low-power mode and the non-low-power mode, by calling the power interface, the screen of the new mobile phone 20 can work in the screen display mode corresponding to the system operating mode.

[0317] For example, when the system of the new mobile phone 20 is not in the low-power mode but meets the conditions for being in the low-power mode. For example, the cloned AOD layer of the new mobile phone 20 exists and is at the top layer of the system layer of the new mobile phone 20, and there is no notification pop-up window displayed on the UI interface of the new mobile phone 20. Then the power interface can be called to make the screen of the new mobile phone 20 enter the AOD mode to reduce the screen display power consumption of the new mobile phone 20.

[0318] For another example, when the system of the new mobile phone 20 is in the low-power mode but does not meet the conditions for being in the low-power mode. For example, the new mobile phone 20 does not display the data reception interface 750 as shown in Figure 7E The cloned AOD layer of the new mobile phone 20 does not exist and is not at the top layer of the system layer cache of the new mobile phone 20, and there is a notification pop-up window displayed on the UI interface of the new mobile phone 20. Then the power interface can be called to make the screen of the new mobile phone 20 exit the AOD mode.

[0319] It can be understood that in the process shown in Figure 12 S401 can be executed before S301; S402 and S403 can be executed after S303 and before S307; S404 can be executed after S307, or executed after S309, which is not limited here.

[0320] Based on the above solution, in the scenario of changing mobile phones, the display interface of the new mobile phone 20 can enter the cloned AOD interface as shown in Figure 7F under corresponding conditions, only display the key information of data migration, and the screen of the new mobile phone 20 enters the AOD mode, and the screen display brightness, screen refresh frame rate, etc. of the new mobile phone 20 are reduced, so that the display power consumption of the new mobile phone 20 during the mobile phone change is reduced, improving the user's mobile phone change experience.

[0321] Through the display method provided by the embodiments of the present application, in the scenario of changing mobile phones between old and new devices, the display interfaces of the old and new devices can enter the cloned AOD interface under corresponding conditions, only display the key information when the old and new devices perform data migration, and the screen display brightness, screen refresh frame rate, etc. of the old and new devices are reduced, so that the display power consumption of the old and new devices during the mobile phone change is reduced, improving the user's mobile phone change experience.

[0322] The following is a structural diagram of the data migration process of the old mobile phone 10 shown in 13A. The data migration process of the old mobile phone 10 is briefly summarized as follows:

[0323] refer to Figure 13A In the example, the old mobile phone 10 as the sending end of the cloning process can scan the QR code displayed on the new mobile phone 20 as the receiving end of the cloning process to establish a data transmission connection with the new mobile phone 20. After the user selects the data to be migrated to be sent to the new mobile phone 20 on the old mobile phone 10, the above data migration process can be performed to send the selected data to be migrated to the new mobile phone 20.

[0324] If the UI interface of the old mobile phone 10 does not detect user operation for 15 seconds or other preset time, and the migration data is not transferred, an AOD layer can be added to the screen of the old mobile phone 10, and the old mobile phone 10 displays Figure 7D The cloned AOD interface 740 in the old mobile phone 10. Correspondingly, the system service Serviceflinger of the old mobile phone 10 can identify the AOD layer of the old mobile phone 10. It can be understood that the AOD layer stacking means that the AOD layer corresponding to the cloned AOD interface is newly added in the system layer cache of the old mobile phone 10, and the AOD layer is located at the top layer in the system layer cache of the old mobile phone 10.

[0325] If the UI interface of the old phone 10 detects the user's operation and the data to be migrated has not been transferred, the timer starts from the completion of the user operation. If the UI interface of the old phone 10 does not detect the user's operation for another 15 seconds, the aforementioned process of adding the AOD layer and the old phone 10 entering the AOD mode is repeated. If the UI interface of the old phone 10 detects the user's operation again at this time, the AOD layer is removed, and the AOD layer of the old phone 10 is popped out based on the recognition of the system service Serviceflinger of the old phone 10. If the system of the old phone 10 is already in low power mode, the AOD mode is exited.

[0326] If the old mobile phone 10 has completed the transmission of the data to be migrated, it means that the old mobile phone 10 has completed the data transmission, and the AOD layer on the screen of the old mobile phone 10 can be removed, and the old mobile phone 10 displays as follows: Figure 7G The data migration success interface 770 is shown; the Serviceflinger of the old mobile phone 10 recognizes that the AOD layer of the old mobile phone 10 is popped out of the stack, and the screen of the old mobile phone 10 exits the AOD mode. The screen refresh frame rate is restored, such as 60HZ, etc.; the CPU screen related processing strategy is controlled and restored.

[0327] It can be understood that the embodiments of the present application do not specifically limit the manner in which the AOD layers are pushed into and out of the stack.

[0328] The following is a schematic diagram of the data migration process of the new mobile phone 20 based on FIG13B. The data migration process of the new mobile phone 20 is briefly summarized as follows:

[0329] refer to Figure 13B In the example, the new mobile phone 20 as the receiving end of the replacement cloning displays a QR code for the old mobile phone 10 as the sending end of the replacement cloning to scan the QR code and establish a connection with the new mobile phone 20; the new mobile phone 20 receives the data to be migrated sent by the old mobile phone 10 and displays the following information: Figure 7E The data receiving interface 750 is shown.

[0330] If the UI interface of the new mobile phone 20 does not detect the user's operation for 15s or other preset time, and the migration data is not imported, an AOD layer can be added to the screen of the new mobile phone 20, and the new mobile phone 20 displays the following Figure 7F The cloned AOD interface 760 in the new mobile phone 20 is displayed. Correspondingly, the system service Serviceflinger of the new mobile phone 20 identifies the AOD layer of the new mobile phone 20 and pushes it into the stack. If the system of the new mobile phone 20 is not in the low power consumption mode, the screen of the new mobile phone 20 is made to enter the AOD mode.

[0331] If the UI interface of the new phone 20 detects the user's operation and the migration data has not been imported, the timer starts from the completion of the user operation. If the UI interface of the new phone 20 does not detect the user's operation for 15 seconds, the above-mentioned process of adding the AOD layer is repeated and the new phone 20 enters the AOD mode. If the UI interface of the new phone 20 detects the user's operation again at this time, the AOD layer is removed, and the AOD layer of the new phone 20 is popped out based on the recognition of the system service Serviceflinger of the new phone 20. If the system of the new phone 20 is already in low power mode, the AOD mode is exited.

[0332] If the new mobile phone 20 has completed the import of the data to be migrated, it means that the new mobile phone 20 has completed the data migration, and the AOD layer on the screen of the new mobile phone 20 can be removed. The new mobile phone 20 displays Figure 7H The data migration success interface 780 is shown; the Serviceflinger of the new mobile phone 20 recognizes that the AOD layer of the new mobile phone 20 is popped out of the stack, and the screen of the new mobile phone 20 exits the AOD mode. The screen refresh frame rate is restored, such as 60HZ, etc.; the CPU screen related processing strategy is controlled and restored.

[0333] In other embodiments, the display method provided in the embodiments of the present application can also be applied to a scenario where multiple terminals perform data transmission based on Bluetooth or NFC, etc. An exemplary description is given below in conjunction with the relevant drawings.

[0334] For example, Figures 14A to 14DThe schematic diagram of the interface for a mobile phone 30 and a mobile phone 40 to transmit video data based on Bluetooth is shown according to an embodiment of the present application.

[0335] Specifically, Figure 14A The schematic diagram of an interface for sending video data displayed on the mobile phone 30 is shown.

[0336] As Figure 14A shown, the data sharing information in the sending interface 140 displayed on the mobile phone 30 includes the names of video data (Video 1, Video 2, Video 3, Video 4, Video 5, Video 6, etc.), the sending progress percentage of each video data, the rate, the remaining sending time, a prompt message to remind the user not to leave the current interface, and a "Cancel" control for canceling the data sharing process, etc.

[0337] Figure 14B The schematic diagram of an interface for receiving video data displayed on the mobile phone 40 is shown.

[0338] As Figure 14B shown, the data sharing information in the receiving interface 141 displayed on the mobile phone 40 may include the names of video data (Video 1, Video 2, Video 3, Video 4, Video 5, Video 6, etc.), the receiving progress percentage of each video data, the rate, the remaining receiving time, a prompt message to remind the user not to leave the current interface, and a "Cancel" control for canceling the data receiving process, etc.

[0339] By applying the display method provided in the present application, the mobile phone 30 and the mobile phone 40 can also reduce the display power consumption when transmitting data based on Bluetooth.

[0340] Figure 14C The schematic diagram of another interface for the mobile phone 30 to send video data is shown.

[0341] As Figure 14C shown, the sending interface 142 displayed on the mobile phone 30. Compared with Figure 14A in Figure 14C , the mobile phone 30 in Figure 14A can be in a black screen display state and can only display the key information of data sharing. For example: "Sending", the data sending progress percentage "50%", "5GB has been sent", "Rate 98MB / second", "Remaining time for sending data 30 minutes", etc. If the user wants to return to the data sending interface of the mobile phone 30 as shown in Figure 14C , they can click "Tap to return" in

[0342] Figure 14D The schematic diagram of another interface for the mobile phone 40 to receive video data is shown.

[0343] As Figure 14DAs shown, the sending interface 143 displayed on the mobile phone 40. Compared with Figure 14B , Figure 14D the mobile phone 40 can be in a black screen display state, and only the key information of data sharing can be displayed. For example: "Receiving", the data receiving progress percentage "50%", "5GB received", "Rate 98MB / second", "Remaining time for receiving data 30 minutes", etc. If the user wants to return to the data receiving interface of the mobile phone 40 as shown in Figure 14B , they can click "Tap to return" as shown in Figure 14D .

[0344] Based on this, in the scenario where multiple devices share data based on Bluetooth, the display interface of the devices can only display the key information of data migration, and the screen refresh frame rate, screen display brightness, etc. of multiple devices are reduced, so that the display power consumption when multiple devices share data based on Bluetooth is reduced.

[0345] For another example, Figures 15A to 15D shows a schematic diagram of the interface for sharing video data between a mobile phone 30 and a mobile phone 40 based on NFC. Compared with sharing data as described above in Figures 14A to 14D , the difference is that Figure 15A and Figure 15D the mobile phone 30 and the mobile phone 40 are based on NFC to share video data. The specific interface diagram is similar to that in Figures 14A to 14D above and can be referred to here and will not be elaborated further.

[0346] Based on this, in the scenario where multiple devices share data based on NFC, the display interface of the devices can only display the key information of data migration, and the screen refresh frame rate, screen display brightness, etc. of multiple devices are reduced, so that the display power consumption when multiple devices share data based on NFC is reduced.

[0347] It can be understood that in the scenario where the display method provided in the embodiments of the present application is applied, when multiple devices transmit data, the type of data transmitted can be various types of application data or data packets such as video data, audio data, file data, folder data, picture data, etc. The type of transmitted data is not limited here.

[0348] Furthermore, Figure 16 According to some embodiments of the present application, a schematic diagram of the structure of a mobile phone is shown.

[0349] As shown in Figure 16As shown in the figure, the mobile phone 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, a headphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, a communication device 196, etc. Among them, the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric 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, a color temperature sensor 180N, etc.

[0350] Among them:

[0351] 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 processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0352] The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0353] A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 may save the stored data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can be directly called from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0354] In some embodiments, the processor 110 may be used to execute the display methods provided in the embodiments of the present application. When switching electronic devices, the data migration interface of the electronic device can be set to only display key information, and the background brightness can be lowered, such as being lowered to a black screen, which is similar to the always-on display of the electronic device.

[0355] The USB interface 130 is an interface that complies with the USB standard specification. Specifically, it can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the mobile phone, and can also be used to transfer data between the mobile phone and peripheral devices. It can also be used to connect headphones to play audio through the headphones. This interface can also be used to connect other electronic devices, such as AR devices, etc.

[0356] The charging management module 140 is used to receive the charging input from the charger. While charging the battery 142, the charging management module 140 can also supply power to the mobile phone through the power management module 141.

[0357] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives the inputs from the battery 142 and / or the charging management module 140, and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, the wireless communication module 160, etc.

[0358] The wireless communication function of the mobile phone can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modulation and demodulation processor, the baseband processor, etc.

[0359] The antenna 1 and the antenna 2 are used to transmit and receive electromagnetic wave signals, that is, wireless carrier information.

[0360] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc. applied to the mobile phone. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves by the antenna 1, filter, amplify, etc. the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves through the antenna 1 and radiate it out.

[0361] The wireless communication module 160 may provide solutions for wireless communications applied to a mobile phone, including wireless local area networks (WLANs) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), ultra wide band (UWB), etc. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 may receive electromagnetic waves through the antenna 2, and perform processing such as filtering and amplifying the received electromagnetic waves, and then transmit them to the modulation and demodulation processor for demodulation. The wireless communication module 160 may also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves through the antenna 2 and radiate them out.

[0362] The mobile phone realizes the interface display function through the GPU, the display screen 194, and the application processor, etc. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. The GPU is used to execute mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs, which execute program instructions to generate or change display information.

[0363] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel may adopt a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a mini-LED, a micro-LED, a micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the key information during data migration when replacing the old mobile phone 10 with the new mobile phone 20 in the embodiments of the present application may be displayed based on the display screen 194.

[0364] The camera 193 is used to capture static images or videos.

[0365] 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 mobile phone. The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function.

[0366] The internal memory 121 can be used to store computer-executable program codes. The executable program codes include instructions, such as the aforementioned memory 103. The internal memory 121 can include a program storage area and a data storage area. Among them, the program storage area can store the operating system, application programs required for at least one function, etc. The data storage area can store data created during the use of the mobile phone, etc. For example, it can be used to store the control identifier of the security control, the screenshot redrawing policy identifier corresponding to the security control, the patterns, images, texts, etc. corresponding to the screenshot redrawing policy. In addition, the internal memory 121 can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 110 executes various functional applications of the mobile phone by running the instructions stored in the internal memory 121 and / or the instructions stored in the memory provided in the processor 110.

[0367] The mobile phone can implement audio functions through the audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and the application processor, etc.

[0368] The touch sensor 180K, also known as a "touch control device". The touch sensor 180K can be disposed on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also known as a "touch control screen". The touch sensor 180K is used to detect touch operations acting thereon or nearby. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In some other embodiments, the touch sensor 180K can also be disposed on the surface of the mobile phone, at a different position from the display screen 194. In some embodiments, when the touch screen detects an operation by the user on the touch screen, it can be sent to the processor 110 to trigger the monitoring of the change in the system layer caused by the user operation provided in the embodiments of the present application.

[0369] The motor 191 can generate a vibration prompt.

[0370] The indicator 192 can be an indicator light, which can be used to indicate the charging state, power change, and can also be used to indicate messages, missed calls, notifications, etc.

[0371] The SIM card interface 195 is used to connect the SIM card.

[0372] It can be understood that the structure of the mobile phone shown in the embodiments of the present application does not constitute a specific limitation on the mobile phone. In other embodiments of the present application, the mobile phone may include more or fewer components than shown in the figures, or combine certain components, or split certain components, or have different component arrangements. The components shown in the figures can be implemented in hardware, software, or a combination of software and hardware.

[0373] The various embodiments disclosed in the present application can be implemented in hardware, software, firmware, or a combination of these implementation methods. The embodiments of the present application can be implemented as a computer program or program code executed on a programmable system, which includes at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0374] The program code can be applied to the input instructions to perform the various functions described in the present application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of the present application, the processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor. The program code can be implemented in a high-level procedural language or an object-oriented programming language in order to communicate with the processing system.

[0375] When needed, the program code can also be implemented in assembly language or machine language. In fact, the mechanisms described in the present application are not limited to the scope of any specific programming language. In any case, the language can be a compiled language or an interpreted language.

[0376] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may be implemented as instructions carried or stored on one or more transitory or non-transitory machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, the instructions may be distributed via a network or via other computer-readable media. Thus, machine-readable media may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including but not limited to, floppy disks, optical disks, optical discs, compact discs read-only memory (CD-ROMs), magneto-optical discs, read-only memory (ROM), random access memory (RAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic or optical cards, flash memory, or tangible machine-readable memories for transmitting information (e.g., carrier waves, infrared signals, digital signals, etc.) in electrical, optical, acoustic, or other forms via the Internet. Thus, machine-readable media include any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a form readable by a machine (e.g., a computer).

[0377] In the drawings, some structural or method features are shown in a particular arrangement and / or order. However, it should be understood that such a particular arrangement and / or ordering may not be required. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. Additionally, the inclusion of a structural or method feature in a particular figure does not imply that such a feature is required in all embodiments, and in some embodiments, these features may not be included or may be combined with other features.

[0378] It should be noted that each unit / module mentioned in the device embodiments of the present application is a logical unit / module. Physically, a logical unit / module may be a physical unit / module, a part of a physical unit / module, or may be implemented as a combination of multiple physical units / module. The physical implementation manner of these logical units / module themselves is not the most important. The combination of the functions implemented by these logical units / module is the key to solving the technical problems proposed by the present application. In addition, in order to highlight the innovative part of the present application, the above device embodiments of the present application do not introduce units / modules that are not closely related to solving the technical problems proposed by the present application, which does not mean that there are no other units / modules in the above device embodiments.

[0379] It should be noted that in the examples and the description of this patent, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising one" does not exclude the presence of additional identical elements in the process, method, article or device comprising the said element. Although this application has been illustrated and described by reference to certain preferred embodiments of the present application, those of ordinary skill in the art should understand that various changes may be made in form and detail without departing from the scope of the present application.

Claims

1. A display method, characterized in that, The method includes: The first electronic device displays a first data transmission interface for data transmission with the second electronic device. Among them, the first data transmission interface has a first display brightness, and the first data transmission interface includes multiple transmission information items; The first electronic device displays a second data transmission interface. Among them, the second data transmission interface has a second display brightness, and the second data transmission interface displays some of the multiple transmission information items; Among them, the second display brightness is less than the first display brightness.

2. The method according to claim 1, characterized in that The multiple transmission information items include the data transmission progress percentage, data transmission rate, amount of data already transmitted, remaining data transmission time, names, icons, and transmission status of the multiple transmission information items.

3. The method according to claim 1, wherein The second display brightness is 0% to 30% of the first display brightness.

4. The method according to claim 1, characterized in that The first electronic device displays the second data transmission interface, including: Determine whether the first data transmission interface meets the interface switching condition; Corresponding to the first data transmission interface meeting the interface switching condition, the first electronic device displays the second data transmission interface.

5. The method according to claim 4, wherein The interface switching condition includes that the first data transmission interface does not receive a first operation within a preset duration; The first operation includes a click operation, double-click operation, swipe operation, and press operation received by the screen of the first electronic device.

6. The method according to claim 5, characterized in that, The interface switching condition further includes that the first data transmission interface does not detect a notification pop-up window within a preset duration.

7. The method according to claim 4, characterized in that, It further includes: Determine whether the second data transmission interface receives a first operation or detects a notification pop-up window; Corresponding to the second data transmission interface receiving the first operation or detecting the notification pop-up window and the data transmission not being completed, the first electronic device exits the display of the second data transmission interface, and the first electronic device displays the first data transmission interface.

8. The method according to claim 7, wherein It further includes: Determine whether the first electronic device has completed data transmission; Corresponding to the first electronic device completing data transmission, the first electronic device exits the display of the second data transmission interface, and the first electronic device displays a data transmission completion interface.

9. The method according to claim 1, characterized in that, The first data transmission interface has a first screen refresh rate, and the second data transmission interface has a second screen refresh rate, and the second screen refresh rate is less than the first screen refresh rate.

10. An electronic device, characterized in that, It includes: a memory for storing instructions; A processor for executing the instructions to implement the display method according to any one of claims 1 to 9.

11. A readable storage medium, characterized in that, Instructions are stored on the readable storage medium, and when the instructions are executed on the electronic device, the electronic device executes the display method according to any one of claims 1 to 9.

Images