Skip to content

Releases

MegaOpen 1.11.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 16:39

The web installer, and WiFi from it (Improv).

Added

  • Web installer. https://barbedx.github.io/MegaOpen/ (ESP Web Tools, Chrome/Edge) flashes the Latest release, or a newer pre-release, over USB with no Python. A running board goes into download mode from the page («Перевести в режим прошивки», a 1200-baud open of its USB port; no buttons). The image is written around the nvs partition, so settings and WiFi survive. GitHub Pages builds the site after every release (tools/stage_installer.py, .github/workflows/pages.yml); the WebUSB page stays at /usb/.
  • WiFi from the installer (Improv). The firmware speaks Improv Wi-Fi on its USB serial (src/net/Improv.*, ImprovSerial.*): «Встановити» on a running board → «Connect to Wi-Fi» lists the networks it sees, and the board joins the chosen one at once, no reboot, and answers with its address. The network is saved as the first one only after it joined; a wrong password leaves the old one in place. Host test test_improv.

Fixed

  • README's first flash wiped the settings. The whole -factory.bin at 0x0 pads over nvs with 0xFF; README and the release notes now say so and point at the installer.

Built from 38249bd with AffaDisplay@6183b2e.

First flash over USB: the web installer, https://barbedx.github.io/MegaOpen/ (keeps the settings), or esptool write-flash 0x0 megaopen-<env>-1.11.0-factory.bin (wipes them).
Later updates: megaopen-<env>-1.11.0.bin from the board's /update page.
The head unit's app: install megaopen-companion-1.11.0.apk (Android 7+, no root).

Same files as v1.11.0-rc1.

MegaOpen v1.11.0-rc1

MegaOpen v1.11.0-rc1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 08 Nov 16:36

The web installer, and WiFi from it (Improv).

Added

  • Web installer. https://barbedx.github.io/MegaOpen/ (ESP Web Tools, Chrome/Edge) flashes the Latest release, or a newer pre-release, over USB with no Python. A running board goes into download mode from the page («Перевести в режим прошивки», a 1200-baud open of its USB port; no buttons). The image is written around the nvs partition, so settings and WiFi survive. GitHub Pages builds the site after every release (tools/stage_installer.py, .github/workflows/pages.yml); the WebUSB page stays at /usb/.
  • WiFi from the installer (Improv). The firmware speaks Improv Wi-Fi on its USB serial (src/net/Improv.*, ImprovSerial.*): «Встановити» on a running board → «Connect to Wi-Fi» lists the networks it sees, and the board joins the chosen one at once, no reboot, and answers with its address. The network is saved as the first one only after it joined; a wrong password leaves the old one in place. Host test test_improv.

Fixed

  • README's first flash wiped the settings. The whole -factory.bin at 0x0 pads over nvs with 0xFF; README and the release notes now say so and point at the installer.

Built from 38249bd with AffaDisplay@6183b2e.

First flash over USB: the web installer, https://barbedx.github.io/MegaOpen/ (keeps the settings), or esptool write-flash 0x0 megaopen-<env>-1.11.0-factory.bin (wipes them).
Later updates: megaopen-<env>-1.11.0.bin from the board's /update page.
The head unit's app: install megaopen-companion-1.11.0.apk (Android 7+, no root).

MegaOpen 1.10.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 11:53

MegaOpen Companion over Bluetooth, and now playing from the head unit's apps with the cover.

