Posts Tagged ‘nexus one’

VloMo Numbers 7 and 8

// November 8th, 2010 // No Comments » // android, blogging

Since I missed yesterday’s VloMo, I decided to do two videos to make up for it. I realize that’s already the second time I’ve had to make up for slacking off, and I’m sure it’s not going to be the last time. The first is one that I’m known for, making videos while driving. The second is an introduction to the McDonald’s McRib sandwich.

The McRib really isn’t good enough to warrant its own video, honestly, but whatever.

Happy National Videoblogging Posting Month!

// November 1st, 2010 // 1 Comment » // blogging

My friend James Whatley has been talking about vlomo10 for a few days now and I had mostly ignored him until he published his first video here. I’m a sucker for video blogging (or at least I used to be) and have been wanting to get back to creating content lately, so this is a perfect excuse.

More to come tomorrow.

An Android Use For The iGo Stowaway Bluetooth Keyboard

// September 26th, 2010 // 13 Comments » // android, pc-free

image

One of the biggest challenges that I’ve been facing with my experiment to not use my laptop for any personal Internet use is with text input. Unfortunately there is a severe lack of decent Android-powered smartphones with a built-in QWERTY keyboard, so I’m stuck using the onscreen keyboard.

After struggling with it, I remembered that some years ago I bought an iGo Stowaway Bluetooth keyboard for $30, which was an incredible deal. I’ve used the keyboard with several of my Nokia handsets, and was bummed to discover that Android does not have the Bluetooth HID support that my Nokia phones have always had. Fortunately, CyanogenMod’s v6.0 ROM has this support built right in.

As you can see in the image, I’m now using my iGo Stowaway Bluetooth keyboard to type this on my Nexus One. It’s definitely a great solution, and will make blogging from my phone a much more enjoyable experience, for sure. Unfortunately, I wasn’t able to find any good deals on the iGo Stowaway Bluetooth keyboard online anymore. Amazon wants over $100 for it, and most of the Ebay auctions are priced the same. If you got in on the $30 deal a while back like I did, I would definitely encourage you to root your phone, install CyanogenMod v6.0, and enjoy the keyboard once again.

Posted from WordPress for Android

Nokia Does Phontography, Droid Doesn’t

// July 22nd, 2010 // 8 Comments » // android, Mobile

When I decided to dump my Symbian-powered smartphones and pick up the Nexus One, I knew there would be some sacrifices involved. One of the biggest things that I knew I would be giving up is a solid phontography experience. If you don’t know, ‘phontography‘ is photography using phones. I’m a huge fan of phontography, and really don’t see the need for a stand-alone camera, specifically with the great selection of solid cameraphones and the connectivity they offer. However, I didn’t realize just how big of a sacrifice this would be until I started using my Nexus One. There are two parts to the phontography experience – hardware and software (much like any other phone use-case-scenario these days).

Hardware

This one’s tough to complain about with the Nexus One, for a few reasons. For starters, I knew ahead of time that the phone lacked a dedicated camera button and decent flash. I also knew that it only has a 5 megapixel camera, and that reviewers had discovered it took rather poor photos. Unfortunately, there are precious few manufacturers building GSM Android-powered smartphones with support for AT&T’s 3G network, much less ones with decent cameras. This is a major reason that I want Nokia to build a few Android-powered smartphones- they dominate in the camera arena, and that’s a niche in the Android ecosystem that’s currently not being addressed at all.

Of course, there are Android-powered smartphones that bring the megapixel count to the table – that’s easy. What the other manufacturers are missing is the various other hardware improvements that Nokia has been focusing on with newer devices like the Nokia N86 8MP and the upcoming Nokia N8. Nokia’s lead camera guy, Damian Dinning, recently posted an exhaustive FAQ on the Nokia Conversations blog, detailing the behind-the-scenes hardware (and software) improvements that the company has focused on with the Nokia N8. Most of Nokia’s cameraphones feature Carl Zeiss optics, and they’re experimenting with larger sensors and different types of lenses to really produce a solid camera experience. As far as I know, no other manufacturer is taking such pains to produce a fantastic phontography experience.

Software

Software, however, is something that could be easily addressed, but isn’t. While I don’t expect a cameraphone to replace a DSLR (though some probably could), I have gotten used to my phones having a certain level of options while snapping photos. Things like burst mode (great for stop-motion vids), scene settings, and more are options that I’m used to having on my Symbian-powered phones but are missing in even the latest version of Android (v2.2 ‘FroYo’).  While the latest version of Android has updated the camera app from what I used on my HTC Eris with Android v2.1, it still doesn’t hold a candle to my Symbian-powered handsets.

Nexus One Camera App

