Tag Archives: iPhone

Okay, first things first: that headline was pure sensationalism at its core. I love Android, and there are currently no alternatives to it that I would consider as reasonable replacements for everything Android does so damn well. But it’s very often the little things that can really frustrate you when dealing with a device or platform.

Case in point, Android’s handling of its multimedia duties. See, when Apple decided to get into the smartphone biz, they completely changed the paradigm of what we expected. Instead of a phone built around business needs that could also browse the web and play audio files, they started with an iPod and built around that. In fact that’s what led to many of the early jokes about the iPhone really just being an iPod that made phone calls. It was initially best at its roots and poor at everything else. It’s since improved drastically, although the joke that it’s terrible at making phone calls remains.

Meanwhile Android came from a more base concept of trying to do everything, and launched after the iPhone set the standard for these concepts. It, IMO, got the overall OS concept down much better, appreciating that we need to run more than one app at a time, that when something wants our attention it shouldn’t completely overtake the activity we’re participating in, and allowing applications to tie their needs together in all kinds of clever and involved ways. But what it lacked was the long history of multimedia experience to inform that functionality, and that’s where it still fails.

To be clear, Android’s built-in media abilities are fine. They do the job well, their interface is decent, and I have little need to complain about it. Some phones, such as the Galaxy S line, include support for a lot more codecs making it actually EASIER to play videos on my phone than on an iPhone (my Epic 4G has so far played every single video format I’ve thrown on its card, without conversion) or Zune, and include improved media players. As well the Android Market is packed with alternatives for better podcasting software than Google’s passable Listen app, better video players such as mVideoPlayer, better music apps such as DoubleTwist or WinAmp or a dozen others, streaming options like Slacker, etc. Point is, its flexibility allows it as a media device to functionally match or surpass the iPhone and Windows Phone 7 quite comfortably, even if not as fluidly or naturally. So it’s not in its technical abilities that Android fails me. It’s merely in one simple overlooked place: audio mixing.

Android seems, under most circumstances, unable to mix two disparate sources of audio into its output at the same time. When playing music, a video, streaming audio, playing a podcast, etc., any other audio playback that occurs (such as the variety of notifications your dozens of apps can use to get your attention, carefully customized to exactly your needs, or directions from your navigation software), the OS will simply kill whatever audio track was already playing for as long as it takes to play back the other audio (including any dead silence that was included in the clip before or after), and then continue playing the original line of audio. It doesn’t pause the audio, it merely mutes it. When playing back music this is unbelievably annoying and distracting, and when playing back an audio book or podcast it’s simply unforgiveable. The number of times I have to hit the skip back button in BeyondPod to see what I missed because an email came in while I was enjoying the latest Drabblecast is ridiculous, not to mention mildly unsafe. And even in music it leads me to avoid using Slacker or my other amazing music sources when I have guests in my car because it’s simply embarrassing to have the audio constantly shut down while we’re trying to enjoy ourselves. I find myself apologizing for it or simply shutting it off and switching to FM.

So far Google seems unconcerned with the issue despite the large number of complaints in their support sites about it. The problem’s existed throughout every version, and it doesn’t seem to be acknowledged. But it’s enough to make me consider digging out my Zune again just for audio, except it still fails to provide me the streaming options I’ve grown to expect since switching to Android.

Another smaller failing in this area is Android’s handling of Bluetooth when there’s an audio cable plugged into the device. It seems to assume that if I have anything plugged into the headphone jack that I must prefer to use that as my hands-free solution instead of the paired and connected Bluetooth headset. This might make sense if I were using the included headphones with microphone built in, but it’s a failed assumption when I’m in the car and have an audio cable plugged into my sound system. It’s even more of a failure since it doesn’t notice that my audio cable doesn’t have a line for microphone, can’t deliver audio to it, and doesn’t leave the phone’s built-in mic open. So when I’m driving and listening to music through my phone and I get a call, despite having my Bluetooth headset on and in my ear, I have to reach over and unplug the audio cable from my phone and then answer the call, otherwise I hear my caller through my car’s speakers and they hear nothing in response. The iPhone, as far as I’ve witnessed, actually asks you which device you want to answer through when a phone call comes in, routing to your Bluetooth or other options accordingly. Presumably if you were to hit the answer button ON your Bluetooth it would be smart enough to route there. Android still doesn’t do this.

These issues aren’t enough to override everything that I love about Android, but they are enough to cause some audible profanities in my car for reasons I don’t think are necessary. These SHOULD be easy to fix, as even Windows Mobile, for all its failings, worked fine in these circumstances. And yet, at least for now, they remain untouched. Google’s lack of concern on these types of matters seems to border almost on Apple’s methods of telling their users their desired features don’t matter, except Google instead simply ignores the problem entirely. It’s unfortunate, and I really hope it improves. While I’m sure there are other issues with Android that bug me, if these two problems were resolved I’d feel as close to 100% happy with it as I could in a technology world with a constantly moving target of expectations. Let’s shore this up and move on.