Skip to content

build: camex 4.0.0 in the tunnel (2.24.2) - #279

Merged
compot-dev merged 1 commit into
v2from
build/camex-4.0.0
Nov 17, 2026
Merged

compot-dev merged 1 commit into
v2from
build/camex-4.0.0

Conversation

@compot-dev

Copy link
Copy Markdown
Collaborator

Moves bundles/camex to camex 4.0.0 (OpenIPC/camex#179, 0712dcb).

  • The Android library has no changes; libcamex.so is rebuilt from the new shared C sources, so this is a PATCH release (2.24.2).
  • A camex 4.0.0 server listens for UDP and TCP on one port by default (--transport both); Decoder's client still uses UDP unless TCP is chosen in Network.
  • README (en/ru/zh-CN) names camex 4.0.0; CHANGELOG has a 2.24.2 section.

Checked locally in compot/android:2026.10: testDebugUnitTest lintDebug assembleDebug; tests/e2e.sh on API 34 and 21 against a 4.0.0 server (no --transport, so both): 14 passed, 0 failed each.

bundles/camex 4c2626f -> 0712dcb (camex 4.0.0, OpenIPC/camex#179): the server takes UDP and
TCP on one port by default. The Android library is unchanged; libcamex.so is rebuilt from the
new C sources. e2e on API 34 and 21 against a 4.0.0 server: 14 passed each.
@qodo-free-for-open-source-projects

qodo-free-for-open-source-projects Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

PR Summary by Qodo

Upgrade the camex tunnel to 4.0.0 for Decoder 2.24.2

✨ Enhancement ⚙️ Configuration changes 📝 Documentation 🕐 10-20 Minutes

Grey Divider

AI Description

• Upgrade the camex submodule to 4.0.0 without changing Decoder’s Android tunnel integration.
• Release Decoder 2.24.2 and document the server’s dual-transport behavior.
• Update the English, Russian, and Chinese READMEs to identify the bundled camex version.
Merge Risk 🟡 Medium

Evidence: Partial. The changed camex submodule is represented by a gitlink, but its checked-out contents and the exact base/head submodule revisions were not available in the supplied workspace. The assessment therefore relies on the release note plus the verified Android integration and activation paths; native implementation-level compatibility and rollback details remain unresolved. The provider did not establish the exact full-PR diff revisions. The report lists 20 more gaps.

Blast radius 🟢 Low 💥 1 capability

  • 1 affected end-to-end capability after fault-specific containment; implementation boundaries do not widen its functional scope.
  • This is one bounded user-facing integration: the Network setting, bundled tunnel client, and camera traffic collectively provide remote camera viewing.
  • The Android project includes the camex tunnel as a library, and the activation path starts that library; these are propagation hops of the same behavior rather than independent capabilities.
  • The release note specifically describes the client transport choice and server interoperability for this integration.
Sources

CHANGELOG.md[15-20]

## 2.24.2 — 2026-11-17

- The camex tunnel is built from camex 4.0.0 (was 3.19.0). The Android library is unchanged:
  the client still uses UDP unless TCP is chosen in Network. A camex 4.0.0 server takes UDP
  and TCP clients on the same port by default and keeps a box's address when it changes
  transport.
Behavioral complexity 🟡 Medium 🧩 Compatibility cases

  • Before: the bundled client was camex 3.19.0 and the documented integration targeted that client/server compatibility behavior.
  • After: the bundled client/library points to camex 4.0.0, while the release note states that the client still selects UDP or TCP and that a 4.0.0 server accepts both on one port and preserves a box address when transport changes.
  • New correctness condition: the client must remain interoperable across the supported UDP/TCP choices and mixed-version deployment states, including preserving the effective tunnel identity/address across a transport transition.
  • This is a compatibility interaction introduced by changing the bundled protocol/library dependency, not complexity inherited merely from using an existing mapping or version helper.
  • The native source was unavailable, so extracted unchanged branches versus newly changed internal protocol branches could not be independently verified.
Sources

CHANGELOG.md[15-20]

## 2.24.2 — 2026-11-17

- The camex tunnel is built from camex 4.0.0 (was 3.19.0). The Android library is unchanged:
  the client still uses UDP unless TCP is chosen in Network. A camex 4.0.0 server takes UDP
  and TCP clients on the same port by default and keeps a box's address when it changes
  transport.
Potential damage 🟡 Medium 🩹 Temporary loss

  • If the changed client/library is incompatible with a supported server or mishandles a transport transition, the concrete consequence is loss or degradation of remote camera viewing through the tunnel.
  • The code can be reverted to restore the previous client artifact, but an already deployed incompatible APK requires reinstall/rollback; no persistent camera data is indicated.
  • The source does not establish automatic repair or compensation for an unavailable tunnel.
  • Equal business importance is assumed because no business-criticality declaration was supplied.
  • Reverting or replacing the APK can restore the prior client behavior, subject to deployment access and compatible server/client versions.
  • A user may also be able to switch transport or correct tunnel settings, but automatic recovery and native rollback semantics are not established.
  • No persistent state corruption or external financial/data effect is evidenced.
Sources

CHANGELOG.md[15-20]

## 2.24.2 — 2026-11-17

- The camex tunnel is built from camex 4.0.0 (was 3.19.0). The Android library is unchanged:
  the client still uses UDP unless TCP is chosen in Network. A camex 4.0.0 server takes UDP
  and TCP clients on the same port by default and keeps a box's address when it changes
  transport.

README.md[92-92]

Decoder has a tunnel built in, [OpenIPC camex](https://github.com/OpenIPC/camex) 4.0.0: cameras that are clients of the same camex server are watched from anywhere, without a separate VPN app. **Network** in the menu (a row under the grid) holds the server (`host:port`), the client name (the box's ID on the server), UDP or TCP, the server's public key, the pre-shared key, the server timeout, the password of the debug page and **On**: connect now and at every start. Off by default. The server gives the address, MTU and routes; only the tunnel network and the server's routes (none wider than a /8) go through it, the local network is reached as before. The state is shown in the dialog (Connecting, Connected with the address, VPN consent needed, Failed) and in a notification. A camera reached through the tunnel plays over TCP with Auto. Decoder tells the server its web page is on port 8085 (for nginx there; a camex server 3.19.0 or later). The password, when set, guards that page from the local network and through the tunnel alike; empty (the default), the page is open.
Assessed commit e97f4e9 > Snapshot assessment: the current PR revision could not be verified.
Diagram

graph TD
  MENU["Network menu"] --> LIB["camex Android library"] --> NATIVE["libcamex.so"] --> SERVER["camex 4.0 server"]
  APP["Decoder app"] --> LIB
Loading
High-Level Assessment

Advancing the existing camex submodule is appropriate: Decoder already consumes its Android library, so vendoring or reimplementing the tunnel would add maintenance without a clear benefit. The main review focus is compatibility with the upstream 4.0.0 revision.

Files changed (6) +13 / -6

Documentation (4) +10 / -3
CHANGELOG.mdRecord the Decoder 2.24.2 release +7/-0

Record the Decoder 2.24.2 release

• Adds a 2.24.2 entry describing the camex 4.0.0 upgrade. It clarifies that Decoder still defaults to UDP, while the new server accepts both transports and preserves a box’s address when transport changes.

CHANGELOG.md

README.mdIdentify camex 4.0.0 in the English network guide +1/-1

Identify camex 4.0.0 in the English network guide

• Changes the version named for Decoder’s built-in tunnel from 3.19.0 to 4.0.0. The separate minimum server version for the web-page feature remains 3.19.0.

README.md

README.ru.mdIdentify camex 4.0.0 in the Russian network guide +1/-1

Identify camex 4.0.0 in the Russian network guide

• Changes the version named for the built-in tunnel from 3.19.0 to 4.0.0 without changing the feature guidance.

README.ru.md

README.zh-CN.mdIdentify camex 4.0.0 in the Chinese network guide +1/-1

Identify camex 4.0.0 in the Chinese network guide

• Changes the version named for the built-in tunnel from 3.19.0 to 4.0.0 without changing the feature guidance.

README.zh-CN.md

Other (2) +3 / -3
build.gradleSet the app version to 2.24.2 +2/-2

Set the app version to 2.24.2

• Increments versionCode from 58 to 59 and versionName from 2.24.1 to 2.24.2 for the patch release.

android/app/build.gradle

camexAdvance the camex submodule to 4.0.0 +1/-1

Advance the camex submodule to 4.0.0

• Moves the submodule from commit 4c2626f to 0712dcb. This supplies the updated native sources used to build the tunnel while retaining the existing Android library integration.

bundles/camex

@qodo-free-for-open-source-projects

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can enable the Remediation agent and Qodo fixes findings in a dedicated fix PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@compot-dev
compot-dev merged commit 0a5763b into v2 Nov 17, 2026
7 checks passed
@compot-dev
compot-dev deleted the build/camex-4.0.0 branch November 17, 2026 17:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant