writing about tech

Page 5 of 15

Misplace your FitBit? There’s (literally) an app for that

This morning, after my stationary bike workout, I misplaced my FitBit One. I knew it was either in my office (where the bike is) or my room, but I wasn’t sure which, and it’s small enough that it could’ve easily fallen in a corner somewhere. Unfortunately, there’s no “find my FitBit” feature on my phone – but it was still connecting to my phone via Bluetooth.

That’s when I got the idea to download an app that would show me Bluetooth signal strength – in my case BlueScan for Android, but there are certainly others for both iOS and Android. By looking at the signal strength, I was able to quickly determine which room it was in (the office) and where it was (on the floor next to my bike).

Signal strength low = not in the bedroom

Signal strength low = not in the bedroom

Signal strength high = probably in the office

Signal strength high = probably in the office

 

I figured this was a neat trick worth sharing, especially as more and more of us are carrying small, easy-to-misplace Bluetooth devices, whether it’s a fitness tracker, smartwatch, or headphones.

Daily Drivers Update, November 2014

Since I’ve had some fairly major changes in my Daily Drivers over the last couple of months, I thought it’d be a fun exercise to explain what has changed, why it changed, and what’s on the horizon.

Tablet

Old and Busted: Nexus 7 (2013)

New Hotness: iPad Air 2 (WiFi, 64 GB)

My history with tablets is a strange one, suffice it to say, I’ve gone through way too many, and I’m tired of making sacrifices in this area.  When it comes to upgrade cycles, I think tablets should be more like laptops than smartphones, and in that regard, the iPad Air 2, with its top-of-the-line processor, 64 GB of storage (finally), a laminated screen (finally), and 2 GB of RAM (finally) might finally be the tablet I can use for years to come. The iPad Air 2 is an iOS tablet that outperforms a 2011 MacBook Air and that’s, frankly, pretty ridiculous.  It’s also the first iPad I’ve used that – probably thanks to the added RAM – legitimately feels like a secondary computer, rather than purely a consumption device.  Of course, it is also a fantastic consumption device, because it’s still an iPad, and that’s where they truly excel.  I have more to say about the iPad Air 2, but that can wait until I’ve used it for a couple more weeks.

As for why the Nexus 7 got ditched – well, it’s complicated. I tended toward smaller tablets – originally the iPad Mini, and later the Nexus 7 – because I thought I’d carry them with me more.  Unfortunately, I found that with devices of that size, they’re often too big to conveniently carry around without a bag, but also, almost paraodically, too small to justify using over my phone, except perhaps for games or reading.  However, since I discovered that I greatly prefer a Kindle for reading books, those use cases became even smaller, and my Nexus 7 quickly became the device that rarely left the nightstand. The final nail in the coffin was that, despite Google’s best efforts, Android simply doesn’t have the software library of the iPad, especially when it comes to games – even for fairly major releases.  Hearthstone?  Finally coming in December, probably – almost eight months after its debut on the iPad.  FTL?  No word on if it’ll ever show up. After awhile, you get tired of waiting for Android tablet ports that, at best, show up “eventually”.

Phone

Old and (actually) Busted: Nexus 5

“New” Hotness: HTC One (M7)

This one is a bit different than the others, because my Nexus 5 is literally busted, in that the screen is broken. Fortunately, I had an old HTC One that was willing and able to take its place.  I’ve already gotten into detail a couple of times about why the HTC One is a fantastic phone, so I won’t bore you with that again, suffice it to say that over a year and a half later, it’s difficult to find a justification to replace it.  Like the iPhone 4 before it, I feel it’s a somewhat-timeless smartphone…at least as long the software updates keep coming. I certainly had my reasons for using a Nexus 5 for awhile, and I believe those reasons are still valid, but now that I’ve put the effort into making the HTC One as unlocked and open as my Nexus 5 was, I’m not in any rush to replace it again.

Smartwatch

Old and Busted: Pebble (original)

“New” Hotness: Moto 360

I’ve written a lot about the Moto 360, but the quick-and-dirty summary: no one needs a smartwatch, but they are useful, and if you want one, and have an Android phone, this is the one I’d recommend, largely thanks to its ambient light sensor and incredibly convenient wireless charging.

Why did the Pebble get ditched?  Some part style, some part software. The original Pebble is not a terribly attractive device, especially when compared to something like the Moto 360.  Perhaps more importantly, however, I’ve found a huge amount of utility in Android Wear’s voice commands, particularly when it comes to setting reminders and creating to-do lists.  Also, while the Pebble excels at showing me notifications, but Android Wear – and by extension, the Moto 360 – allows me act on many of those notifications, and I’ve found that makes a huge difference in utility.  The only real benefit to the Pebble is battery life, but I have no problems charging my smartwatch daily, as long as the charging method is convenient and it doesn’t die on my wrist.

 

So what’s next? I honestly don’t know – I’ve reached a surprisingly happy medium with my current line-up, with each device filling an important niche, and no device feeling underused.  The most obvious candidate for replacement is the HTC One, given its age and the fact my contract is up early next year, but right now, I don’t see anything I’d jump to replace it with. The only real candidate is the new Moto X, but even then, I’m not sure it’d be a huge upgrade.  I’m excited to see what comes out next year – especially from HTC – but if nothing strikes me as being better than my HTC One in most or all areas, then I’ll wait it out.

It’s perhaps my dirty little secret that as much as I love technology, I don’t love buying things on a near-constant basis.  It’s that love of technology that drives me to find the ideal devices that fit so seamlessly into my life that I don’t want to replace them, because replacing them could actually make things worse.  People who know me in person will laugh at this, and they’re right to do so, but for the first time in awhile, I’m not itching to buy anything new any time soon – and it feels good.

My 10 Second Review of Grand Theft Auto 5’s First Person Mode

  1. First person mode sounds like a simple thing, but it’s the best thing to happen to GTA in years. Rockstar makes absurdly detailed worlds, and viewing them in first person  gives me a whole new appreciation for them.
  2. Riding motorcycles in first person is seriously the best.
  3. When proper VR hardware is released, and GTA5 has proper VR support, you will never hear from me again.
  4. I am ready for a first person Red Dead game and/or a first person Bully game.

My 10 Second Review of Middle Earth: Shadow of Mordor

8.5/10, would kill Orcs again.

To elaborate:  This review was on my to do list for awhile, but I kept ignoring it because I’d rather have spent that minimal amount of time playing Shadow of Mordor than writing about it.  I’m also glad I played it to the end before writing about it, because Jesus, what a terrible way to end a game. It wasn’t enough to sour the whole experience, but it was close. The fact it doesn’t ruin the whole thing is testament to how great everything else is. Also, it’s probably the best Assassin’s Creed game you’ll play this year.

I can’t wait until the second one, where they take the good ideas and make them even better and blow us away, and their third game when they run the idea into the ground and ruin the franchise for everyone.

 

Why I’m actually kind-of happy the Nexus 6 isn’t amazing

So, unfortunately, it sounds like the Nexus 6 is kind-of a bust. It’s not a terrible phone, but it has little reason to exist unless you desperately want stock Android on a phablet.  Which I thought I did, back when I played with the iPhone 6 Plus, but there just don’t seem to be enough benefits yet to justify the upgrade.

Here’s the funny thing, though – now that I’m back on my HTC One for the foreseeable future, and probably won’t get a Nexus 6, I’m actually super-excited to see what phones we get next year.  For the first time in a awhile, I’m content and willing to wait until the right phone comes along, rather than just jumping onto something for the sake of newness.

The new Assassin’s Creed is another reason to never pre-order a game

Did you happen to pre-ordered the new Assassin’s Creed game?

Oops.  Turns out it’s not very good at all, which is probably why reviews of the game were delayed for until noon today, so people wouldn’t cancel their pre-orders and early adopters would get bitten in the ass.

The only way to fix this is to vote with our wallets, which means:

  1. Stop pre-ordering games.
  2. Stop buying games before review embargoes are lifted.

Chances are, if you have a chance to buy a game before that game is actually out, it’s probably because the publisher is trying to hide something.  Of course, as Giant Bomb’s Patrick Klepek points out, the gaming media also bares some responsibility:

Returning to the original HTC One, a year and a half later

Introduction

Last weekend, my Nexus 5 suffered a tragic screen-related accident.  It still works, but I’m too OCD to use a phone with a broken screen unless I absolutely have to.  Unfortunately, I bought the phone secondhand from a friend of mine, and it was purchased directly from T-Mobile, so I’m not eligible for Google’s unofficial one-broke-screen-replacement policy.  And yes, I did call to try anyway – the nice Google representative forwarded me to the LG representative, who confirmed that, alas, LG’s warranty did not cover a broken screen.

