Detailed Description
The technical solutions in the embodiments of the present disclosure will be described below with reference to the drawings in the embodiments of the present disclosure. In the description of the present disclosure, unless otherwise indicated, "/" means that the related objects are in a "or" relationship, for example, a/B may mean a or B, and "and/or" in the present disclosure is merely an association relationship describing the related objects, for example, a and/or B may mean that there may be three relationships, for example, a and/or B, three cases where a exists alone, a and B exist together, and B exists alone, where a and B may be singular or plural. Also, in the description of the present disclosure, unless otherwise indicated, "a plurality" means two or more than two. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (a, b, or c) of a, b, c, a-b, a-c, b-c, or a-b-c may be represented, wherein a, b, c may be single or plural. In addition, in order to clearly describe the technical solutions of the embodiments of the present disclosure, in the embodiments of the present disclosure, the words "first", "second", and the like are used to distinguish the same item or similar items having substantially the same function and effect. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ. Meanwhile, in the embodiments of the present disclosure, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "e.g." in the examples of this disclosure should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion that may be readily understood.
In addition, the network architecture and the service scenario described in the embodiments of the present disclosure are for more clearly describing the technical solution of the embodiments of the present disclosure, and do not constitute a limitation on the technical solution provided by the embodiments of the present disclosure, and as a person of ordinary skill in the art can know, with evolution of the network architecture and appearance of a new service scenario, the technical solution provided by the embodiments of the present disclosure is equally applicable to similar technical problems.
For clarity and conciseness in the description of the embodiments below, a brief introduction to related concepts or technologies is first given:
1. The system theme (theme for short) refers to an interface style of the electronic device system, for example, a style of an interface such as a display interface and a notification management interface of the electronic device. The system theme may include preview, wallpaper, icon file, etc.
The preview image refers to a preview effect image of the electronic device after using the system theme. Wallpaper refers to a main interface picture (also called desktop wallpaper) of an electronic device, a screen locking picture (also called screen locking wallpaper) and the like. An icon file refers to a file that can be considered an icon, such as a desktop icon, a folder icon, and the like.
The system theme is usually preconfigured when the electronic equipment leaves the factory, and the user can also change the preconfigured system theme of the electronic equipment according to own hobbies when using the electronic equipment, so that the display interface of the electronic equipment is changed into the favorite style of the user. When the electronic device applies different themes, the style of interface presented by the electronic device is also different.
2. The magazine lock screen is used for providing a plurality of different images for systemUI applications of the electronic device. Each time the screen of the electronic device is lit, systemUI applications can control the lock screen interface of the display screen to display different images. The magazine lock screen is an application or service, and belongs to Android Application Package (APK) files in an Android system. In the present disclosure, the images provided by the magazine lock screen may be magazines, news, or other forms, etc., derived from any one or more of a locally preset resource, cloud resource, or manually added resource by a user, etc.
Because the user can repeatedly appear turning off the screen and turning on the screen in the process of using the electronic device, if the magazine lock screen wants to ensure that different images can be displayed in the lock screen interface every time when the magazine lock screen is turned on, the magazine lock screen can pre-load resources, so that systemUI application of the electronic device can acquire the resources from the magazine lock screen and display different images in the lock screen interface, thereby bringing freshness to the user.
3. The screen locking wallpaper refers to an image contained in a screen locking interface displayed by the electronic equipment when the electronic equipment is in a screen locking state and is on. The screen-locking wallpaper can be an image, a moving picture or a short video, etc. The screen locking wallpaper can be a wallpaper provided by a system theme, a fixed screen locking wallpaper customized by a user, or a plurality of different screen locking images provided by a magazine screen locking. The main function of the screen locking wallpaper is to provide visual attraction and personalized display.
4. The desktop wallpaper refers to a background image contained in a main interface (namely a system desktop) displayed by the electronic equipment after the electronic equipment is unlocked, and the desktop wallpaper can be an image, a moving picture or a short video. The desktop wallpaper can be wallpaper provided by a system theme, and also can be fixed desktop wallpaper customized by a user. Desktop wallpaper creates a comfortable and personalized visual environment for users in the daily use process of operating equipment, opening application programs and the like.
5. SystemUI application, which is an important application in the android operating system, is mainly responsible for managing and presenting user interaction elements at the system level. SystemUI applications cover a number of key parts including status bars, navigation bars, notification bars, lock screen interfaces, desktop interfaces, and the like.
Wherein the status bar is used to display system status information such as signal strength, battery level, time, etc. The navigation bar is used for displaying common operation buttons such as return, homepage and multitasking. The notification bar is used for displaying notification messages from various applications, and a user can view the detailed content and perform corresponding operations by pulling down the notification bar. The lock screen interface is used for displaying time, date and other information, and can also comprise shortcut operation buttons, such as a camera, a flashlight and the like. SystemUI applications can provide a smooth, convenient user experience.
For example, when the mobile phone receives a new short message, systemUI application can display a corresponding icon and prompt information on the notification bar, and when the user slides the screen to unlock, systemUI application can process the unlocking operation and switch to the desktop interface.
With the continuous iteration of the mobile operation system, various new business layers are endless, and richer functional experience is provided for users. SystemUI the application, as an application that interacts directly with the user, also increases in complexity and memory usage.
This phenomenon is more pronounced during practical use, especially in devices with relatively low-end configurations or smaller memory capacities. For low-end machines or devices with less memory, there is a limitation on the hardware performance itself. Under the condition that SystemUI application memories are gradually increased, the limited memory capacity can cause problems of clamping, slow running, even application breakdown and the like of the system more easily, and the normal use and operation experience of a user are seriously affected.
For example, when some low-end mobile phones run the latest version of the system, the speed of opening the application is obviously slowed down due to excessive SystemUI memory occupation, and even the mobile phones crash during the multi-task switching.
For another example, some devices with smaller memory may cause frequent under-memory cues when the system runs other applications, or even fail to run multiple applications at the same time, after SystemUI memory increases. Therefore, how to reduce the memory occupation of SystemUI is a problem to be solved.
As known in the related art, systemUI applications can be used in a plurality of user interaction scenarios, and by providing an intuitive display interface, a user can easily access system functions.
For example, in a scenario where a user wakes up and unlocks an electronic device, systemUI applications can display a lock screen interface and a desktop interface for the user. In general, the screen locking wallpaper displayed by the screen locking interface and the desktop wallpaper displayed by the desktop interface may be the same or different.
It may be appreciated that the screen-locking wallpaper displayed by the screen-locking interface and the desktop wallpaper displayed by the desktop interface may be preset by the electronic device, or may be set in response to a wallpaper setting operation of a user.
Currently, the screen-locking wallpaper displayed by the screen-locking interface and the desktop wallpaper displayed by the desktop interface can be set in various modes. For example, by setting the theme, the lock wallpaper and the desktop wallpaper are replaced by one key. When a user selects a certain theme, the system can automatically apply the matched wallpaper to the screen locking and desktop, so that unified conversion of the whole style is realized, and brand new visual feeling is brought to the user.
For example, referring to fig. 1, fig. 1 is a schematic diagram of updating a lock wallpaper and a desktop wallpaper through a theme according to an embodiment of the disclosure. In the embodiment corresponding to fig. 1, an example in which the electronic device is a mobile phone is illustrated, and this example does not limit the embodiments of the disclosure.
As shown by a in fig. 1, an icon 101 for setting an application is included in a main interface (i.e., desktop) 100 of the mobile phone 1. When the mobile phone receives the operation of clicking the setting application icon 101 by the user, the display interface of the mobile phone jumps to the setting interface 102, and the setting interface 102 is shown as b in fig. 1. When the mobile phone receives the operation of clicking the personality theme setting item 103 by the user, the display interface of the mobile phone jumps from the setting interface 102 to the personality theme interface 104, and the personality theme interface 104 is shown as c in fig. 1.
As shown in c in fig. 1, the personality theme interface 104 may include a plurality of preset themes, such as a theme named wisdom, e.g., light, a theme named magic time, a theme named paller, and a theme named hole. It should be noted that the above subject matter is named as an example, and is not meant to limit the embodiments of the present disclosure.
When the mobile phone receives the operation of clicking the smart e.g. photo theme setting item 105 by the user, the display interface of the mobile phone jumps from the personality theme interface 104 to the smart e.g. photo theme interface 106, and the smart e.g. photo theme interface 106 is shown as d in fig. 1. As indicated by d in fig. 1, the wisdom includes an application option 107 in the light topic interface 106. When the mobile phone receives the operation of clicking the application option 107 by the user, the mobile phone can set the screen locking wallpaper and the desktop wallpaper of the mobile phone according to wisdom such as a light theme, so that the whole visual style can be replaced by one key.
Then, when the user unlocks the mobile phone again, the screen locking wallpaper of the screen locking interface is intelligent wallpaper corresponding to the light theme, and the display effect of the screen locking wallpaper can be shown by referring to (a) in fig. 2. When the user unlocks and enters the desktop, the desktop wallpaper of the desktop interface is intelligent, such as wallpaper corresponding to the light theme, and the display effect of the desktop wallpaper can be shown by referring to (b) in fig. 2.
For another example, the user may also update the lock wallpaper and the desktop wallpaper, respectively, according to the specific image selected by the user. Referring to fig. 3, fig. 3 is a schematic diagram of updating a lock wallpaper and a desktop wallpaper through a specific image according to an embodiment of the disclosure. In the embodiment corresponding to fig. 3, an example in which the electronic device is a mobile phone is illustrated, and this example does not limit the embodiments of the disclosure.
Fig. 3 (a) exemplarily shows a display interface 300 of all photos in a gallery APP, where the display interface 300 includes a plurality of images. When the mobile phone receives the operation of clicking the image 301 by the user, the display interface 300 of the mobile phone jumps to the enlarged interface 302 of the image 301, and the enlarged interface 302 of the image 301 is shown as b in fig. 3.
As shown in b of fig. 3, the enlarged interface 302 of the image 301 may include a plurality of function options, such as a share option, a favorites option, an edit option, a delete option, and a more option 303. It should be noted that the above options are exemplary illustrations, and do not limit the embodiments of the disclosure.
When the handset receives an operation of clicking on the further option 303 by the user, the enlarged interface 302 of the image 301 pops up the window interface 304. The window interface 304 may include a plurality of function options, such as copy option, hide option, set to option 305, rotate option, and so forth. When the handset receives the user click setting option 305 operation, the handset display interface jumps to photo setting interface 306. Photo setup interface 306 may include a number of functional options, such as a set lock screen option, a set desktop option, and a simultaneous setup option 307. When the handset receives the operation of clicking the simultaneous setting option 307 by the user, the handset can set the lock wallpaper and the desktop wallpaper of the handset according to the image 301. And when the user unlocks the mobile phone again, the screen locking wallpaper of the screen locking interface is the image 301, and when the user enters the desktop, the desktop wallpaper of the desktop interface is still the image 301.
For another example, by setting a magazine screen locking function, the electronic device can periodically push a series of pictures, so that continuous updating of screen locking wallpaper is realized. When the screen locking desktop is awakened every time, freshness can be brought to the user.
Of course, other ways of updating the lock wallpaper and desktop wallpaper may be used in addition to those mentioned above, for example, some specific applications may provide rich wallpaper resources for the user to select, or some special wallpaper setting options may be added in the updating of the system, etc. The embodiments of the present disclosure are not limited in any way.
Based on the usage scenario of SystemUI application shown in fig. 1-3, in the process of setting the screen locking wallpaper and the desktop wallpaper, the screen locking wallpaper and the desktop wallpaper are the same. In this case, the wallpaper may be further processed to reduce SystemUI memories, to implement light weight processing on SystemUI, and to further reduce the impact on low-end mobile phones or devices.
For this reason, the present disclosure provides a wallpaper display method applied to an electronic device. Under the condition that the screen locking wallpaper and the desktop wallpaper are the same, the screen locking wallpaper can be subjected to downsampling treatment. Therefore, the memory occupation of the screen locking wallpaper can be reduced, and the memory consumption of SystemUI application can be further reduced. When the lock screen wallpaper is displayed, the lock screen wallpaper can be displayed in a transparent mode, and meanwhile the display state of the desktop wallpaper is set to be visible. Therefore, the desktop wallpaper can be displayed on the screen locking interface in a transparent manner, and the use experience of a user cannot be affected.
The embodiment of the disclosure provides a wallpaper display method which is applied to electronic equipment.
By way of example, the electronic device in the embodiments of the present disclosure may be a portable computer (e.g., a mobile phone), a tablet computer, a wearable device, a vehicle-mounted device, an Augmented Reality (AR)/Virtual Reality (VR) device, a desktop, a laptop, a handheld computer, a notebook, an ultra-mobile personalcomputer, a UMPC, a netbook, a cellular phone, a Personal Digital Assistant (PDA), a media player, etc. having a screen (or referred to as a display screen), and the specific form of the electronic device is not particularly limited in the embodiments of the present disclosure.
Referring to fig. 4, fig. 4 shows a schematic diagram of one possible hardware structure of the electronic device:
As shown in fig. 4, the electronic device 400 may include a processor 410, an external memory interface 420, an internal memory 421, a universal serial bus (universal serial bus, USB) interface 430, a charge management module 440, a power management module 441, a battery 442, an antenna 1, an antenna 2, a mobile communication module 450, a wireless communication module 460, an audio module 470, a speaker 470A, a receiver 470B, a microphone 470C, an earphone interface 470D, a sensor module 480, keys 490, a motor 491, an indicator 492, a camera 493, a display screen 494, and a subscriber identity module (subscriber identification module, SIM) card interface 495, etc.
The sensor module 480 may include a pressure sensor, a gyroscope sensor, a barometric sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.
It is to be understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 400. In other embodiments, electronic device 400 may include more or fewer components than shown, or may combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
The processor 410 may include one or more processing units, for example, the processor 410 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (IMAGE SIGNAL processor, ISP), a controller, a memory, a video codec, a digital signal processor (DIGITAL SIGNAL processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.
The controller may be a neural hub and command center of the electronic device 400. The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.
A memory may also be provided in the processor 410 for storing instructions and data. In some embodiments, the memory in the processor 410 is a cache memory. The memory may hold instructions or data that the processor 410 has just used or recycled. If the processor 410 needs to reuse the instruction or data, it may be called directly from memory. Repeated accesses are avoided, reducing the latency of the processor 410 and thus improving the efficiency of the system.
In some embodiments, processor 410 may include one or more interfaces. The interfaces may include an integrated circuit (inter-INTEGRATED CIRCUIT, I4C) interface, an integrated circuit built-in audio (inter-INTEGRATED CIRCUIT SOUND, I4S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous receiver transmitter (universal asynchronous receiver/transmitter, UART) interface, a mobile industry processor interface (mobile industry processor interface, MIPI), a general-purpose input/output (GPIO) interface, a subscriber identity module (subscriber identity module, SIM) interface, and/or a universal serial bus (universal serial bus, USB) interface, among others.
It should be understood that the connection relationship between the modules illustrated in this embodiment is merely illustrative, and does not limit the structure of the electronic device 400. In other embodiments, the electronic device 400 may also employ different interfaces in the above embodiments, or a combination of interfaces.
The charge management module 440 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. The battery 442 may be charged by the charge management module 440, and the electronic device may be powered by the power management module 441.
The power management module 441 is configured to connect the battery 442, the charge management module 440 and the processor 410. The power management module 441 receives input from the battery 442 and/or the charge management module 440 to power the processor 410, the internal memory 421, the external memory, the display screen 494, the camera 493, the wireless communication module 460, and the like. In some embodiments, the power management module 441 and the charge management module 440 may also be provided in the same device.
The wireless communication function of the electronic device 400 may be implemented by the antenna 1, the antenna 2, the mobile communication module 450, the wireless communication module 460, the modem processor, the baseband processor, and the like. In some embodiments, antenna 1 and mobile communication module 450 of electronic device 400 are coupled, and antenna 2 and wireless communication module 460 are coupled, such that electronic device 400 may communicate with a network and other devices through wireless communication techniques.
The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in electronic device 400 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example, the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.
The mobile communication module 450 may provide a solution for wireless communication, including 2G/3G/4G/5G, as applied to the electronic device 400. The mobile communication module 450 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), or the like. The mobile communication module 450 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation.
The mobile communication module 450 may amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate the electromagnetic waves. In some embodiments, at least some of the functional modules of the mobile communication module 450 may be disposed in the processor 410. In some embodiments, at least some of the functional modules of the mobile communication module 450 may be disposed in the same device as at least some of the modules of the processor 410.
The wireless communication module 460 may provide solutions for wireless communication including WLAN (e.g., (WIRELESS FIDELITY, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation SATELLITE SYSTEM, GNSS), frequency modulation (frequency modulation, FM), near Field Communication (NFC), infrared (IR), etc., applied on the electronic device 400.
The wireless communication module 460 may be one or more devices that integrate at least one communication processing module. The wireless communication module 460 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and transmits the processed signals to the processor 410. The wireless communication module 460 may also receive a signal to be transmitted from the processor 410, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.
The electronic device 400 implements display functions via a GPU, a display screen 494, and an application processor, etc. The GPU is a microprocessor for image processing, and is connected to the display screen 494 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 410 may include one or more GPUs that execute program instructions to generate or change display information.
The display screen 494 is used to display images, videos, and the like. The display screen 494 includes a display panel.
Electronic device 400 may implement capture functionality through an ISP, camera 493, video codec, GPU, display screen 494, and application processor, among others. The ISP is used to process the data fed back by the camera 493. The camera 493 is used to capture still images or video. In some embodiments, electronic device 400 may include 1 or N cameras 493, N being a positive integer greater than 1.
The external memory interface 420 may be used to connect an external memory card, such as a Micro SD card, to enable expansion of the memory capabilities of the electronic device 400. The external memory card communicates with the processor 410 through an external memory interface 420 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.
The internal memory 421 may be used to store computer-executable program code that includes instructions. The processor 410 executes various functional applications of the electronic device 400 and data processing by executing instructions stored in the internal memory 421. For example, in an embodiment of the present disclosure, the processor 410 may include a storage program area and a storage data area by executing instructions stored in the internal memory 421.
The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data created during use of the electronic device 400 (e.g., audio data, phonebook, etc.), and so on. In addition, the internal memory 421 may include a high-speed random access memory, and may also include a nonvolatile memory, such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like.
Electronic device 400 may implement audio functionality through audio module 470, speaker 470A, receiver 470B, microphone 470C, headphone interface 470D, and an application processor, among others. Such as music playing, recording, etc.
The keys 490 include a power-on key, a volume key, etc. The keys 490 may be mechanical keys. Or may be a touch key. The motor 491 may generate a vibration cue. The motor 491 may be used for incoming call vibration alerting as well as for touch vibration feedback. The indicator 492 may be an indicator light, which may be used to indicate a state of charge, a change in charge, an indication message, a missed call, a notification, or the like. The SIM card interface 495 is used to connect to a SIM card. The SIM card may be inserted into the SIM card interface 495 or removed from the SIM card interface 495 to enable contact and separation with the electronic device 400. The electronic device 400 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The SIM card interface 495 may support Nano SIM cards, micro SIM cards, etc.
Further, on the above components, an operating system such as a hong Meng operating system, an iOS operating system, an Android operating system, a Windows operating system, and the like is run. An operating application may be installed on the operating system. In other embodiments, there may be multiple operating systems running within the electronic device.
It should be understood that the hardware modules included in the electronic device illustrated in fig. 4 are merely exemplary and are not limiting on the specific structure of the electronic device. Indeed, other hardware modules may be included in the electronic device according to the embodiments of the present disclosure, where the other hardware modules have an interaction with the hardware modules illustrated in the drawings, and are not specifically limited herein. For example, the electronic device may also include a flash, a miniature projection device, and the like. As another example, if the electronic device is a PC, the electronic device may also include a keyboard, a mouse, and the like.
The software system of the electronic device may adopt a layered architecture, an event driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. Embodiments of the invention are configured in a layered mannerThe system is an example illustrating the software architecture of an electronic device.
Fig. 5 is a software architecture block diagram of an electronic device of an embodiment of the present disclosure. The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, it willThe system is divided into four layers, namely an application layer (application layer for short), an application framework layer (framework), an Zhuoyun rows (Android runtime), a system library and a kernel layer from top to bottom.
The application layer may include a series of application packages. By way of example, the application packages may include camera, gallery, calendar, phone, map, navigation, WLAN, bluetooth, systemUI, theme, wallpaper application, etc. Applications (APP).
The systemUI is used for displaying interfaces of the electronic device, such as screen locking wallpaper for displaying a screen locking interface and desktop wallpaper for displaying a desktop interface.
The application framework layer provides an application programming interface (applica x tion programming interface, API) and programming framework for the application of the application layer. The application framework layer includes a number of predefined functions.
As shown in fig. 5, the application framework layer may include an activity manager, a window manager, a content provider, a view system, a resource manager, a notification manager, etc., to which embodiments of the present disclosure do not limit in any way.
An activity manager (ACTIVITY MANAGER) is used to manage the lifecycle of each application. Applications typically run in the operating system in the form of activities. For each Activity, there will be an application record (ActivityRecord) corresponding to it in the Activity manager, this ActivityRecord records the status of the application's Activity. The Activity manager may schedule the Activity process of the application using this ActivityRecord as an identification.
The window manager (WindowManagerService) is used for managing the resources of a graphical user interface (GRAPHICAL USER INTERFACE, GUI) used on a screen, and is particularly used for acquiring the size of the screen, creating and destroying the window, displaying and hiding the window, layout of the window, focus management, input method and wallpaper management and the like.
The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc. The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.
The application framework layer may also include a power manager (power), a phone window manager (PhoneWindowManager), a lock screen service (keyguardService), a theme service, a wallpaper service, and an image compositor (surfaceflinger). The power manager is used for shutting down unnecessary hardware components, so that power consumption is effectively reduced. The telephone window manager is used to handle telephone related functions on the lock screen interface. Wallpaper services are used to process content related to wallpaper. The theme service is used to process content related to a theme. The image synthesizer is a system service for synthesizing the image layer corresponding to the screen locking interface and the image layer corresponding to the desktop interface.
Android Runtime (Android run) includes a core library and virtual machines. Android runtime is responsible for scheduling and management of the android system. The core library comprises two parts, wherein one part is a function required to be called by java language, and the other part is an android core library. The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.
The system library may include a plurality of functional modules. Such as surface manager (surface manager), media library (Media Libraries), three-dimensional graphics processing library (e.g., openGL ES), two-dimensional image engine (e.g., SGL), etc.
The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications. Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc. OpenGL ES is used to implement three-dimensional graphics drawing, image rendering, composition, and layer processing. SGL is the drawing engine for 2D drawing.
The kernel layer is a layer between hardware and software. The kernel layer at least includes display driver, camera driver, audio driver, sensor driver, etc., which is not limited in any way by the embodiments of the present disclosure.
The methods in the following embodiments may be implemented in an electronic device having the above-described hardware structure or software structure.
The following describes in detail a wallpaper display method according to an embodiment of the present disclosure with reference to the accompanying drawings. The method can be applied to the electronic device. As shown in fig. 6, the method specifically includes:
In step 601, when the electronic device is in the first state, systemUI application determines whether the magazine lock screen function is opened.
The first state may be any state of the electronic device being in an off-screen wake-up state, the electronic device being in a power-on start-up state, a theme being set by a user, or wallpaper being set by the user.
The off-screen wake-up state refers to that when the display screen of the electronic device is in an off-screen state, the display screen is waken up in a preset mode, and the electronic device is enabled to enter an operable state. The preset mode may be that the user presses a power key, or the user picks up the electronic device, and the electronic device changes from a stationary state to a lifted state.
In some examples, the implementation of the electronic device in the first state may be that the electronic device receives a first operation by a user and, in response to the first operation, the electronic device enters the first state. The first operation is used for triggering the electronic equipment to be in a first state. The first operation may be a touch operation, a voice operation, or a space-apart gesture operation.
Taking the first operation as an example, the touch operation comprises the operation of pressing a power key on the side of the electronic equipment to enable the electronic equipment to be in a screen-off awakening state. Or the power key on the side of the electronic equipment is pressed for a long time to enable the electronic equipment to be in a starting state. Or selecting the target image and confirming the application of the target image as wallpaper. And then or selecting and confirming the operation of applying the target theme.
When the user uses the electronic equipment, the user can make the electronic equipment enter an off-screen awakening state through the operation of pressing the power key. In the process that the electronic equipment is awakened, the electronic equipment can acquire the screen locking wallpaper and the desktop wallpaper, and load the screen locking wallpaper and/or the desktop wallpaper for a user through SystemUI application.
Or when the user uses the electronic equipment, the user can make the electronic equipment enter a starting-up starting state through long-time pressing of the power key. In the starting process of the electronic equipment, the electronic equipment can acquire the screen locking wallpaper and the desktop wallpaper, and after the electronic equipment is successfully started, the screen locking wallpaper and/or the desktop wallpaper are loaded for a user through SystemUI application.
Or when the user uses the electronic equipment, if the user wants to change the wallpaper of the electronic equipment, the user can open the gallery application to view all images, if the target image accords with the preference of the user, the user can select the target image, and the target image is set as the screen locking wallpaper and/or the desktop wallpaper through the wallpaper setting operation. Wherein the wallpaper setting operation is for causing the electronic device to set the target image as the target wallpaper.
Still further or while the user is using the electronic device, the user may first return to the desktop including the icons of the subject application and then click on the icons of the subject application to display the interface of the subject application. If a certain theme accords with the preference of the user, the user can select the theme, the electronic equipment applies the theme through the theme setting operation, and the image corresponding to the theme is displayed on the screen locking wallpaper and the desktop wallpaper. The theme setting operation is used for enabling the electronic device to apply the target theme.
The screen locking wallpaper and/or the desktop wallpaper can be static images, dynamic images or videos and the like. Taking the user selection as an example, the static image is set as wallpaper, and the static image can be an image corresponding to the theme of the electronic equipment, such as lovely pet, landscape, cartoon, game, automobile, building and the like, can also be an image, screenshot, network image and the like stored in the album of the electronic equipment, and can also be a static image provided by a wallpaper application program. Specifically, the method can be determined according to actual use requirements, and embodiments of the disclosure are not limited.
When the electronic device is in the first state, systemUI applications need to load the screen-locking wallpaper for the user at the screen-locking interface in order to provide a more personalized and rich visual experience for the user.
SystemUI applications are responsible for managing and controlling the display and interaction of the entire lock screen interface. When the electronic device enters the first state, systemUI applications may call the lock clock layer, the lock wallpaper layer (i.e., backDropView), and the desktop wallpaper layer (i.e., IMAGEWALLPAPER) according to the user settings and the system settings, respectively, to construct a complete lock interface.
The screen locking clock layer is used for displaying current time information on a screen locking interface. The layer may also display other time-related information such as date, week, etc. The layer is presented in BottomAreaView form. The screen locking wallpaper layer is used for displaying screen locking wallpaper of the screen locking interface. The desktop wallpaper layer (i.e., IMAGEWALLPAPER) is used to display desktop wallpaper of the desktop interface.
Before the screen locking interface is constructed, systemUI applications need to acquire screen locking wallpaper and desktop wallpaper first, and load the screen locking wallpaper and the desktop wallpaper into corresponding layers. Then SystemUI application obtains the current time information and displays the obtained time information on the lockscreen clock layer. When the user interacts with the lock screen interface, systemUI application adjusts and updates the three layers according to the user operation, such as sliding unlocking, checking notification, and the like.
For example, when a user triggers an unlocking operation of the electronic device, the SystemUI application gradually hides the lock screen interface and simultaneously displays the desktop interface, and at this time, the desktop wallpaper becomes the main display content.
Typically, systemUI may be the same or different for the lock wallpaper loaded on the lock wallpaper layer and the desktop wallpaper loaded on the desktop wallpaper layer.
When the screen locking wallpaper and the desktop wallpaper are different, the screen locking wallpaper and the desktop wallpaper cannot be replaced with each other, and the wallpaper can be loaded for a user according to a wallpaper loading flow in the related technology.
When the screen locking wallpaper and the desktop wallpaper are the same, the screen locking wallpaper and the desktop wallpaper can be replaced. For example, lock screen wallpaper is displayed with desktop wallpaper. Thus, the user can still view the screen-locking wallpaper at the screen-locking interface. When the desktop wallpaper is utilized to display the screen-locking wallpaper, the screen-locking wallpaper loaded by the screen-locking interface may be processed, e.g., the screen-locking wallpaper loaded by the screen-locking interface is downsampled. Through the processing, the memory space occupied by the screen locking wallpaper is reduced, and the memory occupied by the corresponding SystemUI is also reduced, so that the performance of the electronic equipment can be improved.
It will be appreciated that this approach is implemented on the premise that the lock wallpaper and the desktop wallpaper are identical, so that it is necessary to determine whether the lock wallpaper and the desktop wallpaper are identical prior to applying this approach. And then, loading the wallpaper according to whether the screen locking wallpaper and the desktop wallpaper are the same or not in different modes.
At present, the types of the screen locking wallpaper are more, and the screen locking wallpaper and the desktop wallpaper can be the same or different under different types. For example, the lock wallpaper may be a magazine lock, where the lock wallpaper displayed by the magazine lock at the lock interface is generally different from the desktop wallpaper displayed by the desktop interface. The lock wallpaper may also be a target image set by the user, which may be set as only lock wallpaper, or may be set as both lock wallpaper and desktop wallpaper. Therefore, when the lock wallpaper is a target image set by the user, the lock wallpaper and the desktop wallpaper may be the same or different. The screen locking wallpaper can be an image corresponding to the theme set by the user, when the set source of the theme is a preset catalog, the screen locking wallpaper is considered to be the same as the desktop wallpaper, and when the set source of the theme is not the preset catalog, the screen locking wallpaper is considered to be different from the desktop wallpaper.
According to the above, the type of the lock wallpaper can be magazine lock or non-magazine lock. The method for determining whether the screen locking wallpaper is the same as the desktop wallpaper can be realized by determining whether the screen locking function of the magazine of the electronic equipment is started or not, and continuously judging whether the screen locking wallpaper is the same as the desktop wallpaper under the condition that the screen locking function of the magazine is not started.
In some examples, the Setting database includes a magazine lock status bit. The magazine lock application updates the magazine lock status bit of the Setting database, for example, when the magazine lock function is opened, the magazine lock status bit is 1, and when the magazine lock function is not opened, the magazine lock status bit is 0.
The process of SystemUI application determining whether the magazine lock screen function of the electronic device is opened may be that SystemUI application interacts with an interface of the settingdatabase to obtain a magazine lock screen status bit of the settingdatabase. When the magazine lock status bit is 1, systemUI application determines that the magazine lock function is open. When the magazine lock status bit is 0, systemUI application determines that the magazine lock function is not open.
Step 602, under the condition that the magazine screen locking function is started, systemUI application loads the wallpaper to be displayed based on the original size of the wallpaper to be displayed.
The wallpaper to be displayed is a screen locking wallpaper to be displayed on the screen locking interface.
In connection with step 601, when the magazine lock screen function is turned on, the lock screen wallpaper is different from the desktop wallpaper if the lock screen wallpaper is derived from the magazine lock screen application. Therefore, the desktop wallpaper cannot be utilized, and the screen locking wallpaper is displayed. That is, if it is determined that the magazine lock screen function is on, systemUI applications need to load the wallpaper to be displayed normally according to the original size of the wallpaper to be displayed.
In some examples, the SystemUI application may connect to a preset repository with the magazine lock screen function open. The resource library is used for providing magazine lock screen wallpaper. The repository may be a server provided by the device manufacturer or may be a specific folder stored locally.
SystemUI the application can access the resource library through network connection or a local file system to acquire the picture list or picture catalog information in the resource library. In the case that there are multiple pictures in the resource library, systemUI application may select a picture from the resource library as wallpaper according to a preset order or randomly. The preset sequence may be a time sequence, a topic classification sequence, etc.
In addition, in order to increase the loading speed of the picture, when SystemUI application is in idle state or connected to the network, the preloading and buffering operation can be performed in the background, the wallpaper is downloaded in advance, and the downloaded wallpaper is buffered in the local storage. Therefore, when wallpaper needs to be loaded, systemUI application can directly read the wallpaper from the cache, and waiting time is reduced. And, systemUI application can also adapt and adjust the image according to the screen size and resolution of itself when the wallpaper is loaded, so as to ensure that the wallpaper presents the best display effect.
In some examples, the SystemUI application may load the wallpaper to be displayed based on the original size of the wallpaper to be displayed in the event that the magazine lock screen function is determined to be on, the process of loading the wallpaper to be displayed may be that SystemUI sends a wallpaper acquisition request to the magazine lock screen application in the event that the magazine lock screen function is determined to be on, the magazine lock screen application receives the wallpaper acquisition request and determines the wallpaper to be displayed from the resource library in response to the wallpaper acquisition request and the wallpaper display rules, and sends the wallpaper to be displayed to the SystemUI application, and the SystemUI application receives the wallpaper to be displayed for quick subsequent display. The wallpaper obtaining request is used for requesting the magazine screen locking application to obtain wallpaper to be displayed. Wallpaper display rules may be set according to user preferences or display effects, which is not limiting to the present disclosure.
In step 603, if the magazine lock screen function is not turned on, systemUI application determines whether the status bit of the settings database is the target identifier field.
The status bit of the settings database is used for identifying whether the screen locking wallpaper and the desktop wallpaper are the same. The target identification field is used for representing that the screen locking wallpaper is the same as the desktop wallpaper.
Illustratively, the status bits of the settings database may be represented by different types of identification fields. For example, when wallpaper displayed on the lock screen interface and wallpaper displayed on the desktop interface are the same, the identification field corresponding to the status bit may be updated to 1. When the wallpaper displayed on the screen locking interface and the wallpaper displayed on the desktop interface are different, the identification field corresponding to the status bit can be updated to 0.
As can be seen from step 601, when the magazine screen locking function is not started, the screen locking wallpaper may be a target image set by the user, or may be an image corresponding to a theme set by the user. When the screen locking wallpaper is a target image set by a user, the screen locking wallpaper and the desktop wallpaper can be the same or different. When the screen locking wallpaper is an image corresponding to the theme set by the user and the theme is the theme under the preset directory, the screen locking wallpaper is the same as the desktop wallpaper. That is, when the magazine screen locking function is not opened, the screen locking wallpaper and the desktop wallpaper may be the same or different. Therefore, after determining whether the magazine screen locking function is started, whether the screen locking wallpaper is the same as the desktop wallpaper needs to be continuously judged.
Generally, when a user needs to set wallpaper, the user can set wallpaper in various ways. When the wallpaper setting is completed, the judgment result of whether the screen locking wallpaper is the same as the desktop wallpaper may change. When the judgment result of whether the screen locking wallpaper is the same as the desktop wallpaper is needed, the judgment is needed again, which results in a large number of repeated codes, low processing efficiency and long time consumption.
Therefore, in order to better adapt to the wallpaper setting requirement of the user, after the user finishes wallpaper setting, whether the screen locking wallpaper is the same as the desktop wallpaper or not can be judged in real time, and the judgment result is stored in the form of a status bit of a settingdatabase. When the judgment result of whether the screen locking wallpaper is the same as the desktop wallpaper is needed, the status bit of the settings database can be directly accessed. Therefore, the code quantity can be greatly reduced, the code readability can be improved, and the memory occupation of the electronic equipment can be optimized. Therefore, when determining that the magazine lock screen function is not opened, the present disclosure can directly determine how to load wallpaper through the status bit of the settingdatabase. Of course, other ways may be used to save the determination result of whether the screen-locking wallpaper and the desktop wallpaper are the same, which is not limited in this disclosure.
In connection with the foregoing, it is known that a user can set wallpaper in a variety of ways. And after the user completes wallpaper setting, updating the status bit of the settings database. The updating of the status bits of the settings database involves the following scenario.
And in the first scene, setting of the screen locking wallpaper and the desktop wallpaper is realized through setting the theme. And after the screen locking wallpaper and the desktop wallpaper are set, updating the status bit of the settingdatabase. The setting theme may be set automatically by the electronic device, or may be set by a user, for example. The theme automatically set by the electronic device is a preset theme, and the theme set by the user can be derived from a plurality of different approaches, and the details can be referred to the embodiment shown in fig. 7 and 8.
And in a second scene, setting screen locking wallpaper and desktop wallpaper through images in the gallery application program. After the screen-locking wallpaper and the desktop wallpaper are set, the status bit of the settings database is updated, and the details can be referred to the embodiment shown in fig. 9.
The implementation of lock wallpaper and desktop wallpaper settings by setting the theme is described in exemplary fashion below in connection with fig. 7 and 8. And after the screen locking wallpaper and the desktop wallpaper are set, updating the state bit of the settingdatabase.
In step 701, when the electronic device is started for the first time, the theme service determines whether to apply the target theme.
The target theme is a theme set by users other than a preset theme, and the preset theme is a theme set when the electronic equipment leaves the factory.
In the process of first starting of the electronic equipment, the screen locking wallpaper is generally obtained from a preset path, and the screen locking wallpaper is displayed for a user. The screen locking wallpaper can be derived from a preset theme.
The electronic device receives a start operation of a user, and displays a lock screen interface in response to the start operation. And responding to unlocking operation triggered by the user on the screen locking interface, and displaying the desktop interface by the electronic equipment. The screen locking wallpaper displayed by the screen locking interface is the same as the desktop wallpaper displayed by the desktop interface, and the wallpaper is the wallpaper corresponding to the preset theme. The starting operation is any one of a single click operation, a double click operation and a knuckle knocking operation, and the multi-finger selecting operation.
In some examples, the process of determining whether to apply the target theme may be that the theme application obtains a theme flag bit and determines whether the electronic device applies the target theme according to the theme flag bit. The theme zone bit is determined according to a name corresponding to a theme of the current application of the electronic equipment and a name corresponding to a preset theme.
The process of determining the theme zone bit according to the name corresponding to the theme of the current application of the electronic device and the name corresponding to the preset theme can be, for example, that the name corresponding to the preset theme is obtained from the preset address, the name corresponding to the current theme and the name corresponding to the preset theme are compared, and the theme zone bit is updated according to whether the name corresponding to the current theme and the name corresponding to the preset theme are the same or not.
In step 702, in the case that the electronic device does not apply the target theme, the theme service updates the status bit of the settings database.
When an electronic device is first started, the electronic device generally applies a preset theme to display screen locking wallpaper and desktop wallpaper for a user. The theme service may determine whether the electronic device applies the target theme, and after determining whether the electronic device applies the target theme, may update a status bit of the settings database based on an application condition of the target theme.
For example, in the case that it is determined that the electronic device does not apply the target theme, it is explained that the electronic device applies the preset theme, that is, the current lock wallpaper of the electronic device is the same as the desktop wallpaper, and the status bit of the settingdatabase is updated to 1.
In some examples, where the electronic device does not apply the target theme, the theme service may update the status bits of the settingdatabase by interacting with an interface of the settingdatabase upon determining that the electronic device does not apply the target theme.
It will be appreciated that, in the two implementation manners of setting the theme, the step 701 and the step 801 exist in parallel and do not have a certain sequence, the step 701 may be performed first, then the step 801 may be performed, only the step 701 may be performed, or only the step 801 may be performed, which is not limited in this disclosure.
Step 801, the electronic device receives a theme setting operation of a user on a theme to be applied.
The theme setting operation is used for triggering the electronic equipment to set the theme to be applied as the theme of the electronic equipment. The theme setting operation may be any one of a single click operation, a double click operation, a knuckle tap, and a multi-finger selection operation, for example.
In some examples, the electronic device may include a setup application by which a user may select a theme to be applied and set the selected theme to be applied as a theme of the electronic device. The electronic device may further include a theme application, and the user may select a theme to be applied through the theme application and set the selected theme to be applied as a theme of the electronic device. Of course, the user may set the theme in other ways, which the present disclosure does not limit.
The following exemplifies the theme of the electronic device set by the user through the setting application.
When the user needs to set the theme, the user can open the setting application program on the electronic device, that is, the electronic device can receive the opening operation of the setting application program by the user, for example, the electronic device can receive the clicking operation of the icon corresponding to the setting application program by the user. In response, the electronic device may display an interface corresponding to the setup application. The interface to which the setup application corresponds may include a plurality of function items, for example, a theme function item, a wallpaper function item, and the like. The electronic device may receive a click operation of the subject function by the user. In response, the electronic device may display a theme interface. The theme interface may include at least one theme.
The user can browse a plurality of topics in the topic interface through clicking operation or sliding operation, when the topic to be applied meets the personalized requirements of the user, the electronic device can receive the clicking operation of the topic to be applied by the user, and in response, the electronic device can display an introduction interface of the topic to be applied, and the introduction interface of the topic to be applied can comprise application setting items. The electronic device may receive a click operation of the application setting item by the user. In response, the electronic device sets the theme to be applied as the theme of the electronic device.
In step 802, in response to the theme setting operation, the theme service determines whether the theme to be applied is derived from a preset catalog.
The electronic device comprises a preset catalog, and a plurality of themes can be stored in the preset catalog.
The multiple topics can be shown for the user through the topic function item of the setting application, and can also be shown for the user through the topic application. Of course, the various topics may also be presented to the user by other means, which the present disclosure is not limited to.
After the electronic equipment detects that a user executes theme setting operation on a theme to be applied, the theme service of the electronic equipment sets the theme to be applied as the current theme of the electronic equipment as a response, and simultaneously determines whether the theme to be applied is a theme under a preset directory.
For example, a plurality of topics stored under the preset directory may be presented to the user by setting the topic function item of the application, and when the user needs to set the topic, the topic to be applied may be selected from the plurality of topics displayed by the topic function item of the set application. And in response, the electronic equipment sets the theme to be applied as the current theme of the electronic equipment, and simultaneously determines whether the theme to be applied is the theme under the preset directory.
In some examples, when a user performs a theme setting operation on a touch screen of an electronic device, a user interface event corresponding to the theme setting operation may be triggered. Then, an operating system (e.g., androidTM) of the electronic device captures a user interface event corresponding to the theme setting operation, and parses that the user interface event corresponding to the theme setting operation represents the theme setting operation. Then, the operating system takes the identified theme setting operation as input, calls an application program interface (Application Programming Interface, API) corresponding to the theme setting operation, and transfers the theme setting operation to the theme service. After the theme service receives the theme setting operation through the API, whether the theme to be applied is from the preset catalogue or not is determined according to the theme setting operation.
The process of determining whether the theme to be applied is the theme under the preset directory by the theme service may be that the theme service receives the theme to be applied sent by the electronic device, and examines the package name (CALLINGPACKAGE) of the sender corresponding to the theme to be applied, so as to determine the setting source of the theme to be applied through the package name of the sender corresponding to the theme to be applied. For example, the package name of the sender corresponding to the topic to be applied may be a setting application, or may be a third party application, for example, a topic application, which is not limited by the disclosure.
Step 803, when it is determined that the theme to be applied is derived from the preset directory, the theme service updates the status bit of the settings database.
When the user sets the theme, the electronic device can display the screen locking wallpaper and the desktop wallpaper for the user based on the theme to be applied selected by the user. After the user selects the theme to be applied, the status bit of the settings database may be updated based on whether the theme to be applied originates from the preset catalog.
For example, when it is determined that the theme to be applied is derived from the preset directory, the screen locking wallpaper and the desktop wallpaper of the electronic device are considered to be the same, and the status bit of the settings database is updated to 1. When the theme to be applied does not come from the preset catalog, the screen locking wallpaper and the desktop wallpaper corresponding to the theme to be applied are possibly different, and the status bit of the settings database is updated to 0. In addition, when the electronic device is confirmed to have no application theme, the status bit of the settings database defaults to 0.
In some examples, when determining that the target topic is a topic under a preset directory, updating the status bit of the settingdatabase may be performed by the topic service interacting with an interface of the settingdatabase to update the status bit of the settingdatabase when determining that the source of the topic to be applied is the preset directory.
The implementation of lock wallpaper and desktop wallpaper settings through images in a gallery application is described in exemplary detail below in connection with fig. 9. And after the screen locking wallpaper and the desktop wallpaper are set, updating the state bit of the settingdatabase.
Step 901, the electronic device receives wallpaper setting operation of a user on a target image.
The wallpaper setting operation is used for triggering the electronic device to set the target image as the wallpaper of the electronic device. For example, the wallpaper setting operation may be any one of a single click operation, a double click operation, a knuckle tap, and a multi-finger selection operation.
In some examples, the electronic device may include a gallery application by which a user may select a target image and set the selected target image as wallpaper. The electronic device may also include a wallpaper application by which the user may select a target image and set the selected target image as wallpaper. Or the electronic device may further include a theme application, and the user may select a theme through the theme application and generate wallpaper using the selected theme. Still alternatively, the electronic device may further include a setup application, and the user may select the target image through a wallpaper function of the setup application, and use the selected target image as wallpaper. Of course, the user may set wallpaper in other ways, which the present disclosure does not limit.
The following is an example of wallpaper setting by a user through a gallery application.
When the user needs to set wallpaper, the user can open a gallery application program on the electronic device, namely the electronic device can receive the opening operation of the user on the gallery application program, for example, the electronic device can receive the clicking operation of the user on the icon corresponding to the gallery application program. In response, the electronic device may display an interface corresponding to the gallery application. The interface corresponding to the gallery application may include at least one image.
The user can browse the images in the gallery application program through clicking operation or sliding operation, when the target image meets the personalized requirements of the user, the electronic device can receive wallpaper setting operation of the user on the target image, and in response, the electronic device can set the target image as wallpaper. It will be appreciated that the target image may be set as a lock wallpaper and/or a desktop wallpaper by a wallpaper setting operation.
In response to the wallpaper setting operation of the user, the wallpaper service determines a setting source of the target image, step 902.
After receiving the wallpaper setting operation of the user on the target image, the electronic device may first determine a setting source of the target wallpaper in response to the wallpaper setting operation.
In some examples, in response to a wallpaper setting operation by a user, the process of the electronic device determining a setting source of the target image may include the electronic device generating a wallpaper setting request in response to a wallpaper setting operation by the user on the target image and sending the wallpaper setting request to the wallpaper service. A wallpaper setting request is received, and in response to the wallpaper setting request, the wallpaper service determines a setting source of the target image. Wherein the wallpaper setting request is for requesting that the target image be set as wallpaper. The wallpaper setting request includes a target image.
For example, in response to a wallpaper setting operation of a target image by a user, the process of generating a wallpaper setting request by the electronic device may include first triggering a user interface event corresponding to the wallpaper setting operation when the user performs the wallpaper setting operation on a touch screen of the electronic device. Then, an operating system (e.g., androidTM) of the electronic device captures a user interface event corresponding to the wallpaper setting operation, and parses that the user interface event corresponding to the wallpaper setting operation represents the wallpaper setting operation. Then, the operating system uses the identified wallpaper setting operation as input, calls an application program interface (Application Programming Interface, API) corresponding to the wallpaper setting operation, and transmits the wallpaper setting operation to the electronic device. After receiving the wallpaper setting operation through the API, the electronic equipment generates a wallpaper setting request according to the wallpaper setting operation.
The wallpaper service may determine the setting source of the target image by receiving the target image sent by the electronic device, checking the packet name of the sender corresponding to the target image, and determining the setting source of the target wallpaper by the packet name of the sender corresponding to the target image. For example, the package name of the sender corresponding to the target image may be a gallery application, a theme application, or a setting application, which is not limited by the present disclosure.
In addition, in response to the wallpaper setting request, the wallpaper service may further process the target image to obtain a processed image. The wallpaper service processes the target image, and the process of obtaining the processed image can be that the target image is subjected to operations such as cutting, zooming, color adjustment and the like, so as to obtain the processed image. The processed image can be adapted to the screen size and resolution of different electronic devices.
In step 903, in the case that the set source of the target image is a non-theme application and the target image is not a set application, the wallpaper service loads wallpaper based on the target image.
In response to a wallpaper setting operation by a user, the wallpaper service may determine a setting source of the target image. When the set source of the target image is determined to be a non-subject application and the non-set application, the wallpaper service loads wallpaper based on the target image.
In some scenarios, the wallpaper service is based on the target image, and loading wallpaper specifically refers to loading the lock wallpaper and/or the desktop wallpaper based on the target image. Based on the target image, the process of loading the screen-locking wallpaper and/or the desktop wallpaper may be that the wallpaper service starts a corresponding loading mechanism, acquires the target image from a preset position (i.e., a preset position or a resource library), and sets the target image as the screen-locking wallpaper and/or the desktop wallpaper.
Step 904, the wallpaper service determines whether the lock wallpaper and the desktop wallpaper are the same.
After the wallpaper service finishes the loading of the screen locking wallpaper and/or the desktop wallpaper, the wallpaper service can continuously judge whether the screen locking wallpaper and the desktop wallpaper are the same, and update the status bit of the settings database according to whether the screen locking wallpaper and the desktop wallpaper are the same.
In some examples, the wallpaper service may determine whether the lock wallpaper and the desktop wallpaper are the same by comparing the lock wallpaper and the desktop wallpaper using an image comparison algorithm to obtain a comparison result. The image comparison algorithm may include a pixel level comparison algorithm, a feature extraction and matching algorithm, and the like, and the comparison of the present disclosure is not limited.
The wallpaper service can also inquire the storage paths of the screen locking wallpaper and the desktop wallpaper, and determine whether the screen locking wallpaper and the desktop wallpaper are the same according to the storage paths of the screen locking wallpaper and the desktop wallpaper.
Or the electronic device may assign a unique identifier to each wallpaper. The wallpaper service checks identifiers of the screen locking wallpaper and the desktop wallpaper, and determines whether the screen locking wallpaper and the desktop wallpaper are identical according to whether the identifiers of the screen locking wallpaper and the desktop wallpaper are identical. Of course, whether the lock wallpaper and the desktop wallpaper are the same may also be determined by other means, which is not limited by the present disclosure.
Step 905, updating the status bit of the settings database by the wallpaper service according to whether the screen-locking wallpaper and the desktop wallpaper are the same.
As can be seen from fig. 7-9, a series of steps are required to determine whether the screen-locking wallpaper and the desktop wallpaper are the same, so when the screen-locking wallpaper and/or the desktop wallpaper are changed, the present disclosure may determine whether the screen-locking wallpaper and the desktop wallpaper are consistent by adopting the schemes shown in fig. 7-9, and store the determination result in the form of the status bit of the settings database. Then, when wallpaper is loaded, how to load the wallpaper can be determined directly according to the status bit of the settingdatabase. Shortens the processing time and improves the processing efficiency.
In some examples, the process of updating the status bits of the settingdatabase by the wallpaper service may be to interact with the interfaces of the settingdatabase to update the status bits of the settingdatabase after determining whether the screen-locking wallpaper and the desktop wallpaper are the same, depending on whether the screen-locking wallpaper and the desktop wallpaper are the same.
Illustratively, when the lock wallpaper and the desktop wallpaper are the same, the wallpaper service updates the status bit of the settings database to 1. And when the screen locking wallpaper and the desktop wallpaper are different, updating the status bit of the settingdatabase to 0. Of course, the status bit of the settingdatabase may also be described by other types of data, as long as it can represent whether the lock wallpaper and the desktop wallpaper are the same, which is not limited by the present disclosure.
In addition, the foregoing exemplary description of the status bit updating process of the settingdatabase in fig. 7-9 is for more clearly describing the technical solution of the embodiments of the disclosure, and does not constitute a limitation on the technical solution provided by the embodiments of the disclosure, and it will be known to those skilled in the art that, with the development of the electronic device and the appearance of a new wallpaper setting scenario, the technical solution provided by the embodiments of the disclosure is equally applicable to similar technical problems.
After updating the status bits of the settings database using the exemplary methods of FIGS. 7-9 described above, the following steps may be continued to reduce SystemUI memory.
It will be appreciated that steps 602 and 603 are side-by-side schemes, and that step 603 is not performed when step 602 is performed. When step 603 is performed, step 602 is not performed.
Step 604, in the case that the status bit of the settings database is determined to be the target identification field, systemUI applies downsampling to the wallpaper to be displayed, so as to obtain the processed wallpaper to be displayed.
And when the status bit of the settingdatabase is the target identification field, the screen locking wallpaper is the same as the desktop wallpaper. In combination with step 601, it can be known that, in the case that the lock wallpaper and the desktop wallpaper are the same, the lock wallpaper may be displayed by using the desktop wallpaper. Therefore, when the wallpaper to be displayed is loaded, the wallpaper to be displayed can be processed, and then the processed wallpaper to be displayed is loaded. For example, the screen-locking wallpaper is the first image (i.e. the wallpaper to be displayed), the desktop wallpaper is the first image, and the screen-locking wallpaper and the desktop wallpaper are the same.
The data size of the wallpaper to be displayed is a first numerical value, and the data size of the wallpaper to be displayed after processing is a second numerical value. The second value is less than the first value.
For example, processing the wallpaper to be displayed may be down-sampling the wallpaper to be displayed. Thus, the memory occupation of the wallpaper to be displayed can be reduced, and the memory of SystemUI is reduced.
For example, the down-sampling of the wallpaper to be displayed may be down-sampling the wallpaper to be displayed according to a down-sampling proportion.
For example, the wallpaper to be displayed has a width of 1920 pixels, a height of 1080 pixels and a downsampling ratio of 1/16, and the processed wallpaper has a width of 1920× (1/16) =120 pixels and a height of 1080× (1/16) =67.5 pixels. Therefore, through the downsampling process, the memory occupation of the wallpaper to be displayed can be greatly reduced.
Step 605, in the case that it is determined that the status bit of the settings database is not the target identification field, systemUI applies to load wallpaper to be displayed according to a preset size.
The preset size is the original size of the wallpaper to be displayed.
And when the status bit of the settingdatabase is not the target identification field, indicating that the screen locking wallpaper is different from the desktop wallpaper. According to the step 601, when the screen locking wallpaper and the desktop wallpaper are different, the screen locking wallpaper and the desktop wallpaper cannot be replaced, and the wallpaper to be displayed is required to be loaded according to the preset size, so that a good screen locking display effect is provided for a user. For example, the wall paper is a first image, and the wall paper is a second image, and the wall paper is different from the wall paper.
It will be appreciated that steps 604 and 605 are side-by-side schemes, and that step 605 is not performed when step 604 is performed. When step 605 is performed, step 604 is not performed.
And 606, setting the screen locking wallpaper.
Based on the above steps, when the screen locking wallpaper is the same as the desktop wallpaper, the processed wallpaper to be displayed can be loaded, and the processed wallpaper to be displayed is set as the screen locking wallpaper. When the screen locking wallpaper is different from the desktop wallpaper, the wallpaper to be displayed is loaded according to the preset size, and the wallpaper to be displayed is set as the screen locking wallpaper. The data size (i.e., the second value) of the processed wallpaper to be displayed is smaller than the data size (i.e., the first value) of the wallpaper to be displayed.
In some examples, the process of setting the screen locking wallpaper may be that SystemUI application loads the wallpaper to be displayed and/or the processed wallpaper to be displayed, systemUI application may send the wallpaper to be displayed and/or the processed wallpaper to the screen locking wallpaper layer, and the screen locking wallpaper layer obtains the screen locking wallpaper according to the wallpaper to be displayed and/or the processed wallpaper to be displayed.
Step 607, the electronic device monitors the off-screen event.
The off-screen event refers to an event that a display screen of the electronic device is automatically closed or a user manually closes the display screen.
In some examples, the electronic device receives a user's off-screen operation, and in response to the off-screen operation, the electronic device performs an off-screen procedure. The screen-off operation is used for triggering the electronic equipment to stop screen. The off-screen operation is an operation in which a user presses a power key, for example.
When the user does not need to use the electronic equipment, the user can make the electronic equipment enter the screen-off state by pressing a power key at the side of the electronic equipment. Or the electronic device supports setting specific gestures to realize screen-off. For example, a specific sliding operation is performed on the screen or the screen is double-clicked, etc., to bring the electronic apparatus into an off-screen state. Or even when the electronic device is in a particular scenario, such as a reading mode or a power saving mode. When the electronic equipment does not receive the operation of the user for a period of time, the electronic equipment automatically enters the off-screen state.
It should be noted that the operations performed by the user on the electronic device may be all possible operations performed by the user, and the operations of the user may include, but are not limited to, at least one operation of clicking, double clicking, triple clicking, long pressing a power key, starting an application, and the like, and the disclosure is not limited to parameters such as a type and a number of operations of the user.
In some scenarios, when the backlight of an electronic device is turned off or reduced to a very low level, it is often meant that the user has stopped interacting with the electronic device. In this case, the electronic device may recognize the off-screen event and then transition to a low power state to conserve power and extend battery life. The backlight is an external light source for providing display to the display screen, and is also called a backlight (backlight). The backlight of an electronic device may be understood as the electronic device lighting up a display screen.
As shown in fig. 10, upon recognition of the above backlight event, the power manager, phone window manager, window management service, and user interface application (i.e., systemUI application) perform a series of operations to bring the electronic device into a low-power state.
Illustratively, upon identifying the backlight event described above, the power manager may notify the electronic device that the wake state of the electronic device is about to change via the onWakefulnessChangeStarted method. In addition, the power manager may issue a low power event notification in the form of a broadcast. Wherein the low power event notification is used to notify the electronic device that a low power state is about to be entered.
When the phone window manager receives the low power event notification, the phone-related functions are controlled to be properly handled in a sleep state in response to the low power event notification. For example, when an electronic device has an incoming call, the phone window manager can correctly wake up the device and display the incoming call interface while processing the corresponding user operation.
When the window management service receives the low power event notification, the window management service may send a sleep notification to SystemUI applications in response to the low power event notification. SystemUI the application receives the sleep notification and controls the updating and display of the lock screen interface in response to the sleep notification.
SystemUI applications may include a lock screen service (KeyguardService). The lock service is responsible for displaying the lock interface and also for coordinating the updating of the lock interface through the lock view intermediary KeyguardViewMediator (an intermediary class for handling the lock interface display logic).
In addition, during the time that the electronic device enters a sleep state, the lock view intermediary may invoke the dynamic effects controller (DynEffectController) to further process the lock interface. For example, the lock view intermediary may invoke a dynamic effects controller to implement an animation effect. For example, fade-in and fade-out, sliding effects, etc. The lock view intermediary may also invoke a lock update monitor (KeyguardUpdateMonitor) to refresh changes to the lock interface, such as the fingerprint icon being set to invisible, removing white screen light, refreshing weather locations, and dual clock display, among others. It will be appreciated that the above refreshing is by way of example and is not to be construed as limiting the embodiments of the disclosure.
In response to the off-screen event, systemUI application again determines whether the magazine off-screen function is open, step 608.
Before detecting the off-screen operation, the user may perform some operations on the electronic device, such as setting the lock screen wallpaper display of the lock screen interface to a magazine lock screen display, updating the lock screen wallpaper, and so forth.
As can be seen from fig. 7-9, when the user sets the lock wallpaper or the desktop wallpaper, the status bit of the settings database is updated to indicate whether the lock wallpaper and the desktop wallpaper are the same. When the magazine screen locking function is started, the screen locking wallpaper is different from the desktop wallpaper. However, when the magazine screen locking function is started, the status bit of the setting database is not updated, and the lock screen wallpaper can be continuously processed under the condition that the lock screen wallpaper is the same as the desktop wallpaper, so that SystemUI memory is reduced. Therefore, after detecting the screen-off operation, it is further necessary to determine whether the magazine screen-lock function is opened again.
Step 609, under the condition that the magazine screen locking function is determined to be opened, systemUI is applied to set the display state of the screen locking wallpaper layer of the screen locking interface to be the second display state.
Wherein the second display state is an opaque display.
Referring to step 601, when the magazine screen locking function is turned on, the screen locking wallpaper and the desktop wallpaper are different. In the case where the lock wallpaper and the desktop wallpaper are different, since the lock wallpaper and the desktop wallpaper cannot be replaced with each other, the lock wallpaper needs to be normally loaded and normally displayed (i.e., opaque display). Therefore, when the magazine screen locking function is started, the magazine screen locking application also needs to send the latest wallpaper to be displayed to the SystemUI application again so as to display the latest screen locking wallpaper when the screen locking interface is displayed.
For example, when the magazine lock screen function is turned on, the latest wallpaper to be displayed may be obtained through the resource library corresponding to the magazine lock screen function, and the latest wallpaper to be displayed (i.e., the third image) may be sent to the SystemUI application. And SystemUI, after receiving the latest wallpaper to be displayed, the application sends the latest wallpaper to be displayed to the screen-locking wallpaper layer. In addition, systemUI applications also need to set the display state of the lock wallpaper layer of the lock interface to a second display state (i.e., opaque display), where the display state of the desktop wallpaper layer is invisible.
After receiving the user operation, systemUI applications may obtain the lock screen wallpaper layer and the desktop wallpaper layer in response to the user operation, and synthesize the lock screen wallpaper layer and the desktop wallpaper layer through surfaceflinger, and display a lock screen interface (i.e., a fourth lock screen interface), where the lock screen wallpaper layer displays a third image. When the fourth lock screen interface is displayed, the display state of the lock screen wallpaper layer is the second display state (namely, opaque display), and the display state of the desktop wallpaper layer is invisible.
In step 610, in the case that it is determined that the magazine lock screen function is not turned on, systemUI application determines again whether the status bit of the settings database is the target identification field.
As can be seen in connection with step 603, when the magazine lock screen function is not on, the lock screen wallpaper and the desktop wallpaper may be the same or different. In conjunction with step 607, it is known that, before detecting the screen-off operation, the user may set the wallpaper, and since the status bit of the settings database is updated when the user changes the wallpaper or theme, the SystemUI application needs to determine whether the screen-off wallpaper and the desktop wallpaper are the same again through the status bit of the settings database if it is determined that the magazine screen-locking function is not opened.
It will be appreciated that steps 609 and 610 are side-by-side schemes, and that step 610 is not performed when step 609 is performed. When step 610 is performed, step 609 is not performed.
In step 611, when it is determined that the status bit of the settings database is the target identification field, systemUI sets the display status of the lock wallpaper layer to the first display status, and the display status of the desktop wallpaper layer is the target display status.
Wherein the first display state is transparent display. The target display state is a visual display.
And when the status bit of the settingdatabase is the target identification field, the screen locking wallpaper is the same as the desktop wallpaper. In combination with step 601, it can be known that, in the case that the lock wallpaper and the desktop wallpaper are the same, the lock wallpaper may be displayed by using the desktop wallpaper.
By way of example, with desktop wallpaper, the process of displaying the lock wallpaper may be to set the display state of the lock wallpaper (i.e., the processed first image) of the lock wallpaper layer display to a first display state (i.e., transparent display) and to set the display state of the desktop wallpaper (i.e., the first image) of the desktop wallpaper layer display to a target display state (i.e., visible display) visible display.
Setting the display state of the screen-locking wallpaper displayed by the screen-locking wallpaper layer to the first display state may be SystemUI application implementation by a backdrop view. Setvisibility (INVISIBAL) method, and setting the display state of the desktop wallpaper displayed by the desktop wallpaper layer to the target display state may be SystemUI application implementation by an imagewall view. Setvisibility (INVISIBAL) method. Wherein INVISIBLE is the parameter of the transfer.
The display state of the screen locking wallpaper is set to be transparent display, and the visible state of the desktop wallpaper is set to be visible, so that the desktop wallpaper can be displayed on the screen locking interface in a transparent mode. Because the screen locking wallpaper is the wallpaper to be displayed after being processed, the occupied memory of the screen locking wallpaper is greatly reduced. Moreover, the lock screen wallpaper is displayed in a transparent mode, a user cannot see the lock screen wallpaper, only the desktop wallpaper can be seen, and the arrangement does not cause any adverse effect on the use experience of the user.
Fig. 10 illustrates a detailed process for setting a lock screen when an off-screen event is detected by an electronic device.
Referring to fig. 10 and step 607, after the electronic device enters a low power state, the power manager may invoke updatePowerState a method to update the power state of the electronic device, e.g., update the power state of the electronic device from an awake state to a sleep state, and issue a sleep event notification in the form of a broadcast.
When the window management service receives the sleep event notification, in response to the sleep event notification, a method screenTurnedOff is invoked, the display is turned off, and a display off notification is sent to the SystemUI application. SystemUI the application receives the display off notification and, in response to the display off notification, invokes onScreenTurnedOff a method to handle the logic of the display off.
SystemUI applications include a lock view intermediary, a lock update monitor, a background view (BackDropView), a controller component (ScreenBrightenViewController), a screen brightness view (ScreenBrightenView), and a magazine style lock view component (MagazineView).
The lock view intermediary is used for coordinating lock view behaviors. After the onScreenTurnedOff () method execution is completed, the lock view broker call notifyScreenTurnedOff () notifies other system components that the screen has been closed.
The lock update monitor is configured to monitor for updates of the lock state and to respond to a screen shutdown event. The lock screen update monitor may call dispatchScreenTurnedoff a method for distributing screen close events to which other listeners or components respond, and may call handleScreenTurnedOff () specific logic to handle screen close.
The background view is used to display the lock screen background. The background view may call the lockicon. Setscreen on (false) method and pass false as a parameter to set the state of the lock screen icon. The background view may also determine whether to set a display state of a lock wallpaper layer of the lock interface to a first display state based on aspects of the present disclosure.
The controller component is used to manage screen brightness or animation effects associated with screen lighting. The controller component may invoke stopAnimation (INVISIBLE) to stop the current on-screen animated start drawing and set the animated object to invisible.
The screen brightness view is used to process views related to screen brightness adjustment or screen lighting effects. The screen brightness view may call stopAnimation () and setVisibility (INVISIBLE) methods and pass INVISIBLE as parameters to stop the animation effect and again set the visibility of the view to invisible.
The magazine style lock screen view component may call setVisibility (INVISIBLE) and updateMaskAlpha (0 f) methods to reset the visibility of the view to invisible, update the transparency of the mask layer to 0, and make it completely transparent.
When the window management service monitors that the electronic device is about to complete the sleep process (i.e., finishedGoingToSleep), the window management service sends a sleep completion notification to the SystemUI application. SystemUI the application receives the sleep completion notification and, in response to the sleep completion notification, invokes onFinishedGoingToSleep () method, triggering the subsequent lock screen logic.
In the subsequent screen locking logic, the screen locking view intermediary is further configured to determine whether to set the display of the desktop wallpaper layer of the screen locking interface to a target display state. The lock view intermediary may also call dokeyguardLocked a method to set the lock state or update the lock interface, and call showLocked a method to display the lock interface to ensure that the user sees the lock when the device wakes up. And calling handleShow a () method and processing a method of the lock screen interface display logic to display elements such as update time, date, notification and the like in the lock screen interface.
In step 612, in the case that it is determined that the status bit of the settings database is not the target identification field, systemUI applies that the display state of the lock wallpaper layer of the lock interface is set to be the second display state.
Wherein the second display state is an opaque display.
Referring to the foregoing, when the status bit of the settings database is not the target identification field, it is indicated that the lock wallpaper is different from the desktop wallpaper. Under the condition that the screen locking wallpaper and the desktop wallpaper are different, the screen locking wallpaper and the desktop wallpaper cannot be replaced, and the screen locking wallpaper needs to be normally loaded and normally displayed. Since SystemUI application has set the lock wallpaper in advance, in the case that it is determined that the status bit of the settings database is not the target identification field, the display state of the lock wallpaper layer of the lock interface is set to be the second display state (i.e., opaque display), and the display state of the desktop wallpaper layer of the lock interface is invisible display.
It will be appreciated that steps 611 and 612 are side-by-side schemes, and that step 612 is not performed when step 611 is performed. When step 612 is performed, step 611 is not performed.
Step 613, displaying the lock screen interface when the electronic device is in the second state.
The second state is a state that the electronic equipment displays a screen locking interface.
In some scenarios, the electronic device is in a second state in response to a user operation. And displaying a screen locking interface when the electronic equipment is in the second state. The user operation may be an operation that the user presses a power key, or an operation that the user lifts up a display screen of the electronic device, which is not limited in this disclosure.
For example, the display state of the lock wallpaper layer in the lock interface is a first display state (i.e., transparent display), and the display state of the desktop wallpaper layer is a target display state (i.e., visible display).
For another example, the display state of the lock wallpaper layer in the lock interface is a second display state (i.e., opaque display) and the display state of the desktop wallpaper layer is invisible display.
In some examples, the process of displaying the lock screen interface may be where the SystemUI application sends an interface composition request to surfaceflinger when the electronic device is in the second state, receives the interface composition request, and synthesizes the lock screen wallpaper layer and the desktop wallpaper layer in response to the interface composition request, surfaceflinger, generating the lock screen interface. The interface synthesis request is used for requesting surfaceflinger to synthesize the screen locking wallpaper layer and the desktop wallpaper layer, and generating a screen locking interface. The interface composition request includes wallpaper to be displayed.
In connection with step 611, in the case where it is determined that the status bit of the settings database is the target identification field, systemUI apply to set the display status of the lock wallpaper layer to the first display status, and the display status of the desktop wallpaper layer to the target display status. That is, in the case where the lock wallpaper and the desktop wallpaper are the same, systemUI application may utilize surfaceflinger to generate a lock interface (i.e., a second lock interface) in which the display state of the lock wallpaper layer is the first display state (i.e., transparent display). The display state of the desktop wallpaper layer in the second lock screen interface is a target display state (i.e., a visual display). The data size of the screen locking wallpaper (i.e. the first image) displayed by the screen locking wallpaper layer is a second numerical value. Therefore, when the screen locking interface is displayed on the electronic equipment, the screen locking interface can be transparent to the desktop wallpaper, and therefore the use experience of a user is not affected.
In connection with step 612, systemUI application sets the display state of the lock wallpaper layer to the second display state if it is determined that the status bit of the settings database is not the target identification field. That is, in the case where the lock wallpaper and the desktop wallpaper are not the same, systemUI application may utilize surfaceflinger to generate a lock interface (i.e., a first lock interface) in which the display state of the lock wallpaper layer is the second display state (i.e., the opaque display). The display state of the desktop wallpaper layer in the first screen locking interface is invisible. The data size of the screen locking wallpaper (i.e. the first image) displayed by the screen locking wallpaper layer is a first numerical value. Wherein the first value is greater than the second value.
In some examples, the lock screen interface (i.e., the third lock screen interface) is displayed when the electronic device is in the third state.
The third state may be any state of pressing a power key to trigger the electronic device to unlock a screen, unlock failure, unlock multiple times of failure, and start the electronic device when the screen is turned off, and inputting a screen locking password.
In some scenarios, the electronic device is in a third state in response to a user unlocking operation. And displaying a screen locking interface when the electronic equipment is in the second state.
For example, when the status bit of the settings database is determined to be the target identification field, in the third state of the electronic device, the process of displaying the screen-locking interface (i.e., the third screen-locking interface) may be that, in the third state of the electronic device, systemUI the application sends an interface composition request to surfaceflinger, receives the interface composition request, and synthesizes the screen-locking wallpaper layer and the desktop wallpaper layer in response to the interface composition request, surfaceflinger, to generate the third screen-locking interface. The interface synthesis request is used for requesting surfaceflinger to synthesize the screen-locking wallpaper layer and the desktop wallpaper layer, and generating a third screen-locking interface.
In addition, in a third state of the electronic device, systemUI application sets the display state of the lock wallpaper layer to a second display state (i.e., opaque display), the display state of the desktop wallpaper layer being invisible. The data size of the screen locking wallpaper (i.e. the first image) displayed by the screen locking wallpaper layer in the third screen locking interface is a second numerical value.
Generally, the third screen locking interface displays the screen locking wallpaper with fuzzy processing for the user, and the fuzzy processing can protect the privacy of the user to a certain extent.
The process of the electronic device being in the third state may be, for example, receiving an unlocking operation by a user, and the electronic device being in the third state. The unlocking operation may be any one of a sliding operation, a password input operation, or a fingerprint identification operation.
In the disclosure, when the electronic device is in the third state, the data size of the first image displayed by the lock wallpaper layer of the third lock interface is a second numerical value. The first image is a downsampled image. By the mode, occupation of the screen locking wallpaper to system resources can be effectively reduced, and running efficiency of equipment can be improved. In addition, the processed first image can still keep a good visual effect on the screen locking interface, and cannot be too rough or distorted due to the reduction of resolution. The processing mode meets the personalized requirements of the user, gives consideration to the performance of the electronic equipment, and can bring more comfortable use experience for the user.
It should be understood that the steps in the above-described method embodiments provided by the present disclosure may be accomplished by instructions in the form of integrated logic circuits of hardware in a processor or software. The steps of a method disclosed in connection with the embodiments of the present disclosure may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution.
In one example, the units in the above apparatus may be one or more integrated circuits configured to implement the above methods, e.g., one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of at least two of these integrated circuit forms.
For another example, when the units in the apparatus may be implemented in the form of a scheduler of processing elements, the processing elements may be general-purpose processors, such as CPUs or other processors that may invoke programs. For another example, the units may be integrated together and implemented in the form of a system on chip SOC.
In one implementation, the above means for implementing each corresponding step in the above method may be implemented in the form of a processing element scheduler. For example, the apparatus may comprise a processing element and a storage element, the processing element invoking a program stored in the storage element to perform the method of the above method embodiments. The memory element may be a memory element on the same chip as the processing element, i.e. an on-chip memory element.
In another implementation, the program for performing the above method may be on a memory element on a different chip than the processing element, i.e. an off-chip memory element. At this point, the processing element invokes or loads a program from the off-chip storage element onto the on-chip storage element to invoke and execute the method of the above method embodiment.
For example, an apparatus, such as an electronic device, may include a processor, a memory for storing instructions executable by the processor. The processor is configured to, when executing the above-described instructions, cause the electronic device to implement the data processing method of the previous embodiment. The memory may be located within the electronic device or may be located external to the electronic device. And the processor includes one or more.
In yet another implementation, the unit of the apparatus implementing each step in the above method may be configured as one or more processing elements, which may be disposed on the electronic device corresponding to the above, where the processing elements may be integrated circuits, for example, one or more ASICs, or one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits may be integrated together to form a chip.
For example, embodiments of the present disclosure also provide a chip, as shown in fig. 11, that includes at least one processor 1101 and at least one interface circuit 1102. The processor 1101 and interface circuit 1102 may be interconnected by wires. For example, interface circuit 1102 may be used to receive signals from other devices. For another example, the interface circuit 1102 may be used to send signals to other devices (e.g., the processor 1101).
For example, the interface circuit 1102 may read instructions stored in a memory in the device and send the instructions to the processor 1101. The instructions, when executed by the processor 1101, may cause an electronic device (e.g., the electronic device 200 shown in fig. 2) to perform the various steps of the embodiments described above. Of course, the system-on-chip may also include other discrete devices, as embodiments of the disclosure are not specifically limited in this regard.
Embodiments of the present disclosure also provide a computer readable storage medium having computer program instructions stored thereon. The computer program instructions, when executed by an electronic device, enable the electronic device to implement the data processing method as described above.
Embodiments of the present disclosure also provide a computer program product comprising computer instructions for execution by an electronic device as described above, which when executed in the electronic device, cause the electronic device to implement a data processing method as described above. From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above.
In the several embodiments provided in the present disclosure, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of modules or units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and the parts shown as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present disclosure may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present disclosure may be embodied in the form of a software product, such as a program, in essence or as a part of the technical solutions contributing to the prior art or all or part of the technical solutions. The software product is stored in a program product, such as a computer readable storage medium, comprising instructions for causing a terminal device (which may be a single-chip microcomputer, chip or the like) or processor (processor) to perform all or part of the steps of the methods of the various embodiments of the disclosure. The storage medium includes various media capable of storing program codes such as a U disk, a mobile hard disk, a ROM, a RAM, a magnetic disk or an optical disk.
For example, embodiments of the present disclosure may also provide a computer-readable storage medium having computer program instructions stored thereon. The computer program instructions, when executed by an electronic device, cause the electronic device to implement a data processing method as in the method embodiments described above.
The foregoing is merely a specific embodiment of the disclosure, but the protection scope of the disclosure is not limited thereto, and any changes or substitutions within the technical scope of the disclosure should be covered in the protection scope of the disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.