Added

  • MegaOpen Companion over Bluetooth. The app reaches the board over BLE as it does over USB: one GATT service (4d4f0100-…) carries the same frames (the settings page, the alerts, the board's internet). It runs in every Bluetooth mode but «Вимкнено»; the new mode «Лише апка на ГУ» (bleMode app) is the link alone. The first write bonds (an encrypted link only). WiFi is not touched by it: the log push and the GitHub update go through the app over BLE only when the board's WiFi is offline (the head unit's hotspot gone to 5 GHz). docs/design/usb-link.md «Over Bluetooth LE». In the app: «Підключення» Авто (USB → Bluetooth → WiFi) / only one, the board picker, the next retry on screen.
  • Now playing from the head unit's apps. Companion reads the playing media session on the head unit (Spotify, YouTube Music, a radio app, DUDU's player when it publishes one) and posts it (POST /api/app/media, POST /api/app/art): title, artist, album, the player's name, play state and position, and the cover as a 48×48 one-bit picture. «Джерело треку» has «апка на ГУ»; «авто» takes the app first while it plays, then the head unit's own text, then the iPhone. The pane's new scene «обкладинка» shows the cover (the Media scene until there is one); the glass preview on «Екран» shows it too. Host test test_appmedia. docs/design/companion-media.md.
  • /api/health chain app (app_usb, app_ble, app_none, app_none_ble_off, with mediaPosts, mediaAgoMs) and its row «Апка на ГУ» on «Огляд»; /api/status linkVia and ble beside usb; log tag [link].

Changed

  • The link's code is one session over two transports: src/link/LinkSession.* (HELLO, the channels to httpd, the events, the app's internet), UsbPipe.*, BlePipe.*, served by one task applink (was usblink) in AppLink.*; UsbLink.* is gone. The frame buffers moved from DRAM to PSRAM: 3.5 kB less static DRAM than 1.9.0.
  • /api/status usb: the session counters as before, plus up and lastRxAgoMs.

Fixed

  • «Перевірити» and «Встановити» (GitHub update) refused with fw_ap whenever the board's WiFi was not connected, even with the app on the link offering its internet: now any way out counts (WiFi, or Companion over USB or Bluetooth). Its words say so.

Built from dfeee4f with AffaDisplay@6183b2e.

First flash over USB: esptool.py write_flash 0x0 megaopen-<env>-1.10.0-factory.bin.
Later updates: megaopen-<env>-1.10.0.bin from the board's /update page.
The head unit's app: install megaopen-companion-1.10.0.apk (Android 7+, no root).

Same files as v1.10.0-rc2.

MegaOpen v1.10.0-rc2

MegaOpen v1.10.0-rc2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 07 Nov 22:45

MegaOpen Companion over Bluetooth, and now playing from the head unit's apps with the cover.

Added

  • MegaOpen Companion over Bluetooth. The app reaches the board over BLE as it does over USB: one GATT service (4d4f0100-…) carries the same frames (the settings page, the alerts, the board's internet). It runs in every Bluetooth mode but «Вимкнено»; the new mode «Лише апка на ГУ» (bleMode app) is the link alone. The first write bonds (an encrypted link only). WiFi is not touched by it: the log push and the GitHub update go through the app over BLE only when the board's WiFi is offline (the head unit's hotspot gone to 5 GHz). docs/design/usb-link.md «Over Bluetooth LE». In the app: «Підключення» Авто (USB → Bluetooth → WiFi) / only one, the board picker, the next retry on screen.
  • Now playing from the head unit's apps. Companion reads the playing media session on the head unit (Spotify, YouTube Music, a radio app, DUDU's player when it publishes one) and posts it (POST /api/app/media, POST /api/app/art): title, artist, album, the player's name, play state and position, and the cover as a 48×48 one-bit picture. «Джерело треку» has «апка на ГУ»; «авто» takes the app first while it plays, then the head unit's own text, then the iPhone. The pane's new scene «обкладинка» shows the cover (the Media scene until there is one); the glass preview on «Екран» shows it too. Host test test_appmedia. docs/design/companion-media.md.
  • /api/health chain app (app_usb, app_ble, app_none, app_none_ble_off, with mediaPosts, mediaAgoMs) and its row «Апка на ГУ» on «Огляд»; /api/status linkVia and ble beside usb; log tag [link].

Changed

  • The link's code is one session over two transports: src/link/LinkSession.* (HELLO, the channels to httpd, the events, the app's internet), UsbPipe.*, BlePipe.*, served by one task applink (was usblink) in AppLink.*; UsbLink.* is gone. The frame buffers moved from DRAM to PSRAM: 3.5 kB less static DRAM than 1.9.0.
  • /api/status usb: the session counters as before, plus up and lastRxAgoMs.

Fixed

  • «Перевірити» and «Встановити» (GitHub update) refused with fw_ap whenever the board's WiFi was not connected, even with the app on the link offering its internet: now any way out counts (WiFi, or Companion over USB or Bluetooth). Its words say so.

Built from dfeee4f with AffaDisplay@6183b2e.

First flash over USB: esptool.py write_flash 0x0 megaopen-<env>-1.10.0-factory.bin.
Later updates: megaopen-<env>-1.10.0.bin from the board's /update page.
The head unit's app: install megaopen-companion-1.10.0.apk (Android 7+, no root).

