Display method, electronic device, storage medium and program product

Abstract

The invention relates to the technical field of computers, in particular to a display method, electronic equipment, a storage medium and a program product. The display method provided by the invention is applied to the electronic equipment, and when different interfaces of the first application are displayed, the electronic equipment can adjust the screen refresh rate of the screen based on the display content in the current display interface. Therefore, the electronic equipment can avoid the problems of overhigh equipment power consumption and the like caused by overhigh screen refresh rate setting in a part of display interfaces, and the problems of picture fluency reduction, picture jamming and the like caused by overlow screen refresh rate setting in a part of display interfaces.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a display method, electronic device, storage medium, and program product. Background Technology

[0002] Currently, screen refresh rate control strategies on electronic devices typically use the application name or activity name to uniformly set the screen refresh rate for the same application or activity, thus adjusting the screen refresh rate. For example, since video application A primarily displays video content, user interaction may be relatively infrequent, resulting in a lower demand for screen refresh rate. Therefore, the electronic device will set the screen refresh rate for video application A to a low rate (e.g., 30Hz or 60Hz) based on the application name.

[0003] However, in addition to playing videos, video applications also involve user interaction, such as swiping to switch videos or swiping to view comments on videos. If the screen refresh rate is too low when users are swiping to switch videos or view comments, problems such as screen stuttering may occur, resulting in a poor user experience. Summary of the Invention

[0004] To address the aforementioned technical problems, embodiments of this application provide a display method, an electronic device, a storage medium, and a program product.

[0005] In a first aspect, embodiments of this application provide a display method applied to an electronic device. The method includes: displaying a first display interface of a first application on the screen of the electronic device at a first screen refresh rate, the first display interface including first display content; and displaying a second display interface of the first application on the screen of the electronic device at a second screen refresh rate, the second display interface including second display content; wherein the first screen refresh rate is less than the second screen refresh rate, and the predicted interaction frequency of the second display content is higher than the predicted interaction frequency of the first display content.

[0006] Based on the above solution, when the screen of an electronic device displays different display interfaces of a first application, the electronic device can adjust the screen to a first screen refresh rate based on the predicted interaction frequency of the first display content in the first display interface; similarly, the electronic device can adjust the screen to a second screen refresh rate based on the predicted interaction frequency of the second display content in the second display interface. In this way, the electronic device can adjust the screen refresh rate according to the display content of the same application's display interfaces, avoiding problems such as excessive power consumption due to excessively high screen refresh rates in some display interfaces, and reduced screen smoothness and stuttering due to excessively low screen refresh rates in some display interfaces.

[0007] For example, the first application could be a video application, the first display interface could be a video playback interface, and the second display interface could be an interface that displays both the video and the comment section simultaneously. In this way, when the electronic device displays the interface of the first application, it can adjust the screen refresh rate according to the content displayed on the current display interface. Furthermore, it can adapt to changes in the content displayed on the current display interface, avoiding problems such as excessive power consumption due to an excessively high screen refresh rate, or reduced smoothness and stuttering due to an excessively low screen refresh rate.

[0008] In one possible implementation of the first aspect, the screen of the electronic device displays a first display interface of a first application at a first screen refresh rate, including: detecting a first instruction from a user to open the first display interface; determining that the first display content corresponds to a first display scene; and displaying the first display interface at the first screen refresh rate based on the first display scene.

[0009] Electronic devices determine the corresponding first display scene based on the first display content. When the predicted interaction frequency of the first display content is relatively low, it can be determined that the screen refresh rate required for the first display scene is relatively low. For example, when the first display content is video content, the user may not frequently swipe to switch videos, that is, the predicted interaction frequency is low, and it can be determined that the screen refresh rate required for the first display scene is low, which may be 30Hz or 60Hz.

[0010] In one possible implementation of the first aspect, determining that the first display content corresponds to the first display scene includes: determining that the target view in the first display content satisfies the first scene condition, and determining that the first display content corresponds to the first display scene.

[0011] It can be understood that the target view is a view that is effective for scene identification. For example, when the first application is a video application, the target view can be a video view, and the display scene in the video application can be distinguished solely by the information in the target view.

[0012] In one possible implementation of the first aspect, the above display method further includes: obtaining all view information in the first display interface, the view information including view type; and determining, based on the view type, that the first display content includes a target view.

[0013] It is understandable that the first display interface includes multiple views, and the view information includes the view type, which may include video views, text views, etc.

[0014] In one possible implementation of the first aspect, the target view is a video class view.

[0015] In one possible implementation of the first aspect, the first scene conditions include first video scene conditions, which include: the visibility of all nodes in the target view and its parent view is visible; the width and height of all nodes in the target view and its parent view occupy a proportion greater than or equal to a first value of the width and height of the electronic device screen, and the width of the target view occupies a proportion greater than or equal to a second value of the width of the electronic device screen, or the height of the target view occupies a proportion greater than or equal to a second value of the height of the electronic device screen, wherein the second value is greater than the first value; and the center point of the target view is located within a preset range of the center point of the electronic device screen.

[0016] In one possible implementation of the first aspect, the first scene condition further includes a second video scene condition, which includes: the visibility of the target view is visible; the proportion of the width and height of the target view to the width and height of the electronic device screen is greater than or equal to a first value, and the proportion of the width of the target view to the width of the electronic device screen is greater than or equal to a second value, or the proportion of the height of the target view to the height of the electronic device screen is greater than or equal to a second value; and at least two target view positions change simultaneously.

[0017] In one possible implementation of the first aspect, the screen of the electronic device displays a second display interface of the first application at a second screen refresh rate, including: detecting a second instruction from a user to open the second display interface; determining that the second display content corresponds to a second display scene; and displaying the second display interface at the second screen refresh rate based on the second display scene.

[0018] Electronic devices determine the corresponding second display scene based on the second display content. When the predicted interaction frequency of the second display content is relatively high, it can be determined that the screen refresh rate required for the second display scene is relatively high. For example, when the second display content is text-based, the user may frequently swipe the text-based content, which means the predicted interaction frequency is high, and it can be determined that the screen refresh rate required for the second display scene is relatively high, such as 90Hz or 120Hz.

[0019] In one possible implementation of the first aspect, determining that the second display content corresponds to the second display scenario includes: determining that the second display content does not include the target view, or determining that the target view in the second display content does not meet the first scenario condition, and determining that the second display content corresponds to the second display scenario.

[0020] In one possible implementation of the first aspect, the first application is a video application.

[0021] In one possible implementation of the first aspect, the first display interface is at least one of a short video playback interface, a live streaming interface, and a full-screen video playback interface.

[0022] In one possible implementation of the first aspect, the second display interface is at least one of the following: an interface that displays both video and comment sections simultaneously, a user homepage interface, an online store interface, and a search results interface.

[0023] Secondly, embodiments of this application provide an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements any of the possible implementations of the first aspect described above.

[0024] Thirdly, embodiments of this application provide a storage medium storing instructions that, when executed on an electronic device, cause the electronic device to perform any of the possible implementations of the display method described in the first aspect above.

[0025] Fourthly, embodiments of this application provide a program product that includes computer instructions, which, when executed by an electronic device, cause the electronic device to perform any of the possible implementations of the first aspect described above. Attached Figure Description

[0026] Figure 1 According to some embodiments of this application, a schematic diagram of a view in the active page of an application is shown;

[0027] Figure 2A According to some embodiments of this application, a schematic diagram of a video playback scenario is shown;

[0028] Figure 2B According to some embodiments of this application, a schematic diagram of a comment section sliding scenario is shown;

[0029] Figure 3 According to some embodiments of this application, a schematic diagram of the center point range of a target view is shown;

[0030] Figure 4 According to some embodiments of this application, a schematic diagram of the hardware structure of an electronic device is shown;

[0031] Figure 5 According to some embodiments of this application, a schematic diagram of a display system architecture is shown;

[0032] Figure 6 According to some embodiments of this application, another schematic diagram of a display system architecture is shown;

[0033] Figure 7 According to some embodiments of this application, a schematic diagram of an application display scenario is shown;

[0034] Figure 8 According to some embodiments of this application, a flowchart of a display method is shown;

[0035] Figure 9 According to some embodiments of this application, a flowchart of a method for determining a target view is shown;

[0036] Figure 10 According to some embodiments of this application, a flowchart for determining the triggering time of scene recognition is shown;

[0037] Figure 11 According to some embodiments of this application, another flowchart for determining the scene recognition triggering timing is shown;

[0038] Figure 12 According to some embodiments of this application, a flowchart of a scene recognition method is shown. Detailed Implementation

[0039] The illustrative embodiments of this application include, but are not limited to, a display method, an electronic device, a storage medium, and a program product.

[0040] To better understand the solution of this application, the relevant terms in the field will be explained first.

[0041] (1) Activity Page

[0042] An activity page is a core component of an application, providing the user interface and interaction. Each activity page corresponds to a window / page on a screen, and users can switch between different activity pages to perform different functions.

[0043] (2) View

[0044] A view is the basic element contained within an active page, representing the fundamental building blocks of the user interface. A view occupies a rectangular area on the screen and is responsible for interface rendering and event handling; controls can be defined on a view. There are two types of relationships between views: inheritance and non-inheritance. Inheritance means there is a parent-child relationship between views, and a view can only have one parent view, but a parent view can have multiple child views. In an active page, views are organized according to a hierarchical structure, such as... Figure 1 As shown, the parent view is in the child view Figure 1 And the next layer below subview 2.

[0045] In this application, the electronic device can be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, netbook, or other electronic device, and there is no limitation herein. For ease of description, the following will use video applications on mobile phones as an example.

[0046] As mentioned earlier, current screen refresh rate settings for applications do not consider the varying frequency of user interaction when the same application displays different content, thus requiring different screen refresh rates. For example, for video applications, such as short video apps, users interact less with the screen while watching videos; their predicted interaction frequency is low, hence the need for a lower screen refresh rate. However, when opening the video's comment section, users typically need to swipe through the displayed text or images, resulting in a higher predicted interaction frequency and thus a higher screen refresh rate.

[0047] In some embodiments, considering that certain applications contain content with a high predicted interaction frequency, the screen refresh rate for such applications (e.g., video applications) is set to a high refresh rate based on the application name. However, during the operation of video applications, since the electronic device screen needs to maintain a high refresh rate in various display scenarios of video applications, it may lead to problems such as excessive power consumption and rapid battery drain.

[0048] For example, for Figure 2A The video playback scenario shown primarily displays video content. When the screen refresh rate of the electronic device is between 30Hz and 60Hz (low refresh rate), the video playback is smooth and the image quality is highly realistic. Furthermore, the user's expected interaction frequency is low in this scenario, therefore the refresh rate requirement is relatively low. Setting a high refresh rate (e.g., 90Hz or 120Hz) for a video application named A would result in excessive power consumption and faster battery drain.

[0049] In some embodiments, considering that certain applications contain content with a predicted low interaction frequency, the screen refresh rate for such applications (e.g., video applications) is set to a low refresh rate (e.g., 30Hz or 60Hz) based on the application name. However, during the operation of such video applications, the electronic device screen may remain at a low refresh rate in various display scenarios, potentially leading to problems such as excessively low screen refresh rate and screen stuttering.

[0050] For example, for Figure 2B The illustrated comment section scrolling scenario primarily displays text or image content. Because this scenario likely involves a large number of user scrolling actions (i.e., a high predicted interaction frequency), a high refresh rate is required to ensure smooth display during user interaction. If a video application (application name A) has its screen refresh rate set to low, when a user opens the comment section A2 of a video on the recommendation page A1 and scrolls through it, issues such as excessively low refresh rate and screen stuttering may occur, resulting in a poor user experience.

[0051] It is understandable that video applications typically include multiple activity pages, such as a recommendation page, user homepage, search page, store page, and user login page. In some embodiments, the refresh rate can also be set based on the activity page name. However, an activity page may include multiple display scenarios; for example, for a recommendation page, it may include... Figure 2A The video playback scene shown and Figure 2B The comment section scrolling scenario shown illustrates the different refresh rate requirements for these two display scenarios. Therefore, setting the screen refresh rate via the activity page name and setting the screen refresh rate via the application name, as described above, present the same technical challenges.

[0052] Therefore, this application provides a display method that can identify the display content of various applications on an electronic device and adjust the screen refresh rate in real time according to the different screen refresh rate requirements of the display content. For example, for the aforementioned video applications, if the display content has a low screen refresh rate requirement, such as mainly video content, and the user's predicted interaction frequency is low, then the video being played is displayed at a lower screen refresh rate; if the display content has a high screen refresh rate requirement, such as simultaneously displaying the video and the video comment section, and the user's predicted interaction frequency is high, then the video and the video comment section are displayed at a higher screen refresh rate.

[0053] In some embodiments, the screen of an electronic device displays a first display interface of a first application (e.g., a video application) at a first screen refresh rate, the first display interface including first display content; the screen of the electronic device displays a second display interface of the first application at a second screen refresh rate, the second display interface including second display content. The first screen refresh rate is less than the second screen refresh rate; the first screen refresh rate can be 30Hz or 60Hz, and the second screen refresh rate can be 90Hz or 120Hz. Furthermore, the predicted interaction frequency of the second display content is higher than the predicted interaction frequency of the first display content; the first display content can be video content, and the second display content can be text or image content.

[0054] It is understood that the first display interface can be at least one of a short video playback interface, a live streaming interface, or a full-screen video playback interface. The second display interface can be at least one of the following: an interface that displays both videos and comment sections simultaneously, a user homepage interface, an online store interface, or a search results interface.

[0055] In some embodiments, the currently displayed content can be determined, and then the current display scenario can be determined based on the currently displayed content. The screen refresh rate can then be determined according to the predicted interaction frequency corresponding to the displayed content in the current display scenario. Specifically, for display content with a relatively high predicted interaction frequency, it can be identified as a scenario requiring a higher screen refresh rate. For example, in the video application mentioned above, in the scenario where a video and a comment section are displayed simultaneously, the user may frequently swipe through the text or image content in the comment section, i.e., the predicted interaction frequency is high, and a higher screen refresh rate, such as 90Hz or 120Hz, can be determined. Conversely, for the video playback scenario mentioned above, the user may not frequently swipe to switch videos, i.e., the predicted interaction frequency is low, and a lower screen refresh rate, such as 30Hz or 60Hz, can be determined.

[0056] It is understood that, in the various embodiments of this application, the different scene divisions corresponding to the screen refresh rates required under different predicted interaction frequencies are not limited to the two display scenarios mentioned above. The display can be divided into the required number of display scenarios according to actual needs. For example, it can also be divided into three display scenarios, including video playback scenario, comment section scrolling scenario, live video playback, and product information display scenario (product information includes product list, product detail page, etc.) for video applications.

[0057] For live video playback and product information display scenarios, the application's displayed content includes video content (live video), text content, and image content (product information). In this scenario, users may scroll through the product list and view product detail pages. Because they need to stay and view text or image content, the frequency of user scrolling may be higher than the frequency of scrolling to switch videos, but lower than the frequency of scrolling through the comment section. Therefore, the predicted interaction frequency corresponding to the displayed content in this scenario is higher than in the video playback scenario but lower than in the comment section scrolling scenario. That is, the required screen refresh rate for this scenario is higher than in the video playback scenario but lower than in the comment section scrolling scenario, for example, it could be 70Hz or 80Hz.

[0058] It is understood that the display method provided in this application can be applied to various applications in electronic devices that have display content with different predicted interaction frequencies, such as video applications, including short video applications, online meeting applications, and online teaching applications. For example, online meeting applications may have camera footage and comment section footage. The predicted interaction frequency of the camera footage is usually lower than that of the comment section footage. Therefore, in scenarios where the camera footage and the comment section are displayed simultaneously, the screen refresh rate can be set to a high refresh rate. Online teaching applications may have camera footage and courseware display footage. The predicted interaction frequency of the camera footage is usually lower than that of the courseware display footage. Therefore, in scenarios where the camera footage and the courseware are displayed simultaneously, the screen refresh rate can be set to a high refresh rate. This application does not limit the specific applications.

[0059] For ease of description, the following uses a short video application as an example to illustrate the display method provided in this application's embodiments, dividing the display scenarios in short video applications into video scenarios and non-video scenarios. The video scenario can be... Figure 2A The video playback scenario shown can be replaced by a non-video scenario. Figure 2B The comment section sliding scene shown.

[0060] In some embodiments, the current display scene can be determined based on the currently displayed content of the short video application. Since the predicted interaction frequency differs between video and non-video scenes, the required screen refresh rate also differs. Therefore, the screen refresh rate corresponding to the currently displayed content can be determined based on the current display scene. This avoids problems such as excessive power consumption due to excessively high screen refresh rates in some display scenes, and reduced smoothness and stuttering due to excessively low screen refresh rates in others, enabling the device to achieve better performance and improving the user experience.

[0061] In some embodiments, scene recognition can be achieved by identifying the target view in the current display interface of the short video application, wherein the target view can be a video view related to video content. It is understood that the predicted interaction frequency corresponding to the target view is relatively low.

[0062] Then, the current display scene is determined based on relevant information about the target view in the short video application (including the target view's visibility, offset, and position). For example, based on the relevant information of the target view, it can be determined whether the target view meets the conditions for a video scene. If it meets the first scene condition, it means that the currently displayed content is mainly video content, and the corresponding predicted interaction frequency is low, thus determining the current display scene as a video scene. If it does not meet the first scene condition, it means that the currently displayed content is mainly text or image content, and the corresponding predicted interaction frequency is high, thus determining the current display scene as a non-video scene.

[0063] It is understandable that in electronic device systems (such as Android systems), drawing the display interface usually involves a variety of information. In electronic device systems, different types of views are set for different display content. For example, the view type related to text content is TextView, the view type related to image content is ImageView, and the view type related to video content is SurfaceView or TextureView.

[0064] For example, when drawing the display interface corresponding to the recommendation page in short video application A, the target view related to video content in the recommendation page is determined; then, the visibility, offset and position of the target view are judged. When the visibility, offset and position of the target view meet the first scene condition, it means that the current display content mainly includes video content, the corresponding predicted interaction frequency is low, and the current display scene is determined to be a video scene.

[0065] It's understandable that the total number of views displayed on the recommendation page is large, perhaps exceeding 100. The goal is to identify the view that is effective for scene recognition, i.e., the target view. In short video applications, the target view can be a video-related view; the difference between video and non-video scenes can be distinguished solely by the target view information.

[0066] The following is a brief introduction to the conditions of the first scenario.

[0067] In some embodiments, the target view is determined based on the type of view (i.e., the type of displayed content) in the short video application, the target view and its parent node are marked, and the target view is recorded in the monitoring list. It should be understood that the display interface corresponding to the activity page typically includes a view root, which contains all views in the display interface, and this view root corresponds to a monitoring list.

[0068] It can be understood that the parent node is the node of the parent view of the target view, as shown in the reference. Figure 2A The target view A11 can be the entire video frame, and the parent view can be the background below the target view A11 and all controls. When swiping to switch videos, both the absolute position and the position of the target view A11 relative to its parent view will change. When swiping to switch activity pages, such as swiping from the recommendation page to the store page, the absolute position of the target view A11 will change, but its position relative to its parent view will not change. Therefore, it is necessary to mark the target view A11 and its parent nodes.

[0069] In some embodiments, the first scene condition includes a first video scene condition and a second video scene condition. The first video scene condition corresponds to the video playback scene in the video scene, including but not limited to the following:

[0070] (1) The target view and all its parent nodes are visible.

[0071] It's understandable that when the target view and all its parent nodes are visible, it indicates that a video is currently playing. For example, for Figure 2A In the video playback scenario shown, the target view A11 and all its parent nodes are visible. However, when swiping right on the recommendation page A1 to switch to the e-commerce page, the target view A11 and all its parent nodes become invisible.

[0072] (2) The proportions of the width and height of the target view and all its parent nodes relative to the width and height of the electronic device screen are both greater than or equal to the first value, and the proportion of the width of the target view relative to the width of the electronic device screen is greater than or equal to the second value, or the proportion of the height of the target view relative to the height of the electronic device screen is greater than or equal to the second value. The second value is greater than the first value; the first value can be 20%, and the second value can be 95%.

[0073] It's understandable that even when the target view and all its parent nodes are visible, it's still necessary to determine the target view's position and size. Since videos include both landscape and portrait videos, in a video playback scenario, the width of a view corresponding to a landscape video can reach 95% of the screen width, and the height of a view corresponding to a portrait video can reach 95% of the screen height.

[0074] (3) The center point of the target view is located within a preset range of the center point of the electronic device screen. For example, the preset range can be a rectangular area from the upper left point (e.g., 30% of the screen width and 30% of the screen height) to the lower right point of the electronic device screen. Wherein, if a coordinate system is established with the upper left vertex o of the screen as the origin, such as... Figure 3 As shown, the top left point can be point M, with coordinates of (30% of screen width, -30% of screen height), and the bottom right point can be point N, with coordinates of (70% of screen width, -70% of screen height).

[0075] Understandable, for Figure 2B In the sliding scene of the comment section shown, the center point P of the target view A11 does not meet condition (3). Therefore, it can be distinguished by the above first video scene conditions. Figure 2A The video playback scene shown and Figure 2BThe comment section sliding scene is shown. When the relevant information of the target view simultaneously satisfies all the conditions of the first video scene (i.e., condition (1), condition (2) and condition (3)), it indicates that the currently displayed content mainly includes video content, the corresponding predicted interaction frequency is low, and the current display scene is determined to be a video playback scene.

[0076] The second video scene conditions correspond to video sliding transition scenes, including but not limited to the following:

[0077] (4) The target view is visible.

[0078] It is understandable that in video swiping and switching scenarios, the visibility of the parent node of the target view will not change, so it is only necessary to determine the visibility of the target view.

[0079] (5) The proportion of the width and height of the target view to the width and height of the electronic device screen is greater than or equal to the first value, and the proportion of the width of the target view to the width of the electronic device screen is greater than or equal to the second value or the proportion of the height of the target view to the height of the electronic device screen is greater than or equal to the second value.

[0080] It's understandable that in video swiping transition scenarios, the size of the parent node of the target view will not change, so it's only necessary to determine the size of the target view.

[0081] (6) At least two target view positions change simultaneously.

[0082] It is understandable that in a video sliding transition scenario, during the transition, both the target view corresponding to the current video content and the target view corresponding to the next video content are partially displayed on the display interface. Therefore, the positions of at least two target views will change simultaneously. When the relevant information of the target view satisfies all the conditions in the second video scenario (i.e., conditions (4), (5), and (6)), it indicates that the currently displayed content mainly includes video content, and the corresponding predicted interaction frequency is low. Therefore, the current display scenario is determined to be a video sliding transition scenario.

[0083] It is understood that for different display scenarios, the first scenario condition may only include the first video scenario condition, or only the second video scenario condition, or may include other scenario conditions. It can be set according to actual needs, and this application does not limit it.

[0084] In some embodiments, after determining the current display scene, the screen refresh rate can be adjusted based on the scene recognition result. When the scene recognition result is "the current display scene is a video scene," the current view root state is video playback (HAS_VIDEO) or video switching (VIDEO_MOVING), and the screen refresh rate can be adjusted to a low refresh rate. When the scene recognition result is "the current display scene is a non-video scene," the current view root state is no video (NO_VIDOE), and the screen refresh rate can be adjusted to a high refresh rate.

[0085] In some embodiments, the scene recognition result also includes the disappearance of the current view root. When the scene recognition result is "the current view root has disappeared", the current view root state is CANCEL_VIEWROOT, and the screen refresh rate is determined based on the previous view root.

[0086] It's understandable that the view root name and its corresponding state are recorded in a data set (map). When adjusting the screen refresh rate, the current screen refresh rate is determined based on the state of the last view root (i.e., the current view root). If the current view root state is CANCEL_VIEWROOT, the view root is removed from the map, and the previous view root is the last view root sent in the map.

[0087] It's understandable that the disappearance of the current view root indicates a change in the displayed interface, meaning the interface corresponding to the active page disappears. For example, refer to... Figure 2A When you tap the search bar in the upper right corner, the current display switches to the search interface, and the relevant interfaces on the activity page are no longer displayed. The disappearance of the current view root can also indicate an application switch, such as directly exiting the application and returning to the phone's home screen.

[0088] Thus, this application can adjust the screen refresh rate of electronic devices in real time based on the currently displayed content.

[0089] Before detailing the display method of the embodiments of this application, the electronic devices mentioned in the embodiments of this application will first be described. Taking a mobile phone as an example, the hardware structure diagram of a mobile phone 100 that can implement the method of this application is described below.

[0090] like Figure 4 As shown, the mobile phone 100 may include a processor 110, a power module 140, a memory 180, a mobile communication module 120, a wireless communication module 130, a sensor module 190, an audio module 150, a camera 170, an interface module 160, buttons 101, and a display 102, etc.

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

[0092] Processor 110 may include one or more processing units, such as a central processing unit (CPU), graphics processing unit (GPU), digital signal processor (DSP), microprocessor (MCU), artificial intelligence (AI) processor, or field programmable gate array (FPGA) processing module or circuit. Different processing units may be independent devices or integrated into one or more processors. Processor 110 may include a storage unit for storing instructions and data. In some embodiments of this application, processor 110 may be used to execute the display methods mentioned in this application. The storage unit may store relevant instructions for executing the display methods mentioned in this application.

[0093] The power module 140 may include a power supply, a power management component, etc. The power supply may be a battery. The power management component is used to manage the charging of the power supply and the power supply to other modules.

[0094] The mobile communication module 120 may include, but is not limited to, antennas, power amplifiers, filters, low noise amplifiers (LNAs), etc.

[0095] The mobile communication module 120 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the mobile phone 100. In some embodiments, the mobile communication module 120 and the wireless communication module 130 of the mobile phone 100 may also be located in the same module.

[0096] The display 102 is used to display human-computer interaction interfaces, images, videos, etc. In some embodiments of this application, users can perform operations such as swiping to switch videos and swiping the comment section through the display 102.

[0097] Audio module 150 is used to convert digital audio information into analog audio signal output, or to convert analog audio input into digital audio signal. Audio module 150 can also be used for encoding and decoding audio signals. Camera 170 is used to capture still images or video.

[0098] It should be noted that the hardware functional components of the mobile phone 100 described above can be modified according to user needs. It is understood that the specific embodiments described above are only one specific implementation of the electronic device. Other ways to implement the embodiments of this application are also within the scope of protection of this application, and will not be described in detail here.

[0099] The display method provided in the embodiments of this application will be described below with reference to the accompanying drawings.

[0100] First, combined Figures 5-7 The display system in the embodiments of this application will be described. Figure 5 A schematic diagram of a display system architecture is shown. Figure 6 Another schematic diagram of a display system architecture is shown. For example... Figure 5 As shown, the system includes a view basic capability implementation module (also known as the ViewRootImpl module) 501, a view module 502, a scene recognition module (also known as the view information processing (VrrViewInfoHandler) module) 503, and a refresh rate control module (also known as the predictive image rendering (Advances Graphic Projects, AGP) module) 504. Among them,

[0101] The View Basic Capability Implementation Module 501 is responsible for triggering interface drawing (including view drawing), creating the ViewRootImpl class corresponding to the active page interface drawing, and triggering the Scene Recognition Module 503 to calculate target view information and recognize the scene.

[0102] The view module 502 stores relevant information about the view, is responsible for monitoring changes in the view's position and visibility, and transmits the view information when needed by the scene recognition module 503.

[0103] The scene recognition module 503 is responsible for creating the VrrViewInfoHandler class corresponding to the scene recognition, receiving the target view information and calculating and judging information such as position, offset and visibility, obtaining the scene recognition result, and passing the view root state corresponding to the scene recognition result to the refresh rate control module 504.

[0104] The refresh rate control module 504 is responsible for receiving the scene recognition result from the scene recognition module 503 and controlling the screen refresh rate according to the scene recognition result.

[0105] In some embodiments, after the application is opened on an electronic device, the application process creates an active page in the main thread. Once the active page starts, view drawing is performed in the interface display (Resume) process, creating a ViewRootImpl class. The interface corresponding to an active page typically includes a view root, which contains multiple views. The view module 502 includes all information about the views in the view root, such as... Figure 6 As shown, it may include view Figure 11 ,See Figure 12 Information such as View 13, View 21, View 22, and View 23; the View Basic Capability Implementation Module 501 needs to be associated with multiple views to trigger the interface drawing process.

[0106] It's understandable that the UI rendering process of an activity page typically includes a ViewRootImpl class, a view root, and a VrrViewInfoHandler class. For example, refer to... Figure 6 ,exist Figure 2A In the video playback scenario shown, the drawing of the recommendation page corresponds to one ViewRootImpl1 and one ViewRoot1 (including the view root). Figure 11 ,See Figure 12 (View 13, etc.), and a VrrViewInfoHandler 1. Among them, the view... Figure 11 It can be video content, video Figure 12 This could be the rectangular area containing the comment section, and view 13 could be a repost control. However, in Figure 7 In the displayed scenario, when the user login window A3 pops up in the recommendation page A1, the drawing of this display interface also includes a ViewRootImpl 2, a view root 2 (including views 21, 22, 23, etc.), and a VrrViewInfoHandler 2. View 21 can be the username, and view 22 can be the password. At this time, the refresh rate control module 504 needs to adjust the screen refresh rate based on the scene recognition results of view root 1 and view root 2.

[0107] The following is combined with Figure 8-12 The display method provided in the embodiments of this application is described below. It can be understood that the target view is a video view.

[0108] Figure 8 A flowchart of a display method provided in an embodiment of this application is shown, as follows: Figure 8 As shown, the method includes:

[0109] S101, determine the current display scene based on the currently displayed content.

[0110] In this embodiment, the current display content of the short video application can be identified first. If the current display content includes video content, scene identification can be performed based on the current display content to determine the current display scene.

[0111] Specifically, the first step is to obtain all view information from the current display interface of the short video application, determine the view type, and then identify the target view based on the view type. This target view is then marked and added to the monitoring list. The view information includes the view type, and the target view can be a video-related view. The method for determining the target view will be explained in detail later and will not be elaborated here. If the current display interface includes the target view, and the current displayed content includes video content, scene recognition is required.

[0112] It's understandable that when a short video application is running, the display interface corresponding to the activity page includes various types of views, such as text views and video views. The view type can be determined based on all the view information obtained, thus identifying the target view. If the currently displayed content does not include video content, it indicates that the predicted interaction frequency corresponding to the currently displayed content is high, and the current display scenario can be determined to be a non-video scenario, eliminating the need for scene recognition.

[0113] Then, for the target view in the monitoring list, the system monitors whether the target view information changes to determine the timing for triggering scene recognition. Scene recognition is then performed, where the target view information includes visibility, offset, and position. The method for determining the trigger timing for scene recognition will be explained in detail later and will not be elaborated here.

[0114] It is understandable that the target view information is relative information based on the parent node corresponding to the target view. When performing scene recognition on the target view, it is necessary to traverse all parent nodes. This traversal process takes a lot of time. Therefore, in order to reduce the time consumption, it is necessary to select the triggering time for scene recognition.

[0115] During scene recognition, it is necessary to calculate the target view information and determine whether it meets the first scene condition. When the target view information meets the first scene condition, it indicates that the predicted interaction frequency corresponding to the currently displayed content is low, and the current display scene can be determined to be a video scene, such as... Figure 2A The video playback scenario is shown. When the target view information does not meet the first scenario condition, it indicates that the predicted interaction frequency corresponding to the currently displayed content is high, and the current display scenario can be determined to be a non-video scenario, such as... Figure 2B The example shown is a swiping scene in the comment section. The method for scene recognition will be described in detail later and will not be repeated here.

[0116] S102, determine the screen refresh rate corresponding to the currently displayed content based on the current display scenario.

[0117] In this embodiment, after scene recognition is completed, a scene recognition result is generated. The scene recognition result may include: the current scene is a non-video scene, the current scene is a video scene, and the current view root has disappeared. Based on the scene recognition result, the screen refresh rate corresponding to the currently displayed content can be determined. For example, the screen refresh rate corresponding to a non-video scene can be a high refresh rate, such as 90Hz, 100Hz, or 120Hz; the screen refresh rate corresponding to a video scene can be a low refresh rate, such as 30Hz, 40Hz, or 60Hz.

[0118] In some embodiments, when the electronic device detects a first instruction from a user to open a first display interface of a first application (e.g., a short video application), it determines that the first display content in the first display interface corresponds to a first display scene, and then displays the first display interface at a first screen refresh rate based on the first display scene. The first screen refresh rate can be a low refresh rate, such as 30Hz, 40Hz, or 60Hz. When the electronic device detects a second instruction from a user to open a second display interface, it determines that the second display content in the second display interface corresponds to a second display scene, and then displays the second display interface at a second screen refresh rate based on the second display scene. The second screen refresh rate can be a high refresh rate, such as 90Hz, 100Hz, or 120Hz.

[0119] In some embodiments, when it is determined that the target view in the first displayed content satisfies the first scene condition, the first displayed content is determined to correspond to the first display scene. The target view is a video view. If it is determined that the second displayed content does not include the target view or that the target view in the second displayed content does not satisfy the first scene condition, the second displayed content is determined to correspond to the second display scene.

[0120] In some embodiments, all view information (including view type) in the first display interface is obtained, and the target view is determined to be included in the first display content based on the view type.

[0121] In some embodiments, the first display interface can be at least one of a short video playback interface, a live streaming interface, and a full-screen video playback interface. The second display interface can be at least one of an interface that displays both videos and comments, a user homepage interface, an online store interface, and a search results interface.

[0122] The display method provided in this application will be briefly described below in conjunction with typical display scenarios of short video applications in the embodiments of this application.

[0123] For video playback scenarios in short video applications, such as Figure 2AIn the display interface shown, during the rendering of the activity page, the view module 502 first determines the view type based on the stored view information (corresponding to the content displayed in the current display interface). After identifying the target view A11, it marks the target view A11 and stores it in the monitoring list created by the scene recognition module 503. After the view basic capability implementation module 501 triggers the interface rendering, the scene recognition module 503 monitors the rendering process and performs scene recognition on the target view A11 in the monitoring list. When the target view information meets the first video scene condition, it determines that the current display scene is a video scene and sends the view root state (HAS_VIDEO) corresponding to the scene recognition result to the refresh rate control module 504. The refresh rate control module 504 adjusts the screen refresh rate to a low refresh rate based on the view root state, such as 30Hz or 60Hz.

[0124] For short video applications, such as video swiping and switching scenarios, for example Figure 2A The displayed interface shows a video switching scene when the user performs a swipe to switch videos. During the activity page interface rendering, the view module 502 first determines the view type based on stored view information, identifies the target view A11, marks it, and stores it in the monitoring list created by the scene recognition module 503. After the view basic capability implementation module 501 triggers interface rendering, the scene recognition module 503 monitors the rendering process and performs scene recognition on the target view A11 in the monitoring list. When the target view information meets the second video scene condition, the current display scene is determined to be a video scene, and the view root state (VIDEO_MOVING) corresponding to the scene recognition result is sent to the refresh rate control module 504. The refresh rate control module 504 adjusts the screen refresh rate to a low refresh rate based on the view root state, such as 30Hz or 60Hz.

[0125] In some embodiments, different screen refresh rates can be set for the video playback scenario and the video sliding transition scenario. For example, when the current display scenario is a video playback scenario, the screen refresh rate can be adjusted to 60Hz; when the current display scenario is a video sliding transition scenario, the screen refresh rate can be adjusted to 80Hz. The screen refresh rate corresponding to different scenarios can be set according to the actual application, and this application does not impose any restrictions on this.

[0126] The following is combined with Figure 9 This application describes a method for determining a target view within the display methods provided in its embodiments. (Refer to...) Figure 9 , Figure 9 A flowchart illustrating a method for determining a target view is shown, such as... Figure 9 As shown, the methods for determining the target view include:

[0127] S201, Binding the view to the view root (dispatchAttachedToWindow)

[0128] It's understandable that calling the `dispatchAttachedToWindow` method binds a view to the view root in the active page, and allows for customization of view components within the corresponding interface of the active page. This enables the determination of the views that need to be drawn during the interface rendering process. Therefore, when determining the target view, the view type can be directly judged based on the view information corresponding to the view root of the active page.

[0129] S202, Determine the view type.

[0130] In this step, the view module 502 determines the type of views in the application to identify the target view. Specifically, based on the view information stored in the view module 502 corresponding to the view root of the active page, the view type is obtained, it is determined whether each view is a video view, and video views are marked and recorded in the monitoring list. For example, views of type SurfaceView or TextureView can be marked. Marking the target view may include marking the nodes within the target view.

[0131] It should be understood that during scene recognition, it is necessary to monitor the information of the target view (such as its position). In order to cover the situation of multiple changes in the position of the target view, it is necessary to monitor the relative position of the target view with respect to its parent node. Therefore, when marking the target view, it is necessary not only to mark the target view, but also to mark the parent node of the target view.

[0132] S203, Create a monitoring list (addVideoViews).

[0133] In this step, the scene recognition module 503 creates a monitoring list. In some embodiments, the scene recognition module 503 performs scene recognition only on target views recorded in the monitoring list.

[0134] It's understandable that for a single activity page, step 203 only needs to be executed once: creating a monitoring list. Furthermore, there's a one-to-one correspondence between the view root, the ViewRootImpl class, the VrrViewInfoHandler class, and the monitoring list.

[0135] S204, Add the target view to the monitoring list (mVideoViews.add).

[0136] In this step, the scene recognition module 503 adds the identified target view to the monitoring list.

[0137] S205, traverse all parent nodes.

[0138] In this step, the scene recognition module 503 traverses all parent nodes corresponding to the target view and marks the parent nodes of the target view. It can be understood that the target view is a rectangular area that can include multiple nodes. Since the parent nodes of the target view are below it, each node of the target view corresponds to a parent node. Therefore, based on the marked parent nodes of the target view, the relative position of the target view with respect to its parent nodes can be determined.

[0139] S206, Update the flags of the target view (setHasVideoView).

[0140] In this step, after the target view is determined, the view module 502 updates the flag of the target view to indicate that the target view has completed marking. For example, the flag of the target view can be mVideoViewsFlag, and updating the flag can be done by setting mVideoViewsFlag = true, indicating that the target view has completed marking.

[0141] The following is combined with Figure 10 and Figure 11 This application describes a method for determining the scene recognition triggering time in the display method provided in its embodiments. (Refer to...) Figure 10 , Figure 10 A flowchart illustrating how to determine the triggering timing for scene recognition is shown. For example... Figure 10 As shown, the display method provided in this application embodiment includes the following steps in determining the scene recognition triggering time:

[0142] S301 monitors the current interface drawing process.

[0143] In this step, when the display interface corresponding to the current activity page begins to be drawn, the view basic capability implementation module 501 triggers the interface drawing and triggers the scene recognition module 503 to monitor the interface drawing process. It can be understood that video scenes and non-video scenes can be distinguished based on the target view information; therefore, it is only necessary to monitor the target view information in the monitoring list to determine whether the current display scene has changed.

[0144] S302, Obtain target view information.

[0145] In this step, the scene recognition module 503 first obtains the target view information from the view module 502, and determines the timing of triggering scene recognition by judging the changes in the target view information.

[0146] It is understandable that for the display scenarios of short video applications, the start and end of changes in the target view information indicate that the current display scenario has changed. In order to reduce the time consumption, scene recognition only needs to be performed at the moment when the display scenario changes.

[0147] Specifically, refer to Figure 11 , Figure 11 Another flowchart for determining the triggering timing of scene recognition is shown. For example... Figure 11 As shown, the scene recognition module 503 can obtain target view information from the view module 502, including visibility (setFlags), offset (scrollTo), and position (layout). The scene recognition module 503 determines the target view information (startViewInfoChecking), and updates the current flag bit (setCheckVideoView) of the target view information when the target view information changes. For example, when the flag bit of the target view information is mCheckVideoView, if a change in the target view information is detected, the current flag bit can be modified, setting mCheckVideoView = true.

[0148] It can be understood that the offset of the target view represents the offset of the target view's coordinates. For example, as... Figure 2A and Figure 2B As shown, when you open the comments section A2 in the recommendation page A1, the currently displayed interface changes from... Figure 2A The displayed interface changes as shown below. Figure 2B The coordinates of the target view A11 have shifted in the displayed interface.

[0149] S303, determine whether the target view information has changed.

[0150] In this step, the scene recognition module 503 can determine whether the target view information has changed by comparing the current flag bit of the target view information, and perform scene recognition at the moment when the target view information begins to change and ends to change. When it is determined that the target view information has changed, step S304 is executed to trigger scene recognition; when it is determined that the target view information has not changed, the process returns to step S301 to continue monitoring the interface drawing process.

[0151] Specifically, such as Figure 11 As shown, the current flag of the target view information is mCheckVideoView, and the historical flag is mPreCheckVideoView. We can determine if the current flag and the historical flag are the same. If the current flag and the historical flag are different (i.e., mCheckVideoView != mPreCheckVideoView), it indicates that the target view information has started or ended changing, and scene recognition is required, entering the scene recognition process (currentHasVideoView). If the current flag and the historical flag are the same, scene recognition is not required.

[0152] For example, if the target view information remains unchanged, its flag mCheckVideoView = false. When the target view information changes, mCheckVideoView = true, and mPreCheckVideoView = false. The current flag is inconsistent with the historical flag, i.e., mCheckVideoView ! = mPreCheckVideoView, indicating that the target view information has begun to change, triggering scene recognition. After scene recognition, the value of the current flag is assigned to the historical flag, i.e., mPreCheckVideoView = mCheckVideoView = true, and the current flag is reset, i.e., mCheckVideoView = false. When the target view information continues to change, its current flag changes, i.e., mCheckVideoView = true. At this time, mPreCheckVideoView = mCheckVideoView = true, and scene recognition is not triggered. When the target view information stops changing, its current flag does not change, i.e., mCheckVideoView = false. At this time, mCheckVideoView ! = mPreCheckVideoView, triggering scene recognition.

[0153] It is understandable that regardless of whether the current flag bit and the historical flag bit of the target view are the same, the historical flag bit needs to be updated, that is, mPreCheckVideoView = mCheckVideoView. Furthermore, after comparing the current flag bit and the historical flag bit, regardless of whether scene recognition needs to be performed, the current flag bit needs to be reset, that is, mCheckVideoView = false.

[0154] S304, triggers scene recognition.

[0155] In this step, the scene recognition module 503 performs scene recognition on the target view in the monitoring list when it detects that the target view information starts to change and ends to change.

[0156] Specifically, refer to Figure 12 , Figure 12 A flowchart of a scene recognition method is shown. Figure 12 As shown, scene recognition methods include:

[0157] S401, Determine if the monitoring list exists.

[0158] In this step, the scene recognition module 503 first determines whether the monitoring list exists. If the monitoring list exists, step S402 is executed to determine whether the target view information meets the first scene condition. If the monitoring list does not exist, the current view root disappears, that is, the display interface corresponding to the activity page disappears, indicating that a screen switch or application switch has occurred. No scene recognition is required, and step S405 is executed to obtain the third scene recognition result.

[0159] S402, determine whether the target view information meets the first scene conditions.

[0160] In this step, the scene recognition module 503 calculates the target view information in the monitoring list and determines whether the visibility, offset, and position of the target view meet the first scene conditions.

[0161] Specifically, the first scene conditions include the first video scene conditions and the second video scene conditions. The first video scene conditions correspond to the video playback scene, and the second video scene conditions correspond to the video sliding switching scene. As mentioned above, the first video scene conditions also include conditions (1), (2), and (3), and the second video scene conditions also include conditions (4), (5), and (6). The specific content of the video scene conditions can be found in the relevant descriptions above, and will not be repeated here.

[0162] When the target view information simultaneously satisfies all the conditions of the first video scene condition, it indicates that the predicted interaction frequency corresponding to the currently displayed content is low, and the current display scene can be determined to be a video playback scene. Step S403 is executed to obtain the first scene recognition result. When the target view information simultaneously satisfies all the conditions of the second video scene condition, it indicates that the predicted interaction frequency corresponding to the currently displayed content is low, and the current display scene can be determined to be a video sliding transition scene. Step S403 is executed to obtain the first scene recognition result. If the target view information does not simultaneously satisfy all the conditions of the first video scene condition or does not simultaneously satisfy all the conditions of the second video scene condition, it indicates that the predicted interaction frequency corresponding to the currently displayed content is high, and the current display scene can be determined to be a non-video scene. Step S404 is executed to obtain the second scene recognition result.

[0163] S403 is identified as the first scene recognition result.

[0164] In this step, after the scene recognition module 503 obtains the first scene recognition result, it determines the current view root state based on the first scene recognition result and sends the current view root state to the refresh rate control module 504. The refresh rate control module 504 determines and adjusts the current screen refresh rate based on the current view root state.

[0165] Specifically, the first scene recognition result indicates that the current display scene is a video scene, which corresponds to two view root states. When the target view information simultaneously satisfies all conditions of the first video scene condition, the corresponding current view root state is HAS_VIDEO; when the target view information simultaneously satisfies all conditions of the second video scene condition, the corresponding current view root state is VIDEO_MOVING. When the refresh rate control module 504 receives the state HAS_VIDEO or VIDEO_MOVING, it adjusts the screen refresh rate to a low refresh rate, such as 30Hz or 60Hz.

[0166] In some embodiments, the refresh rate control module 504 can set different screen refresh rates for the states HAS_VIDEO and VIDEO_MOVING. For example, when the state HAS_VIDEO is received, the screen refresh rate is adjusted to 30Hz; when the state VIDEO_MOVING is received, the screen refresh rate is adjusted to 60Hz.

[0167] S404 is identified as the second scene recognition result.

[0168] In this step, after the scene recognition module 503 obtains the second scene recognition result, it determines the current view root state based on the second scene recognition result and sends the current view root state to the refresh rate control module 504. The refresh rate control module 504 determines and adjusts the current screen refresh rate based on the current view root state.

[0169] Specifically, the second scene recognition result is that the current display scene is a non-video scene, and the corresponding current view root state is NO_VIDEO. When the refresh rate control module 504 receives the state NO_VIDEO, it adjusts the screen refresh rate to a high refresh rate, such as 90Hz or 120Hz.

[0170] S405 is identified as the third scene recognition result.

[0171] In this step, after the scene recognition module 503 obtains the third scene recognition result, it determines the current view root state based on the third scene recognition result and sends the current view root state to the refresh rate control module 504. The refresh rate control module 504 determines and adjusts the current screen refresh rate based on the current view root state.

[0172] Specifically, the third scene recognition result is that the current view root disappears, and the corresponding current view root state is CANCEL_VIEWROOT. When the refresh rate control module 504 receives the state CANCEL_VIEWROOT, it determines the current screen refresh rate based on the previous view root.

[0173] It is understandable that when the current display interface is being drawn, the refresh rate control module 504 records the view root name and its corresponding state in a map. When adjusting the refresh rate, the refresh rate control module 504 determines the current screen refresh rate based on the state of the last view root (i.e., the current view root). If the current view root state is CANCEL_VIEWROOT, the current view root is removed from the map, and the previous view root is the last view root sent in the map.

[0174] It is understood that the first scene recognition result, the second scene recognition result, and the third scene recognition result in the embodiments of this application are merely examples, and the scene recognition results may also include more or fewer scene recognition results. The current view root state corresponding to the scene recognition result may also be other states, which can be set according to actual needs, and this application does not limit this.

[0175] The display method provided in this application embodiment can adjust the screen refresh rate of the electronic device in real time based on the current display scenario of the application. This can avoid problems such as excessive power consumption due to excessively high screen refresh rate settings in some display scenarios, and reduced screen smoothness and stuttering due to excessively low screen refresh rate settings in some display scenarios. This enables the device to achieve better performance and improves the user experience.

[0176] This application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the above-described display method.

[0177] This application provides a storage medium storing instructions that, when executed on an electronic device, cause the electronic device to perform the aforementioned display method.

[0178] This application provides a program product that includes computer instructions. When executed by an electronic device, the electronic device performs the above-described display method.

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

[0180] Program code can be applied to input instructions to execute the functions described in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, the processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application-specific integrated circuit (ASIC), or a microprocessor.

[0181] The program code can be implemented using a high-level procedural language or an object-oriented programming language to communicate with the processing system. Assembly language or machine language can also be used when needed. In fact, the mechanisms described in this application are not limited to any particular programming language. In either case, the language can be a compiled language or an interpreted language.

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

[0183] In the accompanying drawings, some structural or methodological features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be necessary. Rather, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. Furthermore, the inclusion of structural or methodological features in a particular figure does not imply that such features are required in all embodiments, and in some embodiments, these features may be omitted or may be combined with other features.

[0184] It should be noted that all units / modules mentioned in the device embodiments of this application are logical units / modules. Physically, a logical unit / module can be a physical unit / module, a part of a physical unit / module, or a combination of multiple physical units / modules. The physical implementation of these logical units / modules themselves is not the most important factor; the combination of functions implemented by these logical units / modules is the key to solving the technical problems proposed in this application. Furthermore, to highlight the innovative aspects of this application, the above-described device embodiments of this application have not introduced units / modules that are not closely related to solving the technical problems proposed in this application. This does not mean that the above-described device embodiments do not contain other units / modules.

[0185] It should be noted that in the examples and description of this application, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0186] Although this application has been illustrated and described with reference to certain embodiments thereof, those skilled in the art will understand that various changes in form and detail may be made thereto without departing from the scope of this application.

Claims

1. A display method applied to an electronic device, characterized in that, include: The screen of the electronic device displays a first display interface of the first application at a first screen refresh rate, and the first display interface includes first display content. The screen of the electronic device displays a second display interface of the first application at a second screen refresh rate, and the second display interface includes second display content. Wherein, the first screen refresh rate is less than the second screen refresh rate, and the predicted interaction frequency of the second displayed content is higher than the predicted interaction frequency of the first displayed content.

2. The display method according to claim 1, characterized in that, The screen of the electronic device displays a first display interface of a first application at a first screen refresh rate, including: A first instruction from the user to open the first display interface was detected; Determine that the first displayed content corresponds to the first displayed scene; Based on the first display scenario, the first display interface is displayed at the first screen refresh rate.

3. The display method according to claim 2, characterized in that, Determining that the first displayed content corresponds to the first displayed scene includes: It is determined that the target view in the first displayed content satisfies the first scene condition, and the first displayed content corresponds to the first display scene.

4. The display method according to claim 3, characterized in that, Also includes: Obtain all view information in the first display interface, including view type; Based on the view type, it is determined that the first displayed content includes the target view.

5. The display method according to claim 4, characterized in that, The target view is a video view.

6. The display method according to claim 3, characterized in that, The first scene conditions include the first video scene conditions, which include: The visibility of all nodes in the target view and its parent view is visible; The width and height of all nodes in the target view and its parent view occupy a proportion greater than or equal to the width and height of the electronic device screen. The width of the target view is greater than or equal to the width of the electronic device screen, or the height of the target view is greater than or equal to the height of the electronic device screen, wherein the second value is greater than the first value; The center point of the target view is located within a preset range of the center point of the electronic device screen.

7. The display method according to claim 3, characterized in that, The first scene condition also includes a second video scene condition, which includes: The target view is visible; The width and height of the target view occupy a proportion greater than or equal to the width and height of the electronic device screen, and, The width of the target view is greater than or equal to the width of the electronic device screen, or the height of the target view is greater than or equal to the height of the electronic device screen, wherein the second value is greater than the first value; At the same time, the positions of at least two of the target views change.

8. The display method according to claim 1, characterized in that, The screen of the electronic device displays a second display interface of the first application at a second screen refresh rate, including: A second instruction from the user to open the second display interface was detected; Determine that the second display content corresponds to the second display scene; Based on the second display scenario, the second display interface is displayed at the second screen refresh rate.

9. The display method according to claim 8, characterized in that, Determining the second display content corresponding to the second display scene includes: Determine that the target view is not included in the second displayed content, or, It is determined that the target view in the second display content does not meet the first scene condition, and the second display content corresponds to the second display scene.

10. The display method according to claim 1, characterized in that, The first application is a video application.

11. The display method according to claim 1, characterized in that, The first display interface is at least one of a short video playback interface, a live streaming interface, and a full-screen video playback interface.

12. The display method according to claim 1, characterized in that, The second display interface is at least one of the following: an interface that displays both videos and comments, a user homepage interface, an online store interface, and a search results interface.

13. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the display method as described in any one of claims 1-12.

14. A storage medium, characterized in that, The storage medium stores instructions that, when executed on an electronic device, cause the electronic device to perform the display method according to any one of claims 1-12.

15. A program product, characterized in that, The program product includes computer instructions, which, when executed by an electronic device, enable the electronic device to perform the display method as described in any one of claims 1-12.

Images