Fortunately, since I’m a hoarder when it comes to tech devices, I still have my “old” HTC One, originally purchased back in April of 2013, and my daily driver until I got the Nexus 5 back in May of this year.  I figured, at the very least, I could use the HTC One until I fixed the Nexus 5 – or used the broken phone as an excuse to upgrade to the Nexus 6.  Now, I’m not sure I want a Nexus 6…or any other phone, for that matter.

Why not just fix the Nexus 5?

I could, but the replacement part is anywhere for $50-80, but the time investment to actually fix it – and that’s assuming the replacement part works as expected.  Repair services in my area are unreasonably expensive, especially given the price of a new Nexus 5.  Also, after using the HTC One for a few days…I honestly just don’t want to.

But isn’t the HTC One ooooold?

Technically, sure.  But day-to-day?  It sure doesn’t feel like it.  It’s running Android 4.4.3, and Sense 6 – HTC’s custom skin – is in some ways just as good, if not better, than stock Android 4.4.3.  I think I still prefer Android 5.0, but as I’ve said, Android 5.0 actually takes a great deal from Sense.  It’s clean and functional enough that swapping the Sense launcher for the Google Now Launcher has scratched most of my stock Android itch – and like the Nexus 5, it supports voice commands with the screen off, as long as it’s plugged in.  It honestly feels just as fast as my Nexus 5 ever did, with the exception of a few dropped frames during certain animations.  Bottom-line: people who say Android is slow are full of shit.  Bad Android phones may be slow, but when you get the right phone on the right software, it soars.  Everything I originally said about the HTC One still stands today, and if anything, the experience is better than it ways back then.

Full disclosure: I am running a custom ROM, something 99% of users will never do.  Specifically, I am running Maximus HD, which I installed a few months ago as a side-project.  Since the HTC One was no longer my daily driver, I felt comfortable messing with it ways that I’d be reluctant to do to before.  That said, I haven’t done any performance tweaks beyond installing the ROM – I am not underclocking or overlocking anything, I’m simply running stock HTC software without AT&T’s horrible bloat.

If the HTC One is so great, why did you even buy a Nexus 5?

There are two answers to this, both equally accurate.  The short answer is that I am easily distracted and like shiny new things.  The more complicated answer is that I wanted an unlocked device, free of any carrier interference with regards to software and update delivery.  I didn’t want any of their unwanted crap on my phone, and ideally I didn’t want to be at all financially tied to a carrier, though obviously I’d still have to finish the two-year contract I renewed when I purchased the HTC One.

In my attempts to escape carrier bloatware with my original Android phone, the HTC One X, I experimented extensively with custom ROMs, and during that time I grew tired of the whole process.  After months of jumping from ROM to ROM, in search of the perfect experience, I just wanted a phone that worked great out of the box – which the HTC One  did provide, albeit at the cost of carrier bloatware and delayed updates.

It turns out I never really needed the Nexus 5, though – I just needed to grow some cojones, dive back into the world of custom ROMs, and free the HTC One from its prison.

So are you ever going back to the Nexus 5?

Honestly?  I don’t really think so, no.  Even if both devices were fully functional, and knowing the One’s flawed, I’d be tempted to stay on the One. There’s just something about it – like my old iPhone 4, it feels like an iconic, timeless device.  I still prefer its design to this year’s HTC One, and I’ll take an optically stabilized camera over a weird depth-based dual-camera gimmick any day of the week.  It really can’t be overstated how great this device still feels in the hand; something I’d forgotten in my months with the understated, nice-in-the-hand-but-kind-of-boring Nexus 5. Build quality and materials is something some people will never care about, but to me, it makes all the difference in the world – it just took using another device for me to realize how important to me it was.

It’s not just the materials and the build quality that makes me prefer the HTC One, though – it’s the little things in the hardware and software that I’ve redicovered.  The lower-in-megapixel-but-infinitely-faster camera.  The wide-angle, better-quality front-facing camera.  The fantastic HTC camera software.  Those still-best-in-class front-facing speakers.  The (in my experience) more reliable Bluetooth connectivity.  The higher-quality, higher pixel density display without any hint of backlight leaking. The fact it has 64 GB of storage, as opposed to the 16 GB of my Nexus 5. The little features of Sense, like the customizable Quick Settings.  The superior lockscreen, complete with shortcuts to my most-used apps and e-mail/text notifications.  HTC’s newfound drive to bring Android updates to flagship phones as quickly as possible.

Special mention should go to the IR blaster, which – combined with the casting ability of various media apps, as well as the Playstation app – allows me to control basically every aspect of my media center with my phone.  None of these alone would be a good reason to prefer the HTC One, but everything together – the complete package – is hard to resist.

I do really miss wireless charging, though, and the ability to use the AirDock in my car.  The side-mounted sleep/wake button was a bit more sane, too.

Should I buy an HTC One?

I feel like you could do a lot worse than to buy a used $200 HTC One, but I’m still not sure I could actively recommend it, if only because, at more than a year and a  half old, it seems likely that Android 5.0 is the last major update it will get.

So what’s next?

I honestly don’t know.  As I alluded to earlier, I originally thought I’d stick with the HTC One until I settled on a new phone, specifically the Nexus 6, but now I’m beginning to question that.  Don’t get me wrong, I will be tempted, and I will certainly walk into an AT&T store to try the Nexus 6, but now I’m leaning towards what I probably should’ve done in the first place – riding out the HTC One as long as it will take me, or at least until something strikes me the same way it did when I first held it a year and a half ago.

Maybe it will be the Nexus 6, or the next HTC flagship, or perhaps something else entirely.  As I said, I am distracted by shiny and new things, and it’s very possible the HTC One is still just “shiny and new” since I haven’t used it for so long.

What does seem likely is that I will no longer shy from messing with my phone, at least if that’s what it takes to tear out the carrier software and ensure more timely updates.  In some ways, after spending just a couple of days with the HTC One I’ve come full-circle to what I originally said about the HTC One X: you can always change a phone’s software, but you can never change a phone’s hardware.

Deprecated Post: 29 Days with the HTC One

My Nexus 5 recently had a freak accident, resulting in a functional unit but a broken screen.  Rather than use a broken smartphone screen (which has always driven my OCD crazy), I decided to bring my old HTC One out of retirement.  I’ll cover my experiences returning to the HTC One in a post later this week (spoiler: it’s a fucking great phone), but for now, I just wanted to revive my original review of the device from a year and a half ago.

The following was originally posted on The Verge’s forums on May 18th, 2013.

INTRODUCTION

A little over a year ago, I migrated from iOS to Android, via the HTC One X. Some time after that, I further reminisced about my experiences with Android, with the tl;dr being:

  1. Tinkering is fun, but at the end of the day, a smartphone is like an appliance – I just want it to work.
  2. Along those lines, I advised my future self to “Just get a Nexus, stupid.”

Well, I never was particularly good at taking my own advice, so here I am to discuss my personal experiences with the HTC One. Here’s thing thing: I didn’t even necessarily want to want a new phone. I’ve never been a “get a new phone every year” kind of guy – I like my phones to last a couple of years, at least. It helps the next phone feel all the better when I finally do upgrade. So, why did I upgrade? Well, this post will explain that, but it boils down to a few key things:

  1. My One X, as much as I loved it, had been frustrating me. I was tired of tinkering with it, and choosing between the camera features I loved and the pure performance of something like Cyanogenmod.
  2. The One won me over, once I realized how well it fits my life.

This isn’t a review, strictly speaking – there are enough reviews out there already…some of them pretty amazing, and other ones pretty terrible. Instead, I want to discuss why I chose the HTC One as the best fit my life, and why you may – or may not – want to do so.

Since this is a long post, I’ll give the tl;dr up-front –

  1. The HTC One gives me the stability, performance, and design excellence I’ve come to expect from an iOS device, but with the added benefits of Android.
  2. The camera isn’t the best in a phone by a long-shot, but it happens to be the best camera for my needs.
  3. The screen and the speakers are just insanely, ridiculously, disgustingly good.

If you still want to stick around for the rest of the ride – let’s get started.

THAT DESIGN

I don’t know what I can add to the discussion about the design of the HTC One that hasn’t been repeated a thousand-fold, but a commenter on Lifehacker gave what I think is the single best description of the look and feel:

It’s like a Retina MacBook Pro gave birth to a smartphone.

This covers both the positive and the negative – the screen, build, design, materials, and performance of both devices are best-in-class. However, if you’re more interested in a device that’s easy to repair, or has a replaceable battery, or expandable storage – best to close this window and move on, since I don’t think you’ll find all that much to like here.

Of course, I was not always a believer. When the leaks first showed up, I said brilliant things like:

I hope this is fake. Home button on the right? No multitasking button? Weird-ass bottom speaker?

This is making my One X roll in its grave and my One X isn’t even dead yet.

Now, I stand by some of this. I believe the home button being on the right and the lack of a multitasking button are still poor choices, but they are poor choices I’ve learned to do deal with, and don’t really bother me in my day-to-day use. I adapted to the new location of the home button within a matter of minutes. Of course, I was terribly, terribly wrong about the speakers…but we’ll get to that later. Overall, I thought the phone looked ridiculous, even after it was announced:

Dear HTC:

You are made of stupid.

Love,

Someone who wants you to succeed but doesn’t understand why you are made of so much stupid

So, yeah, I’m not too proud to admit that I was, in retrospect, mostly wrong. I still think the button layout is poor, and the power/volume keys are a bit too flush for my liking, but honestly, those are the only issues I have with the design. I have owned an iPhone 3G, iPhone 4, and an HTC One X before this…and the One blows them all out of the water when it comes to design and in-hand feel. When I hold the One in one hand, and the One X in the other, the One X feels like a plastic prototype for the One…which, I suppose, is kind-of true.

And here’s the punchline, at least for me:

Design. Matters.

If I’m going to carry, use, and look at something on a daily basis, and I have a choice between a well-designed product, and a par-for-the-course designed product, I will take the well-designed product every time. It’s part of why I used an iPhone for so long, it’s part of why I own a MacBook Air, and it’s part of why I have an iPad Mini.

Now, obviously, I would not buy a product for design alone – but I’d be lying if it wasn’t a major factor in my decisions. If I’m paying a premium for something, I want it to feel like I paid a premium – but perhaps more importantly, I want it to look like someone set down and really thought about the design. As a customer, lazy design actually kind-of offends me – it says to me “We didn’t bother to put much thought into this, because millions of you people are just going to buy it anyway.”

For those who would argue that you’re just going to slap a case on it anyway – I don’t buy thin-and-light smartphones that feel great in the hand, just to shove them in some case that will make them thicker, heavier, and feel worse. I won’t dive too deep into that debate, though, because I think Michael Fisher at PocketNow covered it far better than I ever could.

I totally understand and respect the mentality of those who prefer function and ignore form entirely. There’s a solid case to be made for that approach, and I’m not going to tell those people they’re wrong, because they aren’t. Neither side is wrong – people just have different preferences. Speaking of which…

LET’S TALK ABOUT THAT CAMERA

Some people hate it, some people love it. It’s rare that a smartphone camera is so divisive, and I understand both perspectives. Let me just start by saying this:

I think the camera on the Galaxy S4 is better.

Overall, in good lighting, it takes noticeably better pictures. It’s not that the One is bad; it’s that the S4 is really, really good. Having said that…

I think the camera on the HTC One is better for what I want out of a smartphone camera.

In fact, the camera was a large part of why I did want the phone. My goal for a smartphone camera is to capture a moment, regardless of the circumstances (lighting conditions, motion of the subject, etc.) and quickly share those moments with my friends. In that regard, I think the One’s camera presents some unique advantages in the smartphone world, even if the image quality is not always the best.

Most notably:

  1. Ridiculously fast shutter speed, allowing me to capture pictures that are literally impossible on other cameras.
  2. Reliable pictures in almost any lighting scenario. Daylight pictures aren’t the best – far from it, as they even tend to be overexposed – but the payoff of that means that I can quickly take a picture in medium-to-low lighting and be confident I’ll have a usable image. Perhaps even more importantly, the increased shutter speed I mentioned above means that, unlike most other smartphone cameras, you don’t haveto put the camera in Night Mode to get a usable low-light shot. Even cameras that automatically adjust for night mode like the iPhone 5 and the Lumia 920 do so by keeping the shutter open for longer, thus gathering more light – which is great, unless your subject is in motion. Then you’re basically screwed.
  3. For me, the lower file size of the lower megapixel image is actually a boon. I’m never going to print a smartphone picture – if I want a printable image, I’ll get a big-boy camera – so for my uses, smaller file sizes are ideal. They upload to social networking sites faster, they sync with DropBox quicker, and they take up much less space on my cloud storage drives.
  4. ZOE and Burst Mode are awesome. ZOE is like Burst Mode on steroids, but if I want my old school “hold down the shutter button and get a ton of pictures”, it’s still there.
  5. The wider-angle lens of the camera allows me to capture more of a scene from the same distance away, when compared to other smartphone cameras.

