A method for displaying a boot screen and an electronic device

Abstract

This application provides a boot screen display method and electronic device, relating to the field of terminal technology. When a first device is powered on for the first time, it displays a customized boot screen instead of a regular boot screen. This customized boot screen is determined based on user-inputted customized screen information, satisfying the user's customization needs for the boot screen, achieving personalized display of the boot screen, and ensuring a good user experience.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a boot screen display method and electronic device. Background Technology

[0002] With the development of electronic device technology, there are increasingly more types of electronic devices, such as mobile phones, tablets, and wearable devices. When an electronic device is powered on, it typically displays a boot screen first, such as a boot animation or boot image. After this display ends, the electronic device then enters the user interface, such as the desktop.

[0003] However, the boot screen displayed on electronic devices is a fixed image preset by the factory, which cannot meet the personalized needs of users. Summary of the Invention

[0004] This application provides a boot screen display method and electronic device to avoid displaying a fixed boot screen, meet users' personalized needs, and improve user experience.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] In a first aspect, a method for displaying a boot screen is provided, applied to a first device. The first device receives a power-on operation input by a user. In response to the power-on operation, the first device powers on for the first time. In the case of the first power-on, the first device can display a first boot screen, which is determined based on first data input by the user, and the first data corresponds to the display content of the first boot screen.

[0007] In this application, when the first device is powered on for the first time, the first device displays a first boot screen. The first boot screen is determined based on first data, which corresponds to the display content of the first boot screen, rather than directly displaying a conventional boot screen. This avoids displaying a fixed boot screen, meets the user's personalized display needs for the boot screen, and improves the user experience.

[0008] In one possible design, in response to a received first operation, the first device deletes the data of the first boot screen. Subsequently, in cases other than the first boot, such as the next boot, a second boot screen, different from the first boot screen, is displayed. Based on this, the first device can also delete the data of the first boot screen, stopping its display during boot, thus satisfying different user display needs for the boot screen. Furthermore, user privacy can be protected.

[0009] In one possible design, the first device receives a second operation, which triggers a halt to using the first boot screen as the boot screen. In response to this second operation, the first device can stop using the first boot screen as the boot screen and instead use the second boot screen as the boot screen.

[0010] Correspondingly, in cases other than the first power-on, such as the next power-on, the first device can display the second power-on screen. Based on this, the first device can also change the power-on screen, such as stopping the display of the first power-on screen during power-on, to meet different display needs of users for the power-on screen.

[0011] In one possible design, the first device, in response to a received third operation, saves the first boot screen. Correspondingly, during operation of the first device, in response to a fourth operation, displays the first boot screen. Optionally, the first device saves the first boot screen to its local map library. Accordingly, the fourth operation could be a trigger operation on a thumbnail of the first boot screen in the local map library, allowing the user to view the first boot screen.

[0012] In one possible design, the first device includes a wake-up receiver. The data for the first power-on screen is received before the initial power-on. Specifically, the first device receives a first wake-up signal from the second device via the wake-up receiver. In response to the first wake-up signal, the wake-up receiver performs a wake-up operation on the first device to achieve wake-up. Afterwards, the first device establishes a communication connection with the second device. Subsequently, the first device receives the data for the first power-on screen sent by the second device based on this communication connection. Based on this, the transmission of customized first power-on screen data is achieved. Furthermore, before receiving the first wake-up signal, the first device is not woken up, i.e., the first device is in a powered-off state; only the wake-up receiver is powered on. Since the wake-up receiver has low power consumption, this ensures that the wake-up receiver of the first device can receive the wake-up signal while avoiding excessive power consumption of the first device.

[0013] In one possible design, if the first device determines that the first wake-up signal includes the identifier of the first device, it can continue to perform the wake-up operation of the first device, thereby avoiding unnecessary wake-up operations and preventing the customized boot screen data from being mistakenly transmitted to a device that does not require boot screen customization.

[0014] In one possible design, if the first device determines that the quality of the first wake-up signal is greater than a preset quality value, it can continue to perform the wake-up operation of the first device, thereby avoiding unnecessary wake-up operations and preventing the customized boot screen data from being mistakenly transmitted to a device that does not require boot screen customization.

[0015] In one possible design, after receiving the data for the first boot screen from the second device, the first device can set the priority of the first boot screen data to be higher than the priority of the second boot screen data. This priority indicates the order in which the boot screens are displayed during startup. Based on this, during startup, the first device can display the first boot screen with the higher priority.

[0016] In one possible design, the first device can store the received first boot screen in a target storage location, so that upon first boot, customized boot screen data can be retrieved from the target storage location, thus enabling the reading of customized boot screen data.

[0017] In one possible design, after successful data transmission on the first power-on screen, the first device can be powered off; in the powered-off state, the wake-up receiver in the first device is turned on, and is turned off at other times to save power consumption.

[0018] In a second aspect, this application provides an electronic device, which serves as a first device and includes a wake-up receiver, a display screen, a communication module, a memory, and one or more processors;

[0019] The wake-up receiver is used to receive a wake-up signal sent by the second device. The wake-up signal is used to trigger the electronic device to wake up so as to establish a communication connection with the second device.

[0020] The communication module is used to establish a communication connection with the second device;

