Problem with application

P

ptomic

New Member
Joined
Sep 4, 2022
Messages
15
Reaction score
3
Location
Europe
Country
Serbia
I receive this message when I open settings in application after connecting to the camera.
54C77B12-9162-4859-A9CA-B1306E5A34DF.webp
 
You did not include any version info in your post. The -256 error is usually displayed when the request from the VIOFO app is not understood by the firmware currently installed in the dash camera.

There has been a recent update to the VIOFO app to fix some issues. I would first make sure you're using VIOFO app iOS version 2.9 or Android version 3.2.6.

I've been successfully using those VIOFO app versions with firmware version V1.1_0817 for the A119 Mini.
 
The App version is iOS 2.9 and the camera FW version is A119 Mini_V1.0.20220621. I plan to upgrade the camera FW to the new FW.
 
ptomic said:
The App version is iOS 2.9 and the camera FW version is A119 Mini_V1.0.20220621. I plan to upgrade the camera FW to the new FW.
Click to expand...
If I had to guess, the VIOFO iOS app v2.9 supports setting the HDR settings which first appeared in production firmware version V1.1_0817. The app may be sending a query to the A119 Mini about the HDR settings and the V1.0_0621 did not have that feature. One would hope the app would be able to suppress error responses for unsupported features in that version of firmware.
 
I setup a session to get a packet capture between an A119 Mini with firmware V1.1_0817 and the Android VIOFO app v3.2.6. I wanted to see what camera setting "cmd=2028" was associated with and if it was HDR related.

The VIOFO app sends a HTTP GET request with a parameter named "cmd" with a value of "2028". The A119 Mini firmware responds with a XML document containing the HDR "Start" and "End" time values (blue text in example).

1662616198771.webp


The older V1.0_0621 firmware does not support the "cmd" parameter value "2028". Upgrading the A119 Mini firmware to V1.1_0817 should resolve the error.
 
They really should put in a version checker as to not call to functions that do not meet the version. I know a ton of people that never upgrade the firmware.
 
JDtime said:
They really should put in a version checker as to not call to functions that do not meet the version. I know a ton of people that never upgrade the firmware.
Click to expand...
LMAO.
Raises hand.
I'm still running my A129 Plus Duos on firmware from 2020. lol
-Chuck
 
JDtime said:
They really should put in a version checker as to not call to functions that do not meet the version. I know a ton of people that never upgrade the firmware.
Click to expand...
I've sent this issue to VIOFO asking what they can do to make the VIOFO app more aware of the features available in the installed firmware version or handle (silently) any request for a request for an unsupported feature in the firmware that's currently installed.

The app could make one query to the firmware and ask what are the command (numbers) that are supported by the installed firmware and then they could restrict the app to the list of supported firmware commands. I do see a request with a "cmd=3014" and the large XML response is a list "<cmd>" and "<status>" values, but it doesn't contain a "<cmd>" entry for the 2027 (see below) or 2028 command. Without a list of the "cmd" parameter values and what they mean, it's hard to determine what exactly each one is used to accomplish in the app/firmware connection.

I'll see what VIOFO comes back with on this issue.

I examined the packet capture a bit more and found that "cmd" value "2026" is used to select the "HDR" feature option ("par" values: 0=Off, 1=On, 2=Auto). To adjust the start/end times for the HDR "Auto" mode, a "cmd" value of "2027" is used with a "str" parameter value with the start/end times in the format of "19:00-07:00".
 
As they say " if it aint broke, dont fix it " 😉
I must admit i update when i can, most scary have always been computer motherboard BIOS updates, CUZ i have heard horror stories, but knock on wood i have never experienced that myself.
I have as a younger geek some times messed around in reg edit in windows, and this have caused a need for a reinstall now and then. 😳
 
kamkar said:
As they say " if it aint broke, dont fix it " 😉
I must admit i update when i can, most scary have always been computer motherboard BIOS updates, CUZ i have heard horror stories, but knock on wood i have never experienced that myself.
I have as a younger geek some times messed around in reg edit in windows, and this have caused a need for a reinstall now and then. 😳
Click to expand...
I'm not suggesting having anyone generate HTTP requests to their VIOFO dash camera to change settings, I'm simply pointing out what the app is doing (or not doing). I want the VIOFO app to handle these issues in a graceful manner so the user is not presented with an avoidable error message.
 
I was just talking general, in regard to the post of "PP"
What you suggest sound more than reasonable, and could probably save viofos support team from some unneeded work.
 
rcg530 said:
I've sent this issue to VIOFO asking what they can do to make the VIOFO app more aware of the features available in the installed firmware version or handle (silently) any request for a request for an unsupported feature in the firmware that's currently installed.

The app could make one query to the firmware and ask what are the command (numbers) that are supported by the installed firmware and then they could restrict the app to the list of supported firmware commands. I do see a request with a "cmd=3014" and the large XML response is a list "<cmd>" and "<status>" values, but it doesn't contain a "<cmd>" entry for the 2027 (see below) or 2028 command. Without a list of the "cmd" parameter values and what they mean, it's hard to determine what exactly each one is used to accomplish in the app/firmware connection.

I'll see what VIOFO comes back with on this issue.

I examined the packet capture a bit more and found that "cmd" value "2026" is used to select the "HDR" feature option ("par" values: 0=Off, 1=On, 2=Auto). To adjust the start/end times for the HDR "Auto" mode, a "cmd" value of "2027" is used with a "str" parameter value with the start/end times in the format of "19:00-07:00".
Click to expand...
Sad part is its only a few extra lines of code. I've already told people to update their firmware as I know the apps will update on their phones then Ill get phone calls as to why its not working and how do we fix it... That and there are so many uninformed users who will just vote down and give bad reviews because they don't know any better.
 
JDtime said:
That and there are so many uninformed users who will just vote down and give bad reviews because they don't know any better.
Click to expand...
I gave those folks a special shoutout in my latest review at 34:03
 
You must log in or register to reply here.
Back
Top