VIOFO A119S stopped working

ok that should be fine then, issues when connected via the mount are the problem for most, the power supply will be fine for the camera
Not that this totally rules out a poor power supply, but it certainly seems more unlikely now no? You said Street Guardian uses higher end power supplies, so assuming the power supply is working properly, that's probably not what caused the firmware corruption. Would be nice to get this figured out.
 
Not that this totally rules out a poor power supply, but it certainly seems more unlikely now no? You said Street Guardian uses higher end power supplies, so assuming the power supply is working properly, that's probably not what caused the firmware corruption. Would be nice to get this figured out.

there's always a cause, it's a matter of working out the pattern to the problem and go backwards from there, we've bugfixed probably 100 or more things in the Novatek platform over the last 2 years, it takes time, I don't have an A119 so can't really do much myself but just trying to collect some info and see what the pattern is
 
It died on me again with the X boxes, yesterday, with fw 1.6. This is the third or fourth time she has hung up in a couple months.
... So I formatted the replacement memory card and put 1.7 file on it. Once I reflashed the A119S, it started working again....
So maybe a faulty memory card could be part of the equation that causes this to happen?
Not that this totally rules out a poor power supply, but it certainly seems more unlikely now no?.... Would be nice to get this figured out.
As in the case of @Rhody401, seems the microSD card may get corrupted as well as the firmware. So until the problem is solved, perhaps replacing or at least reformatting the microSD card should be included in the toolbox of things to try to fix the symptoms, along with re-installing firmware and fixing any power problems.
 
Well I have a new card in there now and 1.7. We'll see if the problem goes away. If not, i'll try a new power supply. I do have a few hardwire kits lying around, from CYA, that I havent gotten around to installing yet. One of them is supposed to be to put my trusty Street Guardian in this same vehicle as a rear facing cam. The car has been rear ended twice in just over a year.

I have an A119s in one of my other vehicles, which is same make and model and year, and it has been flawless. That one has the factory power supply with the double cig lighter plug, and the original firmware. 0.9 or 1.0 (I bought a bunch of A119S, A119, A118c2 at once and have them in several fleet vehicles)
 