As a real-world example: last night, in a dimly-lit restaurant, my friends wanted to take a picture of a white sign to send to someone. Unfortunately, when flash was used, the text on the white sign became illegible. Fortunately, with Night Mode, I was able to take a clean looking picture with perfectly legible text. While this may not be a common use-case, I think it helps illustrate the adaptability of the camera, which is what makes is so appealing and valuable to me.

Here are some sample images:
My dog in-motion running up stairs (captured with ZOE): 2013-04-30_2018

Fountain, frozen in motion:

Fountain_medium

Palo Verde tree in my back yard at dusk.

2013-05-14_2019

Night Mode photo of my back yard at 10 PM with very, very little ambient light. This was definitely one of those moments where the camera saw way more light than I did.

2013-05-17_2021

Anyway, that’s enough about the camera. Some love it, some hate it – I’m in the former category, and hopefully I’ve explained why.

THOSE SPEAKERS

I find it hard to add something new to the dialog about those amazing front-facing stereo speakers. Yes, they’re front-facing, and yes, they’re amazing – and I found them way more useful than I ever thought I would. I love having a device that’s always with me and capable of producing decent enough sound that I can play music basically anywhere without having to worry about headphones. I’m just not a fan of headphones, if I can avoid it – especially when I’m moving around a room or around the house. I even find myself lowering the volume of the phone to about half-way when I’m close to it, and I can’t think of any other mobile device where that’s been the case.

Beyond that, though, they’re also amazing for being able to share media. I can’t remember the number of times I’ve wanted to show someone a video or play them a song, but the speakers on my phone weren’t able to overpower the ambient noise. That’s no longer a problem anymore. Again, for me, my phone is largely a social experience – so anything that enhances that social experience is a huge boon.

This actually is one area where my One X was getting really frustrating. The volume of both the earpiece and the speaker were inexcusably low, to the point where making phone calls was a miserable experience, and playing any kind of media was essentially impossible. So for me, the speaker upgrade with the One wasn’t just a nice-to-have – it was a necessity. Call quality on the One is the best I’ve ever heard on a mobile phone, and the speaker phone is right up there is well. I took one of those obnoxious phone surveys today on speaker phone, and the voice was crystal clear.

EVERYTHING ELSE

As I mentioned before, I spent more hours than I want to think about tweaking and customizing my One X. In the end, I always found it came down to two choices:

  1. Enjoy the awesome Sense camera software, at the expense of device performance thanks to Sense.
  2. Run an AOSP ROM, at the expense of the Sense camera software, battery life, and general device stability.

I even reached the point where I had two device backups so that I could swap between a Sense ROM and an AOSP ROM, depending on what I needed out of my device that day. In retrospect, it was kind of absurd.

If I was to be completely honest, there were definitely times where I found myself missing the rock-solid stability of iOS. It’s not that I didn’t have fun with the ROMing and the tweaking – I did – but at the end of the day, my phone is something that I need to just work – and the One X wasn’t giving me that anymore. Unfortunately, I’d also grown quite fond of the benefits of Android, and was reluctant to give that up.

Fortunately, the One made my decision much easier. While I regretted having to buy a new phone after only a year, I felt that the One was a device I could use for at least two years without concern – and so far, that appears to be the case. It is as stable and reliable as my iOS devices, while providing me the additional power and flexibility that comes with Android. I would also argue it’s nearly as smooth and lag-free as the iPhone 5’s I’ve used, with the exception of some poorly-optimized (and, unfortunately, high-profile) apps like Facebook and Chrome.

Unlike with my One X, I decided to run completely bone-stock for awhile, so that I could form a truly honest opinion of the phone. So far, I haven’t regretted this decision at all – I haven’t even rooted the phone yet, or installed a custom launcher. I just haven’t felt the need.

Don’t get me wrong, I love stock Android as much as the next geek, and I still kind-of wish HTC would make elements of Sense removable, but even as a stock lover, I have to say…Sense 5 isn’t bad. I might even go so far as to call it good, and I’m not the only one.

