nanoQ 0903

Just updated to 3/29 FW, Thanks guys. Here is the log on gps:

V,030416,212317.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212318.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212319.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212320.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212321.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212322.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212323.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212324.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212325.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212326.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212327.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212328.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212329.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212330.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212331.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212332.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212333.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212334.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212335.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212336.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212337.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212338.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212339.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212340.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212341.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212342.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212343.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212344.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212345.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212346.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212347.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212348.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212349.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212350.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212351.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212352.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212353.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212354.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212355.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212356.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212357.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212358.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212359.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212400.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212401.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212402.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212403.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212404.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212405.078,,,,,,+0.14,+2.67,+0.38;
V,030416,212406.078,,,,,,+0.14,+2.67,+0.38;

I will leave the device on for longer to see if signal is good. TIA.

WDR is saved.
 
After 15 min. new gps signal in place. It looks like 3/29 FW took care of the problem. Thanks guys for all your help.
 
Clean the lens and your windscreen. It looks like you have grease on the windscreen so use some detergent.
Yes, upon 2nd view it seems there's some dirt/scratch at the middle of lens, which explain why light only disperse at the middle. I will try and clean it.
Clean the lens and your windscreen. It looks like you have grease on the windscreen so use some detergent.
Capture_zpsfx3w8hmt.png

Seems like my lens has some scratches. Not sure if this is production issue but I didn't mistreat my nanoQ. May I know if there's any hacks to fix this?
 
Wow, that's some major scratches. Is it repairable?
 
Anyone know why the camera does not support 128gb MicroSD cards ? Or is the hardware able to support it and it is then
a software issue ?

Is the filsystem still fat32 ?

I would expect any new dashcams (or actioncams) as of 2016 to have 128Gb support ?
 
that is the Novatek SDK limit.
There is exFat support in Ambarella A12 SDK which we are researching, sounds to support primary SDXC which up to 2TB.
but we need to verify later.
 
Aha, ok so it is just a SDK limit, has nothing to do with the hardware !

So in the future old hardware or dashcams could get support for 128Gb, you just need a new SDK that has support for it.
So Novatek need to fix the SDK to get it out to manufacturers and then they in turn can create new firmware with the support.

Nice, lets hope for this in the future then, make this happen novatek !

ExFAT is nice but FAT32 will still work as is.
 
Aha, ok so it is just a SDK limit, has nothing to do with the hardware !

the hardware needs to be capable but assuming specification is correct then yes it's just a matter of paying the license fee to get the updated SDK, it isn't cheap though which for the most part is why you don't see it being offered on many models
 
So Novatek need to fix the SDK to get it out to manufacturers and then they in turn can create new firmware with the support.
I suspect it will never happen for the processor the 0903 uses, exFAT is one of the advantages of using Novatek's newer and more expensive processors with newer SDKs.

There doesn't seem to be much advantage of exFAT anyway, if you want your files to be safe then you want to start new ones frequently anyway and as long as there are viewers which can handle multiple segments then it is not an issue. In some ways FAT is the more resilient file system.
 
Oh, so you need a new SDK and they will not provide you with a cheap upgrade. If that is the case, 64Gb will do just fine. At least the hardware has support for 128Gb
so we might get that sometime in the future. ExFAT has only one advantage, the 4Gb limit is gone, but other than that, not worth paying premium for that if
you can use FAT32 instead. And at least for dashcams it is a total waste as everyone is recording segments anyway. FAT32 is also much more supported on
different platforms.

However for DSLR this could be a issue, but a DSLR is so much more expensive so in that case I do not thing they care if they have to pay
extra for ExFAT. Actioncams, I do not know, it might be nice to have ExFAT, I do not know. But I guess most do record clips on a actioncam
anyway and not continues, then you edit it together to look the way you want.
 
exFAT itself as a filesystem should be more resilient than FAT32 - it's the less mature implementation of it that has let it down in the cameras I've tried with it so far.

It should stand up better to cameras that don't shut down cleanly (if you're in that situation you're better off getting a new dashcam anyway) or being forcefully removed from Windows without being ejected / removed first to flush the cache to the flash memory.

A lot of cameras are working with larger than 32GB cards formatted as FAT32 but it's by luck rather than design and why most don't let you format a larger than 32GB card inside the camera.
 
However for DSLR this could be a issue, but a DSLR is so much more expensive so in that case I do not thing they care if they have to pay
extra for ExFAT. Actioncams, I do not know, it might be nice to have ExFAT, I do not know. But I guess most do record clips on a actioncam
anyway and not continues, then you edit it together to look the way you want.

Put it this way, as you mentioned for a DSLR it's an expensive product so the relative cost is not so much, for some of these dashcam/action cams the upfront cost of adding the exFAT license could add 30% to the factory cost of the camera
 
exFAT itself as a filesystem should be more resilient than FAT32 - it's the less mature implementation of it that has let it down in the cameras I've tried with it so far.

there are some home brew versions of exFAT and some hacked SDKs is the problem, a lot of the products that have exFAT support are not using the Microsoft licensed version

A lot of cameras are working with larger than 32GB cards formatted as FAT32 but it's by luck rather than design and why most don't let you format a larger than 32GB card inside the camera.

A bit of both, the large card FAT32 support needs to be in the SDK for it to work properly
 
I was going to say the only camera I've seen so far that worked natively with the larger sizes was the SG9665GC - are the Novatek SDKs chargeable like Amba then?
 
Do you guys think I have a focus issue? Here is a sample picture:
2016_0406_103544_001.JPG
 
It does look like it's focused a bit too close. Were you stationary?
 
The latest cam i just got from diggcams was nicely in focus. I think QA is picking up a bit.
 
I was stopped at stop light. Other dashcam should be able to get the sign perfectly. This dashcam seems to be foscus on the dashbaord.
 
Back
Top