System starting method and device, electronic equipment and storage medium

Abstract

This application discloses a system startup method, apparatus, electronic device, and storage medium. It relates to the field of terminal technology. Applied to electronic devices having a first operating system and a second operating system, the method includes: if the second operating system is not started, and if its startup time has arrived, starting the second operating system. The startup time of the second operating system is determined based on the user's usage habits of the second operating system. In this application, when the second operating system of the electronic device is not started, the actual startup time of the second operating system is controlled based on whether the current time has arrived. This avoids the problem of wasted power consumption caused by starting the second operating system when the user is not using it, reduces the ineffective power consumption of the electronic device, and improves the battery life of the electronic device.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a system startup method, apparatus, electronic device, and storage medium. Background Technology

[0002] With the development of science and technology, all kinds of electronic devices have appeared in people's daily lives, and people can use electronic devices for entertainment, learning, and so on.

[0003] The operating system, as the foundation for various functions in electronic devices, controls the operation of various applications. In some electronic devices, to facilitate control over different applications, developers have configured two operating systems. These two operating systems consume different amounts of power; some low-power applications can run on the first operating system, while some high-power applications can run on the second. In such scenarios with multiple operating systems, improving the control of electronic devices with two or more operating systems is a pressing problem that needs to be solved. Summary of the Invention

[0004] To address the problems in related technologies, this solution allows electronic devices with a first operating system and a second operating system to control the startup time of the second operating system, which consumes more power, based on the user's usage habits. This reduces unnecessary power consumption and improves the battery life of the electronic device. This application provides a system startup method, apparatus, electronic device, and storage medium. The technical solution is as follows:

[0005] In one aspect, embodiments of this application provide a system startup method applied to an electronic device, the electronic device including a first operating system and a second operating system, wherein the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system, the method comprising:

[0006] If the second operating system is not started, it will start when the second operating system's startup time is reached. The startup time of the second operating system is determined based on the user's usage habits of the second operating system.

[0007] In another aspect, embodiments of this application provide a system startup device applied to an electronic device, the electronic device including a first operating system and a second operating system, wherein the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system, the device comprising:

[0008] The system startup module is used to start the second operating system if the second operating system has not been started and the startup time of the second operating system has been reached. The startup time of the second operating system is determined according to the user's usage habits of the second operating system.

[0009] In another aspect, this application provides an electronic device including a processor and a memory, the memory storing a computer program executable on the processor, wherein the processor executes the computer program to implement the system startup method as described in one aspect above.

[0010] In another aspect, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the system startup method as described in one of the preceding aspects.

[0011] On the other hand, embodiments of this application provide a computer program product that, when run on a computer, causes the computer to execute to implement the system startup method as described in one aspect above.

[0012] On the other hand, embodiments of this application provide an application publishing platform for publishing computer program products, wherein when the computer program product is run on a computer, the computer executes to implement the system startup method as described in one aspect above.

[0013] The beneficial effects of the technical solutions provided in this application include at least the following:

[0014] In electronic devices with a first operating system and a second operating system, the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system. If the second operating system is not started, it will be started if its scheduled startup time is reached. The startup time of the second operating system is determined based on the user's usage habits. In this application, when the second operating system is not started, the actual startup time of the electronic device is controlled based on whether the current time has reached the startup time of the second operating system. This avoids the problem of wasted power consumption caused by starting the second operating system when the user is not using it, reduces the ineffective power consumption of the electronic device, and improves the battery life of the electronic device. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 A schematic diagram of the structure of an electronic device provided as an exemplary embodiment of this application;

[0017] Figure 2 A flowchart of a system startup method provided as an exemplary embodiment of this application;

[0018] Figure 3 A flowchart of a system startup method provided as an exemplary embodiment of this application;

[0019] Figure 4 This is a schematic diagram illustrating the stages of an electronic device collecting usage information according to an exemplary embodiment of this application;

[0020] Figure 5 This is a schematic diagram illustrating the time point for starting a second operating system in an electronic device according to an exemplary embodiment of this application;

[0021] Figure 6 A flowchart illustrating a method for starting an electronic device control system, provided as an exemplary embodiment of this application;

[0022] Figure 7 This is a schematic diagram of a first interface displayed by an electronic device according to an exemplary embodiment of this application;

[0023] Figure 8 This is a schematic diagram of an application closing prompt interface displayed on an electronic device according to an exemplary embodiment of this application;

[0024] Figure 9 This is a schematic diagram of the startup process of an operating system for an electronic device according to an exemplary embodiment of this application;

[0025] Figure 10 This is a schematic diagram of a startup interface according to an exemplary embodiment of this application;

[0026] Figure 11 A structural block diagram of a system startup device provided for an exemplary embodiment of this application. Detailed Implementation

[0027] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

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

[0029] It should be noted that the terms "first, second, third" used in the embodiments of this application are used to distinguish similar or different objects and do not represent a specific order of objects. It can be understood that "first, second, third" can be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0030] The solution provided in this application can be used in real-world scenarios where people control how multiple operating systems are started when using electronic devices with multiple operating systems in their daily lives. To facilitate understanding, some terms and application scenarios involved in the embodiments of this application will be briefly introduced below.

[0031] Big core: In electronic devices, the operating system with higher power consumption is simply referred to as the big core.

[0032] Small core: In electronic devices, a low-power operating system is often referred to as a small core.

[0033] Hybrid mode: A mode in which a high-power operating system and a low-power operating system run simultaneously in an electronic device, that is, a mode in which both large cores and small cores run.

[0034] With the development of science and technology, various electronic devices have appeared in people's daily lives, allowing them to use them for entertainment, learning, and other purposes. Among these devices, the operating system serves as the foundation for all functions, controlling the operation of various applications. For example, the applications downloaded by users onto their electronic devices all require the operating system to run, enabling the device to provide its corresponding functions.

[0035] In some electronic devices, developers set up two operating systems to facilitate the control of different applications. The power consumption of the two operating systems is different. Some low-power applications can run on the first operating system, while some high-power applications can run on the second operating system.

[0036] Please refer to Figure 1 This illustration shows a schematic diagram of the structure of an electronic device provided in an exemplary embodiment of this application. The electronic device 100 may include, but is not limited to, wearable devices (such as wristbands, smartwatches, smart glasses, or other smart wearable devices that can be worn on a user's body), mobile phones, tablets, laptops, smart glasses, smartwatches, MP3 players (Moving Picture Experts Group Audio Layer III), MP4 players (Moving Picture Experts Group Audio Layer IV), desktop computers, laptop computers, etc.

[0037] Optionally, the electronic device 100 in this application may include one or more of the following components: a first processor 110, a second processor 120, a memory 130, and a display module 140.

[0038] The first processor 110 (and / or the second processor 120) may include one or more processing cores. The first processor 110 (and / or the second processor 120) connects to various parts within the electronic device 100 using various interfaces and lines, and performs various functions and processes data of the electronic device 100 by running or executing instructions, programs, code sets, or instruction sets stored in the memory 130, and by calling data stored in the memory 130. Optionally, the first processor 110 (and / or the second processor 120) may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The first processor 110 (and / or the second processor 120) may integrate one or a combination of several of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), Neural Network Processing Unit (NPU), and modem.

