Data transmission method and device, electronic equipment and storage medium
By installing Android and Linux systems on electronic devices and using the remote desktop client and input method framework, the problem of passing data input in the Android system to Linux applications is solved, and the effective data transmission and display is achieved.
Patent Information
- Application Number
- CN202311014603.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-11
- Publication Date
- 2025-02-18
AI Technical Summary
The prior art is difficult to pass the target data entered by users in the Android system to Linux applications, resulting in the inability to display the target data in Linux applications.
By installing the Android system and Linux system on an electronic device, using the remote desktop client and input method framework, the user's input data in the Android system is sent to the second input method application in the Linux system through the first transmission protocol, and the When a virtual key event is received, the data is sent to the target Linux application.
It realizes the data entered by users in the Android system to Linux applications, so that the data can be displayed in Linux applications, solving the problem of difficulty in data transmission in traditional technology.
Smart Images

Figure CN119473647A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a data transmission method, device, electronic device and storage medium. Background Art
[0002] With the popularity of virtual environments (such as virtual machines), operating systems can usually be installed in the local environment and virtual environment of the same device respectively. For example, an Android system can be installed in the local environment of an electronic device, and a Linux system can be installed in the virtual environment of the electronic device.
[0003] In actual applications, it is usually difficult for electronic devices to pass target data input by users in Android input method applications in Android systems to Linux applications in Linux systems, and thus it is impossible to display the target data through Linux applications. For example, the target data may be IME data.
[0004] Therefore, how to pass the target data input by the user in the Android system to the Linux application so as to display it through the Linux application in the Linux system is a problem that needs to be solved. Summary of the invention
[0005] The purpose of the embodiments of the present application is to provide a data transmission method, device, electronic device and storage medium to solve the problem that it is difficult to transmit user input data in an Android system to a Linux application.
[0006] On the one hand, an embodiment of the present application provides a data transmission method, which is applied to an electronic device, wherein the electronic device is respectively installed with an Android system and a Linux system, wherein the Android system is installed in a local environment of the electronic device, and the Linux system is installed in a virtual environment of the electronic device, and the method includes:
[0007] Acquire target data input by a user through a first input method application; the first input method application is installed in an Android system;
[0008] Sending the target data to a second input method application via a first transmission protocol; the second input method application is installed in a Linux system;
[0009] In response to the second input method application receiving a virtual key event, the target data is sent to a target application; the target application is an application installed in the Linux system.
[0010] In one implementation, sending the target data to the second input method application via the first transmission protocol includes:
[0011] Sending the target data to the first input method framework in the Android system through the first input method application;
[0012] The target data is sent to a remote desktop client through the first input method framework; the remote desktop client is a client installed on the Android system;
[0013] The target data is sent to the second input method application through the remote desktop client using the first transmission protocol.
[0014] In one embodiment, the method further comprises:
[0015] Sending virtual key events to the target application through the remote desktop client using the second transmission protocol;
[0016] Sending virtual key events to the second input method framework in the Linux system through the target application;
[0017] The virtual key event is sent to the second input method application through the second input method framework.
[0018] In one implementation, sending a virtual key event to a target application through a remote desktop client using a second transmission protocol includes:
[0019] When it is determined that the target data is to be sent, a virtual key event is sent to a listening process in the Linux system based on the second transmission protocol through the remote desktop client;
[0020] Send the target data to the virtual key event through the monitoring process.
[0021] In one implementation, sending target data to a target application includes:
[0022] Sending target data to the second input method framework in the Linux system;
[0023] The target data is sent to the target application through the second input method framework.
[0024] In one embodiment, the method further comprises:
[0025] Display target data through target applications.
[0026] On the one hand, an embodiment of the present application provides a data transmission device, which is applied to an electronic device, wherein the electronic device is respectively installed with an Android system and a Linux system, wherein the Android system is installed in a local environment of the electronic device, and the Linux system is installed in a virtual environment of the electronic device, and the device includes:
[0027] An acquisition unit, configured to acquire target data input by a user through a first input method application; the first input method application is installed in the Android system;
[0028] A first sending unit is used to send the target data to a second input method application through a first transmission protocol; the second input method application is installed in a Linux system;
[0029] The second sending unit is used to send the target data to the target application in response to the second input method application receiving the virtual key event; the target application is an application installed in the Linux system.
[0030] In one implementation, the first sending unit is used to:
[0031] Sending the target data to the first input method framework in the Android system through the first input method application;
[0032] The target data is sent to a remote desktop client through the first input method framework; the remote desktop client is a client installed on the Android system;
[0033] The target data is sent to the second input method application through the remote desktop client using the first transmission protocol.
[0034] In one implementation, the second sending unit is further used for:
[0035] Sending virtual key events to the target application through the remote desktop client using the second transmission protocol;
[0036] Sending virtual key events to the second input method framework in the Linux system through the target application;
[0037] The virtual key event is sent to the second input method application through the second input method framework.
[0038] In one implementation, the second sending unit is further used for:
[0039] When it is determined that the target data is to be sent, a virtual key event is sent to a listening process in the Linux system based on the second transmission protocol through the remote desktop client;
[0040] Send the target data to the virtual key event through the monitoring process.
[0041] In one implementation, the second sending unit is used to:
[0042] Sending target data to the second input method framework in the Linux system;
[0043] The target data is sent to the target application through the second input method framework.
[0044] In one implementation, the second sending unit is further used for:
[0045] Display target data through target applications.
[0046] On the one hand, an embodiment of the present application provides an electronic device, including:
[0047] Processor; and
[0048] A memory stores computer instructions, wherein the computer instructions are used to enable a processor to execute the steps of the method provided in any of the above-mentioned various optional implementations of data transmission.
[0049] On the one hand, an embodiment of the present application provides a storage medium storing computer instructions, which are used to enable a computer to execute the steps of a method provided in any of the various optional implementations of data transmission described above.
[0050] The data transmission method of the embodiment of the present application includes obtaining target data input by a user through a first input method application; the first input method application is installed in an Android system; the target data is sent to a second input method application through a first transmission protocol; the second input method application is installed in a Linux system; in response to the second input method application receiving a virtual key event, the target data is sent to a target application; the target application is an application installed in the Linux system. In this way, the problem of difficulty in transmitting user input data in an Android system to a Linux application is solved. BRIEF DESCRIPTION OF THE DRAWINGS
[0051] In order to more clearly illustrate the specific implementation methods of the present application or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0052] Figure 1 It is a flow chart of a data transmission method according to an embodiment of the present application.
[0053] Figure 2 It is a schematic diagram of the architecture of a data transmission system according to an embodiment of the present application.
[0054] Figure 3 It is a structural block diagram of a data transmission device according to an embodiment of the present application.
[0055] Figure 4 It is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION
[0056] The technical solution of the present application will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described implementation methods are part of the implementation methods of the present application, rather than all of the implementation methods. Based on the implementation methods in the present application, all other implementation methods obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application. In addition, the technical features involved in the different implementation methods of the present application described below can be combined with each other as long as they do not conflict with each other.
[0057] First, some terms involved in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.
[0058] Terminal device: can be a mobile terminal, a fixed terminal or a portable terminal, such as a mobile phone, a station, a unit, a device, a multimedia computer, a multimedia tablet, an Internet node, a communicator, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a personal communication system device, a personal navigation device, a personal digital assistant, an audio / video player, a digital camera / camcorder, a positioning device, a television receiver, a radio broadcast receiver, an electronic book device, a gaming device or any combination thereof, including accessories and peripherals of these devices or any combination thereof. It is also foreseeable that the terminal device can support any type of interface for the user (such as a wearable device), etc.
[0059] Server: It can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, big data and artificial intelligence platforms, etc.
[0060] The technical idea of this application is explained below.
[0061] With the popularization of virtual environment applications, different operating systems can usually be installed in the local environment and virtual environment of the same device, for example, an Android system can be installed in the local environment of an electronic device, and a Linux system can be installed in the virtual environment of the electronic device.
[0062] However, in actual applications, it is usually difficult for an electronic device to transfer target data input by a user in an Android input method application in an Android system to a Linux application in a Linux system, and thus the target data cannot be displayed through the Linux application.
[0063] Under traditional technology, a single Latin letter input by a user in an Android system can usually be transmitted to a Linux application in a Linux system by using a virtual key, and the Latin letter is displayed by the Linux application. However, a character string input by a user in an Android system cannot be transmitted to a Linux application.
[0064] Based on the defects of the above-mentioned related technologies, the embodiments of the present application provide a data transmission method, device, electronic device and storage medium, aiming to solve the problem that it is difficult to transmit user input data in the Android system to the Linux application.
[0065] The present application provides a data transmission method in an embodiment, which can be applied to an electronic device. The present application does not limit the type of electronic device, which can be any device type suitable for implementation, such as a terminal device and a server, etc. The present application will not repeat this. The electronic device is respectively installed with an Android system and a Linux system, the Android system is installed in the local environment of the electronic device, and the Linux system is installed in the virtual environment of the electronic device.
[0066] See also Figure 1 As shown, it is a flow chart of a data transmission method in an embodiment of the present application. Figure 1 The method is described below. The specific implementation process of the method is as follows:
[0067] Step 100: Acquire target data input by a user through a first input method application; the first input method application is installed in an Android system.
[0068] The first input method application is an Android input method application, that is, any input method application that can be applied to the Android system. As an example, the first input method application can be an input method editor (IME) applied to the Android system.
[0069] In one implementation, a user performs a data input operation through an Android input method application in an Android system, and the electronic device obtains target data in response to the user's input operation on the Android input method application.
[0070] As an example, the target data input by the user is "weather forecast".
[0071] In this way, users can input data through the more commonly used Android input method applications, which is convenient to operate.
[0072] Step 101: Send target data to a second input method application via a first transmission protocol; the second input method application is installed in a Linux system.
[0073] In one implementation, when executing step 101, the following steps may be used:
[0074] S1011: Sending target data to a first input method framework in the Android system through a first input method application.
[0075] In one implementation, when the first input method framework is started, the first input method application is loaded at the same time, and the application of the first input method application needs to rely on the first input method framework.
[0076] The first input method framework may be an Android input method framework, that is, it may be applied to any input method framework in the Android system.
[0077] S1012: Sending target data to a remote desktop client via a first input method framework; the remote desktop client is a client installed on an Android system.
[0078] Optionally, the remote desktop client may be a client based on the Remote Desktop Protocol (RDP), that is, an RDP Client.
[0079] S1013: Send the target data to the second input method application through the remote desktop client using the first transmission protocol.
[0080] In one implementation, the first transmission protocol is Socket, and the second input method application is a Linux input method application, that is, any input method application that can be applied to a Linux system. When the second input method application is initialized, a ServerSocket is created, and a thread is started to loop on the ServerSocket to wait for a data sending event of a remote desktop client, that is, to wait for target data sent by the remote desktop client.
[0081] Specifically, the remote desktop client uses the Socket protocol to send target data to the second input method application. The Server Socket created by the second input method application cyclically waits for a data sending event, and when it is determined that there is a data sending event, receives the target data sent by the remote desktop client.
[0082] In this way, the target data in the Android system can be sent to the second input method application in the Linux system.
[0083] Step 102: In response to the second input method application receiving a virtual key event, the target data is sent to a target application; the target application is an application installed in the Linux system.
[0084] Specifically, the virtual key event is sent to the second input method application through the second transmission protocol. When the second input method receives the virtual key event, it sends the target data to the target application.
[0085] The target application is an application program installed in the Linux system, that is, a Linux application.
[0086] In one implementation, when sending a virtual key event to the second input method application, the following steps may be used:
[0087] S1021: Send a virtual key event to a target application through a remote desktop client using a second transmission protocol.
[0088] Specifically, when the remote desktop client determines to send the target data, it uses the second transmission protocol to send the virtual key event to the monitoring process in the Linux system. The monitoring process sends the virtual key event to the target application.
[0089] In one embodiment, the monitoring process is Weston. Weston is a process that integrates the graphics display protocol (Wayland) and the remote desktop protocol (Free RDP). Weston is used to monitor the Linux display service and send the display data of the Linux application to the Android application. The Android application, i.e., the remote desktop client, can also send virtual key events to the Linux application through Weston, using the Wayland protocol and the Free RDP protocol (i.e., the second transmission protocol).
[0090] It should be noted that the virtual key event is a pre-agreed exclusive event that can be recognized by Weston.
[0091] In this way, while sending the target data to the second input method application of the Linux system, the virtual key event can also be sent to the target application of the Linux system at the same time.
[0092] S1022: Sending the virtual key event to the second input method framework in the Linux system through the target application.
[0093] The second input method framework may be a Linux input method framework, that is, any input method framework applied in a Linux system.
[0094] S1023: Send the virtual key event to the second input method application through the second input method framework.
[0095] Specifically, after receiving the virtual key event, the target application sends the virtual key event to the second input method application through the second input method framework.
[0096] In one implementation, after the Linux system is started, the monitoring process and the second input method framework are preloaded, and the second input method framework will load the second input method application at the same time when it is started. As an example, after the Linux system is started, Weston and the Linux input method framework are preloaded. The Linux input method framework will load the Linux input method application at the same time when it is started. Specifically, the transmission paths of the virtual key events are as follows:
[0097] Weston->Linux application->Linux input method framework->Linux input method application.
[0098] In this way, the virtual key events can be forwarded layer by layer to the second input method application.
[0099] In one implementation, when the second input method receives a virtual key event, the following steps may be used when sending the target data to the target application:
[0100] The target data is sent to a second input method framework in the Linux system; and the target data is sent to a target application through the second input method framework.
[0101] That is, the reception of the virtual key event is used as an opportunity to trigger the second input method application to submit the target input to the target application (eg, WPS application) through the application programming interface (API) of the second input method framework.
[0102] Furthermore, the target data is displayed through the target application. After receiving the target data, the target application can also perform other application operations based on the target data, which is not limited here.
[0103] In the above embodiment, after the user inputs the target data through the first input method application of the Android system, on the one hand, the target data is sent to the second input method application in the Linux system through the first input method framework and the remote desktop client in sequence; on the other hand, while sending the target data, the remote desktop client also sends a virtual key event to the second input method application through the monitoring process, the target application and the second input method framework in sequence. If the second input method application receives the virtual key event, it takes this as an opportunity to submit the target data to the target application. In this way, in the Linux system installed in the virtual environment, it is not necessary to provide any human-machine interface (HMI). Only through a simple second input method application and a thread and channel for transmitting target data, the target data input by the first input method application in the Android system can be obtained, and the operation is relatively simple and the cost is low. Furthermore, the virtual key event is used as an opportunity for the second input method application to obtain data interacting with the target application, so that the target data input under the Android system can be transferred to the target application under the Linux system.
[0104] See also Figure 2 The following is a schematic diagram of the architecture of a data transmission system. Figure 2 The above data transmission method is illustrated. The data transmission system is installed with an Android system, and a Linux system is installed in a Linux container (Container), i.e., a virtual environment. An Android input method application, an Android input method framework, and an RDP Client are installed in the Android system. A Linux application, a Linux input method application, a Linux input method framework, and Weston are installed in the Linux system.
[0105] In one implementation, the Android input method application sends the target data input by the user to the RDP Client through the Android input method framework. The RDP Client sends the target data to the Linux input method application through the Socket protocol, and simultaneously sends the virtual key event to the Linux input method application through Weston, the Linux application, and the Linux input method framework in sequence. When the Linux input method application receives the virtual key event, it submits it to the Linux application. The Linux application can display the target data.
[0106] In this way, the target data input by the user through the Android input method application can be passed to the Linux application through communication cooperation between multiple processes, solving the problem that the Linux application under Linux cannot obtain the data input by the Android input method application under the Android system.
[0107] Based on the same inventive concept, a data transmission device is also provided in the embodiment of the present application. Since the principle of solving the problem by the above device and equipment is similar to that of a data transmission method, the implementation of the above device can refer to the implementation of the method, and the repeated parts will not be repeated. The device can be applied to electronic devices. The present application does not limit the type of electronic devices. It can be any type of device suitable for implementation, such as terminal devices and servers, etc., and the present application will not repeat them.
[0108] See also Figure 3 FIG. 1 is a block diagram of a data transmission device in an embodiment of the present application. In some implementations, the data transmission device in the present application example includes:
[0109] An acquisition unit 301 is used to acquire target data input by a user through a first input method application; the first input method application is installed in an Android system;
[0110] The first sending unit 302 is used to send the target data to the second input method application through the first transmission protocol; the second input method application is installed in the Linux system;
[0111] The second sending unit 303 is used to send the target data to the target application in response to the second input method application receiving the virtual key event; the target application is an application installed in the Linux system.
[0112] In one implementation, the first sending unit 302 is configured to:
[0113] Sending the target data to the first input method framework in the Android system through the first input method application;
[0114] The target data is sent to a remote desktop client through the first input method framework; the remote desktop client is a client installed on the Android system;
[0115] The target data is sent to the second input method application through the remote desktop client using the first transmission protocol.
[0116] In one implementation, the second sending unit 303 is further configured to:
[0117] Sending virtual key events to the target application through the remote desktop client using the second transmission protocol;
[0118] Sending virtual key events to the second input method framework in the Linux system through the target application;
[0119] The virtual key event is sent to the second input method application through the second input method framework.
[0120] In one implementation, the second sending unit 303 is further configured to:
[0121] When it is determined that the target data is to be sent, a virtual key event is sent to a listening process in the Linux system based on the second transmission protocol through the remote desktop client;
[0122] Send the target data to the virtual key event through the monitoring process.
[0123] In one implementation, the second sending unit 303 is used to:
[0124] Sending target data to the second input method framework in the Linux system;
[0125] The target data is sent to the target application through the second input method framework.
[0126] In one implementation, the second sending unit 303 is further configured to:
[0127] Display target data through target applications.
[0128] The data transmission method of the embodiment of the present application includes obtaining target data input by a user through a first input method application; the first input method application is installed in an Android system; the target data is sent to a second input method application through a first transmission protocol; the second input method application is installed in a Linux system; in response to the second input method application receiving a virtual key event, the target data is sent to a target application; the target application is an application installed in the Linux system. In this way, the problem of difficulty in transmitting user input data in an Android system to a Linux application is solved.
[0129] An embodiment of the present application provides an electronic device, including:
[0130] Processor; and
[0131] The memory stores computer instructions, where the computer instructions are used to enable the processor to execute the method of any of the above embodiments.
[0132] In an embodiment of the present application, a storage medium is provided, which stores computer instructions, and the computer instructions are used to enable a computer to execute a method in any of the above-mentioned embodiments.
[0133] Figure 4FIG. 4 is a schematic diagram showing the structure of an electronic device 4000. Figure 4 As shown, the electronic device 4000 includes: a processor 4010 and a memory 4020 , and optionally, may also include a power supply 4030 , a display unit 4040 , and an input unit 4050 .
[0134] Processor 4010 is the control center of electronic device 4000. It connects various components using various interfaces and lines, and performs various functions of electronic device 4000 by running or executing software programs and / or data stored in memory 4020, thereby monitoring electronic device 4000 as a whole.
[0135] In the embodiment of the present application, the processor 4010 executes the various steps in the above embodiment when calling the computer program stored in the memory 4020.
[0136] Optionally, the processor 4010 may include one or more processing units; preferably, the processor 4010 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and applications, and the modem processor mainly processes wireless communications. It is understandable that the modem processor may not be integrated into the processor 4010. In some embodiments, the processor and the memory may be implemented on a single chip, and in some embodiments, they may also be implemented separately on separate chips.
[0137] The memory 4020 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, various applications, etc.; the data storage area may store data created according to the use of the electronic device 4000, etc. In addition, the memory 4020 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices, etc.
[0138] The electronic device 4000 also includes a power source 4030 (such as a battery) for supplying power to various components. The power source can be logically connected to the processor 4010 through a power management system, thereby managing functions such as charging, discharging, and power consumption through the power management system.
[0139] The display unit 4040 may be used to display information input by the user or information provided to the user and various menus of the electronic device 4000, and in the embodiment of the present application, is mainly used to display the display interface of each application in the electronic device 4000 and objects such as text and pictures displayed in the display interface. The display unit 4040 may include a display panel 4041. The display panel 4041 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.
[0140] The input unit 4050 may be used to receive information such as numbers or characters input by the user. The input unit 4050 may include a touch panel 4051 and other input devices 4052. The touch panel 4051, also known as a touch screen, may collect touch operations of the user on or near it (such as operations of the user using a finger, a stylus, or any other suitable object or accessory on or near the touch panel 4051).
[0141] Specifically, the touch panel 4051 can detect the user's touch operation, detect the signal brought by the touch operation, convert these signals into touch point coordinates, send them to the processor 4010, and receive and execute the command sent by the processor 4010. In addition, the touch panel 4051 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. Other input devices 4052 can include but are not limited to one or more of a physical keyboard, function keys (such as volume control keys, power on / off keys, etc.), a trackball, a mouse, a joystick, etc.
[0142] Of course, the touch panel 4051 can cover the display panel 4041. When the touch panel 4051 detects a touch operation on or near it, it is transmitted to the processor 4010 to determine the type of touch event, and then the processor 4010 provides corresponding visual output on the display panel 4041 according to the type of touch event. Figure 4 In the embodiment, the touch panel 4051 and the display panel 4041 are used as two independent components to realize the input and output functions of the electronic device 4000, but in some embodiments, the touch panel 4051 and the display panel 4041 can be integrated to realize the input and output functions of the electronic device 4000.
[0143] The electronic device 4000 may also include one or more sensors, such as a pressure sensor, a gravity acceleration sensor, a proximity light sensor, etc. Of course, according to the needs of specific applications, the electronic device 4000 may also include other components such as a camera. Since these components are not the key components used in the embodiments of the present application, Figure 4It is not shown and will not be described in detail.
[0144] Those skilled in the art will understand that Figure 4 The electronic device is merely an example and does not limit the electronic device, and may include more or less components than those shown in the figure, or may combine certain components, or may include different components.
[0145] For the convenience of description, the above parts are divided into modules (or units) according to their functions and described separately. Of course, when implementing this application, the functions of each module (or unit) can be implemented in the same or multiple software or hardware.
[0146] Obviously, the above embodiments are merely examples for the purpose of clear explanation, and are not intended to limit the embodiments. For those skilled in the art, other different forms of changes or modifications can be made based on the above description. It is not necessary and impossible to list all the embodiments here. The obvious changes or modifications derived therefrom are still within the scope of protection created by this application.
Claims
1. A method for data transmission, characterized in that: Applied to an electronic device, the electronic device is respectively installed with an Android system and a Linux system, the Android system is installed in a local environment of the electronic device, and the Linux system is installed in a virtual environment of the electronic device, the method comprises: Acquire target data input by a user through a first input method application; the first input method application is installed in the Android system; Sending the target data to a second input method application via a first transmission protocol; the second input method application is installed in the Linux system; In response to the second input method application receiving a virtual key event, the target data is sent to a target application; the target application is an application installed in the Linux system.
2. The method according to claim 1, characterized in that The step of sending the target data to the second input method application via the first transmission protocol includes: Sending the target data to a first input method framework in the Android system through the first input method application; The target data is sent to a remote desktop client through the first input method framework; the remote desktop client is a client installed on the Android system; The target data is sent to the second input method application through the remote desktop client using the first transmission protocol.
3. The method according to claim 2, characterized in that The method further comprises: Sending the virtual key event to the target application through the remote desktop client using the second transmission protocol; Sending the virtual key event to a second input method framework in the Linux system through the target application; The virtual key event is sent to the second input method application through the second input method framework.
4. The method according to claim 3, characterized in that The sending the virtual key event to the target application by using the second transmission protocol through the remote desktop client includes: When determining to send the target data through the remote desktop client, sending the virtual key event to the listening process in the Linux system based on the second transmission protocol; The target data is sent to the virtual key event through the monitoring process.
5. The method according to any one of claims 1 to 4, characterized in that: The sending the target data to the target application includes: Sending the target data to a second input method framework in the Linux system; The target data is sent to the target application through the second input method framework.
6. The method according to any one of claims 1 to 4, characterized in that: The method further comprises: The target data is displayed through the target application.
7. A data transmission device, characterized in that: Applied to an electronic device, the electronic device is respectively installed with an Android system and a Linux system, the Android system is installed in a local environment of the electronic device, and the Linux system is installed in a virtual environment of the electronic device, the device comprises: An acquisition unit, configured to acquire target data input by a user through a first input method application; the first input method application is installed in the Android system; A first sending unit is used to send the target data to a second input method application through a first transmission protocol; the second input method application is installed in the Linux system; The second sending unit is used to send the target data to a target application in response to the second input method application receiving a virtual key event; the target application is an application installed in the Linux system.
8. The device according to claim 7, characterized in that The first sending unit is used for: Sending the target data to a first input method framework in the Android system through the first input method application; Sending the target data to a remote desktop client via the first input method framework; The remote desktop client is a client installed on the Android system; The target data is sent to the second input method application through the remote desktop client using the first transmission protocol.
9. The device according to claim 8, characterized in that The second sending unit is further used for: Sending the virtual key event to the target application through the remote desktop client using the second transmission protocol; Sending the virtual key event to a second input method framework in the Linux system through the target application; The virtual key event is sent to the second input method application through the second input method framework.
10. The device according to claim 9, characterized in that The second sending unit is further used for: When determining to send the target data through the remote desktop client, sending the virtual key event to the listening process in the Linux system based on the second transmission protocol; The target data is sent to the virtual key event through the monitoring process.
11. The device according to any one of claims 7 to 9, characterized in that: The second sending unit is used for: Sending the target data to a second input method framework in the Linux system; The target data is sent to the target application through the second input method framework.
12. The device according to any one of claims 7 to 9, characterized in that: The second sending unit is further used for: The target data is displayed through the target application.
13. An electronic device, characterized in that: include: processor; as well as A memory storing computer instructions, wherein the computer instructions are used to enable the processor to execute the method according to any one of claims 1 to 6.
14. A storage medium, characterized in that: Computer instructions are stored, and the computer instructions are used to make a computer execute the method according to any one of claims 1 to 6.