Skip to main content

A Google Nexus 5 review - All you want to know, battery camera speed and more !!

This post is about the NEXUS 5 , I have been using this phone for around 15 days, I got this phone on 8th November . So to know about the battery life, camera , the pros and cons read it further.

Phone spec:
  • 16gb.
  • 5" display.If you have tiny hands it will be difficult to use :)
  • 1920x1080 display.
  • Snapdragon 800, 2.26GHz processor.
  • LTE Enabled.
  • Wireless charging.
  • Android 4.4 aka kitkat.
  • 1.3 MP front facing and 8 MP rear facing camera.
  • 2300 mAh battery.

Pros:
For me battery life was a huge improvement as I was previously using Samsung galaxy S3 whose battery life sucked big time. Now battery lasts for almost a day (9 AM- 11PM) with the following applications being used :

  • Wi-fi on for all the time.
  • Bluetooth for around 30 mins.
  • All of the auto sync on.
  • Facebooking.
  • Nike+ app running for 30mins without GPS.
  • Playing some small games.
  • Extensive use of google now.

  • With all of these and moderate use of other apps, battery lasts for a day. So, Nexus5 is pretty impressive when compared to galaxy S3.

    Google now: is pretty neat in kitkat when compared to the older jelly bean, especially in recognizing most of the speech. It's pretty fast and all the animations are smooth.

    Clock app: looks good and is easy to use but it’s little difficult to change the alarm setting.

    Screen:Screen is really good, large and bright. Everything looks clear and crisp.

    In brief the best things about this phone are its screen, battery life, processing speed and smoothness !!

    Cons:
    Now comes my favorite part!! The entire time I was writing the above section, I was dying to jump to this part, as Nexus 5 sucks in many many ways!!

    First the Camera: I know Google has ads about Nexus 5's camera, but I am guessing none of those folks in the ad used Nexus 5’s camera for they surely would not have dared to make an ad like this . The camera functions fine as long as you don't touch the screen while clicking pics but if you do touch the phones screen to change focus (towards bottom left specially) this is what happens


    Basically it’s an awful 8 MP camera!! But Google has gone ahead to say that it's just a software glitch and they will be releasing an update to fix it, so let’s wait and watch.

    Settings: As I mentioned earlier in this post, I was a Galaxy S3 user .And all I had to do to turn on the Wi-Fi /Bluetooth was, pull down the notification bar and press the icon and TADA!! It’s done. But kit Kat takes you to the settings to turn it on now, which is kind of sad because it’s a whole 3 step process instead of one (an easy solution could have been to have a widget to control these settings).

    LED notification: I am not aware how this worked in Jelly bean version, but I am really not happy about the way notification LED is being handled in kitkat. You are notified for mails, sms, battery charging and other Google products but none of the third party apps (like whats app) are notified through LED. For that, one has to install a paid version of Light flow.

    Ear piece: If you move the earpiece even little bit while talking it ll become extremely hard to listen, sometimes you wont listen anything . One will be constantly adjusting the phone to make sure the earpiece is directed properly.

    In the end, should you buy this ?? and the answer is, if you don't mind having a bad camera and want a phone which will last for, say a day easily, this phone is for you.

    Comments

    Popular posts from this blog

    Enable stats GUI on haproxy.

    Add bottom snippet to the haproxy.conf below the defaults section. listen  stats         bind 19.41.259.10:1234         mode            http         log             global         maxconn 10         clitimeout      100s         srvtimeout      100s         contimeout      100s         timeout queue   100s         stats enable         stats hide-version         stats refresh 30s         stats show-node         stats auth admin:password         stats uri  /haproxy?stats Make sure you are updating the IP address on the bind to your VIP and if you want, you can change the port also. One can even change the uri on the last line of the above snippet, like stats uri /haproxy_stats or whatever one wants. To make sure you have not done any mistake in the config file, one can use the following command to validate. haproxy -c -f haproxy.cfg Once everything looks good, restart the haproxy process and stats GUI should be available at 19.41.259.10:1234/hapro

    Sending a SIGHUP signal to some external process from Python script

    Code : import psutil import os import signal pids = psutil.get_pid_list() for pid in pids: if psutil.Process(pid).name == "process_name": os.kill(pid,signal.SIGHUP) break Steps to follow. 1.Get the PID of the process, in this case  "process_name"   to which you want to send out a SIGHUP signal. 2.Use os.kill(pid,sig) command to send out the SIGHUP signal to that process. 1.Get the PID of the process to which you want to send out a SIGHUP signal. One has to install a package called psutil by the following command. easy_install psutil Check out the following links for more details https://code.google.com/p/psutil/ https://pypi.python.org/pypi/psutil use psutil.get_pid_list() to get all of the PIDs. psutil.get_pid_list() works in the following manner.  pids = [ int ( x ) for x in os . listdir ( '/proc' ) if x . isdigit ()] return pids once you get all the PIDs get the PID you are i

    How to enable Openstack Octavia, LBaaS V2 with devstack.

    Little Intro to Octavia. Octavia is a service manager for Openstack Load balancer as a service. Neutron LBaaS V2 plugin talks to Octavia through Octavia driver. Octavia driver talks to Octavia api(o-api) and that in turn talks to Octavia control worker(o-cw). Neutron LBaaS V2 Plugin ----> Octavia plugin driver -----> o-api ----> o-cw Other than o-api and o-cw Octavia has 2 more components, housekeeping(o-hk) and health manager(o-hm). o-api Octavia api server which receives all the request from octavia LBaaS driver and passes it to o-cw. o-cw It's the main workhorse, it creates the load balancer VMs( amphorae ), configures them. o-hk keeps track of spare amphorae. o-hm Manages the health of the amphorae through heartbeats, collects the stats and takes care of fail over by creating a new amphora when it fails to get the heartbeat. How to enable Openstack Octavia, LBaaS V2 with Devstack. Since octavia uses a VM for loadbalancer its needs good a