writing about tech

Tag: iphone 6 plus

Daily Drivers Update, January 2015

Another year, another daily driver update. This is a big one (no pun intended) – my move from using an Android phone for almost three years, back to using an iPhone.

Phone

Old and Busted: HTC One (M7)

New Hotness: iPhone 6 Plus

The iOS vs. Android debate is a never ending quagmire that I don’t really want to venture into here, suffice it to say that in January of 2015, I decided to try using an iPhone again, and it turns out I really liked it. There’s a variety of reasons, but really, at the end of the day, it came down to battery life and camera performance. This is a fantastic phone, if you can put up with iOS and the somewhat-absurd size.

 

iPhone 6 Plus Conclusions: Battery, battery, battery. Also camera.

Two weeks ago, I purchased an iPhone 6 Plus, largely due to my issues with battery life on Android phones.  If you’ve been following my posts,  you’ve probably figured out that I’ve decided to keep the iPhone and stick with iOS for awhile. I wish I could say I had some grand, all-consuming revelation, but really, it comes down to the same reason I decided to try an iPhone again in the first place: battery life.

My rule for the last two weeks was a simple one: if I was going to keep the iPhone, it had to last all day, every day, only being plugged in at night when I get to bed.  Day two (New Year’s Eve) was actually a close call – it came off the charger early for work, and was used heavily throughout the day to coordinate my NYE party, stream music, etc. It scraped by with 10% left when I finally went to bed at 2 AM.

Since that day, though, I’ve come nowhere close to hitting that 10% mark. Sitting at home right now, after work, 11 or so hours after my phone came off the charger, my phone is at about 70% percent. When I go to bed, I will likely have more than 50% remaining – probably closer to 60%, actually. That means I could have used my phone way, way, way more, and still had battery to spare.  One morning, I went running for two and a half hours, with RunKeeper tracking in the background the whole time, streaming podcasts to my Bluetooth headphones, and still had 88% battery left.

These numbers are about average from what I’ve seen in my two weeks of usage.  They are also quite possibly irrelevant to you, as we likely live in different places, work in different places, and use our phones very differently.  It’s an apples-to-oranges comparison to anything except my own previous experiences with phones – and in that regard, I can say it’s exceptional. I rarely play games or stream video, but I also don’t baby it – I simply use it when I need it. You know, like a tool should be used.

The key to this is standby time: when the phone’s screen is off, it is actually asleep, unless I’m intentionally doing something in the background, or it’s running one of the apps I’ve decided I want running in the background. It’s a bit of a revelation to use a phone whose battery life I don’t have to worry about, at all – in that regard, it’s more like having an iPad Nano than an iPhone. The iPad is a device I use every day without concern for the battery – and my phone now falls squarely in that same category. Until recently, I never would have thought that possible.

I’m not going to pretend there aren’t Android phones which, under the right conditions, would provide me the same results – I’m sure those Android phones exist. The problem is deeper than that: after owning three Android phones, and an Android tablet, I simply don’t trust Android to manage my phone’s battery life anymore.  Given how I use my devices, I fear that buying an Android phone with a bigger battery would just be a bandaid over the larger problem of Android’s battery management. As long as a background app or process has the ability to wake my device and keep it awake, I will always have reason to doubt my phone’s reliability – and at this point,  that’s an unacceptable scenario.  I don’t own technology to babysit it; I own technology to use it.

Reliability is really what the iPhone 6 Plus is all about. It’s a boring answer, but for many of us, it’s also the only answer that matters. Vlad Savov explained why the iPhone’s camera is still the camera to beat better than I ever could, but it boils down to this: I can take my phone out, snap a random photo, and, 99% of the time, get reliable, in-focus results.  I don’t even get that kind of reliability from my point-and-shoot, the fantastic Sony RX100M2.  Obviously the image quality and shooting capabilities of the Sony camera are still far superior, and the camera still comes along to more important events, but I no longer feel the need to dual-wield a phone and a point and shoot on a day-to-day basis.  On my Android phones, and to a lesser extent on my point-and-shoot, I rely on burst mode shots to make sure at least one will be in focus. I haven’t felt the need to do that with the iPhone; I only use burst mode for capturing motion or trying to get a very specific moment in time. I can hold the iPhone in one shaky hand, take a single photo, and, almost every time, it still comes through completely focused. I took a little video to demonstrate:

