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

Abstract

The present application relates to the technical field of electronic devices. Provided are a frame rate adjustment method, an electronic device, a chip system and a storage medium. In the method, an application interface displayed by an electronic device may comprise a plurality of views, and when user operations are performed on different views, frame rates during the execution of response events corresponding to the user operations may be determined on the basis of the views on which the user operations are performed. A response event may be a switching process of switching from the current interface to another interface, which process is triggered by a user operation. For the user operations performed on different views, the frame rates during the execution of the response events may also be different. In this way, frame rates during the execution of some response events with high smoothness requirements may be adjusted to relatively high frame rates, so as to improve the smoothness during interface switching; and frame rates during the execution of some response events with low smoothness requirements may be adjusted to relatively low frame rates, so as to avoid excessive power consumption caused by increasing the frame rates.

Description

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

[0001] The present application claims priority to the Chinese patent application No. 202411097843.8, filed on August 9, 2024, and entitled "Frame rate adjustment method, electronic device, chip system and storage medium", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the technical field of electronic devices, and in particular to a frame rate adjustment method, an electronic device, a chip system and a storage medium. BACKGROUND

[0003] With the increasing intelligence of electronic devices and the increasing requirements of people on electronic devices, the functions provided by electronic devices are also increasing, and for some portable electronic devices, reducing power consumption is also becoming more and more important.

[0004] During the use of the electronic device by the user, even for non-video applications, some scenarios with high requirements on picture smoothness often occur, for example, in a map application, the movement process of the map image triggered by the user's sliding operation on the map image; in some applications, the state change process of the menu bar triggered by the user's sliding operation on the menu bar. In order to improve the user experience, the display frame rate during the running of these applications by the electronic device can be increased, however, the increase of the frame rate will increase the power consumption. SUMMARY

[0005] The present application provides a frame rate adjustment method, an electronic device, a chip system and a storage medium, which can improve picture smoothness while reducing power consumption.

[0006] To achieve the above-mentioned purpose, the first aspect of the present application provides a frame rate adjustment method, which adopts the following technical solution:

[0007] displaying a first interface of a first application, the first interface including a first view and a second view;

[0008] detecting a first operation acting on the first interface;

[0009] in response to the first operation, switching from the first interface to a first target interface of the first application;

[0010] wherein, in the case that 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, and the first target interface is the second interface;

[0011] In a case where the first operation acts on the second view, display image frames during switching from the first interface to a 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.

[0012] In the present application, when a user operates different views of the same interface, the electronic device can be triggered to switch to different interfaces. During the process of switching different interfaces, the user's demand for picture fluency can be different. For example, the user's demand for picture fluency of the interface switching process triggered by the operation on some views is higher, and the user's demand for picture fluency of the interface switching process triggered by the operation on other views is not high. In order to meet the user's demand for fluency and not to cause high power consumption, the frame rate of some interface switching processes with higher demand for picture fluency and the frame rate of some interface switching processes with lower demand for picture fluency can be set to different frame rates. For example, the frame rate of some interface switching processes with higher demand for picture fluency can be set to be greater than the frame rate of some interface switching processes with lower demand for picture fluency.

[0013] In the present application, in the scenario where the user operates different views of the same interface to realize interface switching, the appropriate frame rate can be selected according to the demand of different interface switching processes to display the image frames in the interface switching process, instead of displaying the image frames displayed in the interface switching process based on a unified frame rate. The selection of the frame rate is more flexible, and the power consumption can be reduced.

[0014] Specifically, since different interface switching processes have different demands for picture fluency, the appropriate frame rate can be selected according to the demand of different interface switching processes to display the image frames in the interface switching process, which can better meet the user's demand. Compared with the way of displaying the image frames displayed in the interface switching process based on the same frame rate in the traditional scheme, the power consumption can be reduced.

[0015] As an implementation manner of the first aspect, displaying 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.

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

[0017] Displaying the first target interface at the third frame rate.

[0018] In this application, during the stable display of the interface (non-switching interface period), the content of the interface does not change or changes little, so the frame rate during the stable display of the interface can be set to be low, thereby reducing power consumption. Specifically, the frame rate during the stable display of the interface can be set to be less than or equal to the frame rate during the interface switching period, thereby making the power consumption of the electronic device during the stable display of the interface small. The frame rate during the interface switching period can be set according to the user's demand for the smoothness of the picture during the interface switching period. For example, when the user's demand for the smoothness of the picture during the interface switching process is high, the set frame rate is high, and when the user's demand for the smoothness of the picture during the interface switching process is low, the set frame rate is low.

[0019] 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 the third frame rate is less than the second frame rate.

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

[0021] As another implementation of the first aspect, the method further includes:

[0022] displaying a fourth interface of the second application, the fourth interface including a third view and a fourth view;

[0023] detecting a second operation on the third view or the fourth view of the fourth interface;

[0024] in response to the second operation, displaying image frames during switching from the fourth interface to a second target interface of the second application at a fourth frame rate;

[0025] wherein, in the case where the second operation is on the third view, the second target interface is a fifth interface;

[0026] in the case where the second operation is on the fourth view, the second target interface is a sixth interface.

[0027] In this application, for some applications whose users have low demand for the smoothness of the picture during the interface switching process, the operations on the views of the applications can be set to display the image frames during the interface switching process at the same frame rate, thereby flexibly setting different frame rate switching strategies for different applications.

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

[0029] displaying the fourth interface at a third frame rate, the third frame rate being the minimum frame rate that the electronic device can support, and the third frame rate being less than or equal to the fourth frame rate;

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

[0031] displaying the second target interface at the third frame rate.

[0032] In this application, the frame rate of the electronic device during stable display of the interface can be set as the minimum frame rate that the electronic device can support, and the minimum frame rate that different electronic devices can support can be different. When the minimum frame rate is sufficient to meet the user's demand for picture smoothness 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 demand for picture smoothness during the interface switching process, the fourth frame rate can be set to be greater than the third frame rate, so that the power consumption of the electronic device can be reduced while meeting the user's demand for picture smoothness during the interface switching process.

[0033] As another implementation of the first aspect, the method further includes:

[0034] displaying a fifth interface of the first application, the fifth interface including a fifth view, the fifth view including a first control and a second control;

[0035] detecting a third operation acting on the fifth view;

[0036] in response to the third operation, switching from the fifth interface to a third target interface of the first application;

[0037] wherein, in a case where the third operation acts on the first control, displaying image frames during switching from the fifth interface to the third target interface at a fifth frame rate, the third target interface being a sixth interface;

[0038] in a case where the third operation acts on the second control, displaying image frames during 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.

[0039] In this application, when the user's operation acts on different controls of the same view, the electronic device can be triggered to switch to different interfaces. During the process of switching different interfaces of the electronic device, the user's demand for picture smoothness can be different. For example, the user's demand for picture smoothness during the interface switching process triggered by the operation on some controls is higher, and the user's demand for picture smoothness during the interface switching process triggered by the operation on other controls is not high. In order to meet the user's demand for smoothness and not cause high power consumption, the frame rate of some interface switching processes with high picture smoothness demand and the frame rate of some interface switching processes with low picture smoothness demand can be set to different frame rates. For example, the frame rate of some interface switching processes with high picture smoothness demand can be set to be greater than the frame rate of some interface switching processes with low picture smoothness demand.

[0040] As another implementation form of the first aspect, the method further includes:

[0041] displaying an eighth interface of the first application, the eighth interface including the sixth view;

[0042] detecting a fourth operation acting on the sixth view;

[0043] in response to the fourth operation, switching from the eighth interface to a fourth target interface of the first application;

[0044] wherein, 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;

[0045] 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.

[0046] In the present application, when different user operations act on the same view, the electronic device can be triggered to switch to different interfaces. During the process of switching different interfaces, the user's demand for picture fluency can be different. For example, the picture fluency demand of the interface switching process triggered by some gesture operations is relatively high, and the picture fluency demand of the interface switching process triggered by some other gesture operations is not high. In order to meet the user's demand for fluency and not cause high power consumption, the frame rate of some interface switching processes with high picture fluency demand and the frame rate of some interface switching processes with low picture fluency demand can be set to different frame rates. For example, the frame rate of some interface switching processes with high picture fluency demand can be set to be greater than the frame rate of some interface switching processes with low picture fluency demand.

[0047] As another implementation form of the first aspect, the first gesture operation is a sliding operation, and the ninth interface and the eighth interface are generated based on the 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.

[0048] In the present application, a sliding operation usually triggers at least one of the changes of the position, size or contained display content of a view, which is usually not caused by activity change. The change of the above-mentioned view is usually a gradual change process with the user's sliding operation, and the picture is relatively fluent when the frame rate of the process is high, otherwise it is easy to appear lag. A clicking operation usually triggers another activity corresponding to the interface of the control linked by the clicking operation. The interface change process is usually a process of directly switching to another interface, and the frame rate of the process can be relatively low.

[0049] As another implementation form of the first aspect, 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.

[0050] In the present application, when the first operation is a sliding operation, at least one of the position, size or contained display content of a view is generally triggered to change, the change is a change of the view in an interface generated by the same activity, and the view gradually changes as the user slides the operation. The first target interface triggered to be displayed by the sliding operation is not the interface that gradually changes during the user sliding operation, but the interface to be stably displayed after the sliding operation is released. By setting the same first frame rate during the interface switching process before the stably displayed interface, the picture fluency of the interface switching process is consistent from the user's perspective, and the user experience is better.

[0051] As another implementation form of 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.

[0052] The second aspect of the present application provides a frame rate adjustment method, which adopts the following technical scheme:

[0053] displaying an eighth interface of the first application, the eighth interface including a sixth view;

[0054] detecting a fourth operation acting on the sixth view;

[0055] in response to the fourth operation, switching from the eighth interface to a fourth target interface of the first application;

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

[0057] In the case where the fourth operation is a second gesture operation, image frames during switching from the eighth interface to the fourth target interface are displayed at an eighth frame rate, the fourth target interface is a tenth interface, and the eighth frame rate and the seventh frame rate are different.

[0058] In the present application, when different user operations act on the same view, the electronic device can be triggered to switch to different interfaces. During the process of switching different interfaces, the user's demand for picture fluency can be different. For example, the picture fluency demand of the interface switching process triggered by some gesture operations is higher, and the picture fluency demand of the interface switching process triggered by some other gesture operations is not high. In order to meet the user's demand for fluency and not to cause high power consumption, the frame rate of some interface switching processes with high picture fluency demand and the frame rate of some interface switching processes with low picture fluency demand can be set to different frame rates. For example, the frame rate of some interface switching processes with high picture fluency demand can be set to be greater than the frame rate of some interface switching processes with low picture fluency demand.

[0059] As an implementation manner of the second aspect, the first gesture operation is a sliding operation, the ninth interface and the eighth interface are generated based on the 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, the tenth interface and the eighth interface are generated based on different activities; and the seventh frame rate is greater than the eighth frame rate.

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

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

[0062] Displaying the fourth target interface at the third frame rate.

[0063] As another implementation manner of the second aspect, 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 seventh frame rate and / or the third frame rate is less than the eighth frame rate.

[0064] In a third aspect, an electronic device is provided, including a processor configured to invoke a computer program stored in a memory to implement the method of any one of the first aspect.

[0065] In a fourth aspect, a chip system is provided, including a processor coupled with a memory, and the processor executes a computer program stored in the memory to enable the electronic device to implement the method of any one of the first aspect.

[0066] In a fifth aspect, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program. When the computer program is run on an electronic device, the electronic device is enabled to implement the method of any one of the first aspect.

[0067] In a sixth aspect, an embodiment of the present application provides a computer program product, which, when running on a device, causes the electronic device to perform the method of any one of the first aspect of the present application.

[0068] It can be understood that the beneficial effects of the third aspect to the sixth aspect described above can be referred to the related description in the first aspect and the second aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0069] FIG. 1 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present application;

[0070] FIG. 2 is a schematic diagram of an interface of a map application according to an embodiment of the present application;

[0071] FIG. 3 is a schematic diagram of a state change of a menu bar of view construction according to an embodiment of the present application;

[0072] FIG. 4 is another schematic diagram of a state change of a menu bar of view construction according to an embodiment of the present application;

[0073] FIG. 5 is a schematic diagram of a frame rate change in an interface switching process according to an embodiment of the present application;

[0074] FIG. 6 is a schematic diagram of a frame rate change when adjusting the frame rate from the view dimension according to an embodiment of the present application;

[0075] FIG. 7 is a schematic diagram of a frame rate change when adjusting the frame rate from the view and different operation dimensions according to an embodiment of the present application;

[0076] FIG. 8 is a schematic diagram of a flow of a frame rate adjustment method according to an embodiment of the present application;

[0077] FIG. 9 is a schematic diagram of a technical architecture of a frame rate adjustment method according to an embodiment of the present application;

[0078] FIG. 10 is a timing diagram of a method of adjusting the frame rate from the view dimension according to an embodiment of the present application;

[0079] FIG. 11 is a timing diagram of a method of adjusting the frame rate from the application dimension according to an embodiment of the present application;

[0080] FIG. 12 is another timing diagram of a method of adjusting the frame rate from the view dimension according to an embodiment of the present application;

[0081] FIG. 13 is another timing diagram of a method of adjusting the frame rate from the application dimension according to an embodiment of the present application;

[0082] FIG. 14 is a schematic diagram of an interface of a frame rate adjustment method according to an embodiment of the present application;

[0083] FIG. 15 is an interface diagram of another frame rate adjustment method provided by an embodiment of the present application. DETAILED DESCRIPTION

[0084] In the following description, for the purposes of explanation, numerous specific details are set forth in order to thoroughly describe the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application can be practiced in other embodiments that depart from these specific details. Reference herein to specific details is not intended to limit the scope of the present application.

[0085] It should be understood that the term "comprising" when used in this specification and the appended claims, specifies the presence of stated features, integers, steps, operations, elements, and / or components, but does not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0086] It should also be understood that, in the specification, "one or more" refers to one, two, or more than two; "and / or" describes the associated objects in associative relationship, indicating that there can be three kinds of relationships; for example, A and / or B can mean that A exists alone, A and B exist together, B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects.

[0087] In addition, in the description of the specification and the appended claims, the terms "first", "second", "third", "fourth" and the like are only used to distinguish descriptions, and cannot be understood as indicating or implying relative importance.

[0088] In the present specification, the reference "one embodiment" or "some embodiments" and the like means that a specific feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present application. Therefore, the statements "in one embodiment", "in some embodiments", "in other embodiments", "in additional embodiments" and the like appearing in various places in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically noted. The terms "include", "contain", "have" and their variants mean "including but not limited to", unless otherwise specifically noted.

[0089] The frame rate adjustment method provided in the embodiments of the present application can be applied in an electronic device. The electronic device in the embodiments of the present application can be a tablet computer, a mobile phone, a wearable device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), and the like. The embodiments of the present application do not limit the specific type of the electronic device.

[0090] FIG. 1 shows a structural schematic diagram of an electronic device. The electronic device 100 can 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, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a loudspeaker 170A, a receiver 170B, a microphone 170C, a headset interface 170D, a sensor module 180, a key 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, and the like. The sensor module 180 can include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

[0091] It can be understood that the structure shown in the embodiments of the present application does not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 can include more or fewer components than shown, or combine certain components, or split certain components, or different component arrangements. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0092] The processor 110 can include one or more processing units, for example: the processor 110 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units can be independent devices or integrated in one or more processors.

[0093] The processor 110 can also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory can hold instructions or data that the processor 110 has just used or is recycling. If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. This avoids repeated access and reduces the waiting time of the processor 110, thus improving the efficiency of the system.

[0094] The internal memory 121 can be used to store computer executable program code, which includes instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 can include a program storage area and a data storage area. The program storage area can store an operating system and at least one application program required by a function (such as an image playing function, etc.). The touch sensor 180K, also known as a “touch panel”. The touch sensor 180K can be disposed on the display screen 194, and the touch sensor 180K and the display screen 194 form a touch screen, also known as a “touch screen”. The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be disposed on the surface of the electronic device 100, which is different from the position where the display screen 194 is located.

[0095] The electronic device 100 realizes display functions through the GPU, the display screen 194, and the application processor, etc. 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 for graphics rendering. The processor 110 can include one or more GPUs that execute program instructions to generate or change display information.

[0096] The display screen 194 is configured to display images, videos, and the like. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flex light-emitting diode (FLED), a Miniled, a MicroLed, a Micro-OLED, a quantum dot light emitting diodes (QLED), or the like. In some embodiments, the electronic device 100 can include one or N display screens 194, where N is a positive integer greater than 1.

[0097] The embodiments of the present application do not particularly limit the specific structure of the execution subject of the frame rate adjustment method, as long as the code of the frame rate adjustment method of the embodiments of the present application is run to perform communication according to the frame rate adjustment method of the embodiments of the present application. For example, the execution subject of the frame rate adjustment method of the embodiments of the present application can be a functional module capable of calling and executing programs in the electronic device, or a communication device applied to the electronic device, for example, a chip.

[0098] Before introducing the specific embodiments of the present application, the view in the operating system is first described.

[0099] The application program of the electronic device can provide a user interface for realizing human-computer interaction. The visible content in the user interface can be constructed by a view, for example, the visible content such as the control, the text box, the image, and the menu bar in the user interface. The visible content constructed by the view can also be referred to as a view.

[0100] Referring to FIG. 2, a schematic diagram of one interface of the map application provided by the embodiments of the present application is shown.

[0101] The visible content in the interface is constructed by at least four views, wherein the view 1 constructs the visible content related to the map image; the view 2 and the view 3 construct different floating controls; and the view 4 constructs a foldable menu bar.

[0102] When the electronic device displays the interface through the display screen, the user can operate in the map image region constructed by view 1, so as to trigger the electronic device to perform processing such as moving, zooming in, or zooming out on the map image, so that the electronic device displays the moved map image, the zoomed-in map image, or the zoomed-out map image in the region corresponding to view 1. Of course, correspondingly, the electronic device can also display the moving process, the zooming-in process, or the zooming-out process of the image in the region corresponding to view 1. As an example, the user can perform a sliding operation in the map image region constructed by view 1, which can trigger the electronic device to move the map image, and the user can perform a two-finger pinch operation or a two-finger spread operation in the map image region constructed by view 1, which can trigger the electronic device to zoom out or zoom in the map image.

[0103] The user can perform a click operation on the control constructed by view 2 or view 3, so as to trigger the electronic device to display another interface linked by the control.

[0104] The user can perform a click operation on the control in the menu bar constructed by view 4, so as to trigger the electronic device to display another interface linked by the control.

[0105] The user can also perform a sliding operation in the menu bar region constructed by view 4, so as to trigger the electronic device to switch the menu bar from the current semi-folded state to a folded state or an unfolded state.

[0106] Referring to FIG. 3, a schematic diagram of switching between various states of the menu bar constructed by view 4 is provided in the embodiments of the present application.

[0107] Referring to (a) in FIG. 3, the menu bar constructed by view 4 is in a semi-folded state. The user can trigger the electronic device to display the interface shown in (b) in FIG. 3 by performing an upward sliding operation in the menu bar region. The user can also trigger the electronic device to display the interface shown in (c) in FIG. 3 by performing a downward sliding operation in the menu bar region.

[0108] In response to the upward sliding operation in the menu bar region shown in (a) in FIG. 3, the electronic device displays the interface shown in (b) in FIG. 3. In the interface shown in (b) in FIG. 3, the menu bar constructed by view 4 is in an unfolded state, and the menu bar in the unfolded state completely covers the content constructed by view 1, the content constructed by view 2, and the content constructed by view 3. Of course, in actual applications, the menu bar in the unfolded state can also be set to partially cover the content constructed by view 1 and completely cover the content constructed by view 2 and the content constructed by view 3. The embodiments of the present application do not limit the positional relationship between the menu bar in the unfolded state and the content constructed by other views.

[0109] In response to a downward sliding operation of the menu bar region shown in (a) of FIG. 3, the electronic device displays the interface shown in (c) of FIG. 3, in which the menu bar constructed by view4 is in a folded state, and the menu bar in the folded state displays a search box and an expansion control. The expansion control is used to switch the menu bar in the current folded state to a semi-folded state or an unfolded state. Of course, in actual applications, the menu bar in the folded state can also not display the search box.

[0110] Referring to (b) of FIG. 3, the menu bar constructed by view4 is in an unfolded state, and the user can trigger the electronic device to display the interface shown in (a) of FIG. 3 through a downward sliding operation in the menu bar region with a sliding distance less than or equal to a distance threshold; or the user can trigger the electronic device to display the interface shown in (c) of FIG. 3 through a downward sliding operation in the menu bar region with a sliding distance greater than the distance threshold.

[0111] Referring to (c) of FIG. 3, the menu bar constructed by view4 is in a folded state, and the user can trigger the electronic device to display the interface shown in (a) of FIG. 3 through an upward sliding operation with the expansion control as a starting point and with a sliding distance less than or equal to a distance threshold; or the user can trigger the electronic device to display the interface shown in (b) of FIG. 3 through an upward sliding operation with the expansion control as a starting point and with a sliding distance greater than the distance threshold. Of course, the user can also trigger the electronic device to display the interface shown in (b) of FIG. 3 through a click operation on the expansion control.

[0112] The interface change process from (a) of FIG. 3 to (b) of FIG. 3 can refer to FIG. 4. (a) of FIG. 4 to (d) of FIG. 4 are processes in which the electronic device gradually changes from displaying one interface to displaying another interface in response to a sliding operation of the user.

[0113] Referring to (a) of FIG. 4, the user operation is a sliding operation on the menu bar region and upward. Referring to (b) of FIG. 4, the position, size, and display content of the menu bar when the user's finger slides to the position in the figure. Referring to (c) of FIG. 4, the position, size, and display content of the menu bar when the user's finger slides to the position in the figure. In the process from (a) of FIG. 4 to (c) of FIG. 4, the position, size, and display content of the menu bar are related to the sliding position (or sliding distance) of the finger, and the position, size, and display content of the menu bar change as the user's finger slides.

[0114] In the case where the electronic device displays the interface shown in (c) of FIG. 4, the user releases the hand, and the electronic device displays the interface shown in (d) of FIG. 4.

[0115] The specific display manners (for example, the position relationship with the content constructed by other views in each state, and the specific form of the expansion control) of the menu bar constructed by view 4 in the half-folded state, the unfolded state, and the folded state are merely used for examples, and the display manners in each state can be set according to actual conditions in actual application.

[0116] In addition, the menu bar constructed by view 4 can also include only two states or more than three states, and the number of states of the content constructed by view 4 is also merely used for examples; the operations for triggering the switching between different states are also merely used for examples. The embodiments of the present application do not limit the above content.

[0117] As described above, the upward sliding operation of the user in the menu bar region constructed by view 4 can trigger the electronic device to switch the state of the menu bar; the switching process of the state of the menu bar is the process in which the menu bar gradually changes from one state to another state. Generally, the user has a higher requirement for the fluency of the process, and therefore, in order to improve the user experience, the electronic device can be set to display the above state change process at a higher frame rate during the state switching process of the menu bar constructed by view 4.

[0118] In order to more clearly understand the present solution, the difference and relationship between the refresh rate and the frame rate are described here.

[0119] The refresh rate and the frame rate are two parameters related to the video display performance.

[0120] The refresh rate refers to the number of times of updating the picture per second of the screen, and the measurement unit is Hz. Generally, the refresh rate of the screen is determined by the screen hardware. Taking 60Hz as an example, it means that the screen is refreshed 60 times per second.

[0121] The frame rate is the number of frames (also known as image frames) drawn by the GPU (graphics processor) per second, which can be measured by Hz or FPS. Taking 60FPS as an example, it means that the GPU draws a maximum of 60 frames per second.

[0122] As an example of the relationship between the two, if the screen refresh rate of the electronic device is 120Hz and the frame rate of the GPU when drawing a picture is 60FPS; in theory, each frame of picture drawn by the GPU can be refreshed and displayed on the screen twice. If the screen refresh rate of the electronic device is 120Hz and the frame rate of the GPU when drawing a picture is 120FPS; in theory, each frame of picture drawn by the GPU can be refreshed and displayed on the screen once.

[0123] Of course, in actual application, because the picture drawn inside the electronic device still needs to be rendered, synthesized, and sent to the display, and so on, before the screen can display the drawn picture, considering the influence of factors such as delay, it may not completely comply with the above theory.

[0124] In the embodiment of the present application, during the state switching process of the menu bar constructed by view4, the electronic device changes the frame number of the screen display content, that is, the display frame rate. Taking FIG. 4 as an example, in the case where the refresh rate of the electronic device is fixed, the smoothness of the picture in the process shown in FIG. 4 can be improved by changing the frame number of the picture sent to the screen. Of course, in the embodiment of the present application, the adjusted display frame rate is less than or equal to the screen refresh rate.

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

[0126] Referring to (a) in FIG. 5, a frame rate change process provided by the embodiment of the present application is shown.

[0127] When the electronic device displays interface 1, since the content of the interface displayed by the electronic device does not change or changes little, the electronic device displays interface 1 at a relatively low frame rate. The relatively low frame rate can be the lowest frame rate that can be supported by the hardware of the electronic device, for example, 1 Hz.

[0128] When the electronic device receives a user operation, in response to the user operation, the electronic device needs to switch the currently displayed interface 1 to interface 2. During the switching of the electronic device from interface 1 to interface 2, in order to quickly respond to the switching process and enable the user to quickly see the screen display interface 2, the electronic device increases the frame rate to a relatively high frame rate (for example, 60 Hz, 90 Hz or 120 Hz), and refreshes the switching process from interface 1 to interface 2 at the relatively high frame rate (for example, 60 Hz, 90 Hz or 120 Hz). The example shown in the figure takes 60 Hz as an example.

[0129] After the electronic device successfully displays interface 2, since the content of interface 2 does not change or changes little, the electronic device continues to reduce the frame rate to a relatively low frame rate (for example, the lowest frame rate that can be supported by the hardware of the electronic device: 1 Hz), and displays interface 2 at the relatively low frame rate.

[0130] Of course, 1 Hz, 60 Hz, 90 Hz and 120 Hz in the above example are only for example, and are used to represent that the frame rates during the stable display of the interface and during the switching of the interface are different.

[0131] As another example, the frame rate change process provided by (b) in FIG. 5 can also be provided.

[0132] When the electronic device displays interface 1, since the content of the interface displayed by the electronic device does not change or changes little, the electronic device displays interface 1 at a relatively low frame rate. The relatively low frame rate can be the lowest frame rate that can be supported by the hardware of the electronic device, for example, 1 Hz.

[0133] When the electronic device receives a user operation, in response to the user operation, the electronic device needs to switch the currently displayed interface 1 to interface 2. During the switching of the electronic device 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 (for example, 90Hz or 120Hz), and refreshes the switching process of interface 1 to interface 2 at a high frame rate (for example, 90Hz or 120Hz), and the example in the figure is 120Hz.

[0134] After the electronic device successfully displays interface 2, since the content of interface 2 does not change or changes little, the electronic device continues to reduce the frame rate to a lower frame rate (for example, 60Hz), and the electronic device displays interface 2 at a lower frame rate.

[0135] In the above example, the comparison is made before and after the switching of the higher and lower frame rates, rather than the absolute value of the frame rate.

[0136] The subsequent application is shown in (a) of FIG. 4. During the stable display of the interface, the frame rate is 1Hz. In the above process, during the display of interface 1, since the content of interface 1 does not change or changes little, in order to reduce power consumption, the content of interface 1 can be displayed at a lower frame rate; during the switching from interface 1 to interface 2, the frame rate is increased, so that the user operation can be responded to quickly and interface 2 can be successfully displayed. After successfully displaying interface 2, since the content of interface 2 does not change or changes little, the frame rate can be continuously reduced, thereby reducing power consumption.

[0137] For different applications, the frame rate during the switching of the interface in response to the user operation can be set to different frame rates. For example, during the display of the interface of some novel applications by the electronic device, the frame rate during the switching of the interface in response to the user operation can be increased to 60Hz, which can quickly respond to the user operation to display a new interface, and will not cause too high power consumption.

[0138] During the display of the interface of the map application by the electronic device, there will be some changes in the map image or the menu bar of the map application. The frame rate during the switching of the interface in response to the user operation can be increased to 90Hz to improve the user experience, and will not cause too much power consumption.

[0139] However, during the switching process of the different states of the menu bar shown in FIG. 4, the user has a higher requirement for the smoothness of the state change of the menu bar. The frame rate of 90Hz can not be sufficient to meet the user experience, so the frame rate of the state change process of the menu bar needs to be set higher, for example, 120Hz.

[0140] In a specific implementation, the following content can be set in the dimension of the application:

[0141] In response to a user operation on the novel application, the electronic device switches the frame rate during display of the novel application to 60Hz;

[0142] In response to a user operation on the map application, the electronic device switches the frame rate during display of the map application to 120Hz.

[0143] However, for the map application, if the frame rate during execution of a response event (e.g., interface switching) triggered by any operation on the map application is set to 120Hz, the power consumption of the electronic device can be too high.

[0144] Embodiments of the present application also provide a frame rate adjustment method, which can adjust the frame rate during refreshing of the interface of the application from the dimension of view.

[0145] Continuing with FIG. 3 as an example, when a user operation is performed on the menu bar constructed by view4, triggering state switching of the menu bar constructed by view4, the electronic device displays the content of the application at a higher frame rate (e.g., 120Hz), which can improve the user experience of the user for the state switching process of view4.

[0146] When a user operation is performed on the display content constructed by other views (e.g., view1, view2, or view3), triggering the electronic device to switch to display other content, the electronic device displays the content of the application at another relatively lower frame rate (e.g., 60Hz) than 120Hz, which can avoid increasing the frame rate during interface switching triggered by all operations on the application to 120Hz, i.e., avoid excessive power consumption in the case of increasing to 120Hz.

[0147] It can be understood that embodiments of the present application set the frame rate during execution of a response event (usually including an interface switching process) of a user operation from the dimension of view, which can improve user experience and reduce power consumption compared to setting the frame rate during execution of a response event of a user operation from the dimension of application.

[0148] Referring to FIG. 6, a frame rate change diagram when adjusting the frame rate from the dimension of view is provided by embodiments of the present application.

[0149] As shown in (a) of FIG. 6, when the electronic device displays interface 1, the interface content displayed by the electronic device does not change or changes little, and the electronic device displays interface 1 at a frame rate of 1Hz.

[0150] When the electronic device receives a user operation acting on the view 4 on the interface 1, in response to the user operation, the electronic device needs to switch the currently displayed interface 1 of the application to the interface 2 of the application. During the switching of the electronic device from the interface 1 of the application to the interface 2 of the application, the electronic device increases the frame rate to 120 Hz, and displays the pictures in the interface switching process at the frame rate of 120 Hz, which includes the change process of the content built by the view 4, for example, the change process between the interface shown in (a) of FIG. 4 to the interface shown in (d) of FIG. 4.

[0151] After the electronic device successfully displays the interface 2, the content of the interface 2 also does not change or changes little, and the electronic device reduces the frame rate to 1 Hz, and the electronic device displays the interface 2 at the frame rate of 1 Hz.

[0152] Referring to (b) shown in FIG. 6, when the electronic device displays the interface 1, the content of the interface displayed by the electronic device does not change or changes little, and the electronic device displays the interface 1 at the frame rate of 1 Hz.

[0153] When the electronic device receives a user operation acting on the view 2 on the interface 1, in response to the user operation, the electronic device needs to switch the currently displayed interface 1 of the application to the interface 3 of the application. During the switching of the electronic device from the interface 1 of the application to the interface 3 of the application, the electronic device increases the frame rate to 60 Hz, and displays the pictures in the interface switching process at the frame rate of 60 Hz, and the user's demand for the fluency of the interface switching process triggered by the view 2 is not high, so the frame rate can be set to be relatively low.

[0154] After the electronic device successfully displays the interface 3, the content of the interface 3 also does not change or changes little, and the electronic device reduces the frame rate to 1 Hz, and the electronic device displays the interface 3 at the frame rate of 1 Hz.

[0155] It can be understood that the higher the frame rate, the greater the power consumption. In the case of the frame rate during the switching of the display interface from the application dimension, if in order to cope with the user's perception of the state change of the menu bar built by the view 4, the frame rate needs to be increased to 120 Hz; if from the perspective of power consumption, the frame rate needs to be increased to 60 Hz, even if in order to balance the user experience and power consumption, the frame rate during the interface switching is increased to 90 Hz, it is difficult to balance the user experience and power consumption at the same time.

[0156] If the frame rate during the interface switching process is raised from the dimension of the view, the frame rate during the interface switching process of the interface with higher fluency requirement can be raised to 120Hz, and the frame rate during the interface switching process of the interface with lower fluency requirement can be raised to 60Hz. In actual implementation, the interface switching process is usually related to the view on which the user operation is performed, and therefore, the frame rate to be raised can be determined according to the view on which the user operation is performed. In this way, the user experience can be met, and the power consumption can be reduced.

[0157] Of course, the user's higher requirement for the state switching process of the menu bar constructed by the view 4 is only an example, and other scenarios can also exist in actual application.

[0158] As another example, when the electronic device displays the interface shown in (a) of FIG. 3 or (c) of FIG. 3, the interface also includes a map image constructed by the view 1. The user can also perform an upward sliding operation or a downward sliding operation in the map image region, so as to trigger the content of the map image displayed by the electronic device to change, for example, the map image in the region corresponding to the view 1 is moved upward or downward. The user can also perform a two-finger pinch operation or a two-finger spread operation in the map image region, so as to trigger the electronic device to zoom out or zoom in the map image in the region corresponding to the view 1.

[0159] The user's fluency requirement for the change process of the map image and the user's fluency requirement for the state change process of the menu bar can be different. For example, the user's fluency requirement for the change process of the map image is lower than the user's fluency requirement for the change process of the menu bar, and therefore, in response to the user operation on the view 1, the frame rate during the change process of the map image can be set to 90Hz.

[0160] Referring to (c) of FIG. 6, when the electronic device displays the interface 1, the content of the interface displayed by the electronic device does not change or changes little, and the electronic device displays the interface 1 at a frame rate of 1Hz.

[0161] When the electronic device receives a user operation, the user operation is performed on the view 1 of the interface 1, and in response to the user operation, the electronic device needs to switch the currently displayed interface 1 of the application to the interface 4 of the application. During the switching of the interface 1 of the application to the interface 4 of the application, the electronic device raises the frame rate to 90Hz, and displays the picture during the interface switching process at the frame rate of 90Hz.

[0162] After the electronic device successfully displays the interface 4, the content of the interface 4 does not change or changes little, and the electronic device reduces the frame rate to 1Hz, and displays the interface 4 at a frame rate of 1Hz.

[0163] Based on the above understanding, the frame rate adjustment method provided in the embodiments of the present application can switch the frame rate during the interface switching from the view dimension, for example, the operation on different views can trigger different interface switching processes, and the interface switching process with higher fluency requirement of the user is set to a higher frame rate to meet the user experience, and the interface switching process with lower fluency requirement of the user is set to a lower frame rate to avoid excessive power consumption of the electronic device. Therefore, the frame rate adjustment method provided in the embodiments of the present application can meet the user visual experience while avoiding excessive power consumption of the electronic device due to the increase of the frame rate.

[0164] In addition, in actual applications, the operation of the user on the view 4 can include not only a sliding operation but also a click operation, for example, the sliding operation on the view 4 triggers the state change of the menu bar constructed by the view 4, and the click operation on some controls in the menu bar constructed by the view 4 triggers the entry into another interface linked by the control. The fluency requirements of the user for the state change process of the menu bar and the process of entering another interface linked by the control are also different. Generally, the change process of the menu bar has higher fluency requirement, and the frame rate during the process needs to be higher. The fluency requirement of the process of directly switching from one interface to another interface linked by the control is lower, and the frame rate during the process does not need to be too high. Thus, the balance between the user experience and the power consumption can be achieved.

[0165] Therefore, in actual applications, not only different frame rates can be set for the execution processes of different response events of the user operation on different views, but also different frame rates can be set for the execution processes of different response events corresponding to different operations on the same view, so that the excessive power consumption can be avoided, and the user visual experience can be met.

[0166] Referring to FIG. 7, the frame rate changes of the execution processes of different response events triggered by different operations on the same view are provided in the embodiments of the present application.

[0167] Referring to (a) in FIG. 7, when the electronic device receives a user operation 1 (for example, a sliding operation) on the view 4, the electronic device needs to switch the currently displayed interface 1 of the application to the interface 5 of the application in response to the user operation 1. During the switching of the electronic device from the interface 1 of the application to the interface 5 of the application, the electronic device increases the frame rate to 120 Hz.

[0168] Referring to (b) in FIG. 7, when the electronic device receives a user operation 2 (for example, a click operation on a certain control in the menu bar constructed by the view 4) on the view 4, the electronic device needs to switch the currently displayed interface 1 of the application to the interface 6 of the application in response to the user operation 2. During the switching of the electronic device from the interface 1 of the application to the interface 6 of the application, the electronic device increases the frame rate to 60 Hz.

[0169] The above embodiments take the map application as an example, and in actual applications, the game application, the short video application, etc. can also be used. Of course, the value of the frame rate in the above embodiments is only used for example.

[0170] In addition, a part of the applications (for example, the map application, the game application, the short video application, etc.) can also be set to set the frame rate during the execution of the response event of the user operation according to the view dimension, and a part of the applications (for example, the novel application, the community application, the instant messaging application) can also be set to set the frame rate during the execution of the response event of the user operation according to the application dimension.

[0171] As another embodiment of the present application, a plurality of controls can be set on the same view, and the smoothness requirements of the response events corresponding to the operations on different controls are also different. Therefore, in the specific implementation, the frame rate during the execution of the response event triggered by the user operation on different controls of the same view can also be set to be different. The present application does not give examples one by one.

[0172] Referring to FIG. 8, a flowchart of an interface display method provided by an embodiment of the present application is shown. The flowchart can select different frame rate setting methods according to different categories of applications.

[0173] In S101, the electronic device detects an input event.

[0174] In the present application, the input event can be an input event of the user acting on the touch screen of the electronic device, which can be generated by a click operation, a sliding operation, a double-click operation, etc. The specific form of the user operation is not limited in the embodiments of the present application.

[0175] In S102, it is judged whether the input event is acting on a specific application.

[0176] In the embodiments of the present application, the specific application is an application that improves the frame rate during the interface switching in the view dimension.

[0177] The specific application can be an application of a specific category, for example, a map application, a game application, a short video application, etc.

[0178] The application can also be an application that is pre-set to use the frame rate adjustment method provided by the present application, for example, an application list composed of a plurality of application package names can be pre-stored, and the applications in the application list can be the above-mentioned applications of a specific category, and can also be applications of other categories but with specific interfaces.

[0179] As an example of an application that has a specific interface, a news application displays a news event by a view that displays the news itself, the size, position and content of the view that displays the news itself can be changed, displays some controls such as a like control, a comment control, a collection control and the like by another view, and can also display a news publisher, a news title and the like by other views. The fluency requirement of the response event corresponding to the user operation on the view that displays the news itself in the news application is high, and the frame rate corresponding to the view can be set to be high, that is, the frame rate of the electronic device during the execution of the response event corresponding to the user operation on the view is high (for example, 120Hz). While the frame rate of the electronic device during the execution of the response event corresponding to the user operation on other views is low (for example, 60Hz). Based on the above understanding, the specific application can also be an application in the pre-set application list.

[0180] In the embodiments of the present application, if the input event acts on a specific application, the frame rate in the execution process of the response event corresponding to the input event is improved according to the view dimension.

[0181] In the embodiments of the present application, if the input event acts on a specific application, the frame rate in the execution process of the response event corresponding to the input event is improved according to the view dimension.

[0182] In the embodiments of the present application, for a specific application, the target frame rate corresponding to each view under the specific application can be set.

[0183] In actual application, the frame rate during stable display of the interface can be 1Hz, the target frame rate corresponding to the view can be 60Hz, can also be 90Hz, and can also be 120Hz;

[0184] As an example, the target frame rate of a view is 60Hz, the target frame rate corresponding to a view is 90Hz, and the target frame rate of a view is 120Hz. No matter which view the user operation acts on, the frame rate during the interface switching process needs to be improved.

[0185] In addition, since the minimum frame rate supported by some electronic devices is 60Hz, that is, the frame rate during stable display of the interface can be 60Hz, the target frame rate corresponding to the view can be 60Hz, can also be 90Hz, and can also be 120Hz;

[0186] For example, the target frame rate of a certain view is 60Hz, the target frame rate of a certain view is 90Hz, and the target frame rate of a certain view is 120Hz. When the target frame rate of the view on which the user operation acts is 60Hz, the frame rate during the interface switching process does not need to be raised; when the target frame rate of the view on which the user operation acts is 90Hz or 120Hz, the frame rate during the interface switching process needs to be raised.

[0187] S104, when it is determined according to the view on which the input event acts that the frame rate does not need to be raised in the current interface switching process, the frame rate is not raised.

[0188] S105, when it is determined according to the view on which the input event acts that the frame rate needs to be raised in the current interface switching process, the display frame rate is raised to the target frame rate of the view on which the input event acts by SurfaceFlinger.

[0189] In the embodiment of the application, if the input event does not act on a specific application, the frame rate in the execution process of the response event corresponding to the input event is raised according to the application dimension.

[0190] S106, if the input event does not act on a specific application, the display frame rate is raised to the target frame rate of the application on which the input event acts by SurfaceFlinger.

[0191] In order to more clearly describe the above-mentioned frame rate adjustment method, the technical architecture diagram of the embodiment of the application is described by means of FIG. 9.

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

[0193] The framework layer includes inputdispatcher, view, SurfaceFlinger and frame rate decision center. The inputdispatcher is used to determine whether the user operation acts on a specific application; the view is used to determine the view on which the input event acts and determine the target frame rate of the view on which the input event acts; the SurfaceFlinger is used to adjust the display frame rate according to the received target frame rate, and deliver a Vsync signal to the currently foreground-running application according to the display frame rate, the Vsynv signal being used to trigger the application to issue display content; the SurfaceFlinger is also used to deliver the display content to the screen. The frame rate decision center is used to determine the target frame rate of the currently foreground-running application.

[0194] The kernel layer includes input and LCD driver. The input is used to generate input event according to user operation. The LCD driver is used to receive display content issued by SurfaceFlinger.

[0195] The hardware layer includes TouchPanel and LCD. The TouchPanel is used to detect user operation, and send the user operation to the input, and get input event through the input. The LCD is used as a screen to display the received display content.

[0196] In the frame rate adjustment method provided by the embodiments of the present application,

[0197] 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 the SurfaceFlinger.

[0198] The TouchPanel detects user operation, and sends the user operation to the input. The input generates input event according to the received input operation, and sends the input event to the inputdispatcher. The inputdispatcher judges whether the application on which the input event acts is a specific application.

[0199] If the application is not the specific application, the inputdispatcher sends the instruction of improving frame rate to the SurfaceFlinger. The SurfaceFlinger sets the display frame rate to the target frame rate of the application currently running in the foreground according to the instruction of improving frame rate.

[0200] If the application is the specific application, the target frame rate corresponding to each view of the specific application is stored in the view. The inputdispatcher sends the input event to the view. The view judges the view on which the input event acts, and gets the target frame rate of the view on which the input event acts. The view sends the frame rate adjustment instruction to the SurfaceFlinger. The instruction carries the target frame rate of the view. The SurfaceFlinger sets the display frame rate to the target frame rate of the view on which the input event acts according to the instruction of adjusting frame rate.

[0201] In addition, the inputdispatcher delivers the input event to the application through the view, so as to trigger the application to determine subsequent display content.

[0202] The SurfaceFlinger sends a Vsync signal to the application according to a current display frame rate, and the application sends display content to the SurfaceFlinger according to the Vsync signal.

[0203] The SurfaceFlinger processes the display content (for example, drawing, compositing, rendering, etc.), so that the LCD displays the display content of the application.

[0204] It can be understood that the frame rate adjustment method provided by the embodiments of the present application, whether the frame rate is set in the application dimension or the view dimension, is a system-level adjustment frame rate manner, and does not need to be set separately by each display interface application in the application layer.

[0205] Referring to FIG. 10, it is a timing diagram for setting the frame rate in the dimension of the view on which the input event acts when the input event acts on a specific application (for example, a map application) according to the embodiments of the present application.

[0206] First of all, it needs to be explained that the relationship A is pre-stored in the dispatchTouchEvent function in the view.java, and the relationship A is the target frame rate corresponding to the name of each view of the specific application.

[0207] As an example, the relationship A includes:

[0208] The target frame rate of the view4 in the interface of the map application shown in FIG. 3 is 120Hz;

[0209] The target frame rate of the view1 in the interface of the map application shown in FIG. 3 is 90Hz;

[0210] The target frame rate of the view2 in the interface of the map application shown in FIG. 3 is 60Hz;

[0211] The target frame rate of the view3 in the interface of the map application shown in FIG. 3 is 60Hz.

[0212] As described above, the target frame rate can also be related to the operation type, and when it is necessary to set different target frame rates for different operations on the same view, the target frame rate of one or more operations on each view in the specific application is pre-stored in the dispatchTouchEvent function in the view.java. As another example of the relationship A, the relationship A includes:

[0213] The target frame rate of the sliding operation on the view4 in the interface of the map application shown in FIG. 3 is 120Hz;

[0214] The target frame rate of the click operation on the view4 in the interface of the map application shown in FIG. 3 is 60Hz;

[0215] The target frame rate of the operation on view 1 in the interface of the map application shown in FIG. 3 is 90 Hz;

[0216] The target frame rate of the operation on view 2 in the interface of the map application shown in FIG. 3 is 60 Hz;

[0217] The target frame rate of the operation on view 3 in the interface of the map application shown in FIG. 3 is 60 Hz.

[0218] Of course, the above is only for example, in actual application, the relationship A can also store target frame rates under more conditions, for example, the center position of the view can also be added as a condition to set the target frame rate, and different controls in the view can also be added as a condition to set the target frame rate. The target frame rates under multiple conditions set in the view dimension are within the range of setting the target frame rate from the view dimension provided by the embodiments of the present application, and the present application does not exemplify one by one. Of course, the above various conditions can be set according to actual situations, and regardless of what conditions are set, the embodiments of the present application adjust the frame rate from the view dimension from the system level.

[0219] In addition, the dispatchTouchEvent function in view.java can also record relationship B when the electronic device switches between interfaces, where relationship B records the relationship between the name of the view in the newly switched interface and the position of the view. Of course, the name of the view is only an example, and in actual application, different views can also be distinguished by other unique identifiers.

[0220] S201, the input detects an input event, and the event type of the input event can be a down event.

[0221] Generally, the input event corresponding to the sliding operation includes a down event, a move event and an up event. Of course, other user operations can also include a down event, for example, the input event corresponding to a single click operation includes a down event and an up event.

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

[0223] In the embodiments of the present application, when sending the detected input event to the Inputdispatcher, the event type corresponding to the input event is also carried: the down event, and the coordinates corresponding to the down event are also carried. The coordinates corresponding to the down event are the coordinates of the user touch point on the screen.

[0224] S203, after receiving the input event, the Inputdispatcher determines the event type of the input event is down event, determines the application affected by the input event according to the coordinates, and determines the application as the specific application.

[0225] S204, after receiving the input event, the Inputdispatcher sends the input event to the view. The input event carries the event type and the coordinates.

[0226] S205, in the case of down event, the view finds the name of the view corresponding to the coordinates of the down event in relation B through the dispatchTouchEvent function in the view: view4.

[0227] S206, the target frame rate corresponding to view4 is queried in relation A through the dispatchTouchEvent function in the view.

[0228] In the embodiment of the application, the target frame rate corresponding to each view in the specific application can be stored in the view.

[0229] S207, the view sends the adjustment instruction to the SurfaceFlinger. The adjustment instruction carries the target frame rate corresponding to view4.

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

[0231] S209, the input detects the input event. The event type of the input event is move event. The event can carry the coordinates of the touch point.

[0232] In the embodiment of the application, the user's sliding operation further includes a move event after the down event.

[0233] S210, the input sends the detected input event to the Inputdispatcher. The move event corresponding to the input event and the coordinates corresponding to the move event are carried. The coordinates corresponding to the move event are the coordinates of the user's touch point on the screen.

[0234] S211, in the case of move event, the Inputdispatcher sends the input event to the view. The event type: move event and the coordinates of the move event are carried.

[0235] S212, in the case that the event type of the input event received by the view is a move event, the view sends the input event to the map application. The input event carries the event type and the coordinates.

[0236] S213, the map application determines the display content according to the event type and the coordinates of the input event.

[0237] Referring to (a) of FIG. 4 to (c) of FIG. 4, in the case that the input event is a move event in the sliding operation, the menu bar constructed by the view 4 is in the process of switching state, and the content and the position corresponding to the menu bar can be changed, so the content displayed on the screen is changed in real time. The map application running in the foreground can determine the content to be displayed according to the coordinates carried by the input event.

[0238] S214, after the SurfaceFlinger sets the display frame rate to the target frame rate, the SurfaceFlinger sends a Vsync signal to the map application running in the foreground according to the target frame rate. The Vsync signal is used to trigger the upper-layer application to issue display content.

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

[0240] Subsequently, the SurfaceFlinger triggers the display of the received display content, and of course, before the display is actually sent to the screen, it will also go through rendering and other processes.

[0241] With the SurfaceFlinger sending the Vsync signal according to the target frame rate, the map application will issue the display content according to the Vsync signal, thereby improving the smoothness of the picture.

[0242] It should be noted that with the execution of the user's sliding operation, the upper-layer application needs to update the display content in real time, i.e., S209 to S215 are executed in a loop until the user releases the hand.

[0243] Of course, in some examples, with the end of the user's sliding operation, the interface switching is completed, so when the input event received by the view is an up event, an instruction to restore the frame rate can also be sent to the SurfaceFlinger, i.e., triggering the SurfaceFlinger to set the frame rate to 1Hz or 60Hz again.

[0244] In some other examples, the interface has not been updated completely when the user's sliding operation ends, for example, if the user's sliding operation acts on the map image area constructed by viewl and the sliding speed is fast, the user releases the hand, and the map image continues to slide according to the sliding speed of the sliding operation before the hand is released. In this case, the time when the sliding of the map image ends can be determined according to the sliding speed, and at the time when the sliding of the map image ends, the instruction of resuming the frame rate is sent to SurfaceFlinger, that is, SurfaceFlinger is triggered to set the frame rate to 1 Hz or 60 Hz again.

[0245] The present application does not limit the process performed when the frame rate is resumed to 1 Hz or 60 Hz.

[0246] Referring to FIG. 11, a timing diagram for setting the frame rate in the dimension of the application on which the input event acts when the input event acts on a non-specific application (for example, a novel application) is provided in the embodiments of the present application.

[0247] It should be noted that the target frame rate of each application is stored in the frame rate decision center.

[0248] S301, the monitoring module monitors that the novel application switches to the foreground operation.

[0249] S302, the monitoring module monitors that the novel application switches to the foreground operation, and sends the application package name of the novel application that switches to the foreground operation to the frame rate decision center.

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

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

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

[0253] According to the description of S301 to S305, it can be understood that SurfaceFlinger can record the target frame rate of the currently foreground running application, and when the foreground running application is switched to another application, SurfaceFlinger will also update the recorded display frame rate to the target frame rate of the foreground running application after the switching.

[0254] When the user's operation acts on any interface of application A, the following steps are performed:

[0255] S306, the input detects an input event. The event type of the input event is a down event.

[0256] S307, the input sends the detected input event to the input dispatcher. The event carries the event type and the coordinates.

[0257] S308, the input dispatcher determines the application affected by the input event according to the coordinates when the event type of the input event is a down event, and determines that the application is not a specific application.

[0258] S309, the input dispatcher calls the vrrHook function in the input dispatcher to generate the instruction of boosting the frame rate.

[0259] S310, the input dispatcher sends the instruction of boosting the frame rate to the SurfaceFlinger through the Notifyboostrefreshrate function in the input dispatcher.

[0260] S311, the SurfaceFlinger adjusts the display frame rate to the latest recorded target frame rate after receiving the instruction of boosting the frame rate.

[0261] S312, the input detects an input event. The input event is a move event. The event carries the coordinates of the move event.

[0262] In the embodiment of the present application, the user's sliding operation further includes a move event after the down event.

[0263] S313, the input sends the detected input event to the input dispatcher. The event carries the event type corresponding to the input event: the 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.

[0264] S314, the input dispatcher sends the input event to the view when the event type of the input event is a move event. The event carries the event type: move and the coordinates.

[0265] S315, the view sends the input event to the map application when the input event is a move event after receiving the input event. The input event carries the event type and the coordinates.

[0266] S316, the map application determines the display content according to the event type and the coordinates corresponding to the input event.

[0267] S317, after setting the display frame rate to the target frame rate, SurfaceFlinger sends a Vsync signal to the foreground running map application according to the target frame rate. The sending frequency of the Vsync signal is the same as the target frame rate. The Vsync signal is used to trigger the upper-layer application to issue display content at a certain frequency.

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

[0269] Similarly, with the execution of the user's sliding operation, the application needs to update the display content in real time, that is, S312 to S318 are executed in a loop until the user releases the hand.

[0270] Currently, the process of SurfaceFlinger restoring the display frame rate can refer to the related description in FIG. 10, which will not be repeated here.

[0271] It can be understood that whether the application affected by the input event is the specific application or not, S301 to S305 will be executed, and SurfaceFlinger will record the target frame rate of the foreground running application.

[0272] Then, when the application affected by the input event is the specific application, SurfaceFlinger will first receive the target frame rate of the application, and then receive the target frame rate corresponding to the view. In order to make the execution steps of SurfaceFlinger clearer, refer to the timing diagram shown in FIG. 12.

[0273] In FIG. 12, S301 to S305 can refer to FIG. 11, S201 to S215 can refer to FIG. 10, and after executing S305, SurfaceFlinger will not adjust to the target frame rate corresponding to the application, but after S207, SurfaceFlinger will adjust the frame rate to the target frame rate corresponding to the view in the adjustment instruction carrying the view, instead of the target frame rate of the application recorded in S205.

[0274] In addition, in actual application, the execution result of S203 and whether to execute S204 do not have a specific relationship. That is, whether the application affected by the input event in S203 is the specific application or not, S204 is executed. In order to avoid SurfaceFlinger receiving two adjustment instructions, in the embodiment of the present application, it can be set that only the target frame rate of each view in the specific application is stored in the view. If it is not the specific application, the target frame rate cannot be queried when S206 is executed, that is, S207 cannot be continuously executed, and the target frame rate cannot be set from the view dimension.

[0275] Referring to FIG. 13, S301 to S318 can refer to FIG. 11, S204 to S207 can refer to FIG. 10.

[0276] After S308, S204 to S206 are executed in one aspect, and S309 to S311 are executed in another aspect.

[0277] Since the target frame rate corresponding to the view of the non-specific application is not stored in the view, the result of S206 is that the target frame rate corresponding to the view name cannot be queried, and S207 is not executed any more. Therefore, SurfaceFlinger adjusts the frame rate to the target frame rate of the application dimension recorded in S305 according to the instruction of S310.

[0278] In the above example, the target frame rates of different operations under the same view are not set. In actual application, the judgment of operation type can be added in Inputdispatcher, that is, after receiving the down event, it is not determined whether it is a specific application, and after the next event after receiving the down event (for example, the first input event is of the move type), the specific operation is determined according to the next event, for example, if the next input event after the down event is the up event, it is a single-click operation, and if the next input event after the down event is the move event, it is a sliding operation. After determining the operation type, it is determined whether it is a specific application. In the case of a specific application, the target frame rates of different operations under the same view are recorded in the view, so that the target frame rate can be determined according to the view on which the input event acts and the operation type corresponding to the input event. Of course, the above process of determining the operation type is only an example.

[0279] Referring to FIG. 14, another frame rate adjustment method provided by an embodiment of the present application includes:

[0280] displaying a first interface of a first application, the first interface including a first view and a second view;

[0281] detecting a first operation acting on the first interface;

[0282] in response to the first operation, switching from the first interface to a first target interface of the first application;

[0283] wherein, in the case that 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, and the first target interface is the second interface;

[0284] In a case where the first operation is performed on the second view, image frames during switching from the first interface to a first target interface are displayed at a second frame rate, the first target interface being a third interface, the second frame rate being different from the first frame rate.

[0285] Referring to (a) of FIG. 14, the electronic device displays a first interface of a first application, which can be a map application, a first view in the first application being configured to build a menu bar and a second view being configured to build a map image.

[0286] Referring to (b) of FIG. 14, in a case where an upward swipe operation is performed on the first view, the electronic device displays a second interface shown in (b) of FIG. 14, the second interface and the first interface being generated based on the same activity. The center position, size, and display content of the first view in the first interface and the first view in the second interface are changed. During switching from the first interface to the second interface, the electronic device displays image frames during the switching at a second frame rate (e.g., 120 Hz).

[0287] Referring to (c) of FIG. 14, in a case where an upward swipe operation is performed on the second view, the electronic device displays a second interface shown in (b) of FIG. 14, the second interface and the first interface being generated based on the same activity. The center position and size of the second view in the first interface and the second view in the second interface are not changed, but the specific display content is changed. That is, the map is upwardly moved. During switching from the first interface to the second interface, the electronic device displays image frames during the switching at a third frame rate (e.g., 90 Hz).

[0288] In addition, in the above-described example, the upward swipe operation is only one example of the first operation, and the respective views in the above-described example are only one example of the views.

[0289] There can also be any one of the following cases:

[0290] In a case where the first operation is a first gesture operation and is performed on the first view, image frames during switching from the first interface to a first target interface are displayed at a first frame rate, the first target interface being a second interface, the first frame rate being specifically a ninth frame rate.

[0291] In a case where the first operation is a first gesture operation and is performed on the second view, image frames during switching from the first interface to a first target interface are displayed at a second frame rate, the first target interface being a third interface, the second frame rate being specifically a tenth frame rate.

[0292] In a case where the first operation is a third gesture operation and is performed on the first view, image frames during switching from the first interface to a first target interface are displayed at a first frame rate, the first target interface being an eleventh interface, the first frame rate being specifically an eleventh frame rate.

[0293] In a case where the first operation is the fourth gesture operation and acts on the second view, image frames during switching from the first interface to a first target interface are displayed at a second frame rate, the first target interface is a twelfth interface, and the second frame rate is specifically a twelfth frame rate.

[0294] For example, in the above example, the third gesture operation and the fourth gesture operation can also be single-click operations.

[0295] The embodiments of the present application focus on that operations on different views can trigger different interface switching processes, and the frame rate in the interface switching process is related to the view on which the operation acts. Of course, the frame rate during interface switching corresponding to operations on any two views can be the same or different.

[0296] As another embodiment of the present application, displaying the first interface of the first application includes: 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.

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

[0298] Displaying the first target interface at the third frame rate.

[0299] In the present application, during stable display of the first interface, the second interface and the third interface (of course, stable display of any interface can also be performed), the interface can be displayed at a lower third frame rate. The third frame rate can be the minimum frame rate (for example, 1 Hz or 60 Hz) that the electronic device can support, 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.

[0300] As another embodiment of the present application, the method further includes:

[0301] Displaying a fourth interface of a second application, the fourth interface including a third view and a fourth view;

[0302] Detecting a second operation acting on the third view or the fourth view of the fourth interface;

[0303] In response to the second operation, displaying image frames during switching from the fourth interface to a second target interface of the second application at a fourth frame rate.

[0304] In the present application, the second application can be an application that does not need to adjust the frame rate from the view dimension, for example, 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 actual application, the second application adjusts the frame rate from the application dimension. The target frame rate corresponding to the second application is the fourth frame rate.

[0305] As another embodiment of the present application, displaying the fourth interface of the second application includes:

[0306] displaying the fourth interface at a third frame rate, the third frame rate being a minimum frame rate that the electronic device can support, the third frame rate being less than or equal to the fourth frame rate;

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

[0308] displaying the second target interface at the third frame rate.

[0309] As another embodiment of the present application, the method further includes:

[0310] displaying a fifth interface of the first application, the fifth interface including a fifth view, the fifth view including a first control and a second control;

[0311] detecting a third operation acting on the fifth view;

[0312] in response to the third operation, switching from the fifth interface to a third target interface of the first application;

[0313] 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;

[0314] 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.

[0315] Continuing to take FIG. 14 as an example, operations on different controls on the same view can also correspond to different target frame rates, for example, operations on different controls on the first view can trigger the display of different interfaces, and the frame rates during the switching to different interfaces can be different.

[0316] As another embodiment of the present application, the first operation is a sliding operation, the first target interface and the first interface are generated based on the same Activity, and the first target interface is an interface displayed after the release of the sliding operation.

[0317] As another embodiment of the present application, the first application is a map application, a game application, or a short video application, and the second application is a novel application.

[0318] As another embodiment of the present application, the method further includes:

[0319] displaying an eighth interface of the first application, the eighth interface including a sixth view;

[0320] detecting a fourth operation acting on the sixth view;

[0321] in response to the fourth operation, switching from the eighth interface to a fourth target interface of the first application;

[0322] wherein, 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;

[0323] 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.

[0324] Referring to FIG. 15, the first gesture operation is an up sliding operation, the ninth interface and the eighth interface are generated based on the same activity, and the fourth target interface is an interface displayed after releasing the sliding operation; the second gesture operation is a click operation, the tenth interface and the eighth interface are generated based on different activities; the seventh frame rate (an example shown as 120 Hz) is greater than the eighth frame rate (an example shown as 60 Hz).

[0325] As another embodiment of the present application, displaying the eighth interface of the first application comprises: displaying the eighth interface at a third frame rate (for example, 1 Hz or 60 Hz), 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;

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

[0327] displaying the fourth target interface at the third frame rate.

[0328] As another embodiment of the present application, 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 seventh frame rate and / or the third frame rate is less than the eighth frame rate.

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

[0330] It should be understood that the size of the serial number of each step in the above embodiments does not mean the order of execution, and the execution order of each process should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0331] The embodiment of the present application further provides a computer readable storage medium, the computer readable storage medium stores a computer program, and the computer program can realize the steps in each method embodiment when running on an electronic device.

[0332] The embodiment of the present application further provides a computer program product, when the computer program product runs on an electronic device or a wireless router, the electronic device can realize the steps in each method embodiment.

[0333] The integrated unit, if realized in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the embodiment of the present application can realize all or part of the processes in the above method through a computer program to instruct related hardware, and the computer program can be stored in a computer readable storage medium. The computer program can realize the steps in each method embodiment when executed by a processor. The computer program includes computer program code, which can be in the form of source code, object code, executable files or some intermediate forms. The computer readable medium at least includes 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 telecommunications signal and a software distribution medium. For example, a U disk, a mobile hard disk, a magnetic disk or an optical disk, etc. In some jurisdictions, according to legislation and patent practice, the computer readable medium cannot be an electrical carrier signal and a telecommunications signal.

[0334] The embodiment of the present application further provides a chip, the chip includes a processor, the processor is coupled with a memory, and the processor calls a computer program stored in the memory to realize the steps in any method embodiment of the present application. The chip can be a single chip or a chip module composed of multiple chips.

[0335] In the above embodiments, the description of each embodiment has its own focus, and the parts not described or recorded in detail in a certain embodiment can be referred to the related description of other embodiments.

[0336] Those skilled in the art can realize that the units and method steps of the examples described in combination with the embodiments disclosed herein can be realized in electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solution. The skilled person can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0337] The above examples are only used to illustrate the technical solutions of the present application, but not to limit the present application; although the present application has been described in detail with reference to the foregoing examples, those ordinarily skilled in the art should understand: the technical solutions recorded in the foregoing examples can still be modified, or some technical features can be replaced equivalently; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present 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