[0039] Optionally, the CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content required to be displayed by the display module 140; the NPU is used to implement artificial intelligence (AI) functions; and the modem is used to handle wireless communication. It is understood that the aforementioned modem may also not be integrated into the first processor 110 (and / or the second processor 120), but may be implemented as a separate chip.

[0040] In this embodiment, the first processor 110 is used to run a first operating system, and the second processor 120 is used to run a second operating system.

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

[0042] Optionally, the display module 140 is a display component for displaying a user interface. Optionally, the display module 140 is a touch-enabled display module, through which users can use their fingers, styluses, or any suitable object to perform touch operations on the display module 140.

[0043] The display module 140 is typically located on the front panel of the electronic device 100. The display module 140 can be designed as a full-screen, curved screen, irregularly shaped screen, dual-sided screen, or foldable screen. The display module 140 can also be designed as a combination of a full-screen and a curved screen, or a combination of an irregularly shaped screen and a curved screen, etc., but this embodiment does not limit its design. Furthermore, the display module 140 can be configured using a liquid crystal display (LCD), an organic light-emitting diode (OLED), or other similar forms, and this is not limited here.

[0044] In addition, those skilled in the art will understand that the structure of the electronic device 100 shown in the above figures does not constitute a limitation on the electronic device 100. The electronic device 100 may include more or fewer components than shown, or combine certain components, or have different component arrangements. For example, the electronic device 100 may also include components such as a microphone, speaker, radio frequency circuit, input unit, sensor, audio circuit, Wireless Fidelity (WiFi) module, power supply, and Bluetooth module, which will not be described in detail here.

[0045] Optionally, for the above Figure 1 The electronic device shown has two operating systems. The control of the two operating systems is usually as follows: when the user controls the electronic device to restart or wake it from sleep, the electronic device will run both operating systems at the same time, thereby providing the user with the functional conditions to use various applications on the electronic device.

[0046] In one possible approach, if one operating system in the aforementioned electronic device has higher power consumption than the other, for example, the power consumption of the electronic device running the first operating system is less than that of the electronic device running the second operating system. For instance, the first operating system could be a Real-Time Operating System (RTOS), and the second operating system could be Android. After the electronic device is woken up, if the user is not currently using any applications related to the second operating system, then the above approach will result in wasted power consumption from the second operating system, additionally increasing the power consumption of the electronic device and potentially reducing its battery life.

[0047] To address the aforementioned problems in related technologies and improve the battery life of electronic devices, this application provides a system startup method that allows electronic devices with a first operating system and a second operating system to start the second operating system only when the second operating system's startup time is reached, even if the second operating system is not yet started. This reduces the power consumption caused by running the second operating system when it is not in use.

[0048] Please refer to Figure 2 This illustration shows a flowchart of a system startup method provided in an exemplary embodiment of this application. This system startup method can be applied to electronic devices having a first operating system and a second operating system, wherein the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system. Figure 2 As shown, the system startup method may include the following steps:

[0049] Step 201: If the second operating system is not started, start the second operating system when the startup time of the second operating system is reached. The startup time of the second operating system is determined according to the user's usage habits of the second operating system.

[0050] Optionally, the electronic device in this application includes a first operating system and a second operating system, and the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system. When the second operating system of the electronic device is not started, the system can detect whether the current time has reached the startup time of the second operating system. If it has, the second operating system is then started. This allows the high-power second operating system to be started based on the user's usage habits, avoiding the power waste caused by directly starting the second operating system before the user has used it, and improving the battery life of the electronic device.

[0051] Optionally, when the secondary operating system of the electronic device is not started, it may mean that the secondary operating system is in a closed state or in sleep mode. The sleep mode in this solution may include normal sleep and deep sleep. Normal sleep refers to saving the current working state of the secondary operating system to memory, without powering down the memory, and shutting down other hardware devices—an energy-saving method. Deep sleep refers to saving the current working state of the secondary operating system to the hard drive and powering down the memory—an energy-saving method. Deep sleep saves more power than normal sleep, but switching to start the secondary operating system takes longer than normal sleep.

[0052] Optionally, the boot time of the second operating system is determined based on the user's usage habits, and can be acquired and set by the electronic device. For example, the electronic device can collect data on the user's usage habits of the second operating system, obtain the boot time of the second operating system based on these habits, and set it in the electronic device. For instance, based on the user's usage habits, if it is found that the user usually uses the second operating system at 7:00 AM, then the boot time of the second operating system can be set to 7:00 AM, and the second operating system will start at that specific time.

[0053] In summary, in electronic devices with a first operating system and a second operating system, the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system. If the second operating system is not started, it will be started when its scheduled startup time is reached. The startup time of the second operating system is determined based on the user's usage habits. In this application, when the second operating system is not started, the actual startup time of the electronic device is controlled based on whether the current time has reached the startup time of the second operating system. This avoids the problem of wasted power consumption caused by starting the second operating system when the user is not using it, reduces the ineffective power consumption of the electronic device, and improves the battery life of the electronic device.

[0054] The following describes an electronic device that can store user usage records of a target application. The target application is an application that runs on a second operating system. The user's usage habits of the second operating system are determined based on this usage information. This makes the startup time of the second operating system in the electronic device more consistent with the user's usage habits. It ensures that the startup time of the high-power second operating system is closer to the time when the user actually uses the application running on the second operating system, thus avoiding power waste caused by the electronic device starting the second operating system but not using it.

[0055] Please refer to Figure 3 This illustration shows a flowchart of a system startup method provided in an exemplary embodiment of this application. This system startup method can be applied to electronic devices having a first operating system and a second operating system, wherein the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system. Figure 3 As shown, the system startup method may include the following steps:

[0056] Step 301: Obtain usage information, which includes the user's usage history of the target application, which is an application running on a second operating system.

[0057] Optionally, usage information refers to a user's usage records of the target applications on the electronic device. For example, tracking points can be pre-set in the electronic device to record the user's daily usage of the target applications. Developers can pre-set corresponding tracking points for certain target applications on the electronic device to record the user's usage habits during the device's operation, thus reflecting the user's usage habits of the secondary operating system.

[0058] Optionally, since the electronic device contains two operating systems, the applications running on these two operating systems are usually different. For example, the higher-powered second operating system typically runs applications with higher power consumption (such as chat applications), while the lower-powered first operating system typically runs applications with lower power consumption (such as some low-level system applications). The target application mentioned above is any application running on the higher-powered second operating system. For example, for target application one, the user habitually launches the application at 8:00 AM every day. Through a period of data tracking testing, the electronic device will obtain the user's usage records for target application one, which will include the application identifier of target application one and the corresponding launch time of 8:00 AM.

