N4 Pro S Review

[jsmith]

@Jeff_Vantrue @EricSan @Karagandinez @Hack_man

So after extensive testing, I have found the problem with WHY my camera loses rear camera feed + connection.

Answer

There must be different hardware or variations in hardware production used in N4 Pro S dashcams from beginning (early production) to now.

Origninal N4 Pro S Front + Interior I was sent DOES NOT work properly with Early Production Rear Camera marked F 1.6. After App Crash, it does not communicate with Rear Camera in Low Bitrate and Drops Rear Camera Feed. When put in Collision Mode, Original (Old) N4 Pro S ALWAYS loses Rear Camera Connection Feed when waking back up.

Replacement N4 Pro S Vantrue just sent me works perfect with F 1.6 Early Production Rear Camera marked 1.6. Several tests (obviously I cannot be 100%) show that it DOES NOT lose connection with rear camera after App Crash in low bitrate or Collision Mode. Rear Camera always returns with camera.

When I use Original (Old) N4 Pro S Front + Interior camera with BRAND NEW Rear Camera marked F 1.8, Rear Channel works 100% after crash. I never lose connection.

I have not yet tested New (Replacement) camera with F 1.8 Camera that arrives with New Camera. But I imagine it will work 100%.

I plan to swap out F 1.6 to F 1.8 Camera with NEW UNIT to verify it works and probably maintain using F1.8 Camra.

Recommendation:

Do not include F 1.6 Marked Early Production Camera with ANY SHIPMENT as there is possible Hardware Conflict for reasons I don't know. Maybe Variations in hardware used or Manufacturing Variances with Early Production.

 

[Hack_man]

Just to clarify, when using the OBDII cable, the dash cam relies on the G-sensor to exit Parking (Collision Detection) Mode. The first G-sensor trigger wakes the camera into Collision Detection Mode, but it requires a second G-sensor trigger—typically from regular driving motion—to fully switch back to Normal Recording Mode.
If the vehicle starts moving very slowly or smoothly, the second trigger might not occur, and the camera may stay in Collision Detection Mode.
Our engineers are reviewing whether this logic can be optimized further, and I’ll keep you updated.

I noticed this behavior. How soon after the first must the second G-sensor trigger occur to exit Collision Parking mode? I've been testing Collision mode without the OBDII cable (on a bench, not installed in a car) by waiting 5+ minutes for the camera to enter parking mode. I would first "wake" the camera by lightly jiggling and then a provide a second light jiggle so it does not go back into parking mode immediately. It seems to work reliably this way but I'm never sure of the timing.

 

[jsmith]

I noticed this behavior. How soon after the first must the second G-sensor trigger occur to exit Collision Parking mode? I've been testing Collision mode without the OBDII cable (on a bench, not installed in a car) by waiting 5+ minutes for the camera to enter parking mode. I would first "wake" the camera by lightly jiggling and then a provide a second light jiggle so it does not go back into parking mode immediately. It seems to work reliably this way but I'm never sure of the timing.

Apparently it takes two collision events to wake up but not sure the time frame. I would think collision could work the same as low bitrate and wake up from recognizing vehicle acceleration. I don't know why a collision event is necessary to wake it up from parking mode.

I brought that issue up as well, but I don't know if someone beat me reporting it to Vantrue.

Anyway, I think I've identified the main issues with functionality that need corrected.

 

[Hack_man]

I would think collision could work the same as low bitrate and wake up from recognizing vehicle acceleration. I don't know why a collision event is necessary to wake it up from parking mode.

Hopefully @Jeff_Vantrue will clarify this for us. It would be good to understand what are the trigger requirements to exit parking mode for Collision vs Motion vs Low Bit Rate vs Low Frame Rate.

 

[Jeff_Vantrue]

I noticed this behavior. How soon after the first must the second G-sensor trigger occur to exit Collision Parking mode? I've been testing Collision mode without the OBDII cable (on a bench, not installed in a car) by waiting 5+ minutes for the camera to enter parking mode. I would first "wake" the camera by lightly jiggling and then a provide a second light jiggle so it does not go back into parking mode immediately. It seems to work reliably this way but I'm never sure of the timing.

If a second G-sensor trigger is detected during the recording period following the first collision (approximately 30 seconds), the camera will exit Parking Mode and switch to Driving Mode.

 

[Jeff_Vantrue]

@Jeff_Vantrue @EricSan @Karagandinez @Hack_man

So after extension testing, I have found the problem with WHY my camera loses rear camera feed + connection.

Answer

There must be different hardware or variations in hardware production used in N4 Pro S dashcams from beginning (early production) to now.

Origninal N4 Pro S Front + Interior I was sent DOES NOT work properly with Early Production Rear Camera marked F 1.6. After App Crash, it does not communicate with Rear Camera in Low Bitrate and Drops Rear Camera Feed. When put in Collision Mode, Original (Old) N4 Pro S ALWAYS loses Rear Camera Connection Feed when waking back up.

Replacement N4 Pro S Vantrue just sent me works perfect with F 1.6 Early Production Rear Camera marked 1.6. Several tests (obviously I cannot be 100%) show that it DOES NOT lose connection with rear camera after App Crash in low bitrate or Collision Mode. Rear Camera always returns with camera.

When I use Original (Old) N4 Pro S Front + Interior camera with BRAND NEW Rear Camera marked F 1.8, Rear Channel works 100% after crash. I never lose connection.

I have not yet tested New (Replacement) camera with F 1.8 Camera that arrives with New Camera. But I imagine it will work 100%.

I plan to swap out F 1.6 to F 1.8 Camera with NEW UNIT to verify it works and probably maintain using F1.8 Camra.

Recommendation:

Do not include F 1.6 Marked Early Production Camera with ANY SHIPMENT as there is possible Hardware Conflict for reasons I don't know. Maybe Variations in hardware used or Manufacturing Variances with Early Production.

I will send you the unreleased firmware for both front and rear camera via email and check if the firmware fix the issue

 

[Hack_man]

I received a replacement N4 Pro S camera since some of the footage was blurry and Vantrue felt there could be a focusing issue.
This is the exact same footage between the original and new camera taken about a week apart.
I was surprised to see the difference between cameras, the newer one was definitely more clear looking at the signs under "Mobile Mart"
The text was not completely readable with the new camera but there was improvement

N4 Pro S ORIGINAL camera HDR and PlatePix ON (7/22/2025)

N4 Pro S NEW camera HDR and PlatePix ON (7/30/2025)

N4 Pro S ORIGINAL camera HDR and PlatePix ON (7/22/2025)

N4 Pro S NEW camera HDR and PlatePix ON (7/30/2025)

 

[Hack_man]

Below is License plate Capture with the N4 Pro S and A229 Pro
HDR and PlatePix was ON for N4 Pro S, HDR was OFF for A229 Pro.
I think these settings are reasonable since PlatePix is recommended by Vantrue for reading text in varied light conditions but Viofo's HDR seems to work better at night.

N4 Pro S HDR ON PlatePix ON

A229 Pro HDR OFF

The Plates are equally readable by both cameras

N4 Pro S

A229 Pro

The sign text looks slightly better with the A229 Pro

N4 PRO S

A229 PRO

 

[jsmith]

I will send you the unreleased firmware for both front and rear camera via email and check if the firmware fix the issue

Sadly, firmware did not fix. Old N4 Pro S still loses Rear Camera with Collision Detection (upon waking up) and Low Bitrate loses rear camera feed after App Crashing and camera Reboots. I am emailing you updated logs from both.

 

[Hack_man]

Another Plate Capture shown below
The plates look equally readable to me comparing N4 Pro S to A229 Pro
PlatePix definitely makes the text on the plate thicker so it "pops" more


N4 Pro S HDR ON PlatePix ON

A229 Pro HDR OFF

N4 Pro S

A229 Pro

 

[jsmith]

@Hack_man

I think @EricSan did this but I am losing track LOL. Does Platepix work by itself without HDR? How well does it work alone in the daytime?

I have always heard HDR shouldn't be run in the daytime and only utilized at night. Therefore, I wonder if PlatePix enabled without HDR performs differently or even functions without HDR.

 

[haiou_f]

I agree with JSmith's statement that HDR is usually turned off during the day. Can you compare the images of two dashcams when HDR is turned off completely

 

[Hack_man]

@Hack_man

I think @EricSan did this but I am losing track LOL. Does Platepix work by itself without HDR? How well does it work alone in the daytime?

I have always heard HDR shouldn't be run in the daytime and only utilized at night. Therefore, I wonder if PlatePix enabled without HDR performs differently or even functions without HDR.

According to Vantrue, PlatePix requires HDR. The PlatePix and HDR timers should be synchronized but are not (yet).
Viofo cameras (from what I have read) seem to work better with HDR at night and it's better to turn off during the day.
Vantrue claims PlatePix works in a broad range of lighting conditions, but it's better for reading text at the expense of making other areas of the image darker.
PlatePix without HDR is the same as no PlatePix at all. It's actually not even turned on.

 

[Hack_man]

Sadly, firmware did not fix. Old N4 Pro S still loses Rear Camera with Collision Detection (upon waking up) and Low Bitrate loses rear camera feed after App Crashing and camera Reboots. I am emailing you updated logs from both.

I just don't understand why I have not been able to recreate this condition of losing rear camera feet, I have tested dozens of times in collision and LBR modes. Can you try not using the OBDII cable?

 

[Hack_man]

I agree with JSmith's statement that HDR is usually turned off during the day. Can you compare the images of two dashcams when HDR is turned off completely

What images are you referring to, Do you mean license plate capture with A229 Pro and N4 Pro S both without HDR?

 

[jsmith]

According to Vantrue, PlatePix requires HDR. The PlatePix and HDR timers should be synchronized but are not (yet).
Viofo cameras (from what I have read) seem to work better with HDR at night and it's better to turn off during the day.
Vantrue claims PlatePix works in a broad range of lighting conditions, but it's better for reading text at the expense of making other areas of the image darker.
PlatePix without HDR is the same as no PlatePix at all. It's actually not even turned on.

I believe others have shown comparisons with PlatePix on and HDR off with there being improvements. I believe @EricSan ran some tests on this, but I'll have to look again.

 

[jsmith]

I just don't understand why I have not been able to recreate this condition of losing rear camera feet, I have tested dozens of times in collision and LBR modes. Can you try not using the OBDII cable?

It is a very odd anomaly. I though the port on the original (OLD) N4 Pro S front + interior camera was bad, because the rear feed drops out on the early production rear camera marked F1.6 in collision mode (when awoken) and low bitrate mode (after camera crashes from connecting to wifi and reboots).

Yet, none of these dropouts occur with the (Old) N4 Pro S unit when connected to the F1.8 production level Rear Camera I received with the brand new replacement unit. While the camera still crashes in low bitrate parking mode after connecting to wifi, the Rear Feed returns with the Camera. The same goes for collision mode, where after the camera wakes up, the rear feed is still present.

The only guess I have right now is that were variances in the production of the rear cameras marked F1.6 and/or Hardware changed in Front Camera at production (source of boards, caps, etc) where current hardware has no issue working with the Cameras Marked F 1.6.

Honestly, I'm guessing here because I don't know Vantrue's production methods or suppliers to isolate the variables. All I can report is the results I see.

Strange, huh?

Best I can suggest is have Vantrue mail me out a 3rd unit (so I can cross check issues back and forth), and send back the original unit with the F1.6 Camera for a teardown inspection. As right now, I don't know how many early F 1.6 cameras were manufactured, if this is isolated to just my Front Unit + F 1.6 Camera, or if other product manufactured around the same time also suffer from losing rear feed flaw.

 

[haiou_f]

Yes, Vantrue has made great progress by being able to do this, and I really want to see their comparison at night

 

[Julian23]

It is a very odd anomaly. I though the port on the original (OLD) N4 Pro S front + interior camera was bad, because the rear feed drops out on the early production rear camera marked F1.6 in collision mode (when awoken) and low bitrate mode (after camera crashes from connecting to wifi and reboots).

Yet, none of these dropouts occur with the (Old) N4 Pro S unit when connected to the F1.8 production level Rear Camera I received with the brand new replacement unit. While the camera still crashes in low bitrate parking mode after connecting to wifi, the Rear Feed returns with the Camera. The same goes for collision mode, where after the camera wakes up, the rear feed is still present.

The only guess I have right now is that were variances in the production of the rear cameras marked F1.6 and/or Hardware changed in Front Camera at production (source of boards, caps, etc) where current hardware has no issue working with the Cameras Marked F 1.6.

Honestly, I'm guessing here because I don't know Vantrue's production methods or suppliers to isolate the variables. All I can report is the results I see.

Strange, huh?

Best I can suggest is have Vantrue mail me out a 3rd unit (so I can cross check issues back and forth), and send back the original unit with the F1.6 Camera for a teardown inspection. As right now, I don't know how many early F 1.6 cameras were manufactured, if this is isolated to just my Front Unit + F 1.6 Camera, or if other product manufactured around the same time also suffer from losing rear feed flaw.

Just a quick question.
Did you swap the cable to the one from the new unit as well or did you keep the "old" one?
I mean it's just a cable but we have seen funny behavior with things that shouldn't happen.

 

[jsmith]

Just a quick question.
Did you swap the cable to the one from the new unit as well or did you keep the "old" one?
I mean it's just a cable but we have seen funny behavior with things that shouldn't happen.

Vantrue had sent me a new cable a few days ago as I accidentally mangled the original that came with the box. I tested BOTH the mangled one (still worked) and new cable I received a few days ago with the Original N4 Pro S + F 1.6. It didn't change the outcome on the rear camera feed dropping.

On the replacement unit, I ran the same test with those cables utilizing the F 1.6 Rear Camera, and the rear feed never dropped out.

I then tested the OLD (Original) N4 Pro S with the F 1.8 camera that came with replacement unit, and it works 100% with F 1.8 Rear camera. No Dropouts in collision mode or low bitrate.

Cable isn't the issue.