Ordro Q505W 1296p Dashcam review

Disclaimer: Camera provided by gearbest.com. Buy here : http://goo.gl/QbmJJz

After reviewing excellent 1080P cameras(Mobius and SJCAM M10), I was pretty excited to review a 1296P dashcam. On paper, it sounds very nice. Higher resolution means better chance of catching the number plate, and better overall quality.

Unfortunately, the Ordro Q505W disappoints . Sure, its a 92$ 1296p dashcam, but with the abysmally low bitrate, it does not really feel really good. There are a couple of pluses though. Exposure and colors are pretty accurate, and the WIFI interface is good to use. But in the end, the overall quality is not very good. If you are able to get a much higher discount, well you can take a look at it, but at 92$, there are other options available.

Some screenshots(Click to see full size)

The Daytime footage has pleasing colors and exposure is good even against the sun. But the sharpness is clearly lacking

Daytime footage   Into the sun

 

The Night footage is quite bad. Even on well lit streets, its barely acceptable.

Night 2Night 1

 

And finally, lets take a look at the review video

 

TL;DR : Not recommended

Got a VPN? Make sure you plug the leaks too!

A VPN. Its often touted as the all encompassing answer to your “blocked website” woes. Unfortunately, just getting a VPN and switching it on is not enough. To make sure you are complete protected you need to fix two common holes.

  1. DNS leaks : While data goes through VPN, your DNS queries may still go through regular ISP connection
  2. WebRTC : This leaks your IP address, inspite of connecting through VPN

A site like ipleak.net can easily tell you if you have such a problem. If you do, well here is what to do.

DNS leaks can be fixed by using Google or openDNS as your DNS provider. However, if you do not want to do that for some reason, there is a fix in firefox if you are a socks proxy user. Type about:config in the address bar, and click on “I’ll be careful”. Just change network.proxy.socks_remote_dns to false. You are done.

For WebRTC leaks, just toggle media.peerconnection.enabled to false. Unfortunately, for chrome browser, there is no cure for desktop(Though android has a fix)

With these two fixes, your VPN is plugged. You may need to do this if you are the ssh tunnel type of user.  Always make sure you visit ipleak.net or a similar website to confirm the leaks.