Compiling creates an executable that installs the agent in silent mode. The executable can be loaded on the device with any of these methods:
Compiling generates two APK vectors (Android Application Package File):
The installation procedure is provided below:
Step | Action |
---|---|
1 |
Enable the Unknown origins option in the device settings (typically under Settings, Applications ). The option can be disabled after installation. NOTE: if this option is not enabled, a request to authorize an application not in the Android Market appears during installation. |
2 |
Device root privileges must be obtained if the vector includes Screenshot, Chat and Messages modules. See "What you should know about Android" |
3 |
Run the appropriate APK vector on the selected device. |
4 |
During APK vector installation, accept the permissions requested by the agent. |
5 |
For Android 3.x and 4.x, click Open to start the vector, otherwise the vector will not be installed. IMPORTANT: the default APK vector for Android 3.x and 4.x appears as a normal application called DeviceInfo, that displays device information. |
6 |
A request to obtain root privileges could appear when the vector is running if the Require Administrative Privilege option was enabled. |
Compiling a factory with the Installation Package vector for Windows Phone operating system creates .zip FactoryName_winphone_silent.zip in folder RCS Download that contains two files:
IMPORTANT: in order for compiling to be successfully completed, follow the procedure to load the necessary files in RCS. See "Installation Package preparation for Windows Phone"
The MyPhoneInfo application, used to install the agent, is included in the packet with .xap applications. Installation does not require phone unlock.
.xap and .aetx files can be sent to the target device:
For installation via web, the Web service must correctly support the MIME types for the.xap and .aetx files; the following instructions must be found in the mime.types files:
Run the following procedure for both modes:
Step | Action |
---|---|
1 |
Open file ApplicationName.aetx. IMPORTANT: this is the certificate that must always be opened first. |
2 |
Answer the displayed questions by clicking Add. |
3 |
Open file ApplicationName.xap. |
4 |
Answer the displayed questions by clicking Install: the MyPhoneInfo application will be installed on the phone. |
5 |
From the application list, open the MyPhoneInfo application at least once. |
6 |
Close MyPhoneInfo: the agent is ready. IMPORTANT: if you exit the application without closing it, the application, and thus the agent, are suspended. The agent only starts when the application is closed or the phone is turned back on. |
The agent communications with the RCS server if and as long as the MyPhoneInfo application is installed on the device and the device is on. If a mobile data connection is not available, the agent can only communicate with the RCS server when the user uses the phone or the phone is connected to a computer or battery charger.
NOTE: when the device is turned on, it takes 30 minutes for the agent to restore communications with the RCS server. The 30 minutes are guaranteed if mobile data and Wi-Fi connections are running on the device. Otherwise, it could take longer.
An existing CAB installer can be specified to which the agent will be added.
If a CAB is not specified, the system will use a default, dummy CAB.
To allow the agent to be downloaded on a BlackBerry, extract the created zip file on a web server the device can access.
NOTE: the web server must correctly support the MIME types for .jad and .cod files, .text/vnd.sun.j2me.app-descriptor and application/vnd.rim.cod. respectively. The Collector public folder automatically runs this function.
Once the installer is run on the device, accept the permissions requested by the agent.
IMPORTANT: the certificate is required for Symbian.
Name | Description |
---|---|
Application name |
Application name (visible to target) |
User interaction request |
(Android only) If automatic acquisition fails, this option enables the user request to manually obtain root privileges from the device. WARNING: the request is displayed on the target device. |
Name | Description |
---|---|
Application name | Installer name (visible to target) |
Name | (BlackBerry only) Application data used to "hide" the agent. |
Description | |
Vendor | |
Release |
Name | Description |
---|---|
Application name | Application name (visible to target) |
Certificate tied to IMEI | Device certificate. |
Key tied to the certificate | Certificate key. |
S60 Edition | Operating system version. |
Symbian configuration |
Parameters:
|
RCS9.4 | User's Guide | © COPYRIGHT 2014