[0059] Step 302: Based on the usage information, obtain the user's usage habits of the second operating system. The usage habits include the times when the user actually starts the second operating system within a preset period.

[0060] Optionally, in this solution, to ensure more accurate startup of the second operating system, the user's usage habits for the second operating system are obtained by combining the usage information acquired above. These usage habits include the times when the user actually starts the second operating system within a preset period. The preset period can be pre-set by the developers; for example, a typical preset period is one day, which includes the times when the user actually starts the second operating system each day.

[0061] For example, the usage information obtained above, including the user's usage records of the target application, can be as follows: each time the user launches the target application during the use of the electronic device. The electronic device can obtain the user's usage habits of the second operating system in the following way: For example, the electronic device divides each time the user launches the target application during the use of the electronic device into preset periods (e.g., by day), and detects each time the user launches the target application within each day.

[0062] Optionally, after the above segmentation, the electronic device detects the time points when the user uses the target application each day. If the user launches the target application at roughly the same time each day, then these time points are the user's habitual times for using the target application, and correspondingly, these time points represent the user's usage habits on the second operating system. For example, after detecting the time points when the user uses the target application each day, it is found that these recorded time points indicate that the user habitually launches a target application running on the second operating system around 8:00 AM, around 10:00 AM, around 1:00 PM, and around 6:00 PM. Therefore, the user's usage habits on the second operating system are habitually using it at 8:00 AM, 10:00 AM, 1:00 PM, and 6:00 PM.

[0063] In one possible implementation, the electronic device can detect the time points when a user uses the target application each day as follows: It counts the number of times the user uses the target application within various preset time periods each day. These preset time periods are, for example, divided by hours (8:00-9:00, 9:00-10:00, etc.). By counting the number of times the user launches the target application within each time period (equivalent to the number of times a secondary operating system is launched), if the number of launches in a certain time period exceeds a preset number, then the midpoint of that time period is considered one of the user's habits of using the secondary operating system. The preset number of launches can also be pre-set by the developers within the electronic device.

[0064] Optionally, the preset number of times can automatically change based on the number of days the user uses the electronic device. For example, the preset number could be the number of days the user uses the electronic device plus one time. Based on the above statistics, if the number of times the user launches the second operating system between 8:00 and 9:00 is greater than the preset number, then 8:30 is considered a user's habit of using the second operating system. That is, the user's usage habit of the second operating system includes launching it at 8:30. Of course, in practical applications, the exact times between 8:00 and 9:00 can also be used as the actual times the user launches the second operating system; this is not a limitation here.

[0065] In one possible implementation, the electronic device may also perform the following process: determine the user's usage pattern level based on usage information, wherein the higher the usage pattern level, the closer the time when the user starts the second operating system each time within each preset cycle; if the pattern level is greater than the preset level, obtain the user's usage habits of the second operating system based on usage information; if the pattern level is not greater than the preset level, control the second operating system to enter sleep mode.

[0066] Optionally, after acquiring usage information, the electronic device determines the usage pattern level corresponding to the usage information. If the time of each touch of the electronic device by the user within each preset cycle is closer, it indicates that the user's behavior of starting the second operating system is more regular. If the time of each touch of the electronic device by the user within each preset cycle is farther apart, it indicates that the user's behavior of starting the second operating system is less regular. If the pattern level is greater than the preset level, step 302 is executed. If the pattern level is not greater than the preset level, the second operating system can be controlled to enter sleep mode so that the second operating system can be started faster than in the off state.

[0067] Optionally, the process of determining the user's usage pattern level based on usage information can be as follows: Using a pre-set period of days as an example, since the usage information includes the user's daily usage records of the target application, i.e., the time spent touching the target application each time, the difference between the user's touch time on the target application on the following day and the user's touch time on the target application on the previous day is compared. For example, taking the user's touch time of the target application within the same time period as 8:00 AM to 9:00 AM, if the user touches the target application at 8:10 AM on the following day and at 8:49 AM on the previous day, the difference is 39 minutes. Using a pre-set difference of 0 to 20 minutes, 20 to 40 minutes, and 40 to 60 minutes to divide different pattern levels, then the pattern level obtained this time is the pattern level corresponding to 20 to 40 minutes. This is only an example of two consecutive days. In actual applications, there will be many days. For the same time period across multiple days, the difference is calculated to obtain the maximum time difference across multiple days within the same time period, and then the corresponding usage pattern level is determined.

[0068] Please refer to Table 1, which shows the relationship between the rules and the corresponding rule levels in an exemplary embodiment of this application.

[0069] Table 1 shows the relationship between usage patterns and their corresponding pattern levels.

[0070] Usage Information Time difference Regularity level Information 1 0 to 20 minutes Rule Level 1 Information 2 20 to 40 minutes Pattern Level Two Information 3 40 minutes or more Pattern Level 3 …… ……

[0071] For example, regarding the time when a user first launches the target application each morning, as mentioned in usage information one, the user's usage pattern is generally around 8 AM. Furthermore, the largest time difference across these usage days is within 20 minutes. Referring to Table 1 above, the corresponding pattern level is pattern level one. Of course, if the largest time difference exceeds 40 minutes, the corresponding pattern level would be pattern level three.

[0072] In this solution, the preset level can also be set by the developers or users in the electronic device. After determining the above usage pattern level, the usage pattern level is compared with the preset level. If it is greater than the preset level, it indicates that the user's usage is relatively regular, and the step of obtaining the user's usage habits of the second operating system based on usage information can be executed. Taking the preset level as the above usage pattern level two as an example, if the usage pattern level corresponding to the obtained usage pattern is usage pattern level one, step 302 can be executed. If the usage pattern level corresponding to the obtained usage pattern is usage pattern level three, which is not greater than the preset level, the electronic device can execute the following steps: control the second operating system to enter sleep mode. For example, when the electronic device is running the first operating system, control the second operating system to enter sleep mode. In this mode, the memory space corresponding to the second operating system can be written to the EMMC (Embedded Multi Media Card), and the memory can be powered off.

[0073] In other words, based on the above-mentioned usage pattern level and preset level determination, if the user uses the target application regularly and touches the target application on the electronic device at fixed times every day (for example, at 8 am, 10 am, 1 pm, etc.), then the user's usage habits of the second operating system will also be regular based on the usage information, and the determined startup time of the second operating system will easily match the user's usage habits.

[0074] If a user's usage history of the target application is irregular, meaning the usage regularity level is lower than the preset level, the user may trigger the target application at any time. In order to reduce the user's waiting time, this solution can put the second operating system into sleep mode after waking up the electronic device and starting the first operating system. This can be adapted to users with low usage regularity, achieving the effect of quickly starting the second operating system as the user uses the target application.

