An interactive control method, an electronic device, and a computer-readable storage medium

Abstract

This application provides an interactive control method, an electronic device, and a computer-readable storage medium, relating to the field of terminals. The method includes: launching a first application and displaying a first splash screen page, the first splash screen page including first interactive content, a first sub-option, and a second sub-option. Upon receiving a selection operation on the first sub-option, in response to a first motion control operation on the electronic device, a first interface is displayed, the first interface being the interface corresponding to the first interactive content. Upon receiving a selection operation on the second sub-option, in response to a second motion control operation on the electronic device, the first interface is displayed; in response to the first motion control operation on the electronic device, the first interface is not displayed. This allows for different motion control operations to be responded to based on the user's selection, making the splash screen response more in line with user expectations and improving the user experience.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to an interactive control method, an electronic device, and a computer-readable storage medium. Background Technology

[0002] Currently, mobile phones, tablets, and other electronic devices can display interactive content during the app's splash screen, and these devices can respond to user interactions. This will be referred to as the splash screen interaction scenario below. Taking the display of shake-to-interact interactive content as an example, when the electronic device detects a shake, it can jump from the current screen to the screen corresponding to the interactive content. Conversely, if the electronic device does not detect a shake, it can remain on the current screen until the display time for the interactive content ends, at which point the interactive content will no longer be displayed.

[0003] In existing solutions, during splash screen interactions, electronic devices may detect and respond to user actions even when there is no explicit interaction requirement. For example, when a user is walking, riding in a vehicle, or picking up and putting down the electronic device, the device may shake, and the device may interpret this shaking as an interaction and respond accordingly. This results in a response that does not meet user expectations, negatively impacting the user experience. Summary of the Invention

[0004] This application provides an interactive control method, an electronic device, and a computer-readable storage medium, which can prevent erroneous redirects when an electronic device displays interactive content, making the response results more in line with the user's expectations, thereby improving the user experience.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, this application provides an interactive control method applied to an electronic device, the electronic device including a first application, such as the video application described below. Specifically, the method includes:

[0007] The first application is launched, displaying a first splash screen, which includes first interactive content, a first sub-option, and a second sub-option. Upon receiving a selection operation on the first sub-option, in response to a first motion control operation on the electronic device, a first interface is displayed, which is the interface corresponding to the first interactive content. Upon receiving a selection operation on the second sub-option, in response to a second motion control operation on the electronic device, the first interface is displayed. In response to a first motion control operation on the electronic device, the first interface is not displayed. The first motion control operation causes the electronic device to move at a first amplitude, and the second motion control operation causes the electronic device to move at a second amplitude, where the first amplitude is smaller than the second amplitude.

[0008] In other words, after selecting the first sub-option, the electronic device will switch to another device in response to a small amount of motion control. Only after selecting the second sub-option will the electronic device switch to another device in response to a larger amount of motion control.

[0009] In summary, by adopting this application, on the one hand, electronic devices can provide a first sub-option and a second sub-option on the splash screen for users to choose from, eliminating the need for users to search for and configure the corresponding entry point in the settings application. This approach is more accessible and has a higher reach rate. Furthermore, users can complete the settings by selecting the appropriate option, avoiding multiple steps across multiple interfaces, simplifying the operation and improving human-computer interaction efficiency. On the other hand, the first and second sub-options provided by the electronic device can be used to set the precision of the response to interactive operations. This allows users to adjust the response precision according to their needs, enabling the electronic device to respond to motion control operations of varying amplitudes based on the user's settings. The response results better match the user's expectations, improving the user experience.

[0010] In one possible design approach of the first aspect, launching a first application and displaying a first splash screen includes: launching the first application and displaying a second splash screen, the second splash screen including first interactive content and a first option (such as the "always allowed" option below). The first splash screen is displayed in response to a selection of the first option. That is, the first option, its first sub-option, and its second sub-option have a hierarchical relationship.

[0011] In one possible design of the first aspect, the first splash screen page further includes a second option (as described below, the option to disable during splash screen). After displaying the first splash screen page, the method further includes: receiving a selection operation for the second option; wherein, upon receiving the selection operation for the second option, in response to a motion control operation on the electronic device, the first interface is not displayed.

[0012] In other words, after selecting the second option, the electronic device will not respond to the user's motion control operations on the splash screen. Even large-amplitude motion control operations will not be responded to. This fulfills the requirement of not responding to interactive operations on the splash screen.

[0013] In one possible design of the first aspect, after receiving a selection operation on the first sub-option, the second sub-option, or the second option, the method further includes: displaying a second interface, which is the application interface of the first application and is not a splash screen. In response to a first motion control operation on the electronic device, the first function of the first application is executed.

[0014] In other words, selecting the first, second, or third sub-option on the splash screen will only affect the responsiveness within that splash screen. After the splash screen is displayed, the electronic device can still respond to minor motion control operations for the primary function within the first application, such as the shake feedback function, thus avoiding any impact on the functionality within the application.

[0015] In one possible design of the first aspect, the first splash screen also includes a third option (the disabled option as described below). After displaying the first splash screen, the method further includes: receiving a selection operation on the third option; wherein, upon receiving the selection operation on the third option, in response to a motion control operation on the electronic device, the first interface is not displayed. The third interface is displayed, which is the application interface of the first application and is not the splash screen. In response to a first motion control operation on the electronic device, the first function of the first application is executed.

[0016] In other words, after selecting the third option, motion control operations will not be responded to on the splash screen or after entering the application. This satisfies the user's need for unified control on the splash screen and within the application.

[0017] In one possible design approach of the first aspect, the triggering operation for the first interactive content is a motion control operation.

[0018] In other words, electronic devices will only display the first and second sub-options on the splash screen for interactive content that is triggered by motion control, thus making it easier for users to set the response accuracy for this type of interactive content.

[0019] In one possible design approach of the first aspect, the method further includes: launching a first application and displaying a third splash screen, wherein the third splash screen includes second interactive content. The triggering operation for the second interactive content is not a motion control operation, and the third splash screen does not include a first sub-option or a second sub-option.

[0020] In other words, for interactive content whose triggering operation is not a motion control operation, such as interactive content that responds through clicking or swiping, when displaying the splash screen, electronic devices may not provide the first and second sub-options, thereby enabling targeted provision of response accuracy settings.

[0021] In one possible design approach of the first aspect, after receiving a selection operation on the first sub-option, or after receiving a selection operation on the second sub-option, the method further includes: launching the first application and displaying a fourth splash screen page, the fourth splash screen page including the first interactive content. The fourth splash screen page does not include the first sub-option or the second sub-option.

[0022] In other words, once the user selects an option on the splash screen, the responsiveness setting for that splash screen is complete. When the first application is launched again and the splash screen is displayed, the first and second sub-options are no longer shown to avoid interfering with the user experience.

[0023] In one possible design approach of the first aspect, launching the first application and displaying the first splash screen includes: launching the first application and displaying the first splash screen without receiving a first operation in the settings application. The first operation is used to trigger the electronic device settings application to obtain permission for device motion data.

[0024] In other words, if the user has not set the first application's permission to obtain device motion data in the settings app, the user needs to set the response accuracy on the splash screen for the electronic device to display the first and second sub-options on the splash screen, thus displaying the first and second sub-options in a targeted manner.

[0025] In one possible design of the first aspect, the method further includes: displaying a fourth interface, which is a permission status setting interface for the second application, including settings for the second application's permission to obtain device motion data; receiving a second operation on the fourth interface, the second operation being used to trigger the electronic device to set the second application's permission to obtain device motion data; launching the second application and displaying a fifth splash screen, which includes third interactive content and does not include the first and second sub-options. The third interactive content may be the same as the first interactive content.

[0026] In other words, after the second application's permission to access motion data has been set in the settings app, i.e., after the response accuracy in the splash screen has been set, the first and second sub-options will not be displayed when the second application is launched and the splash screen is displayed, so as to avoid the first and second sub-options affecting the user experience.

[0027] In one possible design approach of the first aspect, after receiving a selection operation on the first sub-option, the method further includes: displaying a fifth interface, which is a permission status setting interface for the first application. The fifth interface includes a third sub-option and a fourth sub-option, the third sub-option corresponding to the first sub-option, the third sub-option being selected, and the fourth sub-option corresponding to the second sub-option. Receiving a selection operation on the fourth sub-option in the fourth interface. Launching the first application and displaying a sixth splash screen, which includes fourth interactive content. The fourth interactive content may also be the same as the first interactive content. Responding to a second motion control operation on the electronic device, displaying the sixth interface; responding to a first motion control operation on the electronic device, not displaying the sixth interface. The sixth interface is the interface corresponding to the fourth interactive content.

[0028] In other words, in the permission settings interface of the first application, the permission of the first application to obtain device motion data can be modified. After modification, when the application is launched again and the splash screen is displayed, the electronic device can respond to the user's motion control operation with different levels of precision.

[0029] In one possible design approach of the first aspect, after launching the first application, the method further includes: when registering the target sensor, querying the permission status of the first application for the target sensor, the target sensor being used to collect motion data from the electronic device. Displaying the first splash screen includes: if the permission status is found to be in the default state, displaying the first splash screen. Wherein, a default permission setting state indicates that the user has not selected any options on the splash screen, nor has the user set any permission status in the permission status settings interface. In this case, a first sub-option and a second sub-option can be displayed on the splash screen so that the user can set the permission status. This allows for targeted setting of the permission status.

[0030] In one possible design approach of the first aspect, the method further includes: if the permission status is not found to be the default state, displaying a splash screen page that does not include the first and second sub-options. Wherein, if the permission setting status is not the default state, it indicates that the user has selected an option on the splash screen page, or set the permission status in the permission status settings interface. In this case, the first and second sub-options may not be displayed on the splash screen page.

[0031] In one possible design of the first aspect, the electronic device includes a sensor service and a security service. Upon receiving a selection operation for a first sub-option, in response to a first motion control operation on the electronic device, a first interface is displayed, including: upon receiving the selection operation for the first sub-option, the security service sends first status information (hereinafter referred to as precise motion status) to the sensor service. In response to receiving the first status information, the sensor service sends first motion data to a first application, the first motion data including motion data collected by the target sensor corresponding to the first motion control operation. The first application displays the first interface based on the first motion data.

[0032] In other words, after selecting the first sub-option, even for minor motion control operations, the sensor service can send the corresponding motion data to the first application, enabling the first application to respond to minor motion control operations with high accuracy. This satisfies the precise response requirement corresponding to the first sub-option.

[0033] In one possible design of the first aspect, the electronic device further includes a sensor service and a security service. Upon receiving a selection operation for a second sub-option, in response to a second motion control operation on the electronic device, a first interface is displayed, including: upon receiving the selection operation for the second sub-option, the security service sends second status information (as described below in the fuzzy motion status section) to the sensor service. In response to receiving the second status information, the sensor service sends a first request to the security service, the first request being used to query whether motion data should be sent to a first application. In response to the second motion control operation on the electronic device, the sensor service sends second motion data collected by a target sensor to the security service. The security service detects, based on the first request, whether a second amplitude corresponding to the second motion data has reached a target amplitude. After detecting that the second amplitude has reached the target amplitude, the security service sends a message to the sensor service allowing the sending of motion data. The sensor service sends third motion data collected by the target sensor to the first application. The first application displays the first interface based on the third motion data.

[0034] In other words, after selecting the second sub-option, the sensor service will query the security service to determine whether to send motion data to the first application. Furthermore, if the security service detects that the device's motion exceeds a target range, it indicates that the motion control operation has caused a significant movement, and thus it can send a message to the sensor service allowing the transmission of motion data. Subsequently, the sensor service can send motion data to the first application after the device has generated a significant movement, enabling the first application to respond to larger-amplitude motion control operations (i.e., with lower precision) and not to respond to smaller-amplitude motion control operations.

[0035] In one possible design of the first aspect, the aforementioned response to a first motion control operation on the electronic device, namely, not displaying the first interface, includes: in response to the first motion control operation on the electronic device, a sensor service sends first motion data collected by a target sensor to a security service. The security service detects, based on a first request, whether a first amplitude corresponding to the first motion data reaches a target amplitude. Upon detecting that the first amplitude has not reached the target amplitude, the security service does not send a message to the sensor service allowing the transmission of motion data, causing the sensor service to not send motion data to the first application, and the first application not to display the first interface.

[0036] In other words, if the security service detects that the device's movement amplitude does not exceed the target amplitude, it indicates that the motion control operation has caused the device to move at a small amplitude, and therefore motion data transmission can be prevented. Subsequently, the sensor service will not send motion data after the device has generated a small amplitude movement to the first application, so that the first application will not respond to the small amplitude motion control operation. This achieves the goal of not responding to small amplitude motion control operations.

