Frame rate adjustment method, electronic equipment, chip system and storage medium

Abstract

The invention provides a frame rate adjusting method, electronic equipment, a chip system and a storage medium, and relates to the technical field of electronic equipment, in the method, an application interface displayed by the electronic equipment can comprise a plurality of views, and when user operation acts on different views, the views can be displayed by the electronic equipment. A frame rate during execution of a response event corresponding to a user operation can be determined according to a view on which the user operation acts. The response event can be a switching process which is triggered by the user operation and is used for switching from the current interface to another interface. For user operations on different views, the frame rates in the response event execution process can also be different. In this way, the frame rate during execution of some response events with high fluency requirements can be adjusted to a higher frame rate, and the fluency in the interface switching process is improved; and the frame rate during execution of some response events with low fluency requirements is adjusted to a low frame rate, so that over-high power consumption caused by improvement of the frame rate is avoided.

Description

Technical Field

[0001] This application relates to the field of electronic equipment technology, and in particular to a frame rate adjustment method, electronic equipment, chip system, and storage medium. Background Technology

[0002] As electronic devices become increasingly intelligent and people's demands for them rise, these devices offer more and more functions. For some portable electronic devices, reducing power consumption is becoming increasingly important.

[0003] Even in non-video applications, users frequently encounter scenarios that demand smooth visuals when using electronic devices. Examples include map applications where swiping the map triggers map movement, and menu bar swiping in other applications causes menu bar state changes. To improve user experience, the frame rate of these applications can be increased; however, increasing the frame rate also increases power consumption. Summary of the Invention

[0004] This application provides a frame rate adjustment method, electronic device, chip system, and storage medium that can improve screen smoothness while reducing power consumption.

[0005] To achieve the above objectives, the first aspect of this application provides a frame rate adjustment method, which adopts the following technical solution:

[0006] Display the first interface of the first application, the first interface including a first view and a second view;

[0007] The first operation acting on the first interface was detected;

[0008] In response to the first operation, switch from the first interface to the first target interface of the first application;

[0009] Wherein, when the first operation is performed on the first view, the image frames during the switch from the first interface to the first target interface are displayed at a first frame rate, and the first target interface is the second interface;

[0010] When the first operation is applied to the second view, the image frames during the switch from the first interface to the first target interface are displayed at a second frame rate. The first target interface is the third interface, and the second frame rate is different from the first frame rate.

[0011] In this application, when a user operates on different views of the same interface, the electronic device may be triggered to switch to different interfaces. During the switching process, the user's requirements for screen smoothness may vary. For example, the user may have a higher requirement for screen smoothness during the interface switching process triggered by operations on some views, while the requirement for screen smoothness during the interface switching process triggered by operations on other views may not be high. In order to meet the user's requirements for smoothness without causing excessive power consumption, the frame rate of some interface switching processes with higher screen smoothness requirements and the frame rate of some interface switching processes with lower screen smoothness requirements can be set to different frame rates. For example, the frame rate of some interface switching processes with higher screen smoothness requirements can be set to be higher than the frame rate of some interface switching processes with lower screen smoothness requirements.

[0012] In this application, when a user operates different views on the same interface to switch between interfaces, the appropriate frame rate can be selected to display the image frames during the interface switching process according to the needs of different interface switching processes, instead of displaying the image frames during the interface switching process based on a uniform frame rate. The selection of frame rate is more flexible and can also reduce power consumption.

[0013] Specifically, since different interface transitions have varying requirements for screen smoothness, an appropriate frame rate can be selected to display image frames during these transitions, better meeting user needs. Furthermore, compared to traditional solutions that display image frames at the same frame rate across different interface transitions, this approach reduces power consumption.

[0014] As one implementation of the first aspect, displaying the first interface of the first application includes: displaying the first interface at a third frame rate, wherein the third frame rate is less than or equal to the first frame rate and the third frame rate is less than or equal to the second frame rate.

[0015] After switching from the first interface to the first target interface of the first application, the method further includes:

[0016] The first target interface is displayed at the third frame rate.

[0017] In this application, during the stable display period (excluding the interface switching period), the content of the electronic device remains unchanged or changes only slightly. Therefore, the frame rate can be set to be lower during the stable display period, thereby reducing power consumption. Specifically, the frame rate during the stable display period can be set to be less than or equal to the frame rate during the interface switching period, thus reducing the power consumption of the electronic device during the stable display period. The frame rate during the interface switching period can be set according to the user's requirements for the smoothness of the screen during the interface switching process. For example, when the user has a high requirement for the smoothness of the screen during the interface switching process, a higher frame rate is set, and when the user has a low requirement for the smoothness of the screen during the interface switching process, a lower frame rate is set.

[0018] As another implementation of the first aspect, the third frame rate is the minimum frame rate that the electronic device can support, and the third frame rate is less than the first frame rate and / or less than the second frame rate.

[0019] In this application, the frame rate during the stable display interface is set to the minimum frame rate that the electronic device can support, so the frame rate during the stable display interface is less than the frame rate during the interface switching; thereby further reducing power consumption.

[0020] As another implementation of the first aspect, the method also includes:

[0021] Display the fourth interface of the second application, which includes the third view and the fourth view;

[0022] A second operation was detected acting on the third or fourth view of the fourth interface;

[0023] In response to the second operation, display image frames during the switch from the fourth interface to the second target interface of the second application at a fourth frame rate;

[0024] In the case where the second operation is performed on the third view, the second target interface is the fifth interface.

[0025] When the second operation is performed on the fourth view, the second target interface is the sixth interface.

[0026] In this application, for applications where users have low requirements for screen smoothness during interface switching, operations performed on the view of the application can be set to display image frames during interface switching at the same frame rate, thereby flexibly setting different frame rate switching strategies according to different applications.

[0027] As another implementation of the first aspect, the fourth interface for displaying the second application includes:

[0028] The fourth interface is displayed at the third frame rate, which is the minimum frame rate that the electronic device can support. The third frame rate is less than or equal to the fourth frame rate.

[0029] After switching from the fourth interface to the second target interface of the second application, the method further includes:

[0030] The second target interface is displayed at the third frame rate.

[0031] In this application, the frame rate of the electronic device during the stable display of the interface can be set to the minimum frame rate that the electronic device can support. The minimum frame rate that different electronic devices can support may be different. When the minimum frame rate is sufficient to meet the user's requirements for the smoothness of the screen during the interface switching process, the third frame rate and the fourth frame rate can be set to be the same. When the minimum frame rate cannot meet the user's requirements for the smoothness of the screen during the interface switching process, the fourth frame rate can be set to be greater than the third frame rate. In this way, while meeting the user's requirements for the smoothness of the screen during the interface switching process, the power consumption of the electronic device can also be reduced.

[0032] As another implementation of the first aspect, the method also includes:

[0033] The fifth interface of the first application is displayed. The fifth interface includes a fifth view, and the fifth view includes a first control and a second control.

[0034] A third operation acting on the fifth view was detected;

[0035] In response to the third operation, switch from the fifth interface to the third target interface of the first application;

[0036] In this case, when the third operation is applied to the first control, the image frames during the switch from the fifth interface to the third target interface are displayed at the fifth frame rate. The third target interface is the sixth interface.

[0037] When the third operation is applied to the second control, the image frames during the switch from the fifth interface to the third target interface are displayed at the sixth frame rate. The third target interface is the seventh interface, and the sixth frame rate is different from the fifth frame rate.

[0038] In this application, when a user operates on different controls within the same view, the electronic device may be triggered to switch to different interfaces. During the switching process, the user's requirements for screen smoothness may vary. For example, the user may have a higher requirement for screen smoothness during interface switching triggered by operations on some controls, while the requirement for screen smoothness during interface switching triggered by operations on other controls may be lower. In order to meet the user's requirements for smoothness without causing excessive power consumption, the frame rate for some interface switching processes with higher screen smoothness requirements and the frame rate for some interface switching processes with lower screen smoothness requirements can be set to different frame rates. For example, the frame rate for some interface switching processes with higher screen smoothness requirements can be set to be higher than the frame rate for some interface switching processes with lower screen smoothness requirements.

[0039] As another implementation of the first aspect, the method also includes:

[0040] Display the eighth interface of the first application, which includes the sixth view;

[0041] A fourth operation acting on the sixth view was detected;

[0042] In response to the fourth operation, switch from the eighth interface to the fourth target interface of the first application;

[0043] In the case where the fourth operation is the first gesture operation, the image frames during the switch from the eighth interface to the fourth target interface are displayed at the seventh frame rate, and the fourth target interface is the ninth interface.

[0044] When the fourth operation is the second gesture operation, the image frames during the switch from the eighth interface to the fourth target interface are displayed at the eighth frame rate. The fourth target interface is the tenth interface, and the eighth frame rate is different from the seventh frame rate.

[0045] In this application, when different user operations are applied to the same view, the electronic device may be triggered to switch to different interfaces. During the switching process, the user's requirements for screen smoothness may vary. For example, some gesture operations triggering interface switching processes have higher requirements for screen smoothness, while other gesture operations triggering interface switching processes have lower requirements for screen smoothness. In order to meet the user's requirements for smoothness without causing excessive power consumption, the frame rate of some interface switching processes with higher requirements for screen smoothness and the frame rate of some interface switching processes with lower requirements for screen smoothness can be set to different frame rates. For example, the frame rate of some interface switching processes with higher requirements for screen smoothness can be set to be higher than the frame rate of some interface switching processes with lower requirements for screen smoothness.

[0046] As another implementation of the first aspect, the first gesture operation is a swipe operation, and the ninth and eighth interfaces are generated based on the same activity; the second gesture operation is a click operation, and the tenth and eighth interfaces are generated based on different activities; the seventh frame rate is greater than the eighth frame rate.

[0047] In this application, swiping operations typically trigger changes in at least one of the view's position, size, or contained display content. These changes are usually not caused by activity changes, but rather by a gradual change in the view as the user swipes. The screen is smoother when the frame rate of this process is high; otherwise, stuttering is likely to occur. Clicking operations typically trigger the interface of another activity linked to the control that displays the effect of the click. This interface change process is usually a direct switch to another interface, and the frame rate of this process can be relatively low.

[0048] As another implementation of the first aspect, the first operation is a swipe operation, the first target interface and the first interface are generated based on the same Activity, and the first target interface is the interface displayed after the swipe operation is released.

[0049] In this application, when the first operation is a swipe, it typically triggers a change in at least one of the view's position, size, or displayed content. This change represents a change in the view within the same activity's interface. As the user swipes, the view gradually changes. The first target interface displayed after the swipe operation is not the interface that gradually changes during the user's swipe, but rather the interface that is about to stabilize after the swipe is released. By setting the same first frame rate during the interface transition process before the stabilized interface, from the user's perspective, the smoothness of the interface transition process is consistent, resulting in a better user experience.

[0050] As another way to implement the first aspect, the first application is a map application, a game application, or a short video application, and the second application is a novel application.

[0051] A second aspect of this application provides a frame rate adjustment method, which adopts the following technical solution:

[0052] Display the eighth interface of the first application, which includes the sixth view;

[0053] A fourth operation acting on the sixth view was detected;

[0054] In response to the fourth operation, switch from the eighth interface to the fourth target interface of the first application;

[0055] In the case where the fourth operation is the first gesture operation, the image frames during the switch from the eighth interface to the fourth target interface are displayed at the seventh frame rate, and the fourth target interface is the ninth interface.

[0056] When the fourth operation is the second gesture operation, the image frames during the switch from the eighth interface to the fourth target interface are displayed at the eighth frame rate. The fourth target interface is the tenth interface, and the eighth frame rate is different from the seventh frame rate.

[0057] In this application, when different user operations are applied to the same view, the electronic device may be triggered to switch to different interfaces. During the switching process, the user's requirements for screen smoothness may vary. For example, some gesture operations triggering interface switching processes have higher requirements for screen smoothness, while other gesture operations triggering interface switching processes have lower requirements for screen smoothness. In order to meet the user's requirements for smoothness without causing excessive power consumption, the frame rate of some interface switching processes with higher requirements for screen smoothness and the frame rate of some interface switching processes with lower requirements for screen smoothness can be set to different frame rates. For example, the frame rate of some interface switching processes with higher requirements for screen smoothness can be set to be higher than the frame rate of some interface switching processes with lower requirements for screen smoothness.

[0058] As one implementation of the second aspect, the first gesture operation is a swipe operation, the ninth and eighth interfaces are generated based on the same activity, and the fourth target interface is the interface displayed after the swipe operation is released; the second gesture operation is a click operation, the tenth and eighth interfaces are generated based on different activities; the seventh frame rate is greater than the eighth frame rate.

[0059] As another implementation of the second aspect, displaying the eighth interface of the first application includes: displaying the eighth interface at a third frame rate, wherein the third frame rate is less than or equal to the seventh frame rate and the third frame rate is less than or equal to the eighth frame rate.

[0060] After switching from the eighth interface to the fourth target interface of the first application, the method further includes:

[0061] The fourth target interface is displayed at the third frame rate.

[0062] As another implementation of the second aspect, the third frame rate is the minimum frame rate that the electronic device can support, and the third frame rate is less than the seventh frame rate and / or less than the eighth frame rate.

[0063] Thirdly, an electronic device is provided, including a processor, which is configured to invoke a computer program stored in a memory to implement the method of any one of the first aspects of this application.

[0064] Fourthly, a chip system is provided, including a processor coupled to a memory, wherein the processor executes a computer program stored in the memory to cause an electronic device to implement the method of any one of the first aspects of this application.

[0065] Fifthly, a computer-readable storage medium is provided, which stores a computer program that, when computer instructions are executed on an electronic device, causes the electronic device to implement the method of any one of the first aspects of this application.

[0066] In a sixth aspect, embodiments of this application provide a computer program product that, when run on a device, causes the electronic device to execute the method of any one of the first aspects of this application.

[0067] It is understood that the beneficial effects of the third to sixth aspects mentioned above can be found in the relevant descriptions in the first and second aspects mentioned above, and will not be repeated here. Attached Figure Description

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

[0069] Figure 2 A schematic diagram of the interface of a map application provided in an embodiment of this application;

[0070] Figure 3 This application provides a schematic diagram illustrating the state changes of a menu bar constructed using a view, as shown in the embodiments of this application.

[0071] Figure 4 Another schematic diagram of the state change of the menu bar constructed by the view provided in the embodiments of this application;

[0072] Figure 5 A schematic diagram of frame rate change during interface switching provided in an embodiment of this application;

[0073] Figure 6 A schematic diagram illustrating a frame rate change when adjusting the frame rate from the view dimension, provided as an embodiment of this application.

[0074] Figure 7 A schematic diagram illustrating frame rate changes when adjusting the frame rate from the view and different operation dimensions, provided as an embodiment of this application.

[0075] Figure 8 A flowchart illustrating a frame rate adjustment method provided in an embodiment of this application;

[0076] Figure 9 This is a schematic diagram of the technical architecture of a frame rate adjustment method provided in an embodiment of this application;

[0077] Figure 10 A timing diagram of a method for adjusting frame rate from the view dimension provided in an embodiment of this application;

[0078] Figure 11 A timing diagram of a method for adjusting frame rate from an application perspective, provided in an embodiment of this application;

[0079] Figure 12 A timing diagram of another method for adjusting the frame rate from the view dimension provided in an embodiment of this application;

[0080] Figure 13 Timing diagram of another method for adjusting frame rate from an application perspective, provided in an embodiment of this application;

[0081] Figure 14 A schematic diagram of an interface for a frame rate adjustment method provided in an embodiment of this application;

[0082] Figure 15 A schematic diagram of an interface for another frame rate adjustment method provided in an embodiment of this application. Detailed Implementation

[0083] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limiting purposes, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details.

[0084] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0085] It should also be understood that in the embodiments of this application, "one or more" refers to one, two, or more; "and / or" describes the relationship between the associated objects, indicating that three relationships can exist; for example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0086] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," "fourth," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0087] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0088] This application provides a frame rate adjustment method that can be applied to electronic devices, such as tablets, mobile phones, wearable devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, and personal digital assistants (PDAs). This application does not limit the specific type of electronic device.

[0089] Figure 1 A schematic diagram of an electronic device is shown. The electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0090] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 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.

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

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

[0093] Internal memory 121 can be used to store computer executable program code, including instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a function (such as image playback). Touch sensor 180K, also called a "touch panel," can be disposed on display screen 194. Touch sensor 180K and display screen 194 together form a touch screen, also called a "touch screen." Touch sensor 180K is used to detect touch operations applied to or near it. Touch sensor can transmit the detected touch operation to application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be disposed on the surface of electronic device 100, in a different location than display screen 194.

[0094] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0095] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a minimized display, a microLED, a micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 100 may include one or N displays 194, where N is a positive integer greater than 1.

[0096] This application does not specifically limit the structure of the execution subject of a frame rate adjustment method. As long as communication can be performed according to the frame rate adjustment method provided by this application by running code that records the frame rate adjustment method of this application. For example, the execution subject of the frame rate adjustment method provided by this application can be a functional module in an electronic device that can call and execute a program, or a communication device applied in an electronic device, such as a chip.

[0097] Before introducing specific embodiments of this application, we will first describe the view in the operating system.

[0098] Applications on electronic devices can provide user interfaces for human-computer interaction. The visible content in the user interface can be constructed using views, such as controls, text boxes, images, menu bars, and other visible elements. The visible content constructed using views can also be called a view.

[0099] Reference Figure 2 This is a schematic diagram of an interface of a map application provided in an embodiment of this application.

[0100] The visible content in this interface is constructed from at least four views: view1 constructs the visible content related to the map image; view2 and view3 construct different floating controls; and view4 constructs a collapsible and expandable menu bar.

[0101] When the electronic device displays this interface on its screen, the user can interact with the map image area constructed in view1, triggering the electronic device to move, zoom in, or zoom out of the map image. This results in the electronic device displaying the moved, zoomed-in, or zoomed-out map image in the corresponding area of ​​view1. Similarly, the electronic device can also display the movement, zooming, or zooming process of the image in the corresponding area of ​​view1. For example, a user can swipe within the map image area constructed in view1 to move the map image, and pinch or separate two fingers within the map image area constructed in view1 to zoom in or out of the map image.

[0102] Users can click on controls built in view2 or view3, which will trigger the electronic device to display another interface linked to that control.

[0103] Users can click on controls in the menu bar built with View4 to trigger the electronic device to display another interface linked by that control.

[0104] Users can also swipe in the menu bar area built by view4 to trigger the electronic device to switch the currently half-folded menu bar to a folded or expanded state.

[0105] Reference Figure 3 This is a schematic diagram illustrating the switching between various states of the menu bar constructed by view4 in the embodiments of this application.

[0106] Reference Figure 3 In (a), the menu bar constructed by view4 is in a semi-collapsed state. Users can trigger the electronic device to display the menu bar by swiping upwards in the menu bar area. Figure 3 The interface shown in (b) is also accessible to the user by swiping down in the menu bar area. Figure 3 The interface shown in (c) is shown in the image.

[0107] In response to Figure 3 The swipe-up operation of the menu bar area described in (a) of the electronic device displays... Figure 3 The interface shown in (b) is in Figure 3In the interface shown in (b), the menu bar constructed by view4 is in an expanded state, completely covering the content constructed by view1, view2, and view3. Of course, in practical applications, the expanded menu bar can also be configured to partially cover the content constructed by view1, and completely cover the content constructed by view2 and view3. This application embodiment does not limit the positional relationship between the expanded menu bar and the content constructed by other views.

[0108] In response to Figure 3 The swipe-down operation of the menu bar area shown in (a) on the electronic device displays... Figure 3 The interface shown in (c) is in Figure 3 In the interface shown in (c), the menu bar constructed by view4 is in a collapsed state. In this collapsed state, the menu bar displays a search box and an expand control. The expand control is used to switch the currently collapsed menu bar to a half-collapsed or expanded state. Of course, in practical applications, the search box may not be displayed in this collapsed state.

[0109] Reference Figure 3 In (b), the menu bar constructed by view4 is in an expanded state. Users can trigger the electronic device to display the menu bar by swiping down a distance less than or equal to a distance threshold within the menu bar area. Figure 3 The interface shown in (a) is also shown; users can also trigger the electronic device to display the interface by sliding down the menu bar area a distance greater than a distance threshold. Figure 3 The interface shown in (c) is shown in the image.

[0110] Reference Figure 3 In (c), the menu bar constructed by view4 is in a collapsed state. Users can trigger the electronic device to display the menu by swiping upwards from the expanded control with a swipe distance less than or equal to a distance threshold. Figure 3 The interface shown in (a) is also shown; users can also trigger the electronic device to display the interface by swiping upwards from the expanded control, with the swipe distance exceeding a distance threshold. Figure 3 The interface shown in (b) is shown in the diagram. Of course, users can also trigger the electronic device to display the interface by clicking on the expand control. Figure 3 The interface shown in (b) is shown in the image.

[0111] in, Figure 3 (a) in Figure 3 The interface change process shown in (b) can be referred to Figure 4 As shown. Figure 4 (a) in Figure 4In the diagram, (d) refers to the process by which an electronic device gradually changes from displaying one interface to displaying another in response to a user's swipe gesture.

[0112] Reference Figure 4 As shown in (a), the user action is an upward swipe on the menu bar area. (See reference...) Figure 4 (b) shows the position, size, and content of the menu bar when the user slides their finger to the location shown in the image. (See reference...) Figure 4 In (c), the position, size, and displayed content of the menu bar are shown when the user slides their finger to the location in the image. Figure 4 (a) to Figure 4 During process (c), the position, size, and content of the menu bar are related to the sliding position (or sliding distance) of the finger, and the position, size, and content of the menu bar change as the user slides their finger.

[0113] On the electronic device display Figure 4 In the case of the interface shown in (c), when the user releases their hand, the electronic device displays... Figure 4 The interface shown in (d) is shown in the image.

[0114] The specific display methods of the menu bar constructed by view4 in the semi-collapsed, expanded, and collapsed states (e.g., the positional relationship between it and the content constructed by other views, and the specific form of the expanded control) in this embodiment are only for illustrative purposes. In actual applications, the display methods of each state can be set according to the actual situation.

[0115] Furthermore, the menu bar constructed by view4 may include only two states, or more than three states. The number of states in the content constructed by view4 is only for illustrative purposes; the operation of triggering the switching between different states is also only for illustrative purposes. The embodiments of this application do not impose any limitations on the above content.

[0116] As mentioned earlier, a user's swipe up on the menu bar area constructed by view4 can trigger the electronic device to switch the menu bar's state. The switching process is a gradual transition from one state to another. Users typically require a high degree of smoothness in this transition. Therefore, to improve the user experience, it can be configured so that the electronic device displays the state change process at a higher frame rate during the menu bar's state transition.

[0117] To better understand this solution, the differences and relationship between refresh rate and frame rate are described here.

[0118] Refresh rate and frame rate are two parameters related to video display performance.

[0119] Refresh rate refers to the number of times a screen updates its display per second, measured in Hz. The screen refresh rate is typically determined by the screen hardware. For example, 60Hz means the screen refreshes 60 times per second.

[0120] Frame rate is the number of frames (also known as image frames) that a GPU (graphics processing unit) renders per second. It can be measured in Hz or FPS. For example, 60 FPS means that the GPU can render a maximum of 60 frames per second.

[0121] As an example of the relationship between the two, if the screen refresh rate of an electronic device is 120Hz, and the frame rate of the GPU rendering the image is 60FPS, then theoretically, each frame rendered by the GPU can be refreshed and displayed on the screen twice. If the screen refresh rate of an electronic device is 120Hz, and the frame rate of the GPU rendering the image is 120FPS, then theoretically, each frame rendered by the GPU can be refreshed and displayed on the screen once.

[0122] Of course, in practical applications, since the electronic device needs to render, composite, and send the drawn image to the screen before it can display the drawn image, the above theory may not be entirely accurate, considering factors such as latency.

[0123] In this embodiment of the application, during the state switching process of the menu bar constructed by view4, the electronic device changes the frame rate of the screen display content. Figure 4 As an example, with a fixed refresh rate for an electronic device, the refresh rate can be improved by changing the number of frames sent to the screen. Figure 4 The smoothness of the displayed image during the process is shown. Of course, in this embodiment, the adjusted display frame rate is less than or equal to the screen refresh rate.

[0124] As an example of this application, the display frame rate can be set to be different during the display of the electronic device interface and during the switching of the interface.

[0125] Reference Figure 5 (a) in this application describes a frame rate change process provided in an embodiment of the present application.

[0126] During the period when the electronic device displays interface 1, since the content of the interface displayed by the electronic device remains unchanged or changes only slightly, the electronic device displays interface 1 at a low frame rate, wherein the low frame rate can be the lowest frame rate that the electronic device hardware can support, for example, 1Hz.

[0127] When an electronic device receives a user action, in response, it needs to switch the currently displayed interface 1 to interface 2. During the switch, to ensure a faster response and allow the user to quickly see interface 2 on the screen, the electronic device increases the frame rate to a relatively high rate (e.g., 60Hz, 90Hz, or 120Hz) to refresh the transition from interface 1 to interface 2. The illustration uses 60Hz as an example.

[0128] After the electronic device successfully displays interface 2, since the content of interface 2 remains unchanged or changes only slightly, the electronic device continues to reduce the frame rate to a lower frame rate (e.g., the lowest frame rate that the electronic device hardware can support: 1Hz), and the electronic device displays interface 2 at a lower frame rate.

[0129] Of course, the 1Hz, 60Hz, 90Hz and 120Hz in the above examples are just examples to indicate that the frame rate is different during the stable display interface and during the interface switching.

[0130] As another example, it can also be for Figure 5 The frame rate change process is provided in (b) of the document.

[0131] During the period when the electronic device displays interface 1, since the content of the interface displayed by the electronic device remains unchanged or changes only slightly, the electronic device displays interface 1 at a lower frame rate. Among them, the minimum frame rate supported by some electronic devices may be 60 frames, so the lower frame rate can be 60Hz.

[0132] When an electronic device receives a user operation, in response, it needs to switch the currently displayed interface 1 to interface 2. During the switch from interface 1 to interface 2, in order to respond to the switching process more quickly, the electronic device increases the frame rate to a relatively high frame rate (e.g., 90Hz or 120Hz) to refresh the switching process from interface 1 to interface 2 at a higher frame rate (e.g., 90Hz or 120Hz). The illustration uses 120Hz as an example.

[0133] After the electronic device successfully displays interface 2, since the content of interface 2 remains unchanged or changes only slightly, the electronic device continues to reduce the frame rate to a lower frame rate (e.g., 60Hz), and the electronic device displays interface 2 at a lower frame rate.

[0134] In the examples above, "higher" and "lower" are comparisons made before and after the frame rate switch, rather than absolute frame rate values.

[0135] This application will subsequently be subject to Figure 4As shown in (a), during the stable display of the interface, the frame rate is 1Hz as an example. In the above process, while the electronic device is displaying interface 1, since the content of interface 1 remains unchanged or changes only slightly, a lower frame rate can be used to display the content of interface 1 in order to reduce power consumption. During the switch from interface 1 to interface 2, the frame rate is increased, thereby enabling a faster response to user operations and successful display of interface 2. After successfully displaying interface 2, since the content of interface 2 remains unchanged or changes only slightly, the frame rate can be further reduced to reduce power consumption.

[0136] For different applications, the frame rate during the user operation interface switching can be set to different frame rates. For example, when an electronic device displays the interface of some novel applications, the frame rate during the user operation interface switching can be increased to 60Hz, which can respond to user operations and display new interfaces quickly without causing excessive power consumption.

[0137] When an electronic device displays the interface of a map application, the map application may experience changes in map images or menu bars. The frame rate during the interface switching in response to user operations can be increased to 90Hz to improve the user experience without causing excessive power consumption.

[0138] However, in Figure 4 During the switching of different states of the menu bar shown, users have high requirements for the smoothness of the menu bar state changes. A frame rate of 90Hz may not be sufficient to meet the user experience. Therefore, it is necessary to set the frame rate of the above menu bar state change process to a higher level, such as 120Hz.

[0139] In practical implementation, the following settings can be configured from the application perspective:

[0140] In response to user actions on a novel application, the frame rate of the electronic device during the switching of the displayed content of the novel application is 60Hz;

[0141] In response to user actions on map applications, the frame rate of the electronic device during the switching of the displayed content of the map application is 120Hz.

[0142] However, for map applications, setting the frame rate to 120Hz during the execution of any response event triggered by any operation on the map application (e.g., interface switching) may result in excessive power consumption of the electronic device.

[0143] This application also provides a frame rate adjustment method that can adjust the frame rate during the refresh of the application interface from the view dimension.

[0144] Continue with Figure 3As an example, when a user interacts with a menu bar built using View4, triggering a state transition of the View4-built menu bar, the electronic device displays the application's content at a higher frame rate (e.g., 120Hz), thereby improving the user experience of the View4 state transition process.

[0145] When a user action is applied to the display content constructed by other views (e.g., view1, view2, or view3), triggering the electronic device to switch to displaying other content, the electronic device displays the application's content at a lower frame rate (e.g., 60Hz) compared to 120Hz. In this way, it avoids increasing the frame rate to 120Hz during all interface switching triggered by actions applied to the application, thus avoiding excessive power consumption caused by increasing the frame rate to 120Hz.

[0146] It is understood that by setting the frame rate during the execution of user operation response events (usually including the interface switching process) from the perspective of the view, the embodiments of this application can improve the user experience and reduce power consumption compared to setting the frame rate during the execution of user operation response events from the perspective of the application.

[0147] Reference Figure 6 This is a schematic diagram of frame rate changes when adjusting the frame rate from the view dimension, provided in an embodiment of this application.

[0148] like Figure 6 As shown in (a), during the period when the electronic device displays interface 1, the content of the interface displayed by the electronic device remains unchanged or changes only slightly, and the electronic device displays interface 1 at a frame rate of 1Hz.

[0149] When an electronic device receives a user action, this action acts on view4 on interface 1. In response to this user action, the electronic device needs to switch the currently displayed application interface 1 to application interface 2. During the switch from application interface 1 to application interface 2, the electronic device increases the frame rate to 120Hz to display the screen during the interface switch at a 120Hz frame rate. This interface switch includes changes in the content constructed by view4, for example... Figure 4 From Figure 4 The interface shown in (a) is to Figure 4 The process of change between interfaces is shown in (d) in the figure.

[0150] After the electronic device successfully displays interface 2, and the content of interface 2 remains unchanged or changes only slightly, the electronic device reduces the frame rate to 1Hz and displays interface 2 at a frame rate of 1Hz.

[0151] Reference Figure 6As shown in (b), during the period when the electronic device displays interface 1, the content of the interface displayed by the electronic device remains unchanged or changes only slightly, and the electronic device displays interface 1 at a frame rate of 1Hz.

[0152] When an electronic device receives a user action, this action is applied to view2 on interface 1. In response to this action, the electronic device needs to switch the currently displayed application interface 1 to application interface 3. During the switch from application interface 1 to application interface 3, the electronic device increases the frame rate to 60Hz to display the screen during the interface transition. Since users typically don't have a high demand for smoothness in the interface transition triggered by view2, the frame rate can be set relatively low.

[0153] After the electronic device successfully displays interface 3, and the content of interface 3 remains unchanged or changes only slightly, the electronic device reduces the frame rate to 1Hz and displays interface 3 at a frame rate of 1Hz.

[0154] It's understandable that higher frame rates lead to higher power consumption. If we consider increasing the frame rate during interface transitions from an application perspective, to accommodate user perception of changes in the menu bar built with View4, the frame rate would need to be increased to 120Hz. From a power consumption perspective, the frame rate would need to be increased to 60Hz. Even if we increase the frame rate to 90Hz during interface transitions to balance user experience and power consumption, it's still difficult to simultaneously achieve both.

[0155] If we increase the frame rate during screen switching from the view perspective, we can increase the frame rate to 120Hz for screens with higher smoothness requirements, and increase it to 60Hz for screens with lower smoothness requirements. In practice, the screen switching process is usually related to the view on which the user operates. Therefore, we can determine the frame rate to be increased by the view on which the user operates. This way, we can meet the user experience requirements and reduce power consumption.

[0156] Of course, the higher user demand for the state switching process of the menu bar built by View4 is just an example. In actual applications, there may be other scenarios.

[0157] As another example, when an electronic device displays Figure 3 (a) or Figure 3When the interface shown in (c) is displayed, it also includes a map image constructed by view1. Users can also swipe up or down in the map image area to trigger changes in the content of the map image displayed on the electronic device, such as moving the map image in the area corresponding to view1 up or down; users can also pinch or spread their two fingers in the map image area to trigger the electronic device to zoom in or out on the map image in the area corresponding to view1.

[0158] The user's requirements for the smoothness of the map image changes may differ from those for the smoothness of the menu bar changes. For example, the user's requirements for the smoothness of the map image changes are lower than those for the smoothness of the menu bar changes. Therefore, in response to user actions on view1, the frame rate during the map image changes can be set to 90Hz.

[0159] Reference Figure 6 As shown in (c), during the period when the electronic device displays interface 1, the content of the interface displayed by the electronic device remains unchanged or changes only slightly, and the electronic device displays interface 1 at a frame rate of 1Hz.

[0160] When the electronic device receives a user operation, which is applied to view1 on interface 1, the electronic device needs to switch the currently displayed application interface 1 to application interface 4 in response to the user operation. During the switching process, the electronic device increases the frame rate to 90Hz and displays the screen during the interface switching process at this 90Hz frame rate.

[0161] After the electronic device successfully displays interface 4, and the content of interface 4 remains unchanged or changes only slightly, the electronic device reduces the frame rate to 1Hz and displays interface 4 at a frame rate of 1Hz.

[0162] Based on the above understanding, the frame rate adjustment method provided in this application embodiment can set the frame rate during interface switching from the view dimension. For example, operations on different views may trigger different interface switching processes. For interface switching processes where users have high requirements for smoothness, a higher frame rate is set to meet user experience. For interface switching processes where users have low requirements for smoothness, a lower frame rate is set to avoid excessive power consumption. Therefore, the frame rate adjustment method provided in this application embodiment can meet the user's visual experience while avoiding excessive power consumption of electronic devices due to increasing the frame rate.

[0163] Furthermore, in practical applications, user actions on View4 can include not only swiping but also clicking. For example, a swipe on View4 can trigger a state change in the menu bar, while clicking on controls within the menu bar can lead to another interface linked by those controls. The smoothness requirements for menu bar state changes and navigation to linked interfaces differ. Typically, menu bar changes require higher smoothness and a higher frame rate, while the smoothness requirements for switching directly from one interface to another are lower, and a lower frame rate is less necessary. This allows for a balance between user experience and power consumption.

[0164] Therefore, in practical applications, different frame rates can be set not only for the execution process of response events of user operations on different views, but also for the execution process of different response events corresponding to different operations on the same view, so as to avoid excessive power consumption and meet the user's visual experience.

[0165] Reference Figure 7 This refers to the frame rate variation of the execution process of different response events triggered by different operations on the same view, as provided in the embodiments of this application.

[0166] Reference Figure 7 In (a), when the electronic device receives a user action 1 (e.g., a swipe action) acting on view 4, in response to the user action 1, the electronic device needs to switch the currently displayed application interface 1 to the application interface 5. During the switching process from the application interface 1 to the application interface 5, the electronic device increases the frame rate to 120Hz.

[0167] Reference Figure 7 In (b), when the electronic device receives a user action 2 acting on view4 (e.g., a click on a control in the menu bar constructed by view4), in response to the user action 2, the electronic device needs to switch the currently displayed application interface 1 to the application interface 6. During the switching process from the application interface 1 to the application interface 6, the electronic device increases the frame rate to 60Hz.

[0168] The above embodiments all use map applications as examples. In actual applications, they may also be game applications, short video applications, etc. Of course, the frame rate values ​​in the above embodiments are only for illustrative purposes.

[0169] Alternatively, you can set the frame rate for some applications (e.g., map applications, game applications, short video applications, etc.) during the execution of user operation response events according to the view dimension, or you can set the frame rate for some applications (e.g., novel applications, community applications, instant messaging applications) during the execution of user operation response events according to the application dimension.

[0170] As another embodiment of this application, multiple controls may be set on the same view, and the smoothness requirements of the response events corresponding to operations on different controls may also be different. Therefore, in specific implementations, the frame rate during the execution of response events triggered by user operations on different controls of the same view may also be set to be different. This application will not provide examples of each case.

[0171] Reference Figure 8 This is a flowchart illustrating the interface display method provided in an embodiment of this application. This flowchart allows for the selection of different frame rate settings based on different application categories.

[0172] S101, the electronic device detected an input event.

[0173] In this application, the input event can be an input event performed by a user on the touchscreen of an electronic device. This input event can be generated by a click operation, a swipe operation, a double-click operation, etc. The embodiments of this application do not limit the specific form of the user operation.

[0174] S102, determine whether the input event applies to a specific application.

[0175] In this application embodiment, the specific application is an application that improves the frame rate during interface switching in the view dimension.

[0176] Specific applications can be applications of a specific category, such as map applications, game applications, short video applications, etc.

[0177] It can also be a pre-configured application that is compatible with the frame rate adjustment method provided in the embodiments of this application. For example, an application list consisting of multiple application package names can be pre-stored. The applications in the application list can be applications of the specific category mentioned above, or applications of other categories but with a specific interface.

[0178] As an example of an application with a specific interface, a news application displays news events through one view showing the news itself. The size, position, and content of this view can be varied. Another view displays controls such as like, comment, and favorite controls. Other views can display the news publisher, news title, etc. This news application requires a high level of smoothness in the response events to user actions on the view displaying the news itself. Therefore, a higher frame rate can be set for this view, meaning a higher frame rate (e.g., 120Hz) during the user action response events on this view. Conversely, a lower frame rate (e.g., 60Hz) is used during the user action response events on other views. Based on this understanding, this specific application can also be pre-configured with applications from a list of pre-defined applications.

[0179] In this embodiment of the application, if the input event is applied to a specific application, the frame rate during the execution of the response event corresponding to the input event is increased according to the view dimension.

[0180] S103, if the input event is applied to a specific application, then determine whether the frame rate needs to be increased during the current interface switching process based on the view where the input event is applied.

[0181] In this application embodiment, for a specific application, the target frame rate corresponding to each view under that specific application can be set.

[0182] In practical applications, the frame rate during a stable display of the interface may be 1Hz, while the target frame rate for the view may be 60Hz, 90Hz, or 120Hz.

[0183] As an example, one view might have a target frame rate of 60Hz, another 90Hz, and yet another 120Hz. Regardless of which view the user interacts with, the frame rate during screen transitions needs to be increased.

[0184] In addition, since some electronic devices support a minimum frame rate of 60Hz, meaning the frame rate during a stable display may be 60Hz, the target frame rate for the view may be 60Hz, 90Hz, or 120Hz.

[0185] As an example, a view might have a target frame rate of 60Hz, another view might have a target frame rate of 90Hz, and yet another view might have a target frame rate of 120Hz. If the view being interacted with by the user has a target frame rate of 60Hz, then there's no need to increase the frame rate during screen transitions. However, if the view being interacted with by the user has a target frame rate of 90Hz or 120Hz, then there's a need to increase the frame rate during screen transitions.

[0186] S104: If it is determined from the view where the input event is applied that the current interface switching process does not require increasing the frame rate, then the frame rate will not be increased.

[0187] S105, if it is determined that the current interface switching process needs to increase the frame rate based on the view where the input event is applied, the display frame rate is increased to the target frame rate corresponding to the view where the input event is applied through SurfaceFlinger.

[0188] In this embodiment of the application, if the input event is not applied to a specific application, the frame rate during the execution of the response event corresponding to the input event is increased according to the application dimension.

[0189] S106. If the input event is not applied to a specific application, the display frame rate is increased to the target frame rate corresponding to the application to which the input event is applied through SurfaceFlinger.

[0190] To make the above frame rate adjustment method clearer, through Figure 9 A technical architecture diagram describing an embodiment of this application.

[0191] The application layer includes one or more specific applications; of course, it can also include one or more non-specific applications. The application layer may also include a monitoring module, which is used to monitor the applications currently running in the foreground.

[0192] The framework layer includes an input dispatcher, a view, a SurfaceFlinger, and a frame rate decision center. The input dispatcher determines whether a user action applies to a specific application; the view determines the view to which the input event occurred and its target frame rate; the SurfaceFlinger adjusts the display frame rate based on the received target frame rate and sends a Vsync signal to the currently running application based on the display frame rate. This Vsync signal triggers the application to send display content; the SurfaceFlinger also sends display content to the screen. The frame rate decision center determines the target frame rate of the currently running application.

[0193] The kernel layer includes the input layer and the LCD driver. The input layer generates input events based on user actions. The LCD driver receives display content from SurfaceFlinger.

[0194] The hardware layer includes TouchPanel and LCD. TouchPanel detects user actions and sends them to the input field, which in turn receives input events. The LCD acts as the screen to display the received content.

[0195] In the frame rate adjustment method provided in the embodiments of this application:

[0196] The monitoring module can monitor the application currently running in the foreground and send the package name of the application currently running in the foreground to the frame rate decision center. The frame rate decision center can query the target frame rate corresponding to the received application package name and send the target frame rate of the application currently running in the foreground to SurfaceFlinger.

[0197] TouchPanel detects a user action and sends the user action to the input field; the input field generates an input event based on the received input action and sends the input event to the inputdispatcher; the inputdispatcher determines whether the application to which the input event is applied is a specific application.

[0198] If it is not for a specific application, the inputdispatcher sends a command to SurfaceFlinger to increase the frame rate. SurfaceFlinger then sets the display frame rate to the target frame rate of the currently running application based on the command.

[0199] For a specific application, the view stores the target frame rate for each view within that application. The InputDispatcher sends an input event to the view, which determines the view to which the input event occurred, obtains the target frame rate of that view, and sends a frame rate adjustment command to the SurfaceFlinger. This command carries the view's target frame rate. Based on the frame rate adjustment command, the SurfaceFlinger sets the display frame rate to the target frame rate of the view to which the input event occurred.

[0200] In addition, InputDispatcher passes input events to the application through the view, thereby triggering the application to determine the subsequent display content.

[0201] SurfaceFlinger sends a Vsync signal to the application based on the current display frame rate, and the application sends display content to SurfaceFlinger based on the Vsync signal.

[0202] SurfaceFlinger processes the displayed content (e.g., drawing, compositing, rendering, etc.) to enable the display content of LCD display applications.

[0203] It is understood that the frame rate adjustment method provided in this application embodiment, whether setting the frame rate at the application level or the view level, is a system-level frame rate adjustment method, which does not require individual settings for each display interface at the application layer.

[0204] Reference Figure 10 This is a timing diagram provided in this application embodiment for setting the frame rate in the dimension of the view where the input is applied when the input event is applied to a specific application (e.g., a map application).

[0205] First, it should be noted that the dispatchTouchEvent function in view.java pre-stores relation A, which is the target frame rate corresponding to the name of each view in a specific application.

[0206] As an example, relation A includes:

[0207] Figure 3 The target frame rate for view4 in the map application interface shown is 120Hz;

[0208] Figure 3 The target frame rate for view1 in the map application interface shown is 90Hz;

[0209] Figure 3 The target frame rate for view2 in the map application interface shown is 60Hz.

[0210] Figure 3 The target frame rate for view3 in the map application interface shown is 60Hz.

[0211] As mentioned earlier, the target frame rate can also be related to the operation type. When different target frame rates need to be set for different operations on the same view, the target frame rate for one or more operations on each view in the specific application can be pre-stored in the dispatchTouchEvent function in view.java. As another example of relation A, relation A includes:

[0212] Figure 3 The target frame rate for the swipe operation on view4 in the map application interface shown is 120Hz;

[0213] Figure 3 The target frame rate for the click operation on view4 in the map application interface shown is 60Hz.

[0214] Figure 3 The target frame rate for the operation on view1 in the map application interface shown is 90Hz.

[0215] Figure 3 The target frame rate for the operation on view2 in the map application interface shown is 60Hz.

[0216] Figure 3 The target frame rate for the operation on view3 in the map application interface shown is 60Hz.

[0217] Of course, the above is only for illustrative purposes. In actual applications, relation A may store target frame rates under more conditions. For example, the center position of the view can be added as a condition to set the target frame rate, and different controls in the view can be added as conditions to set the target frame rate. The target frame rates under multiple conditions set at the view level are all within the scope of setting the target frame rate from the view level provided in this application embodiment, and this application will not list them all. Of course, the above conditions can be set according to the actual situation. Regardless of the conditions set, this application embodiment adjusts the frame rate from the view level at the system level.

[0218] Additionally, the `dispatchTouchEvent` function in `view.java` can record relationship B when switching between different screens on an electronic device. Relationship B records the relationship between the name of the view in the most recently switched screen and the position of the view. Of course, the view name is just an example; in practical applications, different views can be distinguished by other unique identifiers.

[0219] S201, The input event was detected. The event type of the input event can be down.

[0220] Typically, the input events corresponding to a swipe action include the down, move, and up events. Of course, other user actions may also include a down event; for example, the input events corresponding to a click action include both down and up events.

[0221] S202, input sends the detected input event to Inputdispatcher.

[0222] In this embodiment of the application, when sending a detected input event to the InputDispatcher, the event type corresponding to the input event (down event) is also carried, along with the coordinates corresponding to the down event. The coordinates corresponding to the down event are the coordinates of the user's touch point on the screen.

[0223] S203. After receiving an input event, if the InputDispatcher determines that the event type of the input event is a down event, it determines the application that the input event applies to based on the coordinates, and identifies that the application is a specific application.

[0224] S204, After receiving an input event, the InputDispatcher sends an input event to the view, carrying the event type and coordinates of the input event.

[0225] S205, when the input event is a down event, the view uses the dispatchTouchEvent function in the view to find the name of the view corresponding to the coordinates of the down event from relation B: view4.

[0226] S206, use the dispatchTouchEvent function in the view to query the target frame rate corresponding to view4 in relation A.

[0227] In this embodiment of the application, the view can store the target frame rate corresponding to each view in a specific application.

[0228] S207, the view sends an adjustment command to SurfaceFlinger, which carries the target frame rate corresponding to view4.

[0229] S208, SurfaceFlinger sets the display frame rate to the target frame rate through the notifyVrrBoost function.

[0230] S209, an input event was detected. The event type of this input event is move, and this event can carry the coordinates of the touch point.

[0231] In this embodiment of the application, the user's swipe operation includes a move event after the down event.

[0232] S210, the input sends the detected input event to the InputDispatcher. It also carries the corresponding move event and its coordinates. The coordinates of the move event are the coordinates of the user's touch point on the screen.

[0233] S211, InputDispatcher sends an input event to the view when the input event type is move. It carries the event type (move event) and the coordinates of the move event.

[0234] S212, after the view receives an input event, if the input event type is move, it sends an input event to the map application. This input event carries the event type and coordinates.

[0235] S213, The map application determines the content to be displayed based on the event type and coordinates corresponding to the input event.

[0236] Reference Figure 4 (a) to Figure 4 As shown in (c), when the input event is a move event in a swipe operation, the content and position of the menu bar constructed by View4 may change during state switching, thus the content displayed on the screen changes in real time. The map application running in the foreground can determine the content to be displayed based on the coordinates carried by the input event.

[0237] S214, after setting the display frame rate to the target frame rate, SurfaceFlinger will send a Vsync signal to the map application running in the foreground according to the target frame rate. This Vsync signal is used to trigger the upper-layer application to send down the display content.

[0238] S215, after receiving the Vsync signal, the map application sends the display content to SurfaceFlinger according to the Vsync signal.

[0239] Subsequently, SurfaceFlinger triggers the sending of the received display content to the screen. Of course, before it is actually sent to the screen for display, it will undergo drawing, compositing, and rendering.

[0240] As SurfaceFlinger sends Vsync signals according to the target frame rate, the map application will send and display content according to the Vsync signals, thereby improving the smoothness of the screen.

[0241] It should be noted that as the user performs the swipe operation, the upper-layer application needs to update the displayed content in real time, that is, to repeatedly execute S209 to S215 until the user releases the swipe.

[0242] Of course, in some examples, as the user's swipe action ends and the interface transition is complete, when the input event received by the view is an up event, a command to restore the frame rate can also be sent to SurfaceFlinger, that is, to trigger SurfaceFlinger to set the frame rate back to a lower 1Hz or 60Hz.

[0243] In other examples, the interface may not be fully updated after the user's swipe ends. For instance, if the user's swipe occurs on a map image area constructed by view1 and the swipe speed is relatively fast, the map image will continue to be swiped based on the swipe speed before the user releases their finger. In this case, the moment when the map image swiping ends can be determined based on the swipe speed. At the moment when the map image swiping ends, a command to restore the frame rate can be sent to SurfaceFlinger, triggering SurfaceFlinger to set the frame rate back to a lower 1Hz or 60Hz.

[0244] This application does not restrict the process executed when the recovery frame rate is 1Hz or 60Hz.

[0245] Reference Figure 11 This is a timing diagram provided in this application embodiment for setting the frame rate by the dimension of the application on which the input event is applied, when the input event acts on a non-specific application (e.g., a novel application).

[0246] It should be noted that the frame rate decision center stores the target frame rate for each application's application package name.

[0247] S301, the monitoring module detected that the novel application has switched to running in the foreground.

[0248] S302, after the monitoring module detects that the novel application has switched to the foreground, it sends the application package name of the novel application that has switched to the foreground to the frame rate decision center.

[0249] S303, the frame rate decision center queries the target frame rate corresponding to the received novel application's application package name from the target frame rates of each stored application package name.

[0250] S304, the frame rate decision center sends the queried target frame rate to SurfaceFlinger.

[0251] S305, SurfaceFlinger records the received target frame rate.

[0252] As can be understood from the descriptions in S301 to S305, SurfaceFlinger can record the target frame rate of the currently running application in the foreground. When the application running in the foreground is switched to another application, SurfaceFlinger will also update the recorded display frame rate to the target frame rate of the application running in the foreground after the switch.

[0253] When a user action is performed on any interface of application A, the following steps are executed:

[0254] S306, an input event was detected. The event type of this input event is down.

[0255] S307, input sends the detected input event to Inputdispatcher. This event carries the event type and coordinates.

[0256] S308, InputDispatcher determines the application of the input event based on the coordinates when the input event type is down, and determines that the application is not a specific application.

[0257] S309, Inputdispatcher calls the vrrHook function in Inputdispatcher to generate instructions to increase the frame rate.

[0258] S310, InputDispatcher sends a command to SurfaceFlinger to increase the frame rate through the NotifyBoostRefreshrate function in InputDispatcher.

[0259] S311: After receiving a command to increase the frame rate, SurfaceFlinger will adjust the displayed frame rate to the latest recorded target frame rate.

[0260] S312, an input event was detected. This input event is a move event. This event carries the coordinates of the move event.

[0261] In this embodiment of the application, the user's swipe operation includes a move event after the down event.

[0262] S313, the input sends the detected input event to the InputDispatcher. It also carries the event type corresponding to the input event: move event and the coordinates corresponding to the move event. The coordinates corresponding to the move event are the coordinates of the user's touch point on the screen.

[0263] S314, InputDispatcher sends an input event to the view when the input event type is move. It carries the event type: move and coordinates.

[0264] S315, after the view receives an input event, if the input event is a move event, it sends an input event to the map application. This input event carries the event type and coordinates.

[0265] S316, The map application determines the content to be displayed based on the event type and coordinates corresponding to the input event.

[0266] In the S317, after setting the display frame rate to the target frame rate, SurfaceFlinger sends a Vsync signal to the foreground map application according to the target frame rate. The Vsync signal is sent at the same frequency as the target frame rate. The Vsync signal is used to trigger the upper-layer application to send display content at a certain frequency.

[0267] S318, the upper-layer application sends the display content to SurfaceFlinger according to the Vsync signal.

[0268] Similarly, as the user performs a swipe operation, the application needs to update the displayed content in real time, that is, to cycle through S312 to S318 until the user releases their hand.

[0269] Currently, the process of restoring the display frame rate in SurfaceFlinger can be referenced. Figure 10 The relevant descriptions in the document will not be repeated here.

[0270] It is understandable that regardless of whether the application to which the input event applies is a specific application, S301 to S305 will be executed, and SurfaceFlinger will record the target frame rate of the application running in the foreground.

[0271] When the input event is applied to a specific application, SurfaceFlinger will first receive the application's target frame rate, and then receive the target frame rate corresponding to the view. For a clearer understanding of SurfaceFlinger's execution steps, refer to... Figure 12 The timing diagram shown.

[0272] Figure 12 In the middle, S301 to S305 can be referred to Figure 11 As shown, S201 to S215 can be referred to Figure 10As shown, after executing S305, SurfaceFlinger does not adjust to the target frame rate corresponding to the application. Instead, after S207, when SurfaceFlinger receives an adjustment instruction carrying the target frame rate of the view, it adjusts the frame rate to the target frame rate corresponding to the view in the adjustment instruction, rather than the target frame rate of the application recorded in S205.

[0273] Furthermore, in practical applications, the execution result of S203 and whether S204 is executed are not specifically related. That is, S204 is executed regardless of whether the application affected by the input event in S203 is a specific application. To avoid SurfaceFlinger receiving two adjustment instructions, in this embodiment, the view can be set to store only the target frame rate of each view in a specific application. If it is not a specific application, the target frame rate cannot be found when executing S206, that is, S207 cannot be executed, and the target frame rate cannot be set from the view dimension.

[0274] Reference Figure 13 As shown, S301 to S318 can be referred to Figure 11 As shown, S204 to S207 can be referred to Figure 10 As shown.

[0275] After S308, S204 to S206 are executed on one hand, and S309 to S311 are executed on the other.

[0276] Since the target frame rate for views that are not specific to any application is not stored in the view, the result of S206 is that the target frame rate corresponding to the view name cannot be found. Therefore, S207 is not executed. Thus, SurfaceFlinger will adjust the frame rate to the target frame rate for the application dimension recorded in S305 according to the instructions in S310.

[0277] In the example above, no target frame rate was set for different operations within the same view. In practical applications, operation type determination can be added to the InputDispatcher. That is, after receiving a down event, it's not immediately clear whether it belongs to a specific application. After receiving the next event following the down event (e.g., an input event with the first event type being move), the specific operation is determined based on the next event. For example, if the next input event after the down event is an up event, it's a click operation; if the next input event after the down event is a move event, it's a swipe operation. After determining the operation type, it's then determined whether it belongs to a specific application. In the case of a specific application, the view records the target frame rate for different operations within the same view, thus allowing the target frame rate to be determined based on the view to which the input event applies and the corresponding operation type. Of course, the above process for determining the operation type is only an example.

[0278] Reference Figure 14 Another frame rate adjustment method provided in this application embodiment includes:

[0279] Display the first interface of the first application, the first interface including a first view and a second view;

[0280] The first operation acting on the first interface was detected;

[0281] In response to the first operation, switch from the first interface to the first target interface of the first application;

[0282] Wherein, when the first operation is performed on the first view, the image frames during the switch from the first interface to the first target interface are displayed at a first frame rate, and the first target interface is the second interface;

[0283] When the first operation is applied to the second view, the image frames during the switch from the first interface to the first target interface are displayed at a second frame rate. The first target interface is the third interface, and the second frame rate is different from the first frame rate.

[0284] Reference Figure 14 As shown in (a), the electronic device displays a first interface of a first application, which may be a map application. The first view in the first application is used to construct a menu bar, and the second view is used to construct a map image.

[0285] Reference Figure 14 As shown in (b), in response to an upward swipe operation on the first view, the electronic device displays... Figure 14The second interface shown in (b) is generated based on the same activity as the first interface. The center position, size, and displayed content of the first view in the first interface and the first view in the second interface change. During the switch from the first interface to the second interface, the electronic device displays image frames of the process at a second frame rate (e.g., 120Hz).

[0286] Reference Figure 14 As shown in (c), in response to an upward swipe operation on the second view, the electronic device displays... Figure 14 The second interface shown in (b) is generated based on the same activity as the first interface. The center position and size of the second view in the first interface and the second view in the second interface remain unchanged, but the specific content displayed changes. That is, the map is shifted upwards. During the switch from the first interface to the second interface, the electronic device displays the image frames of that process at a third frame rate (e.g., 90Hz).

[0287] In addition, the swipe-up operation in the above examples is only one example of the first operation, and the views in the above examples are also only one example of the views.

[0288] The following situations may also exist:

[0289] When the first operation is a first gesture operation and is applied to the first view, the image frames during the switch from the first interface to the first target interface are displayed at a first frame rate. The first target interface is the second interface, and the first frame rate is specifically the ninth frame rate.

[0290] When the first operation is a first gesture operation and is applied to the second view, the image frames during the switch from the first interface to the first target interface are displayed at the second frame rate. The first target interface is the third interface, and the second frame rate is specifically the tenth frame rate.

[0291] When the first operation is a third gesture operation and is applied to the first view, the image frames during the switch from the first interface to the first target interface are displayed at a first frame rate. The first target interface is the eleventh interface, and the first frame rate is specifically the eleventh frame rate.

[0292] When the first operation is the fourth gesture operation and is applied to the second view, the image frames during the switch from the first interface to the first target interface are displayed at the second frame rate. The first target interface is the twelfth interface, and the second frame rate is specifically the twelfth frame rate.

[0293] For example, in the example above, the third and fourth gesture operations could also be click operations.

[0294] The key point of this application's embodiments is that operations on different views may trigger different interface switching processes, and the frame rate during the interface switching process is related to the view on which the operation is performed. Of course, the frame rate during the interface switching corresponding to operations on any two views may be the same or different.

[0295] As another embodiment of this application, displaying the first interface of the first application includes: displaying the first interface at a third frame rate, wherein the third frame rate is less than or equal to the first frame rate and the third frame rate is less than or equal to the second frame rate;

[0296] After switching from the first interface to the first target interface of the first application, the method further includes:

[0297] The first target interface is displayed at the third frame rate.

[0298] In this application, during the period when the electronic device stably displays the first interface, the second interface, and the third interface (or, of course, during the period when any interface is stably displayed), the interface can be displayed at a lower third frame rate. The third frame rate can be the minimum frame rate supported by the electronic device (e.g., 1Hz or 60Hz), and the third frame rate is less than the first frame rate and / or less than the second frame rate.

[0299] In another embodiment of this application, the method further includes:

[0300] Display the fourth interface of the second application, which includes the third view and the fourth view;

[0301] A second operation was detected acting on the third or fourth view of the fourth interface;

[0302] In response to the second operation, image frames during the switch from the fourth interface to the second target interface of the second application are displayed at a fourth frame rate.

[0303] In this application, the second application can be an application that does not require frame rate adjustment from the view perspective, such as a novel application, and the fourth interface can be any interface of the novel application. The second operation can be any operation that triggers the electronic device to display another interface of the current application. In practical applications, the second application adjusts the frame rate from the application perspective. The target frame rate corresponding to the second application is the fourth frame rate.

[0304] As another embodiment of this application, the fourth interface displaying the second application includes:

[0305] The fourth interface is displayed at the third frame rate, which is the minimum frame rate that the electronic device can support. The third frame rate is less than or equal to the fourth frame rate.

[0306] After switching from the fourth interface to the second target interface of the second application, the method further includes:

[0307] The second target interface is displayed at the third frame rate.

[0308] In another embodiment of this application, the method further includes:

[0309] The fifth interface of the first application is displayed. The fifth interface includes a fifth view, and the fifth view includes a first control and a second control.

[0310] A third operation acting on the fifth view was detected;

[0311] In response to the third operation, switch from the fifth interface to the third target interface of the first application;

[0312] In this case, when the third operation is applied to the first control, the image frames during the switch from the fifth interface to the third target interface are displayed at the fifth frame rate. The third target interface is the sixth interface.

[0313] When the third operation is applied to the second control, the image frames during the switch from the fifth interface to the third target interface are displayed at the sixth frame rate. The third target interface is the seventh interface, and the sixth frame rate is different from the fifth frame rate.

[0314] Continue with Figure 14 As an example, operations on different controls in the same view may correspond to different target frame rates. For instance, operations on different controls in the first view may trigger the display of different interfaces, and the frame rate during the switch between different interfaces may be different.

[0315] In another embodiment of this application, the first operation is a swipe operation, the first target interface and the first interface are generated based on the same Activity, and the first target interface is the interface displayed after the swipe operation is released.

[0316] In another embodiment of this application, the first application is a map application, a game application, or a short video application, and the second application is a novel application.

[0317] In another embodiment of this application, the method further includes:

[0318] Display the eighth interface of the first application, which includes the sixth view;

[0319] A fourth operation acting on the sixth view was detected;

[0320] In response to the fourth operation, switch from the eighth interface to the fourth target interface of the first application;

[0321] In the case where the fourth operation is the first gesture operation, the image frames during the switch from the eighth interface to the fourth target interface are displayed at the seventh frame rate, and the fourth target interface is the ninth interface.

[0322] When the fourth operation is the second gesture operation, the image frames during the switch from the eighth interface to the fourth target interface are displayed at the eighth frame rate. The fourth target interface is the tenth interface, and the eighth frame rate is different from the seventh frame rate.

[0323] Reference Figure 15 The first gesture operation is an upward swipe operation. The ninth and eighth interfaces are generated based on the same activity. The fourth target interface is the interface displayed after the swipe operation is released. The second gesture operation is a click operation. The tenth and eighth interfaces are generated based on different activities. The seventh frame rate (the illustration uses 120Hz as an example) is greater than the eighth frame rate (the illustration uses 60Hz as an example).

[0324] As another embodiment of this application, displaying the eighth interface of the first application includes: displaying the eighth interface at a third frame rate (e.g., 1Hz or 60Hz), where the third frame rate is less than or equal to the seventh frame rate and the third frame rate is less than or equal to the eighth frame rate.

[0325] After switching from the eighth interface to the fourth target interface of the first application, the method further includes:

[0326] The fourth target interface is displayed at the third frame rate.

[0327] In another embodiment of this application, the third frame rate is the minimum frame rate that the electronic device can support, and the third frame rate is less than the seventh frame rate and / or less than the eighth frame rate.

[0328] In addition, any two operations in the embodiments of this application may be the same or different unless otherwise specified; any two frame rates in the above examples may be the same or different unless otherwise specified; any two interfaces in the above examples may be the same or different unless otherwise specified; any two views in the above examples may be the same or different unless otherwise specified.

[0329] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0330] This application also provides a computer-readable storage medium storing a computer program that, when run on an electronic device, can implement the steps in the above-described method embodiments.

[0331] This application also provides a computer program product that, when run on an electronic device or a wireless router, enables the electronic device to perform the steps described in the various method embodiments above.

[0332] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying the computer program code to the first device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0333] This application also provides a chip, which includes a processor coupled to a memory. The processor calls a computer program stored in the memory to implement the steps of any method embodiment of this application. The chip can be a single chip or a chip module composed of multiple chips.

[0334] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0335] Those skilled in the art will recognize that the units and method steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0336] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A frame rate adjustment method, characterized by, The method is applied to an electronic device, and the method comprises: displaying a first interface of a first application, the first interface comprising a first view and a second view; detecting a first operation acting on the first interface; in response to the first operation, switching from the first interface to a first target interface of the first application; wherein, in the case where the first operation acts on the first view, displaying image frames during the switching from the first interface to the first target interface at a first frame rate, the first target interface being a second interface; in the case where the first operation acts on the second view, displaying image frames during the switching from the first interface to the first target interface at a second frame rate, the first target interface being a third interface, the second frame rate being different from the first frame rate.

2. The method of claim 1, wherein, The displaying of the first interface of the first application comprises: displaying the first interface at a third frame rate, the third frame rate being less than or equal to the first frame rate, and the third frame rate being less than or equal to the second frame rate; after switching from the first interface to the first target interface of the first application, the method further comprises: displaying the first target interface at the third frame rate.

3. The method of claim 2, wherein, The third frame rate is the minimum frame rate that can be supported by the electronic device, and the third frame rate is less than the first frame rate and / or the third frame rate is less than the second frame rate.

4. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: displaying a fourth interface of a second application, the fourth interface comprising a third view and a fourth view; detecting a second operation acting on the third view or the fourth view of the fourth interface; in response to the second operation, displaying image frames during the switching from the fourth interface to a second target interface of the second application at a fourth frame rate.

5. The method of claim 4, wherein, The displaying of the fourth interface of the second application comprises: displaying the fourth interface at a third frame rate, the third frame rate being the minimum frame rate that can be supported by the electronic device, and the third frame rate being less than or equal to the fourth frame rate; after switching from the fourth interface to the second target interface of the second application, the method further comprises: displaying the second target interface at the third frame rate.

6. The method according to any one of claims 1 to 5, characterized in that, The method further comprises: displaying a fifth interface of the first application, the fifth interface comprising a fifth view, the fifth view comprising a first control and a second control; detecting a third operation acting on the fifth view; in response to the third operation, switching from the fifth interface to a third target interface of the first application; wherein, in the case where the third operation acts on the first control, displaying image frames during the switching from the fifth interface to the third target interface at a fifth frame rate, the third target interface being a sixth interface; in the case where the third operation acts on the second control, displaying image frames during the switching from the fifth interface to the third target interface at a sixth frame rate, the third target interface being a seventh interface, the sixth frame rate being different from the fifth frame rate.

7. The method according to any one of claims 1 to 6, characterized in that, The method further comprises: displaying an eighth interface of the first application, the eighth interface comprising a sixth view; detecting a fourth operation acting on the sixth view; In response to the fourth operation, switching from the eighth interface to a fourth target interface of the first application; In a case where the fourth operation is a first gesture operation, displaying image frames during switching from the eighth interface to the fourth target interface at a seventh frame rate, the fourth target interface being a ninth interface; In a case where the fourth operation is a second gesture operation, displaying image frames during switching from the eighth interface to the fourth target interface at an eighth frame rate, the fourth target interface being a tenth interface, the eighth frame rate being different from the seventh frame rate.

8. The method of claim 7, wherein, The first gesture operation is a sliding operation, and the ninth interface and the eighth interface are generated based on a same activity; the second gesture operation is a clicking operation, and the tenth interface and the eighth interface are generated based on different activities; The seventh frame rate is greater than the eighth frame rate.

9. The method according to any one of claims 1 to 8, characterized in that, The first operation is a sliding operation, the first target interface and the first interface are generated based on a same activity, and the first target interface is an interface displayed after the sliding operation is released.

10. The method of claim 4 or 5, wherein, The first application is a map application, a game application, or a short video application, and the second application is a novel application.

11. A frame rate adjustment method, characterized by, The method is applied to an electronic device, and the method comprises: displaying an eighth interface of a first application, the eighth interface comprising a sixth view; detecting a fourth operation acting on the sixth view; in response to the fourth operation, switching from the eighth interface to a fourth target interface of the first application; in a case where the fourth operation is a first gesture operation, displaying image frames during switching from the eighth interface to the fourth target interface at a seventh frame rate, the fourth target interface being a ninth interface; in a case where the fourth operation is a second gesture operation, displaying image frames during switching from the eighth interface to the fourth target interface at an eighth frame rate, the fourth target interface being a tenth interface, the eighth frame rate being different from the seventh frame rate.

12. The method of claim 11, wherein, The first gesture operation is a sliding operation, and the ninth interface and the eighth interface are generated based on a same activity, and the fourth target interface is an interface displayed after the sliding operation is released. The second gesture operation is a clicking operation, and the tenth interface and the eighth interface are generated based on different activities; The seventh frame rate is greater than the eighth frame rate.

13. The method of claim 11 or 12, wherein, The display of the eighth interface of the first application comprises: displaying the eighth interface at a third frame rate, the third frame rate being less than or equal to the seventh frame rate, and the third frame rate being less than or equal to the eighth frame rate; after switching from the eighth interface to the fourth target interface of the first application, the method further comprises: displaying the fourth target interface at the third frame rate.

14. The method of claim 13, wherein, The third frame rate is a minimum frame rate that can be supported by the electronic device, and the third frame rate is less than the seventh frame rate and / or the third frame rate is less than the eighth frame rate.

15. An electronic device, comprising: An electronic device comprising one or more processors and one or more memories; wherein the one or more memories are coupled to the one or more processors, the one or more memories are configured to store a computer program that, when executed by the one or more processors, causes the electronic device to perform the method of any one of claims 1-14.

16. A chip system applied to an electronic device, the chip system comprising one or more processors, characterized in that, The processor is configured to invoke computer instructions to cause the electronic device to perform the method of any one of claims 1-14.

17. A computer readable storage medium comprising a computer program, characterized in that, The computer program, when run on an electronic device, causes the electronic device to perform the method of any one of claims 1-14.

Images