After carrying Nexus phones for years I bought a Google Pixel in December 2016. That was just after the Pixel 2 was released, so the older Pixel was priced well and still offered great performance.
I was very pleased with the Pixel until quite recently. The OTA update to Android 9 (Pie) in August has been a huge step backward. Since that update the phone’s battery life has been dramatically reduced. Where it once lasted all day with my typical usage, it now lasts only about 7 hours with only light usage. Further, the phone is often noticeably warm to the touch.
Being the inquisitive sort, I’ve done some experiments to try and find out why this is happening. There are no rogue apps running. Or at least the OS reports no app using more that 2-3% of battery power.
I put the phone in Safe Mode for a day so only the factory installed apps would run. Battery life remained abysmal. That suggests that the problem is not caused by an app at all.
I’ve come to believe that I’ve identified the source of the problem. It’s related to the Wi-Fi. If I turn off the Wi-Fi the battery life is closer to what was experiencing running Oreo. Turn it back on and it plummets.
Let me be clear, I was a big fan of Google’s Nexus series. It started with the Galaxy Nexus, which impressed me so that I later bought a Nexus 4. In 2012 Google also released the first generation of the Nexus 7, which I also purchased.
The Nexus experience continued, so favorable that I didn’t even hesitate when they released a second generation Nexus 7 in 2013. I ordered one immediately.
The Nexus 7 saw heavy use around the house. I loved the Nexus 4 for a device on-the-go. It was the perfect size IMHO. Around the house, where fitting into my pocket was less of an issue, the Nexus 7’s larger screen made it my go-to device.
I’ve actually had three Nexus 7s over the years, replacing one with a shattered display, and later buying a spare when Google stopped offering them. I still have the Asus dock with micro-USB and HDMI ports that lets the tablet run on external power, even as you use it to feed a monitor or HDTV.
Throughout 2016 I carried a Nexus 5 mobile phone. So did my wife. Hers is the red one. She loves it.
My Nexus 5 suffered a crack in the display the very week that I bought it. In fact, that happened the very day that the screen protector was to arrive from Amazon. In frustration, I merely applied the tempered glass screen protector and kept using the phone for a year!
Over that time, although the phone worked perfectly, the crack grew. By the end of the year it was something of an embarrassment, so I broke down and bought a Pixel from Google.
Some have heard me rant that the move from Nexus to Pixel was disappointing. I maintain that the Nexus phones were an outstanding value, whereas the Pixel, while a fine instrument, is just another costly device.
My experience with the Pixel has been great. It’s a big step up in performance. Nougat is nice. I really like the fingerprint unlock feature. Battery life is exemplary, at least in my use case. USB C fast-charging is ok, although I do miss wireless charging.
One of the things I liked about the Nexus 5 on T-Mobile was that I enjoyed HDVoice calling to the few people I call most often. They are also T-Mobile customers, with suitably capable handsets.
This morning, for the very first time, I noticed that the Pixel indicates when it’s connected in HDVoice. I’m not sure if this indication is a new thing, or I simply never noted previously.
There aren’t too many people who get excited about HDVoice. I still do. It’ll be great we can pass HDVoice between carriers. Some say that’s happening now, but I see no evidence of it.
Until very recently I was seriously committed to Google’s Nexus line of devices. From the Galaxy Nexus onward, with just one exception, I carried a Nexus Series mobile phone.
I was so happy with the Galaxy Nexus, and Nexus 4 after it, that I jumped on the first generation of the Nexus 7 tablet in 2012. Similarly, my experience with that tablet was good enough that I bought the Nexus 7 2013 edition immediately upon it’s launch.
Later, when Google stopped offering them, I even bought a spare! I regret not purchasing the HSPA+ capable version when I saw it offered by Expansys at a discount.
That is a curious question. I certainly understand that people can be frustrated with Bluetooth headsets. It’s something that I have suffered now and then.
Class 2 Bluetooth, which is limited to 2.5 mW radiated power, is the most common variety. It’s supposed to deliver a 10 foot range. That’s fine when a mobile phone is in your pocket, but inadequate when it’s on your desk and you need to refill your coffee.
Class 1 Bluetooth kicks the RF power up to 100mW, aiming to allow you to wander up to 100 feet from the host device. Unfortunately, to achieve this freedom to roam, both the host and the headset must be class 1 devices. AFAIK, no mobile phone has ever had a class 1 Bluetooth radio.
I bought it back in February. There were two motivating factors at play; my Nexus 4 had become unreliable, and I was taken-in by the One+ One’s combination of reasonable price, flagship specs and limited availability.