[0037] In one possible design of the first aspect, the electronic device further includes a sensor service and a security service. Upon receiving a selection operation for a second option, in response to a motion control operation on the electronic device, the first interface is not displayed, including: after receiving the selection operation for the second option, the security service sends third status information to the sensor service, such as a disabled state when the screen is on. In response to receiving the third status information, the sensor service sends a second request to the security service, the second request being used to query whether motion data should be sent to the first application. The security service detects whether the first application is displaying a splash screen page based on the second request. After detecting that the first application is displaying a splash screen page, it does not send a message allowing the sending of motion data to the sensor service, causing the sensor service to not send motion data to the first application in response to the motion control operation, and the first application does not display the first interface.

[0038] In other words, after selecting the second option, the sensor service will query the security service to determine whether to send motion data to the first application. Furthermore, if the splash screen is displayed for a certain period, it indicates that the splash screen is not yet finished, thus preventing the sending of motion data. Consequently, the sensor service will not send motion data to the first application, preventing the first application from responding to motion control operations during the splash screen display period. This effectively prevents motion control operations from being responded to during the splash screen display.

[0039] In one possible design of the first aspect, the aforementioned security service detects whether the first application is displaying a splash screen based on a second request, including: the security service periodically detects whether the first application is displaying a splash screen based on the second request. Upon detecting that the first application is not displaying a splash screen, the security service sends a message to the sensor service allowing the transmission of motion data. The sensor service then sends fourth motion data collected by the target sensor to the first application. The first application runs its first function based on the fourth motion data.

[0040] In other words, once the security service detects that the screen has finished loading, it allows the transmission of motion data. Correspondingly, the sensor service sends the motion data to the first application, enabling the first application to respond to motion control operations after the screen has finished loading, thereby running the first function within the first application.

[0041] In one possible design of the first aspect, the electronic device further includes a security service and a sensor service. Upon receiving a selection operation for a third option, in response to a motion control operation on the electronic device, the first interface is not displayed, including: after receiving the selection operation for the third option, the security service sends fourth status information, such as a prohibited state, to the sensor service. In response to receiving the fourth status information, the sensor service, in response to the motion control operation, does not send motion data to the first application, and the first application does not display the first interface.

[0042] In other words, after selecting the third option, the sensor service will not send motion data to the first application, thereby preventing responses to motion control operations.

[0043] Secondly, this application also provides an electronic device including a memory and one or more processors. The memory and processors are coupled. The memory is used to store computer program code, which includes computer instructions. When the computer instructions are executed by the processor, they cause the electronic device to perform the method described in the first aspect and any of its possible design embodiments.

[0044] Thirdly, this application provides a chip system applied to an electronic device including a display panel and a memory; the chip system includes one or more interface circuits and one or more processors; the interface circuits and processors are interconnected via lines; the interface circuits are used to receive signals from the memory of the electronic device and send signals to the processor, the signals including computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device performs the method as described in the first aspect and any of its possible design embodiments.

[0045] Fourthly, this application provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform a method as described in the first aspect and any of its possible design embodiments.

[0046] Fifthly, this application provides a computer program product that, when run on an electronic device, causes the electronic device to perform the method as described in the first aspect and any possible design thereof.

[0047] Understandably, the beneficial effects achieved by the electronic device of the second aspect, the chip system of the third aspect, the computer-readable storage medium of the fourth aspect, and the computer program product of the fifth aspect provided above can be referred to the beneficial effects of the first aspect and any of its possible design embodiments, which will not be repeated here. Attached Figure Description

[0048] Figure 1A This is one of the interface illustrations for a splash screen response;

[0049] Figure 1B The second illustration of a splash screen response interface;

[0050] Figure 1C This is a schematic diagram of interactive content in a splash screen page;

[0051] Figure 2A One of the interface interaction diagrams for setting permission status;

[0052] Figure 2BThe second interactive diagram for setting permission status;

[0053] Figure 3A One of the schematic diagrams of the splash screen provided in the embodiments of this application;

[0054] Figure 3B A second schematic diagram of the splash screen provided in an embodiment of this application;

[0055] Figure 3C A third schematic diagram of the splash screen provided in an embodiment of this application;

[0056] Figure 4A One of the schematic diagrams of the screen opening response provided in the embodiments of this application;

[0057] Figure 4B A second schematic diagram of the screen opening response provided in an embodiment of this application;

[0058] Figure 4C A schematic diagram of in-application interaction responses provided in an embodiment of this application;

[0059] Figure 5A One of the schematic diagrams of the permission status setting interface provided in the embodiments of this application;

[0060] Figure 5B A second schematic diagram of the permission status setting interface provided in an embodiment of this application;

[0061] Figure 6 A schematic diagram of the hardware architecture of a mobile phone provided in an embodiment of this application;

[0062] Figure 7 A schematic diagram of the software architecture of a mobile phone provided in an embodiment of this application;

[0063] Figure 8 This is one of the timing interaction diagrams of the interactive control method provided in the embodiments of this application;

[0064] Figure 9 A schematic diagram illustrating the principle of data filtering provided in the embodiments of this application;

[0065] Figure 10 The second timing interaction diagram of the interactive control method provided in the embodiments of this application. Detailed Implementation

[0066] This application provides an interactive control method applicable to electronic devices. Exemplary examples of the electronic devices in this application include mobile phones, tablets, personal computers (PCs), personal digital assistants (PDAs), netbooks, wearable electronic devices (e.g., smartwatches, smart bracelets), augmented reality (AR) devices, virtual reality (VR) devices, in-vehicle devices, smart screens, smart cars, smart speakers, robots, etc. This application does not impose any special limitations on the specific form of the electronic device. The following description will primarily use a mobile phone as an example to illustrate the solution of this application.

[0067] The method provided in this application can be applied to splash screen interaction scenarios. Specifically, a splash screen interaction scenario refers to a scenario where, after an application (hereinafter referred to as the application) is launched, the mobile phone displays a splash screen page, which includes interactive content and responds to the user's interactive operations on the interactive content.

[0068] Application launch can occur when no application process exists on the phone, commonly known as a cold start. Alternatively, application launch can occur when an application is brought to the foreground from the background, commonly known as a warm start. This application does not specifically limit the scope of the application launch.

[0069] Specifically, the application can be launched in the following ways: in response to the user clicking the application icon on the desktop; in response to the user clicking any task in the multitasking management interface; in response to the user clicking the share link corresponding to the application; in response to the user clicking the notification message corresponding to the application in the notification bar, etc.

[0070] The interactive content can include at least one of the following formats: images, text, and videos. For example, interactive content can include product images, application icons, and video stills.

[0071] A typical splash screen interaction scenario is as follows: After the application launches, the phone can display a splash screen containing interactive content. When the phone detects a shaking motion, it can jump from the current splash screen to the interface corresponding to the interactive content. Conversely, if the phone does not detect a shaking motion (i.e., shake the phone), it remains on the splash screen until the interactive content display time (e.g., 5 seconds) ends, at which point the phone displays the application interface and no longer shows the interactive content.

[0072] The above splash screen interaction scenario is illustrated using a video application as an example. Figure 1AAs shown, the phone can display a desktop interface 101. Desktop interface 101 includes application icons for applications such as clock, calendar, gallery, settings, and video; for example, the application icon for the video application is "Video" 1011. In response to a user's click on "Video" 1011 on desktop interface 101, the phone can display a splash screen 102. Splash screen 102 includes interactive content 1021. When the phone detects a shaking motion, it can jump from the current splash screen 102 to the interactive content interface 103 corresponding to interactive content 1021 (for example, interactive content interface 103 could be the purchase interface corresponding to interactive content 1021). Conversely, if the phone does not detect a shaking motion, it remains on splash screen 102 until the display duration of the interactive content (e.g., 5 seconds) ends, at which point the phone will display... Figure 1B The first application interface 104 of the video application shown no longer displays interactive content.

[0073] Of course, in addition to shaking the phone as mentioned above, interactive operations can also include clicking on interactive content (such as...). Figure 1C The operations include those on the interactive content 1051 in the splash screen 105, and operations such as flipping the phone. For example, after the application is launched, the phone can display the splash screen 105, which includes interactive content 1051. When the phone detects a click on the interactive content 1051, it jumps to the interface corresponding to the interactive content 1051.

[0074] In addition to redirecting to the interface corresponding to the interactive content, the interactive action can also include adding the interactive content to the shopping cart, sharing the interactive content with friends, etc. This application does not specifically limit this. The following text will mainly use this typical splash screen interaction scenario to illustrate the solution of this application.

[0075] In some implementations, even a slight shake of the phone can cause a redirect. In some cases, this redirection is not what the user expects and can be inconvenient. In other words, there may be situations where the user does not want to be redirected, but the phone still redirects.

[0076] To address the issue of the aforementioned unexpected redirection, some improved solutions allow users to configure whether or not to allow redirection during the startup screen in the settings app. Subsequently, in startup screen interaction scenarios, the phone can control the startup screen redirection based on the user's selection, as shown below. Figure 1A , Figure 2A and Figure 2B As shown.

[0077] like Figure 1A As shown, the desktop interface 101 includes an application icon for the settings application, such as "Settings" 1012. Figure 2AAs shown, in response to the user's click on "Settings" 1012 on the desktop interface 101, the phone can display the phone settings interface 201. Interface 201 includes settings such as mobile network, Bluetooth, battery, and permission management, such as the permission management setting item "Permissions" 2011.

[0078] Continue as Figure 2A As shown, in response to the user's click on "Permissions" 2021 in interface 201, the phone can display the permission settings interface 202. The permission settings interface 202 includes settings such as: all application behavior records, microphone usage permission, camera usage permission, and permission management, such as the permission management setting "Permission Management" 2021.

[0079] like Figure 2A As shown, in response to the user's click on "Permission Management" 2022 in the permission settings interface 202, the phone can display the permission management interface 203. The permission management interface 203 includes application options for applications such as clock, music, file manager, browser, recorder, video, and health, such as the application option "Video" 2031 for the video application.

[0080] like Figure 2B As shown, in response to the user's click on "Video" 2031 in the permission management interface 203, the mobile phone can display the permission control interface 204 for the video application. The permission control interface 204 includes settings for various permissions in the video application and their open / closed status. Settings may include "Phone," "Device Actions and Orientation," "Camera," "Location Information," "Microphone," and "SMS," with corresponding open / closed statuses of "Allow," "Allow," "Disallow," "Allow," "Allow," and "Disallow." "Allow" indicates that the application can obtain the corresponding permission, while "Disallow" indicates that the application cannot obtain the corresponding permission. For example, if the open / closed status of "Device Actions and Orientation" 2041 is "Allow," it means that the video application can obtain device actions and orientation, which can be used to detect interactive operations and trigger jumps in splash screen interaction scenarios.

[0081] Continue as Figure 2BAs shown, in response to a click on any permission setting item in the permission control interface 204, the phone can display the corresponding permission settings interface, allowing the user to modify the permission's access status. In response to the user's modification, the phone can update the permission's access status. Taking "Device Actions and Directions" 2041 in the permission control interface 204 as an example, in response to a user's click on "Device Actions and Directions" 2041 in the permission control interface 204, the phone can display the "Device Actions and Directions" permission settings interface 205. The "Device Actions and Directions" permission settings interface 205 includes three options: "Allow" 2051, "Disallow only when screen is on" 2052, and "Disallow" 2053. "Allow" 2051 is selected, indicating that the "Device Actions and Directions" permission is currently allowed, which is consistent with the access status of "Device Actions and Directions" 2041 in the permission control interface 204.

[0082] In response to the user's selection of "Disallow only on screen unlocking" in the "Device Actions and Orientation" permission settings interface 205, the phone can modify the "Device Actions and Orientation" permission to be disabled only on screen unlocking. This means that device actions and orientation cannot be obtained during screen unlocking interactions. Consequently, the phone will not respond to user interactions or trigger redirects during screen unlocking interactions.

[0083] In response to the user's selection of "Disallow" 2053 in the "Device Actions and Orientation" permission settings interface 205, the phone can modify the "Device Actions and Orientation" permission to be disabled. This means that during the operation of the video application (including splash screen interaction scenarios), the phone cannot obtain device actions and orientation. Therefore, in splash screen interaction scenarios, the phone will naturally not respond to the user's interaction to trigger a redirect.

[0084] As can be seen, in the above-mentioned improved solutions, after the user selects "Disallow" (2051) or "Disallow only on startup" (2052), the phone will not redirect in the startup screen interaction scenario, thus solving the problem of unexpected redirection to some extent. However, the above-mentioned improved solutions have at least the following drawbacks:

