CyanogenMod Samsung Exynos 4 Support Ends At Nightly Builds; No General Release CM10.1 For Galaxy S3, Galaxy Note And Others

CyanogenMod fans who own devices with a Samsung Exynos 4 processor will be disappointed to learn that the custom firmware team will not roll out the general release CyanogenMod 10.1 version (ROM of Android 4.2 Jelly Bean) for these devices.

CyanogenMod recently released a statement on Google + explaining that it found developing stable firmware for devices with either the Exynos 4210 and 4412 chipsets to be too difficult. It had issues with binaries and sources for Exynos 4-based devices as early as the inception of Android 4.0 Ice Cream Sandwich, which was released in 2011, and CyanogenMod says it decided to lower its level of support on these devices because they are currently unable to meet their own standards for firmware quality.

The effected devices include:

Galaxy S II (AT&T and International GSM)

Galaxy S III (International GSM)

Galaxy Note (International GSM)

Galaxy Note II (AT&T, T-Mobile, International GSM and International LTE)

Galaxy Note 10.1 (WiFi and International GSM)

CyanogenMod says it will continue to support these devices with nightly builds to roll out bug and security fixes and the latest updates; however, the team will no longer accept bug reports on ROMs for Exynos 4-based devices. The CyanogenMod team also says that if it is able to resolve the issues it has had with these devices, it will release a stable CM10.1 build in the future. For now; however, that seems unlikely.

The team ensures that support for Exynos 3 and Exynos 5-based devices, such as the international Samsung Galaxy S4, is not affected by this issue. Nor are Qualcomm Snapdragon-based devices; which are largely found in the U.S. market. CyanogenMod says it is currently developing its Exynos 5-based builds to increase quality.

Do you install CyanogenMod ROMs on your Exynos 4-based device? How do you feel about this lowering of support? Let us know in the comments below.

Follow me on Twitter @FionnaatIBT.