Vantrue E1 Pro S - Q&A

[Chuck McCoy]

Official Release Date: E1 Pro ($150) January 15, 2025
Official Release Date: E1 Pro S ($190) October 15, 2026 (21 months later)
FCC ID: 2A7EH-E1PROS
https://fccid.io/2A7EH-E1PROS
Application Date: September 8, 2026
E1 Pro S AMAZON USA LINK

$120 Pre-Order (shipped November 15-20) From Official Vantrue website

Q: What’s new & improved with E1 Pro S (2026) over E1 Pro (2025)?
A:

1.) All new next-gen processor / chipset
2.) PlatePix 2.0
3.) 1 Second TurboBoot
4.) AOV Parking Mode
5.) Wi-Fi 6 (download videos faster to smartphone)
6.) Quad GPS (faster, more accurate, more stable)

Q: What was E1 Pro (2025) Achilles' Heel that needed improvement?
A:

1.) Bitrate Too Low (unsatisfactory blurriness above 45MPH daytime & poor night time HDR performance).
2.) PlatePix Too Dark
3.) RUNS A LITTLE WARM

 

[rcg530]

HI Chuck,

Your statement that AOV [Always-On-Video] parking mode is a low power parking mode is not correct. TurboBoot [from powered off state] is a bit slower than the claimed 1-second start time.

• AOV Parking Modes
  • AOV parking modes create time-lapse videos.
  • The playback speed for the time-lapse video is 30 fps, but the recording fps/spf will change depending on which AOV mode selected.
• AOV Collision Detection
  • Writes 1 fps video to the time-lapse while waiting for an impact event.
    • 69 mA @ 12.6V or 0.87 Watts
  • When an impact occurs
    • The E1 Pro S switches from writing at 1 fps to 30 fps for about 25 seconds
    • 205 mA @ 12.6V or 2.58 Watts
    • The time-lapse filename tag of "T" is changed "E" to indicate an event took place while recording that file.
    • The E1 Pro S will then switch back to writing 1 fps as it resumes monitoring for the next impact event
    • Using pre-release firmware EFI242, there is a small time gap in the time-lapse video content as it switches between 1 fps and 30 fps
      • My latest test shows there's a 1.4 second time gap at the time of the impact event as the E1 Pro S switches from writing 1 fps to 30 fps.
      • This issue has been reported to Vantrue and they will work on reducing this in a future firmware update
• AOV Time-Lapse
  • This parking mode creates time-lapse video files.
  • This mode ignores impact events [continues to write time-lapse files when an impact occurs with zero FPS changes].
  • Two SPF [Seconds Per Frame] Choices
    • 1 SPF [aka 1 FPS]
      • Writes a 1 SPF/FPS time-lapse video file with a playback speed of 30 fps
      • 73 mA @ 12.6V or 0.92 Watts
    • 2 SPF
      • Writes a 2 SPF time-lapse video file with a playback speed of 30 fps
      • 43 mA @ 12.6V or 0.54 Watts
• AOV Collision Detection -or- AOV Time-Lapse
  • I reported one additional time gap issue to Vantrue with these parking modes.
  • While the E1 Pro S is in normal/driving recording mode and you turn off the ACC power to the hardwire kit
    • It takes about 6-seconds for the normal/driving video files to close out [that's fine]
    • Unfortunately, there's a rather large 14.86 to 17.36 second time gap after the normal/driving files finish and the time-lapse video starts
• [Low Power] Collision Detection Parking Mode
  • The old collision detection parking mode has been reworked to reduce the power it consumes and the time it takes to start recording after an impact event
  • This parking mode now uses the TurboBoot feature that is also used when the E1 Pro S powers up from an off state
  • When the E1 Pro S is in "low power" collision detection monitoring mode:
    • It consumes 7 mA @ 12.6V or 0.09 Watts.
    • When an impact event is detected:
      • The E1 Pro S starts recording in 1.37 to 1.42 seconds [based on numerous test runs]
      • It creates a 4K UHD 30 fps 30-second unbuffered video based on the TurboBoot kernels default recording settings
      • It consumes 246 mA @ 12.6V or 3.10 Watts while it is creating the 30-second video.
• TurboBoot [from powered off state]
  • This boot configuration for the E1 Pro S [from a powered off state], uses a two-step process
    • Step 1 - TurboBoot Kernel Boot
      • The E1 Pro S starts recording after the power has been restored:
        • Powered Off [VCC On, ACC Off] to TurboBoot Recording Start: 5.11 to 5.70 Seconds
          Powered Off [VCC Off, ACC Off] to TurboBoot Recording Start: 2.76 to 2.89 Seconds
        • A 15-second TurboBoot [B filename tag] video file is created
    • Step 2 - Normal / Driving Mode
      • After the TurboBoot 15-seconds completes, the standard boot kernel takes over and starts recording a normal/driving video
      • As the E1 Pro S is switching from the TurboBoot "B" file to the Normal/Driving "N" file, there's currently a 1.94 time gap
      • This has been reported to Vantrue and they are working to minimize this time gap
• Standard Boot Mode [from powered off state]
  • Powered Off [VCC On, ACC Off] to Standard Recording Start: 12.86 Seconds
    Powered Off [VCC Off, ACC Off] to Standard Recording Start: 10.76 Seconds

 

[Chuck McCoy]

Your statement that AOV [Always-On-Video] parking mode is a low power parking mode is not correct.

Thank you for the correction, (fixed).
The item listing advertising is unclear / misleading.

 

[Chuck McCoy]

• AOV Parking Modes
  • AOV parking modes create time-lapse videos.
  • The playback speed for the time-lapse video is 30 fps, but the recording fps/spf will change depending on which AOV mode selected.
• AOV Collision Detection
  • Writes 1 fps video to the time-lapse while waiting for an impact event.
    • 69 mA @ 12.6V or 0.87 Watts
  • When an impact occurs
    • The E1 Pro S switches from writing at 1 fps to 30 fps for about 25 seconds
    • 205 mA @ 12.6V or 2.58 Watts
    • The time-lapse filename tag of "T" is changed "E" to indicate an event took place while recording that file.
    • The E1 Pro S will then switch back to writing 1 fps as it resumes monitoring for the next impact event
    • Using pre-release firmware EFI242, there is a small time gap in the time-lapse video content as it switches between 1 fps and 30 fps
      • My latest test shows there's a 1.4 second time gap at the time of the impact event as the E1 Pro S switches from writing 1 fps to 30 fps.
      • This issue has been reported to Vantrue and they will work on reducing this in a future firmware update
• AOV Time-Lapse
  • This parking mode creates time-lapse video files.
  • This mode ignores impact events [continues to write time-lapse files when an impact occurs with zero FPS changes].
  • Two SPF [Seconds Per Frame] Choices
    • 1 SPF [aka 1 FPS]
      • Writes a 1 SPF/FPS time-lapse video file with a playback speed of 30 fps
      • 73 mA @ 12.6V or 0.92 Watts
    • 2 SPF
      • Writes a 2 SPF time-lapse video file with a playback speed of 30 fps
      • 43 mA @ 12.6V or 0.54 Watts
• AOV Collision Detection -or- AOV Time-Lapse
  • I reported one additional time gap issue to Vantrue with these parking modes.
  • While the E1 Pro S is in normal/driving recording mode and you turn off the ACC power to the hardwire kit
    • It takes about 6-seconds for the normal/driving video files to close out [that's fine]
    • Unfortunately, there's a rather large 14.86 to 17.36 second time gap after the normal/driving files finish and the time-lapse video starts
• [Low Power] Collision Detection Parking Mode
  • The old collision detection parking mode has been reworked to reduce the power it consumes and the time it takes to start recording after an impact event
  • This parking mode now uses the TurboBoot feature that is also used when the E1 Pro S powers up from an off state
  • When the E1 Pro S is in "low power" collision detection monitoring mode:
    • It consumes 7 mA @ 12.6V or 0.09 Watts.
    • When an impact event is detected:
      • The E1 Pro S starts recording in 1.37 to 1.42 seconds [based on numerous test runs]
      • It creates a 4K UHD 30 fps 30-second unbuffered video based on the TurboBoot kernels default recording settings
      • It consumes 246 mA @ 12.6V or 3.10 Watts while it is creating the 30-second video.
• TurboBoot [from powered off state]
  • This boot configuration for the E1 Pro S [from a powered off state], uses a two-step process
    • Step 1 - TurboBoot Kernel Boot
      • The E1 Pro S starts recording after the power has been restored:
        • Powered Off [VCC On, ACC Off] to TurboBoot Recording Start: 5.11 to 5.70 Seconds
          Powered Off [VCC Off, ACC Off] to TurboBoot Recording Start: 2.76 to 2.89 Seconds
        • A 15-second TurboBoot [B filename tag] video file is created
    • Step 2 - Normal / Driving Mode
      • After the TurboBoot 15-seconds completes, the standard boot kernel takes over and starts recording a normal/driving video
      • As the E1 Pro S is switching from the TurboBoot "B" file to the Normal/Driving "N" file, there's currently a 1.94 time gap
      • This has been reported to Vantrue and they are working to minimize this time gap
• Standard Boot Mode [from powered off state]
  • Powered Off [VCC On, ACC Off] to Standard Recording Start: 12.86 Seconds
    Powered Off [VCC Off, ACC Off] to Standard Recording Start: 10.76 Seconds

All of these new features, and improvements sound great.
But it also sounds like “two steps forward, one step back”.
I want “two steps forward, no steps back”.
Why can’t Vantrue fix all these issues before offering it for sale to the public?
Oh, wait.

 

[rcg530]

All of these new features, and improvements sound great.
But it also sounds like “two steps forward, one step back”.
I want “two steps forward, no steps back”.
Why can’t Vantrue fix all these issues before offering it for sale to the public?
Oh, wait.

There may be a newer firmware included in the production/shipping units. I was given the firmware I ran my tests with at the end of September.

 

[Chuck McCoy]

There may be a newer firmware included in the production/shipping units. I was given the firmware I ran my tests with at the end of September.

Of course, of course.
I'm sure firmware will be 99% ready to go by the time units actually get into customer hands.
$120 Pre-Sale units won't be shipped until November 15-20, so they got about a month to finish, and push out OTA Firmware updates.

 

[kamkar]

I rand into a few quirks.
Nothing big though.

Me favoring 3 minute files, but the system only seem to apply that / my settings after the first 1 minute video is recorded.
This seem to go on even after overnight parking so next day driving, first clip in session again 1 minute, followed by the 3 min segments i have selected.
And in my testing of AOV parking, somehow i managed in the first test to make the camera have a lot more time-lapse footage before handover, than subsequent tests would do.

I am now using AOV parking guard and the Z60 Master also running so 2 systems in parking guard on the old 70mai battery, and doing just fine.

This one also doing just fine with a wide selection of memory cards.

 

[Chuck McCoy]

1 minute video is recorded

What is 1 Minute file size with maximum Bitrate setting?

 

[rcg530]

What is 1 Minute file size with maximum Bitrate setting?

There is no video bitrate setting for the E1 Pro S dash camera. The "Image Quality" setting lets you decided between "Standard" and "PlatePix" not a bitrate. I've looked through my early copy of the E1 Pro S user manual and I cannot find a bitrate specific setting [just making sure I didn't forget a setting].

Here are some of the normal/driving videos created during today's drive. I had HDR enabled and PlatePix enabled for this particular drive. The two files with the higher 43 Mbps and 48 Mbps bitrate seem to be due to driving through a section of road with a large number of trees that were casting shadows and letting sunlight through in very quick bursts [a large number light/dark transitions].

 

[Chuck McCoy]

The two files with the higher 43 Mbps and 48 Mbps bitrate seem to be due to driving through a section of road with a large number of trees

Does that mean this camera has "variable" Bitrate, instead of "fixed" Bitrate?
I really don't like variable, fixed is easier to work with, and check for malfunctions. 🙁

 

[Augustus]

Does that mean this camera has "variable" Bitrate, instead of "fixed" Bitrate?
I really don't like variable, fixed is easier to work with, and check for malfunctions. 🙁

Yes, can confirm it has variable bitrate. A few other cameras I've tested have variable bitrate, doesn't bother me so much - is what it is.

 

[Jeff_Vantrue]

Q: What was E1 Pro (2025) Achilles' Heel that needed improvement?
A:

1.) Bitrate Too Low (unsatisfactory blurriness above 45MPH daytime & poor night time HDR performance).
2.) PlatePix Too Dark
3.) RUNS A LITTLE WARM

Hi sir. Regarding this issue: limited by the actual physical size of the device, we have already done our best by adopting the latest SoC chip available and implementing deep software optimizations.

During the R&D stage, we conducted rigorous high-temperature environment testing. The device does not freeze or crash under high temperatures, and the surface temperature will not burn the user. The overall temperature has already been optimized. Of course, constrained by the laws of physics, a compact device running 4K may feel slightly warmer than a larger-sized device, this is a normal phenomenon. We will continue to find ways to gradually optimize this in future firmware updates.

During development, the team did consider reducing the bitrate to suppress temperature, but in order to uphold the principle of “image quality and performance first,” we ultimately did not compromise and instead chose a balanced approach.

We sincerely welcome everyone’s suggestions. We are closely following and humbly accepting all feedback. Thank you for your support!

 

[Augustus]

1.) What is the Novatek processor / chipset number?
E1 Pro: Novatek 98528
E1 Pro S: Novatek ?????

2.) What is maximum Bitrate?
E1 Pro: 32 Mbps
E1 Pro S: ???

3.) What is maximum 1 Minute File Size?
E1 Pro: 232MB
E1 Pro S: ???

4.) E1 Pro PlatePix is too dark.
Did you fix this with PlatePix 2.0 for E1 Pro S?

5.) What is the Video Codec?
E1 Pro: H.264
E1 Pro S: ???

6.) Please post link to User Manual PDF?

Why are you being aggressive and repeating your questions again that you have already asked Jeff here: https://dashcamtalk.com/forum/threads/ama-about-vantrue-e1-pro-s.61841/post-675951

 

[TonyM]

I'm still collecting and compiling E1 Pro S test footage.

I am impressed with the new AOV "Always On Video" that can record 4K 1fps at lower power consumption than any low bitrate mode I've seen on other dashcams. I think it's a good option for all-day monitoring alongside the other parking modes and I'm pleased to see Vantrue offer something new and useful in this regard.

The impact detection wake up time is not quite as fast as the Vueroid S1 4K, but considering that I have to count individual frames to measure the difference, in real-world terms this is negligible. It's a big step forward from the E1 Pro.

 

[Chuck McCoy]

I am impressed with the new AOV "Always On Video" that can record 4K 1fps at much lower power consumption than any low bitrate mode I've seen on other dashcams.

Does this AOV mode provide audio, or is it time-lapse only?

 

[TonyM]

Does this AOV mode provide audio, or is it time-lapse only?

AOV is recorded without audio

 

[Chuck McCoy]

I am impressed with the new AOV "Always On Video" that can record 4K 1fps at lower power consumption than any low bitrate mode I've seen on other dashcams.

Does this AOV mode provide audio, or is it time-lapse only?

AOV is recorded without audio

Does that mean AOV is basically Time-Lapse?
I like we have another Low Power Parking Mode, but you can’t compare Time-Lapse with Low Bitrate Parking Mode right? 🍎🍊
Time-Lapse = No Audio
Low Bitrate = With Audio