CN106991017B - Event processing method and device - Google Patents
Event processing method and device Download PDFInfo
- Publication number
- CN106991017B CN106991017B CN201710217345.6A CN201710217345A CN106991017B CN 106991017 B CN106991017 B CN 106991017B CN 201710217345 A CN201710217345 A CN 201710217345A CN 106991017 B CN106991017 B CN 106991017B
- Authority
- CN
- China
- Prior art keywords
- device driving
- jni
- specified service
- driving event
- layer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephonic Communication Services (AREA)
Abstract
The embodiment of the invention provides an event processing method and device. After the specified service is started up and initialized, a Java local interface JNI monitoring thread is created in a System service System _ Server process, and the JNI monitoring thread is used for monitoring a device driving event corresponding to the specified service; running a JNI monitoring thread on a local layer; the method comprises the steps of responding to a JNI monitoring thread to monitor a device driving event corresponding to a specified service, reporting the device driving event corresponding to the specified service to a Java layer by calling the corresponding JNI, utilizing an independent code to report a bottom layer event to the upper Java layer, concentrating and independently the code, and being beneficial to multiplexing management and maintenance.
Description
[ technical field ] A method for producing a semiconductor device
The present invention relates to the field of communications, and in particular, to an event processing method and apparatus.
[ background of the invention ]
At present, Android (Android) systems are widely adopted for mobile terminals such as smart phones and tablet computers. The android system of the mobile terminal comprises an equipment driver Layer, a Hardware Abstraction Layer (HAL) Layer, a Framework Layer and a Java application program on the uppermost Layer from bottom to top. The Framework layer comprises a Java Framework layer and a local (Native) Framework layer, wherein the local Framework layer is called a local layer for short.
When the device driver layer obtains a certain bottom layer event, the bottom layer event can be reported to the top layer Java application program through the hardware abstraction layer and the framework. When a project (namely, a Java application) related to the underlying event is implemented, the related codes of the hardware abstraction layer and the framework need to be transplanted into the project, and a large amount of interface codes of the hardware abstraction layer and the framework need to be changed in the transplanting process. Moreover, each item associated with the underlying event requires independent migration and modification of the associated code of the hardware abstraction layer and framework. This manner of event handling results in poor code reusability, maintainability and stability.
[ summary of the invention ]
In view of this, embodiments of the present invention provide an event processing method and apparatus, so as to solve the problem that the event processing manner in the prior art causes poor reusability, maintainability, and stability of codes.
In a first aspect, an embodiment of the present invention provides an event processing method, which is applied to an android terminal, and the method includes:
creating a Java local interface JNI monitoring thread in a System service System _ Server process, wherein the JNI monitoring thread is used for monitoring a device driving event corresponding to a specified service;
running the JNI monitoring thread on a local Native layer;
and responding to the monitoring of the device driving event corresponding to the specified service by the JNI monitoring thread, and reporting the device driving event corresponding to the specified service to a Java layer by calling the corresponding JNI.
As for the above aspect and any possible implementation manner, there is further provided an implementation manner, where in response to the monitoring of the device driving event corresponding to the specified service by the JNI monitoring thread, the reporting of the device driving event corresponding to the specified service to a Java layer by invoking a corresponding JNI includes:
responding to the JNI monitoring thread to monitor the device driving event corresponding to the specified service, and acquiring the monitored event identification of the device driving event corresponding to the specified service;
and reporting the event identifier of the device driving event corresponding to the specified service to a Java layer by calling a corresponding JNI.
In the above aspect and any possible implementation manner, there is further provided an implementation manner, where the specified service is a fingerprint service, and the device driving event corresponding to the specified service is a fingerprint device driving event.
The above-described aspects and any possible implementations further provide an implementation, and the method further includes:
collecting operation information through collection equipment corresponding to the specified service;
identifying the operation information to obtain a device driving event corresponding to the specified service;
and sending the device driving event to a local layer.
In a second aspect, an embodiment of the present invention provides an event processing apparatus, which is disposed in an android terminal, and the apparatus includes:
the System comprises a creating module, a judging module and a processing module, wherein the creating module is used for creating a Java local interface JNI monitoring thread in a System service System _ Server process, and the JNI monitoring thread is used for monitoring a device driving event corresponding to a specified service;
the running module is used for running the JNI monitoring thread on a local Native layer;
and the reporting module is used for responding to the monitoring of the device driving event corresponding to the specified service by the JNI monitoring thread, and reporting the device driving event corresponding to the specified service to a Java layer by calling the corresponding JNI.
As to the above aspect and any possible implementation manner, there is further provided an implementation manner, where the reporting module is configured to, when responding to the JNI monitoring thread to monitor the device driving event corresponding to the specified service and reporting the device driving event corresponding to the specified service to a Java layer by calling a corresponding JNI, specifically:
responding to the JNI monitoring thread to monitor the device driving event corresponding to the specified service, and acquiring the monitored event identification of the device driving event corresponding to the specified service;
and reporting the event identifier of the device driving event corresponding to the specified service to a Java layer by calling a corresponding JNI.
In the above aspect and any possible implementation manner, there is further provided an implementation manner, where the specified service is a fingerprint service, and the device driving event corresponding to the specified service is a fingerprint device driving event.
The above-described aspects and any possible implementations further provide an implementation, where the apparatus further includes:
the acquisition module is used for acquiring operation information through acquisition equipment corresponding to the specified service;
the identification module is used for identifying the operation information to obtain a device driving event corresponding to the specified service;
and the sending module is used for sending the device driving event to a local layer.
The embodiment of the invention has the following beneficial effects:
in the embodiment of the invention, the JNI monitoring thread created in the System _ Server process monitors the device driving event corresponding to the specified service, calls the corresponding Java local interface, reports the device driving event corresponding to the specified service to the Java layer, and reports the bottom layer event to the upper Java layer by using the independent codes, so that the codes are centralized and independent, the multiplexing management and maintenance are facilitated, and the codes in the independent set have the characteristics of high cohesion and low coupling, thereby improving the stability of the codes.
[ description of the drawings ]
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
Fig. 1 is a diagram illustrating a first process of an event processing method according to an embodiment of the present invention.
Fig. 2 is a diagram illustrating a second process of an event processing method according to an embodiment of the present invention.
Fig. 3 is a functional block diagram of an event processing apparatus according to an embodiment of the present invention.
[ detailed description ] embodiments
For better understanding of the technical solutions of the present invention, the following detailed descriptions of the embodiments of the present invention are provided with reference to the accompanying drawings.
It should be understood that the described embodiments are only some embodiments of the invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the examples of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be understood that the term "and/or" as used herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.
Example one
The embodiment of the invention provides an event processing method which can be applied to terminals such as mobile phones and tablet computers adopting android systems. The event processing method can be realized by a program, and the program can be installed on a mobile phone, a tablet computer and other terminals. Herein, a terminal adopting the android system is referred to as an android terminal.
Fig. 1 is a diagram illustrating a first process of an event processing method according to an embodiment of the present invention. As shown in fig. 1, in this embodiment, the event processing method is applied to an android terminal, and the method includes the following steps:
s101, a JNI (Java Native Interface, Java local Interface) monitoring thread is created in a System _ Server process, wherein the JNI monitoring thread is used for monitoring a device driving event corresponding to a specified service;
s102, running a JNI monitoring thread on a Native (local) layer;
and S103, responding to the monitoring of the device driving event corresponding to the specified service by the JNI monitoring thread, and reporting the device driving event corresponding to the specified service to the Java layer by calling the corresponding JNI.
Wherein the specified service is associated with its corresponding device driven event. Device-driven events are the underlying events in the android system, which are typically related to a specific action of a user. After the device driving event occurs, the corresponding specified service needs to be subsequently processed according to the device driving event.
For example. The fingerprint light touch event is also called as a fingerprint equipment driving event, and refers to a simulated key event realized by a fingerprint IC algorithm, when a finger touches the module, the fingerprint IC algorithm identifies the action of pressing down and lifting up the finger through operation, and then reports to the upper layer through driving, and the upper layer software carries out required processing according to the event.
The System _ Server process is a core service process of the android System, and many System-level services of the android System are threads of the System _ Server process.
In S101, a JNI monitoring thread is created in the System _ Server process, so that the framework layer of the android System can monitor the device driving event from the bottom layer (i.e., the device driving layer) in real time, and the framework layer can directly obtain the device driving event corresponding to the specified service without using the hardware abstraction layer.
In S102, after the JNI monitoring thread is run in the local layer, the JNI monitoring thread starts real-time monitoring on the device driving event corresponding to the specified service.
Wherein, the Java layer in S103 is a Java application layer at the uppermost layer of the android system. The Java native interface enables Java applications running on the Java virtual machine to call or be called by programs written in other languages (e.g., C, C + + or assembly language, etc.) that are specific to the native hardware and operating system. Communication between the Java framework layer and the native layer in the framework layer is enabled through a Java native interface in the android system, because the Java framework layer and the native layer use different computer languages, for example, the Java framework layer uses Java language, and the native layer generally uses C language or C + + language.
The JNI monitoring thread is a program in a local layer in the framework layer, so that an event monitored by the JNI monitoring thread cannot be directly transmitted to the upper Java layer, and the event needs to be reported to the Java layer through a Java native interface.
Therefore, in S103, the JNI monitoring thread monitors the device driver event corresponding to the specified service, calls the corresponding JNI, and reports the device driver event corresponding to the specified service to the Java layer, so that the Java layer can directly know the event of the device driver layer without passing through the hardware abstraction layer, and thus, the code of the hardware abstraction layer does not need to be modified.
In a specific implementation process, in response to a monitoring thread of the JNI monitoring that a device driving event corresponding to a specified service is monitored, the device driving event corresponding to the specified service is reported to a Java layer by calling the corresponding JNI, including: responding to the JNI monitoring thread to monitor the device driving event corresponding to the specified service, and acquiring the monitored event identification of the device driving event corresponding to the specified service; and reporting the event identification of the device driving event corresponding to the specified service to a Java layer by calling the corresponding JNI.
In a specific implementation process, the designated service is a fingerprint service, and the device driving event corresponding to the designated service is a fingerprint device driving event.
The code implementing the embodiment shown in FIG. 1 is independent of the android framework layer and does not need to be embedded in the original framework layer of the android system. The embodiment shown in fig. 1 does not need to change the codes of the android framework layer, and reports the bottom layer events to the upper Java layer through the independent codes, so that the codes are centralized and independent, and multiplexing management and maintenance are facilitated. The independent concentrated codes have the characteristic of high cohesion and low coupling, so that the stability of the codes is improved.
Fig. 2 is a diagram illustrating a second process of an event processing method according to an embodiment of the present invention. As shown in fig. 2, in this embodiment, the event processing method is applied to an android terminal, and the method includes the following steps:
s201, creating a JNI monitoring thread in a System _ Server process, wherein the JNI monitoring thread is used for monitoring a device driving event corresponding to a specified service;
s202, running a JNI monitoring thread in a local layer;
s203, collecting operation information through collection equipment corresponding to the specified service;
s204, identifying the operation information to obtain a device driving event corresponding to the specified service;
s205, sending the device driving event to a local layer;
and S206, responding to the monitoring of the device driving event corresponding to the specified service by the JNI monitoring thread, and reporting the device driving event corresponding to the specified service to the Java layer by calling the corresponding JNI.
In S205, after the device driving event corresponding to the specified service is obtained, the device driving event is sent to the local layer, and the JNI listening thread listens to the device driving event. Therefore, the device driving event can be directly uploaded to the local layer of the framework layer by the device driving layer without passing through the hardware abstraction layer.
The event processing method according to the embodiment of the present invention is further described in detail by using an application example.
In this example, the terminal is a mobile phone, the designated service is a fingerprint service, and the device driving event corresponding to the designated service is a fingerprint device driving event. The event processing method of the present example includes the steps of:
a1, starting the mobile phone;
a2, initializing the fingerprint service in the mobile phone;
a3, after the fingerprint service is initialized, creating a JNI monitoring thread in a System _ Server process, wherein the JNI monitoring thread is used for monitoring a device driving event corresponding to the fingerprint service, namely a fingerprint light touch event;
a4, running a JNI monitoring thread at a local layer, and monitoring a fingerprint light touch event;
a5, collecting operation information through a collecting device corresponding to the fingerprint service;
a6, identifying the operation information to obtain a fingerprint touch event corresponding to the fingerprint service;
a7, sending the fingerprint light touch event to the local layer;
after a user touches a fingerprint module of the mobile phone, a fingerprint touch event is determined through a fingerprint IC algorithm, after the kernel layer learns the fingerprint touch event, a message is sent to a JNI monitoring thread, and the JNI monitoring thread receives the message and indicates that the fingerprint touch event is monitored.
a8, judging whether the JNI monitoring thread monitors a fingerprint touch event, if the fingerprint touch event is monitored, executing a step a9, otherwise, repeating a 8;
a9, calling a Java local interface, and reporting the fingerprint light touch event to a Java layer.
The event processing method provided by the embodiment of the invention monitors the device driving event corresponding to the specified service through the JNI monitoring thread established in the System _ Server process, calls the corresponding Java local interface, reports the device driving event corresponding to the specified service to the Java layer, and reports the bottom layer event to the upper Java layer by utilizing the independent codes, so that the codes are centralized and independent, the multiplexing management and maintenance are facilitated, and the codes in the independent set have the characteristics of high cohesion and low coupling, thereby improving the stability of the codes.
Example two
An embodiment of the present invention provides an event processing apparatus, which is capable of implementing each step of the event processing method in the first embodiment.
Fig. 3 is a functional block diagram of an event processing apparatus according to an embodiment of the present invention. As shown in fig. 3, in this embodiment, the event processing apparatus may be disposed in an android terminal, and the apparatus includes:
the creating module 310 is configured to create a Java native interface JNI monitoring thread in a System service System _ Server process, where the JNI monitoring thread is used to monitor a device driving event corresponding to a specified service;
the running module 320 is configured to run a JNI monitoring thread on a local layer;
and the reporting module 330 is configured to respond to the JNI monitoring thread monitoring that the device driving event corresponding to the specified service is monitored, and report the device driving event corresponding to the specified service to the Java layer by invoking the corresponding JNI.
In a specific implementation process, when the reporting module 330 is configured to monitor the device driving event corresponding to the specified service in response to the JNI monitoring thread and report the device driving event corresponding to the specified service to the Java layer by invoking the corresponding JNI, the reporting module is specifically configured to: responding to the JNI monitoring thread to monitor the device driving event corresponding to the specified service, and acquiring the monitored event identification of the device driving event corresponding to the specified service; and reporting the event identification of the device driving event corresponding to the specified service to a Java layer by calling the corresponding JNI.
In a specific implementation process, the designated service is a fingerprint service, and the device driving event corresponding to the designated service is a fingerprint device driving event.
In a specific implementation process, the event processing apparatus may further include: the acquisition module is used for acquiring operation information through acquisition equipment corresponding to the specified service; the identification module is used for identifying the operation information to obtain a device driving event corresponding to the specified service; and the sending module is used for sending the device driving event to the local layer.
Since the event processing apparatus in this embodiment is capable of executing the event processing method in the first embodiment, reference may be made to the related description of the event processing method in the first embodiment for a part of this embodiment that is not described in detail.
The event processing device provided by the embodiment of the invention monitors the device driving event corresponding to the specified service through the JNI monitoring thread established in the System _ Server process, calls the corresponding Java local interface, reports the device driving event corresponding to the specified service to the Java layer, and reports the bottom layer event to the upper Java layer by utilizing the independent codes, so that the codes are centralized and independent, the multiplexing management and maintenance are facilitated, and the codes in the independent set have the characteristics of high cohesion and low coupling, thereby improving the stability of the codes.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the apparatus and the module described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the embodiments provided in the present invention, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and other divisions may be realized in practice, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing unit, or each module may exist alone physically, or two or more modules are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a Processor (Processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (4)
1. An event processing method is applied to an android terminal, and is characterized by comprising the following steps:
creating a Java local interface JNI monitoring thread in a System service System _ Server process, wherein the JNI monitoring thread is used for monitoring a device driving event corresponding to a specified service;
running the JNI monitoring thread on a local Native layer;
responding to the JNI monitoring thread to monitor the device driving event corresponding to the specified service, and reporting the device driving event corresponding to the specified service to a Java layer by calling the corresponding JNI;
responding to the JNI monitoring thread to monitor the device driving event corresponding to the specified service, and reporting the device driving event corresponding to the specified service to a Java layer by calling the corresponding JNI, wherein the method comprises the following steps:
responding to the JNI monitoring thread to monitor the device driving event corresponding to the specified service, and acquiring the monitored event identification of the device driving event corresponding to the specified service;
reporting the event identification of the device driving event corresponding to the specified service to a Java layer by calling a corresponding JNI;
the specified service is a fingerprint service, and the device driving event corresponding to the specified service is a fingerprint device driving event.
2. The method of claim 1, further comprising:
collecting operation information through collection equipment corresponding to the specified service;
identifying the operation information to obtain a device driving event corresponding to the specified service;
and sending the device driving event to a local layer.
3. An event processing device is arranged on an android terminal, and is characterized by comprising:
the System comprises a creating module, a judging module and a processing module, wherein the creating module is used for creating a Java local interface JNI monitoring thread in a System service System _ Server process, and the JNI monitoring thread is used for monitoring a device driving event corresponding to a specified service;
the running module is used for running the JNI monitoring thread on a local Native layer;
the reporting module is used for responding to the monitoring of the device driving event corresponding to the specified service by the JNI monitoring thread, and reporting the device driving event corresponding to the specified service to a Java layer by calling the corresponding JNI;
the reporting module is configured to, when responding to the JNI monitoring thread to monitor the device driving event corresponding to the specified service and reporting the device driving event corresponding to the specified service to a Java layer by invoking a corresponding JNI, specifically:
responding to the JNI monitoring thread to monitor the device driving event corresponding to the specified service, and acquiring the monitored event identification of the device driving event corresponding to the specified service;
reporting the event identification of the device driving event corresponding to the specified service to a Java layer by calling a corresponding JNI;
the specified service is a fingerprint service, and the device driving event corresponding to the specified service is a fingerprint device driving event.
4. The apparatus of claim 3, further comprising:
the acquisition module is used for acquiring operation information through acquisition equipment corresponding to the specified service;
the identification module is used for identifying the operation information to obtain a device driving event corresponding to the specified service;
and the sending module is used for sending the device driving event to a local layer.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710217345.6A CN106991017B (en) | 2017-04-05 | 2017-04-05 | Event processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710217345.6A CN106991017B (en) | 2017-04-05 | 2017-04-05 | Event processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106991017A CN106991017A (en) | 2017-07-28 |
| CN106991017B true CN106991017B (en) | 2020-12-25 |
Family
ID=59416306
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710217345.6A Active CN106991017B (en) | 2017-04-05 | 2017-04-05 | Event processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106991017B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112698999B (en) * | 2019-10-23 | 2022-03-29 | Oppo广东移动通信有限公司 | System monitoring method, device, terminal equipment and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104778075A (en) * | 2015-04-03 | 2015-07-15 | 北京奇虎科技有限公司 | Method and device for calling Java layer API (Application Program Interface) by native layer in Android system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102662665B (en) * | 2012-03-29 | 2015-04-22 | 福州瑞芯微电子有限公司 | Input subsystem enabling Android to support various sensors |
| CN103870316B (en) * | 2014-04-11 | 2016-09-07 | 烽火通信科技股份有限公司 | A kind of JAVA virtual machine realization method in intelligent operating system |
| CN105094952B (en) * | 2015-09-07 | 2018-08-07 | 网易（杭州）网络有限公司 | A kind of method and apparatus of analog subscriber operation |
| CN105242770B (en) * | 2015-11-03 | 2019-07-19 | 上海斐讯数据通信技术有限公司 | A kind of method and system of Android device folding lid |
| CN105376494B (en) * | 2015-11-30 | 2018-11-23 | 诚迈科技（南京）股份有限公司 | A method of multichannel USB camera is supported based on Android system |
-
2017
- 2017-04-05 CN CN201710217345.6A patent/CN106991017B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104778075A (en) * | 2015-04-03 | 2015-07-15 | 北京奇虎科技有限公司 | Method and device for calling Java layer API (Application Program Interface) by native layer in Android system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106991017A (en) | 2017-07-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110442502B (en) | Point burying method, device, equipment and storage medium | |
| CN105068865A (en) | Task scheduling method and apparatus | |
| CN107645546B (en) | File monitoring method based on android system, intelligent device and storage medium | |
| CN103150155B (en) | Data interception method and device | |
| CN112685148B (en) | Asynchronous communication method and device for mass terminals, computer equipment and storage medium | |
| CN103729292A (en) | Cross-host cross-platform remote command invoking method and system | |
| CN105975856A (en) | Method and system for dynamic virus detection of mobile terminal | |
| CN103309728A (en) | Asynchronous request processing method and equipment | |
| CN111666145A (en) | Message processing method and system of message queue and computer equipment | |
| CN114025037B (en) | Cloud mobile phone overhaul method and device, electronic equipment and storage medium | |
| CN109561134B (en) | Electronic device, distributed cluster service distribution method and storage medium | |
| CN106991017B (en) | Event processing method and device | |
| CN103618758A (en) | Web server and system resource access control method thereof | |
| CN108520063A (en) | Processing method, device and the terminal device of event log | |
| CN112887355B (en) | Service processing method and device for abnormal server | |
| CN112835639A (en) | Hook implementation method, device, equipment, medium and product | |
| CN111376255B (en) | Robot data acquisition method and device and terminal equipment | |
| CN105228139B (en) | A kind of call processing method, device and equipment based on smart machine | |
| CN114841267B (en) | Real-time prediction method, device, electronic equipment and computer program product | |
| CN110244974B (en) | Application program maintenance control method, device, server, terminal and storage medium | |
| CN112882711A (en) | Rendering method, device, equipment and storage medium | |
| CN106980575A (en) | A kind of event-handling method and device | |
| CN111176959A (en) | Early warning method, system and storage medium for cross-domain application server | |
| CN110750597A (en) | Data processing method and device, storage medium and processor | |
| CN103577177A (en) | Method and equipment for invoking graphics libraries |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |