jsmith
Well-Known Member
It's a bit random, you don't lose the rear camera every time, just MOST TIMES. Crash it a few more times and see if rear camera drops.
Is your test with the OBDII or the 3 wire Hardwire kit using Battery + Ground (No ACC)?
N4 Pro S Review
- Thread starter Hack_man
- Start date
It's a bit random, you don't lose the rear camera every time, just MOST TIMES. Crash it a few more times and see if rear camera drops.
Is your test with the OBDII or the 3 wire Hardwire kit using Battery + Ground (No ACC)?
OP
OP
Hack_man
Well-Known Member
I am not using an OBDII or 3 wire H/W kit.
I am powering the camera via Vantrue's USB-C cable to the DC input port and waiting for 5 minutes of inactivity which enables LBR Parking Mode.
This test was repeated with the Rear Camera 5 times and I got the same result each time when attempting to connect the App after exiting Parking Mode:
App tries to connect to Live View while showing Parking Mode frame rate (15 FPS) which is not correct (should be showing 30 FPS Driving Mode)
App dumps to "Connect your Device" screen
Camera freezes on all three (front, interior, rear)
Camera reboots
All 3 lenses start working again. I don't have to remove and plug back in the rear camera.
I am powering the camera via Vantrue's USB-C cable to the DC input port and waiting for 5 minutes of inactivity which enables LBR Parking Mode.
This test was repeated with the Rear Camera 5 times and I got the same result each time when attempting to connect the App after exiting Parking Mode:
App tries to connect to Live View while showing Parking Mode frame rate (15 FPS) which is not correct (should be showing 30 FPS Driving Mode)
App dumps to "Connect your Device" screen
Camera freezes on all three (front, interior, rear)
Camera reboots
All 3 lenses start working again. I don't have to remove and plug back in the rear camera.
Last edited:
OP
OP
Hack_man
Well-Known Member
I learned something new. Don't put an SD card formatted for a Vantrue camera into an A229 Pro.
I accidentally switched SD cards between A229 Pro and N4 Pro S and the Viofo camera spit out "SD Card Error" or something like that.
Attempting to reformat SD card in Viofo Camera resulted in "Format Unsuccessful".
I had to format it in the Vantrue camera first and then the A229 Pro allowed me to format it.
The Vantrue camera was much more forgiving of the Viofo formatted card.
I accidentally switched SD cards between A229 Pro and N4 Pro S and the Viofo camera spit out "SD Card Error" or something like that.
Attempting to reformat SD card in Viofo Camera resulted in "Format Unsuccessful".
I had to format it in the Vantrue camera first and then the A229 Pro allowed me to format it.
The Vantrue camera was much more forgiving of the Viofo formatted card.
Last edited:
jsmith
Well-Known Member
Try using Collision Detection Setting. See if it goes to 2 channel after it wakes back up. That seems to happy every time.
OP
OP
Hack_man
Well-Known Member
I added that test case (N4 Pro S without HDR and without PlatePix) to post #42
OP
OP
Hack_man
Well-Known Member
I enabled Collision Detection and repeated the test.
I waited 5 minutes for the camera to go into Parking Mode and then force it to go into Driving mode with some motion
The App connected to the camera and displayed working Live View on both channels (Front and Interior)
This worked 2 out of 2 times
So I was able to confirm what you said, The App connects fine when coming out of Collision Detection Mode but not from Low Bit Rate Recording Mode.
Although in your case you were still having problems with the rear camera, which I was not.
Last edited:
jsmith
Well-Known Member
So to confirm and clarify, the camera wakes up properly from Collision Detection Mode (doesn't crash), but only the front and interior camera feeds work. The rear camera drops and the rear feed doesn't show up on the app either. Is this correct?
jsmith
Well-Known Member
OP
OP
Hack_man
Well-Known Member
My bad, I can understand the confusion. I was only testing 2 channels (Front and Interior) with no rear camera with Collision detection.
I'll run another test using all three channels with collision detection.
I found no problem with 2 channels during this test.
@jsmith I reran the test in collision mode with all three channels and found no problem.
The camera was powered by the Vantrure USB-C cable connected to the Camera DC Input port.
Parking mode (collision) was initiated by allowing the camera to be still for >5 minutes.
Driving mode was initiated by moving the camera.
The app successfully connected after entering Driving mode
Live view appeared, then all three channels were functioning on the live view screen and the App correctly displayed 2160P+1080P+1440P 30 FPS
I am not having any problem with the App when Collision Parking mode transitions to driving mode. Two and Three channels work fine.
Last edited:
jsmith
Well-Known Member
1. Try powering unit through GPS Module and repeating test to see on 3 channels if all 3 channels wake up.
2. Let the camera sit for 15-20 minutes before connecting with the app
There might be two issues here if you can't repeat the dropped rear camera. @EricSan have you tested out all the things from above yet?
A. I've found a firmware bug (or a development flaw)
B. My camera port for rear camera is faulty
jsmith
Well-Known Member
@Hack_man @Jeff_Vantrue @EricSan
I tested the cable I mangled a bit and the new cable, and both drop out channels. So it definitely isn't a cable issue. I lose the rear camera every time in collision mode after camera wakes up.
Far as the units crashing, well that has been replicated.
I tested the cable I mangled a bit and the new cable, and both drop out channels. So it definitely isn't a cable issue. I lose the rear camera every time in collision mode after camera wakes up.
Far as the units crashing, well that has been replicated.
OP
OP
Hack_man
Well-Known Member
I'm not having problems with losing the rear camera in collision mode after the camera wakes up
To summarize my findings:
1. Collision Mode: I had no problem connecting with the App (no crashes or freezing cameras on any of three channels). I could reliably exit Collision mode either by transitioning the ACC terminal to +12V or by jiggling the camera awake.
2. LBR Recording: App crashed and camera rebooted when I exited LBR parking mode by jiggling the camera but NOT when I exited LBR mode by transitioning the ACC line to +12V
3. Once the camera enters LBR Parking Mode and then successfully connects with the camera, the camera resolution and frame rate displayed by the App is INCORRECT.
If the camera never enters LBR parking mode, the App displays correct Driving Mode channel resolutions and FPS (2160P+1080P+1440P 30 FPS).
4. I have had no problems at all specifically related to the rear camera
I still need to test @jsmith condition of waiting 15-20 minutes before connecting with the App, so far my tests were connecting after a few seconds of exiting Parking Mode. I have always been powering unit thru the GPS Module during all of these tests.
I think @jsmith has identified a firmware bug when exiting LBR recording while not using the ACC signal.
To summarize my findings:
1. Collision Mode: I had no problem connecting with the App (no crashes or freezing cameras on any of three channels). I could reliably exit Collision mode either by transitioning the ACC terminal to +12V or by jiggling the camera awake.
2. LBR Recording: App crashed and camera rebooted when I exited LBR parking mode by jiggling the camera but NOT when I exited LBR mode by transitioning the ACC line to +12V
3. Once the camera enters LBR Parking Mode and then successfully connects with the camera, the camera resolution and frame rate displayed by the App is INCORRECT.
If the camera never enters LBR parking mode, the App displays correct Driving Mode channel resolutions and FPS (2160P+1080P+1440P 30 FPS).
4. I have had no problems at all specifically related to the rear camera
I still need to test @jsmith condition of waiting 15-20 minutes before connecting with the App, so far my tests were connecting after a few seconds of exiting Parking Mode. I have always been powering unit thru the GPS Module during all of these tests.
I think @jsmith has identified a firmware bug when exiting LBR recording while not using the ACC signal.
Last edited:
OP
OP
Hack_man
Well-Known Member
I tested your proposed condition (waiting 20 minutes before connecting with App. Collision Mode. All three channels.
I completed Three test runs, one refused to connect with Wifi, the other two worked fine.
I did not experience the dropped rear camera incident that you were reporting
Last edited:
OP
OP
Hack_man
Well-Known Member
@Jeff_Vantrue Why can't Low Bit Rate recording work in conjunction with the collision sensors so that an audible tone or message is played when the car is started and a collision was detected during LBR parking mode? I know all parking footage is stored during LBR mode to a Parking Folder regardless of a detected collision, but it would be nice if there was audible notification.
If a collision is detected in Collision Mode, there is a quick message displayed on the screen but an audible message would be so much better for all parking modes.
If a collision is detected in Collision Mode, there is a quick message displayed on the screen but an audible message would be so much better for all parking modes.
jsmith
Well-Known Member
Sounds like I got a faulty rear or front camera. Although the flip side I did identify universal firmware bugs (Camera Crashing when Exiting Low Bitrate).
Thank you also for highlighting these bugs. I’ve shared them with our team for further investigation. Once we have any updates or solutions, I’ll be sure to keep you informed here.
Thank you very much for your suggestions.
At present, the dash cam's displays an on-screen message if a collision is detected during all parking modes.
Some users prefer audio alerts for peace of mind, while others find them disruptive, so we'll need to carefully assess how to best implement this without affecting the overall user experience.
I've shared your suggestion with our product team for further evaluation.
At present, the dash cam's displays an on-screen message if a collision is detected during all parking modes.
Some users prefer audio alerts for peace of mind, while others find them disruptive, so we'll need to carefully assess how to best implement this without affecting the overall user experience.
I've shared your suggestion with our product team for further evaluation.
jsmith
Well-Known Member
@Hack_man @EricSan @Jeff_Vantrue @Karagandinez
I did a couple Quick Tests (I'm Sick with Covid at the moment) just to examine the previous discussed issues with the NEW REPLACEMENT UNIT Vantrue sent. The New Camera did Crash (Firmware Bug) as described in great detail above. However, I did not lose my Rear Camera Feed on the Replacement N4 Pro S with either Low Bitrate or Collision Detection. Therefore, I suspect the prior unit I was sent has a faulty rear camera port.
So yes, I did identify a major firmware bug (camera crashing), but the second half of the problem (losing rear video feed), PRELIMINARILY appears hardware related.
There may be another bug I identified on both cameras, but I will need to verify before posting. None the less, if anything changes I'll update this thread. Be patient, I'm doing this while not feeling well!
I did a couple Quick Tests (I'm Sick with Covid at the moment) just to examine the previous discussed issues with the NEW REPLACEMENT UNIT Vantrue sent. The New Camera did Crash (Firmware Bug) as described in great detail above. However, I did not lose my Rear Camera Feed on the Replacement N4 Pro S with either Low Bitrate or Collision Detection. Therefore, I suspect the prior unit I was sent has a faulty rear camera port.
So yes, I did identify a major firmware bug (camera crashing), but the second half of the problem (losing rear video feed), PRELIMINARILY appears hardware related.
There may be another bug I identified on both cameras, but I will need to verify before posting. None the less, if anything changes I'll update this thread. Be patient, I'm doing this while not feeling well!
Last edited:
jsmith
Well-Known Member
@Hack_man @EricSan @Karagandinez @Jeff_Vantrue
Please test:
New Firmware Bug
I also confirmed on both cameras, that the N4 Pro S DOES NOT wake up from Collision Detection Mode on the OBDII. You have to tap on camera or press a button before the camera "Wakes Up". It will not do so on its own when starting car and driving.
Please test:
New Firmware Bug
I also confirmed on both cameras, that the N4 Pro S DOES NOT wake up from Collision Detection Mode on the OBDII. You have to tap on camera or press a button before the camera "Wakes Up". It will not do so on its own when starting car and driving.
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.