Skip to content

Latest commit

 

History

History
88 lines (58 loc) · 3.46 KB

File metadata and controls

88 lines (58 loc) · 3.46 KB

Android companion — scan to capture and transfer

Android test phones should not need a new Wi‑Fi proxy every time someone borrows the device. The 1.4.0 Beta companion uses a system VPN to send HTTP(S) to the DevPeek instance you scan.

This is a short GitHub summary. Full screenshots and CA steps: website Android guide (中文).


What it is (and is not)

Does Does not (yet)
Scan / paste / type an address and approve VPN Per-app VPN filter
Route HTTP(S) that honors the system proxy iOS companion
Help install this computer’s CA after connect Bypass certificate pinning
Transfer text, images, and files (up to 2 GB) on a separate channel Put transfer traffic into the capture list

Pairing codes contain a LAN proxy address. Keep them on a trusted test network.


Connect

DevPeek right rail → Phone panel → QR
        ↓
Android app scans (or album / paste / manual IP:port)
        ↓
Approve VPN → HTTP(S) appears under that client tab
  1. Desktop and phone on the same LAN. Start DevPeek so the proxy is listening.
  2. Open the right-rail Phone panel (or View → Phone).
  3. Install the APK from that panel (or the official download URL).
  4. Scan the pairing QR — not the certificate-download QR.
  5. Confirm a green connection dot on the desktop Phone icon, then visit an HTTP page in Chrome.

The app remembers recent computers. If the desktop proxy disappears, the VPN disconnects so the phone is not left hanging.

Wi‑Fi proxy remains the fallback (and the path for iOS). Checklist: quick-start.md


HTTPS plaintext still needs a CA

VPN only forwards. To read HTTPS bodies:

  1. After connect, Android Settings → Install certificate → Save and open settings.
  2. Install Downloads/devpeek-ca.crt as a CA certificate (not “VPN and apps”). A screen lock is usually required.
  3. On the desktop, put the host in the SSL include list and keep it off the exclude list.

Android 7+ apps may reject user CAs. Chrome is the usual smoke test; WeChat and many store builds will stay encrypted. Use an authorized debug build — DevPeek cannot bypass pinning.


File transfer

Once connected, the desktop Phone panel and the app’s transfer assistant send text, images, and files in either direction.

  • Transfer does not appear in the capture list.
  • Capture can still work if transfer is down, and the reverse is also true.
  • Images/videos open in a preview; received files can be saved on the desktop.

Disconnect

Tap Disconnect in the Android header to stop the VPN before changing networks, handing the phone over, or enabling another VPN. Android typically keeps only one VPN at a time.


Typical failures

Symptom Check
Cannot scan Phone panel actually showing a QR; try album, paste, or manual IP
Timeout Same LAN, current desktop IP, proxy running, firewall, AP isolation
HTTP yes, HTTPS no CA install, SSL include/exclude, app trust policy
Browser works, one app does not User-CA rejection or pinning
Transfer fails, capture works Separate channel — reopen Phone panel or reconnect

Related