Lock screen wallpaper display method, storage medium, electronic device and product

Abstract

The embodiment of the invention provides a lock screen wallpaper display method, a storage medium, an electronic device and a product, the method is applied to a terminal operating system, the method comprises the steps that a wallpaper management framework in the terminal operating system creates a lock screen wallpaper window, and lock screen wallpaper is displayed through the lock screen wallpaper window, the window of the lock screen wallpaper window and the desktop wallpaper window are located at different window levels. Through the embodiment of the invention, the problem that the lock screen wallpaper cannot be reused by other application programs due to high coupling between the lock screen wallpaper and the lock screen application due to the fact that the lock screen wallpaper window is the window of the lock screen application in the related technology is solved, and the effect of setting the flexibility of the lock screen wallpaper is further improved.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of electronics, and in particular, to a lock screen wallpaper display method, a storage medium, an electronic device and a product. BACKGROUND

[0002] In the related art, a terminal (e.g., a mobile phone) usually sets a dynamic wallpaper for a desktop, and controls a lock screen window to be transparent to achieve the effect of a lock screen dynamic wallpaper. This method cannot achieve independent setting of dynamic wallpapers for the lock screen and the desktop, because the design of the framework bottom layer of the operating system of the terminal does not support independent lock screen dynamic wallpaper. In the related art, the lock screen wallpaper can only be used by the lock screen application, and cannot be used by other third-party applications, which reduces the playability and developability of the lock screen wallpaper, and the coupling between the lock screen application and the lock screen wallpaper display is too high, which also makes the management of the lock screen wallpaper by the system not flexible enough. SUMMARY

[0003] Embodiments of the present application provide a lock screen wallpaper display method, a storage medium, an electronic device and a product to at least solve the problem that the coupling between the lock screen wallpaper and the lock screen application is too high in the related art because the lock screen wallpaper window is the window of the lock screen application, and the lock screen wallpaper cannot be reused by other applications.

[0004] According to an embodiment of the present application, a lock screen wallpaper display method is provided, including: a wallpaper management framework in a terminal operating system creating a lock screen wallpaper window, and displaying a lock screen wallpaper through the lock screen wallpaper window, wherein the lock screen wallpaper window and a desktop wallpaper window are in different window levels.

[0005] According to another embodiment of the present application, a computer program product is also provided, including a computer program, wherein the computer program is executed by a processor to implement the steps in the above method embodiments.

[0006] According to another embodiment of the present application, a computer readable storage medium is also provided, which stores a computer program, wherein the computer program is set to run to execute the steps in the above method embodiments.

[0007] According to another embodiment of the present application, an electronic device is also provided, including a memory and a processor, the memory stores a computer program, and the processor is set to run the computer program to execute the steps in the above method embodiments.

[0008] According to the embodiments of the present application, since the lock screen wallpaper window used for displaying the lock screen wallpaper is created by the wallpaper management framework in the terminal operating system instead of the lock screen application, the coupling between the lock screen application and the lock screen wallpaper is eliminated, and the lock screen wallpaper window and the desktop wallpaper window are in different window levels, so that the desktop wallpaper and the lock screen wallpaper can be normally displayed. Therefore, the problem that the coupling between the lock screen wallpaper and the lock screen application is too high due to the fact that the lock screen wallpaper window is the window of the lock screen application and cannot be reused by other application programs in the related art can be solved, and the flexibility of setting the lock screen wallpaper is improved. BRIEF DESCRIPTION OF DRAWINGS

[0009] Figure 1 is a structural block diagram of a lock screen wallpaper display system according to an embodiment of the present application;

[0010] Figure 2 is a flowchart of a lock screen wallpaper display method according to an embodiment of the present application;

[0011] Figure 3 is a flowchart of a lock screen wallpaper display method according to another embodiment of the present application;

[0012] Figure 4 is a flowchart of a lock screen wallpaper display method in the related art. DETAILED DESCRIPTION

[0013] Hereinafter, the embodiments of the present application will be described in detail with reference to the accompanying drawings and in conjunction with the embodiments.

[0014] It should be noted that the terms “first”, “second” and the like in the specification and claims of the present application and the above-described drawings are used to distinguish similar objects, and do not necessarily have to be used to describe a specific order or sequence.

[0015] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device using an open source code operating system (for example, an Android operating system), Figure 1 is a structural block diagram of a lock screen wallpaper display system according to an embodiment of the present application. Figure 1 The system framework layer in is located above the Linux kernel layer, and is mainly responsible for providing various system services and application development interfaces, such as Figure 1 As shown in, the system framework layer (for example, the Android operating system framework layer) includes a display framework and a wallpaper management framework, the system application layer (for example, the Android operating system application layer) includes a desktop application / other application, and a lock screen application / other application, and the hardware device includes a smart device screen.

[0016] The display framework (such as the Android display framework) is a core component in the system responsible for managing and rendering the user interface (UI). The functions of the display framework include at least:

[0017] (1) Interface rendering: The display framework is responsible for rendering the application's user interface onto the screen, including text, images, graphics and other UI elements. It performs 2D and 3D graphics rendering through the graphics API. The native lock screen wallpaper is displayed on the screen by obtaining the lock screen image saved by the system and rendering it onto the screen through 2D graphics.

[0018] (2) Window Management: Responsible for managing all application windows. Each application's UI is rendered in its own window. These windows are combined together, and their display order and hierarchy on the screen are determined. The principle of wallpaper display is to combine the wallpaper window with the window of the application itself that is designated to display the wallpaper (either semi-transparent or transparent) to form the final wallpaper display effect we see.

[0019] (3) Composition and layering: The display framework combines UI elements from multiple applications onto a single screen, creating the final display effect by compositing images from multiple layers, which may include the UI layer of the application, the system interface layer, and layers from other applications.

[0020] In other words, the display framework is a key component that ensures the correct, efficient, and smooth display of the user interface. It provides the operating system with a unified display management mechanism and guarantees the compatibility and performance of various applications on different hardware.

[0021] A wallpaper management framework (such as the Android wallpaper management framework) is a set of systems and APIs for managing, displaying, and setting mobile phone wallpapers. A wallpaper management framework should include at least the following functionalities:

[0022] (1) Wallpaper Management: The wallpaper management framework provides an interface for managing wallpapers, allowing users to browse, select and change wallpapers on their phones.

[0023] (2) Live wallpaper support: The wallpaper management framework supports live wallpapers, which are a special type of wallpaper that can display dynamic content, such as animations and real-time data.

[0024] (3) Integration of third-party wallpaper applications: The wallpaper management framework also supports the integration of third-party wallpaper applications. For example, some third-party wallpaper libraries or applications (such as PicSpeed) allow users to download and set full-screen wallpapers.

[0025] In other words, the wallpaper management framework provides a complete set of features that allow developers to easily create and integrate various types of wallpapers for users.

[0026] Desktop applications (such as Android launchers) are a crucial component of the terminal operating system, encompassing at least the following functionalities:

[0027] (1) User interface: It provides users with a personalized user interface through which users can manage, organize and use the application.

[0028] (2) Application launch: Users can quickly launch applications by clicking the application icon on the desktop.

[0029] (3) Desktop management: Users can add, delete or move application shortcuts and desktop widgets on the desktop.

[0030] (4) Themes and Customizations: Users can usually customize the style of desktop applications, including themes, icons, fonts and layouts, to suit their personal preferences, including displaying desktop wallpapers.

[0031] (5) Multitasking: Some desktop applications support displaying a list of recently used applications, making it easy for users to quickly switch back to previous tasks.

[0032] In other words, the desktop Launcher plays the role of organizer and manager in the Android system, providing a platform for users to interact with Android devices, greatly improving the convenience and personalized experience of users using smart devices.

[0033] Other applications can also make a portion of their interface transparent and achieve the effect of displaying the desktop wallpaper by setting a flag (a window marker used to display the desktop wallpaper window).

[0034] Lock screen apps (such as Android lock screen apps) are part of the system user interface and include at least the following functionalities:

[0035] (1) Security Protection: The lock screen app provides the first layer of security protection for the device, preventing unauthorized users from accessing the device. Users need to unlock the screen to access the device's main interface.

[0036] (2) Display Information: Lock screen apps can display basic information such as time, date, battery level, and signal strength. In addition, they can also display notifications such as missed calls, text messages, and emails.

[0037] (3) Personalization settings: Users can personalize the lock screen interface, such as changing the lock screen wallpaper and setting the unlocking method (such as PIN code, pattern, password or biometric technology).

