customrom

Latest

  • CyanogenMod 9 now stable on every supported device, get your fix today

    by 
    Jon Fingas
    Jon Fingas
    08.10.2012

    We saw CyanogenMod 9 reach the perfect poise of a stable release on the Galaxy Nexus just this past Thursday. It's now time for everyone else to join the club: all devices that can run CM9 now get the firmware in the same polished state, giving more conservative fans a path to CyanogenMod's custom Android 4.0 build. The code brings an audio equalizer, OS gesture commands and themes, among other tweaks that you won't find sitting in that vanilla Ice Cream Sandwich. If you're not so adventurous as to live on the bleeding edge that is CyanogenMod 10, hit the source link for the (considerably safer) next best thing. [Thanks, Bryson]

  • CM9's first stable release lands for GSM Galaxy Nexus

    by 
    Terrence O'Brien
    Terrence O'Brien
    08.09.2012

    Well, it's certainly taken a while, but the popular CyanogenMod finally has a stable version of its ninth iteration. It's yet to hit the ROM's homepage, but that's probably because its only available for the GSM Galaxy Nexus at the moment. The Ice Cream Sandwich-based ROM has clearly posed some issues for the devs, but it's worming its way towards a wide release and work on CM10 (which is based on Jelly Bean) is already progressing quite nicely. In many ways moving to a build of Android 4.0.4 will be a step backwards for those running stock 4.1, but CM9's support for themes, gestures and the top-notch DSP equalizer will surely lure a few away from the official Google release. Hit up the source to download the stable Maguro-friendly release for yourself. [Thanks, Jul]

  • OTA Update Center encourages PC-free upgrades for custom Android ROMs

    by 
    Jon Fingas
    Jon Fingas
    08.09.2012

    Over-the-air firmware updates are mainstays for most smartphone platforms, but custom ROM builders have rarely had such a luxury, even with Android. The OTA Update Center wants to shoulder that noble burden. Along with simply hosting the updates to prevent outrageous bandwidth bills, the Center enables everything an Android ROM creator might need, such as update checks, on-device firmware flashing and wiping either a cache or all user data for the more dramatic upgrades. In practice, the real perk is the cost: it's free to use, so everyone from hobbyists to seasoned teams can take advantage. While the list of those either using or planning to use the OTAUC isn't public, we're hoping it leads to a few more experimental builds of CyanogenMod and other ROMs that can now get the same tender loving care as the official code.

  • HTC G1 auditions CyanogenMod 10, runs Jelly Bean at a snail's pace (video)

    by 
    Sean Buckley
    Sean Buckley
    08.09.2012

    Putting Google's latest candy-coated OS update on the very first Android phone? We've got a guy for that. Jcarrz1, the same wizard from XDA-Developers who ported Ice Cream Sandwich to the HTC G1, has managed to port a buggy build of CyanogenMod 10 to the handset -- which puts Jelly Bean on the oldest hardware possible. Sadly, the old handset isn't up to Project Butter's 60FPS interface, but brave tweakers can still use the device's touchscreen for apps, CM10 features and a partially functional Google Now. WiFi is also up and running, but cellular data is MIA. Check out the video above to see the pre-alpha build in action, or try it out for yourself at the source link below.

  • HTC Sense 4.1 reportedly leaked with custom ROM, One X owners taste the future

    by 
    Jon Fingas
    Jon Fingas
    08.06.2012

    It feels like just yesterday that we were getting acquainted with the back-to-basics ways of HTC's Sense 4.0. Well-known HTC phone modder Football doesn't want us to get comfy: he claims to have both obtained a leaked version of Sense 4.1's ROM Upgrade Utility (RUU) and folded it into the 2.2 update to his Maximus firmware for the international One X. While it's no Jelly Bean, the Maximus-tuned version of HTC's Android 4.0 flavor appears to give Sense a shot in the arm, taking care of lag in the launcher and live wallpapers in addition to delivering a healthy overall speed boost. That 0.1 numbering gives a good indication of just how light the visible feature set might be, though -- other than an existing update to substitute the virtual menu button for a long-press of the home key, the interface changes are mostly limited to dedicated buttons for switching browser tabs and between different cameras. It's no surprise that HTC hasn't said a word about its own plans; rumors of new One devices, however, can't help but fuel suspicions that Sense 4.1 is just around the bend.

  • Google posts Android 4.1 Jelly Bean images for Nexus devices, modders rejoice

    by 
    Jon Fingas
    Jon Fingas
    07.27.2012

    If you're the sort to get a little too adventurous with CyanogenMod 10 or other custom ROMs, Google just gave you a crutch. Android 4.1.1 factory images are now available for every Nexus device that can currently get a taste of Jelly Bean: the HSPA+ Galaxy Nexus, Nexus S and the expected Nexus 7. While it's not a complete safety net, the gesture will let dedicated modders flash their phones and tablets knowing that they can almost always jump back to the pure OS if someone's definition of "alpha build" is a little too rough. CDMA users are unfortunately left out of the loop; let's just hope they're brought up to speed before too long. [Thanks, Vince]

  • CM10 preview builds out for Nexus 7 and Galaxy Note: official but experimental

    by 
    Sharif Sakr
    Sharif Sakr
    07.27.2012

    Ready for the latest bout of XDA Recognized goodness? If you own a Nexus 7 or global Galaxy Note (oh yeah) then you'll find official preview builds of CyanogenMod 10 for each device at the source links below. They'll bring some added sparkle, like an almost-buttery version of Jelly Bean on the Note and USB storage on the Nexus 7, but neither build is ready for daily dependence -- so tread carefully or just consider them proof that the CM and Team Hacksung folks are almost there.

  • Motorola to allow bootloader unlocking from Photon Q 4G LTE onwards

    by 
    Jon Fingas
    Jon Fingas
    07.26.2012

    Motorola's initial promise to allow unlocked bootloaders came across to many enthusiasts as somewhat hollow: as long as there was an escape clause, carriers like AT&T and Verizon could clamp down and maintain the tough-to-modify status quo. RAZR-philes will be happy to know that there's a plan to cut their own chains loose, after all. Starting with the Photon Q 4G LTE's August launch, owners will have the option to unlock the bootloader of at least some devices in an official way that reportedly keeps carriers satisfied. Details of how the process works will come later; we don't know if Motorola will take a cue from HTC's identifier tokens or try something more exotic, even if it's likely in either case to offer a big, fat disclaimer regarding the warranty. The option won't be the same as buying a phone that's unlocked from the start, but we don't think too many custom ROM lovers will mind after knowing that one more Android manufacturer is on their side. [Thanks, RTbar]

  • CyanogenMod developers slap Jelly Bean on an Optimus 4X HD, tease CM10 (video)

    by 
    Sean Buckley
    Sean Buckley
    07.13.2012

    That didn't take long. The boys behind CyanogenMod promised a quick turnaround for its upcoming JellyBean-based update and are already teasing workable CM10 ROMs. CyanogenMod's Ricardo Cerqueira tossed a video of an early CM10 build on his YouTube page, declaring "it lives!" The early build is running on an LG Optimus 4X HD, and runs through unlocking the screen and recording and playing back a video. The build is still having some trouble with Google's revamped search integration, but considering Android 4.1's source code was released only days ago, the quick development is promising. Check out Cercuiera's quick demo for yourself after the break.

  • Jelly Bean spreads the butter to Amazon's Kindle Fire in unofficial beta build (video)

    by 
    Joseph Volpe
    Joseph Volpe
    07.11.2012

    Jelly Bean(s) for everyone -- essentially, that's just what Google's done for the tech savvy underground with 4.1.1's release in AOSP. Not two days after that source code was made available, has a developer by the name of Hashcode worked to get an early build up and running on Amazon's Kindle Fire. If you'll remember, that Bezos-backed slate runs a heavily customized UX with Gingerbread buried deep at its core and official plans for a software update beyond its 2.3 underpinnings have not been announced. So, for adventurous owners that are sick of living in the software-past, but aren't quite ready to part ways with 200 bills for that very now Nexus 7, a beta ROM is at the ready. Naturally, you'll need to have your device rooted and loaded with a custom recovery to get things going but, take note, this work-in-progress is far from complete: hardware video acceleration isn't yet supported and WiFi is somewhat unstable. Fixes are assuredly on the way, so the less carefree might want to abstain from flashing at the moment. For everyone else, you can find the necessary downloads at the source below and, while you're at it, check out the video tour after the break. Update: Looks like the crew got Google's apps (Play Store, Gmail, etc.) working as well as WiFi. Check out the updated tour video here.

  • Verizon Galaxy S III has locked bootloader (but it's been rooted anyway)

    by 
    Sharif Sakr
    Sharif Sakr
    07.07.2012

    Based on Samsung's hacker-friendly track record, you'd generally expect one of it smartphones to come with an unlocked bootloader, making it easy to update or tweak with unofficial ROMs. That's not the case with Verizon's imminent version of the Galaxy S III, however. As the folk at XDA know only too well, this particular iteration of Sammy's flagship comes with a sealed bootloader, which makes it resistant (though not impervious) to hackery. Of course, Sammy has nothing to gain from snubbing the modding community in this way, so it stands to reason that VZW pushed the Korean manufacturer to supply them with a locked bootloader -- despite the fact that all other variants have been left open. We've reached out to Big Red for comment, but in the meantime a clever soul over at Rootzwiki claims they've already found a workaround for root access. (At this point, though, we'd better provide our usual disclaimer: be very careful before you poke around in there, because going up against a locked bootloader can be risky. The apparent safety of modern life is just a shallow skin atop an ocean of blood, guts and bricked devices.)

  • Baidu custom ROM for Nexus S swaps Google's apps for Baidu's own, gets few fans in Mountain View

    by 
    Jon Fingas
    Jon Fingas
    06.04.2012

    The Nexus S was supposed to be the definition of Google's perfect phone circa late 2010, so we can't imagine that too many at the Googleplex are enthused with the potential impact of a new custom ROM from Baidu. China's search giant has replaced many of the stock Google apps in Android 4.0 with its own examples, ranging from media players through to navigation. Google will take some consolation from knowing that the firmware can't be pushed out over the air and has to be sideloaded over USB. All the same, with plans from Baidu to expand to other Android 4.0 devices, we can't help but think Google faces a minor Kindle Fire effect where it's cut out from its own ecosystem.

  • Google Music users granted de-authentication reprieve as company retools activation system

    by 
    Zachary Lutz
    Zachary Lutz
    05.16.2012

    Google Music users learned of a frightful new policy this morning that dictates a user may de-authorize only four devices in a year, out of ten total activations. While the policy is likely to go unnoticed by the majority of consumers, it instantly created a great pain for those who regularly flash ROMs to their phones and tablets. It seems the road to de-authorization hell is paved with good intentions, however, as Google has since responded to critics with the revelation that it'll introduce an activation system that accounts for such nuances. We've determined through our own experimentation that Google has temporarily suspended the de-authorization limit of four devices, and while it's difficult to know how long this reprieve will last, we're hopeful that it'll remain in effect until Google implements this new system to recognize duplicate authorizations. Additionally, we've learned through our conversations with the company that users may, in fact, sign in to their Google Music account from any number of devices, and it's only when a tune is deliberately streamed that your smartphone or tablet will be added to the list of ten. What's more, while the company was rather insistent that songs couldn't be streamed to multiple devices at the same time, it seems that Google's system of checks and balances is spotty at best -- we were able to simultaneously stream tunes to three devices without so much as a hiccup. Yes, the system eventually shook its finger at us, but it serves as a nice reminder to have fun while the insanity lasts.

  • Visualized: Android's device diversity cut up into 3,997 little pieces

    by 
    Jon Fingas
    Jon Fingas
    05.16.2012

    Some call it diversity, some call it fragmentation. However you slice it, there's a lot of Android devices out there. OpenSignalMaps has tracked a staggering 3,997 unique phones, tablets and other Google-powered gadgets, and has put them into a chart weighted by popularity. Not surprisingly, it's powerhouses like Samsung's Galaxy S II and HTC's Desire line that dictate the platform, while that Concorde Tab you bought in Hungary sadly doesn't have much traction. The normally signal mapping-oriented crew is careful to warn that the actual variety might be less: there's 1,363 one-timers in the group, and some of those may be custom ROMs and the endless carrier-specific variants that OEMs are sometimes eager to make. There's even more to look at through the source, including Android 2.3's continuing dominance and the mind-boggling number of Android screen resolutions, so click ahead for an even fuller picture.

  • PSA: Google Music allows four device de-authorizations per year, rooters beware

    by 
    Sharif Sakr
    Sharif Sakr
    05.16.2012

    Just when you thought you could go on rooting and switching ROMs with impunity, it turns out you can't -- at least, not if you want to continue enjoying your Google Music account. Watchful eyes at XDA Developers have discovered a snag in Google's authorization system, which means that not only is there an upper limit of ten devices that can be authorized simultaneously, but there's also a limit of four de-authorizations per year. Since every time you flash your phone or tablet counts as a new authorization, and since your other devices probably hog a few tickets already, rooters will quickly hit the ten-device limit, at which point they're going to have to think long and hard about their de-auth strategy. Is that a ration of one flash per quarter? But then what happens if you buy a new device in a few months' time? Oh, this is too much. [Thanks, Aman]

  • Transformer Prime gets power of reincarnation with Team Win Recovery Project 2.1.2

    by 
    Sharif Sakr
    Sharif Sakr
    04.24.2012

    Known affectionately as Twrp, this handy utility allows you to backup and recover your Android world even as you flit effortlessly between different custom ROMs. Two-point-oh worked great on a limited selection of devices, like the Nexus S, Kindle Fire and TouchPad, but this latest update brings improved support for Honeycomb tablets and ICS handsets like the Galaxy Nexus, while also doing its thing on the Transformer Prime for the first time. Team Win has even introduced a OpenRecoveryScript function, which lets apps influence the recovery process in order to preserve even more consciousness across rebirths. Now, if only we could root karma.

  • HTC One X gets unofficial power management fix, boosts battery life 10 to 20 percent

    by 
    Zachary Lutz
    Zachary Lutz
    04.13.2012

    Somewhere along mike1986's development of Android Revolution HD, a custom ROM for the HTC One X, he found that something amiss with the smartphone's stock system -- its Tegra 3 power management software didn't function properly. According to the developer, an app known as NvCPLSvc.apk was misplaced in the /system/bin folder, rather than its proper destination of /system/app. Along with the custom ROM, mike1986 has released the fix as a separate bundle, which is detailed in the source below. To apply the patch, users must push the new APK to their handset via ADB, and then alter the file's permissions. Unless you're seriously hindered by your phone's battery life, however, it seems safe to wait for an official update from HTC. On the upside, users report an battery life increase in the neighborhood of 10 to 20 percent once with the fix in place, and we can only hope that all users will soon benefit from similar gains.[Thanks, Nitin]

  • Android Open Kang Project brings hyper-customization to your nav bar (video)

    by 
    Sharif Sakr
    Sharif Sakr
    04.08.2012

    Still dallying at the corner of Custom ROM Road? Then maybe the forthcoming update from Team Kang (AOKP Build 30, no less) will entice you onwards. The preview clip after the break reveals a new level of freedom for the ICS navigation bar, including the ability to add up to five buttons, assign them to apps or actions as you wish, modify their icons and add separate long-press functions. It also gives you the ability to incorporate Nova Launcher actions into the bar, effectively bringing a whole extra layer of customization. Reactions over at RootzWiki range from "I'm crying, this is a beautiful moment" to "I just broke my hand punching a wall," but the latter dude admitted he'd been drinking.

  • CyanogenMod disables root access by default, now requires user configuration

    by 
    Zachary Lutz
    Zachary Lutz
    03.16.2012

    Holy crap! CyanogenMod, the custom ROM of choice for many power users, will no longer offer root access upon first install. Now before you panic, let's make this part clear: everyone so inclined may still enable superuser access -- for ADB, apps or both -- from the Developer Options menu. The biggest change, in fact, is that CyanogenMod is making a significant departure from the majority of custom ROM developers, which offer root access to all users by default (and often without their knowledge). The move is an attempt by CyanogenMod leaders to make the platform more secure, and given the number of ROMs that are based on CyanogenMod (or glean its packages), we wouldn't be particularly surprised to see this feature become more commonplace amongst other custom Android ROMs. To learn more about the rationale of the project leaders, be sure to hit up the source link below.

  • CM9 for TouchPad gains access to nightly builds

    by 
    Sharif Sakr
    Sharif Sakr
    02.17.2012

    Happy tidings for TouchPad owners looking for the latest Android 4.0 action: the Alpha 6 build of CM9 can now tune into nightly broadcasts of fixes and updates, courtesy of TeamWin members Eyeballer and Kevank. This is an unofficial development branch and users have so far seen mixed results, but the main CyanogenMod crew seems content enough to recommend it -- at least until a new Alpha or Beta build comes along with major improvements like video playback or camera support. It's definitely healthier than holding your breath.