[0021] The display screen is used to display an image generated by the processor, the image including a boot screen;

[0022] The memory is used to store computer program code, which includes computer instructions; when the processor executes the computer instructions, the electronic device performs the boot screen display method as described above.

[0023] Thirdly, this application provides a chip, the chip including a communication interface and at least one processor:

[0024] The communication interface is used for inputting and / or outputting signaling or data;

[0025] The at least one processor is used to execute a computer program to implement the boot screen display method described above.

[0026] Fourthly, this application provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform the boot screen display method described above.

[0027] Fifthly, this application provides a computer program product that, when run on an electronic device, causes the electronic device to execute the boot screen display method described above.

[0028] It is understood that the beneficial effects achieved by the electronic device described in the second aspect, the chip described in the third aspect, the computer-readable storage medium described in the fourth aspect, and the computer program product described in the fifth aspect can be referred to the beneficial effects in the first aspect and any of its possible design embodiments, which will not be repeated here. Attached Figure Description

[0029] Figure 1 A schematic diagram illustrating a customized housing provided for an embodiment of this application;

[0030] Figure 2 This application provides a schematic diagram of a boot screen display. Figure 1 ;

[0031] Figure 3 A schematic diagram of a customized boot screen data import process provided in this application embodiment. Figure 1 ;

[0032] Figure 4 A wake-up diagram provided for an embodiment of this application;

[0033] Figure 5 A schematic diagram of the hardware structure of an electronic device provided in this application embodiment. Figure 1 ;

[0034] Figure 6 A flowchart illustrating a boot screen display method provided in an embodiment of this application;

[0035] Figure 7 A schematic diagram of a customized boot screen provided for an embodiment of this application;

[0036] Figure 8 A schematic diagram of a customized boot screen data import process provided in this application embodiment. Figure 2 ;

[0037] Figure 9 This application provides a schematic diagram of a boot screen display. Figure 2 ;

[0038] Figure 10 This application provides a schematic diagram of a boot screen display. Figure 3 ;

[0039] Figure 11 A schematic diagram illustrating a customized boot screen setup provided in an embodiment of this application;

[0040] Figure 12 A schematic diagram of the hardware structure of an electronic device provided in this application embodiment. Figure 2 ;

[0041] Figure 13 This is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0042] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "exemplary" or "for example" are used in the embodiments of this application to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a specific manner. In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. In the embodiments of this application, "first," "second," "1," and "2" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, features defined with "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "multiple" means two or more.

[0043] With the development of electronic device technology, the types of electronic devices are becoming increasingly diverse, such as mobile phones, tablets, and wearable devices. To meet users' personalized needs, users can customize their electronic devices. Generally, after receiving and turning on an electronic device, users can change the user interface (UI) content by updating the wallpaper, theme, etc., to personalize the UI. Before receiving the electronic device, users can request engraving on the casing from the seller or other relevant parties to have specific content engraved on the casing. Taking a mobile phone as an example, for instance... Figure 1As shown, “XXXXX” is engraved on the phone casing 10.

[0044] However, before users receive their electronic devices, they cannot change the device's UI, such as the boot screen. Upon powering on, especially for the first time, the boot screen is typically a pre-set, fixed animation (the default or standard boot screen), which doesn't meet users' personalized boot screen needs. This boot screen can be a display corresponding to a boot animation or image.

[0045] For example, such as Figure 2 As shown, when the phone is turned on for the first time, it displays a boot animation. Figure 2 Screens 20 and 21 shown in the image are two of the screens in the boot animation. After the boot animation ends, the phone can display the desktop 22.

[0046] Therefore, to address the aforementioned issues, this application proposes a solution for customizing the initial boot screen. Before the electronic device is powered on for the first time, a communication connection is established between the host computer and the electronic device. Based on this communication connection, the user-desired customized boot screen data is transmitted to the electronic device. Upon initial power-on, the electronic device can display the customized boot screen instead of the uniform and fixed boot animation, thus meeting the user's personalized display needs.

[0047] Considering that when a user requests customization, the electronic device is generally already manufactured, meaning it's packaged and powered off. Therefore, transmitting the customized boot screen data to the electronic device would require turning it on. However, turning on the device might damage its packaging. To address this, the electronic device can add a wake-up receiver (WUR) to its existing communication unit (or main communication unit). This wake-up receiver has low power consumption, typically ranging from tens of nanowatts (nW) to hundreds of microwatts (μW), and can remain continuously powered on. Figure 3As shown, during periods of no business demand, the main communication unit of the electronic device is in a switched-off state. The wake-up receiver is in an switched-on state to detect whether a wake-up signal (WUS) is received. Subsequently, the host computer can send a wake-up signal to the wake-up receiver of the electronic device. Upon detecting the wake-up signal, the wake-up receiver triggers the main communication unit to switch to an switched-on state. Then, the main communication unit establishes a communication connection with the host computer. The host computer can then use this communication connection to transmit customized boot screen data to the electronic device, enabling the electronic device to successfully obtain the customized boot screen data. This allows the electronic device to display the customized boot screen upon its first power-on, meeting the user's personalized needs. Furthermore, this process simplifies the import process of customized boot screen data without damaging the electronic device's packaging, improving import efficiency. Additionally, although a wake-up receiver is added to the electronic device, its power consumption is very low, having minimal impact on the electronic device's battery life.