[0075] In one possible implementation, the electronic device can also perform the following steps: if the regularity level is greater than a preset level, determine the target shutdown time of the second operating system based on the user's usage habits; while the second operating system is running, shut it down when the target shutdown time is reached. That is, if the aforementioned regularity level is greater than a preset level, it indicates that the user's usage history of the target application is relatively regular. In addition to determining the startup time of the second operating system, the target shutdown time can also be determined based on the time of the user's last use of the target application, as included in the usage information. For example, if the user exits the target application at 8 PM every day and then does not run the target application again, 8 PM can be set as the target shutdown time. At this time each day, the second operating system can be automatically shut down, reducing the power consumption of the electronic device.

[0076] Step 303: Determine the startup time of the second operating system within the preset period based on usage habits, including the actual startup times of the second operating system within the preset period.

[0077] Optionally, after obtaining the above usage habits, the electronic device can set the startup time of the second operating system within the preset period based on the actual times when the user starts the second operating system within the preset period according to the usage habits.

[0078] Using the aforementioned preset cycle of one day as an example, the obtained usage habits are as follows: users habitually use the secondary operating system at 8:00 AM, 10:00 AM, 1:00 PM, and 6:00 PM. Therefore, the electronic device can be set to advance the startup time of the secondary operating system by half an hour each time point in the usage habits. The set startup times for the secondary operating system would be: 7:30 AM, 9:30 AM, 12:30 PM, and 5:30 PM. Advancing the startup time by half an hour is just one example; in practical applications, the advance time can be appropriately set based on the specific usage habits, such as 10 minutes or 20 minutes. This is not a limitation.

[0079] Optionally, in this solution, the electronic device has the function of optimizing the startup time of the second operating system in a phased manner. For example, the electronic device can also perform the following steps: the electronic device determines the current usage phase of the electronic device; based on the current usage phase of the electronic device, it obtains usage information corresponding to the usage phase, wherein the usage information required for different usage phases is different; based on the usage information corresponding to the usage phase, it updates the user's usage habits of the second operating system.

[0080] In other words, electronic devices can also obtain corresponding usage information based on their current usage stage and update the usage habits of the second operating system determined above. Optionally, this update process can be periodic.

[0081] In one possible implementation, the electronic device contains a target timer. The method for obtaining the current usage stage of the electronic device in this step can be as follows: obtain the accumulated time data of the target timer; determine the current usage stage of the electronic device based on the accumulated time data of the target timer. For example, after the electronic device is initially powered on, the time data in the target timer can be initialized to 0 days. Subsequently, the electronic device directly obtains this data to know how many days the electronic device has been used by the user, thereby determining the current usage stage of the electronic device.

[0082] Optionally, the usage information required varies at different usage stages, and electronic devices need to acquire usage information corresponding to the current stage. When acquiring usage information, if a user is just starting to use the electronic device, the user's usage records are limited during this period, and the electronic device can acquire usage information corresponding to this time period according to its own needs. As the user's usage time increases, the usage records within the electronic device will gradually increase, and therefore, the electronic device will acquire more usage information in subsequent periods. The startup time of the second operating system determined based on the usage information acquired at different usage stages will mostly be different, making the startup time of the second operating system more in line with the user's usage habits, thereby improving the accuracy of the electronic device in determining the startup time of the second operating system.

[0083] Optionally, the target timer can operate on a fixed time period. For example, this time period can be set by the developer or user. Taking a target timer with a time period of days as an example, the accumulated time data of the target timer in the electronic device is X days. Based on the time period corresponding to this time data, the usage information corresponding to that time period is obtained. Each time period can also be set by the developer or user in the electronic device.

[0084] For example, if the target timer's timing cycle is in days, the preset time periods include 0-10 days, 10-20 days, 20-30 days, and more than 30 days. If the target timer's timing cycle is in weeks, the preset time periods include 0-7 weeks, 8-20 weeks, and more than 20 weeks. The specific division rules can be flexible and will not be elaborated here. For instance, if the accumulated time data from the target timer is 5 days, then the current usage phase of the electronic device is determined to be the 0-10 day phase.

[0085] In one possible implementation, the electronic device obtains usage information corresponding to its current usage stage as follows: If the current usage stage is the first time stage, the obtained usage information includes the user's usage pattern of launching the second operating system; if the current usage stage is the second time stage, the obtained usage information includes the time record of the alarm clock application of the electronic device; if the current usage stage is the third time stage, the obtained usage information includes the user's behavior record of launching the target application for the first time each day; if the current usage stage is the fourth time stage, the obtained usage information includes the behavior information of launching the second operating system of the electronic device in the target usage scenario; wherein the first time stage, the second time stage, the third time stage, and the fourth time stage increase sequentially in time order.

[0086] In other words, electronic devices can detect which usage stage the current time data belongs to based on the accumulated time data of the target timer, and obtain usage information corresponding to the current usage stage based on the different usage stages they are in.

[0087] For example, the first time period is the period when a user first starts using the electronic device (e.g., the 0-10 days mentioned above). During this first time period, since the user has just started using the electronic device, not much usage information has been recorded. If the user's usage habits of the second operating system are updated at this time, the usage records of the target application obtained during this period are still being used. That is, the electronic device determines the user's usage habits of the second operating system based on the usage information corresponding to this usage period, and then updates the previously determined startup time of the second operating system within a preset period based on the newly determined usage habits. Optionally, determining the user's usage habits of the second operating system based on the usage information corresponding to this usage period and re-determining the startup time of the second operating system based on the usage habits is similar to the above method, and will not be elaborated here.

[0088] Optionally, the second time period can be a period during which the user has continuously used the electronic device (e.g., the aforementioned 10-20 days). During this period, the user may have used most of the applications. For example, the user may have used an alarm clock application during this time. The usage information is the time record of the alarm clock application on the electronic device, including the time information such as what time the alarm rings in the morning and at noon each day. Here, in the process of updating the startup time of the second operating system within the preset period based on the usage information corresponding to the usage period, since alarms are usually set in the morning, if the startup time of the second operating system within the preset period includes starting the second operating system at 7:30 AM, and the time record of the alarm clock application shows that the user usually wakes up at 6:30 AM, then based on the time record of the alarm clock application, the new usage habit determined includes starting the second operating system at 6:30 AM, and the startup time of the second operating system is determined to be 7:00 AM. The previously determined startup time of the second operating system within the preset period of 7:30 AM is changed to 7:00 AM, completing the update of the startup time of the second operating system every morning, making the startup time of the second operating system more accurate.

[0089] In one possible implementation, the boot time of the second operating system can be set to multiple times, depending on the user's usage habits. Please refer to [reference needed]. Figure 5 This illustrates a schematic diagram of the time point at which a second operating system is started in an electronic device according to an exemplary embodiment of this application. Figure 5 As shown, this includes the alarm clock app's ringing time 501, which is recorded daily in usage information, and the secondary operating system's startup time 502, set daily based on this usage habit. Here, we only use the alarm clock app's ringing time as an example to demonstrate how the usage pattern is determined through the above process, ultimately determining the required startup time for the secondary operating system. Figure 5 It can be seen that the specific time for starting the second operating system can vary each day.

