You all know MIUI by now, don’t you? This would be one of the few ROMs that actually gives you a completely new user experience. We released the port of the new overhaul last week for the original DROID, but today, it’s all about the DROIDX and DROID2. This has been one of those ROMs that wouldn’t make its way onto either device because of its stingy bootloader. Well, thanks to our boy @cvpcs who figured out his 2nd-init magic for some CM7 goodness, we now have MIUI. Huge props to the MIUI team (Frameworks43) for getting this out to us. (more…)
We’ve seen Asurion run out of replacement phones in the past and pick others to take their place, but going from a single-core to a dual-core phone is quite the impressive jump, I’d say. And according to multiple readers of ours, that’s exactly what is happening to owners of the DROIDX who are making an insurance claim. With Asurion running out of select devices (as seen in the screenshot above), the DROIDX2 (our review) is the current replacement phone until they receive another batch. So while we would never tell you to go out of your way to cause damage to your device, now would be the time to look into replacing it should there actually be something wrong with it.
*Note - Yes, I see that the picture is of the DROID2, so you’ll just have to trust me on this one.
Cheers Andrew, app tipster, and everyone else!
If anyone was excited for the official release, then you should be just as excited for the release of CyanogenMod7 nightlies for the DROIDX. Anyone experiencing problems with the first build, should be reassured that all those bugs will get hammered out in some of these nightly builds. And even better is the fact that @cvpcs, the developer responsible for all this, has been amazingly kind and wrote out exactly what to expect from these builds. You can always grab nightlies on your DX from the CyanogenMod official site, or if you have Rom Manager Premium installed on your device – check there first.
In order to see the nightlies in RM you’ll need to do the following:
1. Open RM Premium and hit the “Flash ClockworkMod” button.
2. When prompted, choose the “Droid X (2nd-init) recovery.”
3. Once that flashes, you’ll be able to view nightlies under “DownloadROM.”
So how excited are we all for this? Time to start squashing bugs.
There has been a lot of talk around these parts over the last few weeks that has to do with the wireless tethering situation on Verizon with certain devices like the DROIDX. We’ve posted work-arounds for whatever block they’ve implemented and complaints have been filed with the FCC, but it looks like all we really needed was a little CyanogenMod 7 to get it going. According to reader Ryan, he’s had no issues with a tethering block now that he has flashed the new CM7 for DX that we posted yesterday morning. His proof is above.
To download the latest version (since it has been pulled from the market), head here.
Netflix on Android just received a spicy little update that brings official support to the DROIDX running Gingerbread. Previous market versions actually worked a couple of weeks ago on leaked 2.3 for the DX when Team Netflix removed the device check from the app, but now things should be a little more consistent during that installation process. Go grab it now!
Well folks, it’s here. You can finally get a taste of CyanogenMod7 for the DROIDX. Our boy @cvpcs worked some magic, tested it over the last few days, ironed out the majority of bugs and has released a version (basically a beta) that’s stable enough for everyone to try. This is a pretty damn exciting day. And no need to for any extra wordplay, let’s just jump on into it. (more…)
No, that’s not a misprint in the title. Our buddy @cvpcs has finally done what many considered to be impossible – he’s successfully ported/installed/awesomed CM7 onto the DROIDX. A device that has seen developer almost come to a halt due to limitations may have a second life that is only getting started.
Back in January when he announced through Droid Life that he would be joining the CyanogenMod team, one of his goals was to get the DX into the CM family; it appears now as if we are closer than ever. So how did he do it? I’ll one quote from his post on the matter:
…this was done using my recently new-found-knowledge of 2nd-init, which I will describe later in a blog post (don’t want to get into it here). This still runs on top of the original motorola kernel though. I repeat, the bootloader is still locked, and you are still forced into using moto’s kernels, but that doesn’t really prevent us from doing all that much.
While “2nd-init” means nothing to me, it sure sounds like the breakthrough that we’ve all needed in order to take DX development to the next level. We’ll be eagerly awaiting his explanation.
…no, this means we are able to restart init and run a clean system using the currently existing kernel
Oh, he also plans to open up a testing period in the very near future, so stay close as we’ll definitely have more on that. For now though, please let your feelings be known to the world – how does CM7 on the DX sound?
Update: CVPCS offered some additional details in the comments to help clear up any confusion on the white M logo and whether or not this is Gingerbread:
Ok there seems to be some confusion. CM7 is gingerbread. it always has been gingerbread. it always WILL be gingerbread. The reason there’s a white moto logo is because it has to boot off of the 2.6.32 kernel which shipped with froyo. That does NOT mean that it IS froyo. That just means that it’s the 2.6.32 kernel instead of the 2.6.35 kernel that shipped with gingerbread. This is NO way affects gingerbread, as the D1 is currently running gingerbread off of a .32 kernel as well. Hopefully that will clear up some confusion.
Cheers zepfloyd, Daniel, James and everyone else!
It was just last week that we reported on a new blocking method that Verizon had enabled to stop rooted DROIDX users with Gingerbread from using select wireless tether apps. Today though, thanks to one of our fabulous readers, we have a work-around for the DROIDX (possibly other devices) that appears to get you up and running in just a matter of minutes. Hopefully this gives you a little bit of time while that FCC complaint over this very same subject is being looked at. (more…)