[0048] Optionally, to reduce power consumption, the wake-up receiver can be periodically activated. That is, at preset intervals, the wake-up receiver transitions from sleep mode to active mode. For example, the wake-up receiver operates for 10 seconds every minute, and sleeps for the other 50 seconds, reducing power consumption to 1 / 6. Correspondingly, the host computer can continuously send wake-up signals for a duration greater than or equal to the preset time, ensuring the wake-up receiver successfully receives the wake-up signal. Based on this, the wake-up receiver not only successfully receives the wake-up signal but also does not need to be constantly active, resulting in very low overall power consumption, such as less than 1 microwatt. Alternatively, after the main communication unit is activated, the wake-up receiver can be in sleep mode to reduce unnecessary power consumption.

[0049] Optionally, the aforementioned wake-up receiver can trigger the main communication unit to switch to the on state via the microcontroller unit. For example... Figure 4 As shown, after receiving the wake-up signal, the wake-up receiver sends an enable signal to the microcontroller unit (MCU). In response to the enable signal, the MCU enables the main communication unit.

[0050] In this embodiment, the wake-up receiver can also be referred to as a wake-up radio transceiver. The main communication unit can also be referred to as a main radio transceiver or a communication module. The main communication unit may include a mobile communication module or a wireless communication module.

[0051] Optionally, the wake-up signal can be a low-power-wake-upsignal (LP-WUS), and the wake-up receiver can be a low-power-wake-up receiver.

[0052] For example, the electronic device in this application embodiment may be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, as well as wearable devices (smartwatches, smart bracelets, etc.), personal digital assistant (PDA), augmented reality (AR) / virtual reality (VR) devices, etc., which are capable of displaying a boot screen. This application embodiment does not impose any special restrictions on the specific form of the electronic device.

[0053] For example, Figure 5 A schematic diagram of the structure of electronic device 200 is shown. For example... Figure 5 As shown, the electronic device 200 may include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 211, a power management module 212, a battery 213, an antenna 1, an antenna 2, a mobile communication module 240, a wireless communication module 250, a wake-up receiver 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, a headphone jack 270D, a sensor module 280, buttons 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a subscriber identification module (SIM) card interface 295, etc.

[0054] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 200. In other embodiments of this application, the electronic device 200 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0055] Processor 210 may include one or more processing units, such as application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0056] The controller can be the nerve center and command center of the electronic device 200. The controller can generate operation control signals based on the instruction opcode and timing signals to control the fetching and execution of instructions.

[0057] The processor 210 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. This memory can store instructions or data that the processor 210 has just used or that are used repeatedly. If the processor 210 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 210, and thus improves the efficiency of the system.

[0058] In some embodiments, the processor 210 described above may be integrated on an MCU.

[0059] The wireless communication function of electronic device 200 can be implemented through antenna 1, antenna 2, mobile communication module 240, wireless communication module 250, modem processor, and baseband processor.

[0060] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 200 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch.

[0061] The mobile communication module 240 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 200. The mobile communication module 240 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 240 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 240 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 240 may be housed in the processor 210. In some embodiments, at least some functional modules of the mobile communication module 240 and at least some modules of the processor 210 may be housed in the same device.

[0062] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 270A, receiver 270B, etc.) or displays images or videos through the display screen 294. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 210 and may be housed in the same device as the mobile communication module 240 or other functional modules.

[0063] The wireless communication module 250 can provide solutions for wireless communication applications on the electronic device 200, including wireless local area networks (WLAN) (such as Wi-Fi), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR). The wireless communication module 250 can be one or more devices integrating at least one communication processing module. The wireless communication module 250 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signal, and sends the processed signal to processor 210. The wireless communication module 250 can also receive signals to be transmitted from processor 210, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0064] In some embodiments, the mobile communication module 240 and the wireless communication module 250 may belong to the main communication unit.

[0065] The wake-up receiver 260 is in the ON state and is used to receive wake-up signals. This wake-up signal can be a specific wake-up signal, which is used to trigger the electronic device to enter the customized boot screen state, so as to realize the transmission of the user's customized boot screen data.

[0066] Electronic device 200 implements display functions through GPU, display screen 294, and application processor.

[0067] The display screen (or screen) 294 is used to display the boot screen, video, etc. In some embodiments, the electronic device 200 may include one or N display screens 294, where N is a positive integer greater than 1.

[0068] Electronic device 200 can perform shooting functions through ISP, camera 293, video codec, GPU, display screen 294 and application processor.

[0069] The external storage interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 200.

[0070] Internal memory 221 can be used to store computer executable program code, which includes instructions. Processor 210 executes various functional applications and data processing of electronic device 200 by running the instructions stored in internal memory 221. Internal memory 221 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function, etc. The data storage area may store data created during the use of electronic device 200 (such as audio data, phonebook, etc.). Furthermore, internal memory 221 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0071] Electronic device 200 can implement audio functions such as music playback and recording through audio module 270, speaker 270A, receiver 270B, microphone 270C, headphone jack 270D, and application processor.

