Point release on top of v0.6.1. Two bug fixes, no new features. Firmware identity is now 0.6.2.
\nRunning a path trace in 2-byte mode returned a wrong result. The response was parsed as if it were 1-byte, so it reported twice as many hops as actually existed, each one resolved to the wrong repeater. As an example, a two-hop 2-byte trace of 3601,2198 came back as four hops (36, 01, 21, 98) matched against unrelated repeaters.
The cause was in the trace-response handler: the hop count and hash size were taken from the wrong source. The byte length handed up from the base layer was being read with the packet-header path encoding, which collapses to 1-byte mode for any short path. The real hash size is carried separately in the trace flags.
\nThe handler now reads the hash size from the trace flags and computes the hop count as the path byte length divided by bytes-per-hop. 1-byte traces were already correct and are unchanged. 2-byte traces now report the right hop count and resolve to the correct repeaters.
\nCustom per-channel notification tones stopped playing as of v0.6 (they worked in v0.5). A tone could be selected and would show as set, but nothing played when a message arrived on that channel.
\nThe cause was the v0.6 audio rework, which split file preparation from playback start. The notification trigger prepared the tone file but never issued the start, so it sat ready and silent.
\nThe notification path now starts playback after preparing. The same missing start also affected the tone-picker preview and voice-message playback, both fixed by the same change.
\n3 files changed (MeckMesh.h, MeckUI.cpp, meck.h).
Meck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.
\n\nAn SD card is recommended. With a FAT32-formatted card inserted, every saved setting, channel message, DM, room post, and note is mirrored or stored on the card, notification tones have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot, and the Reader, Notes, and notification sounds have no storage.
\n
Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.\n
meck-p4-0.6.2.bin file you downloadedpip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.6.2.bin\n(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)
Upgrading from v0.6.1 or v0.6 does not require erase_flash. This patch changes program logic only and adds no new settings, so existing prefs carry over unchanged.
For the full feature list see the README.
\nThe Meck-P4 channel on the MeshCore Discord is the fastest path. GitHub Issues on the Meck-P4 repo also work for anything reproducible. Include the serial log if you can: Settings > Debug Logs > Start capt\n…
\n" }, { "version": "v0.6.1-patch", "name": "Meck P4 v0.6.1 Pre-release (Patch): Antenna switch", "datetime": "2026-06-10T03:42:22Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.6.1-patch", "prerelease": true, "notes": "Point release on top of [v0.6](https://github.com/pelgraine/Meck-P4/releases/tag/v0.6), adding a software LoRa antenna selector in Settings. No other functional changes. Firmware identity is now 0.6.1.\r\n\r\n## Antenna Switch\r\n\r\nA new **Antenna (tap to toggle)** row at the top of **Settings**, switching the SX1262 between the two ports on the SKY13453 RF switch (XL9535 IO1 / VCTL).\r\n\r\n- **Internal (RF1)** is the default and corresponds to VCTL HIGH; **External (RF2)** is VCTL LOW. The internal antenna is the one in use when no external antenna is attached, so the device works out of the box without changing this.\r\n- The choice persists via prefs (NVS, mirrored to SD) and is re-applied at boot, so the selected port survives a reboot.\r\n- Tap applies live: the pin is driven immediately and the row label updates to show the active port.\r\n\r\n## Bug Fixes\r\n\r\nNone.\r\n\r\n## Files Changed\r\n\r\n5 files changed.\r\n\r\n## First-Time Flashing: Read This First\r\n\r\nMeck-P4 ships as a single **merged binary** (bootloader + partition table + application combined). One file, flash at offset `0x0`.\r\n> **An SD card is recommended.** With a FAT32-formatted card inserted, every saved setting, channel message, DM, room post, and note is mirrored or stored on the card, notification tones have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot, and the Reader, Notes, and notification sounds have no storage.\r\n\r\nEnsure you use the **right-side USB-C port** (the data port), not the high-speed charger port, to flash.\r\n\r\n### Flashing with the MeshCore Web Flasher (recommended)\r\n\r\n1. Go toPoint release on top of v0.6, adding a software LoRa antenna selector in Settings. No other functional changes. Firmware identity is now 0.6.1.
\nA new Antenna (tap to toggle) row at the top of Settings, switching the SX1262 between the two ports on the SKY13453 RF switch (XL9535 IO1 / VCTL).
\nNone.
\n5 files changed.
\nMeck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.
\n\nAn SD card is recommended. With a FAT32-formatted card inserted, every saved setting, channel message, DM, room post, and note is mirrored or stored on the card, notification tones have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot, and the Reader, Notes, and notification sounds have no storage.
\n
Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.
\nmeck-p4-0.6.1.bin file you downloadedpip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.6.1.bin\n(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)
Upgrading from v0.6 does not require erase_flash. The prefs loader tolerates the older layout, and the new antenna field comes up at its default (Internal).
For the full feature list see the README.
\nThe Meck-P4 channel on the MeshCore Discord is the fastest path. GitHub Issues on the Meck-P4 repo also work for anything reproducible. Include the serial log if you can: Settings > Debug Logs > Start captures it to SD if a serial monitor isn't practical.
\nMIT for Meck-specific code. The combined firmware binary links libraries with mixed licensing including GPL-3.0 and LGPL-2.1 (Codec2) and is effectively GPL-3.0 when distributed.
\n" }, { "version": "v0.6", "name": "Meck P4 v0.6 Pre-release: Web reader, Notes, and EPUB books", "datetime": "2026-06-09T22:14:40Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.6", "prerelease": true, "notes": "Feature release building on v0.5, adding a reader-mode web browser over the ESP32-C6, a Notes app, EPUB book support in the reader, a Cyrillic keyboard layout, optional M5Stack CardKB hardware-keyboard support, and a portrait/landscape orientation toggle, alongside several bug fixes. Firmware identity is now 0.6.\r\n\r\n## Web Reader\r\n\r\nA lightweight reader-mode web browser on the new **Web** home tile, running over the onboard ESP32-C6. It drives the C6 directly over ESP-AT, building its HTTP and TLS requests by hand, so it shares the WiFi companion's C6 link but uses its own request path. The C6 must be connected to WiFi for it to fetch anything.\r\n\r\n- Landing menu with **Enter URL**, a **DuckDuckGo Lite** search, **Bookmarks**, and **History**.\r\n- Reader view: pages are parsed to readable text with a status line. Headings render in dark red; link markers show as a muted grey `[N]` and are followed from the **Links** panel.\r\n- HTTPS support, confirmed against DuckDuckGo Lite.\r\n- GET form fill: an orange **Forms (N)** button opens a picker (duplicate forms collapsed), then a fill modal with a labelled field per text or password input. Submitting builds the `action?name=value&...` query and loads it through the normal page path, so history and status stay correct.\r\n- Bookmarks (added from the reader view with a confirmation toast) and History.\r\n- This is a **work in progress**: an amber notice appears for a few seconds each time the Web tile is opened. See Known Limitations below and the README for the full list.\r\n\r\n## EPUB Reading\r\n\r\nThe reader now opens **EPUB (`.epub`)** files in addition to plain text. The file list shows folders, `.txt`, and `.epub` items.\r\n\r\n- Tapping an EPUB converts it to plain text the first time it is opened. A *Converting ... to txt* screen is shown while the book is decoded.\r\n- The result is cached as a `.txt` in a hidden `.epub_cache` subfolder, so re-opening the same EPUB later loads straight from the cache and the conversion only runs once.\r\n- You only ever see and tap the `.epub` itself; the cached text stays hidden from the browser.\r\n\r\n## Notes\r\n\r\nA Notes app on the **Notes** home tile. Notes are plain UTF-8 `.txt` files stored under `/sdcard/notes`, so they live on the removable card, survive a reflash, and can be read or edited on a computer. The folder is created automatically on first run.\r\n\r\n- Browser modelled on the reader's: folder navigation, an up-one-level button, and a breadcrumb, rooted at `/sdcard/notes`. A green **+ New Note** row sits at the top of every folder.\r\n- Create and edit with the on-screen keyboard (which honours the KB Theme and KB Layout settings). New notes are named by date and time when the clock is synced (`note_YYYYMMDD_HHMM.txt`), or sequentially (`note_NNN.txt`) otherwise.\r\n- Read view reuses the reader's paging: left third of the screen turns back, right two-thirds turns forward, with a progress percentage and a saved-position bookmark.\r\n- Long-press a note for an action menu with **Rename**, **Delete** (with confirmation), and **Cancel**.\r\n\r\n## Cyrillic Keyboard\r\n\r\nA fourth on-screen keyboard layout, **ЙЦУКЕН** (Cyrillic), added to the **Settings > KB Layout** cycle alongside QWERTY, AZERTY, and QWERTZ.\r\n\r\n- Standard Russian arrangement, also commonly used by Bulgarian users. The top three rows carry twelve letters each, with ё on the third row.\r\n- The control keys keep their Latin labels (ABC / abc / 1#) so case and number switching still work.\r\n- Ukrainian and Serbian letter sets are not included. The Settings row shows \"ЙЦУКЕН\" when this layout is active.\r\n\r\n## Physical Keyboard (M5Stack CardKB)\r\n\r\nOptional support for the **M5Stack CardKB**, a small I2C QWERTY keyboard, as an alternative to the on-screen keyboard for typing messages. Gated behind the `MECK_CARDKB` build flag (a build-from-source option).\r\n\r\n- Connects to the board's **P1 connector** (the 1x4 header) as a software-I2C bus on SDA = GPIO 48 and SCL = GPIO 47, at 10 kHz, address 0x5F. Probed for \n…", "notesHtml": "Feature release building on v0.5, adding a reader-mode web browser over the ESP32-C6, a Notes app, EPUB book support in the reader, a Cyrillic keyboard layout, optional M5Stack CardKB hardware-keyboard support, and a portrait/landscape orientation toggle, alongside several bug fixes. Firmware identity is now 0.6.
\nA lightweight reader-mode web browser on the new Web home tile, running over the onboard ESP32-C6. It drives the C6 directly over ESP-AT, building its HTTP and TLS requests by hand, so it shares the WiFi companion's C6 link but uses its own request path. The C6 must be connected to WiFi for it to fetch anything.
\n[N] and are followed from the Links panel.action?name=value&... query and loads it through the normal page path, so history and status stay correct.The reader now opens EPUB (.epub) files in addition to plain text. The file list shows folders, .txt, and .epub items.
.txt in a hidden .epub_cache subfolder, so re-opening the same EPUB later loads straight from the cache and the conversion only runs once..epub itself; the cached text stays hidden from the browser.A Notes app on the Notes home tile. Notes are plain UTF-8 .txt files stored under /sdcard/notes, so they live on the removable card, survive a reflash, and can be read or edited on a computer. The folder is created automatically on first run.
/sdcard/notes. A green + New Note row sits at the top of every folder.note_YYYYMMDD_HHMM.txt), or sequentially (note_NNN.txt) otherwise.A fourth on-screen keyboard layout, ЙЦУКЕН (Cyrillic), added to the Settings > KB Layout cycle alongside QWERTY, AZERTY, and QWERTZ.
\nOptional support for the M5Stack CardKB, a small I2C QWERTY keyboard, as an alternative to the on-screen keyboard for typing messages. Gated behind the MECK_CARDKB build flag (a build-from-source option).
Feature release building on v0.4, adding a plain-text reader, inline colour emoji with a picker, over-the-mesh repeater administration from the companion app, audio player fixes, and draft message saving. Firmware identity is now 0.5.
\n/sdcard/books with subfolder navigation, a breadcrumb, and an up-one-level button..pos sidecar, plus page-back through the pages visited in the current session./sdcard/books root.lv_imgfont) is attached as the fallback of each meck_montserrat_* font, so emoji codepoints the text font can't draw are rendered from baked-in Twemoji images instead of a missing-glyph box. Requires CONFIG_LV_USE_IMGFONT=y.Over-the-mesh repeater administration from the MeshCore app. The app's session state is kept separate from the on-device Repeater Admin screen, so the two can't capture each other's responses.
\nout_path restored afterwards, sync_since reset for room contacts).TXT_TYPE_CLI_DATA). Frame layouts mirror upstream byte-for-byte, so the app parses them with no protocol-version negotiation./sdcard/audio/audiobooks. Music and other audio always start from the beginning, so finishing a short track no longer leaves a near-end position that made it skip on reopen, and no stray bookmark files are written for music.Feature release building on v0.3.8, adding WiFi companion app support, companion protocol compatibility, power optimisation, and stability improvements.
\nExtensive companion protocol implementation for MeshCore app compatibility:
\nMAX_GROUP_CHANNELS).disable_channels() / enable_channels() to Hardware_Iis class so I2S driver PM locks are only held during active audio playback.Feature release building on v0.3.6, adding position adverts, share position, path view, private channels, and voice/picture over LoRa infrastructure (disabled pending final integration).
\nYour GPS position can now be encoded into outgoing adverts, allowing other nodes on the mesh to see your location on their Maps screen. Position is configured via a new Settings > Position sub-screen with three fields:
\nIn Auto-GPS mode, the L76K GPS snapshot is polled every 15 minutes and the stored position is updated automatically whenever the fix changes. A Copy Position button is also available on the sub-screen.
\nThe + button on the channel messages and DM compose screens now includes a Share Position option. Tapping it sends your current lat/lon as a message to the active channel or conversation.
\nLong-pressing an incoming message now opens Path View, which displays the routing path that message took through the mesh, showing each hop in the route.
\nLong-pressing an outgoing message gives you the option to Retry Send if the message failed, or to see which repeaters acknowledged the message.
\nChannels can now be public or private:
\n# (e.g. #test). The secret is derived via SHA-256 from the name, matching the standard MeshCore convention.# prefix. A random 16-byte secret is generated at creation, so only invited users can join.Sharing: open Settings > Channels, tap the channel, then tap Share Channel. This opens a contact picker and sends the channel name and secret as a DM invitation. Recipients see a pending invite they can accept (tap) or dismiss (long-press).
\nThe full infrastructure for Codec2 1200bps voice messaging has been added to the firmware:
\ncomponents/codec2/) wrapping drowe67/codec2 with only the core 1200bps mode compiled inVoice and Picture tiles are present on the home screen as placeholders but the features are disabled in this release pending final integration and testing.
\nChunked image transfer protocol infrastructure has been added but is disabled in this release.
\nMeck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.
\n\nAn SD card is recommended. With a FAT32-formatted card inserted, every saved setting, channel message, DM, and room post is mirrored automatically, notification tones have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot and notification sounds won't be available.
\n
Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.\n<img width=\"377\" height=\"284\" alt=\"correct \n…
\n" }, { "version": "v0.3.6", "name": "Meck-P4 v0.3.6: Custom Radio, Region Scope, Channels, Notification Sounds", "datetime": "2026-05-24T23:38:02Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.3.6", "prerelease": true, "notes": "Pre-release.\r\n\r\nFeature release building on v0.3.5.1, adding custom radio parameters, region scope support, a Channels settings sub-screen, and per-channel notification sounds.\r\n\r\n---\r\n\r\n## What's New\r\n\r\n### Custom Radio Parameters\r\n\r\nFrequency, Bandwidth, and Spreading Factor are now individually editable via text entry in Settings (tap the row, type the value, tap Confirm). Coding Rate cycles on tap (4/5 through 4/8). The Radio Preset row remains available and shows \"Custom\" whenever the current values don't match any of the 17 built-in presets. Selecting a preset populates all four fields; you can then tweak individual values without losing the rest.\r\n\r\nThis is primarily useful for users in regions where the community presets don't cover the exact parameters in use, such as parts of Europe running SR 5/6 with 32.5 kHz bandwidth, or anyone wanting to customise the coding rate independently.\r\n\r\n### Region Scope (MeshCore v1.15+ Compatibility)\r\n\r\nRegions limit how far your flood messages propagate through the mesh. When you set a region, outgoing messages are tagged with a transport code that repeaters use to decide whether to forward them. Messages sent without a region reach all repeaters via the default wildcard, same as always.\r\n\r\n**Setting your device region:**\r\n- Open **Settings**, tap **Default Region**, enter your region name (e.g. `au-nsw`), tap **Confirm**\r\n- Leave empty for unscoped (legacy behaviour, reaches all repeaters)\r\n\r\n**Per-channel region:** Open **Settings > Channels**, tap a channel, then tap **Region Scope** to set an override for that specific channel. Empty uses the device default.\r\n\r\n**Finding your region name:** Region names are determined by your local mesh community. Check with your local group, or browse the community region registry at [regions.meshcore.nz](https://regions.meshcore.nz/) for names already in use. Common patterns follow ISO 3166 codes (e.g. `au` for Australia, `au-nsw`, `gb-eng`, `us-ca`), but communities may also use custom names. Names must be lowercase alphanumeric characters and hyphens, max 30 characters. You can also create your own custom regions on repeaters you manage (see Repeater Admin below).\r\n\r\n**Note:** Region scoping requires repeaters in your area to be running MeshCore v1.10+ with the appropriate regions configured. If no repeaters have region filtering enabled, scoped and unscoped messages behave identically.\r\n\r\n### Repeater Admin: Region Management via CLI\r\n\r\nRepeaters running MeshCore v1.10+ support full region management through the Cmd Line screen in Repeater Admin. Log in to a repeater, tap **Cmd Line**, and use the following commands:\r\n\r\n| Command | Description |\r\n| --- | --- |\r\n| `region putPre-release.
\nFeature release building on v0.3.5.1, adding custom radio parameters, region scope support, a Channels settings sub-screen, and per-channel notification sounds.
\nFrequency, Bandwidth, and Spreading Factor are now individually editable via text entry in Settings (tap the row, type the value, tap Confirm). Coding Rate cycles on tap (4/5 through 4/8). The Radio Preset row remains available and shows \"Custom\" whenever the current values don't match any of the 17 built-in presets. Selecting a preset populates all four fields; you can then tweak individual values without losing the rest.
\nThis is primarily useful for users in regions where the community presets don't cover the exact parameters in use, such as parts of Europe running SR 5/6 with 32.5 kHz bandwidth, or anyone wanting to customise the coding rate independently.
\nRegions limit how far your flood messages propagate through the mesh. When you set a region, outgoing messages are tagged with a transport code that repeaters use to decide whether to forward them. Messages sent without a region reach all repeaters via the default wildcard, same as always.
\nSetting your device region:
\nau-nsw), tap ConfirmPer-channel region: Open Settings > Channels, tap a channel, then tap Region Scope to set an override for that specific channel. Empty uses the device default.
\nFinding your region name: Region names are determined by your local mesh community. Check with your local group, or browse the community region registry at regions.meshcore.nz for names already in use. Common patterns follow ISO 3166 codes (e.g. au for Australia, au-nsw, gb-eng, us-ca), but communities may also use custom names. Names must be lowercase alphanumeric characters and hyphens, max 30 characters. You can also create your own custom regions on repeaters you manage (see Repeater Admin below).
Note: Region scoping requires repeaters in your area to be running MeshCore v1.10+ with the appropriate regions configured. If no repeaters have region filtering enabled, scoped and unscoped messages behave identically.
\nRepeaters running MeshCore v1.10+ support full region management through the Cmd Line screen in Repeater Admin. Log in to a repeater, tap Cmd Line, and use the following commands:
\n| Command | \nDescription | \n
|---|---|
region put <name> [parent] | \nCreate a new region (optional parent for nesting) | \n
region remove <name> | \nRemove a region (remove children first) | \n
region allowf <name> | \nAllow flooding for a region | \n
region denyf <name> | \nBlock flooding for a region | \n
region get <name> | \nShow info for a region | \n
region home / region home <name> | \nView or set the repeater's home region | \n
region default / region default <name> | \nView or set the repeater's default scope | \n
region save | \nPersist region changes to the repeater's flash | \n
region list allowed / region list denied | \nView regions (repeater firmware 1.12+) | \n
region load <name> [F] | \nSingle-line region load (append F to allow flooding) | \n
Not supported: The interactive multi-line region load (without parameters) requires a serial terminal and is not available on the P4, which does not currently support serial CLI commands. Use individual region put and region allowf commands instead.
Quick start example (setting up a repeater for the au-nsw region):
region put au-nsw\nregion allowf au-nsw\nregion home au-nsw\nregion save\nFor full documentation and nested region examples, see the [MeshCore CLI docs](https://docs.meshcore.io/cli_commands/#region-management-v1\n…
\n" }, { "version": "v0.3.5.1", "name": "Meck-P4 v0.3.5.1: Contacts list fixes", "datetime": "2026-05-22T19:34:27Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.3.5.1", "prerelease": true, "notes": "Pre-release.\r\n\r\nPatch release on top of v0.3.5, fixing three bugs in the Contacts screen:\r\n\r\n- **200-row cap removed.** The contacts list previously stopped rendering after 200 matched rows. With 200+ contacts this hid recently-added repeaters from the list entirely (including, in one reproducible case, a freshly-added Repeater that Discover claimed to have added but which was nowhere to be seen). The list now displays every matching contact.\r\n- **Sorted by recency.** Contacts now appear newest-first instead of in creation order. The sort key is local activity time (advert receipt, message send, or message receive), so the most recently active contacts sit at the top of the list regardless of which filter is active.\r\n- **Sort key corrected.** Initial attempt used `last_advert_timestamp`, which is the *sender's claimed clock* embedded in the advert payload rather than our reception time. That gave nonsense ordering: nodes with forward-dated clocks (stale build epoch, mis-set NTP, etc.) sat permanently at the top, and nodes whose clocks were stuck or behind had their adverts silently dropped by the upstream replay-attack guard and sank to the bottom. The fix sorts by `lastmod` (our local RTC time at last contact activity) with an override in `onAdvertRecv` so `lastmod` is updated on every advert receipt regardless of whether the upstream replay guard early-returned.\r\n\r\nNo other behavioural changes from v0.3.5.\r\n\r\n## First-Time Flashing: Read This First\r\n\r\n(Same as v0.3.5 — skip this section if you've already flashed v0.3.5; the contacts fixes carry over via the usual upgrade path.)\r\n\r\nMeck-P4 ships as a single **merged binary** (bootloader + partition table + application combined). One file, flash at offset `0x0`.\r\n\r\n> **An SD card is recommended.** With a FAT32-formatted card inserted, every saved setting, channel message, DM, and room post is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.\r\n\r\nEnsure you use the **right-side USB-C port** (the data port), not the high-speed charger port, to flash.\r\nPre-release.
\nPatch release on top of v0.3.5, fixing three bugs in the Contacts screen:
\nlast_advert_timestamp, which is the sender's claimed clock embedded in the advert payload rather than our reception time. That gave nonsense ordering: nodes with forward-dated clocks (stale build epoch, mis-set NTP, etc.) sat permanently at the top, and nodes whose clocks were stuck or behind had their adverts silently dropped by the upstream replay-attack guard and sank to the bottom. The fix sorts by lastmod (our local RTC time at last contact activity) with an override in onAdvertRecv so lastmod is updated on every advert receipt regardless of whether the upstream replay guard early-returned.No other behavioural changes from v0.3.5.
\n(Same as v0.3.5 — skip this section if you've already flashed v0.3.5; the contacts fixes carry over via the usual upgrade path.)
\nMeck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.
\n\nAn SD card is recommended. With a FAT32-formatted card inserted, every saved setting, channel message, DM, and room post is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.
\n
Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.\n
meck-p4-0.3.5.1-version-merged.bin file you downloadedpip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.3.5.1-version-merged.bin\n(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)
Upgrading from v0.3.5 or v0.3.3 does not require erase_flash. The prefs loader continues to tolerate older shorter-blob layouts, so any new fields come up at default rather than wiping existing settings.
\n\n⚠️ AMOLED variant remains untested by the maintainer. The
\n-amoled.binis built from the same source tree with the AMOLED display option selected in menuconfig, but the project maintainer doesn't have the AMOLED hardware on hand. The TFT variant is the tested and known-working build.
Carried over unchanged from v0.3.5:
\n>> glyph was added to the top bar to indicate when the audio player is actively playing, mirrored across every home tile and full screen. However, the broader background-playback experience has a number of unresolved bugs: tapping the Audio tile while a track is playing doesn't jump back to the Now Playing screen (so pausing requires navigating back to the file manually), and starting a second \n…Direct messaging arrives in v0.3.5 — compose, send, receive, and persist DMs from any companion contact, with unread badges viewable in the channel list. Room server support and repeater admin land alongside, giving you logged-in access to room post history and the full status/CLI/settings interface for remote repeater management. A new map screen renders OSM slippy tiles from the SD card with a GPS dot, contact markers, and pan/zoom. Plus a per-contact path editor, a standalone trace route screen, a keyboard layout overhaul, a GPS time-sync fix, debug logs to SD, and config export to a MeshCore-app-compatible JSON file.
\n\n\n⚠️ Still a pre-release. ⚠️ Web browser, IRC, and the BLE/WiFi companion path are still not in this build. See What's Not Yet Implemented for the full pending list.
\n
Meck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.
\n\nAn SD card is recommended. With a FAT32-formatted card inserted, every saved setting, channel message, DM, and room post is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.
\n
Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.\n
meck-p4-0.3.5-version-merged.bin file you downloadedpip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.3.5-version-merged.bin\n(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)
Upgrading from v0.3.3 does not require erase_flash. The prefs loader continues to tolerate older shorter-blob layouts, so any new fields come up at default rather than wiping existing settings.
\n\n⚠️ AMOLED variant remains untested by the maintainer. The
\n-amoled.binis built from the same source tree with the AMOLED display option selected in menuconfig, but the project maintainer doesn't have the AMOLED hardware on hand. The TFT variant is the tested and known-working build.
Open a companion contact's detail screen (from the Contacts menu tile on the home screen) and tap the cyan Send DM button (stacked above the red Delete button) to compose. The DM conversation view uses the standard chat layout — keyboard on the bottom half, message bubbles scrolling above.
\nTap a Room-type contact to open the same admin login flow as repeaters. On successful login, the room's post timeline appears as a scrollable bubble list, left-aligned, with the author name above each bubble and a timestamp and hop count footer below.
\nOne-step config import from the MeshCore mobile app so existing users can move to a P4 without re-entering everything, a firmware-side fix for the BQ27220 fuel gauge calibration so the battery percentage matches reality, and substantial UI work on the home screen, Settings, and tile layouts. Plus a small power-savings pass that trims about 38 mA off idle draw.
\n\n\n⚠️ Still a pre-release. ⚠️ Direct messaging, roomserver access, repeater admin, trace route, web browser, IRC, and the BLE companion path are still not in this build. See What's Not Yet Implemented for the full pending list.
\n
Meck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.
\n\nAn SD card is recommended. With a FAT32-formatted card inserted, every saved setting and channel message is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.
\n
Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.
\nmeck-p4-0.3.3-version-merged.bin file you downloadedpip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.3.3-version-merged.bin\n(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)
Upgrading from v0.3 does not require erase_flash. The prefs loader has been made tolerant of older shorter-blob layouts, so any new fields added in v0.3.3 (such as Font Size) come up at default rather than wiping existing settings.
\n\n⚠️ AMOLED variant remains untested by the maintainer. The
\n-amoled.binis built from the same source tree with the AMOLED display option selected in menuconfig, but the project maintainer doesn't have the AMOLED hardware on hand. The TFT variant is the tested and known-working build.
Drop your MeshCore mobile or desktop app config export onto the SD card, reboot, and your identity, channels, contacts, node name, and radio settings come across in one step. No more re-entering contacts or generating a fresh keypair when moving to the P4.
\nHow to use:
\nimport.json and copy to /sdcard/meshcore/import.json on the P4's SD cardOn boot, Meck reads the file and applies it:
\n| Field | \nBehaviour | \n
|---|---|
| Identity (private + public key) | \nReplaces _main.id atomically (tmp + rename). Existing identity is overwritten. | \n
| Channels | \nMerged by 16-byte secret. Existing channels kept; new ones appended to free slots; duplicates skipped. | \n
| Contacts | \nMerged by public key. Existing kept; new ones appended. Lat/lon converted from string-decimal to int32 e7. custom_name preferred over name. | \n
| Node name | \nReplaces prefs.node_name. | \n
| Radio settings | \nReplaces freq, BW, SF, CR, TX power on P4NodePrefs. Freq converted kHz to MHz, BW Hz to kHz. | \n
On success the file is moved to /sdcard/meshcore/import.history/import-<unix_epoch>.json so it doesn't re-apply on subsequent boots and leaves an audit trail. On parse failure (bad JSON, missing identity keys, wrong-length hex) a warning is logged and the file is left in place for inspection.
Imported names (node, channels, contacts) are stripped to printable ASCII before being stored. Meck-P4's Montserrat fonts cover Latin-1 only, so emoji codepoints would otherwise render as tofu boxes. Leading an\n…
\n" }, { "version": "v0.3", "name": "Meck-P4 v0.3 -- Audio Player, Active Discovery, Internationalised Keyboard", "datetime": "2026-05-16T03:53:52Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.3", "prerelease": true, "notes": "The third Meck-P4 pre-release. Audio playback from SD, active zero-hop neighbour discovery with one-tap contact add, and a substantially upgraded virtual keyboard with light/dark theme, three physical layouts, and long-press accent input for French and Czech. Plus per-message hop and ACK metadata, and a fix for the battery cell capacity (which had been wrong since v0.1).\r\n\r\n> **⚠️ Still a pre-release.⚠️ ** Direct messaging, roomserver access, repeater admin, trace route, web browser, IRC, and the BLE companion path are still not in this build. See [What's Not Yet Implemented](#whats-not-yet-implemented) for the full pending list.\r\n\r\n---\r\n\r\n## First-Time Flashing -- Read This First\r\n\r\nMeck-P4 ships as a single **merged binary** (bootloader + partition table + application combined). One file, flash at offset `0x0`.\r\n\r\n> **An SD card is recommended.** With a FAT32-formatted card inserted, every saved setting and channel message is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.\r\nThe third Meck-P4 pre-release. Audio playback from SD, active zero-hop neighbour discovery with one-tap contact add, and a substantially upgraded virtual keyboard with light/dark theme, three physical layouts, and long-press accent input for French and Czech. Plus per-message hop and ACK metadata, and a fix for the battery cell capacity (which had been wrong since v0.1).
\n\n\n**⚠️ Still a pre-release.⚠️ ** Direct messaging, roomserver access, repeater admin, trace route, web browser, IRC, and the BLE companion path are still not in this build. See What's Not Yet Implemented for the full pending list.
\n
Meck-P4 ships as a single merged binary (bootloader + partition table + application combined). One file, flash at offset 0x0.
\n\nAn SD card is recommended. With a FAT32-formatted card inserted, every saved setting and channel message is mirrored automatically, audio files have somewhere to live, and the device recovers gracefully from a wiped NVS. Without an SD card the device still works but loses message history on reboot.
\n
Ensure you use the right-side USB-C port (the data port), not the high-speed charger port, to flash.
\nmeck-p4-0.3-version-merged.bin file you downloadedpip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.3-version-merged.bin\n(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)
If you're upgrading from v0.1 and want to start with clean defaults, run esptool.py --chip esp32p4 -p PORT erase_flash before the write. Your contacts and prefs will be restored from the SD card mirror on first boot.
\n\n⚠️ AMOLED variant is untested. The -amoled.bin is built from the same source tree with the AMOLED display option selected in menuconfig, but the project maintainer doesn't have the AMOLED hardware on hand and hasn't been able to flash or run it. Community members are currently testing it. If you have an AMOLED board, please report back via the MeshCore Discord or a GitHub issue with whether it boots, the display works, and touch works. The TFT variant is the tested and known-working build.
\n
MP3 playback directly from the SD card. Two top-level subtrees give the player different defaults so music and audiobooks behave appropriately:
\n| Subtree | \nDefaults | \n
|---|---|
/sdcard/audio/music/ | \nStandard playback. Resume bookmark off. | \n
/sdcard/audio/audiobooks/ | \nAudiobook mode. Resume bookmark on, sleep timer available, position tracked through the playlist. | \n
How to use the audio player:
\nmusic/ and audiobooks/ folders into /sdcard/audio/ on the SD card (the firmware creates the subtree automatically on first boot if it doesn't exist)\n\n" }, { "version": "v0.1", "name": "Meck-P4 v0.1 — First Pre-Release for the LilyGo T-Display P4", "datetime": "2026-05-09T08:14:03Z", "url": "https://github.com/pelgraine/Meck-P4/releases/tag/v0.1", "prerelease": true, "notes": "The first publicly flashable Meck firmware for the LilyGo T-Display P4. One\r\nfile, one offset, you're on the mesh.\r\n\r\n> **⚠️ This is a pre-release, not a finished product.** Many of the features people associate with Meck on the T-Deck Pro and T5S3 — direct messaging, roomserver access, repeater admin, trace route, web browser, IRC, audio player — are **not yet implemented** on the P4. What's here is the foundation: a fully functional MeshCore node with channel messaging, contacts, persistent storage, GPS, and battery monitoring. See the [full feature list and roadmap](https://github.com/pelgraine/Meck-P4#road-map--to-do).\r\n\r\n---\r\n\r\n## Hardware\r\n\r\n⚠️ LilyGo T-Display P4 (TFT version)⚠️ **The AMOLED variant has not been tested** but should be close — adjust the display init in\r\n`main/examples/lvgl_9_ui/main.cpp` if you want to try it.\r\n\r\n## Flashing\r\nRead the audio player guide before copying files to your SD card. MP3s with large embedded album art can starve the IDLE task on first decode and trigger a watchdog reboot. The guide walks through the
\ntools/mp3_clean.pyscript that strip\n…
The first publicly flashable Meck firmware for the LilyGo T-Display P4. One\nfile, one offset, you're on the mesh.
\n\n\n⚠️ This is a pre-release, not a finished product. Many of the features people associate with Meck on the T-Deck Pro and T5S3 — direct messaging, roomserver access, repeater admin, trace route, web browser, IRC, audio player — are not yet implemented on the P4. What's here is the foundation: a fully functional MeshCore node with channel messaging, contacts, persistent storage, GPS, and battery monitoring. See the full feature list and roadmap.
\n
⚠️ LilyGo T-Display P4 (TFT version)⚠️ The AMOLED variant has not been tested but should be close — adjust the display init in\nmain/examples/lvgl_9_ui/main.cpp if you want to try it.
Ensure you use the right-usb C port, ie not the high-speed charger port to flash.
\nThe release file meck-p4-0.1-merged.bin is a merged binary containing the bootloader, partition table, and application combined into a single image — flash it at address 0x0.
Using the MeshCore Flasher (web-based):
\nmeck-p4-0.1.bin file you downloadedUsing esptool.py:
\npip install esptool\nesptool.py --chip esp32p4 -p PORT write_flash 0x0 meck-p4-0.1.bin\n(Replace PORT with /dev/cu.usbmodemXXXX on macOS, /dev/ttyACM0 on Linux, or COM3 on Windows.)
If you've previously had something else on the device, run esptool.py --chip esp32p4 -p PORT erase_flash first to clear NVS so Meck starts with clean defaults.
\n\nAn SD card is recommended. With a FAT32-formatted card inserted, every saved setting and channel message is mirrored automatically. The device works without one but loses message history on reboot.
\n
A horizontal seven-tile home layout. Swipe left/right to switch tiles.
\n| Tile | \nWhat it shows | \n
|---|---|
| 0 Home | \nNode name, freq/SF/RSSI/RX counters, six-button nav grid | \n
| 1 Recent Heard | \nLive list of nodes whose adverts you've received | \n
| 2 Radio Details | \nCurrent freq / BW / SF / CR / TX / sync word | \n
| 3 Advert | \nLong-press to send a manual advert | \n
| 4 GPS | \nFix status, satellites, position, altitude, sentence rate | \n
| 5 Battery | \nVoltage, charge%, current, chip temp, remaining mAh | \n
| 6 Shutdown | \nLong-press to power down | \n