[Source][Manifest] CM-10.2 - Galaxy Tab 3 10.1 Android Development

Hi Folks
I've been hacking away getting CM-10.2 to build for x86 based devices, It turned out to be not too bad in the end with a couple of patches here and there to get things building :good:
I already submitted the patch for bionic upstream to CM and will submitting the busybox / build system changes after I run a couple of more tests to make sure I haven't broken anything elsewhere. In the meantime I've setup a custom manifest which "should" build a x86 cm-10.2 without error
I've only provided a basic device tree as I've not got a device ( yet! ) and am I reluctant to do blind builds as I rather not be responsible for some ones shiny expensive brick on account of something I've forgotten, included or plain f'ed up etc.
As this is not a lesson in how to build CM from source, I'll just say the magic words are
Code:
repo init -u git://github.com/trevd/android_manifest.git -b cm-10.2 -m p52xx.xml
repo sync
Like I mentioned the Device Tree is very basic and there's still much to do with regards .. well everything really but mainly the hardware libraries and what is open source and what isn't, at this stage it shouldn't cause too much of an issue for all the hardware libraries ( those found in /system/lib/hw and /system/vendor/hw ) to be ripped from the device because the api levels haven't changed between 4.3 and 4.2.2 AFAIK .
Anyway It's a starter for 10 to anyone who's interested once again if anyone is making changes to the device tree the obviously you are free to fork the project github or if you send me your github user name I'll happily add you as a collaborator to the existing repo ( https://github.com/trevd/android_device_samsung_p52xx )
Hack On Folks! :laugh:

---

Ill have a look to complete the device tree this week

---

deleted

---

Hi Folks,
Just a quick update on this, The bionic and busybox patches are now upstream in cyanogenmod's sources, So it's Just the kernel building and a small patch to powertop to see CM's source's building out of the box without the need for my "special" manifest :good:

---

I don't want to sound bossy or anything
May I ask if there will some sort of vanilla ROM for the Galaxy Tab 3 10.1 wifi variant?
Because Touchwiz seems to slow down the device quite a lot.
I do not wish to be in polite, I apologise if I am

---

Battlehero said:
May I ask if there will some sort of vanilla ROM for the Galaxy Tab 3 10.1 wifi variant?
Because Touchwiz seems to slow down the device quite a lot.
I do not wish to be in polite, I apologise if I am
Click to expand...
Click to collapse
Not from me there won't be , sorry . I'm just doing a bit of "device enabling" here at the minute. But build roms isn't really that difficult once you get started Get Involved

---

trevd said:
Not from me there won't be , sorry . I'm just doing a bit of "device enabling" here at the minute. But build roms isn't really that difficult once you get started Get Involved
Click to expand...
Click to collapse
But I tried on the internet on how to port Cyanogenmod, but the process seems a difficult considering my knowledge of coding. I guess I'll just have to wait for a port
Thank you for your response.

---

Battlehero said:
But I tried on the internet on how to port Cyanogenmod, but the process seems a difficult considering my knowledge of coding. I guess I'll just have to wait for a port
Thank you for your response.
Click to expand...
Click to collapse
Admittedly , There is a learning curve involved and piecing together of information, mainly figuring out what a device is made up of this and then just doing and experimenting, Although it maybe a brave soul who tries that on a shiny £300GBP device with no previous experience.
This book is probably the only thing out there that kinda goes into details of adding new devices http://shop.oreilly.com/product/0636920021094.do . I picked up the electronic version for around $7 USD after searching around for vouchers for various ebook retailers although it's well worth its cover price.
I will say this manifest is a good start and does pull in the kernel for the device based off of samsung open source stuff
On a side note : I've been talking to some of the CM team while getting these patches upstream and they are actively working on adding x86 support internally so who knows you might see something official pop out [ ** starts the rumor-mill ** ]

---

Thank You!
trevd said:
Admittedly , There is a learning curve involved and piecing together of information, mainly figuring out what a device is made up of this and then just doing and experimenting, Although it maybe a brave soul who tries that on a shiny £300GBP device with no previous experience.
This book is probably the only thing out there that kinda goes into details of adding new devices http://shop.oreilly.com/product/0636920021094.do . I picked up the electronic version for around $7 USD after searching around for vouchers for various ebook retailers although it's well worth its cover price.
I will say this manifest is a good start and does pull in the kernel for the device based off of samsung open source stuff
On a side note : I've been talking to some of the CM team while getting these patches upstream and they are actively working on adding x86 support internally so who knows you might see something official pop out [ ** starts the rumor-mill ** ]
Click to expand...
Click to collapse
You sir certainly have risen my hopes! but I don't know if I want to start getting into Android development as of yet because I have my school courses to study. I will see later on if I have some free time to start learning how to do basic coding!
I think I will just wait for someone to make a x86 version of CyanogenMod and hopefully they'll make an official release for this tablet as I think this 10.1 inch tablet has some potential.

---

trevd said:
Hi Folks
I've been hacking away getting CM-10.2 to build for x86 based devices, It turned out to be not too bad in the end with a couple of patches here and there to get things building :good:
I already submitted the patch for bionic upstream to CM and will submitting the busybox / build system changes after I run a couple of more tests to make sure I haven't broken anything elsewhere. In the meantime I've setup a custom manifest which "should" build a x86 cm-10.2 without error
I've only provided a basic device tree as I've not got a device ( yet! ) and am I reluctant to do blind builds as I rather not be responsible for some ones shiny expensive brick on account of something I've forgotten, included or plain f'ed up etc.
As this is not a lesson in how to build CM from source, I'll just say the magic words are
Code:
repo init -u git://github.com/trevd/android_manifest.git -b cm-10.2 -m p52xx.xml
repo sync
Like I mentioned the Device Tree is very basic and there's still much to do with regards .. well everything really but mainly the hardware libraries and what is open source and what isn't, at this stage it shouldn't cause too much of an issue for all the hardware libraries ( those found in /system/lib/hw and /system/vendor/hw ) to be ripped from the device because the api levels haven't changed between 4.3 and 4.2.2 AFAIK .
Anyway It's a starter for 10 to anyone who's interested once again if anyone is making changes to the device tree the obviously you are free to fork the project github or if you send me your github user name I'll happily add you as a collaborator to the existing repo ( https://github.com/trevd/android_device_samsung_p52xx )
Hack On Folks! :laugh:
Click to expand...
Click to collapse
Are you still in development for this device ?

---

Hi
I will refer you to this weeks cm blog post
http://www.cyanogenmod.org/blog/last-week-in-cm-oct-27-13
and this patch
http://review.cyanogenmod.org/#/c/51502/
By the way that post reads I was never working on it lol. Regardless it seems official support. isn't too far off in the future.
I pushed pciutils last week so My work is done here as you can now build cm's userspaces for x86 ..kernel building however is as I told them. I'd let them figure out the changes internally because the file is a wreck and it should never have been left to get to that point... it's there mess to sort
Sent from my GT-P1000 using XDA Premium 4 mobile app

---

There is now a build of cm10.2 for Razr i....its alpha but its booting and works
Enviado desde mi XT890 mediante Tapatalk

---

Marco Lomas said:
There is now a build of cm10.2 for Razr i....its alpha but its booting and works
Enviado desde mi XT890 mediante Tapatalk
Click to expand...
Click to collapse
Its fully functional on the 10.1?
Sent from my GT-P5210 using xda app-developers app

---

EVIIIL said:
Its fully functional on the 10.1?
Sent from my GT-P5210 using xda app-developers app
Click to expand...
Click to collapse
No, its only an alpha build NOT for galaxy, its for Razr I, but its also a x86 processor
Enviado desde mi XT890 mediante Tapatalk

---

Marco Lomas said:
No, its only an alpha build NOT for galaxy, its for Razr I, but its also a x86 processor
Enviado desde mi XT890 mediante Tapatalk
Click to expand...
Click to collapse
Step in the right direction. Sucks that there isnt any options for these.
Sent from my GT-P5210 using xda app-developers app

---

EVIIIL said:
Step in the right direction. Sucks that there isnt any options for these.
Sent from my GT-P5210 using xda app-developers app
Click to expand...
Click to collapse
It wouldn't take much effort to get the razri rom to work, just some small changes here and there.

---

still working on it... but itś a pain..
New recovery builds, but doeasn boot...
CM never completes the build.... Pain in the Brain.
Patching now, lets see what will happen.
Made:
device_samsung_p52XX
&
vendor_samsung_p52xx
When I hava an alpha you will hear from me.
But a new kernel & recovery will be posted before that... I think....
If you wanna collaberate, sand me a PM... as i'm not a great cm guru
PS. I need a boot.img from a p5200

---

And trevd... I found a file in the system that is interesting...
Have you any idea on how we might be able to use it?
Process.P
Code:
out/target/product/santos103g/obj/STATIC_LIBRARIES/libsec_cryptfs_intermediates/../../../system/vold/Process.o: \
vendor/samsung/common/external/libsec_devenc/cryptfs/../../../system/vold/Process.cpp \
build/core/combo/include/arch/target_linux-x86/AndroidConfig.h \
bionic/libc/include/stdio.h bionic/libc/include/sys/cdefs.h \
bionic/libc/include/sys/cdefs_elf.h \
bionic/libc/include/android/api-level.h bionic/libc/include/sys/_types.h \
bionic/libc/arch-x86/include/machine/_types.h \
/home/se.infra/jenkins1/workspace/HUDSON_JELLYBEANPLUS_SANTOS10-RF_EUR-OPEN_REL-USER/android/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/include/stdarg.h \
/home/se.infra/jenkins1/workspace/HUDSON_JELLYBEANPLUS_SANTOS10-RF_EUR-OPEN_REL-USER/android/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/include/stddef.h \
bionic/libc/include/sys/types.h bionic/libc/include/stdint.h \
bionic/libc/kernel/common/linux/posix_types.h \
bionic/libc/kernel/common/linux/stddef.h \
bionic/libc/kernel/common/linux/compiler.h \
bionic/libc/kernel/arch-x86/asm/posix_types.h \
bionic/libc/kernel/arch-x86/asm/posix_types_32.h \
bionic/libc/kernel/arch-x86/asm/types.h \
bionic/libc/kernel/common/linux/types.h \
bionic/libc/arch-x86/include/machine/kernel.h \
bionic/libc/include/sys/sysmacros.h bionic/libc/include/unistd.h \
bionic/libc/include/sys/select.h bionic/libc/include/sys/time.h \
bionic/libc/kernel/common/linux/time.h bionic/libc/include/signal.h \
bionic/libc/include/limits.h bionic/libc/include/sys/limits.h \
bionic/libc/kernel/common/linux/limits.h \
bionic/libc/arch-x86/include/machine/internal_types.h \
bionic/libc/arch-x86/include/machine/limits.h \
bionic/libc/include/sys/syslimits.h \
bionic/libc/kernel/arch-x86/asm/page.h \
bionic/libc/kernel/arch-x86/asm/page_32.h bionic/libc/include/string.h \
bionic/libc/include/malloc.h bionic/libc/kernel/arch-x86/asm/signal.h \
bionic/libc/kernel/common/asm-generic/signal.h \
bionic/libc/include/errno.h bionic/libc/kernel/common/linux/errno.h \
bionic/libc/kernel/arch-x86/asm/errno.h \
bionic/libc/kernel/common/asm-generic/errno.h \
bionic/libc/kernel/common/asm-generic/errno-base.h \
bionic/libc/kernel/arch-x86/asm/siginfo.h \
bionic/libc/kernel/common/asm-generic/siginfo.h \
bionic/libc/include/sys/sysconf.h \
bionic/libc/kernel/common/linux/capability.h \
bionic/libc/include/pathconf.h bionic/libc/include/fcntl.h \
bionic/libc/kernel/common/linux/fcntl.h \
bionic/libc/kernel/arch-x86/asm/fcntl.h \
bionic/libc/kernel/common/asm-generic/fcntl.h \
bionic/libc/include/dirent.h bionic/libc/include/ctype.h \
bionic/libc/include/pwd.h bionic/libc/include/stdlib.h \
bionic/libc/include/alloca.h bionic/libc/include/strings.h \
bionic/libc/include/memory.h bionic/libc/include/poll.h \
bionic/libc/kernel/common/linux/poll.h \
bionic/libc/kernel/arch-x86/asm/poll.h \
bionic/libc/kernel/common/asm-generic/poll.h \
bionic/libc/include/sys/stat.h bionic/libc/kernel/common/linux/stat.h \
bionic/libc/arch-x86/include/endian.h bionic/libc/include/sys/endian.h \
system/core/include/cutils/log.h bionic/libc/include/time.h \
bionic/libc/include/pthread.h bionic/libc/include/sched.h \
system/core/include/cutils/uio.h bionic/libc/include/sys/uio.h \
bionic/libc/kernel/common/linux/uio.h system/core/include/cutils/logd.h \
system/core/include/android/log.h \
vendor/samsung/common/external/libsec_devenc/cryptfs/../../../system/vold/Process.h
vendor/samsung/common/external/libsec_devenc/cryptfs/../../../system/vold/Process.cpp :
build/core/combo/include/arch/target_linux-x86/AndroidConfig.h :
bionic/libc/include/stdio.h bionic/libc/include/sys/cdefs.h :
bionic/libc/include/sys/cdefs_elf.h :
bionic/libc/include/android/api-level.h bionic/libc/include/sys/_types.h :
bionic/libc/arch-x86/include/machine/_types.h :
/home/se.infra/jenkins1/workspace/HUDSON_JELLYBEANPLUS_SANTOS10-RF_EUR-OPEN_REL-USER/android/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/include/stdarg.h :
/home/se.infra/jenkins1/workspace/HUDSON_JELLYBEANPLUS_SANTOS10-RF_EUR-OPEN_REL-USER/android/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/../lib/gcc/i686-linux-android/4.6/include/stddef.h :
bionic/libc/include/sys/types.h bionic/libc/include/stdint.h :
bionic/libc/kernel/common/linux/posix_types.h :
bionic/libc/kernel/common/linux/stddef.h :
bionic/libc/kernel/common/linux/compiler.h :
bionic/libc/kernel/arch-x86/asm/posix_types.h :
bionic/libc/kernel/arch-x86/asm/posix_types_32.h :
bionic/libc/kernel/arch-x86/asm/types.h :
bionic/libc/kernel/common/linux/types.h :
bionic/libc/arch-x86/include/machine/kernel.h :
bionic/libc/include/sys/sysmacros.h bionic/libc/include/unistd.h :
bionic/libc/include/sys/select.h bionic/libc/include/sys/time.h :
bionic/libc/kernel/common/linux/time.h bionic/libc/include/signal.h :
bionic/libc/include/limits.h bionic/libc/include/sys/limits.h :
bionic/libc/kernel/common/linux/limits.h :
bionic/libc/arch-x86/include/machine/internal_types.h :
bionic/libc/arch-x86/include/machine/limits.h :
bionic/libc/include/sys/syslimits.h :
bionic/libc/kernel/arch-x86/asm/page.h :
bionic/libc/kernel/arch-x86/asm/page_32.h bionic/libc/include/string.h :
bionic/libc/include/malloc.h bionic/libc/kernel/arch-x86/asm/signal.h :
bionic/libc/kernel/common/asm-generic/signal.h :
bionic/libc/include/errno.h bionic/libc/kernel/common/linux/errno.h :
bionic/libc/kernel/arch-x86/asm/errno.h :
bionic/libc/kernel/common/asm-generic/errno.h :
bionic/libc/kernel/common/asm-generic/errno-base.h :
bionic/libc/kernel/arch-x86/asm/siginfo.h :
bionic/libc/kernel/common/asm-generic/siginfo.h :
bionic/libc/include/sys/sysconf.h :
bionic/libc/kernel/common/linux/capability.h :
bionic/libc/include/pathconf.h bionic/libc/include/fcntl.h :
bionic/libc/kernel/common/linux/fcntl.h :
bionic/libc/kernel/arch-x86/asm/fcntl.h :
bionic/libc/kernel/common/asm-generic/fcntl.h :
bionic/libc/include/dirent.h bionic/libc/include/ctype.h :
bionic/libc/include/pwd.h bionic/libc/include/stdlib.h :
bionic/libc/include/alloca.h bionic/libc/include/strings.h :
bionic/libc/include/memory.h bionic/libc/include/poll.h :
bionic/libc/kernel/common/linux/poll.h :
bionic/libc/kernel/arch-x86/asm/poll.h :
bionic/libc/kernel/common/asm-generic/poll.h :
bionic/libc/include/sys/stat.h bionic/libc/kernel/common/linux/stat.h :
bionic/libc/arch-x86/include/endian.h bionic/libc/include/sys/endian.h :
system/core/include/cutils/log.h bionic/libc/include/time.h :
bionic/libc/include/pthread.h bionic/libc/include/sched.h :
system/core/include/cutils/uio.h bionic/libc/include/sys/uio.h :
bionic/libc/kernel/common/linux/uio.h system/core/include/cutils/logd.h :
system/core/include/android/log.h :
vendor/samsung/common/external/libsec_devenc/cryptfs/../../../system/vold/Process.h :
It has a Process.o as well in: /system/vold

---

One question
Is the Samsung Open Source Center a bit of helping?
Sent from my GT-P5210 using xda app-developers app

---

Take it. Here is a boot.img from GT-P5210. Hope it helps!