It is always an exciting time when an AOSP-derived ROM makes its first appearance on a device. It not only gives users a chance to try out vanilla Android on their new toys, but also sets the stage for future AOSP releases. Plus, users seem to really enjoy the full Google experience. Now, Motorola Droid RAZR M users can run CyanogenMod 10.
The unofficial port was released by XDA Senior Member dhacker29, who also released an unofficial build of CM10 for the RAZR HD. Unlike the Droid RAZR HD release, which was for the developer edition only, this CM10 release can used on both the consumer and developer versions of the Droid RAZR M. As can be expected, this is an initial release and that means it’s a little rough. The main features that are still broken include:
These are the main features that are broken, but they are just the ones that dhacker29 knows about. There is likely other issues as well that still need to be found and fixed. Even so, WiFi Direct and NFC aren’t the worst things that could be wrong with an initial port. So if those are features you don’t use very often or don’t intend to use, this could very well be a usable ROM.
For installation instructions and more, check out the original thread.
December 8, 2012 By: David Watt
Sony Ericsson Xperia X10 owners can start to get excited, as the device now has a CyanogenMod 10 ROM, albeit in a very pre-alpha state. With only 384 MB of RAM and a single core 1 GHz CPU, the Xperia X10 is one of those devices you just don’t expect to see running Android’s latest 4.1 Jelly Bean.
XDA Senior Member scritch007 is the developer responsible for the ROM. Having previously released CyanogenMod 9 for the X10, he is using the same knowledge in order to get the CM10 ROM up and running.
The ROM is in a beta state, so it’s safe to assume it’s not ready for every day use quite yet. There are a number of main issues listed:
But to counter that, there is also a large list of working features:
Due to the fact that scritch007 is still in fact working on the CM9 ROM, development on the CM10 ROM may take time, so don’t expect it to be fully functional anytime soon.
If you want to try the ROM in it’s alpha state, or feel you can help develop it further, check out the ROM thread.
December 7, 2012 By: Jimmy McGee
There was a lot of great news this week at XDA, starting with the report of the new Google Now updates. Jordan covers many other stories as well. Jordan talks about the many different rooting articles. First, the Odin root method for the Verizon Galaxy Note II. Second, was the story on the application called Root Transmission. Third, was the video covering three ways to root the Samsung Galaxy S III on XDA Developer TV. In other XDA Developer TV releases, Recognized Developer Benjamin Dobell talked about Heimdall and USB Logging, and TV Producer TK released a app review of Naked Browser.
In CyanogenMod 10 news, Jordan talks about the unofficial release for the AT&T Galaxy Note II. Jordan mentions the HTC Sensation getting a release as well. Finally, the Defy and Defy+ get unoffical CyanogenMod 10 releases. Pull up a chair and check out this video.
December 4, 2012 By: Former Writer
The Galaxy Note II wasn’t released long ago, but it has enjoyed a controversial existence so far. While the phone is quite an impressive device, Samsung has had some issues with documentation that has frustrated many developers working on all Exynos-based devices. That didn’t stop the AOSP goodness from flowing in, though, and now the AT&T Galaxy Note II variant has a CM10 port.
The port was released by XDA Senior Member madmack. It is an initial release, so it’s a little rough around the edges. As madmack notes:
Radio, audio, wifi, bluetooth and GPS should work. I haven’t had time to test this thing thoroughly so feedback is welcome!
The stylus doesn’t work. Need to investigate.
Dev talk: The device tree was forked from N7100. Most of the board share the same peripherals so it was a matter of getting the correct defconfig and the correct initramfs.
That should be encouraging for AT&T Note II owners, as many of the issues should be fixed relatively soon. Of course, as with most ports, there are likely to be a couple lingering issues. However, the majority of the issues should be fixed soon. This is also good news for the other US variants of the Galaxy Note II. Because they share largely the same hardware, getting this ported to the other versions should be a relatively simple task.
For the full details, check out the original thread.
November 28, 2012 By: Former Writer
The last time we brought you news about the Samsung Galaxy S I9001, it was to tell you that CyanogenMod 10 had been ported. Since then, the CM10 efforts for the device have been taken over by XDA Senior Member ivendor. Since then, AOSP development for the Galaxy S I9001 has been a veritable frenzy. With AOSP-built ROMs flying all over the place, and even some fun ROM ports.
The release of CM10 for the device in turn made ports like AOKP and PACman possible. The Galaxy S I9001 now has both. XDA Senior Member camcory has released the increasingly popular PACman ROM, and XDA Senior Member crybert took care of AOKP. Both ROMs work pretty well but users are reporting their quirks.
For AOKP, some users are reporting that the GPS isn’t functioning properly, the internal memory isn’t being recognized properly, and some random rebooting problems. For PACman, users are reporting unusually high RAM usage along with some graphical glitches in areas like landscape multitasking. The ROMs do work for the most part, so don’t let a few bugs scare you away.
The big port that is being worked on is the also increasingly popular FlymeOS. This is thanks to XDA Forum Member sc4les. The ROM seems to have many more major issues. The list of things not working includes:
browser (webview error, seems pretty common for custom roms. will be fixed soon. well it starts already)
network settings (3g works fine, so do calling and sms)
there are some graphical glitches, but only in some places
email (cant view emails due to webview error I think)
the resolution for the launcher doesnt work 100%
So that isn’t daily driver material just yet, but progress is being made. This is a shining example of the kinds of fun things developers can do once a solid AOSP-based ROM appears.
November 26, 2012 By: Jimmy McGee
Our good friend Jordan is here to get you caught up on all the Android development news from this weekend. Jordan updates the news we recently reported regarding the 4G chip in the Nexus 4. Also in 4G related news, Jordan talks about the HTC Incridible 4G LTE getting a Non-HTCDev bootloader unlock. Finally, Jordan covers the article detailing how to compile Android 4.2 for the AT&T Galaxy S II Skyrocket.
In CyanogenMod 10 news, Jordan mentions the unofficial alpha release for the Samsung Galaxy W. Also, Jordan mentions CyanogenMod 10 for the developer edition of the Droid Razr HD. Lastly, there is an experimental CyanogenMod 10.1 release for the Samsung Galaxy SII i9100G. Pull up a chair and check out this video.
November 24, 2012 By: Conan Troutman
AOSP loving Samsung Galaxy W (i8150) owners rejoice because CM10 has arrived, albeit in alpha form. With its 512 MB of RAM and single core processor, the Galaxy W is one of those devices that, according to some, would struggle to run Android 4.0—let alone 4.1. However, all that means to the developers here at XDA is, challenge accepted.
XDA Recognized Developer arco68 Recently released his unofficial version of CyanogenMod 10 for the device. Despite its alpha status, the build seems to pretty darn functional and should be usable on a daily basis unless you have some pretty specific needs. The list of features currently not working is fairly short, and extends only to WiFi tethering, Vsync (that’s buttery smoothness to you and me), and panoramic photos. However, some users are reporting issues accessing their SD cards at times.
You need to make sure that you are using one of two specific recoveries before flashing this build, otherwise you risk damaging your device. So make sure to read up before flashing. Once you’re recovery is set, the usual rules apply: Wipe, flash the zip, flash GAPPS, and you’re good to go.
If you feel like sprucing up your i18150 with a little CM10, head on over to the original development thread for more info.
November 24, 2012 By: Jimmy McGee
XDA Developer TV News specialist Jordan talks about the news you may have missed this week. First thing Jordan talks about Android 4.2 for the Nexus S. Also, mentioned is that the Samsung Wave I and Wave II received CyanogenMod 10 releases. Finally, Jordan covers the article detailing how Google has released a UI testing framework.
In Samsung Galaxy Camera news, Jordan mentions how the device has been rooted. Also, Jordan covers the three part series from XDA Elite Recognized Developer and TV Producer AdamOutler. AdamOutler unboxes the device and shows basic usage in part one, does a complete tear down in part two and shows how to root the device in part three. Also Released this week on XDA Developer TV, was a video talking about why we root by TV Producer azrienoch. Pull up a chair and check out this video.
November 24, 2012 By: Former Writer
Very recently, the CyanogenMod team released CM10 final to the community. However, many developers are still trying to get CM10 ported to their devices. Now, the ROM is available for the Developer Edition of the Droid RAZR HD.
XDA Senior Member GoClifGo05 posted a thread on behalf of the ROM’s developers, XDA Senior Member dhacker29 and XDA Recognized Developer Hashcode. Unfortunately, as stated, it’s for the Developer Edition of the phone only. It seems trivial, but it will not work on the regular Droid RAZR HD.
This is an alpha build of the ROM, so as expected, there will be some issues. Exactly what those issues are haven’t been listed, as not many users have given it a try yet. However, it presumably at least boots and has most of the core features working. In terms of issues, most users seem to be having problems just getting the ROM installed. Currently, it isn’t compatible with SafeStrap 3, and users may run into problems trying to install it via TWRP and CWM. The most common error is that it can’t get /system mounted for flashing. These are all bugs that will likely get fixed with later versions of both the custom recoveries and the ROM itself.
For more details, check out the original thread.
Now onto something different, but not quite different: our mandatory serving of news coming from the pseudo forgotten areas of XDA. No, we are not talking about Off-Topic General, but rather the section for the infamous Samsung Wave and Wave II. Due to the ever increasing popularity of Google’s Android OS, other smaller players essentially fall short in terms of expectations and support. Development costs become a financial burden, as opposed to a profitable venture. This was the case with Samsung’s own BadaOS. So, what is the next best thing you can do if you have a device running this? Flash Android on top of it.
The latter part of that statement is not a simple feat by any means, particularly due to the OS not being designed to work on the hardware. Having said that, when you have people like XDA Elite Recognized Developer Rebellos on task, you know that there is now a chance to get much needed support for the device. In this particular case, Rebellos was able to port CM10 onto the Wave and Wave II. However, the initial version is nowhere near daily driver status. In fact, radio connectivity is non functional, the battery gauge is broken, and according to the dev, the experience is rather slow. All in all, this is an alpha stage build.
Please leave some feedback for the dev and remember to back anything important up if you are going to dive into this.
So once again it’s time. Introducing the first alpha development preview of CyanogenMod 10 (based on Jelly Bean) for the Samsung Wave.
This preview is intended only for developers as it is in a very early development stage and not all features of the device are fully working.
You can find more information in the original thread.
Want something published in the Portal? Contact any News Writer.
[Thanks Rebellos for the tip!]
November 16, 2012 By: Jimmy McGee
CyanogenMod team releases a final version of CyanogenMod 10 for various devices while dealing with website extortion issues. These are only two exciting stories from the XDA Portal this week. Other stories rehashed by Jordan include three other video releases on XDA Developer TV. Released this week by XDA Developer TV Producer TK was his two part review of the Samsung Galaxy Note II and it’s S-Pen. Also, released this week was XDA Developer TV Producer azrienoch’s discussion of the DMCA.
In Android 4.2 news Jordan mentions the release of an image for the Nexus 7, Nexus 4 and Nexus 10 devices. Finally, Jordan mentions that the Android 4.2 update hits AOSP, the SDK has been updated and the Nexus binaries have been added too! Pull up a chair and check out this video.
Recently, the more astute among you may have noticed that the CyanogenMod project has begun to use the cyanogenmod.org domain rather than their previous .com version—a seemingly incongruous change, unfortunately driven by a malicious team member (turned rogue).
SatanR1, to use his username, bought the .com domain name for CyanogenMod via his company, Metserve Enterprises, when they started their own site to host builds and infrastructure such as their build system and distribution network. At some point in the past few months, the owner of the domain decided to fraudulently impersonate Steve Kondik (Cyanogen) towards companies, in order to seek donations and financial contributions. These were claimed to be going to the CyanogenMod project, but were in fact going directly to the impersonator himself.
To make matters worse, this user had (and has) full control of the .com domain name (which CyanogenMod are currently attempting to regain via the ICANN dispute procedure). The impersonator tried to extort $10,000 from the team to have the domain name returned (which they naturally cannot and will not pay). As of today, the domain name has been directed away from the project’s site, presumably in an attempt to try to gain some further money from the team.
To echo the request from the CyanogenMod Team,
If you are a company out there that believes they have also entered into agreements with “CM” by this person impersonating Steve, please contact Shade@chemlab.org. We’d like to get a handle on how widespread this was before we file charges.
The Android community is fairly tightly knit, and to see such a flagrant abuse of trust is frankly shocking. To see someone attempt to extort vast sums of money from an open source project (after already having obtained large sums of money by purporting to represent them to other companies) is likely very distracting for the team, yet they have pressed ahead with the release of CyangenMod 10 nonetheless.
I hope you will agree that this kind of behavior is totally unacceptable, and that such unethical business practices, especially by someone operating under the guise of their business, should be condemned by the community as a whole.
Update: Thankfully, it appears as if the situation is now resolved.
There comes a time in life, when everything must evolve and better itself. This does not happen overnight and certainly not by itself. Apparently, this seems to be the case for the infamous CyanogenMod ROM. The latest installment, known as CM10, is finally getting to a point where the CM team has deemed the release as highly stable and almost bug free. This is great news for anyone using AOSP-based ROMs. as many of them share parts of the CM code as well.
The best part about this is that it allows anyone to try Jelly Bean 4.1, despite not being able to due to lack of updates coming from device manufacturers or because the device may no longer be supported/ineligible for updates. They can now enjoy the improved experience that is offered by the newly revamped OS. Having said that, and going back to the ever evolving nature of our devices’ firmware, you may want to keep an eye out for newer versions of CM (10.1 maybe?) because as of yesterday, 4.2 source code was released to the AOSP, and it comes loaded with all the goods we talked about earlier.
One last thing worth mentioning is that, while the list of supported devices under the CM umbrella is huge, it does not mean that every device supported will receive CM10 final just yet. Only a few of the most popular devices have gotten the green light to label the release as “Final,” including most variants of the SGS3, several variants of the SGS2, HTC One X, Motorola Xoom, and of course the Nexus devices, as well as a few others. So, keep your eyes peeled to see if your device is in the “chosen” list.
You can find if your device is included in the list or not by visiting the CM downloads page, and by visiting your local device forum here on XDA.
Want something published in the Portal? Contact any News Writer.
[Thanks willverduzco for the tip!]