[0072] Buttons 290 include a power button, volume buttons, etc. Indicator 292 may be an indicator light.

[0073] The sensor module 280 may include pressure sensors, gyroscope sensors, barometric pressure sensors, magnetic sensors, accelerometers, distance sensors, proximity sensors, fingerprint sensors, temperature sensors, touch sensors, ambient light sensors, bone conduction sensors, etc.

[0074] This application provides a method for displaying a boot screen. When the electronic device (or first device) is in a storage phase, it is powered off, but its wake-up receiver is powered on. A host computer (or second device) can use the wake-up receiver to trigger the electronic device into a customized boot screen state, transmitting the user's customized boot screen data to the device. This ensures that when the user first powers on the device, the boot screen displayed is the customized one, satisfying the user's personalized boot screen display needs. Furthermore, although the wake-up receiver is on, its power consumption is extremely low, resulting in low power consumption during the storage phase and minimal impact on the device's battery life. This ensures that when the user receives the device, its remaining battery is not depleted, allowing for normal power-on and guaranteeing a positive user experience.

[0075] The following will use a mobile phone as an example to illustrate the boot screen display method. Figure 6 As shown, the method may include:

[0076] S301, The host computer obtains customized boot screen data.

[0077] The customized boot screen data (or the first boot screen data) is determined based on the screen information (or first data) input by user 1. User 1 can submit their customization request online, such as on a specific webpage. This screen information corresponds to the display content of the customized boot screen (or the first boot screen). In one case, this screen information can be directly the customized boot screen data; that is, user 1 directly provides the boot screen data, such as a boot animation or boot image.

[0078] In another scenario, this screen information indicates the content required for the boot screen, and the customized boot screen data needs to be generated based on this information. For example, the screen information entered by the user includes the name "XX" and the greeting "Happy Birthday" (see...). Figure 7 Based on this screen information, relevant devices (such as a host computer or devices that receive screen information input by the user) automatically generate, for example,... Figure 8 The image shown is the customized boot screen data for user 1.

[0079] In another scenario, the relevant device can provide at least one boot screen template. User 1 can select a boot screen template according to their needs, and correspondingly, the aforementioned screen information can be an identifier of the boot screen template selected by User 1.

[0080] In short, the customized boot screen data can be uploaded directly by user 1, or determined by the relevant device based on the requirements input by user 1.

[0081] It should be noted that the host computer and the device receiving the screen information input by user 1 (or device 1) can be the same device or different devices. If the host computer and device 1 are not the same device, the customized boot screen data can be determined by device 1 based on the screen information. After determining the customized boot screen data, device 1 sends the customized boot screen data to the host computer. Alternatively, the customized boot screen data can be determined by the host computer based on the screen information, which is sent by device 1.

[0082] S302, The host computer sends wake-up signal 1 to the target mobile phone. Wake-up signal 1 is used to trigger the target mobile phone to enter the boot screen customization state.

[0083] For example, after the host computer receives the customized boot screen data, it indicates that it needs to import the customized boot screen data into the target mobile phone. The host computer can send a wake-up signal 1 (or the first wake-up signal) to the target mobile phone to trigger the target mobile phone to wake up and enter the boot screen customization state, i.e. the UI customization state, and start to execute the UI customization process to receive the customized boot screen data transmitted by the host computer.

[0084] The target phone refers to the phone that needs to be given to user 1, that is, the phone that needs to have its boot screen customized, which means the phone that needs to have its customized boot screen data imported.

[0085] In some embodiments, the wake-up signal 1 may include specific encoded information that indicates that the target mobile phone needs to enter the UI customization state.

[0086] S303. After leaving the factory, the target mobile phone is in a woken-up state. This wake-up state means that all devices except the wake-up receiver in the target mobile phone are in a turned-off state.

[0087] The "wake-up" state indicates that the target phone is powered off, but the wake-up receiver in the target phone is turned on to detect whether a wake-up signal has been received.

[0088] S304, The wake-up receiver receives the wake-up signal 1.

[0089] S305, Wake-up receiver wakes up the target mobile phone.

[0090] For example, in response to wake-up signal 1, the wake-up receiver wakes up the MCU, main communication unit, and other devices in the target mobile phone, so that the target mobile phone enters the operating state. It should be understood that after the target mobile phone is woken up, the target mobile phone is actually powered on, but the screen of the target mobile phone can still be in a black screen state, thereby reducing unnecessary power consumption waste.

[0091] In some embodiments, the wake-up signal 1 is a radio wave. Considering the propagation characteristics of radio waves, the wake-up signal 1 sent by the host computer may be received by multiple mobile phones, resulting in the wake-up of phones that do not require boot screen customization. Therefore, to prevent phones that do not require boot screen customization from being woken up, in one scenario, the wake-up signal 1 can carry an identifier of the phone to be woken up, thereby achieving accurate wake-up of the phone to be woken up. The wake-up receiver determines whether the identifier of the phone to be woken up in the wake-up signal 1 is the same as the identifier of the target phone.

[0092] If they are the same, it indicates that the target phone needs to have its boot screen customized, and the wake-up receiver can wake up the target phone normally.