Last edited:
Had similar problem with my A119S reported here https://dashcamtalk.com/forum/threads/a119s-firmware-v2-1.30638/page-3#post-366854 , but moved discussion to this thread because problem appears similar and does not seem to be related to a particular A119S firmware version. @jokiin @viofo, I was able to restore function to my A119S with X-box/hash/freezing screen problem without re-loading firmware, after defaulting settings twice and several other actions. Still early checking but seems to be working OK so far. Not certain what actions were key to restoring operation but took some notes and will try to write something up within the next few days. Looking to provide clues to enable a fix to prevent the problem rather than provide a new way to fix the symptoms.
{Edit: Recent related posts:
https://dashcamtalk.com/forum/threa...rking-but-maybe-sensor-bad.31115/#post-368848, and https://dashcamtalk.com/forum/threads/corrupt-display-on-startup-a-possible-cause.31374/#post-371478, and https://dashcamtalk.com/forum/threads/help-with-screen-diagnosis.31438/#post-372166, and https://dashcamtalk.com/forum/threads/help-with-screen-diagnosis.31438/#post-372418 and https://dashcamtalk.com/forum/threads/viofos-a119s.26309/page-23#post-373001, and https://dashcamtalk.com/forum/threads/viofos-a119s.26309/page-24#post-373228, and https://dashcamtalk.com/forum/threads/viofos-a119s.26309/page-24#post-373241 and https://dashcamtalk.com/forum/threads/xxxxxx-boxes-bug-fix.31754/, and https://dashcamtalk.com/forum/threads/viofos-a119s.26309/page-24#post-378083, and https://dashcamtalk.com/forum/threads/screen-freeze-issue-on-2-4-firmware.34334/#post-406532, and https://dashcamtalk.com/forum/threads/full-camera-frozen.34342/#post-406557.}
 
Last edited:
We are still checking this, it is very strange. Reset the camera to default before showing XXXX can solve the issue.
 
There was a user in the Viofo support forum that just reported getting the XXXXXX issue and said he notice some extra files on the memory card. He said he had pulled the card to look at files on the computer, using Winamp for something, and the issue occurred immediately after putting the card back in the camera. He said the files appeared to be from Winamp. Wonder if anyone else who has had this issue can remember if it occurred after putting the card back in the camera after viewing files on the card elsewhere. It was the first I had heard of a user noticing some odd extra files on their card after having the XXXXX issue occur.
 
Wonder if anyone else who has had this issue can remember if it occurred after putting the card back in the camera after viewing files on the card elsewhere.
Don't recall such happening. Unfortunately, I deleted all files on the card on a PC before the issue was discovered.
 
Don't recall such happening. Unfortunately, I deleted all files on the card on a PC before the issue was discovered.
That's something that is better avoided, copy what you want but don't delete, format the card once you put it back in the camera
 
Always good practice to format the card in the camera after it has been in a different device, random files that can get written to card can cause issues
If these files did cause the issue and it occurred immediately after putting the card back in the camera, then there wouldn't be time to format in the camera. The boot up would have already happened.
I have no idea if these files could have caused the issue or not, but found it interesting and worth noting.
 
From experience I have found that if there are files on the card that don't belong it may not trip up immediately but can eventually lockup, more so if the card is full
 
Mine has behaved for several months since I updated the firmware and put a brand new memory card in

Sent from my SM-G955U using Tapatalk
 
Had similar problem with my A119S reported here https://dashcamtalk.com/forum/threads/a119s-firmware-v2-1.30638/page-3#post-366854 , but moved discussion to this thread because problem appears similar and does not seem to be related to a particular A119S firmware version. @jokiin @viofo, I was able to restore function to my A119S with X-box/hash/freezing screen problem without re-loading firmware, after defaulting settings twice and several other actions. ...

A year later, and I got XXXXXX. Not sure when it happened but I was going to upload my RO files because I had 2 this week, and I see my last good regular file was from a few days ago, plus 2 very small videos.
Did you ever write up what to do?
How do I "default settings" when the dashcam is unresponsive. As everyone else describes, the display is live (at least for a while) and it beeps when I press buttons, and reboots when I push with a paper clip, but I can't use the buttons to get to the menu where I would set default settings.
 
A year later, and I got XXXXXX. Not sure when it happened but I was going to upload my RO files because I had 2 this week, and I see my last good regular file was from a few days ago, plus 2 very small videos.
Did you ever write up what to do?
How do I "default settings" when the dashcam is unresponsive. As everyone else describes, the display is live (at least for a while) and it beeps when I press buttons, and reboots when I push with a paper clip, but I can't use the buttons to get to the menu where I would set default settings.
With the camera off, remove the memory card. Start up the camera and try to enter the menu. It may take multiple tries to enter the menu. If it lets you in, navigate to the Default Settings option. If you can't enter the menu, just install the latest firmware available on the Viofo site. Copy the .bin file (firmware file) to the card using a card reader, then insert into the camera and start it up. Update/install will be automatic. Once it's finished (about 1 min or so), go into the menu and manually default the settings.
 
With the camera off, remove the memory card. Start up the camera and try to enter the menu. It may take multiple tries to enter the menu. If it lets you in, navigate to the Default Settings option. If you can't enter the menu, just install the latest firmware available on the Viofo site. Copy the .bin file (firmware file) to the card using a card reader, then insert into the camera and start it up. Update/install will be automatic. Once it's finished (about 1 min or so), go into the menu and manually default the settings.

I was able to get to the Menu to Default Settings by starting with the memory card out, and that didn't do it, but upgrading the firmware from 2.06 to 4.0 was incredibly easy. (I don't like to do firmware -- as a software engineer I tend to break things.) I entered all my non-default settings.
The only hint I needed from the video is "Computer-to-mini-USB cord" plus "Telephone USB wall wart" makes power supply for the camera, so I could test it indoors instead of running out to the car. I don't know that my life will be better with 4.0 firmware, but it is at least as good as it was. (And next time I think I can enter my tag in the CarNo_Backup.txt instead of entering it in the menu.)
Thank you.
 
Last edited:
Back
Top