Photos from the sample video:

2015-01-13 20.35.22 2015-01-13 20.35.23 2015-01-13 20.35.24 2015-01-13 20.35.25 2015-01-13 20.35.27

It’s frustrating because no Android OEM has managed to replicate whatever software algorithms Apple has – there’s certainly nothing special about the hardware optics, so it has to be done in the software. I imagine it’s quickly taking a bunch of photos when you hit the shutter key and either using that data to piece together an in-focus shot, or choosing the most in-focus of the ones it took, or some combination of those techniques. I honestly thought the iPhone’s camera abilities were exaggerated until I started using one again – but now, I am a believer, and it will be hard to settle for anything less.

It feels like a shame to talk about the iPhone 6 Plus without at least mentioning TouchID. I’d had some experience with it on the iPad Air, so I mostly knew what to expect, and I can’t really add much to what others have said.  Personally, it’s hard to imagine going back to a phone that doesn’t allow me to secure my device in such a way – I put my thumb on the home button, push it down to wake up the device, and it unlocks almost instantly:

2015-01-13 21.17.04 (1)

Trusted Devices on Android is good, but TouchID is fantastic, especially now that third-party apps can leverage it. Paying for apps in the App Store, logging into the Amazon app, opening the Mint and Alarm.com app, paying for stuff at NFC terminals – all secured with TouchID.  Speaking of payment – Apple Pay is probably worth its own post at some point, but man, it is good. I used Google Wallet in the past, but Apple Pay definitely has the advantage when it comes to implementation. I simply point the top of my phone at an NFC terminal, an image of my credit card appears, I put my thumb on the TouchID sensor, and it’s done. This is the future, folks – and it’s kind-of neat.

So, does all of this mean I’m “switching” to iOS? Technically, yes, I guess, but I don’t really like the term “switching”, or the connotations that come with it. I’ve opted to use an iPhone as my daily driver for the foreseeable future simply because, at this moment in time, it’s the best device for my needs. A few years ago, Apple and I diverged – their phones weren’t big enough and the OS wasn’t flexible or interesting enough. Today, enough has changed that using an iPhone again just makes sense for me. I no longer feel like I’m making a major compromise when it comes to software or hardware, and the benefits – incredibly reliable all-day battery life and a best-in-class camera – are impossible to ignore.

I hope this isn’t a permanent change. I enjoy having a foot in the iOS world and the Android world, as I feel it forces me to broaden my perspective, both as a tech enthusiast, and with regards to the services I choose to use. Eventually, I hope to see an Android device released that, like the HTC One X before it, offers enough of an advantage over the iPhone that I can’t resist it.

Today, I am an iPhone user again. Tomorrow? I don’t know what I’ll be, but I can’t wait to find out – and that’s why I find the tech world such an exciting place.

The iPhone 6 Plus Experiment: The First Three Days

The following are random thoughts and musings from my first three days of owning an iPhone 6 Plus.

  • Holy Hell, this is thing is big.
  • I’m still torn on the size. For some things, it’s great. For others, it can be frustrating. Most of my smartphone use is generally two-handed, so the lack of one-handed usability isn’t really a big deal, but the weight balance of the phone seems a bit off, so it feels unstable at times even when used with two hands.  If battery life wasn’t a concern, I might actually go with the standard iPhone 6. Of course, after moving from the 3.5-inch iPhone 4 to the 4.7-inch HTC One X, I remember the iPhone felt like a toy.  Similarly, I may not be able to go back to a smaller phone once I’m used to the 6 Plus.
  • Unfortunately, Apple made the same mistake HTC did this year – it made a big, somewhat-slippery phone. Big is fine; slippery is not. It’s not as slippery as I’d been lead to read in reviews, but it’s also not quite as grippy as other phones I’ve used.
  • I generally hate cases, but this time gave in and bought Apple’s official leather case…and promptly took it off again a couple of hours later. It’ll probably going back to Best Buy. It’s fine if you want a case, I guess, and it felt nice enough in the hand, but I very much like the design of the 6 Plus, and dislike covering that up.  It also made the power button annoyingly un-responsive. I might try a clear case but, despite the obvious danger, I prefer carrying my phones case-less.  All of the cases for the 6 Plus will also inevitably ruin the feel of the curved glass on the sides, as well as make edge-gestures less responsive.
  • As I said: I love the design of the iPhone 6 and 6 Plus…as long as you don’t look at those lines on the back. Ick. Also, while I appreciate the desire to have the device lay flat on a table, I miss the in-hand feel of a device with a curved back.
  • Because of the pseudo-tablet nature of the device, I find myself using it in landscape more frequently than other phones I’ve used in the past, especially since Apple’s apps have been optimized to use the bigger screen more effectively. Unfortunately, while the home screen displays in landscape, the lock screen does not. This seems like a silly oversight on Apple’s part.
  • The camera is so, so, so good, you guys. It may not take the best possible image in every possible scenario, but the overall reliability is exceptional. I don’t think I’ve taken a single blurry photo with the thing, nor have I taken a shot with poor white balance. It’s also really great to use an iPhone with burst-mode.
  • Android has definitely taken strides towards being a more fluid experience, but Android on top-of-the-line hardware still doesn’t compare to iOS on top-of-the-line hardware. It is difficult to beat the user experience you get when a company is fully in control of a device’s hardware and software. It’s absurd that a device like the Nexus 6 still has performance problems. Yes, this is likely due to the fact that Lollipop is encrypted by default – but if that’s the case, it’s Google’s job to make sure the UX doesn’t suffer.
  • Battery life is very, very solid – I think this the first time I’ve gone to bed with my phone having more than 50% remaining. I still charge it every night, because I’m anal like that, but it’s refreshing to know that I don’t have to.  Still, you certainly can kill it if you try – I haven’t yet, but I came close my first night, since it was off the charger at 9 AM and I didn’t go to bed until around 2 AM.   So far, it seems as though it will meet my needs when it comes to having a phone that won’t die before the end of the day regardless of what I do with it; in that area, it’s feels closer to an iPad than a smartphone.
  • This is the first smartphone I’ve ever had where I don’t bother to recharging after using RunKeeper or in-car navigation.  Of course, I also don’t typically spend my day playing graphically intensive games or watching hours of video – those activities will kill any smartphone pretty quickly, and that’s where tablets shine over phones.
  • I miss Android’s battery graph. The usage-breakdown-by-app is helpful, but not nearly as helpful as seeing what particular locations/activities/etc. drain my battery more than others.
  • Part of me wonders how battery life would be on a similarly-sized Android phone; benchmarks put the Note 4 and 6 Plus at roughly the same levels of battery performance, but I’ve yet to use an Android device (phone or tablet) that didn’t experience much greater levels of battery drain while on standby. It’s really all about that standby time; 1-2% idle drain per hour, rather than 5% or more. It seems like a small difference, but it adds up throughout the day. So far I haven’t had to turn anything off on the phone, either – for example, Google Now seems to have retained almost all of its location-centric functionality without the battery drain often seen on Android.
  • iOS8 has solved most of the issues I had with iOS, with the glaring exception of setting default apps. With the Today view, I don’t even miss widgets on the home screen – the notification pull-down is debatably a more logical place for them, since you can get to them anywhere.  The Today screen feels like a more powerful version of DashClock, which is one of the only widgets I used anyway.
  • Notifications on iOS are in many ways almost on-par with Android at this point, especially with the addition of notification actions, some of which are actually more useful than their Android counterparts.  For example, I’m more likely to want to mark an e-mail as read than delete it. Some things – like replying to an SMS or iMessage directly from the notification – are actually implemented better on iOS.  Unfortunately, some third-party apps – most notably Google’s – still haven’t implemented these features. Why can’t I mark a message as “Done” from an Inbox notification?  It’s not like Inbox is an older app with legacy code to worry about.
  • I also prefer the way Android 4.4 and earlier displays notifications in the status bar without intruding on screen real-estate, but unfortunately, with heads-up notifications in Android 5.0, this behavior is now essentially identical between the two platforms.  That, combined with the lockscreen notifications of Lollipop, means that, notification-wise, the two platforms are more indistinguishable than they’ve ever been. I miss the status bar icons from Android, but badge counts on app icons serve a similar purpose for me.
  • The Settings screen is insane at this point, and really needs a search option.
  • Touch ID is as great as I expected. I hate passcodes on phones to the point where I’d typically leave my phone unsecured, but Touch ID is the perfect compromise. It makes going without Android’s Trusted Devices feature much easier, and is arguably even more secure.
  • My FitBit’s background sync disconnects my headphones the same way it did on my HTC One running KitKat. Apparently this is a known issue; it’s a shame FitBit doesn’t seem interested in resolving it.
  • On the subject of bluetooth issues: once in awhile, the volume of music and podcasts on my car stereo randomly dips for a couple of seconds. This is something I remember happening on my old iPhone 4, as well as occasionally on my Android phones, but it seems more noticeable with the 6 Plus.
  • I forgot how well-integrated media playback is in iOS. iOS does a much better job of remembering what audio app I was using last (PocketCasts or Play Music, for example) and resuming that app when I hit play/pause on my headphones or Pebble.
  • I still really miss my Moto 360…
  • …but that being said, I’m using a Pebble again and the software’s gotten quite a bit better since the last time I used it. It also seems to work perfectly well with the iPhone. Just being able to dismiss notifications from my watch is a pretty nice change, and makes me miss the Moto 360 a little less.
  • I like than I can activate Siri for my Bluetooth headphones with a long-press; on Android, this would, for some absurd reason, launch the voice dialer rather than Google Now, even on Android 5.0. It’s not quite as convenient as voice commands on the Moto 360, but it’s a decent replacement for a quick note or reminder…
  • …speaking of which, I have yet to find a way of replacing my previous habit of adding items to Wunderlist using voice commands. This is one specific area where I expected my workflow to suffer, so I’m not particularly surprised to see it, but it’s still an adjustment.
  • People sometimes cite iTunes as a reason to avoid using iOS, but I still haven’t had any use for it. Podcasts are managed and sync’d by PocketCasts, while my music still lives happily in Google Play Music, and iCloud backups are handled automatically.
  • I miss being able to download apps from my desktop browser, though. Apple desperately need a web-based app store.
  • I also miss Muzei, my old live wallpaper that would randomly select a new background from my Flickr photos every hour.
  • As an iPad and MacBook owner, I loved the theory of Apple’s Hand-off and Continuity features, but actually using them was still a minor revelation. While I was able to replicate much of the same functionality via third-party apps and services on Android, there’s something reassuring about having it work natively. I was also reminded just how many of my friends use iMessage when I watched 90% of my text conversations turn blue – highlighting one of those few major iOS features that Android has been unable to match, even three years after its introduction.
  • iMessage seems far more reliable than I remember it being during its initial introduction, and there are definite benefits to being seamlessly integrated into the same chat experience that most of my friends are using – especially when you’re a social planner like I am.
  • The ability to make calls and send texts from my iPad means that, at home and at work at least, it is now able to serve as a complete surrogate for my phone. My dream of my smartphone becoming a dumb data/text/phone router while at home is almost a reality – the only missing piece of the puzzle is the notification mirroring functionality I’d grown to enjoy with PushBullet.
  • When out and about, the ability to start a mobile hotspot for my iPad or MacBook without having to even touch the phone is one of those small touches that it’s hard to go without once you’ve experienced it.
  • Speaking of Apple services: why does iOS still blow Android away when it comes to full-device backups?  I can plug my iPhone in every night and confidently know everything I care about (including text message history) will be backed up and available on another device.  This is still a fantasy on Android, which is especially absurd when you consider that cloud services is what Google does.