[0093] If they are different, it means that the target phone does not need to have its boot screen customized. In this case, the wake-up receiver does not need to wake up the target phone, and the target phone will remain in the wake-up state. This avoids waking up a phone that does not need to be woken up, thereby avoiding incorrect boot screen customization. In other words, it prevents phones that do not need boot screen customization from having their boot screen customized, thus ensuring the user experience.

[0094] The identifier of the target mobile phone must be unique. For example, the identifier of the target mobile phone may include the target mobile phone identification code, such as the product serial number (SN).

[0095] In another scenario, the distance between the host computer and the phone to be woken up is generally closer, resulting in a higher quality wake-up signal 1 received by the wake-up receiver in the phone. Therefore, wake-up signal 1 can be uniform. When the wake-up receiver in the phone receives a high quality wake-up signal 1, the phone can be considered a phone that needs to be woken up. For example, the wake-up receiver determines whether the quality of wake-up signal 1 is greater than a preset quality value. If it is greater than the preset quality value, it indicates that the host computer is close to the target phone, and the target phone is the one requiring customized boot screen. In this case, the wake-up receiver can successfully wake up the target phone. Based on this, accurate wake-up of the phone to be woken up can be achieved. Furthermore, since wake-up signal 1 is the same, the host computer can wake up multiple phones simultaneously, and thus customize the boot screen for multiple phones at the same time.

[0096] If the quality of wake-up signal 1 is less than or equal to the preset quality value, it indicates that the host computer is far from the target mobile phone and the target mobile phone is not a mobile phone that needs to have its boot screen customized. Therefore, the wake-up receiver does not need to wake up the target mobile phone.

[0097] Optionally, the quality of the wake-up signal 1 can be characterized by parameters such as signal amplitude and signal strength.

[0098] It is understood that the aforementioned target mobile phone can be one or more. Furthermore, the wake-up receiver in the target mobile phone, upon receiving wake-up signal 1, can directly wake up the target mobile phone without executing the process described above of determining whether to wake up the target mobile phone based on the phone's identifier and the quality of wake-up signal 1. Then, after the target mobile phone is woken up, it can determine whether to enter the UI customization state based on the phone's identifier and the quality of wake-up signal 1. The implementation process of determining whether to enter the UI customization state based on the phone's identifier and the quality of wake-up signal 1 is similar to the process described above. For example, the wake-up receiver responds to wake-up signal 1 and wakes up the target mobile phone. Afterwards, if the identifier of the phone to be woken up in wake-up signal 1 is the same as the identifier of the target mobile phone, the target mobile phone can enter the UI customization state, i.e., execute S306 as described below.

[0099] S306. The target mobile phone establishes a communication connection with the host computer.

[0100] The communication connection can be a wireless communication connection, such as a Wi-Fi connection, Bluetooth connection, or NFC connection. Alternatively, the communication connection can be a cellular network (or mobile communication) connection. The target mobile phone can connect to the cellular network via a virtual SIM card.

[0101] For example, after the target mobile phone is woken up, if it is determined that the wake-up signal 1 carries specific encoded information, the target mobile phone can enter the boot screen customization state.

[0102] The "customized boot screen status" indicates that a communication connection has been established with the host computer to receive customized boot screen data. In other words, the customized boot screen status indicates a state of waiting to receive customized boot screen data transmitted from the host computer. For example, this communication connection can be a Wi-Fi connection. The host computer can provide a Wi-Fi network. After the target mobile phone is woken up, it can access the Wi-Fi network provided by the host computer, establish a Wi-Fi connection, and then use this Wi-Fi connection to transmit customized boot screen service data, i.e., transmit customized boot screen data.

[0103] Optionally, the wake-up signal 1 may carry communication connection information, which indicates the method of establishing the communication connection, that is, how the target mobile phone should establish the communication connection. For example, the communication connection information includes information about the Wi-Fi network provided by the host computer (such as the Wi-Fi network name). Based on the communication connection information, the target mobile phone determines that it needs to establish a Wi-Fi connection in order to access the Wi-Fi network corresponding to the Wi-Fi network name.

[0104] It is understood that the specific encoded information carried by the aforementioned wake-up signal 1 can be defined encoded information. After detecting the encoded information in the wake-up signal 1, the target mobile phone can determine that the wake-up signal 1 is used to trigger the target mobile phone to execute the customized power-on motivation service. As mentioned above, the wake-up signal 1 may or may not carry the identifier of the target mobile phone, and this application does not limit it.

[0105] S307: Based on the aforementioned communication connection, the host computer sends customized boot screen data to the target mobile phone.

[0106] After a successful communication connection is established between the host computer and the target mobile phone, the host computer can send customized boot screen data to the target mobile phone through this communication connection, thus successfully writing the customized boot screen data to the target mobile phone without damaging the packaging.

[0107] S308: The target phone writes the customized boot screen data to the target storage location.

[0108] After receiving the customized boot screen data, the target mobile phone writes the received customized boot screen data to the target storage location. Thus, when booting up, it can determine from the target storage location that the customized boot screen data exists and display the customized boot screen data.

[0109] Optionally, the customized boot screen data has a higher priority than the target phone's default boot screen data (i.e., the boot screen data that is uniformly fixed for the target phone model, i.e., the boot screen data preset at the factory). Thus, the target storage location and the location storing the default boot screen data (or the second boot screen data) can be in the same directory or in different directories. Accordingly, when the target phone is powered on for the first time, it can read the higher-priority customized boot screen from the target storage location and display it.

[0110] Alternatively, the target storage location and the location where the default boot screen data is stored may be in different directories. Upon first powering on the target phone, the phone can first determine if boot screen data exists in the target storage location. If boot screen data exists, it indicates the presence of customized boot screen data. The target phone then reads the customized boot screen data from the target storage location and displays the customized boot screen.

[0111] If the boot screen data is not present in the target storage location, it means that there is no customized boot screen data. The target phone will then read the default boot screen data from the location where the default boot screen data is stored and display a unified default boot screen (or second boot screen).

[0112] The identifier (such as name) of the customized boot screen data is different from that of the default boot screen data. Typically, the target storage location is in a different directory than the location where the default boot screen data is stored.

[0113] Optionally, the priority of the aforementioned customized boot screen data can be sent by the host computer. And / or, the priority of the default boot screen data can also be sent by the host computer. Furthermore, the priority of the customized boot screen data and / or the priority of the default boot screen data can also be set by the target mobile phone; this application does not limit this.

[0114] Optionally, the target storage location can be located in the memory of the target mobile phone.

[0115] S309, the target phone re-enters the wake-up state.

[0116] For example, after the customized boot screen data is written to the target storage location, it indicates that the boot screen customization service operation has been completed, and the target mobile phone can be powered off again, that is, turn off all devices except the wake-up receiver to save power.

[0117] The above describes the process of writing the customized boot screen data. After writing the customized boot screen data to the target phone, the target phone can be sent to the user. For example, before shipping, the host computer writes the customized boot screen data to the target phone inside the packaging box. Then, the target phone is shipped normally so that the user can receive it. Once the user receives the target phone, they can turn it on, and the target phone will display the customized boot screen. The following section will continue to describe the process of the target phone displaying the customized boot screen.

[0118] S310, The target mobile phone receives the power-on operation input by the user.

[0119] The power-on operation is used to trigger the target phone to turn on, such as triggering the power button on the target phone.

[0120] S311, In response to the power-on operation, the target mobile phone is powered on for the first time.

[0121] S312. Determine if the target mobile phone has customized boot screen data.

[0122] For example, when the target mobile phone is powered on for the first time, the target mobile phone can determine whether customized boot screen data exists in the target storage location. If customized boot screen data does not exist, the target mobile phone can execute S313.

[0123] If custom boot screen data exists, the target phone can execute S314-S315.

[0124] The existence of customized boot screen data on the target phone can be determined using the methods described above. For example, the target storage location and the location where the default boot screen data is stored may be in different directories. If the target phone determines that boot screen data exists in that target storage location, it can confirm the existence of customized boot screen data. Otherwise, the target phone can determine that customized boot screen data does not exist.

[0125] For example, the identifier for customized boot screen data differs from the identifier for default boot screen data. The target phone can access the identifiers of all boot screen data stored on the target phone. If any of the boot screen data identifiers contains an identifier other than the default boot screen data identifier, then that other boot screen data is customized boot screen data, and the target phone can confirm the existence of customized boot screen data. Conversely, if all the boot screen data identifiers are only the default boot screen data identifier, the target phone can confirm the absence of customized boot screen data.

[0126] S313, The target phone displays the default boot screen.

[0127] If there is no customized boot screen data during the first boot, the target phone can normally display the boot screen that is fixed for that specific phone model.

[0128] S314. The target mobile phone reads the customized boot screen data from the target storage location.

[0129] S315, The target mobile phone displays the customized boot screen corresponding to the customized boot screen data.

[0130] Upon initial power-on, if customized boot screen data exists, the target phone can display the corresponding customized boot screen, enabling personalized boot screen display to meet user needs and improve the user experience. After booting, the target phone can display the user interface, such as the desktop, normally. For example, ... Figure 9 As shown, after the phone is powered on for the first time, it displays a customized boot screen. Figure 9 Screens 40 and 41 shown in the image are two of the screens in the boot animation. After the boot animation ends, the phone can display the home screen 42.

[0131] In some embodiments, the target mobile phone supports saving customized boot screen data. As described above. Figure 6 As shown, in step S401, the target mobile phone receives a save operation (or third operation) input by the user. This save operation triggers the saving of the customized boot screen. In step S402, in response to the save operation, the target mobile phone saves the customized boot screen data to its local image library.

[0132] The aforementioned save operation can be a user-triggered action on the save control, such as a click. Upon first display of the customized boot screen, the target phone can display the save control, which can be shown on the customized boot screen (see...). Figure 10(See the control 43 for saving the custom boot screen). Additionally, considering that users typically save the custom boot screen the first time it's displayed, the target phone can avoid displaying the save control on subsequent boots to prevent a decrease in user experience caused by displaying the save control every time the phone boots up.

[0133] Alternatively, during the use of the target phone, the user can customize the boot screen using the settings controls provided by the target phone. These settings controls may include a save function. For example, ... Figure 11 As shown, in response to a click on the settings application 50, the target phone displays a settings interface 51, which may include a custom boot screen option 52. The user can then click on the custom boot screen option 52. In response to this click, the target phone can display a custom boot screen interface 53, which includes settings controls for the custom boot screen, such as a save control 54. Subsequently, in response to the user clicking on the save control 54, the phone saves the custom boot screen to its local map library, allowing the user to view the custom boot screen through a local map library application.

