Samsung Exynos-based Phones Are Slowly Losing Developer Support!”
I get home from a long horrible day at work, and checking out all my favorite forums to find out all the awesome news and updates of my favorite ROMs. Then I read this very disappointing article posted by one of my favorite writers Jeff McIntire over at RootzWiki, that leads me to one of my favorite developers Codeworkx blog.
Apparently the Galaxy Note 2 that I was extremely excited to get and other Exynos-based phones will not have the same developer support that the newest Snapdragon, TI OMAP, and Tegra 3-based devices get.
Codeworkx (a developer for CyanogenMod/Team Hacksung and many others) have withdrawn support for many Exynos-based devices including the international versions of the Galaxy S III, Galaxy S II , Galaxy Note, and all new versions of the Galaxy Note 2. It’s all because a lack of developer support from Samsung for its signature chipset.
In a conversation that Jeff had with Codeworkx, he pointed out that AOSP ROMs running on new and recent Exynos-based devices face a variety of bugs because of failure based on Samsung’s part to release the source code that’s needed for its Exynos chipsets. So for example, bugs in the International Galaxy S III (i9300) include certain camera features, broken Bluetooth and WiFi tethering, and unsupported TV Out.
In the international Galaxy S II, the issues include incomplete Jelly Bean support from Hardware Composer (referring to the Mali GPU included in the Exynos chipset), broken camera recording, slow transfer of data over USB in Mass Storage mode, and TV Out (as in the i9300). The international Galaxy S III hasn’t completely lost CyanogenMod support though, as developer Xplodwild is still supporting the device at the moment.
-CyanogenMod/Team Hacksung developer Codeworkx Stated…