So far, I’m surprised how little I miss about Android – but I also know I’m only three days in, and this could quickly change as little annoyances add up. I’m impressed by the strides Apple has taken with iOS, though – they continue to take the right inspiration from Android, while implementing those ideas in such a way that it’s much less likely for a rogue third-party app to negatively impact my experience.  While it is certainly still a walled garden, it is a much prettier walled garden, and when it comes to the computing device I use most on a daily basis, I’ve become more willing accept some minor limitations in exchange for reliability.

Of course, what really matters is long-term reliability – proving to be “reliable” over the course of three days isn’t particularly impressive. I’ll certainly report back if anything changes in this (or any other) regard.

The iPhone 6 Plus Experiment

Oh God what have I done

Oh God what have I done

As many of you probably know, I’ve used Android phones for almost three years now – my last iPhone was the fantastic iPhone 4 – but I’ve recently grown frustrated with inconsistent behavior and performance of Android. Battery life has always been a problem, and it recently grew to a head, but it’s not the only problem I’ve had with Android.  Media controls and integration continue to be a struggle for Android. Third-party app performance is less than ideal.  New apps and services still typically come to iOS first, despite Android’s significant marketshare advantage.  Apple’s ecosystem remains untouchable; if you want an accessory or service for your device, it’s almost certainly available.  The Apple Store remains the gold standard for customer service on consumer electronics, and nothing from any Android OEM has come close.

Personally, I don’t have a strong preference for either platform; I like and appreciate each one for what it is. I’m not a fan of companies, but of devices – specifically, devices that seamlessly fit into our lives.  My chief problem with iOS has always been that it expects the user to fit their workflow to match how Apple wants you to do things; my chief problem with Android has always been that it often demands a fair amount of micromanagement on the user’s part if you want an ideal experience. For me, it comes down to that core struggle: user experience vs. personal workflow.

After a couple weeks of toying with the idea of getting an iPhone 6 Plus, and after being incredibly impressed by the iPad Air 2 I got about a month ago, I finally decided it was worth revisiting the possibility of using an iPhone as a daily driver.  So, at lunch yesterday, I gave into a whim, and here I am, less than a day into owning a new iPhone 6 Plus.

The question that I can’t answer without actually using an iPhone again full time is whether or not I can live with iOS’ limitations on my primary mobile device. It’s one thing when it’s a secondary device used primarily for leisure and content consumption; it’s another when it’s the device that drives my day to day activities.  I’ve become accustomed to adapting a device to my workflow; can I return to adapting my workflow to a device

So, here we go – a two-week experiment with an iPhone 6 Plus.  Here’s what I’m anticipating, both positive and negative:

What I’m looking forward to

Touch ID

I have Touch ID on my iPad Air, and it’s pretty amazing. It’s been more than a year since this feature was initially introduced with the 5S, and no competing phone has been able to match the simplicity and accuracy of Apple’s implementation.

Battery life

Given my rant yesterday, this probably isn’t a surprise, but it’s still worth mentioning.  Standby times on iOS devices tends to be solid, and I’m expecting no less from my 6 Plus.  I’m also not holding anything back – it’s configured more-or-less the same way my Android phone was, at least within the limitations of iOS.  PocketCasts and Play Music are set to automatically download.  FitBit and weather apps are syncing in the background. Notifications are being pushed to my Pebble. Google Now is…Google Nowing.  Like with my Android phones, I have no intention of babying this thing to save battery life. It will meet my demands or I will (eventually) find a device that will.  Battery life is something I’ve always compromised on – I’m the guy who always has his phone plugged in at work – and I’m tired of making that compromise. Assuming I’m not spending all day playing games or streaming my video, my phone should last me all day. Period.

A pure experience

iPhones are still the best example for how to release a phone without any carrier interference. While you do have to deal with Apple’s “bloatware” (its usefulness likely dependent on how deep you want to go into Apple’s ecosystem), at least the carriers can’t touch the hardware or software. Android is getting better in this regard, but you still generally have to buy a phone unlocked if you want a carrier-free experience – even the Nexus 6, if purchased through AT&T, gets their logo stuck on the back. Of course, as we learned from the iOS 8.0.1, the downside to a lack of carrier intervention in the update process is that it can lead to a glitchy software update rolling out to thousands of phones – but that remains the exception, rather than the rule.

One of the best mobile phone cameras, ever

I currently use a Sony RX100M2 as my primary camera, but the iPhone 6 Plus’ camera is a breath of fresh air after coming from an HTC One (which is great in some ways and flawed in others) and a Nexus 5. It’s not that those cameras are objectively terrible, but what they are is not reliable. I’m excited to use a phone with a fast camera that’s quite good in most conditions – it may mean my point and shoot can get left at home a bit more often.

Apps, apps, apps

I’ve greatly enjoyed the quality of apps I’ve seen on the iPad Air, and I’m excited to see that quality brought to my mobile handset.  My daily go-to apps like RunKeeper and MyFitnessPal seem to be better designed and perform better than their Android counterparts.  Even Chrome seems to run a bit better on iOS, likely due to the fact that it has to share the Safari browser engine, essentially becoming a fancy Google-centric Safari wrapper. Given Chrome’s performance on OS X, sometimes I wish the OS X version was also just a fancy Safari wrapper.

Apple’s ecosystem

Although I’ve already put a good deal of effort into making third-parties work together in Android to deliver functionality similar to Continuity, there’s something reassuring when it’s a native solution as opposed to a hacked-together solution dependent on multiple third-party apps (in my case, PushBullet and MySMS).  As an iPad and MacBook owner, I’m already excited to be sending texts from those devices using the native messaging app on each.

Reliable Bluetooth audio controls

Now we’ve reaching the nitty gritty, but I’ve found that one of the more frustrating aspects of Android in my day-to-day usage is that the Bluetooth controls on my go-to set of headphones simply aren’t very reliable. It’s been this way on ever Android device I’ve used in the last couple of years – the Nexus 5, the Nexus 7, and the HTC One.  All of them have varying degrees of problems (the Nexus 7 would typically drop connection entirely after a couple of minutes), the most common being that the phone would take commands from the Bluetooth headphones as suggestions. Pause? I guess, when I get around to it. Go back? Eh, maybe. We’ll see. As someone who often uses headphones for hours a day, between running and working, this adds up to a pretty frustrating experience. I had reached the point where I was using my headphones on my iPad more frequently than my phone, just because I knew the damn things would work right.  For the record, I don’t think this is a problem with the headphones, either.  My Moto 360’s Bluetooth audio controls are often fairly delayed as well.  As a bonus, iOS also displays a battery meter for the connected headphones – something Android can’t do, regardless of you root and ROM it.

A cooler phone

This one…probably sounds weird.  I don’t mean cooler as in hipper – I mean, literally, cooler. I’ve yet to have an Android device (phone or tablet) that didn’t run hot while under load including, occasionally, while it was just sitting in my pocket. I’m hopeful that Apple’s marriage of software to hardware will better handle thermal issues.

The size

I’m excited to try a bigger phone, with all the benefits it can bring. I’m also worried it’s simply too big, however.

 

What I’ll miss

Complete freedom

This is the obvious and predicable choice, but it doesn’t make any less true. Everything positive I’ve ever said about Android remains true, and while iOS8 has made strides towards being more open with the additions of Extensions and Today Widgets, it still doesn’t adapt to my personal workflow the same way Android does.  Whether or not I can put up with doing things the “iPhone way” will largely determine how this experiment plays out.

Android Wear

This is actually a big one.  Despite recent frustrations, I still love my Moto 360, and not being able to use it is a huge, huge hurdle on my potential move back to iOS. I still have an old Pebble, which is…fine, I suppose, but I already miss Android Wear. There’s always a chance Android Wear could work with iOS, at least on the same level as Pebble, but today, that’s simply not a reality.

Default Apps

This is another tough one. While Google has done a commendable job of ensuring its own apps work together inside iOS, there’s still a lot more than can be done. I should be able to ask Siri for directions and have her open Google Maps. I should be able to ask Siri to take a note and have it go into whatever app is able to handle that communication. This is something I use all the time with Android Wear, and not being able to create to-do items in my to-do app of choice is going to be a frustrating hurdle.

Google Now

I’m a huge Google Now user and lover, and I’m going to try using Google Now on the iPhone, but I’m concerned about how well it will perform when it’s not an integral part of the OS. Of course, this could go both ways: perhaps I can get most of the benefits of Google Now within the app restrictions of iOS, thus giving me much of the functionality without the battery life hit. It will be interesting to see how this one plays out.

An IR Blaster

This is specific to my uses, but I had my HTC One setup as a universal remote for my TV and audio system. Obviously this isn’t a deal breaker – I can go back to using my regular remotes, like a peasant – but it was a really, really nice feature.

Wireless Charging

My current phone didn’t have this, but the Nexus 5 did, and it’s a convenience you find it difficult to give up once you’re used to.  At least Apple’s Lightning cables are a step above Micro USB in user-friendliness, though.

The size

Hardware-wise, I still think the HTC One was, like the iPhone 4, close to perfect.  It feels right in your hand, and the size is pretty ideal.  While I’m excited to try a larger phone for the first time, I already miss some aspects of the One’s form factor.

 