I even prefer a few things about Sense to AOSP – most notably the camera and the e-mail apps It also has some nice widgets, though nothing I couldn’t live without. I’ve actually come to kind-of like Blinkfeed when I have a few minutes to kill, but again, it’s nothing I couldn’t live without.

Occasionally, it even feels more cohesive than AOSP – for example, you can swipe left and right through e-mails in the e-mail app, the same way you can in the Gmail app. The last time I tried the AOSP Android mail client, it still didn’t support that, which was mildly infuriating.

Finally, Sense 5 is at least polite enough to try and compliment the Holo theme of AOSP – TouchWiz and Sense 4, on the other hand, look and feel like someone glued Gingerbread to Jellybean.

I just realized I haven’t really mentioned battery life, and I guess that’s because I don’t actually think about it much with this device. It’s better than my One X, and probably about on-bar with my iPhone 4, if not a little better. It lasts me through a day of my normal usage, though like any phone, I’ll top it off in the afternoon if I’m planning to go out that night. I also tend to carry an Anker Astro3 if I planning a long day/night of heavy usage.

Speaking of things I forgot to mention – I have been using the IR blaster feature a surprising amount. It may not be a full-fledged universal remote, but I can turn on my TV and audio system, change the volume, and change input sources, which is pretty much everything I need. Combined with a Roku app, I can control everything I need from my phone, which is kinda awesome.

THE FUTURE

I’m not going to pretend that HTC and AT&T have a great, or even a good, history of keeping their phones up to date. However, for once, that actually doesn’t bother me. Android 4.1 and 4.2 are already really, really good, and now that Google has shown they can make substantial updates to Android without a major version change (as I sort-of predicted would happen), I’m fairly confident I’ll be satisfied for the next two years.

The phone and the software are already pretty great, so even if it never got an update going forward, I’d live – and this might be the first phone I’ve ever felt that way about. When I was using an iPhone and later the One X, I always felt like something was missing – things I tried to compensate for by jailbreaking, rooting, and eventually ROMing. The One has finally given me what I feel is a no-compromise experience smartphone experience.

And, for me, that’s priceless.

Not quite Fit for consumption: Google Fit impressions

When I shared my experiences with the Moto 360 and RunKeeper, my biggest frustration was that the valuable fitness data that was being collected by the device wasn’t actually going anywhere, and instead lived only on the device itself in the form of a card that gave me my daily step totals, and a notification that I’d hit my daily heart rate goal.   At the time, I figured Google Fit was the solution to this data-siloing.  Fortunately, it appears I was correct – Google Fit can, in fact, download data from my Moto 360.  Unfortunately, it doesn’t appear to do much else of value.

So what is Google Fit?  That’s…actually a frustratingly difficult question to answer. Ideally, it’s supposed to be a silo for all your fitness data – so the data gathered by my Moto 360 and RunKeeper could live in the same place as data gathered by my FitBit and Withings scale, all of that coming together in a glorious data-gasm that would, in theory, paint a fairly accurate picture of my personal activity.  Looking at their announcement, they claim:

You can also connect your favorite fitness devices and apps like Strava, Withings, Runtastic, Runkeeper and Noom Coach to Google Fit and we’ll surface all of the relevant data in one spot, giving you a clear and complete view of your fitness. No need to check one app to see your weight and another to review a run – with Google Fit, that data will all be surfaced in one, simple place.

Great, awesome, let’s do this thing.  What services are currently available?

Screenshot 2014-10-30 13.41.47

Oh, good, a list of Fit-friendly apps.  Let me just click on that link, and…

Screenshot 2014-10-30 13.43.52

…what the fuck?  When I first saw this, I ignored it as launch day hiccup, but as I sit writing this two days later, all I can think is…what the fuck?  I imagine no Google Fit-compatible apps are available just yet, but there’s still no reason to link to a dead page.  That shit is amateur hour.

So, unfortunately, at this point, all Google Fit really seems to do is gather data from my 360 and sync it to the web.  Poorly.

So close, but so far.  Wait, not close at all.

Yesterday: So close, but so far. Wait, nope, not close at all.

Today: Better, but still pretty terrible.

Today: Better, but still pretty terrible for a modern web service.

Perhaps I’m coming across as overly harsh here, but it’s important to remember that this isn’t a start-up company with their first fitness product, this is Google, and web services are kind of their whole thing.  There’s absolutely no reason for my phone app and the website to be so outrageously out of sync.