[0134] It should be noted that the above Figure 10 The aforementioned control 43 for saving the customized boot screen or Figure 11 The corresponding settings controls for customizing the boot screen are only illustrative; this application can set the relevant controls according to actual needs.

[0135] In some embodiments, the target mobile phone supports settings for a customized boot screen display, allowing users to choose whether the boot screen displayed after the initial power-on is still the customized boot screen. For example, the target mobile phone supports stopping the display of the customized boot screen. As described above... Figure 6 As shown, in step S403, the target mobile phone receives user input for operation 1. Operation 1 is used to trigger the stopping of displaying the customized boot screen. In step S404, in response to operation 1, the target mobile phone sets its default boot screen as the boot screen. Then, in step S405, the target mobile phone displays the default boot screen when it is not the first time it is powered on. The target mobile phone will display the default boot screen on the next boot.

[0136] For example, the target phone offers such as Figure 11The switch control 55 shown is for displaying a customized boot screen. When the switch control 55 is in the on state, the target phone will display the customized boot screen the next time it is powered on. When the switch control 55 is in the off state, the target phone will not display the customized boot screen the next time it is powered on, and will display the default boot screen. The above operation 1 can be an operation that triggers the switch control 55 to switch to the off state. It should be understood that if the switch control 55 is in the on state, the target phone can display the customized boot screen on subsequent boots, i.e., not the first time it is powered on.

[0137] In addition, triggering the target mobile phone to stop displaying the customized boot screen via the switch control 55 is only one example of operation 1 (or the second operation). Operation 1 can also be other types of operations, such as voice operation, etc., which are not limited in this application.

[0138] Optionally, in response to operation 1 above, the target mobile phone can increase the priority of the default boot screen data and / or decrease the priority of the customized boot screen data, so that the priority of the default boot screen data is higher than that of the customized boot screen data, thereby setting the default boot screen of the target mobile phone as the boot screen.

[0139] In some embodiments, the target mobile phone supports the deletion of customized boot screen data. Examples are as described above. Figure 6 As shown, in step S406, the target phone receives user input for operation 2. Operation 2 triggers the deletion of customized boot screen data. In step S407, in response to operation 2, the target phone deletes the customized boot screen data from the target storage location, thereby deleting the customized boot screen. Then, in step S408, in cases other than the first boot, the target phone displays the default boot screen. For example, on subsequent boots, the target phone displays the default boot screen. Based on this, when a user no longer uses the target phone, such as when returning or exchanging it, the user can delete the customized boot screen data on the target phone, preventing user data leakage and protecting user privacy.

[0140] For example, in response to the user's above Figure 11 The triggering operation of the delete control 56 shown causes the target phone to delete the customized boot screen data from the target storage location. Operation 2 described above can be a triggering operation of the delete control 56. Furthermore, triggering the target phone to delete the customized boot screen data via the delete control 56 is only one example of operation 2 (or the first operation). Operation 2 can also be other types of operations, such as voice operations, or triggering operations of the delete control displayed on the customized boot screen, etc.

[0141] Optionally, if the target phone's local gallery also stores the customized boot screen data, in response to operation 2 above, the target phone not only deletes the customized boot screen data from the target storage location, but also deletes the customized boot screen data stored in its local gallery.

[0142] In some embodiments, the host computer can be an electronic device with communication capabilities, such as a mobile phone, tablet computer, server, or wearable device.

[0143] In some embodiments, the process of writing customized boot screen data described in S301-S309 above is only an example, and customized boot screen data can also be written to the target mobile phone in other ways. For example, relevant personnel can unpack the target mobile phone and turn it on. Afterwards, the host computer can transmit the customized boot screen data to the target mobile phone.

[0144] It should be noted that the operations performed by the wake-up receiver, MCU, main communication unit, and other devices in the target mobile phone described above can also be performed by other devices. This application does not impose any restrictions on the devices that perform the above steps. However, in general, the operations performed by the devices in the target mobile phone are actually performed by the target mobile phone itself. In other words, the target mobile phone is the subject of execution of the technical solution described in this application.

[0145] The above mainly describes the solutions provided by the embodiments of this application from a methodological perspective. It is understood that, in order to achieve the above functions, the electronic device includes hardware structures and / or software modules corresponding to the execution of each function. Based on the units and algorithm steps of the various examples described in the embodiments disclosed in this application, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software.

[0146] Whether a function is implemented through hardware or by a computer-driven hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described function for each specific application, but such implementations should not be considered beyond the scope of the technical solutions in this application.

[0147] This application provides embodiments for dividing an electronic device into functional modules based on the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into a single processing unit. The integrated unit can be implemented in hardware or as a software functional module. It should be noted that the unit division in this application embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used.

[0148] like Figure 12The diagram shown is a structural schematic of an electronic device provided in an embodiment of this application. This electronic device 1000 can be used to implement the methods executed by the electronic devices described in the above method embodiments. For example, the electronic device 1000 may include a processing unit 1001, a communication unit 1002, and a display unit 1003. The processing unit 1001 is used to support the electronic device 1000 in executing... Figures 1 to 11 The electronic device described in any one of the following embodiments includes a communication unit 1002 for supporting the communication function of the electronic device 1000, and a display unit 1003 for supporting the display function of the electronic device 1000.

[0149] Optional, Figure 12 The electronic device 1000 shown may also include a storage unit ( Figure 12 (Not shown in the image), this storage unit stores a program or instruction. When the processing unit 1001 executes the program or instruction, it causes... Figure 12 The electronic device 1000 shown can perform the method described in the above-described method embodiments.

[0150] Figure 12 The technical effects of the electronic device 1000 shown can be referred to the technical effects described in the above method embodiments, and will not be repeated here. Figure 12 The processing unit 1001 in the illustrated electronic device 1000 can be implemented by a processor or processor-related circuit components, and can be a processor or processing module. The communication unit 1002 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver module. The display unit 1003 can be implemented by display screen-related components.

[0151] This application also provides a chip system, such as... Figure 13 As shown, the chip system includes at least one processor 1101 and at least one interface circuit 1102. The processor 1101 and the interface circuit 1102 are interconnected via lines. For example, the interface circuit 1102 can be used to receive signals from other devices. As another example, the interface circuit 1102 can be used to send signals to other devices (e.g., the processor 1101). Exemplarily, the interface circuit 1102 can read instructions stored in memory and send those instructions to the processor 1101. When the instructions are executed by the processor 1101, the electronic device can perform the various steps performed by the electronic device in the above embodiments. Of course, the chip system may also include other discrete devices, and this application embodiment does not specifically limit this.

[0152] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0153] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application does not specifically limit the type of memory or the arrangement of the memory and processor.

[0154] For example, the chip system can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0155] It should be understood that each step in the above method embodiments can be completed by integrated logic circuits in the processor hardware or by instructions in software form. The method steps disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0156] This application also provides a computer storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the boot screen display method described in the above method embodiments.

[0157] This application provides a computer program product, which includes a computer program or instructions that, when executed on an electronic device, cause the electronic device to perform the boot screen display method described in the above method embodiments.

[0158] In addition, this application embodiment also provides an apparatus, which may specifically be a chip, component, or module. The apparatus may include a connected processor and a memory. The memory stores computer execution instructions. When the apparatus is running, the processor executes the computer execution instructions stored in the memory to cause the apparatus to perform the boot screen display method in the above-described method embodiments. The electronic device, computer storage medium, computer program product, or chip provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they achieve can be referred to in the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0159] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0160] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The embodiments can be combined with or referenced to each other without conflict. The apparatus embodiments described above are merely illustrative; for example, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0161] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0162] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0163] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A method for displaying a boot screen, characterized in that, Applied to a first device, the method includes: During the storage phase of the first device, the first device is in a wake-up state; wherein, the wake-up state means that all devices except the wake-up receiver in the first device are in a turned-off state, and the packaging of the first device is not damaged during the storage phase; The wake-up receiver receives the first wake-up signal sent by the second device. Based on the fact that the first wake-up signal includes the unique identifier of the first device, or that the quality of the first wake-up signal is greater than a preset quality value, in response to the first wake-up signal, the wake-up receiver performs a wake-up operation on the first device; wherein, the screen of the first device is in a black screen state after being woken up; Establish a communication connection with the second device; Based on the communication connection, receive data of the first boot screen sent by the second device; Re-enter the awakened state; When a user powers on the device for the first time, the first boot screen is displayed.

2. The method according to claim 1, characterized in that, The method further includes: Receive the first operation; In response to the first operation, the data on the first boot screen is deleted; If the device is not powered on for the first time, a second boot screen will be displayed; wherein the second boot screen is different from the first boot screen.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Receive the second operation; In response to the second operation, stop using the first boot screen as the boot screen; If the device is not powered on for the first time, a second boot screen will be displayed; wherein the second boot screen is different from the first boot screen.

4. The method according to claim 1 or 2, characterized in that, The method further includes: Receive third operation; In response to the third operation, the first boot screen is saved; During the operation of the first device, in response to the fourth operation, the first power-on screen is displayed.

5. The method according to claim 1 or 2, characterized in that, After receiving the data of the first boot screen sent by the second device, the method further includes: The data in the first boot screen is given a higher priority than the data in the second boot screen; the second boot screen is different from the first boot screen.

6. An electronic device, characterized in that, The electronic device, as the first device, includes a wake-up receiver, a display screen, a communication module, a memory, and one or more processors; The wake-up receiver is used to receive a first wake-up signal sent by the second device, and the first wake-up signal is used to trigger the wake-up of the electronic device. The communication module is used to receive data of the first boot screen transmitted by the second device; The display screen is used to display an image generated by the processor, the image including a boot screen; The memory is used to store computer program code, which includes computer instructions; when the processor executes the computer instructions, the electronic device performs the boot screen display method as described in any one of claims 1 to 5.

7. A computer-readable storage medium, characterized in that, The method includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the boot screen display method as described in any one of claims 1 to 5.

8. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the boot screen display method as described in any one of claims 1 to 5.

Images