You can upgrade the FW with 64gb card if formatted as FAT32.This same thing happened to me today. I noticed that the website says the new firmware can only be installed using a 32gb microsd. I was using a 64gb with no problems before. does anyone know if i can flash the new firmware using a 64 gb microsd?
for FAT32 do we get that by formatting card with the computer? And not with the cam? If so when the card is put back in cam it asks for a format with the cam.You can upgrade the FW with 64gb card if formatted as FAT32.
Regarding this bug, we are still checking on it, is not easy to repeat it.
for FAT32 do we get that by formatting card with the computer? And not with the cam? If so when the card is put back in cam it asks for a format with the cam.
Thanks for replyneed to format in the camera for FAT32, computer will format it exFAT when over 32GB in size
need to format in the camera for FAT32, computer will format it exFAT when over 32GB in size
After reinstalling the firmware, be sure to power the camera directly. Seems the power issue while powering through the GPS mount could be corrupting the firmware.I am experiencing this behavior, also, on one of the first v1's sent out. Bunch of boxes with X's on bottom, gps seems stuck at 1mph, clocks are frozen, not recording.
I'll reflash now to hopefully fix. I have a few of these v1 units.
After reinstalling the firmware, be sure to power the camera directly. Seems the power issue while powering through the GPS mount could be corrupting the firmware.
We have new firmware to solve this showing XXX box issue, will share this soon.
As this is a random issue, not easy to repeat, we need more users to do more testing to see if it is really fixed.
I also need this new firmware please.We have new firmware to solve this showing XXX box issue, will share this soon.
As this is a random issue, not easy to repeat, we need more users to do more testing to see if it is really fixed.
Any date for release?We have new firmware to solve this showing XXX box issue, will share this soon.
As this is a random issue, not easy to repeat, we need more users to do more testing to see if it is really fixed.