[0090] Optionally, the third time phase is a period of time during which the user continues to use the electronic device based on the second time phase (e.g., the 20-30 days mentioned above). During this period, the user generates more usage information from using the electronic device. The usage information obtained by the electronic device may include the behavior record of the first launch of the target application each day. By using the behavior record of the first launch of the target application each day, the second operating system updates the time of the first launch of the target application within the preset time period.

[0091] Optionally, the fourth time phase is a period during which the user continues to use the electronic device beyond the third time phase (e.g., more than 30 days as mentioned above). During this period, the user generates more usage information from the electronic device. This usage information can include behavioral information about the electronic device launching the second operating system in the target usage scenario. The target usage scenario can be defined by the developers or the user. For example, at 8:30 AM or 7:30 PM every day, users typically enter an underground parking lot to drive their cars. The target usage scenario can include the scenario where the electronic device is in the underground parking garage, and the user's behavioral records in these scenarios. For instance, in the underground parking garage, the user needs to use the car key function of the electronic device, requiring the launch of the second operating system. The electronic device records the time when the car key function is triggered in this target usage scenario, and based on this usage information, it obtains the corresponding usage habits during this usage phase and updates the launch time of the second operating system (which also needs to be launched at 8:30 AM or 7:30 PM every day).

[0092] Optionally, the target use case can also include scenarios where the user connects the electronic device to Bluetooth headphones (i.e., Bluetooth communication scenarios), and the behavioral information could be a record of how often the user launches a music application. Alternatively, the target use case could be a push notification scenario, and the behavioral information could be a record of how often the user clicks on the push notification. For example, after a push notification from a target application arrives, the record of how often the user clicks on the push notification, based on this usage information, could allow obtaining the corresponding usage habits at that stage. This could include launching a second operating system every 5 minutes after receiving a push notification. Therefore, when updating the startup time of the second operating system within a preset period, the startup time could be updated to include, in addition to the existing startup times, the ability to launch the second operating system after 5 minutes if the electronic device receives a push notification.

[0093] Optionally, the target use cases mentioned above can be determined by electronic devices or by combining big data or artificial intelligence (AI).

[0094] Taking the target timer's cycle as days, and the first time phase as 0-10 days, the second time phase as 10-20 days, the third time phase as 20-30 days, and the fourth time phase as greater than 30 days, as an example, please refer to the following: Figure 4 This illustration shows a phased diagram of an electronic device collecting usage information according to an exemplary embodiment of this application. Figure 4As shown, this includes a first time stage 401, a second time stage 402, a third time stage 403, and a fourth time stage 404. As time progresses, the usage information recorded in the electronic device increases, and the main usage information acquired differs in each stage. Optionally, the above-mentioned staged process can be implemented by the electronic device using a rolling search to collect data, thereby updating the startup time of the second operating system daily.

[0095] Optionally, during the process of updating the startup time of the second operating system within a preset period, the electronic device can delete similar startup times and replace the original startup time with a newly determined startup time, or it can add the newly determined startup time to the startup time of the second operating system within each day. This is not limited here.

[0096] For example, through step 303, the startup time of the second operating system set on the electronic device is: 7:30 AM, 9:30 AM, 12:30 PM, and 5:30 PM. During the second time period, if the user's usage habit for the second operating system is determined to be 6:00 AM based on the time record of the electronic device's alarm clock application, and the new startup time of the second operating system determined based on this usage habit is 6:30 AM, in addition to replacing the original 7:30 AM with 6:30 AM, a startup time of 6:30 AM can also be added before 7:30 AM. Optionally, during the third time period, if the user's usage habit for the second operating system is determined to be 8:00 AM based on the electronic device's daily first launch of the target application behavior record, and the new startup time of the second operating system determined based on this usage habit is 8:00 AM, in addition to replacing the original 7:30 AM with 8:00 AM, the update process can update startup times that are close to the newly determined startup time of the second operating system.

[0097] Step 304: If the second operating system is not started, start the second operating system if the startup time of the second operating system within the preset cycle is reached.

[0098] Optionally, the current time can be detected by using the startup time of the second operating system obtained from the user's usage habits of the second operating system in the above process. If the startup time of the second operating system within a preset period has been reached, the second operating system will be started; otherwise, the second operating system will not be started.

[0099] Optionally, when the second operating system is not running, for example, when the electronic device is in normal sleep mode, both the first and second operating systems are in normal sleep mode. When the user wakes the electronic device, the device will wake up the first operating system and check if the current time has reached the startup time of the second operating system within a preset cycle. If it has, the second operating system will then be woken up and started. That is, the user can control the first and second operating systems of the electronic device to enter sleep mode. When the first operating system switches from sleep mode to startup, if the startup time of the second operating system has arrived, the second operating system will be started, avoiding the problem of wasted power caused by starting both operating systems every time the device starts from sleep mode, even if the user does not use the second operating system.

[0100] Alternatively, when an electronic device restarts / powers on, both the first and second operating systems are in a closed state. During the restart process, after the electronic device wakes up the first operating system, it can detect whether the current time has reached the startup time of the second operating system within a preset cycle. If it has, the second operating system will be woken up and started.

[0101] It should be noted that the startup time of the second operating system mentioned above can be set as either a specific startup time or a delay relative to the wake-up time of the electronic device. For example, if the user's habits dictate that the second operating system needs to be started for the first time at 8:00 AM every day, then the startup time could be 8:00 AM. Alternatively, if the user's habits dictate that the electronic device is woken up by an alarm at 7:00 AM, and the user typically launches the target application at 8:00 AM, then the startup time could be 1 hour (relative to the wake-up time of 7:00 AM). In practical applications, if the user also habitually puts the electronic device into sleep mode at noon and wakes it up at 1:30 PM, and given the user's usual pattern of using the target application at 3:00 PM, then the electronic device could also be set to start the second operating system at 3:00 PM (or delayed by 1.5 hours) relative to the 1:30 PM wake-up time.

[0102] Optionally, in this solution, the first operating system can have a default startup time that coincides with the time the electronic device is woken up. Once the electronic device is woken up, the first operating system starts. Of course, if power saving is also desired for the first operating system, its startup time can be adjusted based on the user's usage habits. This requires monitoring the applications in the first operating system and determining the startup time based on the user's usage records / information. The process can be similar to determining the startup time of the second operating system, and will not be elaborated further here.

[0103] Optionally, after determining the boot time of the second operating system as described above, the second operating system is only launched when its boot time arrives. This ensures that the operation of the second operating system is closer to the user's usage habits and avoids launching the second operating system when the first operating system is already running, thus avoiding wasting power by having the second operating system running unnecessarily without the user using its applications. For example, every night a user can put their electronic device into sleep mode, at which point both operating systems enter sleep mode. The next day, when the electronic device exits sleep mode and wakes the first operating system, the second operating system is not woken up simultaneously. Instead, the system checks if the current time has reached the boot time of the second operating system; if so, the second operating system is launched.