[0085] 1. The access points for permission settings are deeply buried, making them difficult for users to reach. For example, the process of navigating from desktop interface 101 to phone settings interface 201, and then from phone settings interface 201 to the "Device Actions and Orientation" permission settings interface 205, involves six pages. Furthermore, the operation steps are cumbersome and inefficient. For instance, if a user wants to operate on each of the six interfaces mentioned above, at least six steps are required to complete the setting.

[0086] 2. Even when the device's action and direction are set to "allowed," if the user selects "allow" 2051, there may still be issues with the redirection not meeting the user's expectations.

[0087] To address the aforementioned issues, this application provides an interactive control method in which a mobile phone can display control buttons (or options) on the splash screen. These control buttons can be used to set the precision of responses to interactive operations in the splash screen interaction scenario. In response to a user's trigger operation on the control buttons, such as a click or swipe, the mobile phone can respond to the interactive operation with the precision indicated by the trigger operation.

[0088] For example, if the control buttons have multiple options corresponding to different levels of precision, see [link / reference]. Figure 1A and Figure 3A In response to a user's click on the "Video" application icon 1011 on the desktop interface 101, the phone can display a splash screen 301. The splash screen 301 includes interactive content 1021 and a first pop-up window 3011. The first pop-up window 3011 includes "Precise Action" 3012 and "Fuzzy Action" 3013. "Precise Action" 3012 (also known as the first sub-option) and "Fuzzy Action" 3013 (also known as the second sub-option) are options corresponding to two different levels of precision. After the phone receives the user's selection of "Precise Action" 3012, in response to the user's first amplitude interactive operation (such as shaking the phone), the phone can jump to the interface corresponding to the interactive content 1021, such as... Figure 1A The interactive content interface 103. After the mobile phone receives the user's selection of "fuzzy action" 3013, in response to the user's second-amplitude interactive operation (such as shaking the phone), the mobile phone can jump to the interface corresponding to the interactive content 1021, such as... Figure 1A The interactive content interface 103 is described above. The first amplitude is smaller than the second amplitude. That is, when a user selects "precise action" 3012 or "fuzzy action" 3013, the phone can respond to interactive operations of different amplitudes, thus controlling the precision of the phone's response. For example, if a user doesn't want a slight shake of the phone to trigger a jump, they can select "fuzzy action" 3013, and the phone will only jump when it detects a larger amplitude (such as the second amplitude mentioned above).

[0089] Therefore, adopting the embodiments of this application demonstrates two advantages: First, the mobile phone can provide control buttons on the splash screen, eliminating the need for users to search for and configure corresponding entry points in the settings application. This approach is more accessible and has a higher reach rate. Furthermore, users can complete settings simply by operating the control buttons, avoiding multiple steps across various interfaces, simplifying the operation and improving human-computer interaction efficiency. Second, the control buttons provided by the mobile phone can be used to set the precision of the response to interactive operations. This allows users to adjust the response precision according to their needs, enabling the mobile phone to respond to interactive operations of varying degrees based on the user's settings. The response results better match the user's expectations, thus improving the user experience.

[0090] Therefore, it should be noted that: the above Figure 3A In the example, there are two options corresponding to multiple levels of precision. In practice, there can also be three, four, five, etc. Each option corresponds to a level of precision. In response to the user's trigger operation on any option, the mobile phone can respond to the interactive operation of the target amplitude. The target amplitude is matched with the precision corresponding to any option. The lower the precision, the larger the target amplitude.

[0091] Furthermore, the control button can take other forms besides options; for example, it can be a control bar. The control button may also not be presented in the pop-up window; for instance, it can be presented in a notification message. This application does not impose any specific limitations on these aspects. The following explanation primarily uses the form of displaying options in a pop-up window as an example.

[0092] For ease of explanation, the application that displays the splash screen can be referred to as the first application, as mentioned above. Figure 1A and Figure 3A The video application in the example is the first application. The splash screen that includes multiple options corresponding to different levels of precision is called the first splash screen, as described above. Figure 3A The splash screen shown is 301. The interactive content displayed on the first splash screen is referred to as the first interactive content, as described above. Figure 3A The interactive content 1021 in the splash screen 301 shown is an example. The interactive operation is referred to as a motion control operation, where the first amplitude interactive operation can be called the first motion control operation, and the second amplitude interactive operation can be called the second motion control operation. The interface that the user jumps to in response to the interactive operation is called the first interface, that is, the interface corresponding to the first interactive content, such as... Figure 1A The interactive content interface 103 in the middle.

[0093] Furthermore, the splash screen may also include initial prompts for interactive operations, thereby indicating the triggering of the corresponding interactive operation. These initial prompts may include: an icon for the interactive operation, the name of the interactive operation, etc., where the name of the interactive operation could be the text "Shake Phone" 1022 on splash screen 102, or the text "Click" 1052 on splash screen 105. Furthermore, the phone may also use sound, vibration, or other methods to indicate the form of the interactive operation. This application does not specifically limit this aspect.

[0094] In some embodiments, the pop-up window may also include an always-allow option (also known as the first option), and the options corresponding to the above multiple precisions (such as "precise action" 3012 and "fuzzy action" 3013) are always-allow sub-options.

[0095] In one specific implementation, the phone can simultaneously display the "Always Allow" option and multiple options corresponding to different levels of precision in a pop-up window. See also... Figure 1A and Figure 3B In response to a user's click on the "Video" application icon 1011 in the desktop interface 101, the phone can display a splash screen 302. The splash screen 302 includes interactive content 1021 and a second pop-up window 3021. The second pop-up window 3021 includes "Precise Action" 3012 and "Blurred Action" 3013, and also includes "Always Allow" 3023, which is an always-allowed option.

[0096] In another specific implementation, the phone can display an "Always Allow" option in a pop-up window. In response to the user's selection of the "Always Allow" option, such as a click, the phone can display multiple options with varying degrees of precision in the pop-up window. See also... Figure 1A and Figure 3B In response to a user's click on the "Video" application icon 1011 of the video application on the desktop interface 101, the phone can display a splash screen 303. The splash screen 303 includes interactive content 1021 and a third pop-up window 3031. The third pop-up window 3031 includes "Always Allow" 3023. In response to a user's click on "Always Allow" 3023, the phone can display a splash screen 302. Optionally, after displaying multiple precision options, the phone may not display the "Always Allow" option, such as the splash screen 303 not including "Always Allow" 3023. For ease of explanation, a splash screen including the "Always Allow" option can be used as an example. Figure 3B The splash screen 303 in the context is referred to as the second splash screen. Furthermore, the splash screen displayed in response to the user's click on the always-allowed option, such as... Figure 3B The splash screen 302 in the text can also be called the first splash screen.

[0097] Therefore, it should be noted that the relative positions of the multiple precision options and the always-allowed option are not based on... Figure 3B The above is a limited description. For example... Figure 3C As shown, the phone can also display a splash screen 304, which includes a fourth pop-up window 3041. In the fourth pop-up window 3041, "Precise Action" 3012 and "Fuzzy Action" 3013 are located above "Always Allow" 3023.

[0098] After the user selects any of the multiple options corresponding to different levels of precision, in the splash screen interaction scenario, the phone can respond to the interactive operation, such as navigating to the interface corresponding to interactive content 1021. Furthermore, when subsequently displaying the application interface (excluding the splash screen), the phone can respond to operations similar to the interactive operation (such as shaking the phone, flipping the phone, etc.), thereby running in-app functions (also known as primary functions), such as shaking to provide feedback (see below for details). Figure 4C (Introduction), shake to search for nearby people, etc.

[0099] Furthermore, after the user performs a trigger action on any option, in the splash screen interaction scenario, the phone can respond to the interaction action of the target magnitude. This is followed by the display of the application interface (excluding the splash screen, also known as the second interface, as described below). Figure 4C When the user selects an interface (104) on the splash screen, the phone can respond to a third-level interaction to trigger the execution of functions within the application. The third level is less than or equal to a target level, which can be the second level mentioned above. For example, the third-level interaction could be the same as the first-level interaction. This ensures that the precision of the user's selection on the splash screen does not affect the precision of the functions within the application, thus guaranteeing the normal use of the application and improving the user experience.

[0100] User interactions cause the phone to move, resulting in changes in parameters such as acceleration, angle, and displacement. In this article, amplitude can refer to the change in one or more of these parameters caused by the phone's movement. The following example uses the phone's rotation angle as the amplitude to illustrate this solution.

[0101] With any option is Figure 3A Taking the "fuzzy action" 3013 in the splash screen 301 as an example, after the user performs a click operation on the "fuzzy action" 3013 in the splash screen 301, the following situations may occur:

[0102] Scenario a: The user shakes the phone, causing the phone to... Figure 4A The motion is shown by angle α. Here, angle α is the angle by which the phone rotates in one direction, as shown... Figure 4AThe angle of rotation within the plane shown is α. Angle α reaches the second amplitude, thus satisfying the accuracy requirement corresponding to "fuzzy action" 3013. Therefore, in response to movement at angle α, the phone does not jump.

[0103] Scenario b: The user shakes the phone, causing the phone to... Figure 4B The motion is represented by angle β. Here, angle β is the angle by which the phone rotates in one direction, as shown. Figure 4B The angle of rotation within the plane shown. The β angle does not reach the second amplitude and does not meet the accuracy requirement corresponding to the "fuzzy action" 3013. Therefore, the phone does not respond to the movement at the β angle and remains on the splash screen 102 until the display duration of the interactive content 1021 (e.g., 5 seconds) ends, at which point the phone no longer displays the interactive content.

[0104] Scenario c: After the display duration of interactive content 1021 ends, or after navigating to the interface corresponding to interactive content 1021 and returning to the video application, if the user clicks the back button 1031 in the interactive content interface 103 to return to the video application, the mobile phone can display... Figure 4C The first application interface 104 of the video application is shown. While the first application interface 104 is displayed, the user shakes the phone, causing the phone to... Figure 4C The phone can display the β-angle motion shown. Figure 4C The second application interface 401 is shown.

[0105] The second application interface 401 includes a feedback window 4011, which contains two options: "Direct Feedback" 4012 and "Automatic Screenshot Feedback" 4013. "Direct Feedback" 4012 and "Automatic Screenshot Feedback" 4013 are options corresponding to two different feedback methods. In response to the user's selection of the "Direct Feedback" option, the phone can display the feedback interface, allowing the user to report problems encountered while using the video application. In response to the user's selection of the "Automatic Screenshot Feedback" option, the phone can take a screenshot of the current application interface and use the screenshot as the problem interface to report issues encountered while using the video application.

[0106] It is evident that after a user performs a click operation on the "fuzzy action" 3013 in the splash screen 302, it can affect the accuracy of the phone's response to the interactive operation in the splash screen interaction scenario. However, the phone still responds to the shake feedback function in the video application with a high degree of accuracy.

[0107] In some embodiments, the pop-up window may also include a disable option when the screen is opened (also known as a second option), such as... Figure 3B The "Disable on startup" option 3024 is shown in the splash screen 302.

[0108] In response to the user's selection of the disabled option during the splash screen, the phone will not respond to interactive operations during the splash screen interaction scenario. That is, after receiving a motion control operation, the phone will not jump to the interface corresponding to the interactive content, such as the interface corresponding to interactive content 1021. Furthermore, when subsequently displaying the application interface (excluding the splash screen, also known as the second interface), the phone can respond to operations similar to the interactive operation to run functions within the application. For example, the phone can respond to a third-amplitude operation to trigger the execution of functions within the application (such as shaking to provide feedback), as explained above, and will not be repeated here.

[0109] In some embodiments, the pop-up window may also include a disable option (also known as a third option), such as... Figure 3B The "prohibited" option 3025 appears in the splash screen 302.

[0110] In response to the user's selection of the "disable" option, the phone will not respond to the interactive operation in the splash screen interaction scenario. That is, after receiving a motion control operation, the phone will not jump to the interface corresponding to the interactive content, such as the interface corresponding to interactive content 1021. Furthermore, when subsequently displaying the application interface (excluding the splash screen, also known as the third interface), the phone will not respond to operations of the same type as the interactive operation. For example, the phone cannot trigger the execution of functions within the application by responding to third-level motion operations; please refer to the previous explanation for details, which will not be repeated here.

[0111] In some embodiments, the pop-up window may further include a second prompt message. The second prompt message is used to indicate the purpose of the pop-up window, thereby facilitating the user's selection of the appropriate option. Continuing as... Figure 3B As shown, the second pop-up window 3021 includes a prompt message 3022, which contains the text: "Obtain device action and direction information to implement functions such as shaking," indicating the function of each option in the pop-up window. That is, prompt message 3022 is the second prompt message.

[0112] The above Figures 3A-3C The pop-up windows and their options in the examples provided are merely illustrative, and this application does not impose any specific limitations on them. For instance, the mobile phone can adjust the position, size, and shape of the pop-up windows and their options according to actual needs. For example, if the phone screen is large, or in elderly mode, the options in the pop-up window can be set larger than described above. Figures 3A-3C The larger the pop-up window, the more likely it is to be larger. For example, the shape of a pop-up window can also be a rhombus, a circle, an oval, etc.

[0113] Of course, the pop-up window may not include one or more of the options to disable on startup, options to disable on startup, and second prompt information. This application embodiment does not limit this.

[0114] In some embodiments, after the user selects an option in the pop-up window, the phone closes the pop-up window and does not display it again when the user enters the splash screen next time (see the description of the first condition that must be met to display the pop-up window below).

[0115] In addition, the phone will close the pop-up if the user does not select an option in the pop-up: the pop-up times out (e.g., 5 seconds), the user clicks on another area outside the pop-up, or the user actively switches applications or pages. In these cases, the phone will not respond to the user's interactive operations on the interactive content 1021 on the splash screen (e.g., shaking the phone) and will not redirect. After the phone closes the pop-up, it will still display the pop-up the next time the splash screen is accessed, provided the first condition for displaying the pop-up is met. If the user does not select an option in the pop-up after multiple (e.g., 3) pop-ups, the phone will subsequently reduce the frequency of displaying the pop-up on the splash screen, such as displaying it once a week, once every 10 interactive content displays, or once when interactive content is first displayed after each boot.

[0116] As mentioned above, users can adjust the precision of video application response to interactive actions in the pop-up window. Additionally, users can also configure this in the application's permission settings interface, such as by selecting an option (also known as the first action) to adjust the precision of the video application's response to interactive actions.

[0117] Specifically, the permission status settings interface can include multiple options corresponding to different levels of precision. For example... Figure 5A As shown, the phone can display a first permission status setting interface 501. This interface is an application interface within the settings app. It includes "Precise Action" 5011 (also known as the third sub-option) and "Fuzzy Action" 5012 (also known as the fourth sub-option), corresponding one-to-one with "Precise Action" 3012 and "Fuzzy Action" 3013 mentioned earlier. "Precise Action" 5011 and "Fuzzy Action" 5012 represent two different levels of precision. For example, after receiving a user's selection of "Precise Action" 5011, the subsequent interaction in the video application's splash screen will respond to the user's interaction with the precision corresponding to the precise action. Similarly, after receiving a user's selection of "Fuzzy Action" 5012, the subsequent interaction in the video application's splash screen will respond to the user's interaction with the precision corresponding to the precise action. For details on the specific functions of "precise action" 5011 and "fuzzy action" 5012, please refer to the previous explanations of "precise action" 3012 and "fuzzy action" 3013, which will not be repeated here.

[0118] Furthermore, the permission settings interface can also include a "disable on startup" option, and so on. Figure 5A The first permission status setting interface 501 shows "Disable on Startup" 5013. This corresponds to "Disable on Startup" 3024 in the second pop-up window 3021 mentioned earlier. After receiving the user's selection of "Disable on Startup" 5013, the phone will not respond to interactive operations in subsequent video application startup interaction scenarios, such as not jumping to the interface corresponding to interactive content 1021. However, when the application interface (excluding the startup page) is subsequently displayed, the phone can respond to operations similar to the interactive operation, thereby running the functions within the application. For the specific function of "Disable on Startup" 5013, please refer to the previous explanation of "Disable on Startup" 3024, which will not be repeated here.

[0119] Furthermore, the permission status settings interface can also include a disable option, and so on. Figure 5A The first permission status setting interface 501 shows "Disable" option 5014. This corresponds to "Disable" option 3025 in the second pop-up window 3021 mentioned earlier. After receiving the user's selection of "Disable" option 5014, the phone will not respond to interactive operations in subsequent video application splash screen interaction scenarios, such as not jumping to the interface corresponding to interactive content 1021. Simultaneously, when displaying the application interface later, the phone will not respond to operations of the same type as the interactive operation. For the specific function of "Disable" option 5014, please refer to the previous explanation of "Disable" option 3025; it will not be repeated here.

[0120] In some embodiments, the permission status setting interface may also include an "Always Allow" option, and the options corresponding to the various levels of precision (such as "Precise Action" 5011 and "Fuzzy Action" 5012) are sub-options of the "Always Allow" option. Continuing as... Figure 5A The second permission status setting interface 502 shown includes "Always Allow" 5013, which corresponds to "Always Allow" 3023 in the third pop-up window 3031 mentioned above. In response to the user's click operation on "Always Allow" 5013 in the second permission status setting interface 502, the mobile phone can display the first permission status setting interface 501.

[0121] For instructions on how to access the permission settings interface from the Settings app, please refer to [link / reference]. Figure 1A , Figure 2A and Figure 2B The user navigates from the desktop interface 101 to the phone settings interface 201, and then from the phone settings interface 201 to the permission control interface 204. In response to the user's click on "Device Actions and Directions" 2041 in the permission control interface 204, the phone can display... Figure 5A The first permission status settings interface shown is 501. The pages accessed by different phones when entering the permission status settings interface for an application do not strictly follow the same pattern. Figure 2A and Figure 2BThe operation steps can be skipped, depending on the specific situation.

[0122] If the phone has not displayed a pop-up on the app's splash screen, or if the phone has displayed a pop-up on the app's splash screen but the user has not selected any options in the pop-up, then all options in the permission settings interface will be unselected. For example, Figure 5A In the first permission status setting interface 501 shown, none of the options are selected.

[0123] Users can set permission status in the permission status settings interface, and the phone can control the screen navigation based on the user's selection. For example, in response to a user's click operation on the first permission status settings interface 501, which includes a "fuzzy action" 5012, the phone can display the third permission status interface 503. At this time, the option corresponding to the "fuzzy action" 5012 is updated to the selected state, and the button corresponding to the permission status is updated to a black or solid state.

[0124] If a user selects an option in the pop-up window on the splash screen, or sets it in the settings app, the corresponding option will be selected in the permission status settings interface. For example, if a user selects "fuzzy action" 3013 in the second pop-up window 3021 on the splash screen, after entering the settings app, as shown in the third permission status interface 503, the option corresponding to "fuzzy action" 5012 will be selected.

[0125] Users can also modify the selected permission status in the permission status settings interface. As shown in the third permission status interface 503, the user has selected the fuzzy action permission status. If the user wants to change the permission status to the precise action status, they can select the option corresponding to "Precise Action" 5011. In response to the user's selection of "Precise Action" 5011 in the third permission status interface 503, the phone displays the fourth permission status interface 504. In the fourth permission status interface 504, the option corresponding to "Fuzzy Action" 5012 is updated to an unselected state, and the option corresponding to "Precise Action" 5011 is updated to a selected state. Therefore, in subsequent video application splash screen interaction scenarios, the user's interaction will be responded to with the precision corresponding to the precise action.

[0126] Conversely, if the user has already selected "Precise Action" 3012 in the pop-up window, the phone can respond to the user's first interaction on the splash screen and jump to the interface corresponding to the interaction content. Subsequently, when the phone displays the application's permission settings interface (also known as the fifth interface), "Precise Action" 5011 can be selected, while "Fuzzy Action" 5012 is not selected. In response to the user's selection of "Fuzzy Action" 5012 on the fifth interface, the phone can select "Fuzzy Action" 5012 and deselect "Precise Action" 5011. Later, when the application is launched again, the phone can display the splash screen (also known as the sixth splash screen), which includes interaction content triggered by motion control operations (also known as the fourth interaction content, which can be the same as the first interaction content mentioned above). This sixth splash screen does not include multiple options corresponding to different levels of precision. When the sixth splash screen is displayed, the phone will not respond to the user's first interaction, but it can respond to the second interaction and jump to the interface corresponding to the interaction content.

[0127] This application embodiment exemplarily describes the first condition that must be met for a mobile phone to display pop-ups (such as the first pop-up 3011, the second pop-up 3021, the third pop-up 3031, etc.) on the splash screen. The first condition includes one or more of the following:

[0128] 1. Interactive operation refers to the operation that requires obtaining the device's motion and direction, i.e., motion control operation.

[0129] When detecting interactive operations targeting interactive content, such as tapping or swiping the screen, if it is not necessary to obtain "device action and orientation" information (such as motion data such as phone posture, orientation, and position), it means that the user does not need to select the permission status, and therefore no pop-up window needs to be displayed.

[0130] When the phone detects interactive operations on interactive content, such as shaking the phone or flipping the phone, and needs to obtain "device action and orientation" information, it indicates that the user needs to select the permission status, so a pop-up window can be displayed.

[0131] Conversely, when the phone detects an interactive operation targeting interactive content, it does not need to obtain "device action and direction" information. For example, if it's a click or swipe, it means the user does not need to select a permission status, and a pop-up window does not need to be displayed. Correspondingly, it will not include multiple options corresponding to different levels of precision, such as "precise action" 3012 and "fuzzy action" 3013. For ease of explanation, the splash screen displayed in this case can be referred to as the third splash screen, and the interactive content on the third splash screen can be referred to as the second interactive content, as mentioned above. Figure 1CThe splash screen 105 shown is the third splash screen, and the interactive content 1051 in splash screen 105 is the second interactive content.

[0132] 2. The phone did not display a pop-up window on the splash screen; or, the phone did display a pop-up window on the splash screen, but did not receive any user selection of options in the pop-up window.

[0133] If condition "2" is met, it means that the user has not set the permission status in the pop-up window, so the user needs to select the permission status, and therefore the pop-up window can be displayed.

[0134] If condition "2" is not met—that is, if the phone has displayed a pop-up window on the splash screen and received a user's selection of an option in the pop-up window (such as "Precise Action" 3012 or "Fuzzy Action" 3013)—then it indicates that the user does not need to select a permission status, and therefore the pop-up window does not need to be displayed. For ease of explanation, the splash screen that is displayed again after the user has selected an option in the pop-up window can be called the fourth splash screen. The fourth splash screen can also include the aforementioned first interactive content, but it does not include multiple options corresponding to different levels of precision, such as "Precise Action" 3012 and "Fuzzy Action" 3013.

[0135] 3. The phone did not receive the user's selection of options in the permission status settings interface.

[0136] If condition "3" is met, it indicates that the user has not set the permission status in the permission status settings interface, and the user needs to select the permission status. Therefore, a pop-up window can be displayed, such as the one shown above. Figures 3A-3C The splash screen shown.

[0137] Conversely, if condition "3" is not met, it indicates that the user has already set the permission status, and there is no need to display a pop-up window. One scenario is as follows: Display the permission status settings interface (also known as the fourth interface) of a second application (such as an application different from the video application mentioned above). After receiving the operation of selecting an option in the fourth interface (also known as the second operation), the phone can set the second application's permissions to obtain device action and direction information (i.e., motion data). Subsequently, after launching the second application, a splash screen (also known as the fifth splash screen) can be displayed. The splash screen includes interactive content (also known as the third interactive content), but does not include multiple options corresponding to different levels of precision, such as "Precise Action" 3012 and "Fuzzy Action" 3013, etc.

[0138] In summary, the conditions for displaying a pop-up window have been outlined. If any one condition is not met, the phone may not display the pop-up window. All three conditions must be met for the phone to display the pop-up window. That is, if any one of conditions "1", "2", or "3" is not met, the phone may not display the pop-up window. If all three conditions are met, the phone may display the pop-up window.

[0139] The following is a complete example illustrating the conditions for displaying the pop-up window mentioned above:

[0140] Upon first launch after app installation, the phone displays a splash screen. Detecting interactive actions on the splash screen does not require obtaining "device action and orientation" information (such as "click" 1052 in splash screen 105), thus not satisfying "1" above. In this case, the phone will not display a pop-up window. After the splash screen display ends, the shake function within the video app responds normally (such as the shake feedback function within the video app).

[0141] Next, in response to the second app launch, the phone launches the app and displays the splash screen. If the splash screen detects that an interactive operation (such as shaking the phone) requires "device action and orientation" information, and no permission settings have been configured in the app's permission settings interface up to that point, then conditions "1", "2", and "3" are met, and the phone displays a pop-up window. Subsequently, the phone can receive the user's selection of options in the pop-up window and respond to interactive operations based on the user's selection.

[0142] Next, in response to the application launch operation, the phone launches the application and displays the splash screen. If the splash screen detects that the interaction requires "device action and orientation" information, and "2" above is not met, the phone will not display a pop-up window. The phone controls the splash screen response based on the user's previous selection.

[0143] In this embodiment, the mobile phone can obtain the device's motion information based on the options selected by the user in the pop-up window, and then identify and respond to interactive operations that reach the target amplitude (which can be either the first amplitude or the second amplitude mentioned above). This allows for a more precise response based on user settings, resulting in responses that better meet user expectations and improve the user experience.