[0038] In other words, the main functions of lock screen applications are to protect device security, provide basic information display, and offer users convenient operation and personalized experience while the screen is locked.

[0039] Other applications: Other applications can also make a certain part of their interface transparent and achieve the effect of displaying the lock screen wallpaper by setting a flag (a window marker used to display the lock screen wallpaper window).

[0040] Smart device screen: Primarily used to display content from smart devices and interact with users.

[0041] This embodiment provides a method for displaying lock screen wallpapers. Figure 2 This is a flowchart of a lock screen wallpaper display method according to an embodiment of this application, such as... Figure 2 As shown, the process includes the following steps:

[0042] In step S202, the wallpaper management framework in the terminal operating system creates a lock screen wallpaper window and displays the lock screen wallpaper through the lock screen wallpaper window. The lock screen wallpaper window and the desktop wallpaper window are in different window layers.

[0043] In one embodiment, the terminal operating system includes the Android system, which is primarily used in terminal devices such as smartphones and tablets. Based on the Linux kernel, Android is open-source and customizable, boasting a rich application ecosystem. Users can download various applications and games from Android app stores, and customize the device's interface and functionality according to their needs and preferences.

[0044] It's important to note that the desktop wallpaper is the background displayed on the home screen after unlocking the device. Users can choose from a variety of images to use as their desktop wallpaper, such as landscapes, animals, anime characters, family photos, etc. Some systems also offer live wallpapers, such as animations, videos, or real-time weather.

[0045] A lock screen wallpaper is the background a user sees when their phone is locked. Similar to a desktop wallpaper, users can choose their favorite image as their lock screen wallpaper. The lock screen wallpaper and desktop wallpaper can be the same image, or they can be different images to meet the user's visual needs in different states.

[0046] In an exemplary embodiment of this application, after the wallpaper management framework creates the lock screen wallpaper window, it further includes: adjusting the hierarchical order of the vertical height of windows in the terminal operating system, and adjusting the window hierarchy of the lock screen wallpaper window to be higher than the window hierarchy of the desktop wallpaper window.

[0047] In one embodiment, the vertical height of the windows is adjusted by adjusting the Z-axis of the windows in the terminal operating system, thus adjusting the vertical height of the windows. Adjusting the window hierarchy of the lock screen wallpaper ensures that the lock screen interface can correctly cover other content when needed, providing a secure, efficient, and user-friendly unlocking experience.

[0048] In one embodiment, the window level of the lock screen wallpaper window is adjusted to be one level higher than the window level of the desktop wallpaper window. This way, if the desktop wallpaper window and the lock screen wallpaper window are displayed at the same time, the lock screen wallpaper window will be displayed first.

[0049] In an exemplary embodiment of this application, before the wallpaper management framework creates the lock screen wallpaper window, the method further includes: the wallpaper management framework loading lock screen wallpaper information from persistent wallpaper storage; binding a lock screen dynamic wallpaper service if the lock screen wallpaper information includes dynamic lock screen wallpaper information; or binding a lock screen static wallpaper service if the lock screen wallpaper information includes static lock screen wallpaper information; and initializing the lock screen wallpaper engine.

[0050] It should be noted that the native lock screen wallpaper display retrieves the lock screen image saved by the wallpaper management framework from the lock screen application window and renders it. It is highly coupled with the wallpaper management framework, but the display of the lock screen wallpaper is not managed by the wallpaper management framework, which creates a sense of disconnect and is not conducive to the secondary development of the lock screen wallpaper.

[0051] This application's embodiment modifies the original architecture, so that the lock screen wallpaper display process is also managed and triggered by the wallpaper management framework, similar to the desktop wallpaper display process. This modification decouples the lock screen application from the wallpaper display framework, eliminating the need for the application to focus on the setting, display, and updating of the lock screen wallpaper. The wallpaper management framework handles all processes uniformly, and the application also enables the separate setting of dynamic lock screen wallpapers. This functionality is not supported by native terminal operating systems (such as Android) due to underlying architecture limitations. This application's embodiment fully supports the separate setting of dynamic lock screen wallpapers.

[0052] In one embodiment, information about the lock screen and desktop wallpapers is loaded into memory from the persistent wallpaper storage maintained by the wallpaper management framework, including wallpaper location, whether it is a live wallpaper, user identity (ID), wallpaper color, name, etc.

