Android 2.0 features unveiled!

Posted: October 27th, 2009 | Author: | Filed under: Uncategorized | Tags: , , , , , , , , , , , , , , , , , , , , | 1 Comment »

Today, Android SDK Tech lead Xavier Ducrohet announced Android 2.0 support in the SDK, which unveils some of the big capabilities in the latest version of Android, expected to hit the market soon on at least one of Verizon’s upcoming “Droid” devices. In the developer video posted today, for instance, all the new features were shown off on a device connected to the Verizon network, and the release notes say it will be deployable in November.

The keyword with Eclair is interoperability.

Motorola recently launched its custom Android build with a UI called MotoBLUR, the central function of which is the ability to integrate with a user’s many social web services from a single interface. The new APIs included in Eclair give this communicative function to all developers. So with the new Account Manager API, developers can centrally store account credentials on the device, the Contacts application can now sync and aggregate contact data from multiple accounts, and the Sync Adaptors API provides full two-way contact sync with ANY backend.

To provide a single, unified face for this data, the Quick Contact function has been added. By clicking on a contact’s picture, a user can pull up a menu of all the different ways to reach that contact…Gmail, Email, IM, Phone, and the various Social networks. It’s like the existent “live folder” concept for contacts, but brought together under the standard contact list, or in any app the developer chooses.

Android 2.0 also updates the Bluetooth API so apps can now access Bluetooth controls to discover, connect and share information with nearby devices, which unlocks the ability to make peer-to-peer and proximity-based applications.

The built-in Android browser has been updated with a refreshed UI with an actionable address bar, bookmarks sorted by thumbnail, double-tap zoom command, and HTML5 support, which opens up Application cache, client-side SQL databases, geolocation API support, and fullscreen video tag support.

The camera app has again been tweaked, but this time it includes digital zoom (with macro mode), built-in color effects (posterize, solarize, etc) and built-in flash support.

It even adds Exchange Support and includes Multi-touch support for the soft keyboard.

Throw this out there with the upcoming availability of Verizon Droids, the Sony Racheal, and whatever else is coming out, and we’ve got a really huge quarter for Android. I’m gonna start doing video blogs soon, it just takes a bit longer to write and record them.


Android’s first real e-reader was born today

Posted: October 20th, 2009 | Author: | Filed under: Uncategorized | Tags: , , , , , , , , , , , , , , , , , , , , , , , | No Comments »

Never mind that bullshit about the Spring Design “Alex” yesterday. Total patent troll “prior art” move. The Barnes and Noble Nook is real and it’s making me drool.

I’m a Kindle 2 owner and fan. I love how easy it is to read, I love how thin and light it is, I love the free connection to Sprint’s “Now Network” (I wish you could add more quotes around a phrase to increase the sarcasm/attitude/cynicism) . Obviously, I’m also extremely focused on the Android operating system, ecosystem, and lifestyle. So nook really excites me.

I was tempted to rush out my first Android Bakery video podcast to talk about the nook. But I held off.

nook eReader - Android power

nook eReader - Android power

There’s no shortage of news about nook right now. I wrote about it on Betanews earlier today, saying that it somehow managed to combine the spirit of two most “walled garden” tech devices (iphone and kindle) to make a new, uber desirable device.

But the thing is, we don’t know where it fits in the Android family. I contacted B&N this afternoon to see if they could get me in touch with a developer who could explain, just how much of an Android device the nook really is, but I haven’t heard back from them yet. That’s how excited I am. I’m posting a story before I even have any useful info. Just check back, I’ll have something good.


My six reasons for considering the Cliq

Posted: September 10th, 2009 | Author: | Filed under: Uncategorized | Tags: , , , , , , , , , , , , , , , , , , , , , , | 2 Comments »

AndroidGuys is a solid site.

Amid the hue and cry of today’s Motorola Android news, they’ve made a post saying “We want to hear what you think of the Motorola Cliq and MOTOBLUR.”

Well, I’ll tell you what attracts me to the Cliq in order of importance:

The Cliq (aka "Dext" aka "Morrison")
1.) Glass Screen–the G1′s screen is just too sticky. Glass has just enough friction to feel good, and it totally enhances the touch experience, not to mention adds stability to the entire unit.
2.) Boosted RAM–even though it’s only a minor bump, it’s totally something that will make a noticeable difference in day to day use.
3.) Solid Chassis– This is the only thing I consistently favor about the iPhone, and if this is anywhere in that neighborhood, the Cliq will have improved on all my biggest complaints about the G1.
4.) 3.5mm headphone jack–Self explanatory: I use the MP3 player, DroidLive, Listen, and now Pandora and I DESPISE the usb headset. I will dedicate a rant to this in the near future.
5.) Keyboard–it may not be as powerful as the HTCHero*, but it’s the second ‘droid phone on T-Mobile with a keyboard.
6.) Exclusive UI—Not that I particularly have a need for social networking 24 hours a day, but I am interested in the UI design since it’s been compared to HTC’s Rosie/SenseUI, which I totally dig.

Naturally, I want to handle it before I decide to buy it…but it’s beginning to look like this is what I’ll be picking up in the fall.

It’s not a phone to die for by any stretch, but it certainly would be an improvement over the G1, aside from the move from a trackball to a D-pad, which would only take a matter of time to get used to.


Face it, Tattoos aren’t cool any more.

Posted: September 8th, 2009 | Author: | Filed under: Android, hardware | Tags: , , , , , , , , , , , , , , , , , , , , , , , | No Comments »

In case you missed it today, HTC announced its fourth Android device, the “Tattoo” (which was formerly called “Click”.)

Everybody’s expecting it to be the cheapest Android phone yet, which is itself an exciting possibility, but I look at the device with absolute boredom.

I see you have a tattoo.  You are 88% more likely to be a douchebag.

I see you have a tattoo. You are 88% more likely to be a douchebag.

Design-wise, it’s HTC’s third all-touch Android phone in a row (if you don’t count local variations,) and the only unique thing it has going for it is its faceplate changeability.

Once you get into cosmetic “improvements” like that, I get extremely, violently, bored. Any time a company gets into the business of slapping prefabricated “art” on my tech devices, I want to give said company a flying axe handle to the head. I don’t want to see tribal tattoos or urban camouflage on ANYTHING much less on the device which I will prominently hold up to my face in public or have sitting on my lap for hours on end.

Get that shit away from me NOW.

Art-related stuff like Dell Studio notebooks and iGoogle skins I can get down with. Those prominently feature the artists’ names and are unique to their tastes and talents. There is absolutely nothing unique about the shit they’re slapping on the HTC Tattoo. Even the name offends me…I feel like that’s up there in bad names with Motorola Rokr. Why not just name it the HTC BAD BOYZ or something?

Furthermore, this gets into the realm of things that I hate: The separation of “Tattoo” from “Art.” But that’s a rant for a non-tech blog or a day where I have more time to bitch.

On a more fundamental level though, there’s another issue with the Tattoo.

Reportedly, it has been equipped with a resistive touchscreen to get to its lower pricetag. I know how sucky a bad resistive touchscreen can get. You ever use a Chumby? HA. They say you don’t need a stylus for it, but you just try setting an alarm on that thing without one. Resistive touchscreens make me think of business geeks with a coke nail that they grew to make interaction with their phone easier because they don’t want to have to whip out a stylus.

But this brings me to my main issue. I know quite well that Android is a touch OS; but when you’re a big company in the business of making internationally distributed consumer electronics devices, how hard would it be, really, to port Android down to a non-touch device if you’re just looking to save money? Rather than attempt to preserve the experience you’d get with a capacitive touchscreen, you just create a new button-based experience.

I’d love to see a BlackBerry-style Android device. HTC makes the Dash and the Ozone and they’re fantastically comfortable devices. I know..I know, I favor keyboards. I’m sorry. But I strongly believe that anyone who’s had to rely on a smartphone in a high-pressure work situation will agree with me: hard keys are needed for hard work.

We’ve got devices from Motorola coming this week, and some from LG on the horizon. They all at least have keyboards, but what I’m really looking for from HTC is something like the BlackBerry Bold: a smaller touchscreen and a full candybar keyboard. Or hell, just a re-designed Android interface that we can drop into non-touch devices.


Poking around with Electrum Drum Synth

Posted: August 25th, 2009 | Author: | Filed under: Apps | Tags: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , | 3 Comments »

Because I spent many years as a poor musician, my area of gear expertise isn’t with high quality instruments, it’s with bargain equipment (think Zoom, M-Audio, Casio, et al.), pawn shop finds, and things best classified as “musical toys.”

I keep up with the latest toy musical instruments, and delight in their exploitation. Circuit bending brightens my day, and I’m always looking out for the next Stylophone. I got the Korg DS-10 on the day it came out, I have two copies of Traxxpad for PSP, and I consider the iPhone/iPod Touch to be a full-fledged music platform.

I guess i’m a pretty discerning customer in the “Don’t Expect Much” category.

Electrum was made by Niko Twenty and is available for $3.99 in the Android Market. What you get is a 16-step sequencer somewhat like the ol’ TR-808 in design, and each sequence is built with six samples. You can put together up to 32 different sequences and create full songs. The cool part is that you can export your creations as single sequence loops or as a full song. The dumps are 16 bit wav files (mono).

A blurry, late night shot of Electrum's interface

A blurry, late night shot of Electrum's interface

I had originally intended to put in a couple of quick sequences that I whipped up on the “rock kit,” but I’m having some trouble doing that, so I’ll just say that there’s also 808, 909, Orchestral, Hip Hop, and Human Beatbox kits and 6 free downloadable packs. While it’s pretty light on features, the only thing it’s really lacking is the ability to import your own sample set. (See Comments)  I always find myself wishing for a sound recording sampler app so I can make my own Richard James kit of nutty noise captured on the phone’s mic. But I guess I have to wait.

If you’ve ever used BeatMaker on iPhone, don’t expect that level of quality. However, BeatMaker costs 20 fricking dollars and Electrum costs only 4. At one fifth the price of BeatMaker, you get much more than one fifth of the functionality with Electrum. Complaints are few. It does get crashy at times, it has dumped some broken .wavs for some reason, and the UI in Sequence mode looks like it’s unfinished. But it’s a work in progress and junk musicians should applaud Niko Twenty.

This is definitely one of the best music apps we have on the Android Platform, and I’m currently working on a little jam built with beats from BeatMaker, a guitar track from Ubisoft’s Jam Sessions for Nintendo DS, and some Theremin wangling from Bebot on iPhone.