[Development][Source]CyanogenMod 11 for SGT-3 10.1

Search This thread

Angel_666

Senior Member
Mar 18, 2009
317
856
This is development thread for CM11 building on Samsung GalaxyTab3 10.1 devices, based on Intel Clover Trail platform. (x86)

Device tree: https://github.com/Angel666/android_device_samsung_santos103g

CM11 source repo:
Code:
[FONT=Arial]repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0[/FONT]
Patches for CM source needed to build rom. Made by HazouPH:

https://github.com/HazouPH/android_device_motorola_smi/tree/jellybean/patch

Working for now:
hardware accel (with some bugs)
storages and mtp mounting
Ril (partially)
Lights and buttons
Houdini service
anything else I can forgot..

Not working for now:
Wi-Fi (can not obtain mac)
BT (can not obtain mac)
Camera (service works, app can't connect)
SeLinux security (disabled)
Sound (Samsung lib won't work)
Basic CM Launcher3 is glitchy! I don't know why. Third-party launcers works well (testing by GOlauncher)
anything else I can forgot..

Images for testing: >DOWNLOAD< 3g version only for now!

WARNING! This images are for testing purposes only! Don't flash it if you don't know what you doing! Rom is almost UNUSABLE for enduser! Work in progress....

0.Unpack zip's.
1. Flash boot by Odin
2. Flash recovery by Odin
3. Enter to recovery and Wipe cache, dalvik, system and data.
4 Flash system by Odin


I appreciate any possible help (testing, donations, devs and experienced users advices). Let's speedup the process! :)
 
Last edited:

woopdedoda

Senior Member
Jun 4, 2012
59
29
Hey do you think there would be any chance of building this with the abyssplug governor? Or would the fact that hyperthreading is present screw things up? And is it possible to overclock? Thanks for all your work @Angel_666, been following the twrp and manifest threads for a while now, Great progress, just wanted to say thanks.
 

Angel_666

Senior Member
Mar 18, 2009
317
856
Hey do you think there would be any chance of building this with the abyssplug governor? Or would the fact that hyperthreading is present screw things up? And is it possible to overclock? Thanks for all your work @Angel_666, been following the twrp and manifest threads for a while now, Great progress, just wanted to say thanks.

As about CPU - I don't find any information that it can work stable more than 1.6Ghz. But our GPU runs at 400Mhz and can be overclocked to 533 i think.

First post updated.
 
Last edited:

woopdedoda

Senior Member
Jun 4, 2012
59
29
OK, didn't know that. That's the same chip that's in the i9500 right? Would comparing the gpu code for that help with hardware acceleration?
 
Last edited:

superboom

Senior Member
Aug 25, 2012
235
84
I'm now testing CM11
@Angel_666
I flashed the Images and I cant boot CM
I'm always stuck at "Samsung Galaxy Tab 3"
I can only boot to TWRP and Download
logcat doesn't work.
 
Last edited:

Angel_666

Senior Member
Mar 18, 2009
317
856
I'm now testing CM11
@Angel_666
I flashed the Images and I cant boot CM
I'm always stuck at "Samsung Galaxy Tab 3"
I can only boot to TWRP and Download
logcat doesn't work.

flash boot again, flash recovery, go to advanced wipe in recovery and check ALL options exept last (microSD). After process done, flash system img. Try and tell me.

P.S. "samsung logo" it not a bootloop. In your case system does not even run init process. (cm logo). Just checked all uploaded files on my tab p5200. All ok. CM logo, then system start. Before flashing i formatted my device and it was clean like a baby.
 
Last edited:
  • Like
Reactions: pug1

Setialpha

Senior Member
Jul 24, 2011
2,555
5,886
Nürnberg
www.nanolx.org
OnePlus 7T
For me it failed after wiping /system. I restored it from backup, wiped cache/data, flashed again, it worked.

With pimpdroid, not yet tested with cm11, but the issue is the same.

Gesendet von meinem GT-I9100G mit Tapatalk
 

Angel_666

Senior Member
Mar 18, 2009
317
856
For me it failed after wiping /system. I restored it from backup, wiped cache/data, flashed again, it worked.

With pimpdroid, not yet tested with cm11, but the issue is the same.

Gesendet von meinem GT-I9100G mit Tapatalk

Don't understood - CM works or not? Your device is p5210?

Ok now. I setup stock samsung firmware, and then repeat all process step by step. Will post results later.
 
Last edited:
  • Like
Reactions: pug1

pug1

Senior Member
Jun 16, 2012
647
192
Sheffield
Ah. Sorry.

Ok. I flash my device by stock samsung firmware. Then, i flash CM11 as described at first post. CM boots OK and setup wizard turn on. My device is p5200 (3g).

What needs to be altered for it to boot on p5210.

I downloaded cm11 source last night and am gonna try put a build together.... Just need to figure out local manifests to sync your github :thumbup: thanks for that BTW.

Quick question.... How come you are having to flash via Odin? Thought that they could be flashed by recovery. Have you tried any gapps yet

Sent from my GT-I9300 using xda app-developers app
 
  • Like
Reactions: superboom

Angel_666

Senior Member
Mar 18, 2009
317
856
What needs to be altered for it to boot on p5210.

I downloaded cm11 source last night and am gonna try put a build together.... Just need to figure out local manifests to sync your github :thumbup: thanks for that BTW.

Quick question.... How come you are having to flash via Odin? Thought that they could be flashed by recovery. Have you tried any gapps yet

Sent from my GT-I9300 using xda app-developers app

As for img files via odin - "make otapackage" return some errors to me. That's why i use img. As for CM boot on p5210 - give me your build.prop from stock firmware - i'll tru to fix this.
 
  • Like
Reactions: pug1

hfase

Senior Member
Jan 11, 2013
104
40
hfase.com
As for img files via odin - "make otapackage" return some errors to me. That's why i use img. As for CM boot on p5210 - give me your build.prop from stock firmware - i'll tru to fix this.

Here is the build.prop for the P5210

Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=JDQ39.P5210UEUAMK1
ro.build.version.incremental=P5210UEUAMK1
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Tue Nov 26 14:28:02 KST 2013
ro.build.date.utc=1385443682
ro.build.type=user
ro.build.user=se.infra
ro.build.host=R0210-17
ro.build.tags=release-keys
ro.product.model=GT-P5210
ro.product.brand=samsung
ro.product.name=santos10wifiue
ro.product.device=santos10wifi
ro.product.board=clovertrail
ro.product.cpu.abi=x86
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=clovertrail
# ro.build.product is obsolete; use ro.product.device
ro.build.product=santos10wifi
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=santos10wifiue-user 4.2.2 JDQ39 P5210UEUAMK1 release-keys
ro.build.fingerprint=samsung/santos10wifiue/santos10wifi:4.2.2/JDQ39/P5210UEUAMK1:user/release-keys
ro.build.characteristics=tablet
# Samsung Specific Properties
ro.build.PDA=P5210UEUAMK1
ro.build.hidden_ver=P5210UEUAMK1
ro.build.changelist=850131
ro.product_ship=true
ro.chipname=clovertrail
# end build properties
#
# system.prop for santos10 wifi
#

ro.carrier=wifi-only
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0

# System property for Default Brightness
ro.lcd_brightness=118

# System property for Min Brightness
ro.lcd_min_brightness=10

# System Property for Intel MDS
ro.mds.enable=true
ro.kernel.qemu=0

persist.sys.storage_preload=1
# System property for Font Clarity
persist.sys.font_clarity=0

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.sf.lcd_density=160
ro.hdcp2.rx=tz
ro.secwvk=144
ro.sec.fle.encryption=true
ro.error.receiver.default=com.samsung.receiver.error
ro.config.ringtone=Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Alarm_Morning_flower.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.crypto.support=recovery_mount|others
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.jit.code_cache_size=1048576
persist.tel.hot_swap.support=true
drm.service.enabled=true
ro.com.google.apphider=off
ro.com.google.gmsversion=4.2_r3
ro.ril.status.polling.enable=0
ro.product.cpu.abi2=armeabi-v7a
ro.config.personality=compat_layout
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
 

Top Liked Posts

  • There are no posts matching your filters.
  • 52
    This is development thread for CM11 building on Samsung GalaxyTab3 10.1 devices, based on Intel Clover Trail platform. (x86)

    Device tree: https://github.com/Angel666/android_device_samsung_santos103g

    CM11 source repo:
    Code:
    [FONT=Arial]repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0[/FONT]
    Patches for CM source needed to build rom. Made by HazouPH:

    https://github.com/HazouPH/android_device_motorola_smi/tree/jellybean/patch

    Working for now:
    hardware accel (with some bugs)
    storages and mtp mounting
    Ril (partially)
    Lights and buttons
    Houdini service
    anything else I can forgot..

    Not working for now:
    Wi-Fi (can not obtain mac)
    BT (can not obtain mac)
    Camera (service works, app can't connect)
    SeLinux security (disabled)
    Sound (Samsung lib won't work)
    Basic CM Launcher3 is glitchy! I don't know why. Third-party launcers works well (testing by GOlauncher)
    anything else I can forgot..

    Images for testing: >DOWNLOAD< 3g version only for now!

    WARNING! This images are for testing purposes only! Don't flash it if you don't know what you doing! Rom is almost UNUSABLE for enduser! Work in progress....

    0.Unpack zip's.
    1. Flash boot by Odin
    2. Flash recovery by Odin
    3. Enter to recovery and Wipe cache, dalvik, system and data.
    4 Flash system by Odin


    I appreciate any possible help (testing, donations, devs and experienced users advices). Let's speedup the process! :)
    18
    Great news!!!
    I can't wait to get my hands on a working CM11 :good:

    Yes, after fixes and testing, i will create device tree for wi-fi version too.
    18
    Ril fully works, 3g data works, IR led works, all sensors and light works. Still working on sound and mixer roots.
    13
    Well, KitKat is out. Syncing CM git and downloading p5210 firmware....
    12
    Ok, boot and work properly

    Sent from my SPH-L720 using XDA Premium 4 mobile app

    ---------- Post added at 10:24 AM ---------- Previous post was at 10:24 AM ----------



    No this tab hasn't been updated yet

    Sent from my SPH-L720 using XDA Premium 4 mobile app

    Let's wait. If no updates until july - i start CM11 anyway. Just to clear the things - if Sammy realise update, it will be very easy to port CM. If not - it will be harder, but we'll do it anyway, right? ;)