[ROM][4.2.2][P7300/P7310][UNOFFICIAL] CyanogenMod 10.1 [10.1.3, 2013-Oct-22]

#include 
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

• 3G (including GSM calls)
• WLAN
• Audio
• Rotation
• Storage
• Cameras (both)
• Keyboard dock

• HDMI output
• mute bug on gsm calls (but there's a workaround)

• Everything else

• "Stable" 10.1.3 (2013-Oct-22)
  • Final CM10.1, introduced CM account
  • New RIL (p5 only)
  • Flickering issue fixed
• "Stable" 10.1.0 -> 10.1.2
  • Security bug fixes
• 2013-Jul-14
  • Many updates for Privacy Guard
  • koush's new framework for Babel and SecureSMS
  • Security bug fixes
• 2013-Jun-27
  • Privacy Guard
• 2013-May-11
  • CM-10.1.0-RC1 (doesn't mean that this build is stable/bug free!)
  • Fixed Pie Control
• 2013-Apr-23
  • CM-10.1-M3
  • New Superuser
  • Pie Control (doesn't work)
• 2013-Mar-06
  • CM-10.1-M2
• 2013-Feb-19
  • init: remove adb forced config and switch to mtp
• 2013-Feb-16
  • 4.2.2
  • synced with CyanogenMod at 12:30 pm GMT
• 2013-Jan-25
  • ril from I9103
  • synced with CyanogenMod at 7 am GMT
• 2013-Jan-21
  • added xpad.ko
  • fixed video recording (needs new GApps, see first post)
  • a lot of upstream changes
• 2013-Jan-13
  • added ntfs.ko and cifs.ko
  • a lot of upstream changes
• 2013-Jan-06
  • prepared repos for nightlys
  • fixed charging animation
  • a lot of upstream changes, e.g. new lockscreen and launcher bug fixes
• 2012-Dec-30
  • Fixed dock
  • Tab crashes when connected in dock (needs to be verified)
  • Trebuchet app crash
• 2012-Dec-24
  • Fixed QuickSettings
  • Updated kernel to newest Samsung source release
• 2012-Dec-22
  • Fixed Audio
• 2012-Dec-21
  • Initial Build

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="cmorlok/android_kernel_samsung_p5" path="kernel/samsung/p5" revision="refs/heads/cm-10.1" />
  <project name="pershoot/android_device_samsung_p4-common" path="device/samsung/p4-common" revision="refs/heads/cm-10.1" />
  <project name="cmorlok/android_device_samsung_p5" path="device/samsung/p5" revision="refs/heads/cm-10.1" />
  <project name="cmorlok/android_device_samsung_p5wifi" path="device/samsung/p5wifi" revision="refs/heads/cm-10.1" />
  <project name="cmorlok/proprietary_vendor_samsung" path="vendor/samsung" revision="refs/heads/cm-10.1" />
  <project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" />
</manifest>

adb shell
# cd /sdcard/
# rm -rf legacy/
# rm -rf obb/
# mv -f 0/* .
# rm -rf 0/

• The final CM 10.1.0, based on the stable release. (But of course still unstable for our tab...)
• A new nightly including the Privacy Guard.

Status Update: Tegra 2 Support

In the release post for CyanogenMod 10.1, we mentioned we would provide a status update for the Tegra 2 and Exynos platforms. As the issues preventing a release for these platforms differ, today’s update will focus on the T2 platform only.

The Tegra 2 platform is known as non-NEON capable. What this means in plain terms is that it lacks in capabilities in media, audio and graphics when compared to platforms that are NEON capable (eg. Tegra 3). With Android 4.1 and above, we are noticing a trend in the Android space leaning towards greater reliance on NEON support. A prime example of this can be seen in Google’s own applications, with Google Now’s voice recognition, Gesture keyboard and even Photosphere relying on the additional benefits of NEON support to operate.

With the ecosystem shifting away from devices that lack NEON support, we are following suit. Truth is, the lack of support for this added capability will only continue to degrade Tegra 2 users’ functionality of their devices, not only now, but with future iterations of Android and CyanogenMod.

We will, however, continue to release 10.1 weeklies for the Tegra 2 platform until such time that we move on to the next Android release. We urge users who are using these builds to understand that they are operating at a handicap, and expect crashes if you introduce applications to your system that rely on NEON instruction support. As some of the more prominent Google apps have already moved onto requiring NEON, you may also want to look into open source alternatives, such as those available via F-Droid.

Click to expand...

Click to collapse

Der Straßenapotheker said:

RC2 is released !!!

Click to expand...

Click to collapse

shiko80 said:

@C-o-M Can you please give us a short feedback if you can further provide us with New versions of CM10.1. M3 is already out and there are still some open bugs like the start screen centering and the flickering issue. Thanks!

Click to expand...

Click to collapse