OpenAVM V5.1 - Recorder & Phone

OpenAVM V5.1 — Recorder & Phone

A regular release of Recorder 5.1.0 (134) and Phone 5.1.0 (56). Both apps are updated. Install over your existing OpenAVM apps to keep recordings, pairing and settings.

Downloads

Install on	File
Vehicle head unit (ARM64)	OpenAVM-Recorder-5.1.0-arm64-v8a.apk
Android phone	OpenAVM-Phone-5.1.0.apk
File verification	SHA256SUMS.txt

Setup guide · Verification and limits

What's new on the vehicle

• Optional multi-camera recording: record surround together with cabin and/or infrared channels where the head unit supports them. Selected channels use the same chosen recording destination. Enable additional cameras in settings; they are not required for ordinary surround recording.
• Driving data and HUD: optionally record GPS and available vehicle signals alongside video. View speed, gear, indicators and available pedal readings live and in playback. Pedal bars are relative to observed historical peaks, not calibrated pedal percentages; missing data remains unavailable.
• Session playback: a clip list, multi-camera views, shared timeline, recorded HUD and route panel. Enlarge individual views, seek across compatible adjacent clips, select clips or a time range, and transfer or export recordings.
• Maps: view a local recorded trace or opt into online street maps. The map panel opens by default unless you have saved it off; the street-map choice is remembered. Pan, zoom and follow the recorded position. Old recordings without GPS remain playable.
• Recording and preview stability: retains the tested camera connection across eligible preview/record/stop handoffs, waits for acknowledged resource release, and handles same-size cabin encoder-format changes at safe file boundaries. Recovery now keeps waiting for its own closing preview within the existing deadline instead of cancelling at an intermediate warning.
• Smoother review: visible thumbnails load without holding up playback; compatible neighbouring segments share their player and output surface. Actual recording gaps remain visible.
• Floating window: select the cabin feed while it is being recorded without restarting the recording, with clearer live HUD and return/setup choices.

What's new on the phone

• Receive optional recorded GPS/vehicle data together with videos and review the session timeline, HUD and route.
• A map panel that opens by default, with remembered local-trace/street-map choice and map interaction improvements.
• Keeps secure local pairing, media management, video playback/export, widgets and optional cloud vehicle controls in one app.

Local Recorder pairing, transfer and playback do not require a ZEEKR account or cloud configuration. The public phone APK does not include, host or automatically download manufacturer connection parameters. Optional cloud features still require a user-supplied configuration and authorised login; automation is separately enabled. Cloud setup and empty template.

Upgrade notes

1. Stop recording, wait for saving to finish, then install each matching APK over the existing app. Do not uninstall first. Recorder 134 also upgrades the private support builds through 133.
2. Review Return, recording & playback after updating: floating-window behaviour, optional automatic recording, extra cameras, driving-data capture and map display. Saving choices does not immediately start a recording.
3. Check camera directions and the actual recording destination while parked. USB preferred may use internal storage if no single supported, writable USB target is available.
4. Update both apps to use the new drive-data playback together. Existing V5 pairing is retained; V4 connections require secure re-pairing. Compare the complete phone fingerprint when pairing.
5. Phone users with an existing valid user-imported configuration retain it. The older embedded configuration format still requires a new import/sign-in, with old automation stopped. The withdrawn Phone 5.0.0 APK remains withdrawn.

Compatibility and known limits

Both apps require Android 8.0+. Recorder needs an ARM64 head unit with compatible App Lab camera access. Camera concurrency, resolution, vehicle signals and GPS availability vary by firmware. The current phone cloud-control baseline is Australian ZEEKR 7X / AU 1.6.6; this restriction does not apply to account-free local recording transfer.

The owner reported satisfactory normal use of the latest recorder candidate on 14 October 2026 and requested this release. Automated verification is recorded separately; neither establishes compatibility with every vehicle or every camera/USB combination.

• Returning to the car or stopping recording can still involve waiting for the camera driver to release resources. A vendor-specific stall or unexpected encoder timestamp can interrupt recording; not every earlier hardware failure has been independently reproduced or proven eliminated. Check recording status and preserve diagnostics if it happens.
• Reopen OpenAVM after a head-unit reboot or system termination. A retained floating window is not continuous parking recording and does not remotely wake the vehicle.
• Issue #28, USB not being selected on one reported setup, remains open pending device evidence. This release does not claim to resolve that report.
• Drive data is stored locally and accompanies transfer only when selected. Online maps use OpenFreeMap with MapLibre and request map resources from their providers; they need internet. No satellite view or offline region download is included.
• Historical-peak pedal bars are an approximation. Multiple channels use recorded timing evidence; hardware frame synchronisation is not guaranteed.
• Normal phone refresh reads status. The separate cabin-temperature action may briefly run climate control. Widgets and automation depend on Android/network/vehicle availability.

Feedback

Include the app version, vehicle/firmware, enabled cameras, actual storage destination, exact error and whether the issue affects preview, saved video or both. Use Settings → Recording diagnostics to save a diagnostic file when useful. Keep precise routes, account data, connection parameters, pairing information and private footage out of public issues. Security reporting.

OpenAVM is independent and unofficial, with no affiliation to or endorsement by ZEEKR.

OpenAVM V5 - Recorder 5.0.0 + Phone 5.0.1

OpenAVM V5 — Recorder 5.0.0 + Phone 5.0.1

This is a phone-only update. Phone 5.0.1 replaces the withdrawn Phone 5.0.0 APK. It keeps the complete phone client while removing bundled manufacturer connection parameters. OpenAVM Recorder pairing, recording transfer and playback require no cloud configuration or ZEEKR account.

This is the current regular V5 release for compatible ZEEKR vehicles. The vehicle APK is the unchanged Recorder 5.0.0 / 102; the phone APK is 5.0.1 / 52. Existing Recorder 5.0.0 users only need to update the phone. Promotion from prerelease does not change either APK or expand the verified compatibility scope below.

Downloads

File	Install on	Version
OpenAVM-Recorder-5.0.0-arm64-v8a.apk	Vehicle head unit	5.0.0 / 102
OpenAVM-Phone-5.0.1.apk	Android phone	5.0.1 / 52
connection-config.template.json	Empty format example for optional cloud setup; contains no working parameters
SHA256SUMS.txt	Verify downloaded files

Recorder works without a phone. To use the phone only for recordings: install it, choose Set up later, open Media → Connection, and follow secure pairing. Both devices must share a Wi-Fi network or phone hotspot. Compare the complete phone fingerprint before confirming pairing.

Cloud controls are optional: independently prepare a compatible configuration, import it in Home → Set up cloud, then sign in with your authorised account. The app does not include, host or automatically download those parameters. Importing a file alone sends no vehicle requests. See the cloud setup guide.

Setup and upgrade guide · Project overview

Vehicle Recorder

• Recording: normal and time-lapse modes, with continuous capture across normal surround-recording segment boundaries on supported configurations.
• Floating live mirror: preview without recording, individual directions, a four-view grid, Cabin selection, resizing and recording controls.
• When you return: keep a Logo entry, restore the full floating preview, or explicitly enable automatic recording when the screen becomes usable again. Choose the behaviour after each installation or update; automatic recording is off by default.
• Recording library: date filters, grouped segments and emergency clips make recordings easier to find and keep.
• Secure phone transfer: encrypted local connections and pairing that requires comparing the full phone identity fingerprint.
• Setup help: revised tutorials and six interface languages, including English.

Android phone

• Recordings: receive, play, export and share vehicle recordings. V5 improves seeking across legacy video segments and brings recording management into the same app as vehicle controls.
• Vehicle status and widgets: battery, range, cabin temperature, location and data timestamps; 2×2, 4×1, 4×2 and 4×3 widgets with direct actions and progress feedback.
• Preconditioning: set temperature, duration and seat preferences; tap to start and tap again to stop, or schedule a departure.
• Factory Sentry rules: optionally enable Sentry after parking away from home and disable it after a confirmed arrival home. Manual choices made in OpenAVM are respected for the current parking session.
• Separate refresh actions: ordinary status refresh and a dedicated cabin-temperature button, with clearer progress and results.
• Optional cloud setup: local recording features work immediately. Cloud status and controls require user-supplied configuration and login; automation is separately enabled. Setup and help are available in English and Simplified Chinese.

Phone cloud controls currently target the Australian ZEEKR 7X, using the AU 1.6.6 integration. Other regions and models are not generally verified, and shared accounts keep only the permissions granted by the owner. This limitation concerns cloud vehicle controls; local recording transfer and playback do not require a ZEEKR account.

Upgrading from an earlier version

Recorder 5.0.0 users: its in-app update checker compares GitHub release tags, so it may offer this v5.0.1 release even though the Recorder APK is still 5.0.0. Skip reinstalling Recorder for this phone-only update; check the app-specific versions in the download table.

1. Install over the existing app; do not uninstall first. Use the official matching-signature APK. Early standalone-assistant users should follow the setup guide before changing installations.
2. Check camera directions while parked. The first V5 launch applies the right-hand-drive preset once: Front 1, Rear 2, Left 3, Right 4; Cabin 1, Infrared 0. Later manual adjustments are retained.
3. Choose your return behaviour again. Confirm Logo, full preview or the additional automatic-recording option after installing or updating.
4. Use Recorder 5.0.0 with Phone 5.0.1 for recording transfer. Existing V5 pairing is retained; V4 connections need secure pairing again once. Compare the complete fingerprint during pairing.
5. Moving to a new phone? Pause scheduled departures and Sentry automation on the old phone before enabling them on the new one.
6. Upgrading Phone 5.0.0 or an older configuration format? Old cloud configuration and login are removed, and old cloud tasks are stopped. Import and sign in once to use cloud controls again. Recordings, Recorder pairing, home and comfort preferences are retained; review disabled plans and deliberately re-enable the rules you want. The old Phone 5.0.0 APK is not being restored.

Connection verification for this update

The exact signed Phone 5.0.1 APK passed an Android emulator test using the same transport code as the published Recorder 5.0.0: fingerprint verification, encrypted pairing, session reconnection, WebSocket messaging, real MP4 transfer, receiver restart and resume, SHA-256 verification, media-library indexing and credential revocation. The complete local-media and security suite also passed, including video playback in the embedded player, without Zeekr cloud setup.

These are emulator/code compatibility checks, not a new test in the owner's physical vehicle. Camera access and the actual vehicle/phone Wi-Fi environment remain device dependent. Verification details.

Compatibility and practical limits

Both apps require Android 8.0 or newer. Recorder additionally needs an ARM64 head unit with compatible App Lab camera access, installation permissions and writable storage; Android alone does not establish compatibility.

• A retained floating window can restore preview or request recording while the app remains running. Reopen the app after a head-unit restart or system termination. This feature does not provide continuous parking recording or remote camera viewing.
• Camera availability, vehicle power and storage conditions can interrupt capture. Segment continuity does not cover every interruption. A recording-writer failure observed during earlier testing remains under investigation; see the setup guide for reporting details.
• Check the actual recording destination, wait for saving to finish before removing USB, and back up important clips.
• Normal refresh only reads status. The separate temperature button may briefly start climate control, then request that this temporary session stop. A successful read can still return an older vehicle measurement; check the timestamp.
• Phone Sentry automation controls the vehicle's factory feature, independently of Recorder. Android background restrictions, network conditions and vehicle sleep may delay updates and actions. Widgets are not continuously live.

Feedback

For recording or preview issues, include the app version, vehicle model/region, firmware, recording mode, storage destination, steps and exact error. Say whether the problem affects the live preview, the saved recording or both. For pairing and transfer issues, include both app versions.

Report an issue, keeping account details, locations, number plates, pairing information and private footage out of public reports. For sensitive security findings, follow the reporting policy.

OpenAVM is an independent, unofficial project, not affiliated with or endorsed by ZEEKR.

OpenAVM V5 - Recorder

OpenAVM V5 — Recorder 5.0.0

Phone downloads have resumed with Phone 5.0.1. The previous Phone 5.0.0 APK remains withdrawn and is not being restored.

Recorder 5.0.0 / 102 is unchanged. If it is already installed in your vehicle, only update the phone app to 5.0.1 / 52. This original release is superseded by the current regular V5 release linked above.

Downloads

File	Install on
OpenAVM-Recorder-5.0.0-arm64-v8a.apk	Vehicle head unit
OpenAVM-Phone-5.0.1.apk	Android phone; replacement for the withdrawn build
Recorder SHA256SUMS.txt	Checksum for the Recorder attachment on this release
Current release checksums	Checksums for both current APKs and the empty configuration template

Using the phone app

OpenAVM Recorder pairing, recording transfer, playback and export work without a ZEEKR account or cloud configuration. Install Phone 5.0.1, choose Set up later, then open Media → Connection. Put both devices on the same Wi-Fi network or phone hotspot and compare the complete phone fingerprint when pairing.

Cloud vehicle status and controls remain optional. Phone 5.0.1 does not include, host or automatically download manufacturer connection parameters. Independently prepare a compatible configuration, import it, and sign in with your authorised account. Automation requires a separate opt-in. The empty template is a format example, not a working connection profile.

Upgrade over the existing phone app; do not uninstall first. Legacy cloud configuration, login and pending cloud tasks are removed during this upgrade. Recordings and V5 Recorder pairing are retained. Import and sign in again only if you want cloud features. V4 connections need secure pairing again once.

See the full current release notes and verification scope, setup and upgrade guide, and optional cloud setup guide.

OpenAVM is an independent, unofficial project, not affiliated with or endorsed by ZEEKR.

OpenAVM V4 - Recorder and Android Companion

OpenAVM V4 — 4.0.0

Technical explanation · 详细技术说明

V4 brings direct USB recording, an optional Android companion and sound tools together in the current stable release channel. It replaces the previous public alpha as the recommended download, with compatibility still based on targeted owner testing.

Download

File	Install on	Version	Size
OpenAVM-Recorder-V4-arm64-v8a.apk	Compatible ARM64 head unit	4.0.0 (57)	2.24 MB
OpenAVM-Companion-V4.apk	Optional Android phone app	4.0.0 (29)	3.15 MB

Android 8.0+ is required on both devices; the vehicle also needs compatible App Lab camera/storage access. Use the signed APKs attached below. Same-ID, same-signature installations can be upgraded in place. The phone APK is optional: the vehicle app and USB already support the main recording, library and sound-tool workflows.

English setup guide · 中文使用说明

Changes since the previous public release

• Direct USB video recording, internal-to-USB export, storage quotas and managed USB cleanup. Video is not staged internally first; small metadata/settings/diagnostics remain internal. Bounded internal fallback is retained when appropriate.
• Surround, Cabin and IR source choices; normal and time-lapse recording. The 2×, 5× and 10× time-lapse settings have targeted owner testing.
• Categories, grouped one-minute recording sessions, selected-segment transfer, bulk deletion of OpenAVM files and read-only factory Sentry browsing/transfer.
• Android hotspot/LAN transfer, direct USB access on the phone, trimming and individual-view export. Video opens directly into an integrated player and square single-camera footage retains its correct proportions.
• WAV lock/unlock sound creation on both devices, phone-to-vehicle USB sound transfer, and a vehicle toolbox for imported music/video plus USB sound preview/deletion.
• Six UI language choices plus follow system; matching icons and a simpler vehicle Settings page with advanced diagnostics hidden by default.
• Fixes USB loss during vehicle departure incorrectly creating an extra internal clip. The owner retested RC2 and reported no recurrence; V4 retains that recorder implementation.
• Custom parking Sentry capture, its AI model/OpenCV dependency and return-to-car automatic recording are excluded from V4. Shared camera cleanup safeguards and factory Sentry media support remain.

Some capabilities were developed across private test builds; this list describes the public V4 experience, not a claim that every item originated in this final build.

Practical notes

• On the owner's car, normal recording commonly lasts about five minutes after leaving. It can help cover part of the gap before factory Sentry starts, but is not a fixed timer or guaranteed handover.
• A new sound may appear in the factory list only after leaving and returning, or reconnecting USB once file operations finish. OpenAVM cannot select or identify the active factory sound.
• Older test builds experienced a persistent third-party camera-feed stall requiring a head-unit restart. The owner reports no recurrence in current V4 testing; that does not establish a universal fix or guarantee factory-system independence.
• Vehicle model/firmware, USB and Android background behaviour can vary. Long-duration, full-disk and repeated hard-unplug behaviour are not exhaustively tested. This is independent, unofficial software; use its controls while parked.

For diagnostics, tap the vehicle version seven times in Settings → About & privacy, then open Developer tools → Recording diagnostics and copy JSON. Keep all parts of a split report together; no ZIP is needed. Review private information before sharing.

Verification

Both apps were rebuilt from the public-source checkout. All 751 product/shared JVM tests passed, both release assemblies passed, and Lint reported zero errors (existing warnings remain). The release APKs retain the signing certificate used by preceding owner builds. APK integrity, signatures, version IDs, ABI contents, packaged languages, matching icons and absence of parking AI assets were checked. The owner accepted the RC2 departure fix and phone UI; the final branding/settings polish received local verification. Detailed build evidence is recorded in DEVELOPMENT.md.

