The Android Invasion: My impressions of our new Neato XV-11 robotic vacuum

So, my girlfriend has always been saying that the one thing she wishes she had more of is time. She joked around with me several months back about getting a Roomba to make life a little easier for us, and my curiosity was piqued.

Tomorrow is her birthday, so I went all-out and bought a Neato XV-11 robotic vacuum. I've only played with it for about an hour, so consider this more of a "hands-on" review than anything thorough.

First, important "good boyfriend" tip. Never get your girlfriend something that you're even more excited about getting than she is, even if she said she wanted it. She certainly likes it, but I've definitely been given the "oh I see why you got it" treatment. I really did get it for her because I wanted to see her smile as a machine cleaned the house for her, but since it benefits the both of us, perhaps it wasn't exactly the best birthday present choice. Duly noted!

Read on past the break for my review.

The Necromancer

The title of this blog post also happens to be the name of the book I'm reading. Perhaps I've just been inspired to do a little necromancy of my own, but with less cadavers and more circuit board.

I'll explain; let's start with the fact that something's been bugging me. My desktop PC does not have a discreet GPU (video card).

You might be thinking, "WTF, and you call yourself an electronics freak?!" Well, you've got me there, but I do have reasons. One primary reason is that I'm not a gamer anymore. I do almost everything on this laptop nowadays, and I only took my desktop out of storage a few weeks ago so that I could get a decent VM box running in the basement next to my HTPC and my Cisco lab hardware.

However, my integrated GPU (despite it being a reasonably beefy AMD HD 3200) just ain't cuttin' it for some of the video processing and RemoteFX stuff I'd like to mess around with.

Fortunately, I have an NVIDIA 8800 GTS in a static bag that should do what I need it to do. Unfortunately, it's going to take a little more than me popping this sucker into my PC to get it running.

Problem #1: The graphics card does not have an enclosure for the heat sink; the fan cannot circulate air to keep it cool.

Problem #2: It's damaged goods. (Okay, I lied, the card isn't entirely dead. But someone who brings sick people back to life is a doctor, and that's a lot less fun than being a Necromancer!) It displays bands of pixels vertically across the screen that are visible during the boot process, which means it's a hardware issue, not a driver problem. Additionally, it usually won't boot into Windows, causing the system to hang when the operating system is starting up. On the rare chance it does make the boot into Windows, graphics are horribly distorted.

So, I'm screwed, right? Hell no! I wouldn't pass up an opportunity like this! Read on to see how I got this old workhorse running again.

Insights into the MicroSD card black markets...

Trust me, if China's hardware black market fascinates you like it does me, you'll find this blog post very interesting.

http://www.bunniestudios.com/blog/?p=918

I've never read anything else by this guy, but apparently he's a production manager for the Chumby, which is a rather interesting piece of hardware itself, particularly if you're the kind that likes to tinker.

Essentially, his production line ran into a rash of quality control failures and upon investigation, he found that Kingston had sold him a large batch of MicroSD cards from a very questionable source.

He goes into great detail and even drops a bunch of chips into acid to find out where they actually originated from. I learned a lot reading this article, and will undoubtedly be looking much closer at the SD cards I purchase in the future...

Samsung Transform - Sub-par hardware in a pretty package.

Just finished reading the review on Engadget of the Samsung Transform, a "mid-end" Android phone launching on Sprint that shares a lot of similarities with my Epic 4G on the surface. But as the review notes, hardware performance is pretty terrible. And that's not surprising since the Samsung S3C6410 inside is an ARM11 chip that was released in 2008.

That's some pretty tired hardware chugging underneath the surface of the Transform, almost comparable to the hardware in the Droid Eris. The problem is, the hardware in the Eris was called old when it launched nearly a year ago. We shouldn't be seeing ARM11 chips anymore. We're almost 2 generations ahead of that tech. 

Keep in mind that Cortex-A8 chips are way faster MHz for MHz than the ARM11 chips. The 667 MHz processor in the Transform accomplishes the same amount of instructions per second as a Cortex-A8 running at 417 MHz. On top of that, Cortex-A8's ARMv7 architecture accomplishes more with less instructions than the Transform's ARMv6. 

In short, the 550 MHz Cortex-A8 processor in the original Droid (which launched almost a year ago) kicks the pants off this chip. And that's not even going into graphics processing power, where the Mali-200 GPU in the Transform doesn't fare any better.

Releasing phones like this is not healthy for Android, which is moving in a direction that requires phones with better hardware, not stuff that's nearly 3 years old. The new JIT compiler in FroYo (Android 2.2) will allow this chip to perform at least reasonably well by boosting average CPU performance over 4 times. This seems to be the only possible justification that Sprint might have used to launch this phone. Unfortunately, they've made one major oversight; it won't help the miserable performance of the GPU.

Here's hoping this isn't a trend. Improvements to Android's compiler should not be used as an excuse to launching obsolete hardware.

An Epic upgrade...

As you may have guessed, I've gone and gotten an Epic 4G from Sprint, which I'm currently taking for a trial run.

Sprint's network has definitely proven to be a bit more spotty than Verizon's, but not unbearably so. I've been spoiled on Verizon. 4G coverage is actually reasonably good, even if the speeds still don't compare to the WiFi connection I have when at home.

I've had the phone for almost 3 weeks now (yeah... sorry for not mentioning anything earlier, life has been busy), so I'm coming up on the end of my trial run. I think I'll be sticking with Sprint, though the network may prove to test my patience.

I'm not going to rattle on too long about the phone, there's dozens of reviews on the web that'll tell you about the Epic 4G. All I can say is that it definitely meets my expectations and is an excellent piece of hardware. It is not, however without its faults, as Samsung's build quality issues do show through. In the first couple of days I got the phone, sometimes the capacitive Menu button would spontaneously and repeatedly act as if it had been touched, even if I wasn't touching it. Other times it would not respond at all. I found that the device was running a pre-production ROM, and had to manually update it. Once I did, I immediately got an OTA update and the problem disappeared. Perhaps Sprint should take the blame for that one. There are also a few very thin gaps (fractions of a millimeter) between the glass on the front and the bezel, which already are gathering small amounts of dust.

But the complaints are few when compared to the great things I have to say about this device. The screen is amazingly bright, colorful, and responsive. Tilt and acceleration sensors are very accurate. Battery life is good, all things considered. I've had no issues with the GPS since the updates have come through. Front camera works right in the main camera app (Self-Portrait option) and the slide-out keyboard has a nice spring open, feels solid, and the keys themselves are well spaced and have excellent response and travel.

The phone is zippy, but does hit an occasional snag. I'm hoping Froyo works this out of the system with the new JIT compiler, though the problem ultimately likely lies with the I/O bug that plagues the Galaxy S line. I know that the XDA developers have produced a fix for the Captivate, hopefully we'll see one soon for the Epic.

As for Samsung's UI, I've played around with a couple custom home launchers and themes but I keep finding myself coming back to TouchWiz. It might not be pretty, but it does get the job done. Perhaps I'll get rid of it when I get around to rooting my phone, but I've got my 7 homescreens already organized at this point and I'm perfectly fine with the way it looks.

I'll leave things at that for the time being. I'll have further things to write about regarding the phone and Android in general in the coming week, so stay tuned... I'll try to do a better job of keeping my blog up to date, I promise!

HTC Glacier and my friends over at AlienBabelTech.com...

A couple weeks back, I was checking on a comment posted in response to my Android Benchmark blog post regarding some interesting performance values for the Droid X on GLBenchmark.com.

GLBenchmark has been a useful tool for me in the past; specifically I used iPhone 3GS performance values to estimate graphics performance in my Hummingbird vs Snapdragon article. I replied to the comment and noticed something strange, a new contender named "HTC Glacier" sitting on GLBenchmark's results list above the Galaxy S phones which were reigning supreme at the time.

It made me raise my eyebrows... an HTC phone of that power could only contain a new Snapdragon of some sort. I started to dig into the specs a bit... and then I was pulled away from my computer by the joys of fatherhood. HTC Glacier was forgotten as I scraped up food flung all over the place by my misbehaving daughter. I remember being tired that night, heading to bed soon after I managed to get my temperamental child down for the night.

Fortunately, someone else was paying better attention; my good friend MrK over at AlienBabelTech.com who has hosted my article and several of my blog posts, and with whom I communicate regularly. He spotted the HTC Glacier as well, and wasted no time in doing some sleuthing, finding that the person who posted the HTC Glacier was a T-Mobile Design Manager... quickly answering the question of which carrier Glacier will end up on. He also theorized that the Glacier contains the 1.5 GHz Qualcomm Snapdragon QSD8672, and it wasn't long before his article was being linked on tech blogs across the web.

Android phones benchmarked; it's official, the Galaxy S is the fastest.

Consider this post a follow up on my ruminations post, in which it turns out I was likely completely wrong.

But hey, you can't win 'em all, and at least I was right about one thing; the 1GHz OMAP 3640 3630 isn't terribly different than the 550 MHz OMAP 3430 on the Droid, and at 1 GHz doesn't really give us any surprises when it comes to performance.

Then why did it score so well in this test? Taylor Wimberly, owner of AndroidAndMe.com (yes, the same website I've frequently complained of putting bad data in its articles), has performed a series of benchmarks that explains why.

Ruminations on various benchmarks for the OMAP 3600s, Hummingbird, and Snapdragon.

EDIT 7/17/2010 - The benchmarks have been explained for the most part, see my post "Android phones benchmarked; it's official, the Galaxy S is the fastest." Or, feel free to read on, but I was probably wrong. :)

I've been thinking about some of the performance benchmarks I've been seeing on AndroidAndMe.
http://androidandme.com/2010/05/news/high-end-android-phones-benchmarked-with-quadrant/
http://androidandme.com/2010/06/news/high-end-android-gpu-showdown/
http://androidandme.com/2010/06/news/hands-on-the-motorola-droid-2/

CPU performance from the new TI OMAP 3630 3640 (yes, they're wrong again, its 3640 for the 1 GHz SoC, 3630 is the 720 MHz one (TI disagrees) is surprisingly good on Quadrant, the benchmarking tool that Taylor is using. In fact, as you can see from the Shadow benchmarks in the first article, it is shown outperforming the Galaxy S, which initially led me to believe that it was running Android 2.2 (which you may know can easily triple CPU performance). However, I've been assured that this is not the case, and the 3rd article seems to indicate as such, given that those benchmarks were obtained using a Droid 2 running 2.1.

Now, the OMAP 3600 series is simply a 45 nm version of the 3400 series we see in the original Droid, upclocked accordingly due to the reduced heat and improved efficiency of the smaller feature size.

If you need convincing, see TI's own documentation: http://focus.ti.com/pdfs/wtbu/omap3_pb_swpt024b.pdf

So essentially the OMAP 3640 3630 is the same CPU as what is contained in the original Droid but clocked up to 1 GHz. Why then is it benchmarking nearly twice as fast clock-for-clock (resulting in a nearly 4x improvement), even when still running 2.1? My guess is that the answer lies in memory bandwidth, and that evidence exists within some of the results from the graphics benchmarks.

The Samsung Galaxy S Pro exists; fulfills my every desire.

You may have read my article, "Hummingbird vs. Snapdragon: The 1 GHz Smartphone Showdown". I definitely favored the Samsung Galaxy S in my performance review, but personally, the lack of an LED flash has been a detractor for me.

I've also preferred a hardware keyboard, and my understanding was that this was something I'd have to give up for my new smartphone. I'd dismissed rumors of the Samsung Galaxy S Pro, as there was no visual proof and it seemed far-fetched.

But the Samsung Galaxy S Pro has been outed as a reality, and the idea of getting a Galaxy S with a keyboard has been an exciting possibility, however the recent info on the Droid X has been enough to make me ponder my other smartphone options, as it sports a 4.3 inch display and supposedly a 45 nm 1 GHz TI OMAP 3640 SoC (no, not a 3630, Engadget got it wrong, that's the 720 MHz version).

Two game-changers have been dropped on me to make me change my mind, and both hit me with 1 spy shot of the new Galaxy S Pro.

And here are some other shots of the front:

The very first thing I noticed is an LED flash. Awesome! Now no more worries about taking pictures in low light. But what's that above, next to the Sprint logo... 4G?! Sweet! Wait... doesn't Sprint have a tiny 4G network? Yes. But wait... my home city of Rochester is on Sprint's 4G launch list for July?!

... Yeah, I know what my next phone is going to be. This thing is the dream device I've been waiting for since last year. Amazing processor and graphics hardware, 4 inch Super-AMOLED display, 5 MP camera with flash, front-facing camera, slide-out physical keyboard, and 4G connection (with 4G available!)

Knowing my luck, something even more amazing will show up a week before it launches... no, let's not even imagine that!

Source: http://androidcommunity.com/exclusive-first-picture-of-the-galaxy-s-pro-20100614/ and http://androidcommunity.com/exclusive-more-pictures-of-the-galaxy-s-pro-20100614/

Hummingbird vs Snapdragon: the 1 Ghz smartphone showdown

NOTE: This article has been officially hosted at AlienBabelTech.com. For a better reading experience, you may want to view the article here!

If you follow smartphone technology at all, you're sure to have heard of the Qualcomm Snapdragon processor. It's the reigning smartphone CPU heavyweight; a 1 GHz processor packed with a multitude of features, based upon the same ARM CPU technology that modern smartphones such as the Droid, Palm Pre, Nokia N900 and iPhone 3GS use. However, unlike those processors, the Snapdragon runs at 1 GHz while the others run at 600 MHz and under, and thus has become the chip of choice for premium smartphones.

The Snapdragon SoC (System on a Chip) has appeared on the market in several devices recently. The most well-known example is probably the Google Nexus One, though it had already appeared in a previous device, the HTC HD2. The HD2, released November 11th 2009, had a Snapdragon processor as well as a massive 4.3-inch display (diagonally measured), and received rave reviews that almost unanimously ended with one major complaint: the Windows Mobile 6.5 operating system. It’s an operating system largely unchanged from its predecessors and prone to software problems. In addition, to really make good use of the processing power of the phone, applications needed to exist that made use of that power, and the majority of applications written for Microsoft’s mobile OS just didn’t take advantage. The industry begged for an HD2 with Google’s Android mobile operating system, and HTC responded that it wasn’t going to happen.

But then Sprint announced the HTC EVO 4G at the CTIA 2010 trade show, and the mobile industry collectively went wild. Here was the phone everyone had been dreaming of; a 4.3-inch display and 1 GHz Snapdragon like the HD2, as well as a deployable kickstand, 8MP rear camera, 1.3MP front camera, HDMI port, and 4G WiMAX connectivity. The HD2 had essentially been reborn, new and improved, for the Android OS. Judging by the limelight cast upon the EVO 4G by the mobile enthusiast community, the EVO 4G is positioned to become one of the best selling smartphones of the year.

However, another device debuted at CTIA 2010 that was largely overshadowed by the launch of the EVO 4G: the Samsung GT-i9000 Galaxy S. This new phone, in contrast, has a 4-inch Super AMOLED display (more on that later), 5MP rear camera, 0.3MP front camera, (GSM/HSPDA) 3G/3.5G connectivity… and was mentioned almost as an afterthought to contain Samsung’s own 1 GHz processor. Samsung spent a lot of time at CTIA 2010 talking about the Super AMOLED display, and in contrast only a few moments disclosing details on the new SoC, stating that it has over 3x better performance than the leading competition (referring to graphics performance), and bests all other smartphone processors on the market today. Only later was it confirmed that the SoC was Samsung’s new 45 nm “Hummingbird” platform, the only production 1 GHz ARM processor thus far to challenge Qualcomm’s Snapdragon.

When the news of these phones hit the tech blogs, nearly all of the attention went to the HTC EVO 4G. The EVO 4G was what many had been waiting for, and the Samsung was typically given hardly a second glance. But let’s take a moment to really compare the hardware of these two Android 2.1 smartphones, and then we’ll even go a bit deeper into how the SoCs actually stack against one another when it comes to CPU and GPU processing power.

Adobe demos its new Content Aware feature; your Graphic Design degree is now worthless.

The best way to understand this is to watch it. This new tool allows an Adobe product to do what would take hours of manual, painstaking work in seconds.

Sprint debuts the HTC EVO 4G: blows our minds.

Sprint's new 4G WiMAX-capable superphone has been announced, and currently outspecs any other phone on the market.

http://now.sprint.com/evo/

Packed into a slim package, this Android phone running 2.1 (with Sense) has a 4.3-inch-across capacitive multi-touch display, a 1 GHz Snapdragon processor, an 8MP rear camera, 1.3MP forward-facing VGA camera, shoots 720p HD video, has mini-USB and HDMI outputs, has 512 megs of RAM, a 1 GB internal drive (with microSD slot for expandability), full Flash support, can function as a mobile 3G/4G connected WiFi hotspot, will come with mobile TV support, and even has a deployable kickstand for your viewing pleasure.

It suffers only one flaw: it's on Sprint!

NVIDIA's new GPU architecture: Fermi

In line with my latest news item, I encourage those of you out there who are interested to check out this excellent article on NVIDIA's new "Fermi" GPU architecture by AnandTech:

http://www.anandtech.com/video/showdoc.aspx?i=3721&p=1

It sheds a lot of light on what NVIDIA is trying to do to compete with ATI right now. They seem to be banking heavily on tessellation performance, but whether or not game developers will actually take full advantage of it remains to be seen. More articles (including a great article that compares ATI and NVIDIA architectures) as well as my take past the break.