). At that point I was able to enter the menu, but after defaulting the settings and restarting, it hung on the logo again. I then opened it up and found that the latch bar that holds the ribbon cable secure to the main board had somehow popped up enough to release some of the cable. There was even tape over the connector and cable holding things together. Not sure how that could have happened, but once I secured the cable, the camera started up fine. So I had an interesting thing happen with a A119 today. I mention it because of the possibility of it being related to this XXXXXX bug. I had a A119 return show up today that was hanging on the Viofo logo. The user said he was able start the camera normally when he first received it, but this issue occurred soon after. I knew it had the the most recent firmware, V3.3 (hanging on the logo bug was fixed awhile back), but he tried to reload it anyway. No luck. Anyway, I sent him another and had a feeling I knew what the issue was with the defective one. When I got it, I power it up and it hung on the Viofo logo. I had a feeling it was related to the ribbon cable going from the sensor to the main board. So, while stuck on the Viofo logo, I rotated the lens. Nothing happened the first time except a single white line flashed on the screen, but I did it again and the screen did that weird thing where 1/3 of the screen on the left was jumbled and 2/3rds on the right was black (or static, don't remember now
Now while I did not see the XXXXXXX on the screen, the weird scrambled screen issue appeared. Some users just experience the XXXXXX issue, while others like @harsh have experienced the XXXXX issue and the screen issue at the same time. I'll assume they are related in some way. Maybe this firmware corruption is related to a poor connection of the sensor to the main board? This might explain why most have never had any issues, while others seem to get it multiple times.
Maybe those who have had this happen should check the connection. Maybe even re-seat the cable. Might be worth a shot.
The three faces of Eve
, I mean the X-box problem that I saw during my X-box episode included one with the hash and no button action but no X-boxes (see photo #3 - IMG_403 below). Since many have fixed the problem reloading the firmware, seems unlikely to be a hardware problem but you never know. However, as my problems were resolved without reloading the firmware, maybe the firmware itself is not being corrupted, unless it was able to fix itself. Don't know enough to guess what else it might be. Sorry, my better photo files of #3 face were to big to upload, but believe me, there were no X-boxes on that screen. In all three of the photos, the camera was not recording even though the REC light was steady ON. The was no blinking red dot on the status screen over-lay. When the Hash (photo #2) goes away the picture on the screen is live and active, but the camera is still not recording.
I suppose it all depends on what is causing the corruption. The camera will do all sorts of strange things when the ribbon cable isn't connected properly. It's not always the same result. Could be the degree of the poor connection. What I experienced could have nothing to do with the XXXXX issue, but I feel it's something to keep in mind. I do find it odd that most have never experienced this (including myself on my personal cameras) and those that have experienced it, have seen it multiple times.The three faces of Eve
View attachment 34383 View attachment 34384 View attachment 34385
I keep mine firmly on the clicks and there is no problem with lens angle.
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
|
Waterproof case for A119S | A119S | 13 | |
| S | Interesting failure of an A119S (v2). | A119S | 3 | |
| P | Blurry image A119SV2 | A119S | 13 | |
| L | Keeping the A119S inactive but "charged" when not in use | A119S | 7 | |
| C | A119S freeze | A119S | 2 |