SHA256SUMS.txt covers the two APKs and RELEASE_NOTES.md attached to this release.

中文

V4 包含车机端 4.0.0 (57) 和可选安卓手机端 4.0.0 (29)，作为当前正式发布版本。手机 APK 不是必装的：车机端配合 USB 即可完成录像、录像管理和音效制作等主要操作。

• 录像直接写 USB、旧内置录像导出、配额和本软件文件清理；保留必要的少量内部元数据及有条件的内置回退。
• 环视/Cabin/IR 选择、普通与延时录像；2×、5×、10× 已有车主针对性测试。
• 录像分类、同次一分钟分段归组、选择分段传手机，以及只读原车哨兵浏览/传输。
• 手机热点传输、直接 USB、裁剪和单视角导出；点开即播放，正方形视频比例正确。
• 两端 WAV 解闭锁音效制作、手机经车机保存至 USB，以及车机音效查看/试听/删除。
• 六种界面语言和跟随系统、统一图标、默认隐藏高级诊断。
• 离车后额外内置小录像修复已获车主复测，未再出现；正式版保留该录像实现。
• 自研停车哨兵、AI 模型和回车自动录像暂不提供；原车哨兵视频功能保留。

离车后约五分钟是车主车辆的实测表现，不是固定倒计时或保证与原车哨兵衔接。新音效有时需要离车再回车或重新连接 USB 后，原车列表才刷新。旧测试版的相机取流停滞在目前 V4 测试中未复现，不代表所有车辆或场景均已验证。

需要诊断时，在车机“设置 → 关于与隐私”连续点击版本七次，打开开发者工具中的录像诊断，直接复制 JSON 全部分段即可。请在停稳后操作，并检查公开反馈中的个人信息。

OpenAVM v0.3.0-alpha8 Experimental Public Test

OpenAVM v0.3.0-alpha8 — Experimental Public Test

Caution

This is an opt-in experimental prerelease, not the recommended stable path. For the more conservative normal-recording baseline, continue using AVM Recorder v0.2.0-alpha9.

Read before installing

• Normal recording inherits the extensively road-tested v0.2 recorder path, but this exact v0.3.0 build and its latest lifecycle change have not yet completed real-car acceptance testing.
• Time-lapse remains experimental. Always press Stop before leaving or locking the vehicle. Do not rely on automatic vehicle-away termination for time-lapse.
• Earlier development builds entered a persistent third-party Camera2/vendor-pipeline stall after repeated time-lapse and lock cycles. If AVM preview becomes black, frozen or extremely slow, stop using the app. If it does not recover, uninstall AVM Recorder and restart the head unit before testing again.
• Stop using OpenAVM immediately if any OEM camera, reverse-view, parking-view or infotainment behaviour appears abnormal.
• OpenAVM Companion's direct recording download has been tested. Its Toolbox is work in progress and must not be used in this release, including Sentry USB handling and lock/unlock sound writing.
• This software is unofficial, is not endorsed by Zeekr, is not a replacement for an OEM dashcam or any vehicle safety system, and must not be operated while driving.

Included APKs

OpenAVM Recorder v0.3.0-alpha8-safe-lifecycle

• Normal recording remains on the established repeating-request path.
• Selectable 360°, Cabin and IR logical recording sources with compatibility mapping.
• Experimental 2×–150× time-lapse for all three sources.
• Recording segments are grouped into logical Sessions in the gallery.
• Direct hotspot/LAN transfer to OpenAVM Companion, with cancellable queued and active transfers.
• Camera-interruption recovery remains limited to a Session that the user manually started.
• The latest time-lapse lifecycle change serializes paced capture requests, quiesces capture on preliminary power-off evidence, and fences the Camera producer before stopping/releasing the recorder.
• Interrupted segments are preserved only when a valid finalized video track can be read; invalid partial files remain quarantined.

OpenAVM Companion v2.5.0-alpha1

• Pair with the vehicle app over a local phone hotspot/LAN.
• Download recordings and cancel queued or active transfers.
• Session-based phone media library and source-aware playback for 360°, Cabin and IR recordings.
• 360° four-view playback, tap-to-focus, zoom/pan, view export and time-range export.
• Local media import and export workflows.
• Toolbox UI is included for development visibility but is not validated and must not be used in this release.

Keep the phone hotspot active and preferably keep OpenAVM Companion in the foreground during transfers. Automatic reconnection, every Android background state and every phone vendor have not been fully validated.

The public Companion APK is now signed with the stable OpenAVM release certificate. If you installed a private/debug-signed Companion test APK, Android may require you to uninstall that test build once before installing this public APK.

Camera and OEM-resource limitation

OEM camera interfaces and OpenAVM may share Camera HAL/ISP/vendor resources. Concurrent operation is not guaranteed. An OEM camera may interrupt the current OpenAVM segment; a short recording gap and quarantine/loss of an unfinished segment remain possible. OpenAVM must never be treated as having priority over an OEM function.

Verification

• Source commit: d01d90f
• Recorder APK SHA-256: 397700BF80B4BF26CE6FD7D98264D45F15A35089F69CF11510F935A4D7EF4DA1
• Companion APK SHA-256: 9957DAA1521E65CA9DCA812009965E90EA3F17DD7B9EC8699E759C1BD48CBB8F
• Signing certificate: CN=AVM Recorder, O=Dantenothing, C=AU
• APK Signature Schemes v2/v3 verified for both APKs
• Recorder and Companion Release unit tests, Android Lint and Release builds completed successfully

---

中文说明

Caution

这是供自愿测试者使用的实验性 Pre-release，不是推荐的稳定路径。如主要使用普通录像并希望选择更保守的版本，请继续使用 AVM Recorder v0.2.0-alpha9。

安装前必须阅读

• 普通录像沿用了经过较多实车测试的 v0.2 录像路径，但这个具体的 v0.3.0 构建及其最新生命周期修改尚未完成实车验收。
• 延时摄影仍属实验功能。离车或锁车前必须手动按 Stop / 停止录像，不要依赖自动离车终止。
• 此前的开发版本曾在反复进行延时录像与锁车测试后，使第三方 Camera2 / vendor 摄像头管线持续黑屏、卡死或极慢。如果出现此类异常，请立即停止使用；若无法恢复，请卸载 AVM Recorder 并重启车机后再测试。
• 如果原厂摄像头、倒车影像、停车影像或车机出现任何异常，请立即停止使用 OpenAVM。
• OpenAVM Companion 的车机录像直接下载功能已经测试；其中的 Toolbox / 工具箱仍在开发，本版本请勿使用，包括哨兵 USB 和解闭锁音效写入。
• 本软件是非官方实验项目，未获得极氪认可，不能替代原厂行车记录仪或任何车辆安全系统，驾驶过程中请勿操作。

本次包含

OpenAVM Recorder v0.3.0-alpha8-safe-lifecycle

• 普通录像继续使用已建立的 repeating-request 路径；
• 可选择 360°、Cabin 和 IR 三种逻辑录像源并进行兼容性映射；
• 三种录像源均提供实验性的 2×–150× 延时摄影；
• 回看页按照逻辑 Session 归组底层录像分段；
• 可通过手机热点 / 局域网向 Companion 传输录像，并可取消排队或进行中的任务；
• Camera 中断恢复只适用于用户已经手动开始的当前 Session；
• 最新延时生命周期修改会串行提交抽帧请求，在初步关机证据出现时停止继续抽帧，并在停止 Recorder 前隔离 Camera producer；
• 中断录像只有在能够读取到有效视频轨道时才会保留，否则仍会隔离为异常文件。

OpenAVM Companion v2.5.0-alpha1

• 通过手机热点 / 局域网与车机配对并下载录像；
• 可取消排队或进行中的传输；
• 按 Session 管理手机媒体库，兼容 360°、Cabin 和 IR 回看；
• 支持 360° 四画面、点击放大、缩放/移动、按方向导出及按时间范围导出；
• 支持本地媒体导入与导出流程；
• Toolbox 界面虽然存在，但尚未验证，本版本请勿使用。

传输过程中请保持手机热点开启，并尽量让 OpenAVM Companion 保持前台。自动重连、所有 Android 后台状态和不同手机厂商系统尚未全部验证。

公开版 Companion 已改用稳定的 OpenAVM 正式证书。若手机上安装过私下测试的 Debug 签名版本，Android 可能会要求先卸载一次旧测试版，才能安装这次公开版。

Camera 与原厂资源限制

原厂 Camera 界面与 OpenAVM 可能共享 Camera HAL / ISP / vendor 资源，不能保证并发运行。原厂 Camera 可能中断 OpenAVM 当前分段，仍可能产生短暂录像缺口，以及未完成分段被隔离或丢失。OpenAVM 绝不能被视为拥有高于原厂功能的资源优先级。

完整性

• 源码提交：d01d90f
• Recorder APK SHA-256：397700BF80B4BF26CE6FD7D98264D45F15A35089F69CF11510F935A4D7EF4DA1
• Companion APK SHA-256：9957DAA1521E65CA9DCA812009965E90EA3F17DD7B9EC8699E759C1BD48CBB8F
• 签名证书：CN=AVM Recorder, O=Dantenothing, C=AU
• 两个 APK 均已通过 v2/v3 签名验证
• Recorder 与 Companion 的 Release 单元测试、Android Lint 和 Release 构建均已完成

AVM Recorder v0.2.0-alpha9

This prerelease is the exact build validated in a ZEEKR 7X before publication. The attached APK has not been rebuilt or re-signed after the vehicle acceptance test.

Highlights

• Adds three logical recording sources: 360°, Cabin, and IR.
• Adds compatibility camera mapping with verified defaults: 360° Auto/Camera 2, Cabin Camera 1, IR Camera 0.
• Records source/layout metadata so 360° clips use four-lane playback while Cabin/IR clips use a normal single view.
• Recovers the same manually started Session after temporary OEM camera arbitration loss.
• Stops terminally after confirmed vehicle-away/lock camera loss, releases the wake lock, and does not resume after returning to the car.
• Rebuilds the 360° preview Surface after backgrounding to prevent long-running blurry preview while keeping the encoder path unchanged.
• Fixes the duplicate gallery-key crash with large recording libraries.

Real-car acceptance

Validated across normal background recording and segment rollover, repeated foreground/background transitions, source selection and playback, OEM cabin-camera interruption/recovery, and lock/vehicle-away termination. The final lock test stopped automatically after the vehicle camera became unavailable (about five minutes on the tested car) and remained idle after unlock.

Important camera limitation

The OEM rear-seat/cabin camera and AVM Recorder may still share vendor Camera HAL/ISP resources. They are not guaranteed to run concurrently. In this release, opening the OEM camera can interrupt AVM's current segment; AVM waits and resumes the same manual Session after the OEM camera releases the resource. A short recording gap and loss/quarantine of the unfinished segment remain possible.

Not included yet

Time-lapse recording, phone transfer, and four-direction-only recording are planned follow-up work and are not enabled in this build.

Integrity

• Source commit: 01be6860b3517c16d174be9c00c49359bc75981f
• APK SHA-256: E81ACB98608A632B3A630E94A457BC3EE65652FE5FBD9752E1877AD3B3BBFC95
• Signing certificate: CN=AVM Recorder, O=Dantenothing, C=AU
• APK Signature Scheme v2/v3 verified
• 205 unit tests passed; Android lint completed with 0 errors

Thanks

Thanks to @sharkcreep87 for the camera-selection proposal in #11 and the camera-recovery proposal in #12. Both directly informed the expanded source-mapping and recovery design shipped here.

AVM Recorder v0.1.1-rc4

AVM Recorder v0.1.1-rc4

This is a real-car-tested release candidate built from commit 3674d3c.

What changed