[0144] like Figure 6As shown, the mobile phone 100 may include a processor 110, an external memory interface 120, an internal memory 121, an antenna 1, an antenna 2, a mobile communication module 130, a wireless communication module 140, an audio module 150, a speaker 150A, a receiver 150B, a microphone 150C, a headphone jack 150D, a sensor module 160, buttons 170, a motor 171, an indicator 172, a camera module 173, a display screen 174, and a subscriber identification module (SIM) card interface 175, etc. The sensor module 160 may include a gyroscope sensor 160A, an accelerometer sensor 160B, a gravity sensor 160C, a linear acceleration sensor 160D, a magnetic sensor 160E, an orientation sensor 160F, a rotation vector sensor 160G, a touch sensor 160H, etc.

[0145] It is understood that the structure illustrated in the embodiments of this application does not constitute a specific limitation on the mobile phone 100.

[0146] The processor 110 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU).

[0147] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0148] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the mobile phone 100.

[0149] The wireless communication function of mobile phone 100 can be implemented through antenna 1, antenna 2, mobile communication module 130, wireless communication module 140, modem processor, and baseband processor. Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in mobile phone 100 can be used to cover one or more communication frequency bands.

[0150] The mobile communication module 130 can provide solutions for wireless communication applications including 2G / 3G / 4G / 5G on the mobile phone 100. The mobile communication module 130 may include at least one filter, switch, power amplifier, low-noise amplifier (LNA), etc. The mobile communication module 130 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation.

[0151] The wireless communication module 140 can provide solutions for wireless communication applications on the mobile phone 100, including WLAN (such as wireless fidelity, Wi-Fi), Bluetooth, global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR) technology, etc.

[0152] The mobile phone 100 uses a GPU, a display screen 174, and an application processor to achieve its display function. The GPU is a microprocessor for image processing, connecting the display screen 174 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering.

[0153] The display screen 174 is used to display images, videos, etc. The display screen 174 includes a display panel.

[0154] The mobile phone 100 can perform shooting functions through the ISP, camera module 173, video codec, GPU, display 174, and application processor. The ISP is used to process the data fed back by the camera module 173. The camera module 173 is used to capture still images or videos.

[0155] The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the mobile phone 100. The external storage card communicates with the processor 110 through the external storage interface 120 to perform data storage functions.

[0156] The internal memory 121 can be used to store computer executable program code. The processor 110 executes various functional applications and data processing of the mobile phone 100 by running instructions stored in the internal memory 121.

[0157] The mobile phone 100 can achieve audio functions, such as music playback and recording, through the audio module 150, speaker 150A, receiver 150B, microphone 150C, headphone jack 150D, and application processor.

[0158] The gyroscope sensor 160A can be used to measure the angular velocity of the mobile phone 100, thereby determining the motion attitude of the mobile phone 100. The gyroscope sensor 160A is designed based on the law of conservation of angular momentum. In some embodiments, the angular velocity of the mobile phone 100 about three axes (i.e., the x, y, and z axes) can be determined by the gyroscope sensor 160A.

[0159] The accelerometer 160B can detect the magnitude of the acceleration of the mobile phone 100 in various directions (generally three axes). The accelerometer 160B calculates the acceleration value by measuring the change in force caused by the acceleration. When the mobile phone 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to recognize the phone's posture, which is applicable to switching between portrait and landscape modes.

[0160] The gravity sensor 160C can detect changes in the position of the mobile phone 100 in three-dimensional space, and thus measure the gravity acting on the mobile phone 100. The gravity sensor 160C can also be used to identify the phone's posture and motion information.

[0161] The Linear Accelerometer 160D is a sensor that measures dynamic acceleration, used to detect the linear motion of the mobile phone 100, and accurately measures linear acceleration. It does not include acceleration caused by gravity. The Linear Accelerometer 160D offers higher accuracy compared to gravitational acceleration.

[0162] The magnetic sensor 160E includes a Hall sensor. Based on the principle of magnetic field induction, the magnetic sensor 160E can detect information such as the Earth's magnetic field and the rotation direction of the mobile phone 100. It determines the angle of the mobile phone 100 relative to the direction of the magnetic field by measuring the effect of the magnetic field on the coil.

[0163] The orientation sensor 160F can detect the orientation of the mobile phone 100 in three-dimensional space, and is used to identify the attitude of the mobile phone 100. The orientation sensor 160F obtains the attitude information of the mobile phone 100 by measuring parameters such as the rotation angle, angular velocity and acceleration of the mobile phone 100.

[0164] The rotation vector sensor 160G can detect the force or torque generated by the rotation of the mobile phone 100, and calculate the rotation angle of the mobile phone 100 by integrating the acceleration and angular velocity. The rotation vector sensor 160G is used to measure the rotational motion of the mobile phone 100 and can provide rotational attitude information of the device.

[0165] Touch sensor 160H, also known as a "touch device," can be placed on display screen 174. The touch sensor 160H and display screen 174 together form a touch screen, also known as a "touchscreen." Touch sensor 160H is used to detect touch operations applied to or near it.

[0166] In some embodiments, in a splash screen interaction scenario, the mobile phone can detect and respond to interactive operations based on data collected by one or more of the aforementioned sensors.

[0167] The software system of mobile phone 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment takes the layered architecture Android system as an example to illustrate the software structure of electronic device 100.

[0168] Figure 7 This is a software structure block diagram of a mobile phone 100 according to an embodiment of this application. The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system consists of an application layer, an application framework layer, and a kernel layer from top to bottom.

[0169] The application layer can include a range of application packages, such as maps, camera, calendar, call, clock, voice recorder, settings, WLAN, Bluetooth, music, and video applications.

[0170] The settings application can display pop-ups and receive user selections from both the pop-ups and the permission settings interface, facilitating user management of the application's permission status for sensors. Furthermore, the settings application includes a pop-up module and a permission settings interface module. Specifically, the pop-up module displays the pop-ups and receives user selections from the pop-ups. The permission settings interface module receives user selections from the permission settings interface.

[0171] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0172] The application framework layer may include an activity manager, security services, application operation services, sensor services, etc.

[0173] The Activity Manager Service (AMS) provides the Activity Management Service, which is used for starting, switching, and scheduling system components (such as activities, services, content providers, and broadcast receivers), as well as managing and scheduling application processes. The Activity Management Service can monitor the application's lifecycle. In some embodiments, the Activity Management Service can determine whether the currently displayed content is the application interface or a splash screen.

[0174] The Security Service is used to determine whether an application is allowed to register with a sensor and whether it is allowed to access sensor data based on the sensor's permission status.

[0175] The Application Operations Service (AppOps Service) is a service used to manage application operation permissions and record operation information, as well as store the application's permission status for sensors.

[0176] The Sensor Service is used to manage and access various sensor data on the device, and provides an interface for applications to register and query sensor data.

[0177] The kernel layer is the layer between hardware and software. The kernel layer contains at least display drivers and sensor drivers.

[0178] The following text uses the splash screen interaction scenario of a video application as an example to describe the overall process of this application embodiment. Specifically, as follows... Figure 8 As shown:

[0179] S801. When the video application displays the splash screen, the video application sends a sensor registration request to the sensor service.

[0180] In splash screen interaction scenarios, video applications can acquire data collected by sensors, such as accelerometers and gyroscopes, to identify interactive operations and thus achieve splash screen response. Based on this, when the splash screen is displayed after the video application starts (e.g., the portion of splash screen 301 excluding the first pop-up 3011), the video application can send a registration request to the sensor service to obtain permission to access the corresponding sensor (also known as the target sensor), enabling it to subsequently read data collected by that sensor.

[0181] The registration request may include sensor identifiers, such as sensor name, sensor type, and sensor number, to indicate the sensor for which registration is requested.

[0182] Specifically, for each sensor, the video application can send a corresponding registration request to the sensor service. Alternatively, for a class of sensors, such as sensors that detect the motion and direction of a device (including accelerometers, gyroscopes, etc.), the video application can send a single registration request to the sensor service. This application does not impose specific limitations on this approach.

[0183] S802, The sensor service sends a first query request to the security service. The first query request is used to query whether the video application is allowed to register the sensor.

[0184] The first query request may include an application identifier and a sensor identifier. For details on the sensor identifier, please refer to the description in S801. The application identifier indicates the application that initiated the registration request. For example, the application identifier can be an application package name or a user identity document (uid).

[0185] For example, the first query request is canRegisterSensor(uid,type), which queries whether the application indicated by uid (indicating a video application) is allowed to register the sensor indicated by type.

[0186] In some embodiments, prior to S802, the sensor service can filter registration requests. Specifically, if the sensor requesting registration is on a control list, then S802 is executed. The control list includes the identifiers of the sensors to be controlled during registration. This allows the sensor service to query whether the video application is allowed to register the sensor for the one to be controlled, thereby enabling targeted control over sensor registration.

[0187] For example, the controlled sensors include sensors used to acquire the motion and orientation of the device, such as accelerometers and gyroscopes. Accordingly, the controlled list includes the identifiers of sensors such as accelerometers and gyroscopes that acquire the motion and orientation of the device.

[0188] For example, unregulated sensors include sensors used to measure user health data, such as blood pressure sensors and photoplethysmogram (PPG) sensors. Accordingly, the list of regulated sensors does not include the identification of blood pressure sensors, PPG sensors, and other sensors used to measure user health data.

[0189] Additionally, if the sensor requesting registration is not on the controlled list, the sensor service can execute the registration process, such as continuing to request registration from the underlying layer, without further querying whether the video application is allowed to register the sensor.

[0190] S803, the security service sends an acquisition request to the application operation service. The acquisition request is used to obtain the permission status of the video application for the sensor.

[0191] The permission status can include multiple states corresponding to different levels of precision. Precision refers to the magnitude of the interactive operation in the splash screen interaction scenario. For details, please refer to the previous introductions of "Precise Action" 3012 and "Fuzzy Action" 3013, etc., which will not be repeated here. A state corresponding to a certain level of precision indicates that the application can obtain sensor data after reaching the corresponding magnitude.

[0192] Taking multiple levels of precision, including a first amplitude and a second amplitude, as an example: the state corresponding to the first amplitude can include a "precise motion" state (denoted as allowed), indicating that the video application can acquire sensor data after reaching the first amplitude; the state corresponding to the second amplitude can include a "blurred motion" state (denoted as ignored), indicating that the video application can acquire sensor data after reaching the second amplitude.

[0193] In some embodiments, the permission status may further include: an "errored" status and a "foreground-based" status. "Foreground-based" can also be understood as "currently" or "foreground-based." Specifically, an "errored" permission status indicates that the video application cannot acquire sensor data. A "foreground-based" permission status indicates that the video application cannot acquire sensor data during the splash screen interaction scenario.

[0194] In other words, the permission status can be compared with the pop-up window in the splash screen mentioned above (such as...). Figure 3B The options displayed in the second pop-up window 3021 on the splash screen 302 shown correspond to those displayed in the permission status settings interface of the settings application (e.g., Figure 5A The first permission status setting interface 501 is shown below. For details on how to set the above permission status, please refer to the explanation in S806 below, which will not be elaborated on here.

[0195] In addition, before the sensor's permission status is set, the sensor's permission status is in the default state. That is, the default state indicates that the sensor's permission status has not yet been set.

[0196] After receiving a query request from the sensor service, the security service can further send a retrieval request to the application operations service (AppOps). The retrieval request can include the application identifier (such as uid) and the sensor identifier (such as type) from the query request, used to obtain the permission status of the application (such as the video application indicated by uid) to the indicated sensor (such as the sensor indicated by type).

[0197] S804. The application operation service sends the first acquisition result to the security service. The first acquisition result indicates the default state.

[0198] The application operation service can store the mapping relationship between applications, sensors, and sensor permission states. For example, the mapping relationship is shown in Table 1 below:

[0199] Table 1

[0200] First sensor Second sensor Video applications Default state Screen unlocking disabled Shopping Apps Forbidden status "Precision Action" Status Chat application Screen unlocking disabled Screen unlocking disabled Music App "Fuzzy Action" Status Default state

[0201] Table 1 above indicates that: the video application's permission status for the first sensor is in the default state, meaning the video application's permission status for the target sensor has not yet been set; and the video application's permission status for the second sensor is disabled when the screen is on. The shopping application's permission status for the first sensor is disabled...

[0202] After receiving a request from the security service, the application operation service can query the permission status corresponding to the application identifier and sensor identifier in the request from the stored mapping relationship, thereby obtaining the application's permission status for the sensor.

[0203] For example, the uid in the request indicates a video application, and the type indicates the first sensor. The application operation service can query Table 1 above to obtain the permission status as the default status.

[0204] After querying the permission status, the application operation service can send the first retrieval result to the security service. The first retrieval result indicates the default status.

[0205] Therefore, it should be noted that S803-S804 above describes a scenario where the security service sends an acquisition request to the application operation service, and then the application operation service sends the video application's permission status for the sensor to the security service. In other embodiments, the security service can monitor changes in the sensor's permission status, and when a change in the sensor's permission status is detected, the security service can obtain the updated permission status of the sensor.

[0206] S805. When the sensor's permission status is in the default state, the security service sends a request to the settings application to display a pop-up window.

[0207] The security service obtains the sensor's permissions as being in the default state, meaning that the app that queried the request (such as the video app indicated by the uid) has the default permission status for the indicated sensor (such as the sensor indicated by the type). This indicates that the user has not set the permission status for the video app to the indicated sensor, and the security service cannot determine whether to allow the video app to register the sensor.

[0208] The sensor's permission status is in the default state in the following situations: no pop-up window has been displayed on the splash screen; a pop-up window has been displayed on the splash screen, but no user selection operation has been received in the pop-up window; and no user selection operation has been received in the permission status settings interface.

[0209] At this point, the security service sends a request to the settings application to display a pop-up window. The request includes the application identifier (such as UID) and the pop-up window identifier. The request asks the settings application to display the pop-up window in the video application indicated by the application and to receive the user's selection of options in the pop-up window. This allows the security service to obtain the video application's permission status for the sensor. Only then can the security service determine whether to allow the video application to register the sensor based on the sensor's permission status.

[0210] The pop-up identifier is used to indicate the "device movement and direction" pop-up, such as the first pop-up 3011, the second pop-up 3021, and the third pop-up 3031 mentioned above. In a specific implementation, the pop-up identifier can be the aforementioned sensor identifier (type).

[0211] S806: Set up an application display pop-up window and receive the user's selection of options in the pop-up window. Determine the video application's permission status for the sensor based on the selected target option.

[0212] Upon receiving a display request, the settings application can display a pop-up window based on the request. S801 displays the portion of the splash screen 301 excluding the first pop-up window 3011. After S801-S806, the first pop-up window 3011 can be further displayed on the splash screen 301. Specifically, the settings application can display a pop-up window on the splash screen of the application indicated by the application identifier in the display request, and the displayed pop-up window type is the "Device Motion and Direction" pop-up window indicated by the pop-up window identifier in the display request.

[0213] In some other embodiments, the steps from sending the registration request in S801 to S805 can be executed before the splash screen is displayed. Then, while the video application is displaying the splash screen, S806 can be executed to synchronously display the pop-up window on the splash screen (see splash screen 301).

[0214] After the application receives the user's selection of options in the pop-up window, it can determine the application's permission status for the sensor corresponding to the first target option based on the correspondence between the options in the pop-up window and the video application's permission status for the sensor.

[0215] For example, the correspondence between the options in the pop-up window and the application's permission status for the sensor is shown in Table 2 below:

[0216] Table 2

[0217]

[0218] For example, if the application receives the user's first target selection as "Precise Action", the application can query Table 2 above to obtain the video application's permission status for the sensor as "Precise Action".

[0219] For example, if the application is configured to select the first target option as the "disable" option when it receives the user's selection, the application can query Table 2 above to obtain the permission status of the video application for the sensor, which is "disabled".

[0220] In some embodiments, the setting application may receive a request to display a notification message. The setting application displays the notification message based on the request, and the notification message may include one or more options corresponding to the sensor's permission status. Simultaneously, the setting application may obtain a first target option selected by the user in the notification message and determine the video application's permission status for the sensor based on the first target option.

[0221] The settings application may include a pop-up module, and the pop-up module in the settings application may execute the above S806.

[0222] S807, Set the permission status of the application to the sensor when sending video to the application operation service.

[0223] After setting up the application to obtain the permission status of the video application for the sensor, the application sets up the application to send the permission status of the application for the sensor to the video application operation service.

[0224] S808, Application Operation Service stores the permission status of video applications for sensors.

[0225] The application operation service can store the correspondence between applications, sensors, and the permission status of sensors, as shown in Table 1 above. After receiving the permission status of the video application sent by the setting application for the sensor, the application operation service stores the permission status of the application for the sensor and updates the permission status of the application for the sensor indicated by the application identifier in Table 1.

[0226] For example, when the sensor type indicates that the sensor is the first sensor, and the setting application receives the user's selected first target option as the "precise action" option (i.e., the video application's permission status for the sensor is "precise action"), then the video application's permission status for the first sensor is updated. The correspondence between the updated application, sensor, and sensor's permission status is shown in Table 3 below.

[0227] Table 3

[0228] First sensor Second sensor Video applications "Precision Action" Status Screen unlocking disabled Shopping Apps Forbidden status "Precision Action" Status Chat application Screen unlocking disabled Screen unlocking disabled Music App "Fuzzy Action" Status Default state

[0229] In Table 3 above, the permission status of the video application for the first sensor is updated from the default status to the "Precise Action" status.

[0230] S809, The application operation service sends the second acquisition result to the security service.

[0231] The second acquisition result indicates the video application's permission status for the sensor (excluding the default status). Specifically, the second acquisition result corresponds to the prohibited status, the prohibited status on screen startup, the "precise motion" status, and the fuzzy motion status. The security service can determine whether to allow the video application to register with the sensor based on the sensor's permission status.

[0232] S810. When the second acquisition result indicates a prohibited state, the security service sends a first query result to the sensor service, and the first query result indicates that the registration failed.

[0233] When the second acquisition result indicates a prohibited state, i.e., the sensor's permission state is prohibited, the security service sends a first query result to the sensor service. The first query result includes the application identifier (e.g., uid), the sensor identifier (e.g., type), the prohibited state (also known as the fourth state information), and a judgment result on whether sensor registration is allowed. When the sensor's permission state is prohibited, the judgment result on whether sensor registration is allowed in the first query result is "no," that is, the video application indicated by the application identifier is prohibited from registering the sensor indicated by the sensor identifier.

[0234] S811, The sensor service sends a registration failure message to the video application.

[0235] After receiving the first query result, the sensor service sends a registration failure message to the application based on the judgment result of whether sensor registration is allowed in the first query result. When the sensor's permission status is prohibited and the judgment result of whether sensor registration is allowed is "no", the sensor service sends a registration failure message to the video application indicated by the application identifier.

[0236] Registration failure indicates that the video application indicated by the application identifier is prohibited from registering the sensor indicated by the sensor identifier. In this case, in the video application's splash screen interaction scenario, the video application cannot obtain sensor data, cannot recognize interactive operations (such as shaking the phone), and cannot achieve splash screen response (such as jumping to the interface corresponding to interactive content 1021).

[0237] The sensor's permission status is disabled, corresponding to the "Disabled" permission status 3025 in the splash screen 302. In the disabled state, the video application will not obtain sensor data or respond to user interactions, such as shaking the phone, on the splash screen or after entering the video application interface (excluding the splash screen) (e.g., the first application interface 104). For details, please refer to the previous explanation regarding "Disabled" 3025; it will not be repeated here.

[0238] S812. When the second acquisition result indicates the "precise action" status, the security service sends the second query result to the sensor service, and the second query result indicates successful registration.

[0239] When the second acquisition result indicates a "Precise Action" status, meaning the sensor's permission status is "Precise Action," the security service sends a second query result to the sensor service. This second query result indicates successful registration. The second query result includes the application identifier (e.g., UID), the sensor identifier (e.g., type), the "Precise Action" status (also known as the first status information), and a judgment result indicating whether sensor registration is allowed. If the judgment result for allowing sensor registration is "Yes," then the video application indicated by the application identifier is allowed to register the sensor indicated by the sensor identifier.

[0240] The sensor's permission status is "Precise Action," which corresponds to the "Precise Action" permission status 3012 in the splash screen 302. In the "Precise Action" status, it indicates that the video application can register the sensor indicated by the sensor identifier and send sensor data to the video application. This allows it to respond to the user's first interactive action (such as shaking the phone) and jump to the interface corresponding to interactive content 1021. For details, please refer to the previous explanation of "Precise Action" 3012; it will not be repeated here.

[0241] S813, The sensor service sends a registration success message to the video application.

[0242] After receiving the second query result, the sensor service sends a registration success message to the video application based on the judgment result in the second query result regarding whether sensor registration is allowed. When the sensor's permission status is "Precise Action" and the judgment result regarding whether sensor registration is allowed is "Yes", the sensor service sends a registration success message to the video application indicated by the application identifier.

[0243] Successful registration signifies that the video application, as indicated by the application identifier, is permitted to register the sensor, as indicated by the sensor identifier. In the splash screen interaction scenario, the video application can then acquire data collected by the sensors to identify interactive actions, thereby enabling the splash screen response. Based on this, when the video application launches and displays the splash screen, it can send a registration request to the sensor service, requesting permission to access the corresponding sensors, allowing it to subsequently read the data collected by those sensors.

[0244] S814, Sensor Service acquires sensor data.

[0245] When the sensor permission status is "precise action", the sensor service accesses the sensor indicated by the sensor identifier (such as an accelerometer, gyroscope, etc.) to obtain sensor data, such as the motion data corresponding to the first amplitude interactive operation.

[0246] Specifically, the sensor service can request to read the sensor data from the sensor driver, and the sensor driver will return the sensor data to the sensor service based on the request.

[0247] S815, Sensor Service sends sensor data to video applications.

[0248] The "Precise Motion" state corresponds to the first amplitude of the interaction operation, where the amplitude value is greater than or equal to zero and less than the second amplitude value. In the "Precise Motion" state, it is possible to respond to interaction operations with higher precision, that is, to respond to interaction operations with smaller amplitude (such as shaking the phone).

[0249] When the video application's permission status for the sensor is set to "Precise Action," it is always allowed to obtain sensor data corresponding to the sensor identifier during the splash screen interaction scenario. After the sensor service accesses the sensor and obtains the sensor data, it sends the sensor data to the video application. This allows the video application to recognize interactive operations (such as shaking the phone) based on the obtained sensor data (such as accelerometer data and gyroscope data) during the splash screen interaction scenario, thereby enabling the splash screen response.

[0250] S816, video applications respond to interactive operations based on the acquired sensor data.

[0251] After acquiring sensor data, the video application detects whether there is any interactive operation based on the acquired sensor data. If an interactive operation of the first magnitude is found, the application responds to the user's interaction with the content by redirecting the user to a specific page, such as... Figure 1A The interactive content interface 103 corresponds to the interactive content 1021. Responding to interactive operations can include navigating to the corresponding interface, adding the interactive content to the shopping cart, sharing the interactive content with friends, etc. For details, please refer to the previous explanation of the splash screen interaction scenario; it will not be repeated here. Furthermore, when the video application interface (excluding the splash screen) is subsequently displayed (such as the first application interface 104), it can also respond to user actions and trigger the execution of functions within the application.

[0252] S817. When the second acquisition result indicates that the screen is in a prohibited state when it is turned on, the security service sends a third query result to the sensor service. The third query result indicates that the registration is successful.

[0253] When the second result indicates a screen-on-demand state, meaning the sensor's permission status is screen-on-demand, the security service sends a third query result to the sensor service. Similarly, the third query result includes the application identifier (e.g., UID), the sensor identifier (e.g., type), the screen-on-demand state (also known as third state information), and a judgment result regarding whether sensor registration is allowed. Specifically, if the judgment result for whether sensor registration is allowed is "yes," then the video application indicated by the application identifier is allowed to register the sensor indicated by the sensor identifier.

[0254] The sensor's permission status is "Disabled on Startup," corresponding to the "Disabled on Startup" permission status 3024 in the startup page 302. In the "Disabled on Startup" state, the video application can register the sensor indicated by the sensor identifier. When the video application interface (excluding the startup page) is displayed, the application can send sensor data to the video application, thereby triggering the execution of functions within the application. However, in startup interaction scenarios, it will not respond to interactive operations, such as not navigating to the interface corresponding to interactive content 1021. For details, please refer to the previous explanation regarding "Disabled on Startup" 3024; it will not be repeated here.

[0255] S818, the sensor service sends a registration success message to the video application.

[0256] After receiving the third query result from the security service, the sensor service sends a registration success message to the video application.

[0257] S819, The sensor service sends a second query request to the security service. The second query request is used to query whether the transmission of sensor data is permitted.

[0258] When the sensor's permission status is "Deny on screen," it indicates that the security service needs to further determine whether the currently displayed interface of the video application is the application interface or the splash screen. If the currently displayed interface is the splash screen, it means that sensor data can be sent to the video application; if the currently displayed interface is the application interface, sensor data will not be sent. Based on this, the sensor service sends a second query request (also called a second request) to the security service. The second query request is used to query whether sending sensor data is allowed. The second query request may include the application identifier (e.g., uid) and the sensor identifier (e.g., type).

[0259] For example, a query request could be canOnSensorChanged(uid,type), which queries whether the application indicated by uid is allowed to obtain sensor data indicated by type.