[0053] In an exemplary embodiment of this application, the wallpaper management framework controls the desktop wallpaper window and the lock screen wallpaper window when the window in the terminal operating system changes.

[0054] It should be noted that in related technologies, the wallpaper management framework cannot control the lock screen wallpaper window, which is not conducive to the management and secondary development of lock screen wallpapers.

[0055] In an exemplary embodiment of this application, the wallpaper management framework manages the desktop wallpaper window and the lock screen wallpaper window, including: determining whether a window currently existing in the lock screen application or terminal operating system is visible, and whether the window includes a window flag for displaying the lock screen wallpaper window; if both determinations are yes, updating the state of the lock screen wallpaper window to visible and updating the state of the desktop wallpaper window to invisible; or, if it is determined that a window currently existing in the lock screen application or terminal operating system is invisible, or the window does not include a window flag for displaying the lock screen wallpaper window, updating the state of the lock screen wallpaper window to invisible.

[0056] In an exemplary embodiment of this application, when it is determined that a window currently existing in the lock screen application or terminal operating system is invisible, or the window does not include a window flag for displaying the lock screen wallpaper window, the method further includes: determining whether a window in the desktop application or terminal operating system is visible, and whether the window includes a window flag for displaying the desktop wallpaper window; if both determinations are yes, updating the state of the desktop wallpaper window to visible; or, if it is determined that a window in the desktop application or terminal operating system is invisible, or the window does not include a window flag for displaying the desktop wallpaper window, updating the state of the desktop wallpaper window to invisible.

[0057] In one embodiment, updating the visibility state of the current window can be used for subsequent window overlay and composite display, so that the wallpaper is either displayed or not displayed on the screen of the smart device, and the wallpaper is either a lock screen wallpaper or a desktop wallpaper.

[0058] In an exemplary embodiment of this application, when the lock screen wallpaper window or desktop wallpaper window is visible, the method further includes sending a notification to the window management framework that the visibility of the current window has been updated.

[0059] In one embodiment, sending a notification to the window management framework that the visibility of the current window has been updated indicates that the window management framework has been notified that the visibility of the current window has been updated.

[0060] This application's embodiments alter the display architecture of the system lock screen wallpaper and desktop wallpaper. The lock screen wallpaper window is no longer a window of the lock screen application, but a window independently managed by the system framework. Similar to the desktop wallpaper window, its window level is one level higher. It supports independent settings for lock screen live wallpapers and desktop live wallpapers, improving the user experience. Lock screen wallpapers and desktop wallpapers are uniformly managed by the system wallpaper management framework, breaking the coupling with the lock screen application. This allows lock screen wallpapers to be reused by third-party applications, just like desktop wallpapers, increasing the system's flexibility.

[0061] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0062] To facilitate understanding of the technical solutions provided in this application, detailed descriptions will be provided below with reference to specific scenario embodiments.

[0063] Figure 3 This is a flowchart of a lock screen wallpaper display method according to another embodiment of this application, such as... Figure 3 As shown, the process includes the following steps:

[0064] Step S301: Wallpaper Management Framework, indicating that the following steps are performed within the wallpaper management framework.

[0065] Step S302: Load wallpaper information from persistent wallpaper storage. This step loads information about the lock screen and desktop wallpapers into memory from the persistent wallpaper storage location maintained by the wallpaper management framework. This includes the wallpaper location, whether it is a live wallpaper, user ID, wallpaper color, name, etc., in preparation for the subsequent wallpaper operation process.

[0066] Step S303a: Desktop Wallpaper, indicating that the next step is to process the display of the desktop wallpaper.

[0067] In this embodiment, the desktop wallpaper display process has two trigger sources: First, the smart device actively changes the wallpaper. When the smart device changes the wallpaper, the wallpaper service bound to the wallpaper management framework is determined by the wallpaper service name passed to the application layer's wallpaper management framework interface, and this wallpaper information is saved in persistent information for binding the wallpaper service the next time the device restarts. Second, when the smart device restarts / powers on, the wallpaper name to be bound is determined by the latest wallpaper information saved by the system before the last shutdown. If the system has never changed the wallpaper (first power-on), then the system's default configured wallpaper service is read for binding.

