Last Updated: April 27th, 2011
Motorola has had a dark past when it comes to bootloaders. Apart from a couple exceptions (most notably, the XOOM), all of the major Motorola devices have had locked bootloaders, and thus, Android customization enthusiasts have been shut out from such tweaks as custom kernels.
Recently, there has been quite an outcry directed at Motorola and their bootloader policy, in the form of petitions and hijacked polls, and it looks like they have heard users' requests.
Last Updated: June 8th, 2011
Let's face it: as Android users, we like options. One of the greatest things about this platform is the insane level of customization possible, especially if you don't mind getting your hands a little dirty. With some readily available tools (all of which are extremely free) and the proper knowledge, you can make your android phone do almost anything you could possibly want and make it look however you want. What we'll be talking about today is the bootscreen.
Last Updated: February 4th, 2012
In an investor call today, Motorola's CEO Sanjay Jha revealed two interesting tidbits: first, that the ATRIX 4G's Webtop app and accessory are going to be made available for more Motorola devices in the future, and second, that Gingerbread updates for all of Motorola's high-end Android devices are in the works.
On the former, it may be hard for some to get excited about more Webtop action, as the ATRIX 4G's has been dubbed overpriced and "gimmicky." However, it's important to realize that if Moto plans on continuing to offer Webtop accessories and software, they will also continue improving them.
Last Updated: January 28th, 2011
Though Google may have fixed two infamous SMS issues via the recent Android 2.2.2 and 2.3.2 updates, it appears at least one bug is still unconquered. Namely, some users are reporting that when they tap on the "New Message" alert in the notification bar, all their SMS conversations get deleted.
Our tipster experienced this on his HTC Desire Z, but he tells us that two of his friends - one using a Nexus One and the other on a Galaxy S - have come across the same bug.