As for sharing, I’d say that it’s a wash. Using Pixelpipe and Share Online on my Symbian-powered smartphones from Nokia, I had no trouble uploading to Facebook, Twitter, and pretty much anywhere else I’d want to share my photos. Luckily, Pixelpipe is also available on Android, so I didn’t have to sacrifice any capabilities there. One complaint that I actually have about Android is that tons of apps support media uploads. While this is obviously a good thing, it can really junk up the ‘Share’ button found in the gallery – in fact, in landscape mode, I can’t see my Pixelpipe option for all the other junk in this list. I’d love to have the ability to choose what does and doesn’t show up in my Share list on my Nexus One.

Nexus One Sharing

Now, it’s important to be fair – there are newer Android-powered devices that do have a dedicated camera button and a custom camera applications to make the experience better. Unfortunately, these are custom jobs – they’re specific to a handset or manufacturer, and not part of the default Android experience. I really hope that future Android devices pay more attention to the phontography experience by default.

Is the Nexus One a horrid phontography device? Not entirely. While I have to make do with no hardware button to launch the camera, I am able to use the trackball to actually snap photos – which isn’t much different than what I was used to on my Symbian-powered smartphones. The quality of photos obviously lacks on the Nexus One, but there are software improvements that can help that, and newer Android devices such as those from Motorola do have some better features, including a dual-LED flash and dedicated camera button. When taking pictures and video, though, I still miss my Nokia’s – it’s one reason the upcoming Nokia N8 still tempts me to switch back. Nokia, despite their struggles, continues to produce what I consider to be the absolute best content-creation devices on the market.

Why I Chose The Nexus One

// July 21st, 2010 // 12 Comments » // android

google-nexus-oneSince announcing that I was leaving Symbian and picking up a Nexus One from Google, I’ve had countless discussions about why I chose this particular handset over others on the market that are newer. The answer is easy – it’s really the only option for AT&T customers who want a decent Android experience.

The other big guns in the Android ecosystem – the HTC EVO 4G, Motorola Droid X, and HTC Droid Incredible – are all CDMA-based devices that won’t work on AT&T’s network at all, and don’t support the use of SIM cards. In fact, there are currently only 5 Android devices on the market today that support AT&T’s 3G network: the Motorola Backflip, the HTC Aria, the Nexus One, Motorola Milestone, and the Samsung Captivate.

The Motorola Backflip, HTC Aria, and Motorola Milestone don’t have the specs that I needed. Since my biggest complaint with my Symbian-powered smartphones is the overall speed and multitasking capabilities, I knew I needed to get an Android device powered by a 1GHz processor and with a minimum of 256MB of RAM. That instantly rules out the Backflip, Milestone, and the Aria, leaving only the Nexus One and Samsung Captivate. I also really wanted to have at least a 3.7-inch display.

With early reviews showing the Captivate (and its unbranded brethren, the Samsung Galaxy S) with stuttering and lags in the menus and applications, the Nexus One started looking even better. There’s a really active developer community and the Nexus One has already been officially updated to Android v2.2 – an update that the Captivate is slated to get, but no one really knows when. Also, the Nexus One has been the first device to receive previous new versions of Android, by virtue of it being ‘pure’ Android. Thus, it stands to reason that it’s much more likely to get whatever the next version of Android is – more likely than a manufacturer-customized handset like the Captivate is, at least.

Since I used my upgrade to pick up a RIM BlackBerry Bold 9700 a few months ago, I was going to purchase either handset at full retail, so pricing wasn’t a factor in this comparison. To be honest, I ruled out the Samsung Captivate pretty quickly – with no flash for the camera and reviewers saying it stuttered, it doesn’t really offer me any benefits to go on. Oddly enough, the decision actually came down to the Motorola Milestone and the Nexus One.

The Motorola Milestone is the GSM variant of the Motorola DROID offered on Verizon. It’s roughly the same price as the Nexus One, but I’d have to import it – it’s only officially sold in Canada. While the Milestone only has a 550MHz processor and 256MB of RAM, it also has a hardware QWERTY keyboard and dedicated camera button with dual-LED flash – both features that I really wanted to have. In the end, I chose to go with the Nexus One instead, mainly due to the processor and probability that it will continue to be upgraded.

Shortly thereafter, Google announced that the final shipment of Nexus Ones arrived in its distribution centers, and that it would not be ordering any additional units. While some have claimed that makes the device obsolete, I disagree. Of course, the device is now EOL (End-Of-Life), which is somewhat of a factor, but the technology and specs inside are by no means obsolete, especially compared to the current crop of Android-powered devices on the market.

To be quite honest, I only really expect to use the Nexus One for about a year. By next summer, Verizon’s 4G network will likely be launched in enough places, and I’ll have an idea of whether or not I can stick with the same phone for 12 months, too. I’m really hoping that there will be some improvements in the Android cameraphone selection by then.

What do you think? Even though Google’s made the Nexus One officially EOL, does that make it obsolete? Is it still a solid choice?