[0068] C301a: Determines whether the desktop wallpaper is a live wallpaper.

[0069] Specifically, if the judgment result is yes, proceed to S304a; if the judgment result is no, proceed to S305a.

[0070] It's important to note that desktop wallpapers in terminal operating systems (such as Android) are divided into dynamic wallpapers and static wallpapers. Static wallpaper services are provided by the Android system. When a user needs to change a static wallpaper, they are actually changing the image information read from the static wallpaper service. When an application replaces a static wallpaper, it passes the image data stream to the wallpaper management framework's interface. The image display logic is entirely controlled by the Android system. Dynamic wallpaper services, on the other hand, are implemented by third-party applications that inherit from the wallpaper service abstract class provided by the wallpaper management framework. The service name is not fixed; for example, a specific wallpaper service abstract class depends entirely on the wallpaper application developer. When a user needs to change a dynamic wallpaper, they are actually binding to a specific dynamic wallpaper service. When an application replaces a dynamic wallpaper, it passes the dynamic wallpaper service name to the wallpaper management framework's interface. The specific content displayed by the dynamic wallpaper is controlled by the third-party application developer.

[0071] Step S304a: Bind the desktop live wallpaper service. This means that the desktop live wallpaper service will be bound next. After the binding is completed, the wallpaper service name will be saved in the persistent information for binding the wallpaper service the next time the device is restarted.

[0072] Step S305a: Bind the desktop static wallpaper service. This means that the desktop static wallpaper service will be bound next. If the desktop wallpaper triggering method is changed, the wallpaper image resource will be replaced first, and the static wallpaper service will be bound only after the replacement is completed.

[0073] Step S306a: Desktop wallpaper engine initialization. This means that the initialization of the desktop wallpaper engine will be processed next. The desktop wallpaper engine is an inner class of the wallpaper service abstract class. That is to say, whether it is a dynamic wallpaper or a static wallpaper, the wallpaper engine initialization work must be performed. The key is the creation of the wallpaper window, and the focus is on passing in a window of type desktop wallpaper.

[0074] Step S303b: Lock screen wallpaper, indicating the next step is to process the setting of the lock screen wallpaper.

[0075] Specifically, the lock screen wallpaper display process differs from the native Android lock screen wallpaper display architecture. The native lock screen wallpaper display retrieves the lock screen image saved by the wallpaper management framework from the lock screen application window and renders it. This is highly coupled with the wallpaper management framework, but the actual display of the lock screen wallpaper is not managed by the framework, creating a disconnect and hindering secondary development. This embodiment modifies the native architecture so that the lock screen wallpaper display process is also managed and triggered by the wallpaper management framework, similar to the desktop wallpaper display process.

[0076] The advantage of managing lock screen wallpapers with a wallpaper management framework is that it decouples the lock screen application from the wallpaper display framework, so that the application does not need to pay attention to the process of setting, displaying and updating lock screen wallpapers. The wallpaper management framework can manage them all. It can also realize the function of setting lock screen live wallpapers separately. This function is not supported on the native Android system because the underlying architecture does not support it. However, the embodiment of this application fully supports setting lock screen live wallpapers separately.

[0077] The display process of the lock screen wallpaper here also has two trigger sources, the same as S303a.

[0078] C301b determination: Determines whether the lock screen wallpaper is a live wallpaper.

[0079] Specifically, if the judgment result is yes, proceed to S304b; if the judgment result is no, proceed to S305b.

[0080] It should be noted that the modified lock screen wallpapers are also divided into dynamic wallpapers and static wallpapers. The static wallpaper service follows the desktop static wallpaper service, inheriting from the wallpaper service abstract class; while the dynamic wallpaper service also follows the desktop dynamic wallpaper service approach, inheriting from the wallpaper service abstract class and being custom-implemented by other third-party applications. The difference lies in the subsequent wallpaper engine, where the creation of the lock screen wallpaper window uses a lock screen wallpaper type window, newly added in this embodiment, to identify the currently created window as a lock screen wallpaper window.

[0081] Step S304b: Bind the lock screen live wallpaper service. This means that the lock screen live wallpaper service will be bound next. After the binding is completed, the name of the lock screen wallpaper service will be saved in the persistent information for binding the lock screen wallpaper service the next time the device is restarted.