So, those are my expectations going into this experiment. As I said at the beginning, I haven’t used an iPhone on a regular basis in almost three years, so I’m excited to see the ways the platform has changed and grown. Even if I don’t end up keeping the 6 Plus, at least I’ll come away with a better understanding of what the platform is capable of.

PSA: If you downloaded iOS 8.0.1, here’s a fix for your issues

In case you haven’t heard, you probably shouldn’t have download iOS 8.0.1.  Fortunately, it’s already been taken down, so you can’t download it now on accident – but if you already downloaded it, The Verge has a great guide to fixing your issues:

Apple’s already said it’s investigating the issue, but if you’re one of the unlucky souls who downloaded and installed it, there’s a simple trick (via iMore) for getting your phone back up and running, without wiping anything.

Unfortunately, it requires iTunes, but you gotta do watcha gotta do.

I’m starting to understand why Google rolls out updates to their Nexus phones over the course of a few days, that way, any major issues like this are immediately discovered and the damage is contained.

You know, as opposed to potentially breaking 10 million phones.

Are small smartphones dead?

After today, all indications are that the 4.7-inch iPhone 6 and 5.5-inch iPhone 6 Plus are both going to be record-selling smartphones, which leaves us with an important question:

Are the days of the small smartphone dead?

Previously, friends of mine who wanted a smaller smartphone would typically go with the iPhone or the Moto X, regardless of whether or not they preferred iOS or Android.  They were, if nothing else, reliable and perfect for one-handed use for most people.  I only own a Nexus 5 because my friend sold it to me, saying she couldn’t stand the size and, despite having few issues with Android itself, opted to replace it with a 5S.  Unfortunately for her and others like her, the flagship iPhones are now 4.7 and 5.5 inches, Moto X is 5.2 inches and even its cheaper cousin, the Moto G, is 5 inches. Obviously, customers have spoken, and the majority prefer larger phones – according to Android Central, Motorola specifically cited this as their reason for bumping the Moto X up a full .5 inches in size:

We can grumble about that all we want (and we will), but Motorola says it has data showing that 75 percent of folks upgrading phones wanted to go with something bigger. So, Motorola went bigger, too.

For many, screens much greater than 4 inches are far from ideal for a variety of reasons – the 4.7-inch Moto X was about as large as a phone could get while still being considered a “one-handed” phone.  Despite the fact that, on paper, the Moto X and the iPhone 6 are 4.7 inches, the small bezel size of the Moto X means it’s noticeably smaller than the iPhone 6  – you can see a great comparison of that here.

So, the iPhone is no longer the go-to device when friends ask me what small phone they should buy.  On the Android side, the only small smartphones are either lower-end or phones that don’t seem to get US releases, like the Xperia Z Compact series.  Honestly, I don’t know what to tell those friends anymore, except maybe to get the 5S which, despite being a year old, and is still a great phone.

At this point, the only real hope is that Android OEMs will release flagships along the lines of the Xperia Z Compact, in order to fill the niche being abandoned by Apple – which seems unlikely – or that, next year, there will be enough consumer feedback that we’ll see 4-inch, 4.7-inch, and 5-5inch versions of the iPhone 6S.

What do you all think?  Am I missing an obvious choice, or has it now become substantially more difficult to find a small flagship smartphone to recommend to others?  Do people who prefer small smartphones just have to adapt to a smartphone landscape that’s no longer interested in serving their needs?

