With the ability to get root access to some of these new powerful pieces of hardware we call cell phones, we’re a bit surprised we haven’t seen more interfacing with external hardware. Here’s an example of some rudimentary connections between an Android G1 and an Arduino. To do this, you must have your G1 rooted, have the Android SDK installed, and then a custom python program running.  There is also a simple level shifter from 3.3v to 5v necessary for the connection to the Arduino.  You can get all the details from the instructable. They’ve documented the process quite well adn we’re excited to see what kinds of stuff people come up with.

[Matthias] from Intuity Media Lab put together a nice bit on controlling office lights with XMPP from his Android phone. In the article, he explains the components involved in the project, why he chose XMPP, and lists everything you need to replicate it. The project makes use of a wide variety of tools and libraries, weaving together code from multiple languages to achieve its goal. Overall, his project is a welcome change in a world full of Twitter-based solutions.

It’s been many months since the T-Mobile G1 was initially rooted. In that time, the process has been streamlined and tools have been built to make it much easier. Having a rooted phone has become even more desirable with the recent release of the 1.5 firmware that includes an onscreen keyboard along with other improvements. Having a rooted phone means you can do tricks like setting up a 3G/WiFi bridge. [Taylor Wimberly] has written a guide to help you easily root your G1 without having to go digging through forums for software bits. The process starts by using [Mike Moussa]‘s rooting app to revert the phone to the RC29 build. You then use the “Android stupidly executes everything you type” exploit to launch telnetd and upgrade the bootloader. After that, the upgrade process is fairly easy. You just flash a new baseband and build. Once you’ve got your new custom firmware, you can do future updates using an app from the Android Market. We recently updated our Android Dev Phone 1 to 1.5 and haven’t had any issues.

[photo: tnkgrl]

For those wanting to do some hacking  or kernel debugging on their G1, [macpoddotnet] shows how to make a serial to USB cable. He gathered enough information on the Android platform google group to be able to piece something together. He’s using a USB 2.8V serial TTL level converter, and lists several available that should work. Looks like a pretty easy build.

AndroidAndMe is running a bounty program for Android applications. Users can request a specific application and pledge money to be awarded to the developer who delivers the functional app. [Alec Holmes] just fulfilled the first request by creating Torrent Droid. You can use the app to scan media barcodes and then download the related torrent. It uses the phone’s camera to capture the product’s UPC barcode (similar to Compare Everywhere‘s price lookup) and then searches major torrent sites like The Pirate Bay to find a copy that can be downloaded. After getting the .torrent file, the app can submit it to uTorrent‘s web interface for remote downloading. The app will be released later this month and you can see a screenshot tour of it on Alec’s blog. It’s doubtful that an application like this would ever clear Apple’s App Store approval process.

[via TorrentFreak]

[ghostwalker] has put together instructions for running X11 on your Android device. This means you can run a full-blown Linux desktop environment on your phone. It requires you to already have a Debian shell on the phone, which we covered earlier. Instead of having to come up with a custom display driver, it’s hooked to a VNC server. You can connect to it using an Android VNC viewer on the phone or via any other VNC client. The how-to suggests either IceWM or the even lighter-weight LXDE for a window manager. You could potentially install Gnome or KDE, but we’d be surprised if it was any faster than dog slow. Let us know if you have any success with this and what you think the best use is.

Many G1/ADP1 owners have been using the app Tetherbot to get internet access on their laptop via USB to the phone’s data connection. The app relied on the Android Debug Bridge to forward ports. It worked, but people wanted a solution better than a SOCKS proxy. The community figured out a way to create a properly NAT’d connection using iptables and then [moussam] rolled them up into easy to use applications. There’s one for setting up a PAN device on Bluetooth and another for adhoc WiFi networking. It requires you to have root on your phone, but hopefully you’ve achieved that and are already running the latest community firmware.

[photo: tnkgrl]

When we first saw [Jeffrey Nelson]‘s G1 based robot we immediately wondered what the transport for the controls was. The G1‘s hardware supports USB On-The-Go, but it’s not implemented in Android yet. It turns out he’s actually sending commands by using DTMF tones through the headphone adapter. The audio jack is connected to a DTMF decoder that sends signals to the bot’s Arduino. He wrote client/server code in Java to issue commands to the robot. You can find that code plus a simple schematic on his site. A video of the bot is embedded below.

[via Engadget]

[Luke Hutchison] has come up with a rather clever hack to get multitouch support on the G1. He wrote a patch against the Synaptics touchscreen driver. When two fingers are placed, the driver reports the x/y of the midpoint and a radius for the size field. If only one finger is used, the size is reported as zero. The nice thing about this approach is that it’s backwards compatible; the extra data will be ignored by current apps. Unfortunately, Google’s Android team says that if multitouch is ever added, it would identify individual fingers and definitely not using this method.

[via ABN]

[photo: tnkgrl]

It’s the season of gift giving. Did you get anything interesting/hackable? What will you work on next?

We gave ourselves an Android Dev Phone 1 (ADP1). We hadn’t really considered getting a G1 until the ADP1 was announced… It’s actually a lot of fun to use as our primary phone. Our favorite app so far is connectbot, the SSH client. The interface is really smart, way better than all of the iPhone clients.

What did you get?

In our Dev Phone 1 excitement last week, we somehow overlooked phoneWreck’s teardown of the T-Mobile G1. The complex slider mechanism is certainly worth looking out. One of the major oddities they point out is the inclusion of two vibration motors. One is mounted next to the SIM on the mainboard. While the other is mounted in the frame next to the earpiece. We wonder what was gained/solved by using two. The phone also includes a digital compass module. We’d like a more detailed explanation of how the Xilinx CPLD is used. From this article in 2006, it seems HTC uses them to generate custom clock signals and switching off devices for power management.

While working towards open-sourcing Android, the team continued to work on new features in their own private development branch. These have now been published publicly in the “cupcake” branch. There’s a lot of interesting new features and bug fixes included. We’ve got a rundown of many of the significant additions after the break.

The A2DP and AVRCP profiles were both added to the Bluetooth stack. This means support for stereo headsets and remote control. Dial Up Networking wasn’t added, but preliminary work was done on USB Gadget Framework support, which means future devices could appear to the host device as just an ethernet interface.

The browser has been bumped up to the November release of WebKit with the optimized JavaScript engine SquirrelFish. Copy/paste in browser and a 5x draw speed improvement were also added. The trackball now does accelerated scrolling.

Hardware accelerated video recording and playback, an often noted oversight in the initial T-Mobile G1 release, finally show up. A framework for an on-screen keyboard and predictive text are being worked on. Android lets you run background processes and users will be pleased to know there’s a process manager now. Finally, a new Linux 2.6.27 kernel and the least explained addition “basic x86 support” round out the branch.

While there are many good improvements here, there is no indication as to when G1 users will see them or when Android Dev Phone 1 (ADP1) owners will be able to build the release themselves. [Disconnect] points out that there were some other gems included in the branch that aren’t in the announcement like mounting an encrypted e2fs volume which could enable installing apps on the SD card.

[photo: tnkgrl]

[via GotOnTheInter.Net]

Google has new program to sell Android phones directly to developers. The Android Dev Phone 1 is both SIM-unlocked and hardware-unlocked. SIM-unlocked means you can use it on any GSM carrier you want. Hardware-unlocked means you can run any system you want on the phone, not just officially signed ones. No more need to worry about security patches taking away your root access.

The device is $399. You will need to purchase it through the Android Market as a registered developer (a $25 fee). We wonder how long before the unsigned bootloader starts getting flashed to T-Mobile phones.

Two new Android phones have surfaced recently which may prove just as friendly: the Kogan Agora Pro and the QiGi i6.

UPDATE: While shipping is free in US, it is incredibly expensive everywhere else. Yes, we bought one.

[via Techmeme]

[photo: tnkgrl]

The target release date may be over five months out, but the Ubuntu team is already pushing the first alphas of Jaunty Jackalope out the door. The new release is not for the weak and is intended solely for people who want to vet bugs and contribute to the project. The release is designed to bring Ubuntu back in line with Debian. One of the areas they’re working on is the ARM port (we saw the Debian version on the G1).

[photo: Kordite]

[via Download Squad]

[RyeBrye] has been trying to get multitouch working on the Android based T-Mobile G1. He hacked the Synaptics touchscreen driver so that it would dump raw event info to a character device. The demo above is using example code from Google for a fingerpaint program. Polling the device is not the fastest method, but [RyeBrye] just wanted to get a demo out there to prove it could be done.