[0082] Step S305b: Bind the lock screen static wallpaper service. This indicates that the binding process for the lock screen static wallpaper service will begin. If the lock screen wallpaper trigger method is changed, the lock screen wallpaper image resource will be replaced first, and the binding process for the lock screen wallpaper service will only begin after the replacement is complete.

[0083] Step S306b: Lock screen wallpaper engine initialization. This means that the initialization work of the lock screen wallpaper engine will be processed next. The lock screen wallpaper engine is an inner class of the wallpaper service abstract class. That is to say, whether it is a lock screen dynamic wallpaper or a static wallpaper, the wallpaper engine initialization work must be performed. The key is the creation of the wallpaper window, and the focus is on the window type being passed in as a lock screen wallpaper type window.

[0084] Step S307: Window management frame, indicating that the following steps are performed within the window management frame.

[0085] Step S308a: Add a desktop wallpaper type window. The window type is a desktop wallpaper type window, which is the window type provided by the native Android system.

[0086] Step S308b: Add a lock screen wallpaper type window, the window type is lock screen wallpaper type window.

[0087] Step S309: Adjust the Z-axis layer order of windows in the system. This means adjusting the Z-axis order of the lock screen wallpaper window and the desktop wallpaper window for subsequent window overlay and composite display. The layer of the lock screen wallpaper window is only one level higher than that of the desktop wallpaper window. In this way, if the desktop wallpaper window and the lock screen wallpaper window are displayed at the same time, the lock screen wallpaper window will be displayed first.

[0088] Step S310: Whenever a window change in the system triggers a layout, it means that when a window in the Android system changes, such as when an application window is opened, the window size and transparency change, or the visibility changes, the visibility of the subsequent desktop wallpaper window and lock screen wallpaper window needs to be adjusted.

[0089] C302 Determination: Determine whether the lock screen application or these windows currently existing in the system are visible and hold the window marker used to display the lock screen wallpaper window.

[0090] Specifically, if a window (which could be a lock screen application window) exists in the current system, and if it is visible and holds a flag (the flag for displaying the lock screen wallpaper window), then step S311 will be executed; otherwise, step S312 will be executed.

[0091] Step S311: Update the lock screen wallpaper window to be visible, and update the desktop wallpaper window to be invisible.

[0092] Specifically, the Android window management system is notified to update the visibility of the lock screen wallpaper window and the desktop wallpaper window. Since the C302 judgment determines that the currently existing window (which can be the lock screen application window) is visible and holds the flag (show lock screen wallpaper window flag), the lock screen wallpaper window is displayed first, and the desktop wallpaper window does not need to be displayed. Then proceed to step S315.

[0093] Step S312: Update the lock screen wallpaper window to be invisible.

[0094] Specifically, since the C302 judgment determines that the current system window (which may be a lock screen application window) is not visible or does not hold a flag (signal to display lock screen wallpaper window), it is not necessary to display the lock screen wallpaper window at this time.

[0095] C303 Determination: Determines whether a desktop application or a currently existing window is visible and holds a window marker for displaying the desktop wallpaper window.

[0096] Specifically, it means that if the window currently existing in the system is visible and holds the flag (display desktop wallpaper window flag), then step S314 will be processed; otherwise, step S313 will be processed.

[0097] Step S313: Update the desktop wallpaper window to be invisible.

[0098] Specifically, this indicates that the desktop wallpaper window is not intended to be displayed.

[0099] Step S314: Update the desktop wallpaper window to be visible.

[0100] Specifically, this indicates that the desktop wallpaper window is ready to be displayed, and proceeds to step S315.

[0101] Step S315: When visible, perform drawing and composite display.

[0102] Specifically, this indicates that the notification window management framework has updated the visibility of the current window and is performing window overlay and composite display. Ultimately, this will result in the lock screen wallpaper or desktop wallpaper being displayed or not displayed on the smart device's screen.

[0103] Figure 4 This is a flowchart of a lock screen wallpaper display method in related technologies, such as... Figure 4 As shown, the desktop wallpaper display process is similar to... Figure 3 The display methods for desktop wallpapers are basically the same, the difference lies in the display process of lock screen wallpapers. After obtaining the lock screen wallpaper image, the lock screen wallpaper image is displayed through the Systemui window.

