More and more smartphone manufacturers have been moving towards on-screen buttons, with Google really pushing for it over the physical button alternative. However, there are still a few OEMs (we're looking at you, Samsung) that have preferred to keep things a bit more traditional. Tell us which way you prefer and why.
Porting Android To The Good Ol’ HTC Universal
Perhaps the young ones won´t remember the great HTC Universal, the first 3G device worldwide, released back in 2005 with an unique form factor similar to a micro laptop. Well, the Universal still has a very active community and from it we´ve found that Android is on the process to being ported to it. XDA members notime2d8 and orzech2111 are leading this project that started almost one year ago.
I have spoken with one of the developers involved and this is what is happening now:
What is working so far:
– SD card slot
– Max1587a voltage regulator
– Asic3 Buttons
– Automatic screen rotation
– Usb host
– Adb and Usb mass storage
– M24C08 Eeprom
– Keyboard and button backlights
– Support for RTC8564 realtime clock
– Led’s – Red, Green, Blue, and vibrate
– AC Charging
– Phone -working: sim contacts, text messages, signal strength, voicemails, receiving and making calls.
– Audio – no input from mics
– Camera’s -not working in android a camera HAL driver is needed.
– Power Management
-Suspend and Resume
– Running from NAND
– Easier install method besides using and extracting rootfs
— Data -3g or GPRS
– Devices with only 64mb of ram
– Having no graphics accelerator
– No driver for docg3 NAND
What we can expect in the future:
– Donut builds for 64mb devices with more hardware support such as sound and phone functions.
– Cleaner and faster kernels.
– More memory efficient Android builds.
We must remember that Universal has some hardware limitations as it came with 64MB of RAM, but things are moving quickly and in the right direction.
Developers out there, please step in and give a hand to your fellow Devs on this titanic project!
Originally posted by notime2d8
You will need a spare SD Card of at least 250 MB to try this. You have to create the following 2 partitions on your SD Card.
If you have a larger card you can increase the EXT4 partition freely, which will be the root partition.
/dev/sdb1 – 40 MB FAT32
/dev/sdb2 – 150 MB EXT4
The following files included in the zip file below should be downloaded and copied to your FAT32 partition on the SD Card.
* default.txt (HaReT configuration)
* zImage (the kernel)
The following file is to root filesystem. You should download and extract it in the EXT4 root partition on the SD Card (mmcblk0p2).
Link to cmod froyo rootfs: (Link)
Link to other rootfs: (Link)
Use the following command to extract
Continue to the Development thread.
Special thanks to notime2d8 for answering my questions leading to a great updated list
Want something on the XDA Portal? Send us a tip!
While there are frequent unexplained changes and pushes to Google's AOSP repositories, an interesting-looking new branch has been pushed out recently, called "master-soong". Taking a look at the changes made to the manifest repository (which is used to specify the repositories to be downloaded when building Android), it appears there are some new repositories making an appearance. Of note here are new prebuilt repositories for Go, and Ninja. Go is a programming language, created by Google, which compiles to produce...
There already are many solutions on the Google Play store if you want to send a link to one of your devices -- but what if you wanted to do it quickly without having to install any software or logging in to a website on the recipient end? Most apps require you to do either or both, which can be a hassle (or even a security risk) in some cases. Luckily, XDA Forum Member wyemun has developed CaastMe. Inspired by...