jerdog · Jan 29, 2013 at 12:30 pm

Galaxy Note 10.1 Receives Official CM10.1 Nightlies

Anyone who has spent time on XDA, or in the Android community at large, knows that when a device receives inclusion in CyanogenMod’s device tree, it is a beautiful day. This is because CM support ensures that the device will have a longer-than-manufacturer-intended lifespan. This of course depends on the manufacturer providing the tools and documentation necessary for development to occur. In many cases, OEMs do a pretty good job at publishing the documentation for instances in which they deviate from the reference design of a device’s board. Other times, however, manufacturers seem to go into brain fart-mode when it comes to this.

Samsung, in their infinite wisdom, has made it extremely difficult for devices based on the Exynos 4 reference design to receive CyanogenMod 10.x nightlies. This is not new news, as it’s been well-covered that Samsung continues to fail the community when it comes to devices based on their Exynos 4×12 devices (Galaxy S3, Galaxy Note 10.1, Galaxy Note 2, Galaxy Camera, Meizu MX). The sources from Samsung are consistently missing required pieces in order to be GPL-compliant, and recent investigations have found Gingerbread-remnants in their ICS sources.

All of that has not deterred XDA Recognized Developers espenfjo and Entropy512 from diligently laboring to bring the CM10.1 experience to the Galaxy Note 10.1. There have been obstacles, but they have pressed through. Thanks to their work, the Note 10.1 (N80o0 GSM and N8010/N8013 WiFi) recently began to receive CyanogenMod nightlies. As of the time of this posting, there are issues with Netflix working on CM10.1 but Entropy512 has put together a workaround for all Exynos 4 devices via the Xposed framework.

As is always the case, the typical disclaimers apply as CM10.1 is a work-in-progress, especially on these devices. So if you have a bug to report, make sure you post a logcat in the thread with a detailed description of what you were doing and what happened. In order to flash the builds, you will need to use either TWRP or  Entropy’s CWM build because they are the only ones that are confirmed to work at this time. If you receive an ‘assert failed‘ error message, you should first confirm that you are indeed using one of the two aforementioned recoveries.


_________
Want something on the XDA Portal? Send us a tip!

jerdog

jerdog is an editor on XDA-Developers, the largest community for Android users. Jeremy has been an XDA member since 2007, and has been involved in technology in one way or another, dating back to when he was 8 years old and was given his first PC in 1984 - which promptly got formatted. It was a match made in the stars, and he never looked back. He has owned, to date, over 60 mobile devices over the last 15 years and mobile technology just clicks with him. In addition to being a News Editor and OEM Relations Manager, he is a Senior Moderator and member of the Developer and Moderator Committees at XDA. View jerdog's posts and articles here.
Mike McCrary · May 28, 2015 at 01:43 pm · 1 comment

I/O 2015: Google Announces App Link Enhancements

During the Google I/O Keynote, VP of Engineering Dave Burke announced that the Android M Developer Preview will include improved application linking features. Under the current system, Android is limited in its intent system when applications link to other applications, displaying the 'App Chooser' dialog box for the user to select how the link is handled. In the M Developer Preview, developers will be able to add an AutoVerify ability to application links, which is a line of code that verifies the app making...

XDA NEWS
Faiz Malkani · May 28, 2015 at 01:40 pm · no comments

Google Announces its IoT platform titled ‘Brillo’

A few days ago, a leak highlighted Google's foray into the Internet of Things space, and Sundar Pichai has just confirmed it by announcing Project Brillo at Moscone West during Google I/O 2015. Project Brillo is essentially a simple operating system with only the core stack on board, such as the kernel, HAL, connectivity, device administration and BLE. Project Brillo will run on an underlying communications layer called Weave, which will employ standardized scheme to ensure that all connected devices...

XDA NEWS
Aamir Siddiqui · May 28, 2015 at 01:38 pm · no comments

Android M Adds “Doze” Deep Sleeping

Android M has answered the call of battery by adding in a deeper sleep implementation than existing deep sleep. This comes in the form of Doze. The feature make use of the devices sensor to smartly recognize when you have left your device for an extended period. During this period, wakelocks will be minimized. However, you can still continue on receiving higher priority notifications. Needless to say, this does have a tradeoff of not having up to date syncs across...

XDA NEWS
Share This