• Fixed recording failure when the preview Surface is destroyed while switching tabs near a segment boundary (#2, based on PR #8).
• Hardened MediaRecorder stop/finalize and segment-rollover ordering; repeated one-minute rollovers completed successfully in real-car testing (#4).
• Restored stable high-resolution preview behaviour for ordinary tab switches and app background/foreground transitions (#5).
• Added Clear all and Delete unprotected gallery actions (#3).
• Added safe replacement of the recording preview Surface without restarting the active MediaRecorder session.
• Bounded and moved event-log writes away from the camera thread (based on PR #6).
• Bounded failed-segment quarantine retention (based on PR #7).

Validation

• 157 JVM tests passed; 0 failures, 0 skipped.
• Android lint completed with 0 errors.
• Real-car checks covered repeated segment rollover, tab switching for longer than one minute, app background/foreground transitions, stop/finalize, gallery playback, and protected/unprotected deletion.

Known camera-resource limitation — please read (#9)

This conflict was reproduced only with the OEM rear-seat/cabin camera. The OEM 360 screen and reverse view worked normally in our real-car tests and are not included in this limitation. The AVM recording stream and the rear-seat camera appear to contend for the same vendor Camera HAL / ISP resources. Do not intentionally open the rear-seat camera while AVM Recorder is recording.

• In most observed runs, AVM Recorder keeps the camera and the rear-seat camera reports a streaming error; recording continues.
• In some runs, the rear-seat camera wins resource arbitration. AVM Recorder then ends the current recording Session. The current unfinished MP4 segment may not be recoverable or visible in the gallery, while segments finalized before the takeover remain safe.
• Close the rear-seat camera before returning to AVM Recorder, then manually press Start to begin a new Session. Recording does not auto-resume.
• When idle, rear-seat camera use may temporarily make the AVM preview unavailable or report Camera in use. Close the rear-seat camera, then switch tabs or use Start → Stop to rebuild the AVM preview.
• A one-minute segment length is recommended to bound potential loss of the current unfinished segment.

This behaviour is tracked as a confirmed platform/resource conflict in #9, not as a resolved software fix.

Install and integrity

• Package: io.github.dantenothing.openavmrecorder
• Version: 0.1.1-rc4 (versionCode 9)
• Build identity shown in Settings: 3674d3c
• APK SHA-256: 694F4A934DAAF3C3179F617DA369735C63FF2F11FC557C8AA22941B83EA87468
• Signed with the same AVM Recorder release certificate as v0.1.0-alpha.

Thanks to @sharkcreep87 for PRs #6, #7 and #8, and to everyone who supplied real-car reports and retest results.

---

中文说明

这是经过实车验证的 v0.1.1-rc4 候选版，修复了切换页面导致的 Surface abandoned、分段轮换失败和普通场景下的模糊预览问题，并增加“清空全部”和“只删未保护录像”。

目前仅确认原厂后座/车内摄像头存在资源冲突；原厂 360 页面和倒车影像在实车测试中工作正常，不属于此限制。录制期间请勿主动打开后座摄像头：多数情况下后座摄像头会显示流媒体错误而 AVM 继续录像；少数情况下后座摄像头会抢占成功，AVM 当前 Session 随即结束，尚未封口的当前分段可能无法保存，之前已经完成的分段不受影响。关闭后座摄像头后，需要回到 AVM 手动开始新的 Session。建议使用一分钟分段。

AVM Recorder v0.1.0-alpha

First public alpha test build of AVM Recorder.

Highlights

• Experimental surround-view recorder for compatible Zeekr App Lab environments.
• Records the App Lab 1280×5140 composite AVM stream.
• Displays the composite stream as four directional views.
• Includes recording history, protected clips, playback, thumbnails, storage cleanup controls, and English/Chinese UI support.
• Source code is publicly visible for inspection; no project-wide open-source licence is currently granted.
• No root, bootloader unlock, permission bypass, privilege escalation, or system-file modification.

Current test status

• Tested on an Australian Zeekr 7X.
• Approximately four hours of real-world driving and recording testing completed on one vehicle.
• 132 release unit tests passed.
• Release lint completed with 0 errors.
• APK signature verified using APK Signature Scheme v2 and v3.

Download verification

• APK: AVM-Recorder-v0.1.0-alpha.apk
• Size: 1,746,978 bytes
• SHA-256: 756675323c73b9c78d1cf25e6904d436b204e215c6eb7ac24b99a60120841d8f
• Signing certificate SHA-256: 12e528a913c4bad46bc1780f3a0762edb705afbe85f8014aecba1198a030d2e1

Experimental alpha warning

This software is unofficial, experimental, not affiliated with Zeekr, and not endorsed by Zeekr. Use it at your own risk and evaluate suitability for your own vehicle.

Recordings are currently written to internal storage at approximately 200 MB/min. CPU, GPU, memory bandwidth, encoder use, storage I/O, thermal impact, dropped frames, long-term flash wear, and interaction with factory infotainment resources remain under investigation.

Recordings may contain identifiable people, licence plates, homes and travel routes. Users are responsible for applicable privacy and recording laws and should avoid publishing identifiable footage without an appropriate legal basis or consent.

Testing observations do not prove that shared-resource effects or other risks are absent. This build has only been tested on the vehicle configuration described above.