We’ve often wondered what kind of hardware the giant of the internet, Google, used to handle it’s data. They’ve recently revealed what their main workhorses are. It’s a custom motherboard made by Gigabyte with two processors, and eight RAM slots. The main point of interest on these is the fact that each server and piece of network equipment has it’s own battery backup. This may add a little money in the initial cost of the unit, but apparently it is a much more efficient way of handling power. Be sure to click over to the site and check out the shipping container setup that they use. Each container has 1,160 servers. They aren’t the only ones using this method. Microsoft has adopted it for their newer facilities and Sun has done some extensive testing on how these portable facilities handle earthquakes. You can see the quake test after the break.
Continue reading “Googles servers revealed”
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.
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.
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.
Continue reading “Forknife, Android G1 controlled robot”
[ghostwalker] dropped in on our previous Debian Android post to let us know that he had streamlined the install process. The first time around, it quickly became difficult to complete the process because firmware updates had taken away root access. Hackers have since figured out how to downgrade from RC30 and install BusyBox. All you need to do to put Debian on your phone is download the package from [ghostwalker] and then run the installer script. This isn’t technically a port since Debian already has ARM EABI support. What would you run on your phone if you had access to the entire Debian package tree? A video of Debian starting up is embedded below.
Continue reading “Debian on the G1 once again”
[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.