February 14, 2013 By: Samantha
Sony’s Small Apps debuted on the James Bond’s very own Xperia T, allowing the superspy to do some quick and simple maths calculations and jot down some quick reminders among other functions while having other applications running simultaneously. Useful to many Xperia users who have had received ports to their Xperia devices running stock ICS firmwares such as the Xperia Arc, Xperia P, and Xperia Ion, Sony Small Apps have also been ported to devices from any manufacturer running CyanogenMod versions 9 and 10 and Paranoid Android version 2.55.
Ported by XDA Forum Member c3ma138, they allow users to have floating applications running over other applications concurrently. Installation is relatively simple, requiring users with root access to flash the ROM-respective flash file in recovery mode on their devices and then installing an app called ‘SLauncher’ once flashing has finished and phone rebooted. Tested on a Samsung Galaxy SII running CyanogenMod 9 and 10, and a Sony Xperia S running CyanogenMod 10, c3ma138 assures that any Android device, regardless of manufacturer, running the compatible ROMs will be able to enjoy Sony’s Small Apps.
This is great news for CyanogenMod 9 and 10 and Paranoid Android 2.55 users, as they don’t often see ports of manufacturer-specific features. For more details on the port, please check the original thread.
December 12, 2012 By: Former Writer
Even the less popular devices need some lovin’ too. The Samsung Rugby Pro and Samsung Rugby Smart aren’t the most well known smartphones on XDA. However, that hasn’t prevented developers from hacking then and releasing some good stuff. Now, the Rugby Pro has official TWRP, and the Rugby Smart has CM9 and CM10 ports.
XDA Senior Member kemonine96, who has done much work with XBMC, has released various treats for the two devices. The most recent offerings are TWRP for the Rugby Pro, and CM9 and CM10 for the Rugby Smart.
For the Rugby Pro, it’s been accepted by Team Win as an officially supported TWRP device. That’s pretty good news for a lesser known device. With TWRP, users can flash whatever they want in style. For more info, check out the Rugby Pro thread.
The CM9 and CM10 ROMs are both still in their alpha stages, but have a surprisingly small number of things wrong with them. Currently, CM9 has the following issues:
Display auto-brightness toggle — Is not possible, the Rugby Smart lacks a light sensor
2G data only toggle does nothing
No device serial number shown — prop:ril.serialnumber
And for CM10, the issues are as follows:
SD Card swap (CM10 Limitation)
So while there are issues, all of the biggest features like camera, Bluetooth, and WiFi actually work. So these could be used as daily drivers. Both ROMs are being actively worked on, so issues will be fixed in future releases.
November 20, 2012 By: Conan Troutman
You may remember we recently talked about the latest addition to CyanogenMod’s own suite of applications, the CM File Manager. This now sits proudly alongside the collection of other unique apps such as CM messaging and Apollo music player.
The file manager itself is pretty straight forward, and does exactly what you’d expect it to. The interface is clean and intuitive, all the functionality you would expect is there. And of course, you aren’t limited to simply browsing through the SD card. Full root access is supported. The only problem that some people have faced with this latest addition, however, is that the application was specifically made for use with CM10 and wasn’t compatible with older versions. That’s no longer a problem, thanks to XDA Senior Member kemonine96, who modified the app to work on ICS-based CM9 ROMs.
Installation couldn’t be simpler. Just push the modified APK to /system/app, and off you go. Be warned though that NFC might not work properly if at all with this version, due to API compatibility issues. So if you’re running a version of CM9 and would like to give this a shot, head on over to the application thread for more info.
The HTC Explorer was never one of the most popular smartphones to grace the pages of XDA. The Explorer is a low end device that was released in late 2011. With only a 600 MHz processor and 512 MB RAM, it was never going to grab any headlines. This is what makes the recent high level of development activity on the device all the more impressive.
First up, XDA Senior Member oblikas brings us TWRP. The popular touchscreen driven recovery system allows you to do much more than flash a ROM. While it does work as intended, at version 188.8.131.52, it’s not updated to the latest version at the time of writing.
Next up, XDA Senior Member derefas has managed to port HTC Sense 4.0 to the Explorer. Given that the device originally shipped with Sense 3.5, this is an exciting port for Explorer owners, giving their device a complete refresh. The only listed known issues with the ROM are occasional USB issues, Bluetooth, Wifi and Superuser, though these last three issues have been fixed by the dev and will be working in the next ROM update.
Further to this, XDA Senior Member sam_0829 has impressively ported Sense 4.1 to the device, using the HTC Desire HD as a donor. The main functional parts of the device such as radio, sound and camera are all working, but as the Desire HD has a much higher screen resolution, a large amount of the ROM needs to be re-sized to fit the Explorer’s 320 × 480 screen. The dev has created a thread in the hope that others will be able to provide help in re-sizing, so that a usable ROM can be put together.
If Sense isn’t your cup of tea, and you prefer a more true Android experience, there are a number of ROMs available that are more suited.
XDA Senior Member sakindia123 has been busy, and brings us unofficial builds of both Cyanogenmod 9.1 and 10. The Ice Cream Sandwich based Cyanogenmod 9.1 ROM is fully functional with no known issues. The Cyanogenmod 10 ROM is almost completely working, with the only issues being with video decoding and voice search.
Another non Sense option is an unofficial AOKP ROM, built from source by XDA Recognized Developer flowish. This ROM has no known issues and of course has all the standard AOKP features.
Finally, if you haven’t been hiding under that rock of late, you’ll no doubt have heard of PACman ROM, an amalgamation of the best features from Paranoid Android, AOKP and Cyanogenmod 10. This port of PACman ROM is brought to us, again, by XDA Senior Member oblikas. Given the ROM has only just been released and is in an alpha stage, there are a few issues at present, including the camera, audio and USB mass storage.
There are of course many other custom ROMs available in the HTC Explorer Development forum. This article is just intended to highlight some of the more recent development taking place.
If you want to try out any of these ROMs, check out the relevant ROM thread:
October 10, 2012 By: Former Writer
The last time we brought you news on the Samsung Galaxy Blaze 4G, it was getting root and recovery. Since then, developers have been working to make it a more fun to device for flashers. After a few months, the Blaze 4G not only received CM9 but also CM10. On the same day, no less.
XDA Senior Member erikmm ported CyanogenMod9 to the Blaze 4G. Despite it being a first release, it is perfectly stable with the only known issue is that rotation is a bit laggy. Anyone looking for AOSP-based ICS on the Blaze 4G now has a good ROM to try out.
For unofficial CyanogenMod10, XDA Senior Member dr4stic did the heavy lifting. Unlike its CM9 sibling, CM10 does have quite a few issues. This includes some random rebooting, CM Updater freezes, and a reboot bug that is triggered by notifications due to a non-CM driver being used for the Blaze 4G buttons. Most of these issues are slated to be fixed in future updates, but for now this probably isn’t daily driver material due to the reboots.
Consequently, the CM10 port to the Blaze 4G also works on the Samsung Galaxy Exhilarate. Also developed by dr4stic, the ROM just needed a couple of kernel tweaks. Presumably, the same number of things are wrong since it is essentially the same ROM for both devices. XDA Forum Member ktempleton is maintaining a thread specifically for the Exhilarate folks here.
Just a short time ago we brought you news that the Acro S was rooted. As the only Android phone out there that can swim, that’s great news. However, that is not all that developers had in store.
With the device rooted, developers could get started on creating the things that make XDA go ’round, including ROMs, kernels, hacks, mods, and others. As a result, the Sony Xperia Acro S now has CyanogenMod 9. Not impressed? Okay, it also received CyanogenMod 10 on the same day.
XDA Recognized Developer FXP, who regularly brings CM goodness to Xperia devices, released both builds. There are some issues with the unofficial CM10 build related to the camera, and the known issues on the CM9 build include:
Known issues being worked on:
* The recovery on first attempt fail to mount /system
* ALS is disabled (broke PowerManager)
To better keep track of issues, FXP has provided a bug tracker. Aside from the issues reported, users have predominantly good things to say. And for many, the ROMs can be used as daily drivers. For more info, check out the CM9 thread or the CM10 thread.
A few days ago, we reported on the Motorola Droid impressively receiving a working Jelly Bean ROM. The Droid’s GSM successor, the Motorola Milestone 2 has now followed suit and been given a number of recent updates in the form of CyanogenMod 9 and CyanogenMod 10.
XDA Senior Member tezet started an Alpha version of CyanogenMod 9 several months ago in order to give users a taste of CM9 on their Milestone 2. Though labelled an alpha build, a large number of the standard functions of the phone are functional. However, video functions still remain problematic.
XDA Senior Member sfc3001 has taken tezet’s ROM as a base and continued the CyanogenMod 9 development with his own creation. Also labelled an alpha build, this ROM has only a small number of outstanding issues that are by no means show stoppers. These include WiFi tether and phone encryption.
Taking it one step further, tezet has also produced a Jelly Bean-based CyanogenMod 10 ROM for the Milestone 2. Development is very much active, with regular updates. Amazingly, there are no major issues that limit the ROM’s functionality.
These custom ROMs, as with all others, are a testament to the great work the developers here on XDA put into keeping these older devices alive with much newer flavors of Google’s Android operating system.
If you would like to CM your Milestone 2, take your pick of these threads:
Way back in 2009, HTC released their third Android smartphone, the HTC Hero. The device shipped with Android 1.5 (Cupcake) or 2.1 (Eclair). Yes, that’s how long ago it was! In it’s day, it was a very popular device here on XDA, attracting a good number of developers. But as with all older devices, it has since slipped by the wayside and has become somewhat forgotten. For most people, that is.
Within the last few months, both the CDMA and GSM versions of the Hero have received both Ice Cream Sandwich and, more incredibly, Jelly Bean custom ROMs added to their arsenal.
For the CDMA version, XDA Senior Member tvall brings us Ice Cream Sandwich based CyanogenMod 9. Development has slowed of late, but the ROM appears to be functional, with only camera and USB mass storage not functioning.
CyanogenMod 9 on the GSM Hero is brought to us by XDA Senior Member jordfaz. Again, there are a few minor issues, such as GPS and hardware acceleration, as well as some minor issues with the camera. Despite this, the ROM is otherwise functional.
XDA Senior Member Shelnutt2 has gone one step further and has brought Jelly Bean to the CDMA Hero in the form of CyanogenMod 10. Of course with builds of this nature, there are a number of known issues, such as audio, camera and hardware acceleration, but these are being worked on by a number of members in the ROM thread.
Not to be outdone, the GSM Hero also has CyanogenMod 10 thanks to XDA Senior Member jordfaz. Based on the CDMA version mentioned above, the same known issues apply. The ROM is an alpha build and should only be flashed if you wish to help with development or provide feedback.
If you’re an HTC Hero owner and want to try out one of these newer Android flavors, head over to one of the development threads:
August 30, 2012 By: Ian Stacy
While CyanogenMod 10 becomes the norm for many cutting-edge device, it appears that CyanogenMod 9.1 still has a trick up its sleeve when it debuts. In an industry first, CyanogenMod (a community-maintained Android ROM that isn’t directly affiliated with the AOSP) has partnered with NFC cloud-based payment company SimplyTapp to produce a new method of paying for real goods and services with NFC-capable devices.
Much like Google Wallet, Google’s NFC payment system, SimplyTapp allows users of NFC capable devices (flashed with CM 9.1) to store payment method information in the cloud. By installing the app and signing up for a card ($0 to $5 depending on the type of card, with fixed amount gift cards, re-loadable cards and some local store cards available) your device can be used in a similar fashion to a debit or credit card but with the added simplicity of waving your NFC capable device to make a payment and the added security of storing your payment information in the cloud until needed.
According to the announcement at the Cyanogenmod homepage, enhancements to the Ice Cream Sandwich NFC stack were necessary to make this service work, and those changes have been implemented in the upcoming CyanogenMod 9.1 release. CyanogenMod 10, which is based on Jelly Bean (Android 4.1), will eventually see Tapp as well, but not until changes to the AOSP Jelly Bean tree slow down.
The announcement also mentions that while CM 9.1 will not contain new features, it ushers in a host of bug-fixes. This also serves as an indicator that new features will no longer be introduced to CM9.
August 13, 2012 By: Haroon Q. Raja
Great news, CM lovers: After months of coding and tweaking, the CyanogenMod team has released the stable version of ICS-based CyanogenMod 9 for all supported devices on the official CM mirror network. The nightly and release candidate CM9 builds have been around for a while and were already quite stable, but this step marks the final release of the ICS-based builds.
Here is a list of devices currently gettign CyanogenMod 9:
Along with the release comes the announcement that CM9 will not be further developed, in favor of Jelly Bean-based CyanogenMod 10. Work on CM10 started as soon as source was released not too long ago. CM9 will only get critical bug fixes in the future, and all the devices that support it should support and officially receive CM10 in the future.
With the title of “Worlds Longest Name for a Smartphone” already in the bag, the Sprint Samsung Galaxy S II Epic 4G Touch (SSGS2E4GT) has become known as the SGS2’s Red-Headed Stepchild. Back when Samsung released the US variants of the SGS2 i9100, the E4GT was the first to appear. However, it has taken the longest to receive official ICS from Samsung. Coupled with taking longer to receive official CM9 love, and you have a device that seems to have been forgotten.
XDA Recognized Developer darchstar has done a great job, with the help of the rest of Team Epic CM, in continuing to work on CM9 for the E4GT without much help, naturally, from Sprint and Samsung. After months of leaks, Sprint started rolling out the FF18 ICS OTA and Samsung released the kernel source—two essential elements in getting to an official CM9 for the device.
Now that Team Epic CM has had a chance to look over the published code, they have posted a status update on their team blog:
- Team Epic dev mkasick has been working on porting kexec support for the source kernel similar to the Gingerbread based directbootCWM kexec kernel released earlier.
- Team Epic dev nubecoder has been working on an FF18 temp boot utility similar to the EL29 temp boot released earlier. This will allow for prl and profile updates, recalibrating sensors, device activations, gps locks, etc, while on a CM build for those who need it.
- Team Epic dev chris41g has also been working on getting the source kernel booting and integrating it into the CM build process. He has also updated the custom recovery from CWM5 to Koush’s latest, CWM6. Along with that, the emmc brick bug has been patched making it safe to wipe, flash, backup and restore in.
July 20, 2012 By: Jimmy McGee
Jordan is back today, talking about Jelly Bean, Samsung Galaxy S III, and other news from the XDA Portal. Jordan covers news on official CyanogenMod 10 previews for the International Galaxy S III and its US variants. Jordan talks about the two stories regarding Verizon, and the locked bootloader on their Galaxy S III. Jordan also mentions Erica’s video on Easy UMS.
In Jelly Bean news, Jordan mentions the Jelly Bean alphas for the HTC HD2, Sensation and Amaze 4G. Also, getting Jelly Bean is the Galaxy S II. Jordan wraps up the video with a mention of the marriage proposal the XDA way story.
While the XDA Portal has seemingly been Jelly Bean, Jelly Bean, JELLY BEAN as of late, there is still much development work to be done on finalizing and perfecting builds based on Android 4.0 Ice Cream Sandwich. After all, many would rather have a bullet-proof daily driver than an admittedly awesome preview build, which could potentially be a bit buggy.
As such, the CyanogenMod team has now released CyanogenMod 9 Release Candidate 2. Users can expect RC2 to be quite stable. It also adds support for new devices. As described on the CyanogenMod blog:
This release serves to stabilize CM9 as a product that you’d let your mom use, as well as add support for the following devices:
* Samsung Galaxy Tab 2 10.1 (all variants)
* Samsung Galaxy SII on AT&T – Skyrocket
* Samsung Galaxy SII on T-Mobile – Hercules
* Samsung Galaxy Note on AT&T
* Samsung Galaxy SIII – i9300 (International GSM model)
In addition to the new devices, those which were previously supported in earlier CM9 builds retain official support. Currently supported devices, courtesy of a discussion thread created by XDA Forum Member safariking are:
Cyanogenmod 9 RC2 Supported the following devices
– P3113 (Galaxy Tab 2 7”)
– P3110 (Galaxy Tab 2 7″)
– I9300 (GalaxyS3)
(T-Mobile Blaze 4G)[Ed: this is actually the AT&T Galaxy Note]
– Skyrocket (Galaxy S2 LTE ATT)
– Hercules (Galaxy S2 T-mobile)
– Zeusc (SE Xperia Play CDMA-R800x)
– Zeus (SE Xperia Play -R800i)
– Wingray (Motorola Xoom WIFI)
– Urushi (SE XperiaRay-ST18i)
– Toroplus (Galaxy Nexus Sprint)
– Toro (Galaxy Nexus VZW)
– TF300T (Asus Transformer Pad)
– TF201 (ASUS EeePad Transformer Prime)
– TF101 (ASUS EeePad Transformer)
– Smultron (SE XperiaMini-ST15i)
– satsuma (SE XperiaActive-ST17i)
– p930 (LG Nitro HD / Optimus LTE)
– pyramid (HTC Sensation)
– N7000 (Galaxy Note INTL)
– Mango (SE XperiaMiniPro-SK17i)
– Maguro (Google Galaxy Nexus GSM)
– iyokan (SE XperiaPro-MK16i)
– I777 (Galaxy S2 ATT)
– I9100G (Galaxy S2 G)
– Hallon (SE XperiaNeo-MT15i)
– Haida (Haida)
– GalaxySMTD (Galaxy S)
– GalaxySBMTD (Galaxy S B)
– galaxyS2 (Galaxy S2)
– EpicMTD (Epic 4G)
– E937 (Lg My-Touch)
– E730 Lg Optimus Soul)
– Crespo (Google Nexus S)
– Crespo4G (Google Nexus S 4G)
– CaptivateMTD (Samsung Captivate)
– Coconut (SE LiveWithWalkman-WT19i)
– Anzu (SE XperiaArc-LT15i)
– P5113 (Galaxy tab 2 WIFI 10.1″)
– P5110 (Galaxy tab 2 3G 10.1″)
Interested in getting in on some RC2 action? If so, head over to the safariking’s discussion thread and head over to the CyanogenMod Mirror Network. Be sure to also check out the CyanogenMod blog for more details and CM-related announcements.