properties.local Configuration¶

The properties.local file is the system configuration file for the FIRERPA service, typically stored on the device. It contains strings in the key=value format. By editing this file, you can configure FIRERPA to automatically connect to OpenVPN, a proxy, or port forwarding on startup, as well as set a login password or certificate, and other system configurations. When FIRERPA starts, it looks for and loads this file from /data/usr. You can find configurable items in the project's properties.local.example and select them as needed. However, please do not copy this file directly; only include the parts you require.

Attention

The `/data/usr` directory is FIRERPA's user data directory and does not exist before the first startup. If you need to pre-configure `properties.local`, you must create this directory manually.

Instructions on how to write the properties.local startup configuration are also provided in the documentation for each feature. You can also refer to properties.local.example.

Configuration Parameter List¶

Core Basic Configuration¶

Configures the basic operating environment for the LAMDA service, including listening port, authentication, login credentials, and cross-origin policy settings.

Parameter Name	Default Value	Example Value	Introduced	Removed	Description
`port`	`65000`	`65000`	-	-	The default listening port for the LAMDA service.
`brandname`	`FIRERPA`	`LAMDA-DEV`	-	-	Device name displayed on the remote desktop (up to 10 characters).
`cert`	None	`TEFNREEg...`	-	-	Base64 encoded certificate for TLS encryption and authentication.
`ssl-web-credential`	None	`pwd123`	-	-	Backup password for remote desktop login (6-32 characters).
`allow_origin`	None	`https://a.com`	-	-	Sets the CORS header to allow WebUI embedding.
`logfile`	None	`/data/log.txt`	-	-	Path to store the log file (the directory must be created in advance).

System Optimization and Compatibility¶

Controls underlying business logic and stealth strategies to enhance automation operations or to make fallback adjustments when compatibility issues arise on the device.

Parameter Name	Default Value	Example Value	Introduced	Removed	Description
`disable-client-api`	`false`	`true`	-	-	Disables the Python client API. Set to `true` if the device crashes.
`enhanced-stealth-mode`	`false`	`true`	7.65	-	Enhanced stealth mode to prevent components from being detected.
`enhanced-automation`	`false`	`true`	-	-	Enables enhanced automation support.
`touch.backend`	`native`	`system`	-	-	Touch backend: `system` (fixes offset) or `native` (default).
`intercept-intent`	`false`	`true`	8.20	-	Enables the Intent interception feature (get_last_activities).

OpenVPN Service¶

Built-in OpenVPN client configuration that enables the device to communicate through a VPN tunnel, supporting global traffic forwarding and user authentication.

Parameter Name	Default Value	Example Value	Introduced	Removed	Description
`openvpn.enable`	`false`	`true`	-	-	Enables the built-in OpenVPN service.
`openvpn.global`	`false`	`false`	-	-	Enables global VPN traffic forwarding.
`openvpn.proto`	`udp`	`udp`	-	-	VPN communication protocol.
`openvpn.cipher`	`AES-256-GCM`	`AES-256-GCM`	-	-	Encryption algorithm.
`openvpn.host`	None	`123.123.123.123`	-	-	OpenVPN server address.
`openvpn.port`	None	`1190`	-	-	OpenVPN server port.
`openvpn.ca`	None	`LS0t...`	-	-	Base64 encoded CA certificate.
`openvpn.cert`	None	`LS0t...`	-	-	Base64 encoded client certificate.
`openvpn.key`	None	`LS0t...`	-	-	Base64 encoded client key.

Global Proxy Service¶

Configures LAMDA to automatically connect to an HTTP or SOCKS5 proxy on startup, allowing device traffic to be automatically relayed through a specified intermediate server.

Parameter Name	Default Value	Example Value	Introduced	Removed	Description
`gproxy.enable`	`false`	`true`	-	-	Automatically connects to the proxy on startup.
`gproxy.type`	None	`http-connect`	-	-	Proxy type: `http-connect` or `socks5`.
`gproxy.host`	None	`172.1.1.1`	-	-	Proxy server address.
`gproxy.port`	None	`8080`	-	-	Proxy server port.
`gproxy.login`	None	`admin`	-	-	Proxy login username.
`gproxy.password`	None	`pwd123`	-	-	Proxy login password.

FRP Port Forwarding Service¶

Based on FRP for NAT traversal, this service maps the device's service port to a public server, solving remote access issues in environments without a public IP address.

Parameter Name	Default Value	Example Value	Introduced	Removed	Description
`fwd.enable`	`false`	`true`	-	-	Enables the FRP forwarding service.
`fwd.host`	None	`123.123.123.123`	-	-	FRP server address.
`fwd.port`	None	`9911`	-	-	FRP server control port.
`fwd.protocol`	`tcp`	`tcp`	-	-	Forwarding protocol type.
`fwd.token`	None	`abc123`	-	-	FRP login authentication token.
`fwd.rport`	`0`	`10086`	-	-	Remote forwarding port (0 for random).

Development and Management Services¶

Provides toggles for common system management tools, including the ADB service, SSH for remote shell access, and scheduled task management.

Parameter Name	Default Value	Example Value	Introduced	Removed	Description
`adb.enable`	`true`	`true`	-	-	Enables the built-in ADB service.
`adb.directory`	`/data/local/tmp`	`/data/local/tmp`	-	-	ADB working directory.
`adb.privileged`	`false`	`true`	-	-	Enables Root privileges (otherwise, shell privileges).
`sshd.enable`	`true`	`true`	-	-	Enables the SSH service.
`cron.enable`	`true`	`true`	-	-	Enables the scheduled task service.

Bridge Proxy Service¶

An advanced network proxy mode that allows traffic bridging through a specific network interface (e.g., mobile data network). It enables internet access via the device's network as a proxy and supports user authentication.

Parameter Name	Default Value	Example Value	Introduced	Removed	Description
`tunnel2.enable`	`false`	`true`	-	-	Enables the bridge proxy service.
`tunnel2.login`	None	`lamda`	-	-	Bridge proxy username.
`tunnel2.password`	None	`1234`	-	-	Bridge proxy password.
`tunnel2.iface`	None	`rmnet`	-	-	Outgoing network interface: `rmnet` (mobile data) or `wlan` (WiFi).

Broadcast Discovery Service¶

An automatic device discovery service based on the mDNS protocol. When enabled, it allows for quick location and identification of LAMDA devices on the local network via domain names or metadata.

Parameter Name	Default Value	Example Value	Introduced	Removed	Description
`mdns.enable`	`false`	`false`	-	-	Enables mDNS broadcast discovery.
`mdns.meta`	`false`	`true`	-	-	Broadcasts device metadata (model, ID, etc.).
`mdns.name`	None	`LAMDA.local`	-	-	Custom local broadcast name.
`mdns.service`	`lamda`	`lamda`	-	-	The name of the broadcast service.