MegaOpen v1.10.0-rc1

MegaOpen v1.10.0-rc1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 07 Nov 22:30

MegaOpen Companion over Bluetooth, and now playing from the head unit's apps with the cover.

Added

  • MegaOpen Companion over Bluetooth. The app reaches the board over BLE as it does over USB: one GATT service (4d4f0100-…) carries the same frames (the settings page, the alerts, the board's internet). It runs in every Bluetooth mode but «Вимкнено»; the new mode «Лише апка на ГУ» (bleMode app) is the link alone. The first write bonds (an encrypted link only). WiFi is not touched by it: the log push and the GitHub update go through the app over BLE only when the board's WiFi is offline (the head unit's hotspot gone to 5 GHz). docs/design/usb-link.md «Over Bluetooth LE». In the app: «Підключення» Авто (USB → Bluetooth → WiFi) / only one, the board picker, the next retry on screen.
  • Now playing from the head unit's apps. Companion reads the playing media session on the head unit (Spotify, YouTube Music, a radio app, DUDU's player when it publishes one) and posts it (POST /api/app/media, POST /api/app/art): title, artist, album, the player's name, play state and position, and the cover as a 48×48 one-bit picture. «Джерело треку» has «апка на ГУ»; «авто» takes the app first while it plays, then the head unit's own text, then the iPhone. The pane's new scene «обкладинка» shows the cover (the Media scene until there is one); the glass preview on «Екран» shows it too. Host test test_appmedia. docs/design/companion-media.md.
  • /api/health chain app (app_usb, app_ble, app_none, app_none_ble_off, with mediaPosts, mediaAgoMs) and its row «Апка на ГУ» on «Огляд»; /api/status linkVia and ble beside usb; log tag [link].

Changed

  • The link's code is one session over two transports: src/link/LinkSession.* (HELLO, the channels to httpd, the events, the app's internet), UsbPipe.*, BlePipe.*, served by one task applink (was usblink) in AppLink.*; UsbLink.* is gone. The frame buffers moved from DRAM to PSRAM: 3.5 kB less static DRAM than 1.9.0.
  • /api/status usb: the session counters as before, plus up and lastRxAgoMs.

Built from 179d9af with AffaDisplay@6183b2e.

First flash over USB: esptool.py write_flash 0x0 megaopen-<env>-1.10.0-factory.bin.
Later updates: megaopen-<env>-1.10.0.bin from the board's /update page.
The head unit's app: install megaopen-companion-1.10.0.apk (Android 7+, no root).

MegaOpen 1.9.0

Choose a tag to compare

@github-actions github-actions released this 03 Nov 22:28

The panel role (radio emulator or radio extension) and the clean-out of what older firmware left behind.