Apple Watch, Apple Pay, iPhone 6 Announcement Thoughtstream

  • Cool work with that livestream, Apple.  Love the way it keeps cutting off.  Hope you aren’t going to brag too much about your cloud services today…
  • Whelp, guess I’m reading live blogs instead. Way less exciting this way. Way to ruin the mood out of the gate, Apple.
  • Holy shit this is the fastest event ever. They must have a lot to talk about.  I bet this would be way more exciting with a functional live stream.
  • iPhone 6 and iPhone 6 Plus.  Look just like the leaks.  I would’ve gone with iPhone 6 Pro, but eh.
  • “Retina HD” is one way to name something, I guess.
  • 1080p resolution for the 5 inch – interesting.  That’s lower than the guesses made by Gruber.
  • The live stream is working!  And now there’s a Chinese translation over it, because reasons.
  • Okay, that “Reachability” feature looks like something out of Samsung’s playbook.  Or even something Samsung would’ve rejected.  Gross.
  • I’m actually pretty excited by the motion co-processor stuff, especially if it really can differentiate between running and biking. No exercise tracker has nailed that yet.
  • Still 8MP, but I’d argue that’s all you need for a good camera phone.
  • With that camera bump, I really expected OIS.
  • Ah, there it is…but only on the Plus. Shame.
  • Burst Selfies. Yup, that’s what the world needed.
  • iOS8 is still pretty great…and that’s about as much time as Apple spent on it, too
  • Apple finally bumped up the storage in their models, though of course they couldn’t bother to put 32 GB in the $199 model. Because margins.
  • 40 minutes for the new iPhones. That’s a lot of time for whatever is left.
  • I wonder if Apple will talk about wireless payments without even mentioning NFC.
  • If Apple fails at mobile payments, I feel like it’s probably dead for a long time. Hope they get this right.
  • Oh, I was wrong. They actually mentioned NFC.
  • If nothing else, maybe this will get NFC-based mobile payments into more places, regardless of payment platform.
  • Oh wow, an actual “One More Thing…”  Here we go.
  • Apple’s making a watch?! No way!  Said no one, ever.
  • Wow, is it really just a square smartwatch?  Hope there’s more to it, because right now this looks like an Android Wear watch for iPhones.
  • Lots of customization though, so that’s neat.
  • I love how this is getting a standing ovation before we even know what it does.
  • I really don’t see how this is any more acceptable to wear in public than existing smartwatches.
  • So…what’s the battery life?
  • Not always on. Responds to wrist-raise.  Strange that it turns “on” to the home screen and not the watch face, though.
  • I…don’t know about this.  This looks like an iPhone on your wrist, rather than a companion to said phone.
  • I’m starting to think this thing doesn’t have a touchscreen.
  • Ah, there it is.
  • Looks like the exercise tracking stuff isn’t really much more advanced than something like the Moto 360.  That’s a shame.
  • Wireless charging on an Apple device. That’s always good.  Wonder if it’s Qi, or something proprietary.
  • Multiple sizes is good. More companies need to get on that.
  • So much for the claims that Apple would unveil something that changes the entire way people think about wrist wearables.  It’s very pretty, but it’s not a game-changer – it just means the game is truly afoot in the wearable race.
  • This looks way more like a Galaxy Gear than I’d be comfortable with, if I was Apple.
  • These apps are cool, but it’s like it does too much – I don’t wear a smartwatch to use tiny apps.
  • Did people seriously just applaud canned responses to text messages? At least it does have a voice dictation option.
  • Siri on the watch.  Table stakes for the watch game at this point, but still good to see.
  • “Being active is one of the best things you can do to improve your health”…gee, you think?
  • To be fair, this is exactly what I want out of a wearable – smartwatch + exercise tracker + microphone – but it requires an iPhone, which makes it an iffy proposition.  I’m excited to use a Moto 360 to see how decent its heart rate tracking and step tracking are.
  • I mean, it’s basically the iPod Nano on your wrist that so many people wanted.  I’m sure it’ll sell amazingly.  I just don’t know if it’s for me.
  • A basic amount of backwards compatibility down through the iPhone 5 gets applause.  I guess I expected that at bare minimum.
  • Really? “Inductive wireless charging is something only Apple can do”?  *looks over at his wireless charging Nexus 5*.  Fuck off.
  • Using the ease of charging as a way to redirect from likely issues with battery life.  A day at most seems likely.  Probably a bit better than the Moto 360, but behind other Android Wear watches.
  • I love how Apple’s making it look like their charging solution is amazing and innovative, despite the 360’s being better.
  • Early next year – saw that coming.  Not in time for Christmas, so that’s a big miss.
  • Apple Pay works with Apple Watch.  Obviously, but still good.
  • $350.  Not bad. Less than expected, but more than Android Wear competitors.

Overall…I think I’m sticking with Android, for now.  I was relying on the Apple Watch to push me over the edge back into Apple ecosystem, but it’s just not quite enough at this point. Also, seriously, fuck that “Reachability” mode.  What is Apple thinking?

Copyright © 2019 writing about tech

Theme by Anders NorenUp ↑