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.
Continue reading “Android adds A2DP, AVRCP Bluetooth and more”
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.
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).
[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.
Google has been trickling out info about what they’re actually fixing in the G1 firmware updates. Before RC29, users were able to bypass the phone lock using safe mode. RC29 also brought WebKit up to date, presumably patching the bug [Charlie Miller] found. RC30 takes care of root console problem. Unfortunately there are very few details as to what or how particular items were broken. This release method leaves much to be desired; having the official Android Security Announcements group be the absolute last place to get security news is asinine.
[Jay Freeman] has a rather exhaustive tutorial on how to set up a Debian environment on your T-Mobile G1. The first major issue with this is that getting root level access through telnetd is being patched. It certainly is a security issue that needs to be fixed, but a user shouldn’t have to root their own phone to begin with. While the G1 comes with some Linux tools, they’re limited. [Jay]‘s goal was to create a familiar Debian environment on the phone. It takes a few tricks, but if you’re familiar with the command line, you shouldn’t have any problems. Debian already has ARM EABI support, so creating a working image isn’t a problem. The image file is stored on the SD card and mounted using the loopback device. The G1′s kernel has module support turned on, so [Jay] created an ext2 and unionfs kernel modules. [Benno Leslie]‘s Android version of busybox is used to perform the actual mounting. Once mounted, you just need to chroot into the environment to start playing with native Linux apps. [Jay] takes this a step further by using unionfs to make the Android and Debian environments share the same root. This is really a great how-to and it’s nice to know that modules can be added to the kernel.
The G1 ‘execute every command you type‘ bug naturally spawned ‘rm -rf /’ jokes. rm is the Linux command for deleting files. The -r and -f flags will cause it to remove files recursively and ignore confirmation. Executed as root it will annihilate the entire filesystem. Won’t it? [Jon Hohle] decided to test exactly how destructive the command was to *nix systems. How functional would the system be afterwards? He tested it side by side with the Windows equivalent, both ‘format c:’ and ‘del /F /S /Q’. He wanted to see what protections were available and what would be left working. Linux ended up completely broken while Windows, thanks to file locking, actually shutdown cleanly… and never came back. Some OSes, like Solaris, refuse to run the command ‘rm -rf /’ to prevent accidents.