Day at the Rally

This past weekend, I, along with thousands of others, attended Jon Stewart and Stephen Colbert’s Rally to Restore Sanity and/or Fear. We drove down on Friday and headed to the Rally early Saturday. We got there early enough to get a great spot close to the stage, but a couple of us got shafted on a food run when the Park Police weren’t letting people back in, causing them to miss half the Rally.

I won’t bother talking too much about the Rally itself, as I’m sure if you care you’ve watched it online, but it was a lot of fun and I met plenty of other Redditors (thanks to the QR Code game the Reddit admins cooked up) and even met one of Reddit’s cofounders at the Reddit afterparty (I even got a shirt signed).

Estimates for the event put it at around 215,000 people, and I can believe it. The mall was packed, and from satellite photos, there were people a couple blocks out in either direction. I wish we’d had another day or so to explore the city, but we all had something to get back to on Monday, so after another ~12 hours in the car, we were back in Louisville (made much less monotonous thanks to decent 3G coverage along the interstate).

Oh yeah, Lookit 0.3 is out

I pushed 0.3 out to the PPA a while ago, but have yet to do much with 0.4. I’ve just committed the first change that actually changes functionality at all and it’s the beginning of a fairly big feature for 0.4, hotkey support. Currently it’s hardcoded in, but I’d like to support changing the key combinations before 0.4 goes much further. Currently <Ctrl><Shift>3 captures the entire screen and <Ctrl><Shift>4 captures an area.

Lookit 0.3 hits Beta

Just the other day, I pushed out the first beta of version 0.3 of my screenshot utility, Lookit. Just a few minutes ago, I pushed out the second.

Lookit is a tool inspired by TinyGrab for quickly uploading and sharing screenshots. This new version brings a couple of new features that the previous version lacked, in particular, compatibility with older, non-compositing window managers, and a selection rectangle to more clearly see the area of the screen that you’re selecting.

Beta 2 includes just a couple bugfixes over beta 1, which are KDE compatibility (at least the beginnings of it, I still need some testers for this) and properly saving and restoring the save directory, if you choose to not delete images after upload.

More on the Evo

I’ve now had my new toy for a little over a month. Shortly after my last post, I took the plunge and rooted my Evo and have since been playing with some of the different ROMs that are available for it. For the most part, I’ve been using Fresh Evo, which is currently in version 0.5.3, with a 1.0.0. beta in limited availability. Fresh Evo let me get rid of a large amount of HTC’s Sense UI, which, while pretty, slows the phone done a fair amount. I’ve since moved on to a new, more stock Android ROM (Evo-NonSense), which is almost fully AOSP components, except for the Camera app, which is needed to support the dual cameras. I’ll give Fresh another whirl once 1.0.0 is released.

HTC EVO 4G

A little over a week ago, I picked up my first Android phone, the EVO 4G on Sprint. For a year before that I was using a Palm Pre, so I thought I’d take some time to do a comparison between the two.

Hardware:

In terms of hardware, the phones couldn’t be much more different. In terms of size, the EVO is considerably larger with a 4.3″ screen rather than the Pre’s 3.1″. Screen resolutions scale appropriately, with the Pre running on 320×480 and the EVO on 480×800. The Palm Pre is a vertical slider with a physical QWERTY keyboard, while the EVO uses a soft keyboard. The Pre has a 3MP camera while the EVO features two: an 8MP camera on the back and a 1.3MP on the front for video calls.

At first I thought the EVO’s massive size would be a problem, but after a day or so of use it felt perfectly natural to hold and fits fine in my pockets. Also on the outside of the device, the EVO features a kickstand, presumably for when watching video, as well as an HDMI port for outputting to a TV, which I have yet to test.

Internally, there’s a lot of difference as well. The Pre runs on a 500MHz TI OMAP processor, where the EVO has a 1GHz Snapdragon CPU. The RAM has doubled as well, from 256MB to 512MB (although due to a software bug, Android 2.1 can only address the first half of that, this is supposedly fixed in 2.2, as well as some custom ROMs). The Pre has 8GB of internal memory, while the EVO has 1GB along with an expandable 8GB via micro SD.

And of course, there’s the Sprint 4G radio in the EVO, but since Louisville isn’t even on the roadmap for that yet, I’ve been unable to test it.

The closest thing I have to a benchmark utility for these phones is Sunspider, so here goes: (single run each, both on WiFi, totally non-scientific, lower is better)

Palm Pre: 30480.0ms

HTV EVO 4G: 13165.8ms

and, for fun:

Dragon (Core i7, Ubuntu, Chromium): 389.2ms

Software

This is what was most appealing to me about the new phone. The Palm Pre ran on Palm’s webOS which, while nice, doesn’t have the same development community that Android does. The EVO is running on Google’s Android operating system, currently the latest (stable!) version, 2.1.

Surprisingly, there were actually a good number of software elements that I miss from the old phone. First up is cardview, the method that Palm uses to handle multitasking which basically puts each app in its own “card” that can be switched between and then tossed off the screen to close. Android, on the other hand, leaves most apps running in the background after close, and instead of cards, a long press of the home key brings up a list of the six most recently used apps (whether they’re still running or not). If you want to access a running app older than that, you’ll have to find it’s icon and launch it that way.

Another oddity in Android is the way apps seem to “stack.” For example, if I’m in the Reddit app and I click on a link, it opens in the web browser. However, if I now hit the “back” key, I’m taken back into the Reddit app. In situations like this, it makes sense, but I’ve run into a couple of cases where I’m taken between apps unexpectedly by the back button. In general, apps don’t seem as contained as they did in webOS.

Another small touch that I miss from webOS is screen rotation. While Android will rotate the screen automatically, it does so instantly with no sort of animation for the transition, where Palm had the screen rotate and expand, which gave it a nice appearance.

Synchronization with web services is just as good if not better than on webOS, especially if those services are run by Google. I was already using Google Voice to manage my voicemail, but now I’m moving towards using it for more, since I have a good level of integration with my phone. I also now have proper support for Google Latitude without having to hack in support as well as a much more full-featured Maps application in general, with Street View and Turn by Turn Navigation.

The amount of available software for Android is one of the big reasons I decided to switch to the platform. Apps that I’ve found without equivalent on webOS include: Dropbox (for accessing my cloud-stored files), Layar (an augmented reality app that for now is more of a toy since I’ve yet to figure out how to use it properly), Mint (frontend to Mint.com, a financial management service), Shazam (for identifying music), and XBMC Remote (lets me browse and control playback for my media PC). Upcoming apps seem to include Audible (I’ve already played with the beta client), Kindle, and Netflix. And that doesn’t even take into account all of the Google services I was unable to use before, like Earth, Goggle, Latitude, Buzz, Sky Map, etc.

Since the Android SDK is based on Java rather than Palm’s Javascript based solution, apps seem to have better control of the hardware, which allows for some of these cooler apps to exist. One of my favorite features is the barcode scanning ability, which allows you to, among other things, install apps from the web by scanning a barcode off your computer screen.

I’ve yet to get into running custom ROMs on my EVO, but I’ve been following the development pretty closely and will probably give one of them a spin in the near future, especially if they can get Froyo working well.

A look at Lookit 0.3

Well, maybe “look” isn’t quite the right word, there’s not a lot of GUI to look at. However, I’ve spent a large portion of the day figuring out how to get around two of the more annoying issues in the current version, specifically, non-compositing window manager support and drawing the selection rectangle.

The new solution involves grabbing the mouse directly rather than letting the input be grabbed by an invisible window. That alone improves the application dramatically by allowing it to run without a compositing manager. With some luck, this will help with multimon support as well. Drawing the rectangle requires some lower level code, though, specifically using Xlib instead of GDK.

If there’s anything that you want to see implemented in the next release, make sure it’s mentioned on the Bug Tracker.

New Look

Don’t worry, you’re in the right place! Unless of course, you weren’t trying to find this blog, in which case you’re in the wrong place. I’m tinkering with the layout looking for something cleaner.

Lookit 0.2 Released

It’s a new project, and I’m moving fast. I just pushed Lookit 0.2 to bzr as well as the Lookit PPA. Changes include support for Imgur as an upload option, a warning when using a non-compositing window manager, Ubuntu Mono icons, and a few minor bugfixes. As always, *please* report any bugs to http://bugs.launchpad.net/lookit.

EDIT: I’ve moved to github, report bugs here: http://github.com/zachtib/lookit/issues

Lookit 0.1 Released

After around two weeks of coding in my freetime, I yesterday uploaded the first public release of my screenshot utility, Lookit. Unlike my bash script, this version has a proper GUI and no longer relies on external utilities like scrot and xclip. Instead, everything is done in native Python.

EDIT: Ubuntu 10.04 packages can be found on the project’s page on Launchpad: http://launchpad.net/lookit.

Other development is done at github: http://zachtib.github.com/lookit/

Building a GUI for my screenshot uploader

Today’s project goes back to what I was working on a couple of days ago with my screenshot upload script. I’ve been building a GUI with PyGTK to manage connections to the server that hosts the screenshots. I made a lot of progress today, learning to use the new GtkBuilder libraries and also the AppIndicator framework in Ubuntu 10.04. I’m hoping to have something out in the next couple of days.