December 12, 2012 By: Joseph Hindy
CyanogenMod10.1 has been making its way around the forums as of late. Granted, they’re mostly unofficial builds, but any step forward is a step in the right direction. Now, CM10.1 has made to another device, the Samsung Galaxy S III I9300.
Like the build announced earlier today for the Galaxy Tab 2, XDA Elite Recognized Developer codeworkx took the reigns on this unofficial release as well. It’s a pretty early build so there are some issues, including:
- UI: Apps like NHK are broken
- Camera: Recording effects broken
- Camera: Touch 2 focus issues with enabled flashlight
- Bluetooth: audio streaming sometimes becomes laggy or stops at a distance > 1m
- FM Radio: unsupported
- TV Out: unsupported, will never work (proprietary, undocumented)
- Lots of missing and yet unimplemented features
- and a lot more
So if you’re looking for AOSP Jelly Bean 4.2 and you want it to be stable, you’re going to have to wait a little bit longer. That’s expected, though, as 4.2 is still pretty new. In a change from the norm, codeworkx requests that no one who flashes this submit any bug reports because the legendary Team Hacksung knows them all already. So simply relax, sit back, try it out, and watch the developers develop.
If you’d like to try it out, go to the original thread.
[Thanks goes out to XDA Forum Member UrbanDrawer for the tip!]
December 12, 2012 By: Joseph Hindy
CyanogenMod 10.1 (and thus Jelly Bean 4.2) has been making its way around the forums recently, and users couldn’t be happier. Moreover, it’s being released for devices that otherwise have little to no chance of receiving official Android 4.2 from the OEMs. Now, there are unofficial CyanogenMod 10.1 builds being released for the Samsung Galaxy Tab 2 10.1.
CM10.1 for the Tab 2 10.1 was released to the forums by the legendary XDA Elite Recognized Developer codeworkx. These are early builds, so there will likely be some issues. There isn’t a running list of issues, but users have reported things like the gesture typing not working, some apps like YouTube not working, and the occasional lag. Another interesting issue is the reformatting of the SD card to prepare for multiple users. This is exactly the same issue experienced on the Galaxy Nexus. There isn’t a fix for it yet, though, but it has been determined that an updated ClockworkMod Recovery will help prevent the formatting issues.
Finding workarounds for most of the issues isn’t very hard, and many users are running this as their daily driver. In fact, many have posted their solutions to the issues they’ve had to help make it easier. However, if you’re looking for 100% stability, you might want to stick with another build for the time being.
For additional info, check out the original thread.
Efforts to compile Android 4.2 ROMs for various devices have been well under way. Now, we’re starting to see some their release around the forums. This includes CM10.1, the Android 4.2 version of CyanogenMod. Now, Sony Xperia Arc and Arc S users can give unofficial CM10.1 a try.
XDA Recognized Developer Zackconsole released the build for the Arc and the Arc S. The ROM is pretty stable, although that shouldn’t be surprising, since 4.2 isn’t an enormous update over 4.1. The issues are pretty standard, and include:
Anymore? Please Report(Don’t get to test as i need to return the device)
Despite the small number of issues, Zackconsole doesn’t recommend people use this as a daily driver because it’s still in its alpha stages. In other words, only give it a shot if you’re willing to bug hunt and help make it better. Users have reported that it is working nearly as well as the device’s CM10 builds, so it may not be very long before the ROM is stable enough to run daily.
For more info, check out the original thread.
With Jelly Bean 4.1 development finally winding down after an exciting summer, Jelly Bean 4.2 seems to be picking up. The CM10.1 ports began a couple week ago, and they probably won’t stop for quite some time. Now, the HTC Desire Z and G2 have a port of CM10.1.
XDA Senior Member Flinny released a port on behalf of the Andromadus team. If you’re unfamiliar with the team, they’re a group of devs who work on devices with hardware that isn’t really supported anymore: things such as hardware keyboards and trackpads. The port is surprisingly stable for an initial release. As Flinny explains:
All of the stuff learnt from the AOSP builds has been incorporated so basically all hardware should work to the same level as it does in the AOSP4.2 builds.
If a feature is not there then it’s not been ported/merged by CM yet, I will merge them as they do.
Vision – Trackpad unlock still inoperative.
The track pad doesn’t work right now, but most of the other features should. Users have reported that the ROM works pretty well so far, with only a minor issue here and there. However, it is still an alpha, which means there may be bugs that have not yet been found. If you have a G2 / Desire Z and you like AOSP, then this is definitely something to try out.
For more info, check out the original thread.
Jelly Bean seems to have found its way to many/most devices on XDA. Since not too many manufacturers are willing or able to provide us with the most recent updates due to a slew of reasons, we need to get somewhat creative in order to stay on top of the fast paced and never-slowing tech world of ours. The time for CM10 has come and gone, with many devices running almost perfect JB AOSP ROMs, but what’s next? What else do we have to look forward to?
Well, as you may be aware, Google has released an incremental update under the same code name, which takes the OS to version 4.2, and very recently a minor bug fix release, which takes it to 4.2.1. Good folks in our forums, like XDA Recognized Developer bruce2728 have decided to take the plunge and start off on the next best thing: CM10.1. This new ROM, which was ported to the HTC Sensation is based on 4.2.1, and as you may have noticed from this article’s title, it is in a very alpha stage. What this means is that you will likely experience tons of bugs and non-functional features. The dev states that so far, camera, Bluetooth, and audio are missing in this build, but you should be able to get most other things working properly, such as WiFi, GSM radio, SD card access, touch screen, and more.
Again, please do not try this unless you are ready to live / cope with bugs that are yet to be fixed. Having said that, if you do take it for a spin, please be sure to share your feedback in the shape of bug reports, logcats, etc. with the dev. Happy flashing and welcome to the future yet again.
This is an early build of CyanogenMod 10.1 Android 4.2.1 for the HTC Sensation
You can find more information in the original thread.
Want something published in the Portal? Contact any News Writer.
The Motorola Defy is not only impervious to water, sand, and good old fashioned brute force (within reason obviously), but it is also apparently not the slightest bit phased by Motorola’s own unwillingness to keep the updates coming. When the device isn’t scuba diving or spelunking, chances are that it’s kicking back and enjoying one of the latest versions of Android, all the way up to 4.2 in the form of an unofficial version of CM10.1 thanks to XDA Recognised Developer Quarx.
Now this is very much an alpha version and really not suitable for daily use. However, it certainly proves that 4.2 isn’t out for the question for this plucky little device. You’ll be able to boot up and swipe around, make calls and send texts. A lot of the basic functionality is there. However, there are obviously going to be quite a few bugs, and some of them are fairly annoying. You may find your SD card not recognized, WiFi needs to be connected manually, camera/video recording is not fully functional, and neither are the device’s USB capabilities. All in all though, a promising start for 4.2 on the Defy
If you would like to try this version of CM10.1 for yourself, check out the original development thread for more info.
December 3, 2012 By: Haroon Q. Raja
With the release of Android 4.2, Google added several new features to the the OS. While the CyanogenMod team has officially started the transition to 4.2 based CM 10.1, it may take a while for them to start rolling out the latest 10.1 nightlies for all devices. That’s where XDA Recognized Developer and Team Euroskank member makelegs has stepped in, providing us with a working self-compiled kang built from the latest CM 10.1 sources for the Google Nexus 10.
Announced through Google+ by makelegs, this build joins the CM 10.1 builds for Nexus 7 already bring provided by Team Euroskank. As with all nightlies, some glitches here and there would be expected. However, based on the response in the forum thread, the build seems solid enough to be usable, and it lets the early adopters among us give CM 10.1 a shot before it’s officially released.
You can find more information and download links in the forum thread.
November 25, 2012 By: Conan Troutman
Android 4.2 may have only been released a short time ago, but already this latest version is finding it’s way onto numerous devices thanks to the development community and its plain unwillingness to wait for official OEM updates. The latest device to be graced with a build of 4.2 is the Samsung Galaxy SII i9100G, and it comes in the form of an official version of Cyanogenmod 10.1.
XDA Elite Recognized Developer codeworkx wasted no time in getting an experimental build of CM10.1 up and running on the device. The key word there is experimental. In the developers own words “Use it like it is or leave it.” This is probably not daily driver material yet, so unless you absolutely must be on the absolute bleeding edge, you may want to hold off flashing for a while. Who am I kidding? Of course you’re going to flash it. Just make sure to read the thread beforehand, so you know what issues you’re likely to encounter.
As mentioned above, this is for the i9100G and the i9100G only. That’s the Galaxy S II variant sporting a Texas Instruments OMAP CPU and PowerVR GPU. This ROM is not suitable for flashing on other Galaxy S II variants, so those of us with such a device will continue waiting patiently for now. For those of you who do own this device, all the information you need can be found in the original forum thread.