Changed

  • The board's role on the display bus, named. «Реєструвати щиток» (funcReg, a switch read in seven places) is now one setting with two values, panelRole: Емулятор магнітоли (emulator, no stock radio: the board is the radio) or Доповнення магнітоли (extension, the stock radio stays and the board draws over it). Екран → Панель → «Роль на шині», applied by a restart; the update turns the old switch into the role (on = emulator, off = extension) and removes the old key. The role is applied in one place (App::Panel::begin: the library's passive mode for the extension), and the extension role's own work lives in one module (app/StockRadio).

  • The radio code exists in the extension role only. In the emulator role radioCode is not sent by GET /api/settings, not shown, and a POST is refused as radioCode: role; nothing about a stock radio runs.

  • The bus watch reports, it no longer decides. The emulator used to go silent (passive, TX off, listen-only) for 30 s windows whenever another master synced, then probe again, and held its TX gate shut for a 3 s listen window at boot. Now the board does what its role says, and the watch only tells when the bus disagrees: health panel_foreign_master (emulator, another radio syncs) and the new panel_no_radio (extension, no stock radio heard), one [panel] line per change. The library's own TX gate (nobody ACKs) is unchanged.

  • Stored settings migrate in one place. src/cfg/Migrations.* rewrites what older firmware stored into today's NVS keys before Config reads any, one numbered step per format change (the recipe is in Migrations.h); Config itself reads and writes only today's keys, and tools/check_rules.py fails on a key it reads but never writes. A step removes the keys it replaces in the same step: nothing is left behind for later (a rollback finds those settings at their defaults). Schema v4: funcReg becomes panelRole; removed with it everything older firmware left in NVS (funcReg, the car screen's index keys carSig0..2/carSigV, 1.6.1's gr1..5, 1.6.x's tables decode/huFmap/alerts/macros). Host test test_migrations. The old steps v1/v2 only set defaults on fresh boards and are gone: a fresh board's notification popup is now off, as Settings.h always said.

  • Findings go to the backlog. docs/BACKLOG.md → «Findings» collects every inconsistency, bug or suspicion an agent sees, for the owner's sweeps (CLAUDE.md says so).

Removed

  • POST /api/display (it wrote displayType and funcReg beside the registry): both are registry entries, POST /api/settings. GET /api/display has role instead of funcReg.
  • The 1.6.x import. A board updating straight from 1.6.x no longer carries its decode map, head-unit field map, alerts and macros into /cfg/car.json (every board is past 1.7, where that happened): gone are CarStore's import, Config's readers of those NVS tables, DecodeTable::pack/unpack, FieldMap::pack/unpack, Rules::fromAlertBlob/fromMacroBlob and Vehicle::sigFromSaved. A board with no car file starts from the factory's.

Built from de349c5 with AffaDisplay@6183b2e.

First flash over USB: esptool.py write_flash 0x0 megaopen-<env>-1.9.0-factory.bin.
Later updates: megaopen-<env>-1.9.0.bin from the board's /update page.
The head unit's app: install megaopen-companion-1.9.0.apk (Android 7+, no root).

Same files as v1.9.0-rc1.

MegaOpen v1.9.0-rc1

MegaOpen v1.9.0-rc1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Nov 22:25

The panel role (radio emulator or radio extension) and the clean-out of what older firmware left behind.

Changed

  • The board's role on the display bus, named. «Реєструвати щиток» (funcReg, a switch read in seven places) is now one setting with two values, panelRole: Емулятор магнітоли (emulator, no stock radio: the board is the radio) or Доповнення магнітоли (extension, the stock radio stays and the board draws over it). Екран → Панель → «Роль на шині», applied by a restart; the update turns the old switch into the role (on = emulator, off = extension) and removes the old key. The role is applied in one place (App::Panel::begin: the library's passive mode for the extension), and the extension role's own work lives in one module (app/StockRadio).

  • The radio code exists in the extension role only. In the emulator role radioCode is not sent by GET /api/settings, not shown, and a POST is refused as radioCode: role; nothing about a stock radio runs.

  • The bus watch reports, it no longer decides. The emulator used to go silent (passive, TX off, listen-only) for 30 s windows whenever another master synced, then probe again, and held its TX gate shut for a 3 s listen window at boot. Now the board does what its role says, and the watch only tells when the bus disagrees: health panel_foreign_master (emulator, another radio syncs) and the new panel_no_radio (extension, no stock radio heard), one [panel] line per change. The library's own TX gate (nobody ACKs) is unchanged.

  • Stored settings migrate in one place. src/cfg/Migrations.* rewrites what older firmware stored into today's NVS keys before Config reads any, one numbered step per format change (the recipe is in Migrations.h); Config itself reads and writes only today's keys, and tools/check_rules.py fails on a key it reads but never writes. A step removes the keys it replaces in the same step: nothing is left behind for later (a rollback finds those settings at their defaults). Schema v4: funcReg becomes panelRole; removed with it everything older firmware left in NVS (funcReg, the car screen's index keys carSig0..2/carSigV, 1.6.1's gr1..5, 1.6.x's tables decode/huFmap/alerts/macros). Host test test_migrations. The old steps v1/v2 only set defaults on fresh boards and are gone: a fresh board's notification popup is now off, as Settings.h always said.

  • Findings go to the backlog. docs/BACKLOG.md → «Findings» collects every inconsistency, bug or suspicion an agent sees, for the owner's sweeps (CLAUDE.md says so).

Removed

  • POST /api/display (it wrote displayType and funcReg beside the registry): both are registry entries, POST /api/settings. GET /api/display has role instead of funcReg.
  • The 1.6.x import. A board updating straight from 1.6.x no longer carries its decode map, head-unit field map, alerts and macros into /cfg/car.json (every board is past 1.7, where that happened): gone are CarStore's import, Config's readers of those NVS tables, DecodeTable::pack/unpack, FieldMap::pack/unpack, Rules::fromAlertBlob/fromMacroBlob and Vehicle::sigFromSaved. A board with no car file starts from the factory's.

Built from de349c5 with AffaDisplay@6183b2e.

First flash over USB: esptool.py write_flash 0x0 megaopen-<env>-1.9.0-factory.bin.
Later updates: megaopen-<env>-1.9.0.bin from the board's /update page.
The head unit's app: install megaopen-companion-1.9.0.apk (Android 7+, no root).

MegaOpen 1.8.0

Choose a tag to compare

@github-actions github-actions released this 03 Nov 15:16

The stabilisation release: the review of 2026-11-03 (the architecture behind the heap corruptions) implemented, plus the stock radio's code.

Added

  • The stock radio's code, typed for you. With «Реєструвати щиток» off (the OEM radio drives the panel), the radio asks for its four-digit code on the panel after the battery was off. Плата → Система → «Код магнітоли» (radioCode, NVS; empty = off): when the prompt appears (" CODE " on 0x151, then the entry field with the 0xB0 cursor, as the car's captures show), the board types it on the bus as the stalk would, one key frame every 160 ms — the wheel up per digit, the bottom button to the next place, held to confirm. One attempt per prompt and never two within a minute (the radio waits longer after every wrong code); the screen's verdict goes to the log, tag code (typed, accepted, rejected, skipped). The logic is pure (src/display/RadioCode.*), host-tested against the captured frames.
  • The heap diagnostic build. PLATFORMIO_BUILD_FLAGS=-DHEAP_SENTINEL=1 (src/utils/HeapSentinel.h) walks the heap at every network step, around every web route and every 500 ms, and on a hit logs the address, the step, the task and the bytes around it before the coredump. It replaces HEAP_HUNT (2026-10-19). Not in the release image.

Changed

  • One network worker. The log push and the GitHub update each created a task per job (10 kB and 8 kB of internal stack, every minute for the push) and deleted it after, serialised by a mutex and a 100 ms poll (TlsJob). The bench's heap corruption of 2026-11-01 sat in exactly the hole those stacks churned. Both jobs now run on netjob, one task for the whole boot with a queue; its 8 kB stack is taken from the internal heap once, at the first job, and kept (a static one moved the heap under the OTA trial's floor: rc1 never confirmed). A check or install pressed during a push waits its turn as before (queued); the push's heap floor is 30 kB now that the stack is already there (it was 40 kB with the stack still to take). The error code tls_busy is gone; push_busy says the worker's queue was full.
  • Settings hold no Strings. Every text in Settings is a fixed Cfg::Text<N>: a copy is a copy, and a reader on another task can never find a freed buffer behind a field (the car task's resolveCarSigs read one while httpd's save() reassigned it; WifiManager read mdnsName on net_svc). The settings lock is for the writers now.
  • Web replies stream. 28 routes built the whole reply as a String on httpd (2 kB realloc steps in internal heap, under the settings lock) and 59 documents took their pools there: a document now goes straight into the chunked reply (replyDoc), every document on httpd allocates in PSRAM, and the head-unit ring (/api/canbox/last) streams too.
  • The formula parser caps nesting. Brackets, calls and chains of nots recursed with no limit (127 brackets in a rule were 12–40 kB of recursion on the car task's 4 kB stack): past Program::MAX_NEST (about five levels) a formula is refused as expr_deep. The car task never takes the blocking settings lock (tryLock, retried next pass), its stack is 6 kB, and tools/check_rules.py checks its functions in main.cpp. The stacks that lived outside TaskPlan.h (logbus, capwr, bt_begin) are in it.
  • One of each. utils/PsHeap.h is the one "PSRAM, else internal" allocator (ten copies before); utils/Hex.h the one hex digit (five); utils/JsonEscape.h the one JSON string escape (three, two of which let a control byte through into /api/catalog and the head-unit ring). LogFile::path fills the caller's buffer instead of handing one static buffer to every task; the pane copies its Custom picture, so the web's copy of it is whole; the request gate uses the boot's mDNS name without a lock (nothing renames it: it is not in the registry); the log push can no longer spin on a flash-log stretch with no line end.

Removed

  • Functions with no callers: WebUi::addRoute, Registry::enumName, Keys::laneName, Log::statusInterval, Rav4Emitter::msgEnabled, LogFile::requestFlush; src/net/TlsJob.*; HEAP_HUNT.

Built from 288740b with AffaDisplay@6183b2e.

First flash over USB: esptool.py write_flash 0x0 megaopen-<env>-1.8.0-factory.bin.
Later updates: megaopen-<env>-1.8.0.bin from the board's /update page.
The head unit's app: install megaopen-companion-1.8.0.apk (Android 7+, no root).

Same files as v1.8.0-rc2.

MegaOpen v1.8.0-rc2

MegaOpen v1.8.0-rc2 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Nov 15:13

The stabilisation release: the review of 2026-11-03 (the architecture behind the heap corruptions) implemented, plus the stock radio's code.

Added

  • The stock radio's code, typed for you. With «Реєструвати щиток» off (the OEM radio drives the panel), the radio asks for its four-digit code on the panel after the battery was off. Плата → Система → «Код магнітоли» (radioCode, NVS; empty = off): when the prompt appears (" CODE " on 0x151, then the entry field with the 0xB0 cursor, as the car's captures show), the board types it on the bus as the stalk would, one key frame every 160 ms — the wheel up per digit, the bottom button to the next place, held to confirm. One attempt per prompt and never two within a minute (the radio waits longer after every wrong code); the screen's verdict goes to the log, tag code (typed, accepted, rejected, skipped). The logic is pure (src/display/RadioCode.*), host-tested against the captured frames.
  • The heap diagnostic build. PLATFORMIO_BUILD_FLAGS=-DHEAP_SENTINEL=1 (src/utils/HeapSentinel.h) walks the heap at every network step, around every web route and every 500 ms, and on a hit logs the address, the step, the task and the bytes around it before the coredump. It replaces HEAP_HUNT (2026-10-19). Not in the release image.

Changed

  • One network worker. The log push and the GitHub update each created a task per job (10 kB and 8 kB of internal stack, every minute for the push) and deleted it after, serialised by a mutex and a 100 ms poll (TlsJob). The bench's heap corruption of 2026-11-01 sat in exactly the hole those stacks churned. Both jobs now run on netjob, one task for the whole boot with a queue; its 8 kB stack is taken from the internal heap once, at the first job, and kept (a static one moved the heap under the OTA trial's floor: rc1 never confirmed). A check or install pressed during a push waits its turn as before (queued); the push's heap floor is 30 kB now that the stack is already there (it was 40 kB with the stack still to take). The error code tls_busy is gone; push_busy says the worker's queue was full.
  • Settings hold no Strings. Every text in Settings is a fixed Cfg::Text<N>: a copy is a copy, and a reader on another task can never find a freed buffer behind a field (the car task's resolveCarSigs read one while httpd's save() reassigned it; WifiManager read mdnsName on net_svc). The settings lock is for the writers now.
  • Web replies stream. 28 routes built the whole reply as a String on httpd (2 kB realloc steps in internal heap, under the settings lock) and 59 documents took their pools there: a document now goes straight into the chunked reply (replyDoc), every document on httpd allocates in PSRAM, and the head-unit ring (/api/canbox/last) streams too.
  • The formula parser caps nesting. Brackets, calls and chains of nots recursed with no limit (127 brackets in a rule were 12–40 kB of recursion on the car task's 4 kB stack): past Program::MAX_NEST (about five levels) a formula is refused as expr_deep. The car task never takes the blocking settings lock (tryLock, retried next pass), its stack is 6 kB, and tools/check_rules.py checks its functions in main.cpp. The stacks that lived outside TaskPlan.h (logbus, capwr, bt_begin) are in it.
  • One of each. utils/PsHeap.h is the one "PSRAM, else internal" allocator (ten copies before); utils/Hex.h the one hex digit (five); utils/JsonEscape.h the one JSON string escape (three, two of which let a control byte through into /api/catalog and the head-unit ring). LogFile::path fills the caller's buffer instead of handing one static buffer to every task; the pane copies its Custom picture, so the web's copy of it is whole; the request gate uses the boot's mDNS name without a lock (nothing renames it: it is not in the registry); the log push can no longer spin on a flash-log stretch with no line end.

Removed

  • Functions with no callers: WebUi::addRoute, Registry::enumName, Keys::laneName, Log::statusInterval, Rav4Emitter::msgEnabled, LogFile::requestFlush; src/net/TlsJob.*; HEAP_HUNT.

Built from 288740b with AffaDisplay@6183b2e.

First flash over USB: esptool.py write_flash 0x0 megaopen-<env>-1.8.0-factory.bin.
Later updates: megaopen-<env>-1.8.0.bin from the board's /update page.
The head unit's app: install megaopen-companion-1.8.0.apk (Android 7+, no root).

MegaOpen v1.8.0-rc1

MegaOpen v1.8.0-rc1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Nov 14:56

The stabilisation release: the review of 2026-11-03 (the architecture behind the heap corruptions) implemented, plus the stock radio's code.

Added

  • The stock radio's code, typed for you. With «Реєструвати щиток» off (the OEM radio drives the panel), the radio asks for its four-digit code on the panel after the battery was off. Плата → Система → «Код магнітоли» (radioCode, NVS; empty = off): when the prompt appears (" CODE " on 0x151, then the entry field with the 0xB0 cursor, as the car's captures show), the board types it on the bus as the stalk would, one key frame every 160 ms — the wheel up per digit, the bottom button to the next place, held to confirm. One attempt per prompt and never two within a minute (the radio waits longer after every wrong code); the screen's verdict goes to the log, tag code (typed, accepted, rejected, skipped). The logic is pure (src/display/RadioCode.*), host-tested against the captured frames.
  • The heap diagnostic build. PLATFORMIO_BUILD_FLAGS=-DHEAP_SENTINEL=1 (src/utils/HeapSentinel.h) walks the heap at every network step, around every web route and every 500 ms, and on a hit logs the address, the step, the task and the bytes around it before the coredump. It replaces HEAP_HUNT (2026-10-19). Not in the release image.

Changed

  • One network worker. The log push and the GitHub update each created a task per job (10 kB and 8 kB of internal stack, every minute for the push) and deleted it after, serialised by a mutex and a 100 ms poll (TlsJob). The bench's heap corruption of 2026-11-01 sat in exactly the hole those stacks churned. Both jobs now run on netjob, one task for the whole boot with a static stack and a queue; a check or install pressed during a push waits its turn as before (queued). The error code tls_busy is gone; push_busy says the worker's queue was full.
  • Settings hold no Strings. Every text in Settings is a fixed Cfg::Text<N>: a copy is a copy, and a reader on another task can never find a freed buffer behind a field (the car task's resolveCarSigs read one while httpd's save() reassigned it; WifiManager read mdnsName on net_svc). The settings lock is for the writers now.
  • Web replies stream. 28 routes built the whole reply as a String on httpd (2 kB realloc steps in internal heap, under the settings lock) and 59 documents took their pools there: a document now goes straight into the chunked reply (replyDoc), every document on httpd allocates in PSRAM, and the head-unit ring (/api/canbox/last) streams too.
  • The formula parser caps nesting. Brackets, calls and chains of nots recursed with no limit (127 brackets in a rule were 12–40 kB of recursion on the car task's 4 kB stack): past Program::MAX_NEST (about five levels) a formula is refused as expr_deep. The car task never takes the blocking settings lock (tryLock, retried next pass), its stack is 6 kB, and tools/check_rules.py checks its functions in main.cpp. The stacks that lived outside TaskPlan.h (logbus, capwr, bt_begin) are in it.
  • One of each. utils/PsHeap.h is the one "PSRAM, else internal" allocator (ten copies before); utils/Hex.h the one hex digit (five); utils/JsonEscape.h the one JSON string escape (three, two of which let a control byte through into /api/catalog and the head-unit ring). LogFile::path fills the caller's buffer instead of handing one static buffer to every task; the pane copies its Custom picture, so the web's copy of it is whole; the request gate uses the boot's mDNS name without a lock (nothing renames it: it is not in the registry); the log push can no longer spin on a flash-log stretch with no line end.

Removed

  • Functions with no callers: WebUi::addRoute, Registry::enumName, Keys::laneName, Log::statusInterval, Rav4Emitter::msgEnabled, LogFile::requestFlush; src/net/TlsJob.*; HEAP_HUNT.

Built from a71233f with AffaDisplay@6183b2e.

First flash over USB: esptool.py write_flash 0x0 megaopen-<env>-1.8.0-factory.bin.
Later updates: megaopen-<env>-1.8.0.bin from the board's /update page.
The head unit's app: install megaopen-companion-1.8.0.apk (Android 7+, no root).