Firmware size now above 4MB in `edge`
Everyone,
FYI: the latest edge build 3.3.006-224-g6cfa0081e now exceeds the 4MB
limit, so from here on new builds will no longer be published in the
v3.3 directory, but only in v3.3-5.
Last build on v3.3 was 3.3.006-215-g6a1a8b4db (Thu Jul 30 20:06:23
CEST 2026).
main (branch release-3.3.006) still fits 4MB with the latest fixes
(3.3.006-172-g362f87425 Sat Aug 1 09:49:50 CEST 2026).
Regards, Michael
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
Opening this for discussion here:
For those not on EDGE and not running >4MB partition schemes, I think we now need to ‘evangelise’ updating the MAIN and then doing the partition upgrade. Any suggestions for how to achieve this? Agree a text and then send by eMail to all registered accounts? Push notifications?
Suggested starting point for content:
Over recent releases, the OVMS v3 firmware image has grown close to the original 4 MB application partition limit defined in the legacy partition layout (factory, ota_0, ota_1, each 4 MB on a 16 MB flash). To ensure we can continue to deliver new features and fixes, we have introduced an updated partitioning scheme with larger application partitions, and the latest MAIN and EAP firmware builds are now designed to run on these expanded partitions. Modules that remain on the old 4 MB partition layout will soon be unable to accept newer firmware images, and will therefore stop receiving further OTA updates.
To stay current, you will need to first update your module to the latest MAIN or EAP firmware release, and then perform a one‑time partition upgrade using the web UI (Config → Partitioning), as documented in the OVMS downloads and OTA guidance. The upgrade process will re‑partition the module’s flash to the new layout and migrate your installation so that it can accept larger firmware images going forward. Please ensure you complete both steps—firmware update and partition upgrade—as soon as practical; until the partition upgrade is finished, your module will remain on the old 4 MB scheme and will not receive new releases.
Once the partition upgrade has been completed successfully, your OVMS module will continue to receive MAIN, EAP, or EDGE updates as usual, and you will benefit from ongoing enhancements and bug fixes without running into the previous 4 MB size limit. If you are unsure which partition layout your module is using, or need assistance with the upgrade, please consult the online OVMS documentation or your firmware provider’s download page, or contact support for guidance before proceeding.
Summary of steps: Upgrade to latest EAP or MAIN firmware (3.3.006 or later). [instructions from app, or web ui] Perform partition upgrade. [instructions from app, console, or web ui] Check that you are using the updated partition arrangement. [instructions from app, console, or web ui]
Regards, Mark.
On 1 Aug 2026, at 5:32 PM, Michael Balzer via OvmsDev <ovmsdev@lists.openvehicles.com> wrote:
Signed PGP part Everyone,
FYI: the latest
edgebuild 3.3.006-224-g6cfa0081e now exceeds the 4MB limit, so from here on new builds will no longer be published in thev3.3directory, but only inv3.3-5.Last build on
v3.3was 3.3.006-215-g6a1a8b4db (Thu Jul 30 20:06:23 CEST 2026).
main(branch release-3.3.006) still fits 4MB with the latest fixes (3.3.006-172-g362f87425 Sat Aug 1 09:49:50 CEST 2026).Regards, Michael
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com <mailto:ovmsdev@lists.openvehicles.com> To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com <mailto:ovmsdev-leave@lists.openvehicles.com>
Seems users are starting to respond. Maybe the automated PUSH notifications will be sufficient.
Currently my server has 11.2% of users with updated partition scheme, and 88.8% running old scheme. But it is early days with the new version just reaching MAIN yesterday.
83.8% of my users are on main, 6.4% on eap, 7.1% on edge, and the rest on very weird old versions (including v2 OVMS).
45.2% of my users are on a 3.3.006 version, 36.4% on 3.3.003, 7.6% on 3.3.005, 3.6% on 3.3.004, with the rest on older.
These numbers are for users not using paranoid mode.
Regards, Mark

On 3 Aug 2026, at 3:19 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Opening this for discussion here:
For those not on EDGE and not running >4MB partition schemes, I think we now need to ‘evangelise’ updating the MAIN and then doing the partition upgrade. Any suggestions for how to achieve this? Agree a text and then send by eMail to all registered accounts? Push notifications?
Suggested starting point for content:
Over recent releases, the OVMS v3 firmware image has grown close to the original 4 MB application partition limit defined in the legacy partition layout (factory, ota_0, ota_1, each 4 MB on a 16 MB flash). To ensure we can continue to deliver new features and fixes, we have introduced an updated partitioning scheme with larger application partitions, and the latest MAIN and EAP firmware builds are now designed to run on these expanded partitions. Modules that remain on the old 4 MB partition layout will soon be unable to accept newer firmware images, and will therefore stop receiving further OTA updates.
To stay current, you will need to first update your module to the latest MAIN or EAP firmware release, and then perform a one‑time partition upgrade using the web UI (Config → Partitioning), as documented in the OVMS downloads and OTA guidance. The upgrade process will re‑partition the module’s flash to the new layout and migrate your installation so that it can accept larger firmware images going forward. Please ensure you complete both steps—firmware update and partition upgrade—as soon as practical; until the partition upgrade is finished, your module will remain on the old 4 MB scheme and will not receive new releases.
Once the partition upgrade has been completed successfully, your OVMS module will continue to receive MAIN, EAP, or EDGE updates as usual, and you will benefit from ongoing enhancements and bug fixes without running into the previous 4 MB size limit. If you are unsure which partition layout your module is using, or need assistance with the upgrade, please consult the online OVMS documentation or your firmware provider’s download page, or contact support for guidance before proceeding.
Summary of steps: Upgrade to latest EAP or MAIN firmware (3.3.006 or later). [instructions from app, or web ui] Perform partition upgrade. [instructions from app, console, or web ui] Check that you are using the updated partition arrangement. [instructions from app, console, or web ui]
Regards, Mark.
On 1 Aug 2026, at 5:32 PM, Michael Balzer via OvmsDev <ovmsdev@lists.openvehicles.com> wrote:
Signed PGP part Everyone,
FYI: the latest
edgebuild 3.3.006-224-g6cfa0081e now exceeds the 4MB limit, so from here on new builds will no longer be published in thev3.3directory, but only inv3.3-5.Last build on
v3.3was 3.3.006-215-g6a1a8b4db (Thu Jul 30 20:06:23 CEST 2026).
main(branch release-3.3.006) still fits 4MB with the latest fixes (3.3.006-172-g362f87425 Sat Aug 1 09:49:50 CEST 2026).Regards, Michael
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com <mailto:ovmsdev@lists.openvehicles.com> To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com <mailto:ovmsdev-leave@lists.openvehicles.com>
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com
I think we should wait for another 2-3 weeks, besides the main release
delay there's also still summer holidays for many users.
Push notifications probably won't be sufficient, they are ignored by many users. OTOH, these users probably also will ignore an email.
The main release on my server was July 18th, current state is 22% of
my users are now running the 7MB partitioning.
Tag distribution (V3 only):
- 83.2%
main - 10.7%
edge - 3.4%
eap - 0.1%
pre - …and the rest is distributed over a bunch of misspelled or
non-standard tags like
Mainorsmarteq.
Major versions (V3 only):
- 68.5% 3.3.006
- 21.1% 3.3.005
- 6.8% 3.3.004
- 2.1% 3.3.003
- …rest is running 3.3.002 or older
There are many users not having auto updates enabled (or not allowing via cellular and normally not parking within Wifi range).
There are also some users with misconfigured OTA updates, some detectable from the access log showing "ovms3.ver" requests with invalid paths, others probably not detectable due to an already invalid update server. We need to apply more strict input validation for the OTA configuration, I'll have a look at that.
Regards, Michael
Am 04.08.26 um 03:27 schrieb Mark Webb-Johnson:
Seems users are starting to respond. Maybe the automated PUSH notifications will be sufficient.
Currently my server has 11.2% of users with updated partition scheme, and 88.8% running old scheme. But it is early days with the new version just reaching MAIN yesterday.
83.8% of my users are on main, 6.4% on eap, 7.1% on edge, and the rest on very weird old versions (including v2 OVMS).
45.2% of my users are on a 3.3.006 version, 36.4% on 3.3.003, 7.6% on 3.3.005, 3.6% on 3.3.004, with the rest on older.
These numbers are for users not using paranoid mode.
Regards, Mark
PastedGraphic-1.png
On 3 Aug 2026, at 3:19 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Opening this for discussion here:
For those not on EDGE and not running >4MB partition schemes, I think we now need to ‘evangelise’ updating the MAIN and then doing the partition upgrade. Any suggestions for how to achieve this? Agree a text and then send by eMail to all registered accounts? Push notifications? Suggested starting point for content:
Over recent releases, the OVMS v3 firmware image has grown close to the original 4 MB application partition limit defined in the legacy partition layout (factory, ota_0, ota_1, each 4 MB on a 16 MB flash). To ensure we can continue to deliver new features and fixes, we have introduced an updated partitioning scheme with larger application partitions, and the latest MAIN and EAP firmware builds are now designed to run on these expanded partitions. Modules that remain on the old 4 MB partition layout will soon be unable to accept newer firmware images, and will therefore stop receiving further OTA updates. To stay current, you will need to first update your module to the latest MAIN or EAP firmware release, and then perform a one‑time partition upgrade using the web UI (Config → Partitioning), as documented in the OVMS downloads and OTA guidance. The upgrade process will re‑partition the module’s flash to the new layout and migrate your installation so that it can accept larger firmware images going forward. Please ensure you complete both steps—firmware update and partition upgrade—as soon as practical; until the partition upgrade is finished, your module will remain on the old 4 MB scheme and will not receive new releases. Once the partition upgrade has been completed successfully, your OVMS module will continue to receive MAIN, EAP, or EDGE updates as usual, and you will benefit from ongoing enhancements and bug fixes without running into the previous 4 MB size limit. If you are unsure which partition layout your module is using, or need assistance with the upgrade, please consult the online OVMS documentation or your firmware provider’s download page, or contact support for guidance before proceeding. Summary of steps: 1. Upgrade to latest EAP or MAIN firmware (3.3.006 or later). [instructions from app, or web ui] 2. Perform partition upgrade. [instructions from app, console, or web ui] 3. Check that you are using the updated partition arrangement. [instructions from app, console, or web ui]Regards, Mark.
On 1 Aug 2026, at 5:32 PM, Michael Balzer via OvmsDev <ovmsdev@lists.openvehicles.com> wrote:
Signed PGP part Everyone,
FYI: the latest
edgebuild 3.3.006-224-g6cfa0081e now exceeds the 4MB limit, so from here on new builds will no longer be published in thev3.3directory, but only inv3.3-5.Last build on
v3.3was 3.3.006-215-g6a1a8b4db (Thu Jul 30 20:06:23 CEST 2026).
main(branch release-3.3.006) still fits 4MB with the latest fixes (3.3.006-172-g362f87425 Sat Aug 1 09:49:50 CEST 2026).Regards, Michael
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
OvmsDev mailing list --ovmsdev@lists.openvehicles.com To unsubscribe send an email toovmsdev-leave@lists.openvehicles.com
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com
OvmsDev mailing list --ovmsdev@lists.openvehicles.com To unsubscribe send an email toovmsdev-leave@lists.openvehicles.com
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
Summer holidays are well over, so it's about time to check again:
Current state in my user base is: 30.4% are running the 7MB partitioning, with 76.5% now on 3.3.006. So adoption of the 7MB scheme is still behind.
On release 3.3.007 the OTA system will inform users still on 4MB partitioning that the update cannot be installed.
Is that sufficient, or should we send emails to all registered users now?
Regards, Michael
Am 04.08.26 um 11:05 schrieb Michael Balzer via OvmsDev:
I think we should wait for another 2-3 weeks, besides the
mainrelease delay there's also still summer holidays for many users.Push notifications probably won't be sufficient, they are ignored by many users. OTOH, these users probably also will ignore an email.
The
mainrelease on my server was July 18th, current state is 22% of my users are now running the 7MB partitioning.Tag distribution (V3 only):
- 83.2%
main- 10.7%
edge- 3.4%
eap- 0.1%
pre- …and the rest is distributed over a bunch of misspelled or non-standard tags like
Mainorsmarteq.Major versions (V3 only):
- 68.5% 3.3.006
- 21.1% 3.3.005
- 6.8% 3.3.004
- 2.1% 3.3.003
- …rest is running 3.3.002 or older
There are many users not having auto updates enabled (or not allowing via cellular and normally not parking within Wifi range).
There are also some users with misconfigured OTA updates, some detectable from the access log showing "ovms3.ver" requests with invalid paths, others probably not detectable due to an already invalid update server. We need to apply more strict input validation for the OTA configuration, I'll have a look at that.
Regards, Michael
Am 04.08.26 um 03:27 schrieb Mark Webb-Johnson:
Seems users are starting to respond. Maybe the automated PUSH notifications will be sufficient.
Currently my server has 11.2% of users with updated partition scheme, and 88.8% running old scheme. But it is early days with the new version just reaching MAIN yesterday.
83.8% of my users are on main, 6.4% on eap, 7.1% on edge, and the rest on very weird old versions (including v2 OVMS).
45.2% of my users are on a 3.3.006 version, 36.4% on 3.3.003, 7.6% on 3.3.005, 3.6% on 3.3.004, with the rest on older.
These numbers are for users not using paranoid mode.
Regards, Mark
PastedGraphic-1.png
On 3 Aug 2026, at 3:19 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Opening this for discussion here:
For those not on EDGE and not running >4MB partition schemes, I think we now need to ‘evangelise’ updating the MAIN and then doing the partition upgrade. Any suggestions for how to achieve this? Agree a text and then send by eMail to all registered accounts? Push notifications? Suggested starting point for content:
Over recent releases, the OVMS v3 firmware image has grown close to the original 4 MB application partition limit defined in the legacy partition layout (factory, ota_0, ota_1, each 4 MB on a 16 MB flash). To ensure we can continue to deliver new features and fixes, we have introduced an updated partitioning scheme with larger application partitions, and the latest MAIN and EAP firmware builds are now designed to run on these expanded partitions. Modules that remain on the old 4 MB partition layout will soon be unable to accept newer firmware images, and will therefore stop receiving further OTA updates. To stay current, you will need to first update your module to the latest MAIN or EAP firmware release, and then perform a one‑time partition upgrade using the web UI (Config → Partitioning), as documented in the OVMS downloads and OTA guidance. The upgrade process will re‑partition the module’s flash to the new layout and migrate your installation so that it can accept larger firmware images going forward. Please ensure you complete both steps—firmware update and partition upgrade—as soon as practical; until the partition upgrade is finished, your module will remain on the old 4 MB scheme and will not receive new releases. Once the partition upgrade has been completed successfully, your OVMS module will continue to receive MAIN, EAP, or EDGE updates as usual, and you will benefit from ongoing enhancements and bug fixes without running into the previous 4 MB size limit. If you are unsure which partition layout your module is using, or need assistance with the upgrade, please consult the online OVMS documentation or your firmware provider’s download page, or contact support for guidance before proceeding. Summary of steps: 1. Upgrade to latest EAP or MAIN firmware (3.3.006 or later). [instructions from app, or web ui] 2. Perform partition upgrade. [instructions from app, console, or web ui] 3. Check that you are using the updated partition arrangement. [instructions from app, console, or web ui]Regards, Mark.
On 1 Aug 2026, at 5:32 PM, Michael Balzer via OvmsDev <ovmsdev@lists.openvehicles.com> wrote:
Signed PGP part Everyone,
FYI: the latest
edgebuild 3.3.006-224-g6cfa0081e now exceeds the 4MB limit, so from here on new builds will no longer be published in thev3.3directory, but only inv3.3-5.Last build on
v3.3was 3.3.006-215-g6a1a8b4db (Thu Jul 30 20:06:23 CEST 2026).
main(branch release-3.3.006) still fits 4MB with the latest fixes (3.3.006-172-g362f87425 Sat Aug 1 09:49:50 CEST 2026).Regards, Michael
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
OvmsDev mailing list --ovmsdev@lists.openvehicles.com To unsubscribe send an email toovmsdev-leave@lists.openvehicles.com
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com
OvmsDev mailing list --ovmsdev@lists.openvehicles.com To unsubscribe send an email toovmsdev-leave@lists.openvehicles.com
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
OvmsDev mailing list --ovmsdev@lists.openvehicles.com To unsubscribe send an email toovmsdev-leave@lists.openvehicles.com
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
The api.openvehicles.com <http://api.openvehicles.com/> server seems to be doing worse. Only about 20% using new partitioning scheme.
Tag distribution (V3 only):
85.0% main
6.3% edge
6.3% eap
…and the rest is distributed over a bunch of misspelled or non-standard tags like Main or smarteq.
Major versions (V3 only): 76.1% 3.3.006 9.6% 3.3.003 5.6% 3.3.005 2.0% 3.3.004 …rest is running 3.3.002 or older
I think we should send eMails.
Regards, Mark
On 6 Sep 2026, at 6:38 PM, Michael Balzer via OvmsDev <ovmsdev@lists.openvehicles.com> wrote:
Summer holidays are well over, so it's about time to check again:
Current state in my user base is: 30.4% are running the 7MB partitioning, with 76.5% now on 3.3.006. So adoption of the 7MB scheme is still behind.
On release 3.3.007 the OTA system will inform users still on 4MB partitioning that the update cannot be installed.
Is that sufficient, or should we send emails to all registered users now?
Regards, Michael
Am 04.08.26 um 11:05 schrieb Michael Balzer via OvmsDev:
I think we should wait for another 2-3 weeks, besides the
mainrelease delay there's also still summer holidays for many users.Push notifications probably won't be sufficient, they are ignored by many users. OTOH, these users probably also will ignore an email.
The
mainrelease on my server was July 18th, current state is 22% of my users are now running the 7MB partitioning.Tag distribution (V3 only): 83.2%
main10.7%edge3.4%eap0.1%pre…and the rest is distributed over a bunch of misspelled or non-standard tags likeMainorsmarteq. Major versions (V3 only): 68.5% 3.3.006 21.1% 3.3.005 6.8% 3.3.004 2.1% 3.3.003 …rest is running 3.3.002 or older There are many users not having auto updates enabled (or not allowing via cellular and normally not parking within Wifi range).There are also some users with misconfigured OTA updates, some detectable from the access log showing "ovms3.ver" requests with invalid paths, others probably not detectable due to an already invalid update server. We need to apply more strict input validation for the OTA configuration, I'll have a look at that.
Regards, Michael
Am 04.08.26 um 03:27 schrieb Mark Webb-Johnson:
Seems users are starting to respond. Maybe the automated PUSH notifications will be sufficient.
Currently my server has 11.2% of users with updated partition scheme, and 88.8% running old scheme. But it is early days with the new version just reaching MAIN yesterday.
83.8% of my users are on main, 6.4% on eap, 7.1% on edge, and the rest on very weird old versions (including v2 OVMS).
45.2% of my users are on a 3.3.006 version, 36.4% on 3.3.003, 7.6% on 3.3.005, 3.6% on 3.3.004, with the rest on older.
These numbers are for users not using paranoid mode.
Regards, Mark
<PastedGraphic-1.png>
On 3 Aug 2026, at 3:19 PM, Mark Webb-Johnson <mark@webb-johnson.net> <mailto:mark@webb-johnson.net> wrote:
Opening this for discussion here:
For those not on EDGE and not running >4MB partition schemes, I think we now need to ‘evangelise’ updating the MAIN and then doing the partition upgrade. Any suggestions for how to achieve this? Agree a text and then send by eMail to all registered accounts? Push notifications?
Suggested starting point for content:
Over recent releases, the OVMS v3 firmware image has grown close to the original 4 MB application partition limit defined in the legacy partition layout (factory, ota_0, ota_1, each 4 MB on a 16 MB flash). To ensure we can continue to deliver new features and fixes, we have introduced an updated partitioning scheme with larger application partitions, and the latest MAIN and EAP firmware builds are now designed to run on these expanded partitions. Modules that remain on the old 4 MB partition layout will soon be unable to accept newer firmware images, and will therefore stop receiving further OTA updates.
To stay current, you will need to first update your module to the latest MAIN or EAP firmware release, and then perform a one‑time partition upgrade using the web UI (Config → Partitioning), as documented in the OVMS downloads and OTA guidance. The upgrade process will re‑partition the module’s flash to the new layout and migrate your installation so that it can accept larger firmware images going forward. Please ensure you complete both steps—firmware update and partition upgrade—as soon as practical; until the partition upgrade is finished, your module will remain on the old 4 MB scheme and will not receive new releases.
Once the partition upgrade has been completed successfully, your OVMS module will continue to receive MAIN, EAP, or EDGE updates as usual, and you will benefit from ongoing enhancements and bug fixes without running into the previous 4 MB size limit. If you are unsure which partition layout your module is using, or need assistance with the upgrade, please consult the online OVMS documentation or your firmware provider’s download page, or contact support for guidance before proceeding.
Summary of steps: Upgrade to latest EAP or MAIN firmware (3.3.006 or later). [instructions from app, or web ui] Perform partition upgrade. [instructions from app, console, or web ui] Check that you are using the updated partition arrangement. [instructions from app, console, or web ui]
Regards, Mark.
On 1 Aug 2026, at 5:32 PM, Michael Balzer via OvmsDev <ovmsdev@lists.openvehicles.com> <mailto:ovmsdev@lists.openvehicles.com> wrote:
Signed PGP part Everyone,
FYI: the latest
edgebuild 3.3.006-224-g6cfa0081e now exceeds the 4MB limit, so from here on new builds will no longer be published in thev3.3directory, but only inv3.3-5.Last build on
v3.3was 3.3.006-215-g6a1a8b4db (Thu Jul 30 20:06:23 CEST 2026).
main(branch release-3.3.006) still fits 4MB with the latest fixes (3.3.006-172-g362f87425 Sat Aug 1 09:49:50 CEST 2026).Regards, Michael
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com <mailto:ovmsdev@lists.openvehicles.com> To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com <mailto:ovmsdev-leave@lists.openvehicles.com>
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com <mailto:ovmsdev@lists.openvehicles.com> To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com <mailto:ovmsdev-leave@lists.openvehicles.com>
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com <mailto:ovmsdev@lists.openvehicles.com> To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com <mailto:ovmsdev-leave@lists.openvehicles.com>
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com <mailto:ovmsdev@lists.openvehicles.com> To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com <mailto:ovmsdev-leave@lists.openvehicles.com>
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com
FYI: I have placed this announcement on the www.openvehicles.com <http://www.openvehicles.com/> forums:
https://www.openvehicles.com/node/4571
Regards, Mark.
On 4 Aug 2026, at 9:27 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Seems users are starting to respond. Maybe the automated PUSH notifications will be sufficient.
Currently my server has 11.2% of users with updated partition scheme, and 88.8% running old scheme. But it is early days with the new version just reaching MAIN yesterday.
83.8% of my users are on main, 6.4% on eap, 7.1% on edge, and the rest on very weird old versions (including v2 OVMS).
45.2% of my users are on a 3.3.006 version, 36.4% on 3.3.003, 7.6% on 3.3.005, 3.6% on 3.3.004, with the rest on older.
These numbers are for users not using paranoid mode.
Regards, Mark
<PastedGraphic-1.png>
On 3 Aug 2026, at 3:19 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Opening this for discussion here:
For those not on EDGE and not running >4MB partition schemes, I think we now need to ‘evangelise’ updating the MAIN and then doing the partition upgrade. Any suggestions for how to achieve this? Agree a text and then send by eMail to all registered accounts? Push notifications?
Suggested starting point for content:
Over recent releases, the OVMS v3 firmware image has grown close to the original 4 MB application partition limit defined in the legacy partition layout (factory, ota_0, ota_1, each 4 MB on a 16 MB flash). To ensure we can continue to deliver new features and fixes, we have introduced an updated partitioning scheme with larger application partitions, and the latest MAIN and EAP firmware builds are now designed to run on these expanded partitions. Modules that remain on the old 4 MB partition layout will soon be unable to accept newer firmware images, and will therefore stop receiving further OTA updates.
To stay current, you will need to first update your module to the latest MAIN or EAP firmware release, and then perform a one‑time partition upgrade using the web UI (Config → Partitioning), as documented in the OVMS downloads and OTA guidance. The upgrade process will re‑partition the module’s flash to the new layout and migrate your installation so that it can accept larger firmware images going forward. Please ensure you complete both steps—firmware update and partition upgrade—as soon as practical; until the partition upgrade is finished, your module will remain on the old 4 MB scheme and will not receive new releases.
Once the partition upgrade has been completed successfully, your OVMS module will continue to receive MAIN, EAP, or EDGE updates as usual, and you will benefit from ongoing enhancements and bug fixes without running into the previous 4 MB size limit. If you are unsure which partition layout your module is using, or need assistance with the upgrade, please consult the online OVMS documentation or your firmware provider’s download page, or contact support for guidance before proceeding.
Summary of steps: Upgrade to latest EAP or MAIN firmware (3.3.006 or later). [instructions from app, or web ui] Perform partition upgrade. [instructions from app, console, or web ui] Check that you are using the updated partition arrangement. [instructions from app, console, or web ui]
Regards, Mark.
On 1 Aug 2026, at 5:32 PM, Michael Balzer via OvmsDev <ovmsdev@lists.openvehicles.com> wrote:
Signed PGP part Everyone,
FYI: the latest
edgebuild 3.3.006-224-g6cfa0081e now exceeds the 4MB limit, so from here on new builds will no longer be published in thev3.3directory, but only inv3.3-5.Last build on
v3.3was 3.3.006-215-g6a1a8b4db (Thu Jul 30 20:06:23 CEST 2026).
main(branch release-3.3.006) still fits 4MB with the latest fixes (3.3.006-172-g362f87425 Sat Aug 1 09:49:50 CEST 2026).Regards, Michael
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com <mailto:ovmsdev@lists.openvehicles.com> To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com <mailto:ovmsdev-leave@lists.openvehicles.com>
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com
Copied & translated over to my news channel: https://dexters-web.de/
Regards, Michael
Am 05.08.26 um 02:30 schrieb Mark Webb-Johnson:
FYI: I have placed this announcement on the www.openvehicles.com <http://www.openvehicles.com> forums:
https://www.openvehicles.com/node/4571Regards, Mark.
On 4 Aug 2026, at 9:27 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Seems users are starting to respond. Maybe the automated PUSH notifications will be sufficient.
Currently my server has 11.2% of users with updated partition scheme, and 88.8% running old scheme. But it is early days with the new version just reaching MAIN yesterday.
83.8% of my users are on main, 6.4% on eap, 7.1% on edge, and the rest on very weird old versions (including v2 OVMS).
45.2% of my users are on a 3.3.006 version, 36.4% on 3.3.003, 7.6% on 3.3.005, 3.6% on 3.3.004, with the rest on older.
These numbers are for users not using paranoid mode.
Regards, Mark
<PastedGraphic-1.png>
On 3 Aug 2026, at 3:19 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Opening this for discussion here:
For those not on EDGE and not running >4MB partition schemes, I think we now need to ‘evangelise’ updating the MAIN and then doing the partition upgrade. Any suggestions for how to achieve this? Agree a text and then send by eMail to all registered accounts? Push notifications?
Suggested starting point for content:
Over recent releases, the OVMS v3 firmware image has grown close to the original 4 MB application partition limit defined in the legacy partition layout (factory, ota_0, ota_1, each 4 MB on a 16 MB flash). To ensure we can continue to deliver new features and fixes, we have introduced an updated partitioning scheme with larger application partitions, and the latest MAIN and EAP firmware builds are now designed to run on these expanded partitions. Modules that remain on the old 4 MB partition layout will soon be unable to accept newer firmware images, and will therefore stop receiving further OTA updates. To stay current, you will need to first update your module to the latest MAIN or EAP firmware release, and then perform a one‑time partition upgrade using the web UI (Config → Partitioning), as documented in the OVMS downloads and OTA guidance. The upgrade process will re‑partition the module’s flash to the new layout and migrate your installation so that it can accept larger firmware images going forward. Please ensure you complete both steps—firmware update and partition upgrade—as soon as practical; until the partition upgrade is finished, your module will remain on the old 4 MB scheme and will not receive new releases. Once the partition upgrade has been completed successfully, your OVMS module will continue to receive MAIN, EAP, or EDGE updates as usual, and you will benefit from ongoing enhancements and bug fixes without running into the previous 4 MB size limit. If you are unsure which partition layout your module is using, or need assistance with the upgrade, please consult the online OVMS documentation or your firmware provider’s download page, or contact support for guidance before proceeding. Summary of steps: 1. Upgrade to latest EAP or MAIN firmware (3.3.006 or later). [instructions from app, or web ui] 2. Perform partition upgrade. [instructions from app, console, or web ui] 3. Check that you are using the updated partition arrangement. [instructions from app, console, or web ui]Regards, Mark.
On 1 Aug 2026, at 5:32 PM, Michael Balzer via OvmsDev <ovmsdev@lists.openvehicles.com> wrote:
Signed PGP part Everyone,
FYI: the latest
edgebuild 3.3.006-224-g6cfa0081e now exceeds the 4MB limit, so from here on new builds will no longer be published in thev3.3directory, but only inv3.3-5.Last build on
v3.3was 3.3.006-215-g6a1a8b4db (Thu Jul 30 20:06:23 CEST 2026).
main(branch release-3.3.006) still fits 4MB with the latest fixes (3.3.006-172-g362f87425 Sat Aug 1 09:49:50 CEST 2026).Regards, Michael
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
OvmsDev mailing list --ovmsdev@lists.openvehicles.com To unsubscribe send an email toovmsdev-leave@lists.openvehicles.com
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com
OvmsDev mailing list -- ovmsdev@lists.openvehicles.com To unsubscribe send an email to ovmsdev-leave@lists.openvehicles.com
OvmsDev mailing list --ovmsdev@lists.openvehicles.com To unsubscribe send an email toovmsdev-leave@lists.openvehicles.com
-- Michael Balzer * Am Rahmen 5 * D-58313 Herdecke Fon 02330 9104094 * Handy 0176 20698926
participants (2)
-
Mark Webb-Johnson -
Michael Balzer