The good news: my Nexus 5 and Moto 360 get along great.  The Steps card has been replaced with more health info, as seen here:

2014-10-30 13.30.10
2014-10-30 13.30.23 2014-10-30 13.30.34 2014-10-30 13.31.00 2014-10-30 18.42.12

 

Nothing to complain about here, and as I’ve mentioned before, I continue to be impressed by the fact that the Moto 360 (and thus Google Fit) can track bike rides and runs, something my FitBit can only do if I wear it at the bottom of my bike shorts, near the knee.  I believe it’s forward-motion based, however, which means it doesn’t work on my stationary bike, and I’ve heard reports of people driving incredibly slow in traffic and having Google Fit log that as cycling minutes. Whoops.

Unfortunately, that’s about where the positive section ends.  I mentioned running and bike rides…and those are two of the three activities Google Fit can track, the third being walking.  That’s it – even if you add an activity manually:

Screenshot 2014-10-30 18.12.45

Yup, that’s all anyone ever does! No other type of workout is possible.

It probably goes without saying at this point, but by-far the biggest problem with Google Fit is that it just doesn’t do anything of value.  It asks for my height and weight, but doesn’t give me any sort of calorie burn.  It lets me manually enter activities, but I better hope I didn’t go hiking or swimming.  I can view charts, but those charts provide me very little of value:

Screenshot 2014-10-30 18.16.26

What value does that data have?  Why does this chart even exist?

Compare it to the charts I get from FitBit’s website:

Holy shit! Useful data!

Holy shit! Useful data! Literally every one of these is more useful than what Google Fit tried to stuff into their single graph.

The only thing I can think of is that this was rushed out the door to go along with the Android 5.0 release, but there’s still no excuse for such a low-quality, barebones product from a company like Google.  The fact that none of the partner apps are even ready just underscores the lack of care and polish in this release.

It’s not that Google hasn’t stumbled before, but usually they at least bring something new and exciting to the table.  Android Wear is still basically beta software, but it also does things other wearable software doesn’t, and it has so much potential.  Meanwhile, Google Fit, at least inn its current form, seems to exist just for the sake of existing, and that’s not enough in a world with Apple HealthKit and, more recently, Microsoft Health.  Health, in particular, seems to basically be everything Google Fit should be, but somehow isn’t:

Microsoft Health is a cloud-based service that helps you live healthier by providing actionable insights based on data gathered from the fitness devices and apps that you use every day. Activity-tracking devices like the new Microsoft Band, smart watches, and mobile phones plus services like RunKeeper or MyFitnessPal connect easily to Microsoft Health. Using this fitness data and our Intelligence Engine in the cloud, Microsoft Health provides valuable, personal insights so you can reach your fitness goals.

Microsoft Health is designed to work with you, no matter what phone you have, device you wear, or service you use. The power of the cloud platform lies in its ability to combine the data from all the devices and services you use to give you a more holistic and insightful picture of your fitness.

Google Fit’s only real use for me is that it interfaces with Android Wear, and now, it looks like Microsoft Health might do that, too.  There’s absolutely no reason that Google Fit couldn’t have been this, but Microsoft has beaten them to the punch in a dramatic way.

know Google can do better than this, and that’s perhaps why this frustrates me so much.  It’s not that they did their best, strived for something new and exciting, and then failed – that, at least, would have been an admirable failure.  Instead, Google has done something I’ve never seen them do – release a product with almost no potential value to my life, and while I acknowledge that it will almost certainly get better in the next year, as they add more functionality and more partner apps come onboard, that’s no excuse for releasing it in the state it’s in today.

Apple approves and features “calculator” widget, then changes their mind

From six colors:

First there’s the maddening inconsistency: This is an app that was accepted into the App Store, and is even being featured in the App Store as I write this. And now, a few weeks in, someone at Apple has decided that the app is too… what? Too useful?

And the icing on the cake:

I just don’t understand this behavior from Apple, though maybe I’m just overly sensitive to it as a programmer myself. Don’t they realize a large reason for the success of the iPhone is the fantastic third-party developers who make their platform what it is? Either allow things or reject them, but don’t open your doors, welcome someone in, then slam those doors behind them and set the room on fire.

Update: Apple has clarified their position on Calculator Widgets, and it looks like PCalc can stay!

« Older posts Newer posts »

Copyright © 2024 writing about tech

Theme by Anders NorenUp ↑