Skip to content

Android app: camex 4.0.1, TCP tunnel fixed (1.47.5) - #100

Merged
compot-dev merged 1 commit into
mainfrom
camex-4.0.1
Nov 18, 2026
Merged

compot-dev merged 1 commit into
mainfrom
camex-4.0.1

Conversation

@compot-dev

Copy link
Copy Markdown
Collaborator

Moves bundles/camex to camex 4.0.1 (9e721e5, OpenIPC/camex#181): a frame body read in pieces is kept per connection, so a tunnel over TCP no longer stalls from the server to the client. The fix is in the shared receive path, so the client library in the app needs it too. UDP, the protocol and the tunnel API are unchanged.

Checked:

  • tests/run.sh, Android assembleDebug lintDebug assembleRelease;
  • tests/android/remote-e2e.sh on API 34 and 21: 11/11;
  • TV box with Android 10 through a camex 4.0.1 server over TCP, after a reboot: Detect finds CH341A with BY25Q64AS, an 8 MB dump downloads by the nginx name in 7 s (~1.2 MB/s, was ~10 KB/s) with the same md5.

@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 type 'qodo, fix this' on a finding and the fix lands right on your PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

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

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

Copy link
Copy Markdown

PR Summary by Qodo

Fix Android TCP tunnel stalls with camex 4.0.1

🐞 Bug fix ⚙️ Configuration changes 🕐 10-20 Minutes

Grey Divider

AI Description

• Pin Android’s camex client to 4.0.1 to fix stalled server-to-client TCP traffic.
• Release the fix as 1.47.5; UDP, the protocol, and the tunnel API remain unchanged.
• Report passing tests, Android builds, emulator checks, and an on-device dump.
Merge Risk 🟡 Medium

Blast radius 🔴 High 💥 2 capabilities

  • 2 affected capabilities span independent functional scopes: Android remote-access tunnel integration, Product release/version identification.
  • The tunnel library, RemoteService startup, and the web endpoint form one bounded remote-access integration: the user outcome is an operator reaching the device's web interface through camex.
  • The library is an implementation hop in that path, not an independent capability.
  • UDP and TCP are transport variants of the same remote-access outcome; no separate functional scope is established.
  • CLI/web version display and Android package version metadata serve the bounded outcome of identifying the installed product release.
  • The C constant and Gradle consumer are implementation and packaging hops of that outcome, not independent capabilities.
Behavioral complexity 🟡 Medium 🧩 Data transformation

  • Before: the tunnel library's TCP framing behavior could lose a frame body when the body arrived in pieces.
  • After: the pinned implementation changes how a framed TCP body is accumulated and delivered to the Android-side tunnel consumer.
  • New correctness condition: all partial reads for a frame must be accumulated in order, with correct length boundaries and connection/error handling, before the downstream HTTP stream observes the body.
  • This is more than a version-only change, but the exact implementation and whether it introduces additional state interactions cannot be verified because the submodule contents are unavailable.
Potential damage 🟡 Medium 🩹 Temporary loss

  • A malformed or stalled TCP tunnel stream can prevent the remote operator from reaching or completing requests against the web interface.
  • The affected behavior is one end-to-end remote-access capability, not separate damage for the tunnel library, HTTP server, and Android service.
  • No persistent flash or application state is implicated by the available path, and the failure is recoverable by reconnecting, restarting the tunnel/app, or reverting the embedded library; automatic recovery for every stream failure is not proven.
  • With no business-criticality declaration, equal business importance is assumed.
  • Code rollback would restore the prior tunnel implementation, while an activated connection may still need to be closed and re-established.
  • No persistent state repair or external compensation is indicated.
  • RemoteService has retry logic for selected failed/stopped states, but invocation for partial TCP frame failures is unresolved; manual restart or reconfiguration may be required.
Assessed commit 0df9d69 > Snapshot assessment: the current PR revision could not be verified.
Diagram

graph TD
  Browser["Operator Browser"] <--> Server["camex Server"] <--> Receive["TCP Receive Path"] <--> Tunnel["Android Tunnel"] <--> Web["Remote Web Mode"]
Loading
High-Level Assessment

Pinning the upstream camex release is appropriate: the fix belongs in its shared receive path, which the Android client builds from the submodule. A local workaround would duplicate protocol handling without addressing the underlying library behavior.

Files changed (3) +7 / -2

Documentation (1) +5 / -0
CHANGELOG.mdDocument the 1.47.5 TCP tunnel fix +5/-0

Document the 1.47.5 TCP tunnel fix

• Adds a release entry explaining that camex 4.0.1 prevents server-to-client TCP stalls when frame bodies arrive in pieces. Notes that UDP is unchanged.

CHANGELOG.md

Other (2) +2 / -2
camexPin camex to revision 9e721e5 +1/-1

Pin camex to revision 9e721e5

• Advances the camex submodule revision used to build the Android tunnel client. The referenced 4.0.1 release contains the shared receive-path fix; its source changes are not included in this diff.

bundles/camex

main.cBump the release version to 1.47.5 +1/-1

Bump the release version to 1.47.5

• Changes '_VER' from 1.47.4 to 1.47.5. The Android build reads this value for its app version.

src/main.c

@compot-dev
compot-dev merged commit 004991f into main Nov 18, 2026
9 checks passed
@compot-dev
compot-dev deleted the camex-4.0.1 branch November 18, 2026 00:45
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