[0260] S820, the security service obtains the lifecycle status of the video application from the activity management service.

[0261] The Activity Management Service (AMS) can obtain the lifecycle state of the video application, and based on this lifecycle state, it can determine whether the currently displayed screen is a splash screen or the video application interface. The security service can periodically retrieve the video application's lifecycle state from the Activity Management Service, for example, every 3 to 5 seconds. Alternatively, the security service can continuously retrieve the video application's lifecycle state from the Activity Management Service.

[0262] Specifically, security services can use Activity Observers to monitor changes in the lifecycle of video applications. Based on the lifecycle state of the video application, they can then determine whether to display the splash screen or the main video application interface.

[0263] In some embodiments, the security service sends a request to the activity management service to obtain the lifecycle state of the video application. The activity management service returns the lifecycle state of the video application to the security service based on the request. The security service can then determine whether the currently displayed screen is a splash screen or the video application interface based on the lifecycle state of the video application.

[0264] S821. When the current display is a video application interface, the security service sends a fourth query result to the sensor service. The fourth query result indicates that the sending of sensor data is permitted.

[0265] When the currently displayed interface is a video application (such as the first application interface 104), it indicates that sensor data can be sent to the video application, and the application's functions can be triggered in response to user operations. At this time, the security service sends the fourth query result to the sensor service. The result for determining whether to allow obtaining sensor data is "yes," meaning that the video application indicated by the application identifier is allowed to obtain the sensor data indicated by the sensor identifier.

[0266] In other embodiments, when the current displayed screen is a splash screen, it indicates that sending sensor data is not allowed, and responding to user interactions (such as shaking the phone) is not permitted. In this case, the security service may send a query result indicating that sending sensor data is not allowed to the sensor service, or the security service may not send a query result indicating that sending sensor data is allowed to the sensor service. In this situation, the sensor service will not send sensor data to the video application. Therefore, in the splash screen interaction scenario, the video application will not obtain sensor data, cannot recognize the interaction based on the sensor data (such as shaking the phone), and will not implement a splash screen response (such as redirecting to the interface corresponding to the interactive content).

[0267] S822, Sensor Service acquires sensor data.

[0268] When the sensor permission status is "disabled when the screen is on" and the result of the judgment on whether to allow the acquisition of sensor data is "yes", the sensor service accesses the sensor indicated by the sensor identifier (such as accelerometer, gyroscope, etc.) to acquire sensor data (also known as fourth motion data).

[0269] Specifically, the sensor service can request to read the sensor data from the sensor driver, and the sensor driver will return the sensor data to the sensor service based on the request.

[0270] S823, Sensor Service sends sensor data to video applications.

[0271] When the sensor's permission status is "disabled when the screen is on," the sensor service accesses the sensor driver to obtain sensor data and then sends the sensor data to the video application. This allows the video application to trigger and run in-app functions (such as shake-to-provide feedback) based on the obtained sensor data (such as accelerometer data and gyroscope data) when the video application interface is displayed.

[0272] S824, the video application responds to interactive operations based on the acquired sensor data.

[0273] When displaying the video application interface (excluding the splash screen), such as the first application interface 104, after receiving sensor data, the video application can trigger the execution of functions within the application based on the acquired sensor data, as shown in the second application interface 401. However, when displaying the splash screen, sensor data is not sent to the video application, nor are interactive operations responded to; for example, the user will not be redirected to the interface corresponding to interactive content 1021.

[0274] S825. When the second acquisition result indicates a "fuzzy action" state, the security service sends a fifth query result to the sensor service, and the fifth query result indicates successful registration.

[0275] When the second query result indicates a "fuzzy action" state, meaning the sensor's permission status is in the "fuzzy action" state, the security service sends a fifth query result to the sensor service. The fifth query result indicates successful registration. The fifth query result includes the application identifier (e.g., UID), the sensor identifier (e.g., type), the "fuzzy action" state (also known as the second state information), and the judgment result regarding whether sensor registration is permitted.

[0276] In the fifth query result, the judgment result for whether to allow sensor registration is "yes", that is, the video application indicated by the application identifier is allowed to register the sensor indicated by the sensor identifier.

[0277] The sensor's permission status is "fuzzy action," which corresponds to the permission status of "fuzzy action" 3013 in the splash screen 302. In the "fuzzy action" state, it indicates that the video application can register the sensor indicated by the sensor identifier. When the sensor data meets the second condition (see the description of the second condition below), it can send sensor data to the video application, thereby responding to the user's second-amplitude interactive operation (such as shaking the phone) and jumping to the interface corresponding to interactive content 1021. When the sensor data does not meet the second condition, it will not send sensor data to the video application and will not respond to the user's interactive operation. For details, please refer to the previous explanation of "fuzzy action" 3013; it will not be repeated here.

[0278] S826, The sensor service sends a registration success message to the video application.

[0279] After receiving the fifth query result from the security service, the sensor service sends a registration success message to the video application.

[0280] S827, Sensor Service Acquires Sensor Data

[0281] The sensor permission status is "fuzzy action," indicating that the security service needs to further determine whether the sensor data meets the second condition (see the introduction to the second condition below). Based on this, the sensor service accesses the sensor indicated by the sensor identifier to obtain sensor data (such as accelerometer, gyroscope, etc.). Specifically, the sensor service can request to read the sensor from the sensor driver, and the sensor driver returns the sensor data to the sensor service based on the request.

[0282] S828, Sensor Service sends sensor data to Security Service.

[0283] After receiving sensor data, the sensor service sends the sensor data to the security service, enabling the security service to judge the sensor data. When the sensor data meets the second condition, the security service sends the sensor data to the video application, thereby responding to interactive operations that reach the target amplitude and achieving the effect of controlling the accuracy of the phone's response to interactive operations.

[0284] S829. The sensor service sends a third query request to the security service. The third query request is used to query whether the video application is allowed to obtain sensor data.

[0285] When the sensor's permission status is "fuzzy action," it indicates that the security service needs to further determine whether the sensor data meets the second condition (see the description of the second condition below). Based on this, while sending sensor data to the security service, the sensor service also sends a third query request (also known as the first request) to the security service. The third query request is used to query whether the video application is allowed to obtain the sensor data. The third query request may include the application identifier (such as uid) and the sensor identifier (such as type).

[0286] For example, the third query request can be canOnSensorChanged(uid,type), which queries whether the application indicated by uid is allowed to obtain the sensor data indicated by type.

[0287] S830. When the sensor data meets the second condition, the security service sends a sixth query result to the sensor service, and the sixth query result indicates that the sensor data can be sent.

[0288] When the sensor data meets the second condition, it indicates that the amplitude of the interactive operation has reached the target amplitude. For example, after the user performs an interactive operation with the second amplitude, the sensor collects the corresponding second motion data and sends it to the security service via the sensor service. The security service can then detect that the second condition has been met. In this case, the security service can send a sixth query result to the sensor service to notify the sensor service to send sensor data to the video application.

[0289] In the sixth query result, the judgment result for whether to allow the acquisition of sensor data is "yes", that is, the video application indicated by the application identifier is allowed to acquire the sensor data indicated by the sensor identifier.

[0290] For example, accelerometers, gyroscopes, gravity sensors, and linear accelerometers can acquire the acceleration value of a mobile phone. Magnetometers, orientation sensors, and rotation vector sensors can acquire the orientation and rotation angle of the mobile phone.

[0291] Prior to S830, the security service could detect whether sensor data met a second condition, which included, but was not limited to, at least one of the following:

[0292] a. The acceleration is not less than X. For example, X ≥ 12 m / s². 2 For example, X = 15 m / s 2 .

[0293] b. The rotation angle is not less than 30°, for example, Y ≥ 30°, such as Y = 35°.

[0294] c. The operation time shall not be less than Z seconds. For example, Z ≥ 2 seconds, such as Z = 3 seconds.

[0295] For example, satisfying "a" indicates that the interaction has reached the second amplitude, allowing a jump to the interface corresponding to interaction content 1021. To obtain the phone's acceleration value, the sensor service can request sensor data from an accelerometer, gravity sensor, and linear acceleration sensor. There may be one or more accelerometers, gravity sensors, and linear acceleration sensors. The acceleration calculated from the sensor data of one of these sensors must be at least 15 m / s². 2 Then, condition "a" is satisfied. This allows sensor data to be sent to the video application, which can then redirect to the interface corresponding to interactive content 1021. For example, when the average acceleration calculated from the sensor data of all sensors is not less than 15 m / s²... 2 If , then a is satisfied.

[0296] In one specific implementation, both "a" and "b" must be satisfied simultaneously to indicate that the interaction has reached the second level, satisfying the requirements of the "fuzzy action" state. At this point, the security service sends a sixth query result to the sensor service, indicating that the transmission of sensor data is permitted.

[0297] In some embodiments, when the sensor data meets the second condition, the security service sends a query result to the sensor service. The result of the determination of whether to allow access to the sensor data is "No," meaning that the video application indicated by the application identifier is not allowed to access the sensor data indicated by the sensor identifier.

[0298] like Figure 9 As shown, when the sensor's permission status is "fuzzy action," the security service can judge the sensor data based on the second condition, filtering out sensor data that does not meet the second condition (i.e., invalid data in the figure), and sending valid data that meets the second condition to the video application. Data with an acceleration calculated from the sensor data that is less than 15 m / s², or a rotation angle calculated from the sensor data that is not less than 30°, is filtered out. In the "fuzzy action" state, the phone can only switch when it detects a relatively large shaking operation (such as the second amplitude), which can meet the user's need to avoid triggering a switch with slight shaking of the phone.

[0299] In some specific implementations, the sensor data used to determine whether the second condition is met may be different from the sensor data sent by the sensor service to the video application after the second condition is met. Because the security service determines whether the second condition is met quickly (at the millisecond level), after determining that the second condition is met, the sensor service sends the latest sensor data (also known as third motion data) to the application, enabling the video application to respond to interactive operations based on the latest sensor data.

[0300] Conversely to S830 described above, if the sensor data does not meet the second condition, it indicates that the amplitude of the interactive operation has not reached the target amplitude. For example, after the user performs an interactive operation with the first amplitude, the sensor collects the corresponding first motion data and sends it to the security service through the sensor service. The security service can then detect that the second condition is not met. In this case, the security service does not notify the sensor service to send sensor data, and the sensor service will not acquire the sensor data and send it to the application.

[0301] S831, Sensor Service sends sensor data to video applications.

[0302] When the sensor data meets the second condition, the sensor service receives the sixth query result and sends the sensor data to the video application. This allows the video application to recognize interactive operations (such as shaking the phone) based on the acquired sensor data (such as accelerometer data and gyroscope data) in the splash screen interaction scenario, and then realize the splash screen response (such as jumping to the interface corresponding to interactive content 1021).

[0303] S832, the video application responds to interactive operations based on the acquired sensor data.

[0304] When the sensor data meets the second condition, it can be sent to the video application, thus responding to the user's second-amplitude interactive operation (such as shaking the phone) and redirecting to the interface corresponding to interactive content 1021. Conversely, if the sensor data does not meet the second condition, it will not be sent to the video application and will not respond to the user's interactive operation. The phone can respond to interactive operations of varying amplitudes, thereby allowing control over the accuracy of the phone's response to interactive operations.

[0305] The "fuzzy action" state can affect the accuracy of responding to interactive operations in splash screen scenarios, but it still responds to the shake feedback function in video applications with high accuracy. In the "fuzzy action" state, the video application interface (non-splash screen page) can trigger the execution of functions within the application (such as shake feedback) based on the acquired sensor data (such as accelerometer data and gyroscope data).

[0306] The interactive control method of this solution allows users to select the required permission status, enabling the mobile phone to respond to interactive operations with the precision of the corresponding permission status based on the user's settings. The response results are more in line with the user's expectations, which can improve the user experience.

[0307] The process of this embodiment is explained using the example of a user modifying the permission status of a video application for a sensor in the permission status settings interface. Specifically, as shown... Figure 10 As shown:

[0308] S1001, Set the application to display the permission status setting interface, and receive the user's selection operation on the options in the permission status setting interface, and determine the permission status of the video application on the sensor based on the selection operation.

[0309] For instructions on how to access the permission settings interface from the Settings app, please refer to [link / reference]. Figure 1A , Figure 2A and Figure 2B For details, please refer to the above introduction on entering the permission status settings interface of the settings application; it will not be repeated here. The settings application displays the permission status settings interface, and the settings application can receive user selections of options in the permission status settings interface module.

[0310] After receiving the user's selection of options in the permission status settings interface, the setting application can determine the permission status of the application corresponding to the second target option for the sensor based on the correspondence between the options in the permission status settings interface and the permission status of the video application for the sensor.

[0311] For example, if the application receives the user's second target option as "Precise Action", the application can query Table 2 above to obtain the video application's permission status for the sensor as "Precise Action".

[0312] Users can modify the sensor's permission status in the permission status settings interface. The options in the permission status settings interface correspond one-to-one with the sensor's permission status, as shown in Table 2 above. Users can set the sensor's permission status in the permission status settings interface or in a pop-up window, thus controlling the screen navigation based on the user's selection.

[0313] If no user selection has been received in the pop-up window (i.e., the pop-up window has not been displayed on the application's splash screen, or the pop-up window has been displayed but the user has not selected an option), and no settings have been made in the permission status settings interface, then all options in the permission status settings interface will be unselected, as shown in the first permission status settings interface 501. Users can set the desired permission mode in the permission status settings interface. For example, if the user selects "fuzzy action" 5012, then in response to the user's selection of "fuzzy action" 5012, "fuzzy action" 5012 will be updated to a selected state (as shown in the third permission status interface 503).

[0314] If the app has received user selections in the pop-up window, but the user wants to modify the selected permission status, they can access the permission status settings interface through the settings app and modify the permission status there. For example, the fuzzy action status can be changed to a precise action status. For details, please refer to the introduction on modifying the permission status in the permission status settings interface (from the third permission status interface 503 to the fourth permission status interface 504), which will not be repeated here.

[0315] The settings application may include a permission status settings interface module, and the above S1001 can be executed by the permission status settings interface module in the settings application.

[0316] S1002. Set the permission status of the application to the sensor when sending video to the application operation service.

[0317] After the application obtains the permission status of the video application for the sensor, it sends the permission status of the video application for the sensor to the application operation service so that the application operation service can update the permission status of the video application for the sensor.

[0318] S1003, Application operation service updates the sensor's permission status.

[0319] The application operation service stores the correspondence between applications, sensors, and sensor permission statuses, as shown in Table 1 above. After receiving the permission status of the video application for the sensor sent by the setting application, the application operation service stores the permission status of the video application for the sensor and updates the permission status of the video application for the sensor indicated by the application identifier in Table 1.

[0320] After the application operation service updates the sensor's permission status, when the video application displays the splash screen again, the above steps S801-S803 can be executed to query the application operation service for the video application's permission status for the sensor.

[0321] S1004. Send the updated video application's permission status for the sensor.

[0322] The application operation service can send the updated sensor permission status from S1003 above to the security service.

[0323] Subsequently, based on the updated sensor permission status, the video application, sensor service, security service, and activity management service can execute corresponding processes. For example, if the updated sensor permission status is "prohibited," processes S810 to S811 can be executed. Another example is if the updated sensor permission status is "precise action," processes S812 to S816 can be executed. Yet another example is if the updated sensor permission status is "prohibited when the screen is on," processes S817 to S824 can be executed. And yet another example is if the updated sensor permission status is "fuzzy action," processes S825 to S832 can be executed.

[0324] This application also provides an electronic device, which may include a memory and one or more processors (such as a CPU, GPU, NPU, etc.). The memory and processor are coupled. The memory is used to store computer program code, which includes computer instructions. When the processor executes the computer instructions, the electronic device can perform various functions or steps performed by the device in the above method embodiments.

[0325] This application also provides a chip system including at least one processor and at least one interface circuit. The processor and the interface circuit are interconnected via lines. For example, the interface circuit can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit can be used to send signals to other devices (e.g., the processor). Exemplarily, the interface circuit can read instructions stored in the memory and send the instructions to the processor. When the instructions are executed by the processor, the electronic device can perform the steps in the above embodiments. Of course, the chip system may also include other discrete devices, and this application does not specifically limit this.

[0326] This embodiment also provides a computer storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the aforementioned method steps to implement the image processing method described above.

[0327] This embodiment also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement the image processing method described above.

[0328] In addition, embodiments of this application also provide an apparatus, which may specifically be a chip, component, or module. The apparatus may include a connected processor and a memory; wherein the memory is used to store computer execution instructions, and when the apparatus is running, the processor may execute the computer execution instructions stored in the memory to cause the chip to execute the image processing methods in the above-described method embodiments.

[0329] In this embodiment, the electronic device, computer storage medium, computer program product or chip are all used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding method provided above, and will not be repeated here.

[0330] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0331] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0332] The unit described as a separate component may or may not be physically separate. The component shown as a unit can be one physical unit or multiple physical units, that is, it can be located in one place or distributed in multiple different places. Some or all of the units can be selected to achieve the purpose of the solution in this embodiment according to actual needs.

[0333] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0334] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, essentially or in other words, the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0335] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit it. Although this application has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of this application without departing from the spirit and scope of the technical solutions of this application.

Claims

1. An interactive control method, characterized in that, Applied to an electronic device, the electronic device including a first application, the method includes: Launch the first application and display the first splash screen, which includes first interactive content, a first sub-option, and a second sub-option. Upon receiving a selection operation for the first sub-option, in response to a first motion control operation on the electronic device, a first interface is displayed, which is the interface corresponding to the first interactive content. Upon receiving a selection operation for the second sub-option, the first interface is displayed in response to a second motion control operation on the electronic device; the first interface is not displayed in response to the first motion control operation on the electronic device. Wherein, the first motion control operation causes the electronic device to move at a first amplitude, and the second motion control operation causes the electronic device to move at a second amplitude, wherein the first amplitude is smaller than the second amplitude.

2. The method according to claim 1, characterized in that, The launching of the first application and displaying the first splash screen includes: Launch the first application and display the second splash screen, which includes the first interactive content and the first option; In response to the selection of the first option, the first splash screen page is displayed.

3. The method according to claim 1 or 2, characterized in that, The first splash screen also includes a second option; After displaying the first splash screen page, the method further includes: The system receives a selection operation for the second option; wherein, upon receiving the selection operation for the second option, the first interface is not displayed in response to a motion control operation on the electronic device.

4. The method according to any one of claims 1-3, characterized in that, After receiving a selection operation for the first sub-option, the second sub-option, or the second option, the method further includes: The second interface is displayed. The second interface is the application interface of the first application. The second interface is not the splash screen. In response to the first motion control operation on the electronic device, the first function of the first application is executed.

5. The method according to any one of claims 1-4, characterized in that, The first splash screen also includes a third option; After displaying the first splash screen page, the method further includes: The system receives a selection operation for the third option; wherein, upon receiving the selection operation for the third option, the first interface is not displayed in response to a motion control operation on the electronic device. The third interface is displayed, which is the application interface of the first application, and is not the splash screen page. In response to the first motion control operation on the electronic device, the first function of the first application is executed.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: Launch the first application and display a third splash screen, which includes the second interactive content; Wherein, the triggering operation of the second interactive content is not a motion control operation, and the third splash screen interactive page does not include the first sub-option and the second sub-option.

7. The method according to any one of claims 1-6, characterized in that, After receiving a selection operation for the first sub-option, or after receiving a selection operation for the second sub-option, the method further includes: Launch the first application and display the fourth splash screen, which includes the first interactive content; The fourth splash screen does not include the first sub-option and the second sub-option.

8. The method according to any one of claims 1-7, characterized in that, The launching of the first application and displaying the first splash screen includes: Without receiving the first operation in the settings app, launch the first app and display the first splash screen; The first operation is used to trigger the electronic device to set the first application's permission to obtain device motion data.

9. The method according to claim 8, characterized in that, The method further includes: The fourth interface is displayed. The fourth interface is the permission status setting interface of the second application. The fourth interface includes the setting item for the second application's permission to obtain device motion data. The electronic device receives a second operation in the fourth interface, the second operation being used to trigger the electronic device to set the second application's permission to obtain device motion data; Launch the second application and display the fifth splash screen, which includes the third interactive content but does not include the first sub-option and the second sub-option.

10. The method according to any one of claims 1-9, characterized in that, After receiving a selection operation for the first sub-option, the method further includes: The fifth interface is displayed. The fifth interface is the permission status setting interface of the first application. The fifth interface includes the third sub-option and the fourth sub-option. The third sub-option corresponds to the first sub-option and is in the selected state. The fourth sub-option corresponds to the second sub-option. Receive the selection operation for the fourth sub-option in the fourth interface; Launch the first application and display the sixth splash screen, which includes the fourth interactive content; In response to a second motion control operation on the electronic device, the sixth interface is displayed; in response to a first motion control operation on the electronic device, the sixth interface is not displayed. The sixth interface is the interface corresponding to the fourth interactive content.

11. The method according to any one of claims 1-10, characterized in that, After launching the first application, the method further includes: When registering a target sensor, the permission status of the first application for the target sensor is queried. The target sensor is used to collect motion data of the electronic device. The display of the first splash screen page includes: If the permission status is found to be in the default state, the first splash screen page is displayed.

12. The method according to claim 11, characterized in that, The method further includes: If the permission status is not found to be the default status, a splash screen page that does not include the first sub-option and the second sub-option will be displayed.

13. The method according to any one of claims 1-12, characterized in that, The electronic device includes sensor services and security services; Upon receiving a selection operation for the first sub-option, in response to a first motion control operation on the electronic device, a first interface is displayed, including: Upon receiving a selection operation for the first sub-option, the security service sends first status information to the sensor service; In response to receiving the first status information, the sensor service sends first motion data to the first application, the first motion data including motion data collected by the target sensor corresponding to the first motion control operation; The first application uses the first motion data to display on the first interface.

14. The method according to any one of claims 1-12, characterized in that, The electronic device also includes sensor services and security services; Upon receiving a selection operation for the second sub-option, in response to a second motion control operation on the electronic device, a first interface is displayed, including: Upon receiving a selection operation for the second sub-option, the security service sends second status information to the sensor service; In response to receiving the second status information, the sensor service sends a first request to the security service, the first request being used to query whether to send motion data to the first application; In response to a second motion control operation on the electronic device, the sensor service sends the second motion data acquired by the target sensor to the security service; The security service detects whether the second amplitude corresponding to the second motion data reaches the target amplitude based on the first request. After detecting that the second amplitude has reached the target amplitude, the security service sends a message to the sensor service allowing the transmission of motion data. The sensor service sends the third motion data collected by the target sensor to the first application; The first application displays the first interface based on the third motion data.

15. The method according to claim 14, characterized in that, The step of not displaying the first interface in response to the first motion control operation on the electronic device includes: In response to a first motion control operation on the electronic device, the sensor service sends the first motion data acquired by the target sensor to the security service. The security service detects whether the first amplitude corresponding to the first motion data reaches the target amplitude based on the first request. After detecting that the first amplitude has not reached the target amplitude, the sensor service does not send a message to the sensor service allowing the transmission of motion data, so that the sensor service does not send motion data to the first application, and the first application does not display the first interface.

16. The method according to any one of claims 3-12, characterized in that, The electronic device also includes sensor services and security services; Upon receiving a selection operation for the second option, in response to a motion control operation on the electronic device, the first interface is not displayed, including: Upon receiving a selection operation for the second option, the security service sends third status information to the sensor service; In response to receiving the third status information, the sensor service sends a second request to the security service, the second request being used to query whether to send motion data to the first application; The security service detects whether the first application is displaying a splash screen page based on the second request; After detecting that the first application is displaying a splash screen, the sensor service does not send a message to the sensor service allowing the sending of motion data. As a result, the sensor service does not send motion data to the first application in response to the motion control operation, and the first application does not display the first interface.

17. The method according to claim 16, characterized in that, The security service detects whether the first application is displaying a splash screen based on the second request, including: The security service periodically checks whether the first application is displaying a splash screen page based on the second request; After detecting that the first application is not displaying the splash screen page, a message allowing the sending of motion data is sent back to the sensor service; The sensor service sends the fourth motion data collected by the target sensor to the first application; The first application runs its first function based on the fourth motion data.

18. The method according to any one of claims 5-12, characterized in that, The electronic device also includes security services and sensor services; Upon receiving a selection operation for the third option, in response to a motion control operation on the electronic device, the first interface is not displayed, including: Upon receiving a selection operation for the third option, the security service sends a fourth status information to the sensor service; In response to receiving the fourth state information, the sensor service does not send motion data to the first application in response to the motion control operation, and the first application does not display the first interface.

19. An electronic device, characterized in that, include: A display panel, one or more processors, and one or more memories; the one or more processors are coupled to the display panel and the one or more memories; the one or more memories are used to store computer program code, the computer program code including computer instructions, which, when executed by the one or more processors, cause the electronic device to perform the method as described in any one of claims 1-18.

20. A computer-readable storage medium storing computer instructions thereon, characterized in that, When the computer instructions are executed on an electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1-18.

21. A computer program product comprising computer instructions, characterized in that, When the computer program product is run on an electronic device, it causes the electronic device to perform the method as described in any one of claims 1-18.

Images