Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. It should be noted that the embodiments and features of the embodiments of the present invention may be arbitrarily combined with each other without conflict.
A mobile terminal implementing various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in themselves. Thus, "module" and "component" may be used in a mixture.
The mobile terminal may be implemented in various forms. For example, the mobile terminal described in the present invention may include devices such as a mobile phone, a smart phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a navigation device, etc., and it will be understood by those skilled in the art that the configuration according to the embodiment of the present invention can be applied to a fixed type terminal in addition to elements particularly used for mobile purposes.
Fig. 1 is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present invention.
The mobile terminal 100 may include a wireless communication unit 110, an a/V (audio/video) input unit 120, a user input unit 130, a sensing unit 140, an output unit 150, a memory 160, an interface unit 170, a controller 180, and a power supply unit 190, etc. Fig. 1 illustrates a mobile terminal having various components, but it is to be understood that not all illustrated components are required to be implemented. More or fewer components may alternatively be implemented. Elements of the mobile terminal will be described in detail below.
The wireless communication unit 110 typically includes one or more components that allow radio communication between the mobile terminal 100 and a wireless communication system or network. For example, the wireless communication unit may include at least one of a mobile communication module 111, a wireless internet module 112, and a short-range wireless communication module 113.
The mobile communication module 111 transmits and/or receives radio signals to and/or from at least one of a base station (e.g., access point, node B, etc.), an external terminal, and a server. Such radio signals may include voice call signals, video call signals, or various types of data transmitted and/or received according to text and/or multimedia messages.
The wireless internet module 112 supports wireless internet access of the mobile terminal. The module may be internally or externally coupled to the terminal. The wireless internet access technology to which the module relates may include Wibro (wireless broadband), Wimax (worldwide interoperability for microwave access), HSDPA (high speed downlink packet access), and the like.
The short range wireless communication module 113 is a module for supporting short range communication. Some examples of short-range communication technologies include WLAN (Wireless LAN) (Wi-Fi), BluetoothTMRadio Frequency Identification (RFID), infrared data association (IrDA), Ultra Wideband (UWB), zigbeeTMAnd Near Field Communication (NFC), among others.
The a/V input unit 120 is used to receive an audio or video signal. The a/V input unit 120 may include a camera 121 and a microphone 122, and the camera 121 processes image data of still pictures or video obtained by an image capturing apparatus in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 151. The image frames processed by the cameras 121 may be stored in the memory 160 (or other storage medium) or transmitted via the wireless communication unit 110, and two or more cameras 121 may be provided according to the construction of the mobile terminal. The microphone 122 may receive sounds (audio data) via the microphone in a phone call mode, a recording mode, a voice recognition mode, or the like, and can process such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the mobile communication module 112 in case of a phone call mode. The microphone 122 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.
The user input unit 130 may generate key input data according to a command input by a user to control various operations of the mobile terminal. The user input unit 130 allows a user to input various types of information, and may include a keyboard, dome sheet, touch pad (e.g., a touch-sensitive member that detects changes in resistance, pressure, capacitance, and the like due to being touched), scroll wheel, joystick, and the like. In particular, when the touch pad is superimposed on the display unit 151 in the form of a layer, a touch screen may be formed.
The sensing unit 140 detects a current state of the mobile terminal 100 (e.g., an open or closed state of the mobile terminal 100), a position of the mobile terminal 100, presence or absence of contact (i.e., touch input) by a user with the mobile terminal 100, an orientation of the mobile terminal 100, acceleration or deceleration movement and direction of the mobile terminal 100, and the like, and generates a command or signal for controlling an operation of the mobile terminal 100. For example, when the mobile terminal 100 is implemented as a slide-type mobile phone, the sensing unit 140 may sense whether the slide-type phone is opened or closed. In addition, the sensing unit 140 can detect whether the power supply unit 190 supplies power or whether the interface unit 170 is coupled with an external device.
The interface unit 170 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The identification module may store various information for authenticating a user using the mobile terminal 100 and may include a User Identity Module (UIM), a Subscriber Identity Module (SIM), a Universal Subscriber Identity Module (USIM), and the like. In addition, a device having an identification module (hereinafter, referred to as an "identification device") may take the form of a smart card, and thus, the identification device may be connected with the mobile terminal 100 via a port or other connection means. The interface unit 170 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal and the external device.
In addition, when the mobile terminal 100 is connected with an external cradle, the interface unit 170 may serve as a path through which power is supplied from the cradle to the mobile terminal 100 or may serve as a path through which various command signals input from the cradle are transmitted to the mobile terminal. Various command signals or power input from the cradle may be used as signals for recognizing whether the mobile terminal is accurately mounted on the cradle. The output unit 150 is configured to provide output signals (e.g., audio signals, video signals, alarm signals, vibration signals, etc.) in a visual, audio, and/or tactile manner. The output unit 150 may include a display unit 151, an audio output module 152, and the like.
The display unit 151 may display information processed in the mobile terminal 100. For example, when the mobile terminal 100 is in a phone call mode, the display unit 151 may display a User Interface (UI) or a Graphical User Interface (GUI) related to a call or other communication (e.g., text messaging, multimedia file downloading, etc.). When the mobile terminal 100 is in a video call mode or an image capturing mode, the display unit 151 may display a captured image and/or a received image, a UI or GUI displaying a video or an image and related functions, and the like.
Meanwhile, when the display unit 151 and the touch pad are overlapped with each other in the form of a layer to form a touch screen, the display unit 151 may serve as an input device and an output device. The display unit 151 may include at least one of a Liquid Crystal Display (LCD), a thin film transistor LCD (TFT-LCD), an Organic Light Emitting Diode (OLED) display, a flexible display, a three-dimensional (3D) display, and the like. Some of these displays may be configured to be transparent to allow a user to view from the outside, which may be referred to as transparent displays, and a typical transparent display may be, for example, a TOLED (transparent organic light emitting diode) display or the like. Depending on the particular desired implementation, the mobile terminal 100 may include two or more display units (or other display devices), for example, the mobile terminal may include an external display unit (not shown) and an internal display unit (not shown). The touch screen may be used to detect a touch input pressure as well as a touch input position and a touch input area.
The audio output module 152 may convert audio data received by the wireless communication unit 110 or stored in the memory 160 into an audio signal and output as sound when the mobile terminal is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output module 152 may provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output module 152 may include a speaker, a buzzer, and the like.
The memory 160 may store a software program or the like for processing and controlling operations performed by the controller 180, for example, a software program for implementing the super shot implementing method of the present invention, or may temporarily store data (e.g., a phonebook, messages, still images, videos, etc.) that has been or will be output. Also, the memory 160 may store data regarding various ways of vibration and audio signals output when a touch is applied to the touch screen.
The memory 160 may include at least one type of storage medium including a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. Also, the mobile terminal 100 may cooperate with a network storage device that performs a storage function of the memory 160 through a network connection.
The controller 180 generally controls the overall operation of the mobile terminal. For example, the controller 180 performs control and processing related to voice calls, data communications, video calls, and the like. The controller 180 may perform a pattern recognition process to recognize a handwriting input or a picture drawing input performed on the touch screen as a character or an image.
The power supply unit 190 receives external power or internal power and provides appropriate power required to operate various elements and components under the control of the controller 180.
The various embodiments described herein may be implemented in a computer-readable medium using, for example, computer software, hardware, or any combination thereof. For a hardware implementation, the embodiments described herein may be implemented using at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a processor, a controller, a microcontroller, a microprocessor, an electronic unit designed to perform the functions described herein, and in some cases, such embodiments may be implemented in the controller 180. For a software implementation, the implementation such as a process or a function may be implemented with a separate software module that allows performing at least one function or operation. The software codes may be implemented by software applications (or programs) written in any suitable programming language, which may be stored in the memory 160 and executed by the controller 180.
Based on the above mobile terminal hardware structure, various embodiments of the mobile terminal of the present invention are provided.
Referring to fig. 2, in a first embodiment of the mobile terminal of the present invention, the mobile terminal includes:
a first adding module 10, configured to add a concrete implementation of a super screenshot function in a hardware abstraction layer, so as to abstract and encapsulate data collected by a fingerprint chip on a bottom layer;
the second adding module 20 is configured to add a callback function for calling back data acquired by the fingerprint chip in the JNI layer to provide an operation interface for the application framework layer;
a third adding module 30, configured to add an application programming interface for implementing the super screenshot function in the application framework layer, so as to be called by the application layer, and implement the super screenshot function.
In order to facilitate understanding of the solution of the present invention, the following first describes a super screenshot function of a mobile terminal with reference to the accompanying drawings.
The super screenshot described by the invention comprises three functions of screen recording, long screenshot and free screenshot.
As shown in fig. 3, for an illustration of a screen recording function, when the illustration "start" control is clicked, a screen recording operation is triggered, and at this time, the mobile terminal records the received screen operation and also records sound, and finally generates a video file with a set format, such as a video file with an mp4 format.
As shown in fig. 4, the free screenshot function is illustrated, and through the "free screenshot", the user can select and capture the desired content, and the experience is more convenient. In addition, the method supports circular screenshots, heart-shaped screenshots and the like, and is more differentiated and interesting.
As shown in fig. 5, the long screenshot function is illustrated, and the main purpose of the long screenshot is that the content of the single-page mobile terminal interface cannot meet the requirements of the user, and at this time, the long screenshot needs to be used to capture the whole content, so that the whole picture content can be easily captured across multiple screens, and the whole content can be shared after screenshot.
In actual production, different terminal manufacturers adopt the standard flow of Google on the implementation of basic functions of fingerprints (such as prenroll, enroll, authentication, etc.), and the software flow of the Google is shown in fig. 6.
The FingerprintManager module can be said to be a proxy module of the application layer. Every application needing to use the fingerprint realizes the relevant function by calling the interface of the FingerprintManager. It provides interfaces such as preEnroll, enroll, postEnroll, authentite, getAutothenatotorId and registers callback function downwards. The bottom layer module calls back the registration result and the authentication result to the FingerprintManager module.
The FingerprintService module manages the logic of the whole processes of registering, identifying, deleting fingerprints, checking authority and the like.
The fingerprinttd module initializes a fingerprintt module of the hardware abstraction layer, provides an interface for operating a Fingerprint chip for the FingerprintService module, and registers a message callback function and the like to the hardware abstraction layer.
Referring to fig. 7, a schematic diagram of a fingerprint data reporting process is shown, in which a firmware burned in a fingerprint chip is responsible for controlling a process of collecting fingerprint data; the Fingerprint driver is responsible for transmitting Fingerprint data and processing algorithm results and reporting corresponding events; and the upper layer realizes an algorithm and returns a processing result.
Referring to fig. 8, an exemplary diagram of a fingerprint chip module includes a glass cover plate, an annular fixing device, a fingerprint chip and a flexible circuit board.
Referring to fig. 9, a user touches the Fingerprint chip with a finger, and the Fingerprint chip reports corresponding data to the Fingerprint drive or the upper layer through an identified touch gesture (e.g., left-sliding) so as to implement a specific application (e.g., left-sliding to implement a return key function).
Based on the foregoing description, the main aspects of the present invention will be explained next.
The main scheme of the invention is that different fingerprint chips provide the same super screenshot realization interface for the super screenshot function.
Specifically, referring to fig. 10 in combination, firstly, a first adding module 10 adds a concrete implementation of a super screenshot function to a Fingerprint module of a hardware abstraction layer, so as to abstract and encapsulate the collected data of the Fingerprint chip at the bottom layer, and shield differences of different types of Fingerprint chips. The hardware abstraction layer is an interface layer located between the kernel of the operating system and the hardware circuit, and is intended to abstract the hardware. It hides the hardware interface details of specific platform, provides virtual hardware platform for operation system, makes it have hardware independence, and can be transplanted on several platforms. From the perspective of software and hardware testing, the software and hardware testing can be completed based on the hardware abstraction layer, so that the parallel execution of the software and hardware testing becomes possible.
Secondly, a second adding module 20 adds a callback function for calling back data collected by the fingerprint chip in a Fingerprintd module of a JNI (Java Native Interface) layer, so as to provide an Interface for operating the fingerprint chip for an application framework layer. The JNI layer plays a role of starting and stopping, the upper layer receives the application framework layer, and the lower layer calls the hardware abstraction layer to realize concrete implementation.
Finally, the third adding module 30 adds an application programming interface for implementing the super screenshot function to the FingerprintService module of the application framework layer, so as to be called by the application layer, thereby implementing the super screenshot function.
Therefore, the invention realizes the unification of the interfaces of the super screenshots of different types of fingerprint chips.
Furthermore, the specific code implementation for the aforementioned operations can be performed by those skilled in the art, and the present invention is not particularly limited.
According to the mobile terminal provided by the invention, the realization interface of the super screenshot function and the related callback function are added upwards layer by layer from the hardware abstraction layer, the application programming interface for realizing the super screenshot function is added on the application framework layer for the application layer to call, so that the unification of super screenshot realization interfaces of different types of fingerprint chips is completed, the workload of software programming is obviously reduced, and the purpose of reducing the realization difficulty of the super screenshot is achieved.
Based on the first embodiment, a second embodiment of the mobile terminal of the present invention is provided, in this embodiment, the second adding module 20 is further configured to, while adding a callback function of the callback fingerprint chip to collect data in the JNI layer, identify whether a JNI call source code for implementing a super screenshot function exists in the JNI layer; and deleting the JNI calling source code when the JNI calling source code exists in the JNI layer.
It should be noted that, compared with the first embodiment, the present embodiment adds redundancy elimination operation. Specifically, in this embodiment, the second adding module 20 adds a callback function of data collected by a callback fingerprint chip to a fingerpringtd module in the JNI layer, and also identifies whether a JNI calling source code for implementing a super screenshot function exists in the fingerpringtd module, and if so, deletes the JNI calling source code for implementing the super screenshot function, thereby avoiding a program running error.
Based on the first embodiment, a third embodiment of the mobile terminal of the present invention is provided, in this embodiment, the third adding module 30 is further configured to, while adding an application programming interface for implementing a super screenshot function to the application framework layer, identify whether an extension service for implementing the super screenshot function exists in the application framework layer; and the system is also used for deleting the extended service when the extended service exists in the application framework layer.
It should be noted that, compared with the first embodiment, the present embodiment adds redundancy elimination operation. Specifically, in this embodiment, the third adding module 30 is configured to, while adding a callback function for calling back data acquired by the fingerprint chip to the FingerprintService module in the application framework layer, identify whether an extended service for implementing the super screenshot function exists in the FingerprintManager module, and if so, delete the extended service for implementing the super screenshot function, thereby avoiding a program running error.
Further, a fourth embodiment of the mobile terminal of the present invention is provided based on any of the foregoing embodiments, and in this embodiment, the mobile terminal further includes a screenshot module, configured to invoke an application programming interface that implements a screenshot function based on a background-running screenshot super application, and switch the screenshot application to foreground running when a result of the invocation is a preset fingerprint long-touch event.
It should be noted that, compared with the foregoing embodiments, the present embodiment adds an operation of triggering the super screenshot function. Specifically, in this embodiment, the screenshot module calls an application programming interface for implementing the super screenshot function in real time based on the super screenshot application running in the background, and when a call result returned by the application programming interface is received, identifies whether the call result is a preset fingerprint long-touch event, so as to determine whether the user needs to trigger the super screenshot function. When the calling result is identified to be the preset fingerprint long touch event, the screenshot module switches the super screenshot application to the foreground for operation, as shown in fig. 3 to 5, the user can slide the super screenshot interface of the mobile terminal screen as required, and the super screenshot interface is switched randomly among the three functions of the super screenshot to complete screenshot.
In this embodiment, in order to improve the flexibility of fingerprint identification of the mobile terminal, the screenshot module is further configured to identify whether the mobile terminal is currently in a bright-screen and unlocked-screen state when the calling result is a preset fingerprint long-touch event; and the super screenshot application is switched to the foreground for running when the current screen is in a bright screen and unlocked state and the screen locking password is set.
TABLE 1
As shown in table 1, the present embodiment presets responses for different fingerprint events, including:
1. under the bright screen and the non-lock screen, a screen-locking password is set, but no registered fingerprint is detected (for example, a user registers a thumb fingerprint, but touches the fingerprint chip with an index finger), and then the user long-touching the fingerprint chip triggers the super screenshot function of the mobile terminal.
2. When the screen is bright and not locked, the user presses the screen, and the mobile terminal returns to the main interface;
3. under the condition of bright screen and non-locked screen, a user presses for a long time, and the mobile terminal is switched to a multitask interface;
4. and under the condition of bright screen and non-locked screen, the user double clicks, and the mobile terminal returns to the main interface.
It is understood that the above-mentioned fingerprint events such as touch once, long touch, press once, long press, and double-click can be set by those skilled in the art according to actual needs, for example, two seconds of continuously pressing the fingerprint chip is defined as a fingerprint long touch event.
Further, the present invention also provides a super screenshot implementation method, which is executed by the mobile terminal shown in fig. 2, and with reference to fig. 2 and fig. 11, corresponds to the first embodiment of the mobile terminal of the present invention, and in the first embodiment of the super screenshot implementation method of the present invention, the super screenshot implementation method includes:
step S10, adding concrete realization of super screenshot function in the hardware abstraction layer to abstract and package the collected data of the bottom fingerprint chip;
step S20, adding a callback function for calling back data collected by the fingerprint chip on the JNI layer to provide an operation interface for the application framework layer;
and step S30, adding an application programming interface for realizing the super screenshot function in the application framework layer so as to be called by the application layer to realize the super screenshot function.
Specifically, referring to fig. 10 in combination, firstly, a first adding module 10 adds a concrete implementation of a super screenshot function to a Fingerprint module of a hardware abstraction layer, so as to abstract and encapsulate the collected data of the Fingerprint chip at the bottom layer, and shield differences of different types of Fingerprint chips. The hardware abstraction layer is an interface layer located between the kernel of the operating system and the hardware circuit, and is intended to abstract the hardware. It hides the hardware interface details of specific platform, provides virtual hardware platform for operation system, makes it have hardware independence, and can be transplanted on several platforms. From the perspective of software and hardware testing, the software and hardware testing can be completed based on the hardware abstraction layer, so that the parallel execution of the software and hardware testing becomes possible.
Secondly, a second adding module 20 adds a callback function for calling back data collected by the fingerprint chip in a Fingerprintd module of a JNI (Java Native Interface) layer, so as to provide an Interface for operating the fingerprint chip for an application framework layer. The JNI layer plays a role of starting and stopping, the upper layer receives the application framework layer, and the lower layer calls the hardware abstraction layer to realize concrete implementation.
Finally, the third adding module 30 adds an application programming interface for implementing the super screenshot function to the FingerprintService module of the application framework layer, so as to be called by the application layer, thereby implementing the super screenshot function.
Therefore, the invention realizes the unification of the interfaces of the super screenshots of different types of fingerprint chips.
Furthermore, the specific code implementation for the aforementioned operations can be performed by those skilled in the art, and the present invention is not particularly limited.
The super screenshot realization method provided by the invention is characterized in that a realization interface of a super screenshot function and a related callback function are added upwards layer by layer from a hardware abstraction layer, an application program programming interface for realizing the super screenshot function is added on an application framework layer for being called by the application layer, so that the unification of super screenshot realization interfaces of different types of fingerprint chips is completed, the workload of software programming is obviously reduced, and the purpose of reducing the realization difficulty of the super screenshot is achieved.
Based on the first embodiment, which corresponds to the second embodiment of the foregoing mobile terminal, a second embodiment of the super screenshot implementing method of the present invention is proposed, in this embodiment, while executing step S20, the following steps are also executed:
identifying whether a JNI calling source code for realizing a super screenshot function exists in a JNI layer;
and deleting the JNI calling source code when the JNI calling source code exists in the JNI layer.
It should be noted that, compared with the first embodiment, the present embodiment adds redundancy elimination operation. Specifically, in this embodiment, the second adding module 20 adds a callback function of data collected by a callback fingerprint chip to a fingerpringtd module in the JNI layer, and also identifies whether a JNI calling source code for implementing a super screenshot function exists in the fingerpringtd module, and if so, deletes the JNI calling source code for implementing the super screenshot function, thereby avoiding a program running error.
Based on the first embodiment and corresponding to the third embodiment of the foregoing mobile terminal, a third embodiment of the super screenshot implementing method of the present invention is proposed, in this embodiment, while executing step S30, the following steps are also executed:
identifying whether an application framework layer has an extended service for realizing a super screenshot function;
and when the application framework layer has the extended service, deleting the extended service.
It should be noted that, compared with the first embodiment, the present embodiment adds redundancy elimination operation. Specifically, in this embodiment, the third adding module 30 is configured to, while adding a callback function for calling back data acquired by the fingerprint chip to the FingerprintService module in the application framework layer, identify whether an extended service for implementing the super screenshot function exists in the FingerprintManager module, and if so, delete the extended service for implementing the super screenshot function, thereby avoiding a program running error.
Further, based on any one of the foregoing embodiments, corresponding to the foregoing fourth embodiment of the mobile terminal, a fourth embodiment of the super screenshot implementing method of the present invention is provided, in this embodiment, after step S30, the method further includes:
and calling an application programming interface for realizing the super screenshot function based on the super screenshot application running in the background, and switching the super screenshot application to the foreground to run when the calling result is a preset fingerprint long-touch event.
It should be noted that, compared with the foregoing embodiments, the present embodiment adds an operation of triggering the super screenshot function. Specifically, in this embodiment, the mobile terminal further includes a screenshot module, where the screenshot module calls an application programming interface for implementing a super screenshot function based on a super screenshot application running in the background in real time, and when a call result returned by the application programming interface is received, identifies whether the call result is a preset fingerprint long-touch event, so as to determine whether the user needs to trigger the super screenshot function. When the calling result is identified to be the preset fingerprint long touch event, the screenshot module switches the super screenshot application to the foreground for operation, as shown in fig. 3 to 5, the user can slide the super screenshot interface of the mobile terminal screen as required, and the super screenshot interface is switched randomly among the three functions of the super screenshot to complete screenshot.
In this embodiment, before the step of switching the super screenshot to foreground operation, the method further includes:
when the calling result is a preset fingerprint long-touch event, identifying whether the current screen is in a bright-screen and unlocked-screen state;
and when the current screen is in a bright screen and unlocked screen state and the screen locking password is set, switching to the step of executing switching of the super screenshot application to the foreground for operation.
In order to improve the flexibility of fingerprint identification of the mobile terminal, in this embodiment, the screenshot module is further configured to identify whether the current screen is in a bright-screen and unlocked-screen state when the calling result is a preset fingerprint long-touch event; and the super screenshot application is switched to the foreground for running when the current screen is in a bright screen and unlocked state and the screen locking password is set.
As shown in table 1, the present embodiment presets responses for different fingerprint events, including:
1. under the bright screen and the non-lock screen, a screen-locking password is set, but no registered fingerprint is detected (for example, a user registers a thumb fingerprint, but touches the fingerprint chip with an index finger), and then the user long-touching the fingerprint chip triggers the super screenshot function of the mobile terminal.
2. When the screen is bright and not locked, the user presses the screen, and the mobile terminal returns to the main interface;
3. under the condition of bright screen and non-locked screen, a user presses for a long time, and the mobile terminal is switched to a multitask interface;
4. and under the condition of bright screen and non-locked screen, the user double clicks, and the mobile terminal returns to the main interface.
It is understood that the above-mentioned fingerprint events such as touch once, long touch, press once, long press, and double-click can be set by those skilled in the art according to actual needs, for example, two seconds of continuously pressing the fingerprint chip is defined as a fingerprint long touch event.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the invention. However, it will be apparent to one skilled in the art that the specific details are not required in order to practice the invention. The foregoing descriptions of specific embodiments of the present invention have been presented for purposes of illustration and description. They are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching. The embodiments are shown and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents.