WO2014205765A1

WO2014205765A1 - Method for automatic installation and synchronization of software between android intelligent devices

Info

Publication number: WO2014205765A1
Application number: PCT/CN2013/078327
Authority: WO
Inventors: 翁杰军
Original assignee: 深圳市掌讯通讯设备有限公司
Priority date: 2013-06-28
Filing date: 2013-06-28
Publication date: 2014-12-31

Abstract

The present invention relates to a method for automatic installation and synchronization of software between Android intelligent devices by using a master device starting USB-OTG and a slave device running an adbd process. The method comprises: 101) the master device detecting whether a USB device is accessed, if yes, entering 102), otherwise, returning to 101); 102) starting an adb service; 103) calling a shell command in the adb to access a specified file ; 104) determining whether the access succeeds, if yes, entering 105), otherwise, entering 108); 105) calling the shell command in the adb to send a specified APK to the slave device for software installation; 106) the slave device executing the install shell command, if software is installed, the slave device withdrawing and sending an installation response to the master device, otherwise, continuing to execute the installation, and sending installation success or installation failure information to the master device; 107) the master device prompting a user about whether installation is performed or a result of installation success/installation failure; and 108) ending.

Description

Title of Invention: An Automatic Installation and Synchronization Method for Software between Android Intelligent Devices

[1] The present invention relates to automatic installation of computer software, and particularly relates to a software automatic installation and synchronization method between Android (Intel) smart devices, especially between a smart car system and a mobile phone/tablet. Background technique

[2] Existing Android smart device installation software and application installation technology generally use network connection computer (

PC), and other possible ways to install the software via the Android installation package (APK). There are some drawbacks in these installation methods: Users need to install the same software or application on other Android smart devices, and must be installed once; and when the user reinstalls the main operating system, or the currently installed software is destroyed by skill , you need to manually restart the software installer to install the software.

[3] The software installation process is somewhat simple for the average user, some are very complex, and require network or traffic consumption. Incorrect operation may result in the software not being installed properly, or the software may not work properly given the correct configuration. For software vendors and hardware vendors, the cost of supporting software installation and maintenance is quite high, and installation errors can affect user satisfaction with the installed software.

[4] Through the above description, the current installation method can not solve the following needs:

[5] 1) Users have multiple Android smart devices, which need to use the same application simply;

[6] 2) Users use the same application on multiple Android smart devices, and need to maintain consistent software settings;

[7] 3) Users using the same application on multiple Android smart devices need to use the same data source, such as:

MP3 audio files, MP4 video files. On the one hand, they need to be downloaded repeatedly; in the second aspect, after interrupting the application on one device and then switching to other devices, it is difficult to connect; there are some Android smart devices, such as: Intelligent in-vehicle system, generally using 2nd generation mobile communication ( 3G) Network, it is difficult to use wireless LAN (wifi), and downloading MP3 audio files, MP4 video files, huge traffic, limiting their application in intelligent vehicle systems. In order to save traffic, the traditional method is complicated and requires the user to master certain basic skills, so it is difficult to promote. The mobile phone companion of the intelligent in-vehicle system proposed by the applicant in the present invention successfully solves a series of problems including the above technical problems, so that the mobile phone can conveniently enjoy the peers of the vehicle application, save the flow and use the car audio to play high quality music. And video, at home, set the car on the phone, save driving time and improve safety and driving performance.

Disclosure of invention

technical problem

The technical problem to be solved by the present invention is how to provide an automatic installation and synchronization method for software between Android smart devices, which can automatically install existing applications to other Android smart devices, and further synchronize user settings and control between them, and further Can use data synchronously to save traffic.

Problem solution

Technical solution

The above technical problem of the present invention is solved as follows: Build a software automatic installation and synchronization method between Android smart devices, which is characterized in that a master device that turns on USB-OTG (On-Th _e- Go, a USB docking standard) and The slave device running the Android Debug Bridge (ADB) background process (adbd process) includes the following specific steps:

101) Does the master detect its own USB port for device access? Yes, proceed to step 102), otherwise return to step 101);

102) The master device starts the adb service;

103) The master device invokes the adb internal shell command to access the specified file that exists in all slave devices; 104) The master device determines whether the access is successful? If yes, go to step 105), otherwise, prompt the user to go to step 108) or do not prompt to go directly to step 108);

105) The master device calls adb's internal 'install' shell command to send the specified APK to the slave device for software installation;

106) Execute the 'install' shell command from the device. If the APK is installed in its own Android system, exit the APK installation and send the installed response directly to the master device; otherwise continue to install the APK and install successfully. Or failure information is sent to the master device;

107) The master device prompts the user whether to install or install the success/failure result;

108) End. [19] The method for automatically installing and synchronizing software between Android smart devices according to the present invention, between steps 101) and 102), further includes:

[20] 201 ) Check if the USB-OTG function is turned on normally? Go to step 102), otherwise go to step 202);

[21] 202) Switch and turn on the USB-OTG function: If it is normally open, go to step 202); if it fails or fails several times, it will prompt that it cannot be installed, ie: The master device that does not support USB-OTG function cannot start the invention Automatic program installation method.

[22] According to the present invention, the Android smart device software automatic installation and synchronization method, in step 103), the adb internal shell command includes 'cat', 'pull' or 'push'.

[23] According to the present invention, the Android smart device software automatic installation and synchronization method, in step 104), prompts the user to include, but is not limited to, prompting the user to check whether the USB connection is unblocked or prompting the user to check whether the slave device adbd process is enabled.

[24] According to the present invention, the Android smart device software automatic installation and synchronization method, in step 105), specifies one or more APKs.

[25] The method for automatically installing and synchronizing software between Android smart devices according to the present invention, step 101)

Between 102) also includes:

[26] 601) The user selects whether to install or install a software application through the master device;

[27] 602) If the user chooses not to install, go directly to step 108), otherwise repeat steps 105), 106) and 107) one by one according to the number of software applications selected by the user.

[28] The method for automatically installing and synchronizing software between Android smart devices according to the present invention further includes the following specific steps after step 104):

[29] 701) The user selects whether to synchronize data or data to be synchronized through the master device;

[30] 702) If the user chooses not to synchronize, exit directly, otherwise the master device calls the adb internal read/transmit shell command to obtain the specified synchronization list file from the slave device;

[31] 703) The master device compares the acquired slave synchronization list file with the corresponding synchronization list file to generate a synchronization list;

[32] 704) The master device calls the adb internal write I transfer shell command one by one according to each file in the synchronization list to write data on the master device to the slave device, or calls the adb read/transmit shell command to write data from the device. Enter Master device.

[33] If the sync list file is missing or corrupted, a full sync is performed.

[34] According to the present invention, an Android smart device software automatic installation and synchronization method is provided, the data including user setting data in a software application.

[35] According to the present invention, an Android smart device software automatic installation and synchronization method is provided, the data including an audio file or a video file.

[36] The above technical problem of the present invention can also be solved as follows: A method for automatically installing and synchronizing software between in-vehicle Android smart devices is constructed, which is characterized in that it comprises the following specific steps:

[37] 1001) Does the master detect its own USB port for device access? Yes, proceed to step 1002), otherwise return to step 1001);

[38] 1002) Check if the USB-OTG function is turned on normally? Go to step 1003), otherwise go to step 1003);

[39] 1003) The master device starts the adb service;

[40] 1004) The master device invokes the adb internal shell command to access all specified files that exist in the slave device; [41] 1005) Does the master device determine whether the access is successful? If yes, go to step 1006), otherwise, prompt the user to go to step 1013) or do not prompt to go directly to step 1013);

[42] 1006) The master device calls the adb internal 'install' shell command to send the specified APK to the slave device for software installation;

[43] 1007) Execute the 'install' shell command from the device. If the APK is already installed in its own Android system, exit the APK installation and send the installed response directly to the master device; otherwise continue to install the APK, and Send the installation success or failure information to the master device;

[44] 1008) The master device receives the installed response sent by the slave device, or the installation success or failure information, if it is the installation success or failure information, the user is prompted to proceed to step 1013); if the response is installed, proceed to step 1009. ) ;

[45] 1009) Does the user choose to synchronize data through the master device? If yes, go to step 1010), otherwise exit to the step; the data includes user setting data in the software application;

[46] 1010) The master device calls the adb internal read I transport shell command to obtain the specified sync list file from the slave device; [47] 1011) The master device compares the acquired slave synchronization list file with the corresponding synchronization list file to generate a synchronization list;

[48] 1012) The master device calls the adb internal write I transfer shell command one by one according to each file in the synchronization list to write the data on the master device to the slave device, or calls the adb read/transmit shell command to acquire the data on the slave device and Write to the master device;

[49] 1013) End.

Advantageous effects of the invention

Beneficial effect

[50] The method for automatically installing and synchronizing software between Android smart devices provided by the present invention has the following advantages over the prior art:

[51] 1. Only need USB connection, it can automatically install the same application in other Android smart devices, no need to find and download on the network;

[52] 2, only need to take the time to define the software application settings and control on the mobile phone, through the USB connection and data synchronization, directly complete the setting of other Android smart devices, without wasting the user in a limited environment;

[53] 3, only need to borrow other Android smart devices that are convenient for WIFI to download data, obtain huge files or data through USB connection and data synchronization, save users 3G traffic, and promote various applications. Brief description of the drawing

DRAWINGS

[54] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments:

1 is a schematic diagram showing the architecture of an interconnection control model of an intelligent in-vehicle system and a mobile phone according to the present invention;

[56] FIG. 2 is a schematic diagram of an automatic program installation process corresponding to FIG. 1;

[57] FIG. 3 is a schematic diagram of a data synchronization process corresponding to FIG. 1;

[58] FIG. 4 is a schematic diagram of the control flow of the sync extension command used in FIG.

BEST MODE FOR CARRYING OUT THE INVENTION

[59] The automatic installation and synchronization method of the software between the Android smart devices of the invention is implemented in the intelligent vehicle system and the mobile phone I Between tablets, the smart car system automatically installs the phone companion program on the phone/tablet and enables data synchronization.

[60] As shown in FIG. 1 , the interconnection between the intelligent in-vehicle system and the mobile phone of the present invention is based on USB connection control, and the intelligent in-vehicle system is the main device, and the USB-OTG function needs to be supported and turned on, the adb service is started, and the adb shell is called by the adb service. Command, package/unpacking via protocol layer and underlying driver, connection control slave device: mobile phone, mobile terminal needs to run adbd process.

[61] As shown in FIG. 2, the master device (intelligent vehicle system) of the present invention automatically installs a control program to the slave device (mobile phone), and specifically includes the following steps:

[62] 2001) begins;

[63] 2002) Does the master detect its own USB port for device access? Yes, go to step 2003), otherwise go back to step 2002);

[64] 2003 ) Check if the USB-OTG function is turned on normally? Is to enter step 2004), otherwise open to step 2004);

[65] 2004) The master device starts the adb service;

[66] 2005) The master device calls the adb internal cat/pull/push shell command to access all the specified files that exist in the slave device; the specified file may be an Android system or a user core file;

[67] 2006) Does the master judge whether the access is successful? Yes, go to step 2007), otherwise prompt the user to enter step 2010) or do not prompt to go directly to step 2010);

[68] 2007 ) Prompt and receive user selection input? If you choose to install the car phone companion software, go to step 2008), if you choose not to install, exit, go to step 2010);

[69] 2008 ) The master device calls the adb internal 'install' shell command to send the mobile companion APK to the slave device for software installation;

[70] 2009 ) From the device execute the ' install ' shell command, if the mobile companion program is installed in its own Android system, exit the installation of the mobile phone companion APK and send the installed response directly to the main device; otherwise continue to execute the mobile phone companion APK Install, and send the installation success or failure information to the master device; the master device receives the response or information sent by the slave device, if it is the installation success or failure information, the user is prompted to successfully install or fail; if the response is installed, the prompt The user has already installed the app;

[71] 2010 ) End. [72] As shown in FIG. 3, the automatic data synchronization control program of the master device (intelligent vehicle system) and the slave device (mobile phone) of the present invention specifically includes the following steps:

[73] 3001) Start;

[74] 3002) Does the master detect its own USB port for device access? Yes, proceed to step 3003), otherwise return to step 3002);

[75] 2003 ) Check if the USB-OTG function is turned on normally? Go to step 3004), otherwise go to step 3004);

[76] 3004) The master device starts the adb service;

[77] 3005) The master device calls the adb internal cat/pull/push shell command to access the specified files that exist in all the slave devices; the specified file may be an Android system or a user core file;

[78] 3006) The master device determines whether the access is successful? If yes, go to step 3007), otherwise the user is prompted to go to step 3009) or not to go directly to step 3009);

[79] 3007) Prompt and receive user input input? If the synchronization data is selected, proceed to step 3008), if the selection is not synchronized, exit, and proceed to step 3009);

[80] 3008) The master device invokes the custom adb extension command 'sync' in the present invention to synchronize data with the slave device;

[81] 3009) End.

[82] As shown in FIG. 4, the custom adb extension command 'sync' of the present invention specifically includes the following steps: [83] 4001) Start;

[84] 4002) The master device calls the adb cat/pull command to read the slave device synchronization list file;

[85] 4003) Is it successful to read? Yes, go to step 4004), otherwise go to step 4006)

[86] 4004) The slave device synchronization list file obtained by the master device compares with the corresponding synchronization list file to generate a synchronization list; if the slave device synchronization list file is lost or damaged, all data in the synchronization slave device is set according to the master device;

[87] 4005) The master device calls the adb internal push shell command one by one to write the data on the master device to the slave device, or calls the adb cat/pull shell command to obtain the data on the slave device and write it to the master device. ; the files in the synchronization list are all executed and proceed to step 4007);

[88] 4006) The master device calls the cat/pull shell command in the adb to get the specified location or directory from the slave device. All data I specifies data and writes to the master device;

[89] 4007) End.

[90] The synchronized data is mainly MP3 files, MP4 files, and software setting data.

[91] Of course, the above description is only a preferred embodiment of the present invention, and equivalent changes or modifications made to the structures, features, and processes described in the scope of the present patent application are included in the patent application of the present invention. Within the range

Embodiments of the invention

[92] The method for automatically installing and synchronizing software between Android smart devices provided by the present invention can also be applied between a mobile phone and a mobile phone, between a mobile phone and a tablet computer, between a tablet computer and an in-vehicle device, and the like.

Industrial applicability

[93] The method for automatically installing and synchronizing software between Android smart devices provided by the present invention is more direct, simple and greatly reduces the outstanding advantages of repetitive work than the prior art, and has no additional network or server requirements, especially for users. use.

Sequence table free content

Claims

claims

[Claim 1] A method for automatic software installation and synchronization between Android smart devices, characterized by using a master device that turns on USB-OTG and a slave device that runs the adbd process, including the following specific steps:

101) The main device detects whether there is a device connected to its USB port? Yes, proceed to the steps

102), otherwise return to step 101);

102) The main device starts the adb service;

103) The master device calls the adb internal shell command to access the specified files that exist in all slave devices;

104) Does the master device determine whether the access is successful? If yes, go to step 105), otherwise prompt the user and go to step 108) or go directly to step 108) without prompting; 105) The master device calls the adb internal 'install' shell command to send the specified APK to the slave device for software installation;

106) Execute the 'install' shell command from the device. If the APK has been installed in its own Android system, exit the installation of the APK and send the installed response directly to the main device; otherwise, continue the installation of the APK and the installation will be successful. Or failure information is sent to the main device;

107) The main device prompts the user whether to install or the installation is successful/failed;

108) End.

[Claim 2] The automatic software installation and synchronization method according to claim 1, characterized in that, between steps 101) and 102), it also includes:

201) Check whether the USB-OTG function is turned on normally? If yes, go to step 102); otherwise, go to step 202);

202) Switch and turn on the USB-OTG function: If it is turned on normally, go to step 202); if it fails or fails multiple times, it will prompt that the installation cannot be performed.

[Claim 3] The automatic software installation and synchronization method according to claim 1, characterized in that:

103) Medium adb internal shell commands include 'cat', 'pull' or 'push'.

[Claim 4] The automatic software installation and synchronization method according to claim 1, characterized in that: 104) The prompts for the user include checking whether the USB connection is smooth or checking whether the adbd process of the slave device is open.

The software automatic installation and synchronization method according to claim 1, characterized in that:

105) The APK specified in is one or more.

The automatic software installation and synchronization method between Android smart devices according to claim 5, characterized in that, between steps 101) and 102), it also includes:

601) The user chooses whether to install or the software applications that need to be installed through the main device;

602) If the user chooses not to install, exit directly and enter step 108), otherwise, repeat steps 105), 106 and 107) one by one according to the number of software applications selected by the user.

The automatic software installation and synchronization method according to claim 1, characterized in that, after step 104), the following specific steps are also included:

701) The user chooses whether to synchronize data or the data to be synchronized through the main device;

702) If the user chooses not to synchronize, exit directly, otherwise the master device calls the adb internal read/transmit shell command to obtain the specified synchronization list file from the slave device;

703) The master device compares the synchronization list file obtained from the slave device with its own corresponding synchronization list file to generate a synchronization list;

704) The master device calls the adb internal write/transfer shell command one by one for each file in the synchronization list to write the data on the master device to the slave device, or calls the adb read/transfer shell command to write the data from the device to the master device. .

The automatic software installation and synchronization method according to claim 7, wherein the data includes user setting data in the software application.

The automatic software installation and synchronization method according to claim 7, wherein the data includes audio files or video files.

A method for automatic installation and synchronization of software between in-vehicle Android smart devices, which is characterized by including the following specific steps:

1001) The main device detects whether there is a device connected to its USB port? If yes, go to step 1002), otherwise return to step 1001);

1002) Check whether the USB-OTG function is turned on normally? Yes, proceed to step 1003), No Then open and enter step 1003);

1003) The main device starts the adb service;

1004) The master device calls the adb internal shell command to access the specified files that exist in all slave devices;

1005) Does the main device determine whether the access is successful? If yes, go to step 1006), otherwise prompt the user and then go to step 1013) or go directly to step 1013) without prompting;

1006) The master device calls the adb internal 'install' shell command to send the specified APK to the slave device for software installation;

1007) Execute the 'install' shell command from the device. If the APK has been installed in its own Android system, exit the installation of the APK and send the installed response directly to the main device; otherwise, continue the installation of the APK and the installation will be successful. Or failure information is sent to the main device;

1008) The master device receives the installed response sent from the slave device, or the installation success or failure information. If it is the installation success or failure information, it will prompt the user and then go to step 101 3); if it is the installed response, go to step 1009);

1009) Does the user choose whether to synchronize data through the main device? Yes, go to step 1010)

, otherwise exit the entry step; the data includes user setting data in the software application

1010) The master device calls the adb internal read/transmit shell command to obtain the specified synchronization list file from the slave device;

1011) The master device compares the synchronization list file obtained from the slave device with its own corresponding synchronization list file to generate a synchronization list;

1012) The master device calls the adb internal write/transfer shell command one by one for each file in the synchronization list to write the data on the master device to the slave device, or calls the read/transfer shell command in adb to obtain the data on the slave device and write it to the master device. equipment;

1013) End.