[0104] In related technologies, lock screen live wallpaper solutions either cannot be set independently from desktop live wallpapers, or are implemented separately by the lock screen application, creating a disconnect between the system wallpaper management framework and the lock screen wallpaper display. Third-party applications are also unable to use the highly customized live wallpaper display of their lock screen applications, making the lock screen wallpaper function closed, unfriendly to third-party developers, and also losing the product's customizability.

[0105] In this embodiment, by changing the display architecture of the system's lock screen and desktop wallpaper, the lock screen wallpaper window and desktop wallpaper window are maintained simultaneously at the system framework layer. This allows the lock screen wallpaper and desktop wallpaper to be independent of each other and not affect each other, fully supporting the independent setting and display of lock screen and desktop live wallpapers.

[0106] This application optimizes the coupling between lock screen applications and lock screen wallpapers. Wallpapers are uniformly managed by the wallpaper management service at the system framework layer, including lock screen wallpapers and desktop wallpapers. Thus, like third-party applications, when a lock screen application needs to display a lock screen wallpaper, it only needs to set a window flag (a window marker for displaying the lock screen wallpaper window). The system framework will then automatically update and determine whether to display the lock screen wallpaper or the desktop wallpaper in the appropriate scenario.

[0107] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.

[0108] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0109] Embodiments of this application also provide an electronic device including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0110] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0111] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0112] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this application should be included within the protection scope of this application.

Claims

1. A lock screen wallpaper display method, characterized by, The application is applied to a terminal operating system, and comprises the following steps: A wallpaper management framework in the terminal operating system creates a lock screen wallpaper window, and displays a lock screen wallpaper through the lock screen wallpaper window, wherein the lock screen wallpaper window and a desktop wallpaper window are in different window levels.

2. The method of claim 1, wherein, After the wallpaper management framework creates the lock screen wallpaper window, the method further comprises the following steps:

3. The method of claim 1, wherein, The method further comprises the following steps: In the case that a window in the terminal operating system changes, the wallpaper management framework controls the desktop wallpaper window and the lock screen wallpaper window.

4. The method of claim 3, wherein, The wallpaper management framework controls the desktop wallpaper window and the lock screen wallpaper window, which comprises the following steps: determining whether the lock screen application or a currently existing window in the terminal operating system is in a visible state and whether the window comprises a window mark for displaying the lock screen wallpaper window; in the case that the determination results are both yes, updating the state of the lock screen wallpaper window to visible and updating the desktop wallpaper window to invisible; or in the case that the lock screen application or the currently existing window in the terminal operating system is in an invisible state or the window does not comprise the window mark for displaying the lock screen wallpaper window, updating the state of the lock screen wallpaper window to invisible.

5. The method of claim 4, wherein, In the case that the lock screen application or the currently existing window in the terminal operating system is in an invisible state or the window does not comprise the window mark for displaying the lock screen wallpaper window, the method further comprises the following steps: determining whether a window in the desktop application or the terminal operating system is in a visible state and whether the window comprises a window mark for displaying the desktop wallpaper window; in the case that the determination results are both yes, updating the state of the desktop wallpaper window to visible; or in the case that the window in the desktop application or the terminal operating system is in an invisible state or the window does not comprise the window mark for displaying the desktop wallpaper window, updating the state of the desktop wallpaper window to invisible.

6. The method of claim 5, wherein, In the case that the state of the lock screen wallpaper window or the desktop wallpaper window is visible, the method further comprises the following step: sending a notification of the visibility of the current window to a window management framework.

7. The method of claim 1, wherein, Before the wallpaper management framework creates the lock screen wallpaper window, the method further comprises the following steps: The wallpaper management framework loads lock screen wallpaper information from a wallpaper persistent storage; in the case that the lock screen wallpaper information comprises dynamic lock screen wallpaper information, binding a lock screen dynamic wallpaper service; or in the case that the lock screen wallpaper information comprises static lock screen wallpaper information, binding a lock screen static wallpaper service; performing lock screen wallpaper engine initialization.

8. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, wherein the computer program is executed by a processor to implement the steps of the method in any one of claims 1 to 7.

9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, The processor executes the computer program to implement the steps of the method in any one of claims 1 to 7.

10. A computer program product comprising a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the method in any one of claims 1 to 7.

Images