[0104] Optionally, the electronic device is a wearable device. Before the startup time of the second operating system is reached, the electronic device may also perform the following operations: obtain the wearing status of the wearable device, including wearing and / or not wearing; if the wearing status of the wearable device is not wearing, and the wearing status of the wearable device switches to wearing, start the second operating system; if the wearing status of the wearable device is wearing, and the startup time of the second operating system is reached, start the second operating system. That is, in addition to starting the second operating system according to the startup time set above, the wearable device can also monitor in real time whether the wearable device is being worn by the user, obtain the wearing status of the wearable device, and if the currently obtained wearing status of the wearable device is not wearing, and a switch from not wearing to wearing is detected, then start the second operating system; if the currently obtained wearing status of the wearable device is wearing, then by combining the above-mentioned startup time determination, start the second operating system.

[0105] In other words, to better adapt to situations where users are wearing wearable devices, if the system detects that a user is not wearing the device, but the user is currently wearing or has finished wearing the device, it indicates that the wearable device's wearing state has switched to "wearing," and the user may need to use the wearable device, in which case the second operating system is launched. If the system detects that the user is already wearing the device, it can wait for the second operating system to launch before launching it. In other words, the electronic device can decide whether to launch the second operating system based on the wearable device's wearing state; when not wearing the device, only the first operating system can be launched, and when the system detects that a user is wearing the device, the second operating system can be launched.

[0106] Taking wearable devices as an example, users control their wearable devices to exit sleep mode daily. Using this solution, the first operating system can be launched after the wearable device exits sleep mode, and the second operating system will only be launched shortly before the user actually uses the target application. For instance, based on the usage information mentioned above, if it's determined that the user typically launches the target application half an hour after the alarm rings in the morning, then after the alarm rings, the wearable device will be woken up and the first operating system will launch. Based on the startup time of the second operating system determined by the usage information, it should be launched half an hour after waking up.

[0107] In one possible implementation, the electronic device is a wearable device. In the wearable device, the usage information obtained above can be sent to other terminal devices with stronger data processing capabilities, so that the terminal devices can perform the steps of obtaining the user's usage habits of the second operating system and determining the startup time of the second operating system within a preset period based on the usage habits. The wearable device only needs to receive the startup time of the second operating system within the preset period sent back by the terminal device, so as to facilitate the use of subsequent steps.

[0108] In some wearable devices, the device restarts every time it exits sleep mode, and by default, both operating systems are restarted. However, with this solution, after the first operating system starts, it can determine whether the current time has reached the startup time of the second operating system. If it has, then the second operating system starts.

[0109] In summary, in electronic devices with a first operating system and a second operating system, the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system. If the second operating system is not started, it will be started when its scheduled startup time is reached. The startup time of the second operating system is determined based on the user's usage habits. In this application, when the second operating system is not started, the actual startup time of the electronic device is controlled based on whether the current time has reached the startup time of the second operating system. This avoids the problem of wasted power consumption caused by starting the second operating system when the user is not using it, reduces the ineffective power consumption of the electronic device, and improves the battery life of the electronic device.

[0110] Below, we can describe how electronic devices can be set to different working modes. Users can flexibly control the switching of electronic devices between different working modes. In the first mode, if the electronic device is woken up, it can execute the process of starting the second operating system when the startup time of the second operating system is reached. If the electronic device is working in other modes, the first operating system and the second operating system can be run simultaneously, which improves the flexibility of operating system startup control.

[0111] Please refer to Figure 6 This document illustrates a flowchart of a method for starting an electronic device control system according to an exemplary embodiment of this application. This system startup method can be applied to electronic devices having a first operating system and a second operating system, where the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system. Figure 6 As shown, the system startup method may include the following steps:

[0112] Step 601: Display a first interface on the screen, the first interface containing a first startup control for the first mode.

[0113] In this mode, the first operating system is active while the second operating system is disabled. The user performs a series of actions to display a first interface on the electronic device's screen. By triggering a first startup control within this interface, the user controls the electronic device to enter the first mode. That is, the first operating system can be either active or in sleep mode.

[0114] Please refer to Figure 7 This illustrates a schematic diagram of a first interface displayed on an electronic device according to an exemplary embodiment of this application. Figure 7As shown, it includes a first startup control 701 and a second startup control 702. The first startup control 701 controls the electronic device to start in a first mode, and the second startup control controls the electronic device to start in a second mode. The second mode is the mode in which the second operating system of the electronic device is started. In this solution, the electronic device can only operate in one of the first and second modes; it cannot operate in both modes simultaneously.

[0115] It should be noted that this embodiment is based on an electronic device including a display screen. In practical applications, some electronic devices may not have a display screen, but can be controlled by setting physical controls to allow users to trigger them and thus control the electronic device to enter the corresponding working mode. This solution is not limited to this.

[0116] Step 602: In response to the triggering operation of the first startup control of the first mode, the first mode is started.

[0117] Optionally, in the first interface described above, the user can trigger an operation on the first launch control of the first mode to make the electronic device respond and thus enter the first mode. For example, the user can click on the first launch control to make the electronic device respond to the click operation and launch the corresponding first mode.

[0118] Optionally, the first interface shown above also includes a second startup control 702 for a second mode, which the user can also use. Figure 7 The second startup control 702 is triggered. If the user clicks to trigger the second startup control 702, the electronic device can respond to the triggering operation of the second startup control in the second mode and start the second operating system so that the electronic device can work in the second mode.

[0119] Optionally, since the first mode is a mode that runs the first operating system and shuts down the second operating system, the electronic device needs to shut down the second operating system in this mode. In this case, applications running on the second operating system certainly cannot run and need to be closed. For example, in response to the triggering operation of the first launch control in the first mode, the electronic device can start the first mode as follows: if the running time of the currently running target application exceeds a first preset time, the target application is automatically closed. The target application is an application running on the second operating system; after all currently running target applications in the electronic device are closed, the second operating system is shut down, and the device enters the first mode.

[0120] In other words, after responding to the trigger operation of the first startup control in the first mode, the electronic device can monitor each target application. To respond to user actions more quickly and enter the first mode, it can actively close target applications whose runtime exceeds a first preset time after the trigger operation, ultimately closing all target applications and then shutting down the second operating system to enter the first mode. Of course, for even faster operation, the electronic device can skip the above judgment and directly close all currently running target applications before shutting down the second operating system and entering the first mode.

[0121] In one possible implementation, before activating the first mode, the electronic device may also display an application closing prompt interface in response to a triggering operation of the first startup control of the first mode. The closing prompt interface displays various running target applications and a closing control. The target applications are applications running on a second operating system, and the closing control is used to control the closing of each running target application. In response to a triggering operation of the closing control, the selected target applications are closed.

[0122] Please refer to Figure 8 This illustration shows a schematic diagram of an application closing prompt interface displayed on an electronic device according to an exemplary embodiment of this application. Figure 8 As shown, it can be in Figure 7 Based on this, the electronic device enters the interface in response to the user's trigger operation of the first launch control in the first mode. Figure 8 This includes various running target applications 801, a selection control 802, a close control 803, and a cancel control 804. Users can select the target applications to be closed using the selection control 802 and trigger the close control 803 to close them. Alternatively, users can trigger the cancel control 804 to prevent the current target application from closing.

[0123] In this example, if the user closes all running target applications using the close control, the electronic device can shut down the second operating system and enter the first mode. If the user selects the cancel control 804, it means the user does not want the electronic device to directly enter the first mode; the electronic device can enter the first mode according to a preset time. This preset time can be 00:00 every day, that is, entering the first mode of this solution from the next day.

[0124] Step 603: In the first mode, if the startup time of the second operating system is reached, start the second operating system.

[0125] Optionally, if the electronic device reaches the startup time of the second operating system, the process for starting the second operating system can refer to the above. Figure 3 The method embodiments shown are not described in detail here.

[0126] Please refer to Figure 9 This illustration shows a schematic diagram of the startup process of an operating system for an electronic device according to an exemplary embodiment of this application. Figure 9 As shown, this includes a first mode stage 901, a wake-up stage one 902, and a wake-up stage two 903. In the first mode stage 901, both the small core and the large core are disabled. In this first mode, if the electronic device is woken up, it first enters the wake-up stage one 902, where only the small core is activated, and the large core remains disabled. As time progresses, it reaches the wake-up stage two 903, where the large core is then activated, allowing the first and second operating systems to be started at different times. Optionally, the electronic device can be woken up from a power-off state or from sleep mode.

[0127] In one possible implementation, since the boot time of the second operating system differs from that of the first operating system, this solution can also display a prompt message on the aforementioned screen when the second operating system boots up, indicating to the user that the second operating system is currently booting. Please refer to [reference needed]. Figure 10 This illustration shows a schematic diagram of a startup interface according to an exemplary embodiment of this application. Figure 10 As shown, it includes prompt message 1001. Prompt message 1001 indicates that the second operating system is starting up. Of course, the first operating system can also have a prompt message when it starts up, and the prompt message will be different from that of the second operating system. This solution does not limit this.

[0128] In summary, in electronic devices with a first operating system and a second operating system, the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system. If the second operating system is not started, it will be started when its scheduled startup time is reached. The startup time of the second operating system is determined based on the user's usage habits. In this application, when the second operating system is not started, the actual startup time of the electronic device is controlled based on whether the current time has reached the startup time of the second operating system. This avoids the problem of wasted power consumption caused by starting the second operating system when the user is not using it, reduces the ineffective power consumption of the electronic device, and improves the battery life of the electronic device.

[0129] In addition, this solution allows for flexible control of electronic devices to enter either the first or second mode through interface management, enabling the setting of conditions for starting the first and second operating systems at different times. This improves the adaptability of electronic devices to the startup control of the two operating systems and better suits the user's chosen working mode.

[0130] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0131] Please refer to Figure 11 This illustration shows a structural block diagram of a system startup device provided in an exemplary embodiment of this application. The system startup device 1100 can be used in an electronic device having a first operating system and a second operating system, wherein the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system, to execute all or part of the steps performed by the electronic device in the methods provided in the various embodiments shown above. The system startup device 1100 includes:

[0132] The system startup module 1101 is used to start the second operating system if the startup time of the second operating system is reached when the second operating system is not started. The startup time of the second operating system is determined according to the user's usage habits of the second operating system.

[0133] In summary, in electronic devices with a first operating system and a second operating system, the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system. If the second operating system is not started, it will be started when its scheduled startup time is reached. The startup time of the second operating system is determined based on the user's usage habits. In this application, when the second operating system is not started, the actual startup time of the electronic device is controlled based on whether the current time has reached the startup time of the second operating system. This avoids the problem of wasted power consumption caused by starting the second operating system when the user is not using it, reduces the ineffective power consumption of the electronic device, and improves the battery life of the electronic device.

[0134] Optionally, the device further includes:

[0135] The first acquisition module is used to acquire the startup time of the second operating system based on the user's usage habits of the second operating system.

[0136] Optionally, the first acquisition module includes: a first acquisition unit, a second acquisition unit, and a first determination unit;

[0137] The first acquisition unit is used to acquire usage information, which includes the user's usage records of the target application, and the target application is an application running on the second operating system;

[0138] The second acquisition unit is used to acquire the user's usage habits of the second operating system based on the usage information, wherein the usage habits include the times when the user actually starts the second operating system within a preset period;

[0139] The first determining unit is configured to determine the startup time of the second operating system within the preset period based on the usage habits, including the various times when the user actually starts the second operating system within the preset period.

[0140] Optionally, the device further includes:

[0141] The first determining module is used to determine the current usage stage of the electronic device;

[0142] The second acquisition module is used to acquire usage information corresponding to the current usage stage of the electronic device, wherein the usage information required for different usage stages is different;

[0143] The first update module is used to update the user's usage habits of the second operating system based on the usage information corresponding to the usage stage.

[0144] Optionally, the first update module is further configured to:

[0145] If the current usage phase of the electronic device is the first time phase, the acquired usage information includes the user's usage pattern of starting the second operating system;

[0146] If the current usage phase of the electronic device is the second time phase, the acquired usage information includes the time records of the alarm clock application of the electronic device.

[0147] If the current usage phase of the electronic device is the third time phase, the acquired usage information includes the user's behavior record of launching the target application for the first time each day;

[0148] If the current usage stage of the electronic device is the fourth time stage, the acquired usage information includes the behavior information of the electronic device launching the second operating system in the target usage scenario; wherein, the first time stage, the second time stage, the third time stage and the fourth time stage increase sequentially in time order.

[0149] Optionally, the device further includes:

[0150] The second determining module is used to determine the user's usage pattern level based on the usage information before obtaining the user's usage habits of the second operating system based on the usage information, wherein the higher the usage pattern level, the closer the time when the user starts the second operating system each time within each preset cycle;

[0151] The second acquisition unit is further configured to, if the regularity level is greater than the preset level, acquire the user's usage habits of the second operating system based on the usage information;

[0152] The first control module is used to control the second operating system to enter sleep mode when the startup time of the second operating system is reached, if the regularity level is not greater than the preset level.

[0153] Optionally, the device further includes:

[0154] The third determining module is used to determine the target shutdown time of the second operating system based on the user's usage habits of the second operating system if the regularity level is greater than the preset level.

[0155] The first shutdown module is used to shut down the second operating system when the target shutdown time is reached while the second operating system is running.

[0156] Optionally, the electronic device is a wearable device, and the device further includes:

[0157] The third acquisition module is used to acquire the wearing status of the wearable device before the startup time of the second operating system, the wearing status including wearing and / or not wearing;

[0158] The first startup module is used to start the second operating system when the wearable device is switched from being worn to being worn, provided that the wearable device is not being worn.

[0159] The second startup module is used to start the second operating system when the wearable device is in the wearing state and the startup time of the second operating system is reached.

[0160] Optionally, the device further includes:

[0161] The third startup module is used to start the first mode, which is a mode in which the first operating system is not shut down and the second operating system is shut down;

[0162] The system startup module is further configured to, in the first mode, start the second operating system if the startup time of the second operating system is reached.

[0163] Optionally, the electronic device also has a display screen, and the device further includes:

[0164] The first display module is used to display an application closing prompt interface in response to a triggering operation of the first launch control of the first mode before the first mode is launched. The closing prompt interface displays each running target application and a closing control. The target application is an application running on the second operating system, and the closing control is used to control the closing of each running target application.

[0165] The second closing module is used to close the selected target applications in response to the triggering operation of the close control.

[0166] Optionally, the device further includes:

[0167] The second control module is used to control the first operating system and the second operating system of the electronic device to enter sleep mode;

[0168] The fourth startup module is used to start the second operating system when the first operating system switches from sleep mode to startup, if the startup time of the second operating system has arrived.

[0169] Optionally, embodiments of this application also provide an electronic device, which includes a memory and a processor. The memory stores a computer program that can run on the processor. When the processor executes the computer program, it implements all or part of the steps performed by the electronic device in the system startup methods of the various embodiments described above.

[0170] Optionally, embodiments of this application also provide a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements all or part of the steps performed by an electronic device in the system startup methods of the various embodiments described above.

[0171] Optionally, embodiments of this application also provide a chip containing an executable computer program. When the chip executes the computer program, it implements all or part of the steps performed by the electronic device in the system startup methods of the various embodiments described above.

[0172] Optionally, embodiments of this application also provide a computer program product that, when run on a computer, causes the computer to execute all or part of the steps of the system startup methods described in the above embodiments, performed by an electronic device.

[0173] Optionally, embodiments of this application also provide an application publishing platform for publishing computer program products, wherein when the computer program product is run on a computer, the computer executes all or part of the steps of the system startup method described in the above embodiments, which are performed by an electronic device.

[0174] It should be noted that the device provided in the above embodiments is only illustrated by the division of the above functional modules when controlling electronic devices. In practical 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. In addition, the device and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0175] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0176] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

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

Claims

1. A system startup method, characterized in that, Applied to an electronic device, the electronic device including a first operating system and a second operating system, wherein the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system, the method includes: If the second operating system is not started, it will start when the second operating system's startup time is reached. The startup time of the second operating system is determined based on the user's usage habits of the second operating system.

2. The method according to claim 1, characterized in that, The method further includes: Based on the user's usage habits of the second operating system, obtain the boot time of the second operating system.

3. The method according to claim 2, characterized in that, The step of obtaining the boot time of the second operating system based on the user's usage habits of the second operating system includes: Obtain usage information, which includes the user's usage history of the target application, the target application being an application running on the second operating system; Based on the usage information, the user's usage habits of the second operating system are obtained, and the usage habits include the various times when the user actually starts the second operating system within a preset period; Based on the usage habits, including the actual times when the user starts the second operating system within a preset period, the startup time of the second operating system within the preset period is determined.

4. The method according to claim 3, characterized in that, The method further includes: Determine the current stage of use of the electronic device; Based on the current usage stage of the electronic device, usage information corresponding to the usage stage is obtained, wherein the usage information required for different usage stages is different; Based on the usage information corresponding to the usage stage, the startup time of the second operating system within the preset period is updated.

5. The method according to claim 4, characterized in that, The step of obtaining usage information corresponding to the current usage stage of the electronic device includes: If the current usage phase of the electronic device is the first time phase, the acquired usage information includes the user's usage records of the target application; If the current usage phase of the electronic device is the second time phase, the acquired usage information includes the time records of the alarm clock application of the electronic device. If the current usage phase of the electronic device is the third time phase, the acquired usage information includes the user's behavior record of launching the target application for the first time each day; If the current usage stage of the electronic device is the fourth time stage, the acquired usage information includes the behavior information of the electronic device launching the second operating system in the target usage scenario; wherein, the first time stage, the second time stage, the third time stage and the fourth time stage increase sequentially in time order.

6. The method according to claim 3, characterized in that, Before obtaining the user's usage habits of the second operating system based on the usage information, the method further includes: Based on the usage information, the user's usage pattern level is determined, wherein the higher the usage pattern level, the closer the time when the user starts the second operating system each time within each preset cycle; If the regularity level is greater than the preset level, the user's usage habits of the second operating system are obtained based on the usage information. If the regularity level is not greater than the preset level, the second operating system is controlled to enter sleep mode.

7. The method according to claim 6, characterized in that, The method further includes: If the regularity level is greater than the preset level, the target shutdown time of the second operating system is determined based on the user's usage habits of the second operating system; If the target shutdown time is reached while the second operating system is running, the second operating system will be shut down.

8. The method according to any one of claims 1 to 7, characterized in that, The electronic device is a wearable device, and before the startup time of the second operating system, it also includes: The wearing status of the wearable device is obtained, including wearing and / or not wearing; If the wearable device is not worn when it is not worn, and then switches to being worn, the second operating system is started. When the wearable device is in the wearing state, if the startup time of the second operating system is reached, the second operating system is started.

9. The method according to any one of claims 1 to 7, characterized in that, The method further includes: Start the first mode, where the first operating system is not shut down and the second operating system is shut down; In the first mode, if the startup time of the second operating system is reached, the second operating system is started.

10. The method according to claim 9, characterized in that, The electronic device also has a display screen, and the method further includes, prior to activating the first mode: In response to the triggering operation of the first launch control of the first mode, an application closing prompt interface is displayed. The closing prompt interface displays each running target application and a closing control. The target application is an application running on the second operating system, and the closing control is used to control the closing of each running target application. In response to a trigger action on the close control, the selected target applications are closed.

11. The method according to any one of claims 1 to 7, characterized in that, The method further includes: The first operating system and the second operating system of the electronic device are controlled to enter sleep mode; If the first operating system switches from sleep mode to startup, and the startup time of the second operating system is reached, the second operating system is started.

12. A system startup device, characterized in that, An application to an electronic device, the electronic device including a first operating system and a second operating system, wherein the power consumption of the electronic device running the first operating system is less than the power consumption of the electronic device running the second operating system, the device comprising: The system startup module is used to start the second operating system if the second operating system has not been started and the startup time of the second operating system has been reached. The startup time of the second operating system is determined according to the user's usage habits of the second operating system.

13. An electronic device, characterized in that, The electronic device includes a memory and a processor, the memory storing a computer program that can run on the processor, and the processor executing the computer program to implement the system startup method according to any one of claims 1 to 11.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the system startup method as described in any one of claims 1 to 11.

Images