[ROM][GT-P52XX][UNOFFICIAL][6.0.1] CyanogenMod 13.0

Search This thread

OKAstro

Senior Member
Mar 5, 2011
653
172
0
Edmond, OK
My TWRP version matches. The Houdini zip has been flashed too to no avail. And I do not have a memory card.

Odd. You're sure it's rooted? I'm guessing you couldn't flash if not rooted.

I would try one more thing. Boot into recovery and besides wiping everything again (factory reset), try formatting the data partition. NOTE THIS WILL DELETE ALL PHOTOS, MUSIC, FILES SO BE WARNED.

Then flash these in this order:
1. cm-13.0-20161210-UNOFFICIAL-santos10wifi
2. houdini_6.0.0_x.47745
3. open_gapps-x86-6.0-pico-20161213 Select X86....6.0...I use the PICO package
 
  • Like
Reactions: ZDEKONik

humzaahmed155

Senior Member
Dec 30, 2011
1,340
295
113
London
Odd. You're sure it's rooted? I'm guessing you couldn't flash if not rooted.

I would try one more thing. Boot into recovery and besides wiping everything again (factory reset), try formatting the data partition. NOTE THIS WILL DELETE ALL PHOTOS, MUSIC, FILES SO BE WARNED.

Then flash these in this order:
1. cm-13.0-20161210-UNOFFICIAL-santos10wifi
2. houdini_6.0.0_x.47745
3. open_gapps-x86-6.0-pico-20161213 Select X86....6.0...I use the PICO package

So I went and bought a memory card and curiously tried it in the Tab since someone mentioned it. And weirdly enough it booted right away with the memory card in it. That's definitely one of the weirdest things I've seen so far.
I was even considering a re-partition through Odin. I'm glad it's working now though :confused:
 

OKAstro

Senior Member
Mar 5, 2011
653
172
0
Edmond, OK
So I went and bought a memory card and curiously tried it in the Tab since someone mentioned it. And weirdly enough it booted right away with the memory card in it. That's definitely one of the weirdest things I've seen so far.
I was even considering a re-partition through Odin. I'm glad it's working now though :confused:

Glad it's working!! You might PM the developer and describe what happened. Maybe he knows why

---------- Post added at 10:40 AM ---------- Previous post was at 10:36 AM ----------

So I went and bought a memory card and curiously tried it in the Tab since someone mentioned it. And weirdly enough it booted right away with the memory card in it. That's definitely one of the weirdest things I've seen so far.
I was even considering a re-partition through Odin. I'm glad it's working now though :confused:

Also - I wonder if previous owner had used a memory card, and tablet was "still looking for it" when booting up. Had you formatted data partition to wipe all traces of things like that?
 

humzaahmed155

Senior Member
Dec 30, 2011
1,340
295
113
London
Glad it's working!! You might PM the developer and describe what happened. Maybe he knows why

---------- Post added at 10:40 AM ---------- Previous post was at 10:36 AM ----------



Also - I wonder if previous owner had used a memory card, and tablet was "still looking for it" when booting up. Had you formatted data partition to wipe all traces of things like that?

That's the thing, I assumed that too but then even after formatting everything (and then into F2FS) it still did that :confused:
 

Sandman291au

New member
Apr 25, 2015
2
1
0
Sydney,Australia
Firstly I'd like to thank Nels for all your work on this project,I've been following it since you first ported over CM12 which was godsend.Nels I've noticed in my experiences anyway that the Google Now launcher could be causing some of the issues with lag and increased battery consumption. I've switched between the last 2 Beta's back and forth several times with the same result.Once I changed to the Trebuchet launcher everything from keyboard lag to battery life and also inconsistent benchmarks was instantly eradicated.Hope this helps some of you.
 

Pirex69

Senior Member
Apr 16, 2012
837
242
73
Lisboa
Firstly I'd like to thank Nels for all your work on this project,I've been following it since you first ported over CM12 which was godsend.Nels I've noticed in my experiences anyway that the Google Now launcher could be causing some of the issues with lag and increased battery consumption. I've switched between the last 2 Beta's back and forth several times with the same result.Once I changed to the Trebuchet launcher everything from keyboard lag to battery life and also inconsistent benchmarks was instantly eradicated.Hope this helps some of you.
Just to remind you that Nels83 work are not ports. There a difference between porting and building
Merry Christmas to you all
Cheers

Enviado do meu SM-J500FN através de Tapatalk
 

MisterVKLN

Member
Nov 28, 2016
11
0
0
Hello! This problem, in the BETA 2 does not work deep sleep, how to solve this issue?
Do a clean install with all wipe :confused::(
Sorry for my bad English
 
Last edited:

Kuzja

Member
Dec 26, 2016
5
1
0
>>>>>>>Fix for platform.xml<<<<<<<<
/etc/permissions/platform.xml

<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
</permission>

<permission name="android.permission.WRITE_MEDIA_STORAGE" >
<group gid="sdcard_r" />
<group gid="media_rw" />
<group gid="sdcard_rw" />
</permission>

<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="media_rw" />
<group gid="sdcard_rw" />
</permission>
 
Last edited:

guusw

Member
Jul 30, 2016
15
7
0
Changes in platform.xml will not change permissions in in CM13 /Marshmallow. This method only works on Android 4.4 - 5.1.
In Android 6 (and further?) permissions are managed in Packages.xml and must be set for every app.
You can use this Xposed module to set write permissions on sd card per app. Works on p5210.
Also Extsdfix claims to work on Marshmallow (all installed apps in one time). I used v1.9b earlier with succes.
 
Last edited:

cognacais

New member
Dec 28, 2016
1
0
0
Hi my english is not good, i'm french ;)

I have a problem with skype. I can't create my account. Skype craches. I clean data but it doens't work. I am alone or you have problem too.

Thanks you.
 

Christoph21x

Senior Member
May 22, 2009
699
334
83
Schwyz
Dear All
I encounter some kind of weird issue:
I bought a new BT keyboard. No problem in finding it and pairing it. Within System, it's then called "Keyboard BT 3.0".
As soon as it's paired (it works) and the system enters the lock screen, I'm blown.
I see the lockscreen (no pin, just a wipe needed), I wipe to open main screen, the Screen turns black (and also the lights of the two buttons go off.
No way other than to reboot. But after a fresh reboot, I'm again stuck with the same behaviour in lock screen.
Even switching of BT doesn't change a thing...

... the only way to get my Tab back, is to restore from previous install without this BT pair.

Any Idea? My Idea: HW doesn't supprt BT3, but MArshmallow pretends (or thinks :) ) to support... so it's a mismatch

Kind greetz - Chris
 

Top Liked Posts

  • There are no posts matching your filters.
  • 99
    Unofficial CyanogenMod 13.0 for Samsung Galaxy Tab 3 10.1

    CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.

    Code:
    #include 
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards, ...
     * You flash this at your own risks
     */

    About CM

    CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Important information

    You need a recent TWRP version to flash this ROM.

    Installation

    First time installing, coming from another ROM or upgrading from alpha < 4
    • Copy ROM to SDCard
    • Copy Houdini to SDCard
    • Copy GApps to SDCard
    • Boot into recovery
    • Backup EFS partition
    • Wipe -> Advanced Wipe -> Dalvik Cache + System + Cache + Data
    • Install ROM
    • Install Houdini
    • Install GApps
    • Reboot
    • First start takes a long time

    Upgrading from earlier version of CyanogenMod 13.0 (alpha >= 4)
    • Copy ROM to SDCard
    • Boot into recovery
    • Install ROM
    • Reboot

    [OPTIONAL] Converting filesystem to F2FS (thanks @michiil)

    The ROM has F2FS support. You may want to use it instead of the default (EXT4).

    This will delete ALL files/data from your tab.

    What you will need: A working PC and a working USB cable.

    1. Install the most recent Recovery
      Download the most recent Recovery from the second post. Flash the zip file in recovery. Back in the main menu press Reboot > Recovery
    2. Format Data and Cache to F2FS
      Wipe > choose Cache > repair or change file system > change file system > F2FS > Swipe to Confirm
      Go back and repeat the same steps with Data. I got some error messages when formatting Data but they don't seem to be a problem.
      Back in the main menu press Reboot > Recovery
    3. Install Rom + Houdini + Gapps
      Connect your tab to your PC and copy the zip files on the tab.
      Flash the files, reboot and enjoy :good:

    How to get back to EXT4

    You will again loose all files/data on the tab.
    Just repeat Step 2 but use EXT4 instead of F2FS.

    What's working

    • RIL (audio calls, data, sms, mms)
    • 2D/3D acceleration
    • HW video encoding/decoding
    • Screen cast (Miracast/Wifi Display)
    • MHL/HDMI
    • Sound
    • InfraRed
    • Camera
    • Wifi
    • Bluetooth
    • GPS
    • Sensors
    • SDCard, USB OTG
    • Tethering (USB, Bluetooth, Wifi)
    • Software DRM (Level 3, see below)

      Known to be working
      • Google Movies
      • Amazon Prime Video
      • Molotov TV
      • myCANAL
      • Canalplay Kids
      Known *not* to be working
      • 6play

    Features

    • Automatic brightness
    • Change Color profile
    • Change mDNIe scenario
    • Enable/disable mDNIe negative mode
    • Multiuser
    • Enable/disable capacitive keys
    • Change capacitive keys width
    • Buttons backlight on screen touch or key touch only
    • Smart cover lock/unlock
    • F2FS and exFAT support
    • Houdini (allows to install arm only apps on this x86 device)
    • Updated ZRAM support with LZ4 compression for maximum memory and speed
    • Updated Xbox Controller driver
    • Updated interactive CPU governor
    • Available CPU governors: powersave, interactive, performance, ondemand
    • Available I/O schedulers: noop, deadline, cfq, bfq (v7r8), fiops
    • Available battery modes (CM power profiles): power save, balanced, performance

    What's not working

    • Chromecast screencasting (other functions work)
    • Hardware DRM (Level 1)
    • SELinux (permissive)
    • You tell me

    How to root

    • Go to 'Settings/About tablet'
    • Tap 7 times on 'Build number'
    • Go back
    • Go to 'Developer options'
    • Tap on 'Root access'
    • Select 'Apps only' ('Apps and ADB' if you plan to use it in adb shell)

    How to help

    When something is not working correctly, in addition to common informations, I may ask you to provide logs. There are different kind of logs and it's not always easy to get all of them. For this, you can use SysLog (available on F-Droid or Google Play).
    Fixed in version 2.1.0 There is currently a bug in the app. Download it from AndroidFileHost. Use this patch if you want to compile it yourself:

    Make sure to root device before using this app.

    To get the logs:
    • Start SysLog
    • Click on 'TAKE LOG'
    • Once log is taken, SysLog will try to share the resulting file, just cancel
    • Send me the file /sdcard/SysLog/[YYYY-MM-DD_HH.mm]/[YYYY-MM-DD_HH.mm].zip

    If you left 'Scrub potentially personal information from the logs' checked, you should be safe.

    Sources

    Credits

    • Angel_666 , moonbutt74 and Restl3ss for starting the work on this device
    • Android-Andi for his device tree
    • crpalmer for his work on Intel support
    • Deltadroid for his GApps package
    • All testers of the "signup" thread
    • CyanogenMod and Google for Android
    • XDA
    • AndroidFileHost

    XDA:DevDB Information
    CyanogenMod 13.0 for GT-P52XX, ROM for the Samsung Galaxy Tab 3 10.1

    Contributors
    nels83
    ROM OS Version: 6.0.x Marshmallow
    ROM Kernel: Linux 3.4.x
    Based On: CyanogenMod

    Version Information
    Status: Alpha

    Created 2016-03-21
    Last Updated 2017-04-11
    62
    Downloads

    ROM

    ROM - Beta 2 (20161210)
    Galaxy Tab 3 10.1 3G : santos103g (MD5)
    Galaxy Tab 3 10.1 Wifi : santos10wifi (MD5)
    Galaxy Tab 3 10.1 LTE : santos10lte (MD5)

    You can find old versions on AndroidFileHost. Version code is in file description.

    Houdini 6.0.0_x.47745
    Houdini for Android 6.0

    GApps
    See Open Gapps, select Platform x86 and Android 6.0.

    Other

    Flash player (11.1.112.60)
    Flash player for x86
    Note: not much used nowadays but useful if you want to play flash games.
    35
    Changes

    Changelog

    Beta 2 (20161210)
    - Fixed audio calls
    - Switched to dlmalloc

    Old changes


    Beta 1 (20161204)
    - Fixed freezes
    - Fixed AGPS
    - Cleaned up sensors hal
    - Use opensource audio hal
    - Added FIOPS io scheduler

    Alpha 7 (20161121)
    - CM update (android 6.0.1_r74)
    - Added software DRM support (Level 3)
    - Fixed touchscreen lags (maybe not all lags, thanks to @Alphita and @KNGPN Q w Q)
    - Fixed lock screen rotation (thanks to @tinko975)
    - Fixed Google SetupWizard loop when no network is available (CM)

    Alpha 6 (20161018)
    - CM update
    - Updated kernel memory management (and removed samsung specific code)
    - Updated kernel android drivers
    - Fixed button lights always on when disabled
    - Fixed rotation (small) bug
    - Fixed deep sleep issues
    - Fixed many reboot issues
    - Enabled CABC

    Alpha 5 (20160822)
    - Updated to stable/cm-13.0-ZNH5Y branch
    - Enabled Doze mode (thanks to @vin_)
    - Enabled 180deg rotation by default
    - Enabled swap volume keys on rotation by default
    - Added MHL/HDMI support
    - Added houdini Intel patches for better compatibility
    - Added USB charger port support
    - Fixed fast/slow charging reports
    - Fixed buttons backlight on key touch only
    - All kernel modules are now builtin
    - Various tweaks

    Alpha 4 (20160731)
    - Switched back to stable/cm-13.0-ZNH0E branch

    Alpha 3 (20160727)
    - CM update
    - Fixed Flash Player
    - Fixed /dev/last_kmsg
    - Fixed cpuset
    - Tweaked power management
    - Implemented CM power profiles (battery modes)
    - Added color profile setting (in LiveDisplay)
    - Added Advanced Settings (mDNIe scenario, large/small capacitive keys, buttons light on screen/button touch)
    - Added stock charger images

    Alpha 2 (20160430)
    - Based on stable/cm-13.0-ZNH2K branch
    - First try at RIL (3G and LTE)
    - Fixed Wifi tethering (thanks @deadfun)
    - Enabled and tweaked cpusets (fixes SMP "bug")
    - Updated and tweaked cpufreq interactive
    - Updated xpad driver (thanks @X-Coder)
    - Updated kernel config (merged android recommended settings)
    - Added bfq io scheduler
    - Enabled deadline scheduler
    - Enabled powersave cpufreq scaling governor

    Alpha 1 (20160321)
    - First release
    - Based on stable/cm-13.0-ZNH0E branch
    20
    I miss @nels83 , is the project still on?

    Sent from my SM-G7102 using Tapatalk

    Yep, still working on it. And since the wifi bug is finally fixed (in LineageOS) work will start again and you should get a first preview of LO14.1 soon ;)
    19
    Nougat status

    As many of you agree, I'll stop CM12.1 support (well, it has not been updated since some time now anyway).

    I'll start CM14.0 port in the next weeks. For what it's worth, I think there should be no major problem in getting CM14.0 running on our device.
    The biggest issue will be Houdini. If we can't get our hands on a nougat version, arm support won't be available and less apps will work.

    Thanks to everyone for the support and the reports.

    (@sashokmc I think I answered all your questions :D)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone