CN102123196B - Method for realizing WinCE/Android mixed API (Application Programming Interface) on Android cell phone - Google Patents
Method for realizing WinCE/Android mixed API (Application Programming Interface) on Android cell phone Download PDFInfo
- Publication number
- CN102123196B CN102123196B CN201010622298.1A CN201010622298A CN102123196B CN 102123196 B CN102123196 B CN 102123196B CN 201010622298 A CN201010622298 A CN 201010622298A CN 102123196 B CN102123196 B CN 102123196B
- Authority
- CN
- China
- Prior art keywords
- android
- api
- wince
- function
- application
- 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
Landscapes
- Stored Programmes (AREA)
- Telephone Function (AREA)
Abstract
The invention relates to a method for realizing a WinCE/WM (Windows Mobile) and Android mixed API (Application Programming Interface) on an Android cell phone. In an Android system, a proxy process as an Android process is provided for a WinCE/WM application operating outside Android, a virtual API intermediary layer is provided for the proxy process, the calling of an Android API function by an application program is converted into an operation request to be sent to the proxy process, and the proxy process calls a corresponding Android function and sends a result back to the application process. The method provided by the invention has the beneficial effects that programmers can provide a mixed API for the development of the applications of a WinCE/WM mode and the applications can call functions provided by the Android in a program.
Description
Technical field
The present invention relates to a kind of Android field of mobile phones, especially a kind of method that realizes WinCE/Android mixing API at the Android mobile phone, its outstanding feature is to make the programmer both can call the function of WinCE when exploitation Android application software in program, can call the function of Android itself again.
Background technology
The intelligent mobile terminal device that with the mobile phone is representative is an important development direction of computer technology, is again the market that competition is very fierce.Since Google and open mobile phone alliance's release Android operating system and the mobile phone based on Android, occupied no small share at world's mobile phone market soon, various Android mobile phones emerge in an endless stream, also being based on Android by China Mobile exploitation and the OPhone that releases, also is a kind of Android mobile phone.
So-called Android operating system, be actually a kind of reorganization and expansion to (SuSE) Linux OS, its kernel is exactly the kernel of Linux basically, but but done significantly to improve and strengthen at the characteristics of mobile phone and mobile terminal device specially at user's space, these are changed mostly with programming mode and graphical interfaces, are that graphic user interface (GUI) is relevant.
The operating system that another kind is usually used in mobile phone be Microsoft WinCE and WM, be Windows Mobile, this is to grow up in the Windows of Microsoft operating system.Mobile phone based on WinCE/WM also accounts for no small share in market, and has developed the no small WinCE/WM application software of quantity.Moving if can take these application software on the Android mobile phone, obviously is favourable for the occupation rate of market that improves the Android mobile phone.
By open source software Wine is transplanted on the Android mobile phone, the support grafting that should be provided by Windows to Linux, and expanded, make it to support WinCE/WM to it, can allow the WinCE/WM application software directly move at the operation of Android mobile phone, the linux kernel that is actually at the Android mobile phone.Like this, the people who originally is familiar with the WinCE/WM software development just can be by original pattern, in original development environment, use original developing instrument, WinCE/WM software is developed Android software as Kai Fa, and the software that develops is that WinCE/WM software can move at the Android mobile phone again, and this also is very favourable for the developer.
, the software that develops like this is still pure WinCE/WM software in fact, and its basis is to promise to undertake the every function that provides by WinCE/WM.In fact, there do not have a kind of application software what one is particularly good at not have to be big and small fully by all functions are provided oneself, all is to be based upon on the basis of the more basic functions that other software such as operating system, basic platform, middleware etc. provide.Conversely, every promise provides the software of some function for other software, and then will define, namely offer some clarification on oneself to provide some which type of functions, and how to call these functions.Such definition is called " application programming interface ", is API.On the other hand, the function of software is realized by " function " and provides, since such software will provide some function for other software, just must provide a function set of in fact realizing these functions, so another meaning of API just refers to a such function set.As seen, the above-mentioned API that all is based on WinCE/WM for the application software of WinCE/WM platform development.And the Android software of " orthodox school " then is based on the API of Android oneself.Transplanted after the Wine, though these two kinds of application software can both be moved at Android, in fact be that well water does not intrude into river water, irrelevant mutually.From the principle, the API of WinCE/WM and the API of Android should be homologues of equal value in function aspects, but in fact can only be like this substantially, the two still is some difference, even so the WinCE/WM that develops at the Android mobile phone uses, can not take full advantage of the advantage of Android.Because these functions are in Android inside of frame operation, though and WinCE/WM software can move on the linux kernel of Android mobile phone, be the outside at the Android framework.The more important thing is that Android is an open system, constantly has many new basic functions to be created out and be added among the API of Android, in for the WinCE/WM written program, just can not call these functions.
Can imagine, if one " mixing API " can be provided for the developer that WinCE/WM uses, make them in program, can as usually call the function that the API by WinCE/WM provides, some special or novel functions that provided by Android can be provided again, and these developers just can develop more better application softwares for Android.Say it for example, for the Android from Google, map function is its strong point, if exploitation is the Android application of " orthodox school ", calling with the map function associated in program is to be relatively easy to.But, if exploitation is the application of WinCE/WM pattern, although purpose also is to move at the Android mobile phone, can't call these functions.This shows, provide one to mix API, make the application of WinCE/WM pattern also can call the peculiar function of Android in program, is highly significant.
But, such API not a duck soup is provided.
Summary of the invention
The problem of mixing API is provided for solution, the invention provides a kind of method that realizes WinCE/Android mixing API at the Android mobile phone, it is a kind of method that adopts agency mechanism, in the Android system, for using, the WinCE/WM that runs on the Android outside provides one as the agent process of Android process, and provide a virtual API intermediary layer for it, application program is changed into operation requests and sends to agent process calling of Android api function, call corresponding Android function and the result is sent back to application process by agent process.
The present invention solves the technical scheme that its technical problem adopts: this method at Android mobile phone realization WinCE/WM and Android mixing API of the present invention, and main points are:
● whenever will just creating an agent process AppProxy for it in the Android system when the Android mobile phone starts a WinCE/WM and uses, the application process of this process and reality " is lived and died together ", and arranged identical life cycle.Actual application process all follows the TinyX service processes to have socket to be connected with agent process.
● provide a virtual Android API intermediary module in the Android outside for WinCE/WM uses, provide the api function corresponding with the Android function by this intermediary's module.This intermediary's module and original Wine module lump together the API that WinCE/WM both is provided, and the API of Android also is provided, so be called " mixing API ".
● when Android api function that the WinCE/WM application call is provided by API intermediary layer module, the intermediary layer module converts it into operation requests, and sends it to the TinyX service processes.
● the TinyX service processes is transmitted to agent process with operation requests.
● agent process in the corresponding Android function of Android framework intrinsic call, and sends back to operation result the application process of Android outside according to operation requests via the TinyX service processes.
● application process is from returning the calling of Android api function.
Why the operation requests here and operation result will be transmitted by the TinyX service processes, are because application process just had socket to be connected with the TinyX service processes originally, and agent process will be set up socket with the TinyX service processes and is connected very convenient.On the Linux platform, TinyX or X service processes are to use the unified service processes that figure shows and man-machine interaction is imported that provides for Linux.But, this link of TinyX service processes also can be skipped, and makes directly to set up socket by application process and agent process into and is connected also direct communication.
Like this, be in the operation of the outside of Android framework though WinCE/WM uses, calling but of function that Android provides finished in the Android inside of frame by agent process.By contrast, application program is then irrelevant with Android to calling of WinCE/WM api function.From programming angle, it is a mixing API that WinCE/WM uses utilizable API.
The effect that the present invention is useful is: make programmers provide one to mix API for the exploitation that the WinCE/WM pattern is used, make these application that the function that is provided by Android can be provided in program.The direct purpose of the present invention is to provide the API that mixes API, namely is made of WinCE/WM API and Android API mixing for the WinCE/WM that moves at the Android mobile phone uses; But in fact also can be used for providing the API that mixes API, namely constituted by Linux API and Android API mixing for the Linux that moves at the Android mobile phone uses.
Description of drawings
Fig. 1 provides by the method for the invention to mix API system schematic before;
Fig. 2 provides by the method for the invention to mix API system schematic afterwards;
Fig. 3 is the program flow diagram of AppProxy.
Embodiment
The invention will be further described below in conjunction with drawings and Examples:
Vertical dotted line among Fig. 1 with system in two, the right is Android system and application thereof, the left side is the application of Linux itself, the two shares same linux kernel.There are two Android processes on the right among the figure, they are the various basic functions that provided by Android of the API Calls by Android all, and Android then calls the more basic functions that is provided by kernel by the API (being called " system call ") of linux kernel.By contrast, the left side is the application of Linux itself, and the Wine module among the figure is used changing into Linux originally in the application that WinCE/WM moves, and in other words: WinCE/WM application+Wine=Linux uses.But however, the interface between WinCE/WM application and the Wine but still is the API of WinCE/WM.Like this, that API that is afraid of Android provides good function, uses the inside at WinCE/WM and also can't be called.
At these many on one side application proxy process AppProxy of Android, this agent process is equivalent to an Android to be used among Fig. 2, and it can call any function that the API of Android provides.And Linux this on one side, then many intermediary's modules.This provides a virtual Android API on one side to this intermediary's module at Linux.Why say virtual, be because in fact this module is not really realized these functions on this one side of Linux, but send operation requests by the Socket connection to this agent process AppProxy on one side of Android, be achieved in the framework of Android by AppProxy.Like this, by the API that intermediary's module provides, add the API that is provided by the Wine module, lump together and just constituted one and mix API.
In fact, the API that is provided by intermediary's module needs not to be complete Android API, and only need be the latter's a subclass, because most of function that AndroidAPI provides has in WinCE/WM API, some more distinctive functions among the just Android API that need be provided by intermediary's module.
Among Fig. 3, when the Linux that will start a band graphical interfaces as the user used, actual that start was AppProxy, was used for starting Linux originally and used required order line and then pass to AppProxy as (for AppProxy's) command line parameter.After the startup, AppProxy just enters a circulation, and the request that wait is used from WinCE/WM in circulation is just resolved and carried out in case there is request to arrive, and the result is sent back to the WinCE/WM application, just enters the next round circulation then.
In the concrete enforcement of this method, the transfer of TinyX service processes is all passed through in communicating by letter between WinCE/WM application process and the agent process AppProxy.This be because, present Linux platform all is with graphical human-computer interaction interface (GUI), general Linux uses (except Android) and must come into contacts with the TinyX service processes that human-computer interaction interface is provided when moving.These Linux application processes are just set up Socket with the TinyX service processes automatically and are connected when starting.And agent process AppProxy also is easy to set up Socket with the TinyX service processes connect, because the latter was exactly a service processes originally, just connects with it in other process of wait originally.So it is the modification of the source code of X that the concrete enforcement of this method relates to TinyX, X is open source software, and its source code can obtain from relevant website.
Supposing among the API of Android to have defined a function, is to play one section background music, and we want to allow WinCE/WM can call this function in using.The framework of Android adopts Java language, and a function is called one " method (Method) ", and the title of this method is start_music, and the definition in API is:
public?boolean?start_music(String[]filename，int?volume)；
This " method " has two parameters, and first is the filename of audio file, and second is the volume of playing.Our purpose is that this function among the Android API is offered the WinCE/WM application as a function that mixes among the API.
An embodiment who divides five aspect explanation this method below.Notice that same method can have multiple different enforcement, provided here is one of them.
1, as the executable program AppProxy of application proxy
For in the Android framework, carrying out the Android api function operation requests from WinCE/WM application and intermediary's module, need this create an agent process on one side at Android, on one side this calls the various functions that Android API provides at Android by this agent process.
In the Android system, an application process is called an Activity, be " class (Class) " in the Java language, this kind is extended to a self-defining class, be exactly that an Android uses, at last on the display screen of Android, just have an icon, click this icon and will carry out " method (Method) " onCreate () in this class.So onCreate () just is equivalent to the main () in the c program.Provide relevant false code below
This Activity at first will start the FS application of Linux, concrete grammar is to call its method startApp by the JNI mechanism of Java language, and JNI mechanism can convert it into calling C language function Java_Android_AppProxy_jni_JniMethod_startApp () automatically:
This section program is created a subprocess by the system call fork () of Linux, allows this subprocess carry out the FS concrete application program of Linux then.So just guaranteed " with giving birth to " of agent process and application process; But this not enough, must guarantee " dead altogether " of the two, can also be defined as a kind of additional operation requests to " out of service " for this reason, sends this request at the eve out of service to agent process by application process, makes agent process in time out of service.
2, the agreement of an intercommunication of definition
When the WinCE/WM application is partly called its certain function according to the Android among the mixing API, it is actual that what called is certain corresponding function with it in intermediary's module, this function will send specific operation requests to agent process AppProxy, carried out by agent process, operation requests sends as " message ".For this reason, need between intermediary's module and agent process, define the agreement of an intercommunication, make agent process can correctly understand the intention of intermediary's module.
The agreement of so-called intercommunication, one side are the forms of message, are the types of message on the one hand.
As embodiment, the form of message can define like this:
● 32 integer representation type of messages of first in the message, type of message are representing the function (being a kind of specific function) among the API.
● second 32 integer in the message in two, the number of its high 16 bit representation parameters, the length of the low whole message of 16 bit representations.
● the 3rd 32 integers in the message begin to be call parameters.If the type of parameter is pointer (definition can be known according to api function), then to copy data structure pointed in message, make the starting point of copy in message of this this data structure of pointed again.For example, suppose that by parameter among the API 2 are character string pointers, that will be copied this character string in message, make parameter 2 point to this copy then.
As for type of message, in we embodiment, can define like this:
As previously mentioned, we are example with the function start_music that plays music, so only listed a definition that type is PROXY_START_MUSIC here.In fact what have need be placed on the function that mixes among the API will define how many different type of messages.Note PROXY_START_MUSIC being defined as 0x80000020 here, its highest order is 1, and this is that the drawing command of TinyX itself can not use so big numerical value for the drawing command with TinyX itself makes a distinction.
3, in intermediary's module, provide corresponding mixing api function
Intermediary's module is embodied as a dynamic link libraries, is DLL.A supporting .h file also will be arranged simultaneously, and this .h file is exactly the definition of API, and the inside has provided the prototype definition of all api functions.Because we will provide start_music this function, just add in this .h function:
int?start_music(char*filename，int?volume)；
This definition with the front is slightly different, is because Java language is adopted in the definition of front, and adopts the C language here, is actually equally.
So just can this .h file of include in the program of WinCE/WM, just can in program, call this function then.Certainly, in the program of intermediary's module, must provide start_music () this function.But this function that provides in intermediary's module is not really play music as previously mentioned, and just sends an operation requests to application process, is the false code of this function below:
4, will be transmitted to application proxy from the message of intermediary's module by TinyX
TinyX is service processes, and its major cycle is Dispatch (), the code of this function Xserver dix among the dispatch.c.In this major cycle, the main thread of TinyX monitors input from external equipment and Socket by system call select () in a function WaitForSomething (), this section code source file Xserver os among the WaitFor.c:
When this thread of TinyX returns from system call select (), must be on certain socket or the I/O port what to have taken place, return value i indicates concrete socket or port, below just handled by WakeupHandler () and reacted.To do some modifications at WakeupHandler (): for socket, and the highest order of first 32 words is 1 in the message, just illustrate that this is for realizing mixing the message that API sends, will be handled this moment by function serv_api (), this function is for realizing that mixing API newly adds, and its false code is as follows:
Like this, be example with PROXY_START_MUSIC, this message will be forwarded to application proxy.
5, by the request of application proxy executable operations
As previously mentioned, when application proxy receives the message that is forwarded by TinyX, will be resolved and be called corresponding method (function) and be carried out.For this reason, for need all will in application proxy, increasing a method of correspondence therewith at each function that mixing API provides.Be example with start_music (), just increase a method do_start_music () in application proxy, its false code is as follows:
Notice that the WinCE/WM application process has individual api function start_music () in the module therebetween, individual start_music () is also arranged among the API of Android, but these two is different fully, and be in two different processes.Start_music () in intermediate module sends to message after the TinyX, just waits in sleep always, and the execution result of application proxy being beamed back up to TinyX is transmitted just and is waken up, and turns back to the application program from start_music () again.
In addition to the implementation, the present invention can also have other execution modes.All employings are equal to the technical scheme of replacement or equivalent transformation formation, all drop on the protection range of requirement of the present invention.
Claims (3)
1. realize it is characterized in that the method for WinCE/WM and Android mixing API at the Android mobile phone for one kind:
1.1) whenever will be when the Android mobile phone starts a WinCE/WM and uses, just in the Android system, create an agent process for it, agent process has identical life cycle with the application process of reality, and two processes all follow the TinyX service processes to have socket to connect;
1.2) for using, WinCE/WM provides a virtual Android API intermediary module in the Android outside, provide the API corresponding with the Android function by this intermediary's module; This intermediary's module and original Wine module lump together the API that WinCE/WM both is provided, and the API of Android also is provided, and are called " mixing API ";
1.3) when Android api function that the WinCE/WM application call is provided by intermediary's module, intermediary's module converts it into operation requests, and sends it to the TinyX service processes;
1.4) the TinyX service processes is transmitted to agent process with operation requests;
1.5) agent process in the corresponding Android function of Android framework intrinsic call, and sends back to operation result the application process of Android outside according to operation requests via the TinyX service processes.
2. according to claim 1ly realize the method for WinCE/WM and Android mixings API at the Android mobile phone, it is characterized in that: this method is integrated with Android mutually for X window image interface.
3. the method at Android mobile phone realization WinCE/WM and Android mixing API according to claim 1 is characterized in that: directly set up socket between application process and the agent process and connect and direct communication, transmit without the TinyX service processes.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010622298.1A CN102123196B (en) | 2010-12-29 | 2010-12-29 | Method for realizing WinCE/Android mixed API (Application Programming Interface) on Android cell phone |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010622298.1A CN102123196B (en) | 2010-12-29 | 2010-12-29 | Method for realizing WinCE/Android mixed API (Application Programming Interface) on Android cell phone |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102123196A CN102123196A (en) | 2011-07-13 |
| CN102123196B true CN102123196B (en) | 2013-07-17 |
Family
ID=44251645
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010622298.1A Active CN102123196B (en) | 2010-12-29 | 2010-12-29 | Method for realizing WinCE/Android mixed API (Application Programming Interface) on Android cell phone |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102123196B (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102331928A (en) * | 2011-06-24 | 2012-01-25 | 浙大网新科技股份有限公司 | Method of source code level compatible hybrid API (application programming interface) |
| CN102331927B (en) * | 2011-06-24 | 2014-06-25 | 浙大网新科技股份有限公司 | Method for integrating soft keyboard input of Wine and Android mobile phone |
| CN102419708B (en) * | 2011-12-19 | 2014-04-09 | 广州杰赛科技股份有限公司 | Method and device for operating Java 2 micro edition (J2ME) games |
| CN102768680A (en) * | 2012-06-26 | 2012-11-07 | 广东欧珀移动通信有限公司 | Fast searching method for camera |
| CN105607895B (en) * | 2014-11-21 | 2021-03-02 | 阿里巴巴集团控股有限公司 | Application program operation method and device based on application program programming interface |
| CN104850462B (en) * | 2015-05-04 | 2018-12-14 | 联想(北京)有限公司 | A kind of information processing method and electronic equipment |
| CN105183455B (en) * | 2015-08-13 | 2018-09-21 | 深圳市广和通无线股份有限公司 | A kind of method and system integrating JT/T808 programs under Android platform |
| CN105867964A (en) * | 2015-12-15 | 2016-08-17 | 乐视网信息技术（北京）股份有限公司 | Android platform open service access system and generation system thereof and generation method and access method |
| CN108170503B (en) * | 2018-01-24 | 2022-04-12 | 腾讯科技（深圳）有限公司 | Method, terminal and storage medium for cross-system android application running |
| CN109189584B (en) * | 2018-07-05 | 2021-02-19 | 北京三快在线科技有限公司 | Communication method and device between application programs, electronic equipment and storage medium |
| CN110109718B (en) * | 2019-03-26 | 2023-06-02 | 创新先进技术有限公司 | Application program interface calling method and device |
| CN112558841B (en) * | 2020-09-29 | 2022-05-20 | 统信软件技术有限公司 | Application icon management method, computing device and readable storage medium |
| CN114047945B (en) * | 2021-11-17 | 2024-07-12 | 沈阳概幕网络科技有限公司 | Application software compatible method, device, computer equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101840341A (en) * | 2010-04-01 | 2010-09-22 | 惠州Tcl移动通信有限公司 | Intelligent mobile phone system and starting method thereof |
| CN201639632U (en) * | 2009-12-25 | 2010-11-17 | 深圳市银星数码有限公司 | Multi-system multi-module intelligent mobile terminal |
| CN101924775A (en) * | 2010-09-08 | 2010-12-22 | 北京大学 | A transparent loading method and system for Android application components |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TWI336848B (en) * | 2002-08-26 | 2011-02-01 | Interdigital Tech Corp | Wireless transmit/receive unit and method for providing a communication path between a plurality of operating systems in a wireless device |
| KR20040050460A (en) * | 2002-12-10 | 2004-06-16 | 주식회사 셀빅 | Pocketpc shell emulator and emulation method thereof, and personal digital assistant comprising the same |
-
2010
- 2010-12-29 CN CN201010622298.1A patent/CN102123196B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN201639632U (en) * | 2009-12-25 | 2010-11-17 | 深圳市银星数码有限公司 | Multi-system multi-module intelligent mobile terminal |
| CN101840341A (en) * | 2010-04-01 | 2010-09-22 | 惠州Tcl移动通信有限公司 | Intelligent mobile phone system and starting method thereof |
| CN101924775A (en) * | 2010-09-08 | 2010-12-22 | 北京大学 | A transparent loading method and system for Android application components |
Non-Patent Citations (2)
| Title |
|---|
| Windows程序运行于Linux系统的技术;王亚军等;《计算机应用》;20090831;第29卷(第8期);第2128-2131、第2135页 * |
| 王亚军等.Windows程序运行于Linux系统的技术.《计算机应用》.2009,第29卷(第8期),第2128-2131、2135页. |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102123196A (en) | 2011-07-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102123196B (en) | Method for realizing WinCE/Android mixed API (Application Programming Interface) on Android cell phone | |
| US10839141B2 (en) | System and method for provisioning a mobile software application to a mobile device | |
| WO2022199111A1 (en) | Method and apparatus for implementing functions in application program, electronic device and storage medium | |
| CA2208289C (en) | Method and computer program product for interconnecting software drivers in kernel mode | |
| US7895594B2 (en) | Virtual machine extended capabilities using application contexts in a resource-constrained device | |
| CN104740872B (en) | Simulate game program operation control method and device in Android environment | |
| WO2021129253A1 (en) | Method for displaying multiple windows, and electronic device and system | |
| CN100354828C (en) | Middleware services layer for platform system for mobile terminals | |
| CN102073542B (en) | Method for integrating Chinese input method during operation of Linux applications on Android mobile phone | |
| WO2021018005A1 (en) | Inter-process communication method, apparatus and device | |
| US20040083015A1 (en) | System for multimedia rendering in a portable device | |
| JP2013542515A (en) | Redirection between different environments | |
| AU2003251399C1 (en) | System for multimedia rendering in a portable device | |
| Hernandez et al. | Analysis for the design of open applications on mobile devices | |
| CN102364436A (en) | Method and system for realizing debugging of WinCE/Android mixed application program interface (API) | |
| CN102819430B (en) | A kind of device and method of realizing serial communication interface under linux environment | |
| She et al. | Hermes: A tool for testing mobile device applications | |
| CN102799581B (en) | A kind of system and method realizing cross-platform graphic library | |
| CN113419650B (en) | Data moving method, device, storage medium and electronic device | |
| Pan et al. | Development and research of music player application based on android | |
| Fu et al. | Research on audio/video codec based on Android | |
| CN115314588B (en) | Background synchronization method, device, terminal, equipment, system and storage medium | |
| WO2022166553A1 (en) | Method and apparatus for implementing batch system calls | |
| Mikkonen et al. | Towards pervasive mashups in embedded devices | |
| CN114296809A (en) | An operating system-based object model construction method and its system call interface |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |